US20100150351A1 - Method of Delivering Direct Proof Private Keys to Devices Using an On-Line Service - Google Patents
Method of Delivering Direct Proof Private Keys to Devices Using an On-Line Service Download PDFInfo
- Publication number
- US20100150351A1 US20100150351A1 US12/710,439 US71043910A US2010150351A1 US 20100150351 A1 US20100150351 A1 US 20100150351A1 US 71043910 A US71043910 A US 71043910A US 2010150351 A1 US2010150351 A1 US 2010150351A1
- Authority
- US
- United States
- Prior art keywords
- key
- private key
- encrypted data
- data structure
- private
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
- 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
- H04L9/0844—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 with user authentication or key authentication, e.g. ElGamal, MTI, MQV-Menezes-Qu-Vanstone protocol or Diffie-Hellman protocols using implicitly-certified keys
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/08—Key distribution or management, e.g. generation, sharing or updating, of cryptographic keys or passwords
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/30—Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2209/00—Additional information or applications relating to cryptographic mechanisms or cryptographic arrangements for secret or secure communication H04L9/00
- H04L2209/12—Details relating to cryptographic hardware or logic circuitry
- H04L2209/127—Trusted platform modules [TPM]
Definitions
- the present invention relates generally to computer security and, more specifically, to securely distributing cryptographic keys to devices in processing systems.
- 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.
- DH Diffie-Hellman
- 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.
- RSA Rivest, Shamir and Adelman
- ECC Elliptic Curve Cryptography
- 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.
- OEMs original equipment manufacturers
- 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
- TPM Trusted Platform Module
- 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 to devices using an on-line service according to an embodiment of the present invention
- FIG. 6 is a flow diagram illustrating stages of a method of distributing Direct Proof keys using an on-line service according to an embodiment of the present invention
- FIG. 7 is a flow diagram illustrating protected server set-up processing according to an embodiment of the present invention.
- FIG. 8 is a flow diagram illustrating device manufacturer set-up processing according to an embodiment of the present invention.
- FIG. 9 is a flow diagram illustrating device manufacturer production processing according to an embodiment of the present invention.
- FIGS. 10-12 are flow diagrams of client computer system set-up processing according to an embodiment of the present invention.
- FIG. 13 is a flow diagram of client computer system processing according to an embodiment of the present invention.
- 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.
- 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 (DP) private key (e.g., used for signing) to be delivered in a secure manner to the device using an on-line service, 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.
- the reduction in device storage required to support this capability may be from approximately 300 to 700 bytes down to approximately 40 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.
- DP private signing keys are not distributed in or with a device. Instead, the device supports a protocol by which the device in the field may safely retrieve its private key from an on-line protected server provided by a manufacturer or vendor, or a delegate. This protocol creates a trusted channel between the device and the server, and does not require trust in any intervening software, including software on a local processing system.
- 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.
- 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.
- some cryptographic information e.g., digital signature, a secret such as a key, etc.
- 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.
- Direct proof refers to zero-knowledge proofs, as these types of proofs are commonly known in the field.
- 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.
- 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.
- 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.
- TPM Trusted Platform Module
- 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.
- device manufacturer(s) 110 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
- second platform 104 comprises a Trusted Platform Module (TPM) 115 .
- TPM 115 is a cryptographic device that is manufactured by device manufacturer(s) 110 .
- 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 .
- second platform 104 comprises a processor 202 coupled to TPM 115 .
- processor 202 is a device that processes information.
- processor 202 may be implemented as a microprocessor, digital signal processor, micro-controller or even a state machine.
- 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).
- FPGAs Field Programmable Gate Arrays
- TTL transistor-transistor logic
- ASIC Application Specific Integrated Circuit
- 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 .
- 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 .
- 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.
- 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.
- a display such as a cathode ray tube (CRT), Liquid Crystal Display (LCD) or any flat panel display, for displaying information to an end user.
- CTR cathode ray tube
- LCD Liquid Crystal Display
- an alphanumeric input device 316 may be coupled to bus 302 for communicating information and/or command selections to processor 310 .
- cursor control unit 318 is Another type of user input device, 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.
- 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.
- the computer system may be coupled on-line over a network to a protected server.
- 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.
- 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.
- trusted software modules e.g., tamper-resistant software, or systems having the ability to run protected programs
- 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.
- DH Diffie-Hellman
- 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.
- 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.
- 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.
- 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.
- a device manufacturer stores a 128-bit pseudorandom number into a device in the manufacturing line, and a much larger Direct Proof private key (DPpri) may be encrypted and delivered to the device in the field using an on-line service operated by a protected server.
- 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 four entities in this system, a device manufacturing protected system 502 , a device manufacturing production system 503 , a client computer system 504 , and a protected server 522 .
- the device manufacturing protected system comprises a processing system used in the set-up process prior to manufacturing of a device 506 .
- the manufacturing 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.
- 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.).
- the device comprises a pseudorandom value RAND 508 , and a key service public key hash value 509 , 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.
- the manufacturing protected system also includes a key service public key 507 used for an on-line protocol as described in further detail below.
- 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 protected server 522 .
- the protected server may be operated by the device manufacturer, device distributor, or other affiliated entity.
- the protected server may be communicatively coupled to a client computer system 504 using a network, such as the Internet for example.
- the protected server also includes a key service private key 511 for use in the on-line protocol between the protected server and the device.
- 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 protected server using a key service public/private key pair and the on-line protocol described in further detail below.
- 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 .
- 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.
- a site of a device manufacturer there are at least three stages: protected server set-up stage 601 , device manufacturer set-up stage 602 , and device manufacturer production stage 604 .
- the protected server set-up stage is described herein with reference to FIG. 7 .
- the device manufacturer set-up stage is described herein with reference to FIG. 8 .
- the device manufacturer production stage is described herein with reference to FIG. 9 .
- client computer system set-up stage 606 there are at least two stages: client computer system set-up stage 606 , and client computer system use stage 608 .
- client computer system set-up stage is described herein with reference to FIGS. 10-12 .
- client computer system use stage is described herein with reference to FIG. 13 .
- FIG. 7 is a flow diagram 700 illustrating protected server set-up stage processing according to an embodiment of the present invention. This processing may be performed by a device manufacturer prior to production of devices.
- a device manufacturer establishes a protected server 522 to support key retrieval requests.
- the protected server is communicatively coupled to the Internet in a well-known manner. For improved security, the protected server should not be the same processing system used in the manufacturing protected system or the manufacturing production system.
- the device manufacturer generates a key service public/private key pair that will be used for the key retrieval service provided by the protected server.
- the key service public/private key pair may be stored in the protected server. This key pair may be generated once for all processing performed by the system, or a new key pair may be generated for each class of devices.
- the device manufacturer delivers the key service public key 507 to the manufacturing protected system 502 .
- FIG. 8 is a flow diagram 800 illustrating device manufacturing set-up processing according to an embodiment of the present invention.
- a device manufacturer may perform these actions using a manufacturing protected system 502 .
- 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.
- generation function 512 of manufacturing protected system 502 performs blocks 804 to 820 .
- the generation function generates a unique pseudo-random value (RAND) 508 .
- RAND pseudo-random value
- the length of RAND is 128 bits. In other embodiments, other sizes of values may be used.
- the pseudo-random values for a number of devices may be generated in advance.
- the one-way function may be any known algorithm appropriate for this purpose (e.g., SHA-1, MGF1, Data Encryption Standard (DES), Triple DES, Advanced Encryption Standard (AES), etc.).
- ID identifier
- the generation function generates the DP private signing key DPpri correlating to the device's Family public key (Fpub).
- the generation function hashes DPpri to produce DPpri Digest using known methods (e.g., using SHA-1 or another hash algorithm).
- the generation function builds a keyblob data structure for the device.
- the keyblob includes at least DPpri and DPpri Digest.
- 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 .
- the Device ID generated at block 808 and the encrypted keyblob 514 generated at block 814 may be stored in an entry in a keyblob database 520 .
- the entry in the keyblob database may be indicated by the Device ID.
- the current RAND value may be stored in protected database 510 .
- 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.
- other methods for providing this secrecy and integrity protection could be used.
- 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.
- 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 .
- the keyblob database 520 having a plurality of encrypted keyblobs may be stored on the protected server 522 , with one keyblob database entry to be used for each device, as indexed by the Device ID field.
- FIG. 9 is a flow diagram 900 illustrating device manufacturing production processing according to an embodiment of the present invention.
- 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.
- the non-volatile storage comprises a TPM.
- the RAND value may be stored in approximately 16 bytes of non-volatile storage.
- a hash 509 of the key service public key 507 may be stored in the non-volatile storage of the device.
- the hash may be generated using any known hashing algorithm.
- the hash value may be stored in approximately 20 bytes of non-volatile storage.
- the manufacturing production system destroys any record of that device's RAND value in the protected database 510 . At this point, the sole copy of the RAND value is stored in the device.
- 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.
- 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.
- FIGS. 10-12 are flow diagrams 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.
- the client computer system may be booted up in the normal manner and a device driver software module 526 for the device may be loaded into main memory of the client computer system.
- the device driver determines at block 1004 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 1006 . If not, then processing continues with block 1008 .
- the device driver issues an Acquire Key command to the device 506 to initiate the device's DP private key acquisition process.
- the device driver sends the key service public key 507 to the device.
- the device extracts the received key service public key, generates a hash value of the key service public key, and compares the hash of the received key service public key to the key service public key hash 509 stored in non-volatile storage on the device. If the hashes match, the received key service public key is known to be that of the device manufacturer's key retrieval service, and client computer system set-up processing continues.
- the device could receive a certificate of a certified key service public key for which the certificate could be verified through a certificate chain to the key service public key whose hash is the key service public key hash 509 stored in non-volatile storage on the device. Then the certified key service public key could be used as the key service public key in the subsequent steps.
- the device generates a transient symmetric key Tkey. This key will be sent to the protected server, which may use the key to encrypt the message the protected server returns to the device.
- the device builds a retrieve key request message containing the Device ID and the transient symmetric key Tkey, encrypts the message using the key service public key received from the device driver at block 1014 , and sends the retrieve key request message to the protected server via the device driver.
- Retrieve Key Request Encrypt (Device ID, Tkey) with the key service public key).
- the protected server decrypts the received key request message using the key service private key 511 , and extracts the fields stored therein. Since the protected server now knows the Device ID (obtained from the key request message), the protected server searches the keyblob database for the record containing the matching Device ID value, and extracts the device's encrypted keyblob from the record.
- Skey session key
- the protected server builds a second response message containing the Family public key and the encrypted keyblob and encrypts the second response message using the transient symmetric key Tkey supplied by the device.
- Key Response (Family public key, Encryption of (Encrypted Keyblob) using Tkey). Encrypting the Encrypted keyblob with Tkey is not to protect the keyblob, since it is already encrypted with a symmetric key SKEY, which only the device can regenerate.
- the second response message may be returned to the device driver on the client computer system at block 1112 , which forwards the message to the device.
- the device extracts the Family public key from the second response message, decrypts the wrapped keyblob using the transient symmetric key Tkey, and stores the encrypted keyblob in volatile memory of the device. Processing then continues with flow diagram 1200 of FIG. 12 .
- the initialization vector (IV) may be discarded.
- 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 in one embodiment also set a Key Acquired flag to true to indicate that the DP private key has been successfully acquired.
- the new encrypted localized keyblob may be returned to a Key Retrieval utility software module (not shown in FIG. 5 ) on the client computer system.
- 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.
- FIG. 13 is a flow diagram 1300 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.
- 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.
- 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 FIGS. 10-12 is performed. If there is an encrypted localized keyblob available for this device, then processing continues with block 1306 .
- 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.
- 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 (IV 2 , DPpri, DPpri Digest) using SKEY).
- the second initialization vector (IV 2 ) may be discarded.
- the device checks the integrity of DPpri by hashing DPpri and comparing the result against DPpri Digest.
- 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.
- the new encrypted localized keyblob may be returned to the Key Retrieval utility.
- 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.
- the device DP private keys it is not necessary to generate all of the device DP private keys at one time. Assuming that the keyblob database on the protected server is updated regularly, the device DP private keys could be generated in batches as needed. Each time the keyblob database is updated on the protected server, it would contain the keyblob database as generated to date, including those device keys that had been generated but not yet assigned to devices.
- the protected sever may generate a request to the manufacturing protected system, which still holds the device's RAND value. At this time, the manufacturing protected system generates the DPpri key for the device, returns it to the protected server, and only then destroys the RAND value.
- the device manufacturer may choose to store the hash of a root key, and then sign certificates for key service public keys with the root key. In this way, the same root key could be used for a very large number of devices.
- 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.
- 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.
- 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.
- machine readable medium shall accordingly include, but not be limited to, solid-state memories, optical and magnetic disks, and a carrier wave that encodes a data signal.
- 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.
Abstract
Description
- This application is a continuation of U.S. patent application Ser. No. 10/892,256, filed on Jul. 14, 2004.
- 1. Field
- The present invention relates generally to computer security and, more specifically, to securely distributing cryptographic keys to devices in processing systems.
- 2. 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.
- 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 ofFIG. 1 . -
FIG. 3 illustrates a second embodiment of the platform including the TPM ofFIG. 1 . -
FIG. 4 illustrates an exemplary embodiment of a computer system implemented with the TPM ofFIG. 2 . -
FIG. 5 is a diagram of a system for distributing Direct Proof keys to devices using an on-line service according to an embodiment of the present invention; -
FIG. 6 is a flow diagram illustrating stages of a method of distributing Direct Proof keys using an on-line service according to an embodiment of the present invention; -
FIG. 7 is a flow diagram illustrating protected server set-up processing according to an embodiment of the present invention; -
FIG. 8 is a flow diagram illustrating device manufacturer set-up processing according to an embodiment of the present invention; -
FIG. 9 is a flow diagram illustrating device manufacturer production processing according to an embodiment of the present invention; -
FIGS. 10-12 are flow diagrams of client computer system set-up processing according to an embodiment of the present invention; and -
FIG. 13 is a flow diagram of client computer system processing according to an embodiment of the present invention. - 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 (DP) private key (e.g., used for signing) to be delivered in a secure manner to the device using an on-line service, 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 40 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.
- In embodiments of the present invention, DP private signing keys are not distributed in or with a device. Instead, the device supports a protocol by which the device in the field may safely retrieve its private key from an on-line protected server provided by a manufacturer or vendor, or a delegate. This protocol creates a trusted channel between the device and the server, and does not require trust in any intervening software, including software on a local processing system.
- 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 arequest 106 that a second platform 104 (Responder) provides information about itself. In response torequest 106,second platform 104 provides the requestedinformation 108. - Additionally, for heightened security,
first platform 102 may need to verify that requestedinformation 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 challengessecond 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 convincefirst platform 102 thatsecond 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 tofirst 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 ofsecond platform 104 withTPM 115. For this embodiment of the invention,second platform 104 comprises aprocessor 202 coupled toTPM 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 astorage 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 ofTPM 115 in lieu ofstorage unit 206 as shown inFIG. 3 . The cryptographic information may be encrypted, especially if stored outsideTPM 115. -
FIG. 4 illustrates an embodiment of a platform including acomputer system 300 implemented withTPM 115 ofFIG. 2 .Computer system 300 comprises a bus 302 and aprocessor 310 coupled to bus 302.Computer system 300 further comprises amain memory unit 304 and astatic memory unit 306. - Herein,
main memory unit 304 is volatile semiconductor memory for storing information and instructions executed byprocessor 310.Main memory 304 also may be used for storing temporary variables or other intermediate information during execution of instructions byprocessor 310.Static memory unit 306 is non-volatile semiconductor memory for storing information and instructions forprocessor 310 on a more permanent nature. Examples ofstatic memory 306 include, but are not limited or restricted to read only memory (ROM). Bothmain memory unit 304 andstatic memory unit 306 are coupled to bus 302. - In one embodiment of the invention,
computer system 300 further comprises adata storage device 308 such as a magnetic disk or optical disc and its corresponding drive may also be coupled tocomputer system 300 for storing information and instructions. -
Computer system 300 can also be coupled via bus 302 to agraphics 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 iscursor control unit 318, such as a mouse, a trackball, touch pad, stylus, or cursor direction keys for communicating direction information and command selections toprocessor 310 and for controlling cursor movement ondisplay 314. - A
communication interface unit 320 is also coupled to bus 302. Examples ofinterface 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. In one embodiment, the computer system may be coupled on-line over a network to a protected server. - 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 inmain memory 304 and/ormass storage device 308 and being executed byprocessor 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 asgraphics 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 co-pending patent application Ser. No. 10/999,576, filed on Nov. 30, 2004, entitled “An Apparatus and Method for Establishing an Authenticated Encrypted 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 keys 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 stores a 128-bit pseudorandom number into a device in the manufacturing line, and a much larger Direct Proof private key (DPpri) may be encrypted and delivered to the device in the field using an on-line service operated by a protected server. 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 asystem 500 for distributing Direct Proof keys according to an embodiment of the present invention. There are four entities in this system, a device manufacturing protectedsystem 502, a devicemanufacturing production system 503, aclient computer system 504, and a protectedserver 522. The device manufacturing protected system comprises a processing system used in the set-up process prior to manufacturing of adevice 506. The manufacturing protectedsystem 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 apseudorandom value RAND 508, and a key service publickey hash value 509, stored in non-volatile storage of the device. - The manufacturing protected system includes a protected
database 510 and ageneration 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 bygeneration 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 akeyblob 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 ofDPpri 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. The manufacturing protected system also includes a key servicepublic key 507 used for an on-line protocol as described in further detail below. - 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 protectedserver 522. In one embodiment, there may be many keyblobs in the keyblob database. The protected server may be operated by the device manufacturer, device distributor, or other affiliated entity. The protected server may be communicatively coupled to aclient computer system 504 using a network, such as the Internet for example. The protected server also includes a key serviceprivate key 511 for use in the on-line protocol between the protected server and the device. - A
client computer system 504 desiring to use a Direct Proof protocol for authentication and key exchange of a communications session withdevice 506 included withinsystem 504 may read a selectedkeyblob 514 out of thekeyblob database 520 on the protected server using a key service public/private key pair and the on-line protocol described in further detail below. 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 andcontrol device 506. - In embodiments of the present invention, there may be five 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 three stages: protected server set-upstage 601, device manufacturer set-upstage 602, and devicemanufacturer production stage 604. The protected server set-up stage is described herein with reference toFIG. 7 . The device manufacturer set-up stage is described herein with reference toFIG. 8 . The device manufacturer production stage is described herein with reference toFIG. 9 . At a consumer site having the client computer system, there are at least two stages: client computer system set-up stage 606, and client computer system use stage 608. The client computer system set-up stage is described herein with reference toFIGS. 10-12 . The client computer system use stage is described herein with reference toFIG. 13 . -
FIG. 7 is a flow diagram 700 illustrating protected server set-up stage processing according to an embodiment of the present invention. This processing may be performed by a device manufacturer prior to production of devices. Atblock 702, a device manufacturer establishes a protectedserver 522 to support key retrieval requests. In one embodiment, the protected server is communicatively coupled to the Internet in a well-known manner. For improved security, the protected server should not be the same processing system used in the manufacturing protected system or the manufacturing production system. Atblock 704, the device manufacturer generates a key service public/private key pair that will be used for the key retrieval service provided by the protected server. In one embodiment, the key service public/private key pair may be stored in the protected server. This key pair may be generated once for all processing performed by the system, or a new key pair may be generated for each class of devices. Atblock 706, the device manufacturer delivers the key servicepublic key 507 to the manufacturing protectedsystem 502. -
FIG. 8 is a flow diagram 800 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 protectedsystem 502. Atblock 802, 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 protectedsystem 502 performsblocks 804 to 820. First, atblock 804, 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. Atblock 806, 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, Advanced Encryption Standard (AES), etc.). Atblock 808, in one embodiment, the generation function generates an identifier (ID) label that will be used to reference this device'skeyblob 514 in thekeyblob database 520 on the protectedserver 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 810, the generation function generates the DP private signing key DPpri correlating to the device's Family public key (Fpub). Atblock 812, the generation function hashes DPpri to produce DPpri Digest using known methods (e.g., using SHA-1 or another hash algorithm). Atblock 814, 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 anencrypted keyblob 514. Atblock 816, the Device ID generated atblock 808 and theencrypted keyblob 514 generated atblock 814 may be stored in an entry in akeyblob database 520. In one embodiment, the entry in the keyblob database may be indicated by the Device ID. Atblock 818, the current RAND value may be stored in protecteddatabase 510. Atblock 820, 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 820, atblock 822 the protected database of RAND values may be securely uploaded tomanufacturing 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 protectedsystem 502. Finally, atblock 824, thekeyblob database 520 having a plurality of encrypted keyblobs may be stored on the protectedserver 522, with one keyblob database entry to be used for each device, as indexed by the Device ID field. -
FIG. 9 is a flow diagram 900 illustrating device manufacturing production processing according to an embodiment of the present invention. As devices are being manufacturing in a production line, atblock 902 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. In one embodiment, the RAND value may be stored in approximately 16 bytes of non-volatile storage. Atblock 904, ahash 509 of the key servicepublic key 507 may be stored in the non-volatile storage of the device. The hash may be generated using any known hashing algorithm. In one embodiment, the hash value may be stored in approximately 20 bytes of non-volatile storage. Atblock 906, once the storage of the RAND value is successful, the manufacturing production system destroys any record of that device's RAND value in the protecteddatabase 510. 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. -
FIGS. 10-12 are flow diagrams 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. Starting withflow 1000 onFIG. 10 , atblock 1002, the client computer system may be booted up in the normal manner and a devicedriver software module 526 for the device may be loaded into main memory of the client computer system. When the device driver is initialized and begins execution, the device driver determines atblock 1004 if there is already an encryptedlocalized keyblob 524 stored inmass storage device 308 fordevice 506. If there is, then no further set-up processing need be performed and set-up processing ends atblock 1006. If not, then processing continues withblock 1008. Atblock 1008, the device driver issues an Acquire Key command to thedevice 506 to initiate the device's DP private key acquisition process. - At
block 1010, the device driver sends the key servicepublic key 507 to the device. Atblock 1014, the device extracts the received key service public key, generates a hash value of the key service public key, and compares the hash of the received key service public key to the key service publickey hash 509 stored in non-volatile storage on the device. If the hashes match, the received key service public key is known to be that of the device manufacturer's key retrieval service, and client computer system set-up processing continues. - In another embodiment, the device could receive a certificate of a certified key service public key for which the certificate could be verified through a certificate chain to the key service public key whose hash is the key service public
key hash 509 stored in non-volatile storage on the device. Then the certified key service public key could be used as the key service public key in the subsequent steps. - At block 1013 the device uses its one-way function f to regenerate the symmetric key SKEY from the embedded RAND value 508 (SKEY=f(RAND)). At
block 1020, 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). Processing continues with flow diagram 1100 ofFIG. 11 . - At
block 1102 ofFIG. 11 , the device generates a transient symmetric key Tkey. This key will be sent to the protected server, which may use the key to encrypt the message the protected server returns to the device. Atblock 1104, the device builds a retrieve key request message containing the Device ID and the transient symmetric key Tkey, encrypts the message using the key service public key received from the device driver atblock 1014, and sends the retrieve key request message to the protected server via the device driver. (Retrieve Key Request=Encrypt (Device ID, Tkey) with the key service public key). One skilled in the art will recognize that to encrypt a message with a public key, one would typically create a session key (Skey) for a symmetric cipher, encrypt the session key with the public key, and then encrypt the message with the session key. Atblock 1106, the protected server decrypts the received key request message using the key serviceprivate key 511, and extracts the fields stored therein. Since the protected server now knows the Device ID (obtained from the key request message), the protected server searches the keyblob database for the record containing the matching Device ID value, and extracts the device's encrypted keyblob from the record. Atblock 1110, the protected server builds a second response message containing the Family public key and the encrypted keyblob and encrypts the second response message using the transient symmetric key Tkey supplied by the device. Thus, Key Response=(Family public key, Encryption of (Encrypted Keyblob) using Tkey). Encrypting the Encrypted keyblob with Tkey is not to protect the keyblob, since it is already encrypted with a symmetric key SKEY, which only the device can regenerate. Rather, encrypting the message in this way ensures that the returned keyblob changes each time the key acquisition process is performed, thus ensuring that the keyblob itself cannot be used as a “cookie.” The second response message may be returned to the device driver on the client computer system atblock 1112, which forwards the message to the device. - At
block 1114, the device extracts the Family public key from the second response message, decrypts the wrapped keyblob using the transient symmetric key Tkey, and stores the encrypted keyblob in volatile memory of the device. Processing then continues with flow diagram 1200 ofFIG. 12 . - At
block 1216 ofFIG. 12 , 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. Atblock 1218, 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 in one embodiment also set a Key Acquired flag to true to indicate that the DP private key has been successfully acquired. Atblock 1220, 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). In one embodiment, the new encrypted localized keyblob may be returned to a Key Retrieval utility software module (not shown inFIG. 5 ) on the client computer system. Atblock 1222, the Key Retrieval utility stores the encrypted, localized keyblob in storage within the client computer system (such asmass 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. 13 is a flow diagram 1300 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. Atblock 1302, the client computer system may be booted up in the normal manner and adevice 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 encryptedlocalized keyblob 524 stored inmass storage device 308 fordevice 506. If there is not, then the set-up processing ofFIGS. 10-12 is performed. If there is an encrypted localized keyblob available for this device, then processing continues withblock 1306. Atblock 1306, 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 1308 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)). Atblock 1310, 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. Atblock 1312, 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. Atblock 1314, 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. Atblock 1316, the Key Retrieval utility stores the encrypted, localized keyblob in storage within the client computer system (such asmass 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 keyblob database on the protected server is updated regularly, the device DP private keys could be generated in batches as needed. Each time the keyblob database is updated on the protected server, it would contain the keyblob database as generated to date, including those device keys that had been generated but not yet assigned to devices.
- In another embodiment, it may be possible to delay the generation of the device's DPpri key, allowing these keys to be generated only for those devices that require them. Upon receipt of the first key acquisition request from the device, the protected sever may generate a request to the manufacturing protected system, which still holds the device's RAND value. At this time, the manufacturing protected system generates the DPpri key for the device, returns it to the protected server, and only then destroys the RAND value.
- In another embodiment, instead of storing the key service public key hash in non-volatile storage on the device, the device manufacturer may choose to store the hash of a root key, and then sign certificates for key service public keys with the root key. In this way, the same root key could be used for a very large number of 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, optical and magnetic disks, and a carrier wave that encodes a data signal. 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 (28)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/710,439 US8660266B2 (en) | 2004-07-14 | 2010-02-23 | Method of delivering direct proof private keys to devices using an on-line service |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/892,256 US7697691B2 (en) | 2004-07-14 | 2004-07-14 | Method of delivering Direct Proof private keys to devices using an on-line service |
US12/710,439 US8660266B2 (en) | 2004-07-14 | 2010-02-23 | Method of delivering direct proof private keys to devices using an on-line service |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/892,256 Continuation US7697691B2 (en) | 2004-07-14 | 2004-07-14 | Method of delivering Direct Proof private keys to devices using an on-line service |
Publications (2)
Publication Number | Publication Date |
---|---|
US20100150351A1 true US20100150351A1 (en) | 2010-06-17 |
US8660266B2 US8660266B2 (en) | 2014-02-25 |
Family
ID=35599441
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/892,256 Expired - Fee Related US7697691B2 (en) | 2004-07-14 | 2004-07-14 | Method of delivering Direct Proof private keys to devices using an on-line service |
US12/710,439 Expired - Fee Related US8660266B2 (en) | 2004-07-14 | 2010-02-23 | Method of delivering direct proof private keys to devices using an on-line service |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/892,256 Expired - Fee Related US7697691B2 (en) | 2004-07-14 | 2004-07-14 | Method of delivering Direct Proof private keys to devices using an on-line service |
Country Status (6)
Country | Link |
---|---|
US (2) | US7697691B2 (en) |
JP (1) | JP4673890B2 (en) |
CN (1) | CN101019369B (en) |
DE (1) | DE112005001672B4 (en) |
GB (1) | GB2430127B (en) |
WO (1) | WO2006023151A2 (en) |
Cited By (10)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100266128A1 (en) * | 2007-10-16 | 2010-10-21 | Nokia Corporation | Credential provisioning |
WO2011143774A1 (en) * | 2010-05-17 | 2011-11-24 | Research In Motion Limited | Method for authenticating and registering devices |
US20120102565A1 (en) * | 2010-10-26 | 2012-04-26 | Oberthur Technologies | Method and system for controlling the execution of a function protected by authentification of a user, in particular for the access to a resource |
US20130336481A1 (en) * | 2012-06-15 | 2013-12-19 | Kabushiki Kaisha Toshiba | Device |
US20130339733A1 (en) * | 2012-06-15 | 2013-12-19 | Kabushiki Kaisha Toshiba | Device |
US20130336488A1 (en) * | 2012-06-15 | 2013-12-19 | Kabushiki Kaisha Toshiba | Host device |
US20140140504A1 (en) * | 2012-02-14 | 2014-05-22 | Thomson Licensing | System, devices and methods for collaborative execution of a software application comprising at least one encrypted instruction |
WO2016007785A1 (en) * | 2014-07-11 | 2016-01-14 | Cryptography Research, Inc. | Secure data provisioning |
WO2021016459A1 (en) * | 2019-07-25 | 2021-01-28 | Vengar Technologies, LLC | Enhanced secure encryption and decryption system |
US11876797B2 (en) | 2020-03-30 | 2024-01-16 | Everything Blockchain Technology Corp. | Multi-factor geofencing system for secure encryption and decryption system |
Families Citing this family (42)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8165297B2 (en) * | 2003-11-21 | 2012-04-24 | Finisar Corporation | Transceiver with controller for authentication |
US7802085B2 (en) | 2004-02-18 | 2010-09-21 | Intel Corporation | Apparatus and method for distributing private keys to an entity with minimal secret, unique information |
US7693286B2 (en) * | 2004-07-14 | 2010-04-06 | Intel Corporation | Method of delivering direct proof private keys in signed groups to devices using a distribution CD |
US7697691B2 (en) | 2004-07-14 | 2010-04-13 | Intel Corporation | Method of delivering Direct Proof private keys to devices using an on-line service |
US7792303B2 (en) * | 2004-07-14 | 2010-09-07 | Intel Corporation | Method of delivering direct proof private keys to devices using a distribution CD |
US8924728B2 (en) * | 2004-11-30 | 2014-12-30 | Intel Corporation | Apparatus and method for establishing a secure session with a device without exposing privacy-sensitive information |
HK1155587A1 (en) * | 2005-06-14 | 2012-05-18 | Certicom Corp | System and method for remote device registration |
CA2510366C (en) | 2005-06-14 | 2013-02-26 | Certicom Corp. | System and method for remote device registration |
JP4989806B2 (en) * | 2005-06-14 | 2012-08-01 | サーティコム コーポレーション | System and method for remote device registration |
WO2007098584A1 (en) | 2006-02-28 | 2007-09-07 | Certicom Corp. | System and method for product registration |
US8014530B2 (en) | 2006-03-22 | 2011-09-06 | Intel Corporation | Method and apparatus for authenticated, recoverable key distribution with no database secrets |
US7941845B2 (en) | 2006-10-27 | 2011-05-10 | Storage Appliance Corporation | Systems and methods for controlling production quantities |
US8762714B2 (en) * | 2007-04-24 | 2014-06-24 | Finisar Corporation | Protecting against counterfeit electronics devices |
US9148286B2 (en) * | 2007-10-15 | 2015-09-29 | Finisar Corporation | Protecting against counterfeit electronic devices |
US8627079B2 (en) | 2007-11-01 | 2014-01-07 | Infineon Technologies Ag | Method and system for controlling a device |
US8908870B2 (en) * | 2007-11-01 | 2014-12-09 | Infineon Technologies Ag | Method and system for transferring information to a device |
US20090240945A1 (en) * | 2007-11-02 | 2009-09-24 | Finisar Corporation | Anticounterfeiting means for optical communication components |
US8819423B2 (en) * | 2007-11-27 | 2014-08-26 | Finisar Corporation | Optical transceiver with vendor authentication |
GB2469594B (en) * | 2008-01-22 | 2012-08-29 | Hewlett Packard Development Co | Shared secret used between keyboard and application |
CN101562784B (en) * | 2008-04-14 | 2012-06-06 | 华为技术有限公司 | Method, device and system for distributing messages |
EP2526505B1 (en) * | 2010-01-20 | 2015-06-17 | Intrinsic ID B.V. | Device and method for obtaining a cryptographic key |
US8715625B1 (en) | 2010-05-10 | 2014-05-06 | The Clorox Company | Natural oral care compositions |
JP5644194B2 (en) * | 2010-06-10 | 2014-12-24 | 株式会社リコー | Information protection device and information protection program |
US20120137137A1 (en) * | 2010-11-30 | 2012-05-31 | Brickell Ernest F | Method and apparatus for key provisioning of hardware devices |
US8600061B2 (en) | 2011-06-24 | 2013-12-03 | Broadcom Corporation | Generating secure device secret key |
US9064209B2 (en) * | 2011-10-01 | 2015-06-23 | Intel Corporation | Printing through physical proximity between printer and print client device |
US8874904B1 (en) * | 2012-12-13 | 2014-10-28 | Emc Corporation | View computation and transmission for a set of keys refreshed over multiple epochs in a cryptographic device |
FR3004561B1 (en) * | 2013-04-15 | 2016-11-11 | Banque Accord | METHOD AND SYSTEM FOR ENHANCING SECURITY OF ELECTRONIC TRANSACTIONS |
CN103259651B (en) * | 2013-05-30 | 2016-06-08 | 成都欣知科技有限公司 | A kind of method and system to terminal data encryption and decryption |
US9485250B2 (en) * | 2015-01-30 | 2016-11-01 | Ncr Corporation | Authority trusted secure system component |
US9680646B2 (en) * | 2015-02-05 | 2017-06-13 | Apple Inc. | Relay service for communication between controllers and accessories |
US10037436B2 (en) * | 2015-12-11 | 2018-07-31 | Visa International Service Association | Device using secure storage and retrieval of data |
DE102015016302A1 (en) * | 2015-12-15 | 2017-06-22 | Giesecke & Devrient Gmbh | Agreement of exchange keys based on two static asymmetric key pairs |
DE102016116152A1 (en) * | 2016-04-30 | 2017-11-02 | Krohne Messtechnik Gmbh | Electrical device with a functional device |
US10897459B2 (en) * | 2017-01-26 | 2021-01-19 | Microsoft Technology Licensing, Llc | Addressing a trusted execution environment using encryption key |
DE102017202787A1 (en) * | 2017-02-21 | 2018-08-23 | Siemens Aktiengesellschaft | Method and validation unit for controlling the loading of cryptographic keys that can be used in IT systems, in particular embedded systems, in particular "key blobs" |
US11823501B2 (en) * | 2017-08-18 | 2023-11-21 | Oracle International Corporation | Associating voting sessions with tabulation machines in electronic voting |
EP3619886A4 (en) * | 2017-08-18 | 2020-04-29 | Samsung Electronics Co., Ltd. | Method and an apparatus for onboarding in an iot network |
US11101984B2 (en) * | 2019-04-04 | 2021-08-24 | Micron Technology, Inc. | Onboarding software on secure devices to generate device identities for authentication with remote servers |
CN110149209B (en) * | 2019-04-15 | 2022-06-28 | 深圳奇迹智慧网络有限公司 | Internet of things equipment and method and device for improving data transmission safety of Internet of things equipment |
US11477014B1 (en) | 2019-08-23 | 2022-10-18 | Liberty Mutual Insurance Company | Anonymized data transmission using per-user-functionality secret shares |
CN116208428B (en) * | 2023-04-27 | 2023-07-18 | 中科信工创新技术(北京)有限公司 | Method, system, device, storage medium and electronic equipment for transmitting file |
Citations (41)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5430802A (en) * | 1992-06-24 | 1995-07-04 | Page; Steven L. | Audio speaker system |
US5581621A (en) * | 1993-04-19 | 1996-12-03 | Clarion Co., Ltd. | Automatic adjustment system and automatic adjustment method for audio devices |
US5771291A (en) * | 1995-12-11 | 1998-06-23 | Newton; Farrell | User identification and authentication system using ultra long identification keys and ultra large databases of identification keys for secure remote terminal access to a host computer |
US5857021A (en) * | 1995-11-07 | 1999-01-05 | Fujitsu Ltd. | Security system for protecting information stored in portable storage media |
US5924094A (en) * | 1996-11-01 | 1999-07-13 | Current Network Technologies Corporation | Independent distributed database system |
US6032260A (en) * | 1997-11-13 | 2000-02-29 | Ncr Corporation | Method for issuing a new authenticated electronic ticket based on an expired authenticated ticket and distributed server architecture for using same |
US6032261A (en) * | 1997-12-30 | 2000-02-29 | Philips Electronics North America Corp. | Bus bridge with distribution of a common cycle clock to all bridge portals to provide synchronization of local buses, and method of operation thereof |
US6038322A (en) * | 1998-10-20 | 2000-03-14 | Cisco Technology, Inc. | Group key distribution |
US6036061A (en) * | 1998-04-27 | 2000-03-14 | O'donnell; Thomas F. | Retainer for blank of split cap |
US6151676A (en) * | 1997-12-24 | 2000-11-21 | Philips Electronics North America Corporation | Administration and utilization of secret fresh random numbers in a networked environment |
US6185316B1 (en) * | 1997-11-12 | 2001-02-06 | Unisys Corporation | Self-authentication apparatus and method |
US6389403B1 (en) * | 1998-08-13 | 2002-05-14 | International Business Machines Corporation | Method and apparatus for uniquely identifying a customer purchase in an electronic distribution system |
US6411715B1 (en) * | 1997-11-10 | 2002-06-25 | Rsa Security, Inc. | Methods and apparatus for verifying the cryptographic security of a selected private and public key pair without knowing the private key |
US20020080190A1 (en) * | 2000-12-23 | 2002-06-27 | International Business Machines Corporation | Back-up and usage of secure copies of smart card data objects |
US6424717B1 (en) * | 1995-04-03 | 2002-07-23 | Scientific-Atlanta, Inc. | Encryption devices for use in a conditional access system |
US6438666B2 (en) * | 1997-09-26 | 2002-08-20 | Hughes Electronics Corporation | Method and apparatus for controlling access to confidential data by analyzing property inherent in data |
US20020178354A1 (en) * | 1999-10-18 | 2002-11-28 | Ogg Craig L. | Secured centralized public key infrastructure |
US20030037237A1 (en) * | 2001-04-09 | 2003-02-20 | Jean-Paul Abgrall | Systems and methods for computer device authentication |
US6611812B2 (en) * | 1998-08-13 | 2003-08-26 | International Business Machines Corporation | Secure electronic content distribution on CDS and DVDs |
US20030182584A1 (en) * | 2002-03-22 | 2003-09-25 | John Banes | Systems and methods for setting and resetting a password |
US6711263B1 (en) * | 1999-05-07 | 2004-03-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Secure distribution and protection of encryption key information |
US6738904B2 (en) * | 2000-06-02 | 2004-05-18 | Koninklijke Philips Electronics N.V. | Recordable storage medium with protected data area |
US20040103281A1 (en) * | 2002-11-27 | 2004-05-27 | Brickell Ernie F. | System and method for establishing trust without revealing identity |
US6749511B2 (en) * | 2000-08-17 | 2004-06-15 | Adam S. Day | Website promotional applet process |
US6792113B1 (en) * | 1999-12-20 | 2004-09-14 | Microsoft Corporation | Adaptable security mechanism for preventing unauthorized access of digital data |
US6826616B2 (en) * | 1998-10-30 | 2004-11-30 | Science Applications International Corp. | Method for establishing secure communication link between computers of virtual private network |
US6829250B2 (en) * | 2000-08-10 | 2004-12-07 | Verizon Communications Inc. | Automatic programming of customer premises equipment for vertical services integration |
US6898706B1 (en) * | 1999-05-20 | 2005-05-24 | Microsoft Corporation | License-based cryptographic technique, particularly suited for use in a digital rights management system, for controlling access and use of bore resistant software objects in a client computer |
US6941456B2 (en) * | 2001-05-02 | 2005-09-06 | Sun Microsystems, Inc. | Method, system, and program for encrypting files in a computer system |
US6983368B2 (en) * | 2000-08-04 | 2006-01-03 | First Data Corporation | Linking public key of device to information during manufacture |
US6983511B2 (en) * | 2001-05-31 | 2006-01-10 | Lindhaus S.R.L. | Multipurpose tool for cleaning machines |
US6987853B2 (en) * | 2000-11-29 | 2006-01-17 | Bodacion Technologies, Llc | Method and apparatus for generating a group of character sets that are both never repeating within certain period of time and difficult to guess |
US20060117181A1 (en) * | 2004-11-30 | 2006-06-01 | Brickell Ernest F | Apparatus and method for establishing a secure session with a device without exposing privacy-sensitive information |
US7093139B2 (en) * | 2000-02-15 | 2006-08-15 | Silverbrook Research Pty Ltd | Unauthorized modification of values stored in flash memory |
US7178030B2 (en) * | 2000-10-25 | 2007-02-13 | Tecsec, Inc. | Electronically signing a document |
US7216100B2 (en) * | 1999-01-11 | 2007-05-08 | Teq Development | Method for obtaining and allocating investment income based on the capitalization of intellectual property |
US7297188B2 (en) * | 2001-06-15 | 2007-11-20 | Larry Nielsen | Floor finishing and dust collection apparatus |
US7526651B2 (en) * | 2003-05-20 | 2009-04-28 | France Telecom | Electronic group signature method with revocable anonymity, equipment and programs for implementing the method |
US7693286B2 (en) * | 2004-07-14 | 2010-04-06 | Intel Corporation | Method of delivering direct proof private keys in signed groups to devices using a distribution CD |
US7792303B2 (en) * | 2004-07-14 | 2010-09-07 | Intel Corporation | Method of delivering direct proof private keys to devices using a distribution CD |
US7844819B2 (en) * | 2001-11-26 | 2010-11-30 | Panasonic Corporation | Application authentication system |
Family Cites Families (22)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH01200735A (en) | 1988-02-05 | 1989-08-11 | Nec Corp | Sound wave transmitter |
DE19539538A1 (en) | 1994-10-31 | 1996-05-02 | Tektronix Inc | Inaudible insertion of information into an audio signal |
EP0784386A2 (en) | 1996-01-11 | 1997-07-16 | Marikon Resources, Inc | Wireless audio signal transmission system |
AU1456397A (en) | 1996-01-23 | 1997-08-20 | Aim Corporation | Information display system |
JPH11143781A (en) * | 1997-11-10 | 1999-05-28 | Taisei Corp | Decipherment limiting device |
US5991399A (en) | 1997-12-18 | 1999-11-23 | Intel Corporation | Method for securely distributing a conditional use private key to a trusted entity on a remote system |
JPH11202765A (en) * | 1998-01-16 | 1999-07-30 | Mitsubishi Materials Corp | Ciphered information processor, ciphered information processing method and recording medium |
AU2998100A (en) | 1999-02-18 | 2000-09-04 | Sun Microsystems, Inc. | Data authentication system employing encrypted integrity blocks |
FI112315B (en) | 1999-05-11 | 2003-11-14 | Nokia Corp | Integrity protection method for radio network signaling |
US6928615B1 (en) | 1999-07-07 | 2005-08-09 | Netzero, Inc. | Independent internet client object with ad display capabilities |
GB9929050D0 (en) | 1999-12-08 | 2000-02-02 | Nokia Networks Oy | Communication method |
GB0004178D0 (en) | 2000-02-22 | 2000-04-12 | Nokia Networks Oy | Integrity check in a communication system |
AU2001255525A1 (en) | 2000-04-21 | 2001-11-07 | Keyhold Engineering, Inc. | Self-calibrating surround sound system |
JP2002016592A (en) * | 2000-04-25 | 2002-01-18 | Open Loop:Kk | Encryption key management system and encryption key management method |
FI111423B (en) | 2000-11-28 | 2003-07-15 | Nokia Corp | A system for securing post-handover communications |
GB0103416D0 (en) | 2001-02-12 | 2001-03-28 | Nokia Networks Oy | Message authentication |
JP2002314522A (en) * | 2001-04-09 | 2002-10-25 | Fuji Xerox Co Ltd | Secret key transmission device and method |
US6703923B2 (en) * | 2001-04-18 | 2004-03-09 | Thomson Licensing S.A. | Apparatus for providing security on a powerline-modem network |
DE10218835B4 (en) * | 2002-04-22 | 2009-09-10 | Deutscher Sparkassen Verlag Gmbh | Method for producing a chip card and chip card |
EP1617587A1 (en) | 2004-07-12 | 2006-01-18 | International Business Machines Corporation | Method, system and computer program product for privacy-protecting integrity attestation of computing platform |
US7697691B2 (en) | 2004-07-14 | 2010-04-13 | Intel Corporation | Method of delivering Direct Proof private keys to devices using an on-line service |
GB2439150A (en) | 2006-06-17 | 2007-12-19 | Stepashead Ltd | Ball rack allowing triangular or diamond ball formation |
-
2004
- 2004-07-14 US US10/892,256 patent/US7697691B2/en not_active Expired - Fee Related
-
2005
- 2005-07-08 GB GB0700524A patent/GB2430127B/en not_active Expired - Fee Related
- 2005-07-08 DE DE112005001672T patent/DE112005001672B4/en not_active Expired - Fee Related
- 2005-07-08 JP JP2007521519A patent/JP4673890B2/en not_active Expired - Fee Related
- 2005-07-08 WO PCT/US2005/024374 patent/WO2006023151A2/en active Application Filing
- 2005-07-08 CN CN2005800307184A patent/CN101019369B/en not_active Expired - Fee Related
-
2010
- 2010-02-23 US US12/710,439 patent/US8660266B2/en not_active Expired - Fee Related
Patent Citations (44)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5430802A (en) * | 1992-06-24 | 1995-07-04 | Page; Steven L. | Audio speaker system |
US5581621A (en) * | 1993-04-19 | 1996-12-03 | Clarion Co., Ltd. | Automatic adjustment system and automatic adjustment method for audio devices |
US6424717B1 (en) * | 1995-04-03 | 2002-07-23 | Scientific-Atlanta, Inc. | Encryption devices for use in a conditional access system |
US5857021A (en) * | 1995-11-07 | 1999-01-05 | Fujitsu Ltd. | Security system for protecting information stored in portable storage media |
US5771291A (en) * | 1995-12-11 | 1998-06-23 | Newton; Farrell | User identification and authentication system using ultra long identification keys and ultra large databases of identification keys for secure remote terminal access to a host computer |
US5924094A (en) * | 1996-11-01 | 1999-07-13 | Current Network Technologies Corporation | Independent distributed database system |
US6438666B2 (en) * | 1997-09-26 | 2002-08-20 | Hughes Electronics Corporation | Method and apparatus for controlling access to confidential data by analyzing property inherent in data |
US6411715B1 (en) * | 1997-11-10 | 2002-06-25 | Rsa Security, Inc. | Methods and apparatus for verifying the cryptographic security of a selected private and public key pair without knowing the private key |
US6185316B1 (en) * | 1997-11-12 | 2001-02-06 | Unisys Corporation | Self-authentication apparatus and method |
US6032260A (en) * | 1997-11-13 | 2000-02-29 | Ncr Corporation | Method for issuing a new authenticated electronic ticket based on an expired authenticated ticket and distributed server architecture for using same |
US6151676A (en) * | 1997-12-24 | 2000-11-21 | Philips Electronics North America Corporation | Administration and utilization of secret fresh random numbers in a networked environment |
US6032261A (en) * | 1997-12-30 | 2000-02-29 | Philips Electronics North America Corp. | Bus bridge with distribution of a common cycle clock to all bridge portals to provide synchronization of local buses, and method of operation thereof |
US6036061A (en) * | 1998-04-27 | 2000-03-14 | O'donnell; Thomas F. | Retainer for blank of split cap |
US6389403B1 (en) * | 1998-08-13 | 2002-05-14 | International Business Machines Corporation | Method and apparatus for uniquely identifying a customer purchase in an electronic distribution system |
US6611812B2 (en) * | 1998-08-13 | 2003-08-26 | International Business Machines Corporation | Secure electronic content distribution on CDS and DVDs |
US6038322A (en) * | 1998-10-20 | 2000-03-14 | Cisco Technology, Inc. | Group key distribution |
US6826616B2 (en) * | 1998-10-30 | 2004-11-30 | Science Applications International Corp. | Method for establishing secure communication link between computers of virtual private network |
US7216100B2 (en) * | 1999-01-11 | 2007-05-08 | Teq Development | Method for obtaining and allocating investment income based on the capitalization of intellectual property |
US6711263B1 (en) * | 1999-05-07 | 2004-03-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Secure distribution and protection of encryption key information |
US6898706B1 (en) * | 1999-05-20 | 2005-05-24 | Microsoft Corporation | License-based cryptographic technique, particularly suited for use in a digital rights management system, for controlling access and use of bore resistant software objects in a client computer |
US20020178354A1 (en) * | 1999-10-18 | 2002-11-28 | Ogg Craig L. | Secured centralized public key infrastructure |
US7392377B2 (en) * | 1999-10-18 | 2008-06-24 | Stamps.Com | Secured centralized public key infrastructure |
US7216110B1 (en) * | 1999-10-18 | 2007-05-08 | Stamps.Com | Cryptographic module for secure processing of value-bearing items |
US6792113B1 (en) * | 1999-12-20 | 2004-09-14 | Microsoft Corporation | Adaptable security mechanism for preventing unauthorized access of digital data |
US7093139B2 (en) * | 2000-02-15 | 2006-08-15 | Silverbrook Research Pty Ltd | Unauthorized modification of values stored in flash memory |
US6738904B2 (en) * | 2000-06-02 | 2004-05-18 | Koninklijke Philips Electronics N.V. | Recordable storage medium with protected data area |
US6983368B2 (en) * | 2000-08-04 | 2006-01-03 | First Data Corporation | Linking public key of device to information during manufacture |
US6829250B2 (en) * | 2000-08-10 | 2004-12-07 | Verizon Communications Inc. | Automatic programming of customer premises equipment for vertical services integration |
US6749511B2 (en) * | 2000-08-17 | 2004-06-15 | Adam S. Day | Website promotional applet process |
US7178030B2 (en) * | 2000-10-25 | 2007-02-13 | Tecsec, Inc. | Electronically signing a document |
US6987853B2 (en) * | 2000-11-29 | 2006-01-17 | Bodacion Technologies, Llc | Method and apparatus for generating a group of character sets that are both never repeating within certain period of time and difficult to guess |
US20020080190A1 (en) * | 2000-12-23 | 2002-06-27 | International Business Machines Corporation | Back-up and usage of secure copies of smart card data objects |
US20040039924A1 (en) * | 2001-04-09 | 2004-02-26 | Baldwin Robert W. | System and method for security of computing devices |
US20030037237A1 (en) * | 2001-04-09 | 2003-02-20 | Jean-Paul Abgrall | Systems and methods for computer device authentication |
US6941456B2 (en) * | 2001-05-02 | 2005-09-06 | Sun Microsystems, Inc. | Method, system, and program for encrypting files in a computer system |
US6983511B2 (en) * | 2001-05-31 | 2006-01-10 | Lindhaus S.R.L. | Multipurpose tool for cleaning machines |
US7297188B2 (en) * | 2001-06-15 | 2007-11-20 | Larry Nielsen | Floor finishing and dust collection apparatus |
US7844819B2 (en) * | 2001-11-26 | 2010-11-30 | Panasonic Corporation | Application authentication system |
US20030182584A1 (en) * | 2002-03-22 | 2003-09-25 | John Banes | Systems and methods for setting and resetting a password |
US20040103281A1 (en) * | 2002-11-27 | 2004-05-27 | Brickell Ernie F. | System and method for establishing trust without revealing identity |
US7526651B2 (en) * | 2003-05-20 | 2009-04-28 | France Telecom | Electronic group signature method with revocable anonymity, equipment and programs for implementing the method |
US7693286B2 (en) * | 2004-07-14 | 2010-04-06 | Intel Corporation | Method of delivering direct proof private keys in signed groups to devices using a distribution CD |
US7792303B2 (en) * | 2004-07-14 | 2010-09-07 | Intel Corporation | Method of delivering direct proof private keys to devices using a distribution CD |
US20060117181A1 (en) * | 2004-11-30 | 2006-06-01 | Brickell Ernest F | Apparatus and method for establishing a secure session with a device without exposing privacy-sensitive information |
Non-Patent Citations (2)
Title |
---|
Baldwin, Adrian. Shiu, Simon. "Encryption and Key Management in a SAN". First International IEEE Security in Storage Workshop. Pub. Date: Dec. 2002. Relevant Pages: 35-44. Found on the World Wide Web at: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=1183508 * |
Feige, Uriel; Lapidot, Dror; Shamir, Adi. Multiple Non-Interactive Zero Knowledge Proofs Based on a Single Random String. 31st Annual Symposium on Foundations of Computer Science. Vol. 1 Pub. Date: 1990. Relevant Pages: 308-317. Found on the World Wide Web at: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=89549 * |
Cited By (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100266128A1 (en) * | 2007-10-16 | 2010-10-21 | Nokia Corporation | Credential provisioning |
US8724819B2 (en) * | 2007-10-16 | 2014-05-13 | Nokia Corporation | Credential provisioning |
WO2011143774A1 (en) * | 2010-05-17 | 2011-11-24 | Research In Motion Limited | Method for authenticating and registering devices |
US9325677B2 (en) | 2010-05-17 | 2016-04-26 | Blackberry Limited | Method of registering devices |
US20120102565A1 (en) * | 2010-10-26 | 2012-04-26 | Oberthur Technologies | Method and system for controlling the execution of a function protected by authentification of a user, in particular for the access to a resource |
CN102546169A (en) * | 2010-10-26 | 2012-07-04 | 欧贝特技术公司 | Method and system for controlling the performance of a function protected by user authentication, in particular for accessing a resource |
US8931080B2 (en) * | 2010-10-26 | 2015-01-06 | Oberthur Technologies | Method and system for controlling the execution of a function protected by authentification of a user, in particular for the access to a resource |
US20140140504A1 (en) * | 2012-02-14 | 2014-05-22 | Thomson Licensing | System, devices and methods for collaborative execution of a software application comprising at least one encrypted instruction |
US20130339733A1 (en) * | 2012-06-15 | 2013-12-19 | Kabushiki Kaisha Toshiba | Device |
US8898463B2 (en) * | 2012-06-15 | 2014-11-25 | Kabushiki Kaisha Toshiba | Device |
US20130336488A1 (en) * | 2012-06-15 | 2013-12-19 | Kabushiki Kaisha Toshiba | Host device |
US8948400B2 (en) * | 2012-06-15 | 2015-02-03 | Kabushiki Kaisha Toshiba | Host device |
US8989374B2 (en) * | 2012-06-15 | 2015-03-24 | Kabushiki Kaisha Toshiba | Cryptographic device for secure authentication |
US20130336481A1 (en) * | 2012-06-15 | 2013-12-19 | Kabushiki Kaisha Toshiba | Device |
WO2016007785A1 (en) * | 2014-07-11 | 2016-01-14 | Cryptography Research, Inc. | Secure data provisioning |
US10440000B2 (en) * | 2014-07-11 | 2019-10-08 | Cryptography Research, Inc. | Secure data provisioning |
US20200120077A1 (en) * | 2014-07-11 | 2020-04-16 | Cryptography Research, Inc. | Secure data provisioning |
US11765149B2 (en) * | 2014-07-11 | 2023-09-19 | Cryptography Research, Inc. | Secure data provisioning |
WO2021016459A1 (en) * | 2019-07-25 | 2021-01-28 | Vengar Technologies, LLC | Enhanced secure encryption and decryption system |
US11570155B2 (en) | 2019-07-25 | 2023-01-31 | Everything Blockchain Technology Corp. | Enhanced secure encryption and decryption system |
US11876797B2 (en) | 2020-03-30 | 2024-01-16 | Everything Blockchain Technology Corp. | Multi-factor geofencing system for secure encryption and decryption system |
Also Published As
Publication number | Publication date |
---|---|
GB2430127B (en) | 2008-12-31 |
GB2430127A (en) | 2007-03-14 |
GB0700524D0 (en) | 2007-02-21 |
CN101019369B (en) | 2011-05-18 |
JP2008507205A (en) | 2008-03-06 |
US8660266B2 (en) | 2014-02-25 |
WO2006023151A2 (en) | 2006-03-02 |
CN101019369A (en) | 2007-08-15 |
US7697691B2 (en) | 2010-04-13 |
DE112005001672T5 (en) | 2007-05-31 |
DE112005001672B4 (en) | 2010-12-09 |
WO2006023151A3 (en) | 2006-11-30 |
JP4673890B2 (en) | 2011-04-20 |
US20060013402A1 (en) | 2006-01-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8660266B2 (en) | Method of delivering direct proof private keys to devices using an on-line service | |
US7693286B2 (en) | Method of delivering direct proof private keys in signed groups to devices using a distribution CD | |
JP4616345B2 (en) | A method for directly distributing a certification private key to a device using a distribution CD | |
US6058478A (en) | Apparatus and method for a vetted field upgrade | |
US8074265B2 (en) | Methods and systems for verifying a location factor associated with a token | |
AU2003202511B2 (en) | Methods for authenticating potential members invited to join a group | |
US5796840A (en) | Apparatus and method for providing secured communications | |
CN1708942B (en) | Secure implementation and utilization of device-specific security data | |
US7571329B2 (en) | Method of storing unique constant values | |
WO2018144578A1 (en) | Origin certificate based online certificate issuance | |
CN111614621B (en) | Internet of things communication method and system | |
CN109800588B (en) | Dynamic bar code encryption method and device and dynamic bar code decryption method and device | |
CN117155549A (en) | Key distribution method, key distribution device, computer equipment and storage medium | |
KR100883442B1 (en) | Method of delivering direct proof private keys to devices using an on-line service | |
KR100897075B1 (en) | Method of delivering direct proof private keys in signed groups to devices using a distribution cd | |
CN114553557A (en) | Key calling method, key calling device, computer equipment and storage medium | |
US11783057B2 (en) | Method for securely provisioning a device incorporating an integrated circuit without using a secure environment | |
CN117318941B (en) | Method, system, terminal and storage medium for distributing preset secret key based on in-car network | |
CN116232639A (en) | Data transmission method, device, computer equipment and storage medium | |
CN115022057A (en) | Security authentication method, device and equipment and storage medium | |
CN111062005A (en) | Copyright authentication password generation method, authentication method, device and storage medium |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCF | Information on status: patent grant |
Free format text: PATENTED CASE |
|
FPAY | Fee payment |
Year of fee payment: 4 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20220225 |