G06F21/70—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer

G06F21/71—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information

G06F21/73—Protecting specific internal or peripheral components, in which the protection of a component leads to protection of the entire computer to assure secure computing or processing of information by creating or determining hardware identification, e.g. serial numbers

H04L63/08—Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network

H04L63/0853—Network architectures or network communication protocols for network security for supporting authentication of entities communicating through a packet data network using an additional device, e.g. smartcard, SIM or a different communication terminal

H04L9/0816—Key establishment, i.e. cryptographic processes or cryptographic protocols whereby a shared secret becomes available to two or more parties, for subsequent use

H04L9/0838—Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these

H04L9/0841—Key agreement, i.e. key establishment technique in which a shared key is derived by parties as a function of information contributed by, or associated with, each of these involving Diffie-Hellman or related key agreement protocols

H04L2209/125—Parallelization or pipelining, e.g. for accelerating processing of cryptographic operations

Abstract

Delivering a Direct Proof private key to a device installed in a client computer system in the field may be accomplished in a secure manner without requiring significant non-volatile storage in the device. A unique pseudo-random value is generated and stored in the device at manufacturing time. The pseudo-random value is used to generate a symmetric key for encrypting a data structure holding a Direct Proof private key and a private key digest associated with the device. The resulting-encrypted data structure is stored on a removable storage medium (such as a CD), and distributed to the owner of the client computer system. When the device is initialized on the client computer system, the system checks if a localized encrypted data structure is present in the system. If not, the system obtains the associated encrypted data structure from the removable storage medium. The device decrypts the encrypted data structure using a symmetric key regenerated from its stored pseudo-random value to obtain the Direct Proof private key. If the private key is valid, it may be used for subsequent authentication processing by the device in the client computer system.

Description

Some processing system architectures supporting content protection and/or computer security features require that specially-protected or “trusted” software modules be able to create an authenticated encrypted communications session with specific protected or “trusted” hardware devices in the processing system (such as graphics controller cards, for example). One commonly used method for both identifying the device and simultaneously establishing the encrypted communications session is to use a one-side authenticated Diffie-Hellman (DH) key exchange process. In this process, the device is assigned a unique public/private Rivest, Shamir and Adelman (RSA) algorithm key pair or a unique Elliptic Curve Cryptography (ECC) key pair. However, because this authentication process uses RSA or ECC keys, the device then has a unique and provable identity, which can raise privacy concerns. In the worst case, these concerns may result in a lack of support from original equipment manufacturers (OEMs) for building trustable devices providing this kind of security.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the present invention will become apparent from the following detailed description of the present invention in which:

FIG. 1 illustrates a system featuring a platform implemented with a Trusted Platform Module (TPM) that operates in accordance with one embodiment of the invention;

FIG. 2 illustrates a first embodiment of the platform including the TPM of FIG. 1.

FIG. 3 illustrates a second embodiment of the platform including the TPM of FIG. 1.

FIG. 4 illustrates an exemplary embodiment of a computer system implemented with the TPM of FIG. 2.

FIG. 5 is a diagram of a system for distributing Direct Proof keys according to an embodiment of the present invention;

FIG. 6 is a flow diagram illustrating stages of a method of distributing Direct Proof keys according to an embodiment of the present invention;

FIG. 7 is a flow diagram illustrating device manufacturing set-up processing according to an embodiment of the present invention;

FIG. 8 is a flow diagram illustrating device manufacturing production processing according to an embodiment of the present invention;

FIG. 9 is a flow diagram of client computer system set-up processing according to an embodiment of the present invention; and

FIG. 10 is a flow diagram of client computer system processing according to an embodiment of the present invention.

DETAILED DESCRIPTION

Using the Direct Proof-based Diffie-Hellman key exchange protocol to permit protected/trusted devices to authenticate themselves and to establish an encrypted communication session with trusted software modules avoids creating any unique identity information in the processing system, and thereby avoids introducing privacy concerns. However, directly embedding a Direct Proof private key in a device on a manufacturing line requires more protected non-volatile storage on the device than other approaches, increasing device costs. An embodiment of the present invention is a method to allow the Direct Proof private key (e.g., used for signing) to be delivered in a secure manner on a distribution compact disc-read only memory (CD-ROM), and subsequently installed in the device by the device itself. The method presented in this invention is designed so that the device does not need to reveal identity information for the installation process. In one embodiment, the reduction in device storage required to support this capability may be from approximately 300 to 700 bytes down to approximately 20 bytes. This reduction in the amount of non-volatile storage required to implement Direct Proof-based Diffie-Hellman key exchange for devices may result in broader adoption of this technique.

Reference in the specification to “one embodiment” or “an embodiment” of the present invention means that a particular feature, structure or characteristic described in connection with the embodiment is included in at least one embodiment of the present invention. Thus, the appearances of the phrase “in one embodiment” appearing in various places throughout the specification are not necessarily all referring to the same embodiment.

In the following description, certain terminology is used to describe certain features of one or more embodiments of the invention. For instance, “platform” is defined as any type of communication device that is adapted to transmit and receive information. Examples of various platforms include, but are not limited or restricted to computer systems, personal digital assistants, cellular telephones, set-top boxes, facsimile machines, printers, modems, routers, or the like. A “communication link” is broadly defined as one or more information-carrying mediums adapted to a platform. Examples of various types of communication links include, but are not limited or restricted to electrical wire(s), optical fiber(s), cable(s), bus trace(s), or wireless signaling technology.

A “challenger” refers to any entity (e.g., person, platform, system, software, and/or device) that requests some verification of authenticity or authority from another entity. Normally, this is performed prior to disclosing or providing the requested information. A “responder” refers to any entity that has been requested to provide some proof of its authority, validity, and/or identity. A “device manufacturer,” which may be used interchangeably with “certifying manufacturer,” refers to any entity that manufactures or configures a platform or device.

As used herein, to “prove” or “convince” a challenger that a responder has possession or knowledge of some cryptographic information (e.g., digital signature, a secret such as a key, etc.) means that, based on the information and proof disclosed to the challenger, there is a high probability that the responder has the cryptographic information. To prove this to a challenger without “revealing” or “disclosing” the cryptographic information to the challenger means that, based on the information disclosed to the challenger, it would be computationally infeasible for the challenger to determine the cryptographic information.

Such proofs are hereinafter referred to as direct proofs. The term “direct proof” refers to zero-knowledge proofs, as these types of proofs are commonly known in the field. In particular, a specific Direct Proof protocol as referenced herein is the subject of co-pending patent application Ser. No. 10/306,336, filed on Nov. 27, 2002, entitled “System and Method for Establishing Trust Without Revealing Identity,” assigned to the owner of the present application. Direct Proof defines a protocol in which an issuer defines a family of many members that share common characteristics as defined by the issuer. The issuer generates a Family public and private key pair (Fpub and Fpri) that represents the family as a whole. Using Fpri, the issuer can also generate a unique Direct Proof private signing key (DPpri) for each individual member in the family. Any message signed by an individual DPpri can be verified using the family public key Fpub. However, such verification only identifies that the signer is a member of the family; no uniquely identifying information about the individual member is exposed. In one embodiment, the issuer may be a device manufacturer or delegate. That is, the issuer may be an entity with the ability to define device Families based on shared characteristics, generate the Family public/private key pair, and to create and inject DP private keys into devices. The issuer may also generate certificates for the Family public key that identify the source of the key and the characteristics of the device family.

Referring now to FIG. 1, an embodiment of a system featuring a platform implemented with a trusted hardware device (referred to as “Trusted Platform Module” or “TPM”) that operates in accordance with one embodiment of the invention is shown. A first platform 102 (Challenger) transmits a request 106 that a second platform 104 (Responder) provides information about itself. In response to request 106, second platform 104 provides the requested information 108.

Additionally, for heightened security, first platform 102 may need to verify that requested information 108 came from a device manufactured by either a selected device manufacturer or a selected group of device manufacturers (hereinafter referred to as “device manufacturer(s) 110”). For instance, for one embodiment of the invention, first platform 102 challenges second platform 104 to show that it has cryptographic information (e.g., a signature) generated by device manufacturer(s) 110. The challenge may be either incorporated into request 106 (as shown) or a separate transmission. Second platform 104 replies to the challenge by providing information, in the form of a reply, to convince first platform 102 that second platform 104 has cryptographic information generated by device manufacturer(s) 110, without revealing the cryptographic information. The reply may be either part of the requested information 108 (as shown) or a separate transmission.

In one embodiment of the invention, second platform 104 comprises a Trusted Platform Module (TPM) 115. TPM 115 is a cryptographic device that is manufactured by device manufacturer(s) 110. In one embodiment of the invention, TPM 115 comprises a processor with a small amount of on-chip memory encapsulated within a package. TPM 115 is configured to provide information to first platform 102 that would enable it to determine that a reply is transmitted from a valid TPM. The information used is content that would not make it likely that the TPM's or second platform's identity can be determined.

FIG. 2 illustrates a first embodiment of second platform 104 with TPM 115. For this embodiment of the invention, second platform 104 comprises a processor 202 coupled to TPM 115. In general, processor 202 is a device that processes information. For instance, in one embodiment of the invention, processor 202 may be implemented as a microprocessor, digital signal processor, micro-controller or even a state machine. Alternatively, in another embodiment of the invention, processor 202 may be implemented as programmable or hard-coded logic, such as Field Programmable Gate Arrays (FPGAs), transistor-transistor logic (TTL) logic, or even an Application Specific Integrated Circuit (ASIC).

Herein, second platform 104 further comprises a storage unit 206 to permit storage of cryptographic information such as one or more of the following: keys, hash values, signatures, certificates, etc. A hash value of “X” may be represented as “Hash(X)”. It is contemplated that such information may be stored within internal memory 220 of TPM 115 in lieu of storage unit 206 as shown in FIG. 3. The cryptographic information may be encrypted, especially if stored outside TPM 115.

FIG. 4 illustrates an embodiment of a platform including a computer system 300 implemented with TPM 115 of FIG. 2. Computer system 300 comprises a bus 302 and a processor 310 coupled to bus 302. Computer system 300 further comprises a main memory unit 304 and a static memory unit 306.

Herein, main memory unit 304 is volatile semiconductor memory for storing information and instructions executed by processor 310. Main memory 304 also may be used for storing temporary variables or other intermediate information during execution of instructions by processor 310. Static memory unit 306 is non-volatile semiconductor memory for storing information and instructions for processor 310 on a more permanent nature. Examples of static memory 306 include, but are not limited or restricted to read only memory (ROM). Both main memory unit 304 and static memory unit 306 are coupled to bus 302.

In one embodiment of the invention, computer system 300 further comprises a data storage device 308 such as a magnetic disk or optical disc and its corresponding drive may also be coupled to computer system 300 for storing information and instructions.

Computer system 300 can also be coupled via bus 302 to a graphics controller device 314, which controls a display (not shown) such as a cathode ray tube (CRT), Liquid Crystal Display (LCD) or any flat panel display, for displaying information to an end user. In one embodiment, it may be desired for the graphics controller to be able to establish an authenticated encrypted communications session with a software module being executed by the processor.

Typically, an alphanumeric input device 316 (e.g., keyboard, keypad, etc.) may be coupled to bus 302 for communicating information and/or command selections to processor 310. Another type of user input device is cursor control unit 318, such as a mouse, a trackball, touch pad, stylus, or cursor direction keys for communicating direction information and command selections to processor 310 and for controlling cursor movement on display 314.

A communication interface unit 320 is also coupled to bus 302. Examples of interface unit 320 include a modem, a network interface card, or other well-known interfaces used for coupling to a communication link forming part of a local or wide area network. In this manner, computer system 300 may be coupled to a number of clients and/or servers via a conventional network infrastructure, such as a company's Intranet and/or the Internet, for example.

It is appreciated that a lesser or more equipped computer system than described above may be desirable for certain implementations. Therefore, the configuration of computer system 300 will vary from implementation to implementation depending upon numerous factors, such as price constraints, performance requirements, technological improvements, and/or other circumstances.

In at least one embodiment, computer system 300 may support the use of specially-protected “trusted” software modules (e.g., tamper-resistant software, or systems having the ability to run protected programs) stored in main memory 304 and/or mass storage device 308 and being executed by processor 310 to perform specific activities, even in the presence of other hostile software in the system. Some of these trusted software modules require equivalently “trustable” protected access not just to other platforms, but to one or more peripheral devices within the same platform, such as graphics controller 314. In general, such access requires that the trusted software module be able to identify the device's capabilities and/or specific identity, and then establish an encrypted session with the device to permit the exchange of data that cannot be snooped or spoofed by other software in the system.

One prior art method of both identifying the device and simultaneously establishing the encrypted session is to use a one-side authenticated Diffie-Hellman (DH) key exchange process. In this process, the device is assigned a unique public/private RSA or ECC key pair. The device holds and protects the private key, while the public key, along with authenticating certificates, may be released to the software module. During the DH key exchange process, the device signs a message using its private key, which the software module can verify using the corresponding public key. This permits the software module to authenticate that the message did in fact come from the device of interest.

However, because this authentication process uses RSA or ECC keys, the device has a unique and provable identity. Any software module that can get the device to sign a message with its private key can prove that this specific unique device is present in the computer system. Given that devices rarely migrate between processing systems, this also represents a provable unique computer system identity. Furthermore, the device's public key itself represents a constant unique value; effectively a permanent “cookie.” In some cases, these characteristics may be construed as a significant privacy problem.

One alternative approach is described in the co-pending patent application Ser. No. 10/999,576, filed Nov. 30, 2004, entitled “Apparatus and Method for Establishing A Secure Session with a Device Without Exposing Privacy-Sensitive Information,” assigned to the owner of the present application. In that approach, the use of RSA or ECC key in the one-sided authenticated Diffie-Hellman process is replaced with Direct Proof keys. A device using this approach may be authenticated as belonging to a specific Family of devices, which may include assurances about the behavior or trustworthiness of the device. The approach does not expose any uniquely identifying information that could be used to establish a unique identity representing the processing system.

Although this approach works well, it requires additional storage in the device to hold the Direct Proof private key, which may be larger than a RSA or ECC key. To alleviate the burdens of this additional storage requirement, embodiments of the present invention define a system and process for ensuring that the device has the Direct Proof private key when it needs the key, without requiring substantial additional storage in the device.

In at least one embodiment of the present invention, a device manufacturer only stores a 128-bit pseudorandom number into a device in the manufacturing line, with a much larger Direct Proof private key (DPpri) may be encrypted and delivered using a distribution CD. Other embodiments may store a number into the device that is longer or shorter than 128 bits. This process ensures that only a specified device can decrypt and use its assigned DPpri key. FIG. 5 is a diagram of a system 500 for distributing Direct Proof keys according to an embodiment of the present invention. There are three entities in this system, a device manufacturing protected system 502, a device manufacturing production system 503, and a client computer system 504. The device manufacturing protected system comprises a processing system used in the set-up process prior to manufacturing of a device 506. The protected system 502 may be operated by a device manufacturer such that the protected system is protected from attack from hackers outside the device manufacturing site (e.g., it is a closed system). Manufacturing production system 503 may be used in the manufacturing of the devices. In one embodiment, the protected system and the production system may be the same system. Device 506 comprises any hardware device for inclusion in the client computer system (e.g., a memory controller, a peripheral device such as a graphics controller, an I/O device, etc.). In embodiments of the present invention, the device comprises a pseudorandom value RAND 508, stored in non-volatile storage of the device.

The manufacturing protected system includes a protected database 510 and a generation function 512. The protected database comprises a data structure for storing multiple pseudorandom values (at least as many as one per device to be manufactured) generated by generation function 512 in a manner as described below. The generation function comprises logic (either implemented in software or hardware) to generate a data structure called a keyblob 514 herein. Keyblob 514 comprises at least three data items. A unique Direct Proof private key (DPpri) comprises a cryptographic key which may be used by a device for signing. DP private digest 518 (DPpri Digest) comprises a message digest of DPpri 516 according to any well-known method of generating a secure message digest, such as SHA-1. Some embodiments may include a pseudorandom initialization vector (IV) 515 comprising a bit stream as part of the keyblob for compatibility purposes. If a stream cipher is used for the encryption, then the IV is used in a well known method for using an IV in a stream cipher. If a block cipher is used for the encryption, then the IV will be used as part of the message to be encrypted, thus making each instance of the encryption be different.

In embodiments of the present invention, the manufacturing protected system generates one or more keyblobs (as described in detail below) and stores the keyblobs in a keyblob database 520 on a CD 522. In one embodiment, there may be many keyblobs on a single CD, the only limitation being the physical storage limits of the CD. The CD is then distributed through typical physical channels to computer system manufacturers, computer distributors, consumers, and others. Although a CD is described herein as the storage medium, any suitable removable storage medium may be used (e.g., a digital versatile disk (DVD), or other medium).

A client computer system 504 desiring to use a Direct Proof protocol for authentication and key exchange of a communications session with device 506 included within system 504 may read a selected keyblob 514 out of the keyblob database 520 on the CD, once the CD is inserted into a CDROM drive (not shown) of the client computer system. The keyblob data may be used by the device to generate a localized keyblob 524 (as described below) for use in implementing the Direct Proof protocol. Device driver software 526 is executed by the client computer system to initialize and control device 506.

In embodiments of the present invention, there may be four distinct stages of operation. FIG. 6 is a flow diagram 600 illustrating stages of a method of distributing Direct Proof keys according to an embodiment of the present invention. According to embodiments of the present invention, certain actions may be performed at each stage. At a site of a device manufacturer, there are at least two stages: set-up stage 602 and the manufacturing production stage 604. The set-up stage is described herein with reference to FIG. 7. The manufacturing production stage is described herein with reference to FIG. 8. At a consumer site having the client computer system, there are at least two stages: set-up stage 606, and use stage 608. The client computer system set-up stage is described herein with reference to FIG. 9. The client computer system use stage is described herein with reference to FIG. 10.

FIG. 7 is a flow diagram 700 illustrating device manufacturing set-up processing according to an embodiment of the present invention. In one embodiment, a device manufacturer may perform these actions using a manufacturing protected system 502. At block 702, the device manufacturer generates a Direct Proof Family key pair (Fpub and Fpri) for each class of devices to be manufactured. Each unique device will have a DPpri key such that a signature created using DPpri may be verified by Fpub. A class of devices may comprise any set or subset of devices, such as a selected product line (i.e., type of device) or subsets of a product line based on version number, or other characteristics of the devices. The Family key pair is for use by the class of devices for which it was generated.

For each device to be manufactured, generation function 512 of manufacturing protected system 502 performs blocks 704 to 720. First, at block 704, the generation function generates a unique pseudo-random value (RAND) 508. In one embodiment, the length of RAND is 128 bits. In other embodiments, other sizes of values may be used. In one embodiment, the pseudo-random values for a number of devices may be generated in advance. At block 706, using a one-way function, f, supported by the device, the generation function generates a symmetric encryption key SKEY from the unique RAND value (SKEY=f(RAND)). The one-way function may be any known algorithm appropriate for this purpose (e.g., SHA-1, MGF1, Data Encryption Standard (DES), Triple DES, etc.). At block 708, in one embodiment, the generation function generates an identifier (ID) label that will be used to reference this device's keyblob 514 on the distribution CD 522, by using SKEY to encrypt a “null entry” (e.g., a small number of zero bytes) (Device ID=Encrypt (0..0) using SKEY. In other embodiments, other ways of generating the Device ID may be used or other values may be encrypted by SKEY.

Next, at block 710, the generation function generates the DP private signing key DPpri correlating to the device's Family public key (Fpub). At block 712, the generation function hashes DPpri to produce DPpri Digest using known methods (e.g., using SHA-1 or another hash algorithm). At block 714, the generation function builds a keyblob data structure for the device. The keyblob includes at least DPpri and DPpri Digest. In one embodiment, the keyblob also includes a random initialization vector having a plurality of pseudo-randomly generated bits. These values may be encrypted using SKEY to produce an encrypted keyblob 514. At block 716, the Device ID generated at block 708 and the encrypted keyblob 514 generated at block 714 may be stored in an entry in a keyblob database 520 to be released on the distribution CD 522. In one embodiment, the entry in the keyblob database may be indicated by the Device ID. At block 718, the current RAND value may be stored in protected database 510. At block 720, SKEY and DPpri may be deleted, since they will be regenerated by the device in the field. The creation of the DPpri Digest and the subsequent encryption by SKEY are designed so that the contents of DPpri cannot be determined by any entity that does not have possession of SKEY and so that the contents of the KeyBlob cannot be modified by an entity that does not have possession of SKEY without subsequent detection by an entity that does have possession of SKEY. In other embodiments, other methods for providing this secrecy and integrity protection could be used. In some embodiments, the integrity protection may not be required, and a method that provided only secrecy could be used. In this case, the value of DPpri Digest would not be necessary.

At any time after block 720, at block 722 the protected database of RAND values may be securely uploaded to manufacturing production system 503 that will store the RAND values into the devices during the manufacturing process. Once this upload has been verified, the RAND values could be securely deleted from the manufacturing protected system 502. Finally, at block 724, the keyblob database having a plurality of encrypted keyblobs may be “burned” to a common distribution CD 522. In one embodiment, the CD may be distributed along with each device, with one keyblob database entry to be used for each device, as indexed by the Device ID field. In addition, the CD includes a Key Retrieval utility software module whose use is described in further detail below.

FIG. 8 is a flow diagram 800 illustrating device manufacturing production processing according to an embodiment of the present invention. As devices are being manufacturing in a production line, at block 802 the manufacturing production system selects an unused RAND value from the protected database. The selected RAND value may then be stored into non-volatile storage in a device. In one embodiment, the non-volatile storage comprises a TPM. At block 804, once the storage of the RAND value is successful, the manufacturing production system destroys any record of that device's RAND value in the protected database. At this point, the sole copy of the RAND value is stored in the device.

In an alternative embodiment, the RAND value could be created during the manufacturing of a device, and then sent to the manufacturing protected system for the computation of a keyblob.

In another embodiment, the RAND value could be created on the device, and the device and the manufacturing protected system could engage in a protocol to generate the DPpri key using a method that does not reveal the DPpri key outside of the device. Then the device could create the Device ID, the SKEY, and the keyblob. The device would pass the Device ID and the keyblob to the manufacturing system for storage in protected database 510. In this method, the manufacturing system ends up with the same information (Device ID, keyblob) in the protected database, but does not know the values of RAND or of DPpri.

FIG. 9 is a flow diagram 900 of client computer system set-up processing according to an embodiment of the present invention. A client computer system may perform these actions as part of booting up the system. At block 902, the client computer system may be booted up in the normal manner and a device driver 526 for the device may be loaded into main memory. When the device driver is initialized and begins execution, the device driver determines if there is already an encrypted localized keyblob 524 stored in mass storage device 308 for device 506. If there is, then no further set-up processing need be performed and set-up processing ends at block 906. If not, then processing continues with block 908. At block 908, the device driver causes the display of a message to the user of the client computer system asking for the insertion of the distribution CD 522. Once the CD is read by the computer system, the device driver then launches the Key Retrieval utility software (not shown in FIG. 5) stored on the CD. This utility issues an Acquire Key command to the device 506 to initiate the device's DP private key acquisition process.

In response, at block 910 the device uses its one-way function f to regenerate the symmetric key SKEY (now for use in decryption) from the embedded RAND value 508 (SKEY=f(RAND)). At block 912, the device then generates its unique Device ID label, by using SKEY to encrypt a “null entry” (e.g., a small number of zero bytes) (Device ID=Encrypt (0..0) using SKEY). The device then returns the Device ID to the Key Retrieval utility software. At block 914, the Key Retrieval utility searches the keyblob database 520 on the CD for the database entry containing the matching Device ID, extracts the device's encrypted keyblob, and transfers the keyblob to the device.

In one embodiment, if rogue software tries to send an Acquire Key command to the device after the device has the keyblob, the device does not respond to the rogue software with the Device ID. Instead, the device will return an error indicator. In effect, if the device has access to a localized keyblob, then the functionality of the Acquire Key command is disabled. In this way, the device does not reveal the unique Device ID except when it does not have the keyblob.

At block 916, the device decrypts the encrypted keyblob using the symmetric key SKEY, to yield DPpri and DPpri Digest, and stores these values in its non-volatile storage (Decrypted Keyblob=Decrypt (IV, DPpri, DPpri Digest) using SKEY). The initialization vector (IV) may be discarded. At block 918, the device then checks the integrity of DPpri by hashing DPpri and comparing the result against DPpri Digest. If the comparison is good, the device accepts DPpri as its valid key. The device may also set a Key Acquired flag to true to indicate that the DP private key has been successfully acquired. At block 920, the device chooses a new IV and creates a new encrypted localized keyblob, using the new IV (Localized Keyblob=Encrypt (IV2, DPpri, DPpri Digest) using SKEY). The new encrypted localized keyblob may be returned to the Key Retrieval utility. At block 922, the Key Retrieval utility stores the encrypted, localized keyblob in storage within the client computer system (such as mass storage device 308, for example). The device's DPpri is now securely stored in the client computer system.

Once the device has acquired DPpri during set-up processing, the device may then use DPpri. FIG. 10 is a flow diagram of client computer system processing according to an embodiment of the present invention. The client computer system may perform these actions anytime after set-up has been completed. At block 1002, the client computer system may be booted up in the normal manner and a device driver 526 for the device may be loaded into main memory. When the device driver is initialized and begins execution, the device driver determines if there is already an encrypted localized keyblob 524 stored in mass storage device 308 for device 506. If there is not, then the set-up processing of FIG. 9 is performed. If there is an encrypted localized keyblob available for this device, then processing continues with block 1006. At block 1006, the device driver retrieves the encrypted localized keyblob and transfers the keyblob to the device. In one embodiment, the transfer of the keyblob may be accomplished by executing a Load Keyblob command.

At block 1008 the device uses its one-way function f to regenerate the symmetric key SKEY (now for use in decryption) from the embedded RAND value 508 (SKEY=f(RAND)). At block 1010, the device decrypts the encrypted localized keyblob using the symmetric key SKEY, to yield DPpri and DPpri Digest, and stores these values in its non-volatile storage (Decrypted Keyblob=Decrypt (IV2, DPpri, DPpri Digest) using SKEY). The second initialization vector (IV2) may be discarded. At block 1012, the device checks the integrity of DPpri by hashing DPpri and comparing the result against DPpri Digest. If the comparison is good (e.g., the digests match), the device accepts DPpri as the valid key acquired earlier, and enables it for use. The device may also set a Key Acquired flag to true to indicate that the DP private key has been successfully acquired. At block 1014, the device chooses yet another IV and creates a new encrypted localized keyblob, using the new IV (Localized Keyblob=Encrypt (IV3, DPpri, DPpri Digest) using SKEY). The new encrypted localized keyblob may be returned to the Key Retrieval utility. At block 1016, the Key Retrieval utility stores the encrypted, localized keyblob in storage within the client computer system (such as mass storage device 308, for example). The device's DPpri is now securely stored once again in the client computer system.

In one embodiment of the present invention, it is not necessary to generate all of the device DP private keys at one time. Assuming that the distribution CD is updated regularly, the device DP private keys could be generated in batches as needed. Each time the distribution CD was “burned,” it would contain the keyblob database as generated to date, including those device keys that had been generated but not yet assigned to devices.

Although the operations discussed herein may be described as a sequential process, some of the operations may in fact be performed in parallel or concurrently. In addition, in some embodiments the order of the operations may be rearranged without departing from the spirit of the invention.

The techniques described herein are not limited to any particular hardware or software configuration; they may find applicability in any computing or processing environment. The techniques may be implemented in hardware, software, or a combination of the two. The techniques may be implemented in programs executing on programmable machines such as mobile or stationary computers, personal digital assistants, set top boxes, cellular telephones and pagers, and other electronic devices, that each include a processor, a storage medium readable by the processor (including volatile and non-volatile memory and/or storage elements), at least one input device, and one or more output devices. Program code is applied to the data entered using the input device to perform the functions described and to generate output information. The output information may be applied to one or more output devices. One of ordinary skill in the art may appreciate that the invention can be practiced with various computer system configurations, including multiprocessor systems, minicomputers, mainframe computers, and the like. The invention can also be practiced in distributed computing environments where tasks may be performed by remote processing devices that are linked through a communications network.

Each program may be implemented in a high level procedural or object oriented programming language to communicate with a processing system. However, programs may be implemented in assembly or machine language, if desired. In any case, the language may be compiled or interpreted.

Program instructions may be used to cause a general-purpose or special-purpose processing system that is programmed with the instructions to perform the operations described herein. Alternatively, the operations may be-performed by specific hardware components that contain hardwired logic for performing the operations, or by any combination of programmed computer components and custom hardware components. The methods described herein may be provided as a computer program product that may include a machine readable medium having stored thereon instructions that may be used to program a processing system or other electronic device to perform the methods. The term “machine readable medium” used herein shall include any medium that is capable of storing or encoding a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methods described herein. The term “machine readable medium” shall accordingly include, but not be limited to, solid-state memories and optical and magnetic disks. Furthermore, it is common in the art to speak of software, in one form or another (e.g., program, procedure, process, application, module, logic, and so on) as taking an action or causing a result. Such expressions are merely a shorthand way of stating the execution of the software by a processing system cause the processor to perform an action of produce a result.

While this invention has been described with reference to illustrative embodiments, this description is not intended to be construed in a limiting sense. Various modifications of the illustrative embodiments, as well as other embodiments of the invention, which are apparent to persons skilled in the art to which the invention pertains are deemed to lie within the spirit and scope of the invention.

Claims (37)

1. A method comprising:

generating encrypted data structures, each for a different device in a class of devices that comprise different private keys based on a Direct Proof family key pair for the class of devices, wherein a family public key of the Direct Proof family key pair can be used to verify a signature created by a private key corresponding to at least one of the devices without determining which specific device created the signature;

generating identifiers for the encrypted data structures, based on values for the devices;

storing the identifiers and the encrypted data structures on a removable storage medium; and

storing a different one of the values into non-volatile storage in each of the devices, one of the values to be used to obtain one of the encrypted data structures from the removable storage medium.

2. The method of claim 1, further comprising distributing the removable storage medium and one of the devices.

3. The method of claim 1, wherein:

the private keys comprise Direct Proof private signing keys based on a family private key of the Direct Proof family key pair; and

further comprising hashing the Direct Proof private signing keys to generate private key digests and including the private key digests in the encrypted data structures.

4. The method of claim 1, further comprising generating a symmetric key based on the value for one of the devices.

5. The method of claim 4, wherein generating one of the identifiers comprises encrypting a data value using the symmetric key.

6. The method of claim 4, further comprising encrypting one of the data structures using the symmetric key.

7. The method of claim 1, wherein one of the encrypted data structures further comprises a substantially random initialization vector.

9. The method of claim 1, wherein one of the values for one of the devices is a unique pseudo-random value.

10. An article comprising a first storage medium having a plurality of machine readable instructions, wherein when the instructions are executed by a processor, the instructions provide for:

generating encrypted data structures, each for a different device in a class of devices, that comprise different private keys based on a Direct Proof family key pair for the class of devices, wherein a family public key of the Direct Proof family key pair can be used to verify a signature created by a private key corresponding to at least one device in the class of devices without determining which specific device created the signatures signature;

generating identifiers for the encrypted data structures, based on pseudo-random values for the devices; and

storing the identifiers and the encrypted data structures on a second removable storage medium;

wherein when one of the pseudo-random values is stored into non-volatile storage in one of the devices, the stored pseudo-random value can be used to obtain one of the encrypted data structures from the second removable storage medium.

11. The article of claim 10, wherein:

the private keys comprise Direct Proof private signing keys based at least in part on a family private key of the Direct Proof family key pair; and

further comprising instructions for hashing the Direct Proof private signing keys to generate private key digests and including the private key digests in the encrypted data structures.

12. The article of claim 10, further comprising instructions for generating a symmetric key based on the pseudo-random value for one of the devices.

13. The article of claim 12, wherein instructions for generating one of the identifiers comprise instructions for encrypting a data value using the symmetric key.

14. The article of claim 12, further comprising instructions for encrypting one of the data structures using the symmetric key.

15. The article of claim 10, wherein one of the encrypted data structures further comprises a substantially random initialization vector.

16. The article of claim 10, wherein one of the pseudo-random values for one of the devices is unique.

17. A method comprising:

providing a removable storage medium that includes (a) encrypted data structures, associated with devices of a class, that comprise different private keys based on a Direct Proof family key pair for the class, and (b) identifiers, based on values for the multiple devices, for the encrypted data structures;

determining whether a first encrypted data structure, associated with a first device installed in a computer system, is stored in a memory on the computer system; and

obtaining the first encrypted data structure from the removable storage medium based on a first identifier, included in the identifiers, that is associated with the first device and a first value, included in the values, stored in non-volatile storage included in the first device;

wherein a family public key of the key pair can be used to verify a signature created by a private key corresponding to one of the devices without determining which specific device created the signature.

18. The method of claim 17, wherein the removable storage medium comprises a CD created by a manufacturer of the device.

19. The method of claim 17, wherein obtaining the first encrypted data structure comprises issuing an acquire key command to the first device to initiate a private key acquisition process.

20. The method of claim 17, wherein a first private key, included in the private keys, comprises a Direct Proof private signing key based at least in part on a family private key of the Direct Proof family key pair.

21. The method of claim 19, wherein the private key acquisition process comprises generating a symmetric key based on a unique pseudo-random value, included in the values, stored in the first device.

22. The method of claim 21, wherein the private key acquisition process comprises generating a device identifier, based on the pseudo-random value, for the first encrypted data structure.

23. The method of claim 22, wherein the private key acquisition process further comprises searching the removable storage medium for the first identifier matching the generated device identifier and transferring the first encrypted data structure to the first device.

24. The method of claim 23, wherein the private key acquisition process further comprises decrypting the first encrypted data structure received from the removable storage medium using the symmetric key to obtain a first private key, included in the private keys, and a first private key digest.

25. The method of claim 24, wherein the private key acquisition process further comprises hashing the first private key to generate a new private key digest, comparing the first private key digest from the decrypted data structure with the new private key digest, and accepting the first private key as valid for the first device when the first and new digests match.

26. An article comprising:

a first storage medium having a plurality of machine readable instructions, wherein when the instructions are executed by a processor, the instructions provide for obtaining a first private key for a first device installed in a computer system by:

providing a removable storage medium that includes (a) encrypted data structures, associated with devices of a class, which includes the first device, that comprise different private keys based on a Direct Proof family key pair for the class, and (b) identifiers, based on values for the multiple devices, for the encrypted data structures;

determining whether a first encrypted data structure, associated with the first device, is stored in a memory on the computer system; and

obtaining the first encrypted data structure from the removable storage medium based on a first identifier, included in the identifiers, that is associated with the first device and a first value, included in the values, stored in non-volatile storage included in the first device;

wherein a family public key, of the key pair, can be used to verify a signature created by a private key corresponding to one of the devices without determining which specific device created the signature.

27. The article of claim 26, wherein instructions for obtaining the encrypted data structure comprise instructions for issuing an acquire key command to the first device to initiate a private key acquisition process.

28. The article of claim 26, wherein a first private key comprises a Direct Proof private signing key based at least in part on a family private key of the Direct Proof family key pair.

29. The article of claim 27, wherein the private key acquisition process comprises instructions for generating a symmetric key based on a unique pseudo-random value, included in the values, stored in the first device.

30. The article of claim 29, wherein the private key acquisition process comprises instructions for generating a device identifier, based on the pseudo-random value, for the first encrypted data structure.

31. The article of claim 30, wherein the private key acquisition process further comprises instructions for searching the removable storage medium for the first identifier matching the generated device identifier and transferring the first encrypted data structure to the first device.

32. The article of claim 31, wherein the private key acquisition process further comprises instructions for decrypting the first encrypted data structure received from the removable storage medium using the symmetric key to obtain a first private key and a first private key digest.

33. The article of claim 32, wherein the private key acquisition process further comprises instructions for hashing the first private key to generate a new private key digest, comparing the first private key digest with the new private key digest, and accepting the first private key as valid for the first device when the first and new digests match.

34. A method comprising:

providing a removable storage medium that includes (a) encrypted data structures, associated with devices of a class, that comprise different private keys based on a Direct Proof family key pair for the class, and (b) identifiers, based on values for the devices, for the encrypted data structures; wherein a family public key of the key pair can be used to verify a signature created by a private key corresponding to one of the devices without determining which specific device created the signature;

obtaining a first encrypted data structure from the removable storage medium based on a first identifier, included in the identifiers and associated with a first device that is included in the devices, and a first value that is included in the values and stored in non-volatile storage of the first device;

retrieving the first encrypted data structure from a memory on a computer system, wherein the first encrypted data structure comprises a first private key digest and a first private key for the first device and, the first device does not include the private key or the private key digest;

generating a symmetric key based on the first value, which includes a substantially unique pseudo-random value;

decrypting the first encrypted data structure using the symmetric key to obtain the first private key and the first private key digest;

hashing the first private key to generate a new private key digest, and comparing the first private key digest with the new private key digest; and

accepting the first private key as valid for the device when the first and new digests match.

35. The method of claim 34, wherein the first private key comprises a Direct Proof private signing key based at least in part on a family private key of the Direct Proof family key pair.

36. The method of claim 34, wherein the first device comprises a peripheral device of the computer system.

37. The method of claim 34, further comprising:

generating a first random initialization vector;

generating a new encrypted data structure by encrypting the first private key, the first private key digest, and the first random initialization vector using the symmetric key; and

storing the new encrypted data structure in the memory of the computer system.

The Patent Office of the State Intellectual Office of the People's Republic of China, First Office Action dated Apr. 3, 2009, in a related application.

The Patent Office of the State Intellectual Property Office of the People's Republic of China, First Office Action dated Dec. 11, 2009 in Chinese patent application No. 200580023787.2.

U.S. Patent and Trademark Office Final Official Action in related U.S. Appl. No. 10/892,256 dated Apr. 1, 2008, with corresponding Reply to Final Official Action filed May 30, 2008, Advisory Action mailed on Jun. 16, 2008 with Request for Continued Examination (RCE) filed on Jun. 30, 2008.

U.S. Patent and Trademark Office Final Official Action in related U.S. Appl. No. 10/892,280 dated May 14, 2008, with corresponding Reply to Final Official Action filed Jul. 9, 2008.