The patent badge is an abbreviated version of the USPTO patent document. The patent badge does contain a link to the full patent document.
The patent badge is an abbreviated version of the USPTO patent document. The patent badge covers the following: Patent number, Date patent was issued, Date patent was filed, Title of the patent, Applicant, Inventor, Assignee, Attorney firm, Primary examiner, Assistant examiner, CPCs, and Abstract. The patent badge does contain a link to the full patent document (in Adobe Acrobat format, aka pdf). To download or print any patent click here.
Patent No.:
Date of Patent:
Sep. 20, 2005
Filed:
Dec. 27, 2000
Ronald M. Smith, Sr., Wappingers Falls, NY (US);
Edward J. D'avignon, Kingston, NY (US);
Robert S. Debellis, Raleigh, NC (US);
Randall J. Easter, Poughquag, NY (US);
Lucina L. Green, Verbank, NY (US);
Michael J. Kelly, Poughkeepsie, NY (US);
William A. Merz, Wappingers Falls, NY (US);
Vincent A. Spano, Poughkeepsie, NY (US);
Phil Chi-chung Yeh, Poughkeepsie, NY (US);
Ronald M. Smith, Sr., Wappingers Falls, NY (US);
Edward J. D'Avignon, Kingston, NY (US);
Robert S. DeBellis, Raleigh, NC (US);
Randall J. Easter, Poughquag, NY (US);
Lucina L. Green, Verbank, NY (US);
Michael J. Kelly, Poughkeepsie, NY (US);
William A. Merz, Wappingers Falls, NY (US);
Vincent A. Spano, Poughkeepsie, NY (US);
Phil Chi-Chung Yeh, Poughkeepsie, NY (US);
International Business Machines Corporation, Armonk, NY (US);
Abstract
Public key security control (PKSC) is provided for a cryptographic module by means of digitally signed communications between the module and one or more authorities with whom it interacts. Authorities interact with the crypto module by means of unsigned queries seeking nonsecret information or signed commands for performing specified operations. Each command signed by an authority also contains a transaction sequence number (TSN), which must match a corresponding number stored by the crypto module for the authority. The TSN for each authority is initially generated randomly and is incremented for each command accepted from that authority. A signature requirement array (SRA) controls the number of signatures required to validate each command type. Upon receiving a signed command from one or more authorities, the SRA is examined to determine whether a required number of authorities permitted to sign the command have signed the command for each signature requirement specification defined for that command type. A command requiring multiple signatures is held in a pending command register (PCR) while awaiting the required cosignatures. The crypto module also stores a single crypto module signature sequence number (CMSSN) which it increments for each reply to any authority to enable one authority to determine whether any other authority has communicated with the module.