US 7,802,085 B2Grant
Apparatus and method for distributing private keys to an entity with minimal secret, unique information
Issue Date:2010-09-21
•14 Claims
•13 Drawing Sheets
Abstract
In some embodiments, a method and apparatus for distributing private keys to an entity with minimal secret, unique information are described. In one embodiment, the method includes the storage of a chip secret key within a manufactured chip. Once the chip secret key is stored or programmed within the chip, the chip is sent to a system original equipment manufacturer (OEM) in order to integrate the chip within a system or device. Subsequently, a private key is generated for the chip by a key distribution facility (KDF) according to a key request received from the system OEM. In one embodiment, the KDF is the chip manufacturer. Other embodiments are described and claims.
Metadata
Assignee
- Intel Corporation
Inventor
- Gary L. Graunke
Application Information
Application Number:US 10/782,572
Filing Date:2004-02-18
Priority Date:2004-02-18
Art Unit:2437
Classifications
IPC:
G06F9/00
Patent Drawings (13 sheets)
Description
Field of the Invention
[0001] One or more embodiments of the invention relate generally to the field of cryptography. More particularly, one or more of the embodiments of the invention relates to a method and apparatus for distributing private keys to an entity with minimal secret, unique information.
Background of the Invention
[0002] The proliferation of the Internet has led to the creation of a new form of commerce, generally referred to as Internet or electronic commerce (E-commerce). E-commerce enables users to sell and purchase items from a worldwide community connected via the Internet. This added simplicity, coupled with the continually reduced costs and increasing processing speed of modern-day computers, has led to the inclusion of a personal computer (PC) in many homes throughout the world. Unfortunately, the proliferation of PCs within the homes throughout the world, as well as the use of such PCs for E-commerce, often results in the storage of sensitive information within a computer.
[0003] As a result, computer users become susceptible to rogue agents, which may desire to gain access to secure information loaded within their personal computer. In order to combat the various rogue agents from gaining access to the secure information, many computer systems employ some form of cryptographs in order to prevent access to sensitive information. As known to those skilled in the art, cryptography provides a technique for keeping information secret, for determining that the information has not been tampered with and for determining who authored pieces of information.
[0004] One form of cryptography involves public/private key systems. Public/private key systems encrypt information prior to transmission using a public key and decrypting received encrypted information using a private key that is only known to the recipient of the encrypted information. However, once the sensitive information arrives at its designated location, the information is often decrypted and stored in a clear format. In other words, the sensitive information is not maintained in a secure format at its destination. As a result, during operation of a PC, a rogue agent could possibly gain access to the PC and gain access to sensitive information.
[0005] Furthermore, the proliferation of E-commerce has led to the availability of media applications, such as motion pictures and music, which may be downloaded to a PC for one-time use or for use for a predetermined period of time. Unfortunately, without some mechanism for protecting the contents of such media applications from access by rogue agents, E-commerce involving media applications may be prohibitive to the media providers. As a result, media or content providers may be reluctant to create high quality media or content providing applications when such content may be susceptible to rogue agents.
Brief Description of the Drawings
[0006] The various embodiments of the present invention are illustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings and in which:
[0007] FIG. 1 is a block diagram illustrating a computer system including a chipset having key logic to enable receipt of a private key while storing minimal secret, unique information within the chipset, in accordance with one embodiment.
[0008] FIG. 2 is a block diagram illustrating an overview of distributing private keys to an entity with minimal secret, unique information, in accordance with one embodiment.
[0009] FIG. 3 is a block diagram further illustrating secret key logic of FIG. 2 , in accordance with one embodiment.
[0010] FIG. 4 is a block diagram further illustrating key logic of FIG. 1 , in accordance with one embodiment.
[0011] FIG. 5 is a block diagram further illustrating key distribution facility of FIG. 2 , in accordance with one embodiment.
[0012] FIG. 6 is a flowchart illustrating a method for installing minimal secret, unique information within a manufactured chip to enable distribution of at least one private key to the manufactured chip, in accordance with one embodiment.
[0013] FIG. 7 is a flowchart illustrating a method for installing minimal secret, unique information within a manufactured chip, in accordance with one embodiment.
[0014] FIG. 8 is a flowchart illustrating a method for generating a private key in response to a key update request, in accordance with one embodiment.
[0015] FIG. 9 is a flowchart illustrating a method for authenticating a received key update request, in accordance with one embodiment.
[0016] FIG. 10 is a flowchart illustrating a method for generating a key vector, in accordance with one embodiment.
[0017] FIG. 11 is a flowchart illustrating a method for initializing an integrated chip, including stored secret, unique information, to receive at least one private key, in accordance with one embodiment.
[0018] FIG. 12 is a flowchart illustrating a method for initializing an integrated chip having minimal unique, secret information, in accordance with one embodiment.
[0019] FIG. 13 is a flowchart illustrating a method for initializing an integrated chip having stored minimal secret, unique information to perform authentication using at least one private key assigned to the integrated chip, in accordance with one embodiment.
[0020] FIG. 14 is a flowchart illustrating a method for requesting an integrated chip having stored minimal unique, secret information to perform a key update request, in accordance with one embodiment.
Detailed Description
[0021] A method and apparatus for distributing private keys to an entity with minimal secret, unique information are described. In one embodiment, the method includes the storage of a chip secret key within a manufactured chip. Once the chip secret key is stored or programmed within the chip, the chip is sent to a system original equipment manufacturer (OEM) in order to integrate the chip within a system or device. Subsequently, a private key is generated for the chip by a key distribution facility (KDF) according to a key request received from the system OEM. In one embodiment, the KDF is the chip manufacturer.
[0022] In the following description, certain terminology is used to describe features of the invention. For example, the term “logic” is representative of hardware and/or software configured to perform one or more functions. For instance, examples of “hardware” include, but are not limited or restricted to, an integrated circuit, a finite state machine or even combinatorial logic. The integrated circuit may take the form of a processor such as a microprocessor, application specific integrated circuit, a digital signal processor, a micro-controller, or the like.
[0023] An example of “software” includes executable code in the form of an application, an applet, a routine or even a series of instructions. The software may be stored in any type of computer or machine readable medium such as a programmable electronic circuit, a semiconductor memory device inclusive of volatile memory (e.g., random access memory, etc.) and/or non-volatile memory (e.g., any type of read-only memory “ROM,” flash memory), a floppy diskette, an optical disk (e.g., compact disk or digital video disk “DVD”), a hard drive disk, tape, or the like.
System
[0024] FIG. 1 is a block diagram illustrating computer system 100 including chipset 310 manufactured to include chip secret key (Kc) 250 to enable distribution of a private key to chipset 310 using key logic 320, in accordance with one embodiment. Computer system 100 comprises processor system bus (front side bus (FSB)) 102 for communicating information between processor (CPU) 110 and chipset 310 coupled together via FSB 102. As described herein, the term “chipset” is used to describe, collectively the various devices coupled to CPU 110 to perform desired system functionality.
[0025] Chipset 310 is coupled to main memory 120 and non-volatile (e.g., Flash) memory 150. In one embodiment, main memory 120 is volatile memory including, but not limited to, random access memory (RAM), synchronous RAM (SRAM), double data rate (DDR), synchronous dynamic RAM (SDRAM), rambus dynamic RAM (RDRAM), or the like. In addition, hard disk drive devices (HDD) 130, as well as one or more input/output (I/O) devices 140 (140-1, . . . , 140-N) are also coupled to chipset 310. As illustrated, chipset 310 includes store chip secret key 250 and key logic 320, which are further described with reference to FIG. 2 .
[0026] FIG. 2 provides an overview for the installation of chip secret key 250 within chip 222 manufactured by manufacturer 200 and the subsequent generation and assignment of at least one private key 290 to chip 222 once integrated within chipset 310, in accordance with one embodiment. As described herein, chip 222 is may alternatively referred to as manufactured chip 222, and integrated chip 222. In one embodiment, private key 290 is stored within flash memory 150. Representatively, private key 290 enables chip 222 to perform an authentication procedure to establish a secure authenticated channel, in accordance with one embodiment. In one embodiment, a chip secret key 250 enables assignment of at least one public/private key crypto-system key to chip 222.
[0027] In one embodiment, the installation of chip secret key 250 within manufactured chip 222 enables public key cryptography. As described herein, a cryptographic system refers to a system that uses two keys; a public key known to everyone, and a private, or secret, key known only to the recipient of digital content. Accordingly, digital content is initially encrypted by transforming the content into an unreadable format referred to as “cipher text” using a recipient's public key. Subsequently, when the encrypted digital content, or cipher text, is received by the recipient, the received content may be decrypted, or deciphered, using a private key of the recipient to form the digital content in the clear format.
[0028] However, as will be recognized by those skilled in the art, the embodiments described herein are not limited to public key cryptography or asymmetric encryption, which uses a public key and private key pair, but may be used within systems for symmetric encryption, which uses single secret, or private, key. Hence, the techniques described herein can be modified to function within cryptographic system, such as symmetric key systems that use a single key that both the sender and the recipient have, as well as public key systems that use two public keys; a public key known to everyone and a private key known to only the recipient of encrypted cipher text.
[0029] Referring again to FIG. 2 , chip manufacturer 200 initially gathers unique manufacturing information (Mc) for each chip. As illustrated, chip 222 is formed during wafer sort from fabricated wafer 212. Hence, in one embodiment, manufacturing information from each chip may include a wafer serial number from which chip 222 is formed in addition to a coordinate X,Y location of chip 222 within wafer 212. Once this information is formed, the manufacturing information Mc is provided to secret key logic 230, as further illustrated with reference to FIG. 3 .
[0030] As illustrated with reference to FIG. 3 , manufacturing information Mc 232 is initially provided to first block cipher 236. First block cipher 236 also receives first key (K1) 234. As illustrated, block cipher 236 encrypts Mc 232 to form a unique chip ID (IDc) 240. As further illustrated, chip ID 240 is provided to second block cipher 244, which encrypts IDc 240 to form chip secret key (Kc) 250. Once chip secret key 250 is formed, chip secret key 250 is provided to Kc program logic 252. In one embodiment, program logic 252 installs chip secret key 250 within manufactured chip 222.
[0031] In one embodiment, block cipher 236 and block cipher 244 may be implemented using the advanced encryption standard (AES), the triple data encryption standard (3DES), the data encryption standard (DES) or other like encryption/decryption standard. Accordingly, as described herein, the term cryptographic block refers to logic designed to encrypt content or decrypt cipher text according to AES, DES, 3DES or other like encryption/decryption standard.
[0032] In one embodiment, chip secret key 250 is installed and programmed into manufactured chip 222 by blowing fuses or equivalent mechanism to store chip set key 250 within manufactured chip 222. Once installed, chip 222 is sent to system OEM 300 for integration. For example, referring again to FIG. 3 , secret key logic 230 transmits manufactured chip 222, including chip secret key 250 to OEM 300 for integration within chipset 310. Once installed or integrated within chipset 310, OEM 300 initializes chipset 310 to generate key request 322 using key logic 320 (FIG. 1 ), as further illustrated with reference to FIG. 4 .
[0033] As illustrated with reference to FIG. 4 , key logic 320 includes a first block cipher 322, which receives cipher text (G) 302 from OEM 300 during initialization of chipset 310. As illustrated, key logic 320 decrypts cipher text G 302 using chip secret key 250 in order to form chip ID 240. However, as part of the initialization process, OEM 300 initially generates random cipher text G 302, which is to include chip ID 240, at least one private key assigned to chipset 310 and a private key digital certificate. However, as part of the initialization process, the initial cipher text merely includes random data in an encrypted format. Accordingly, as part of the initialization process, cryptographic block 322, following decryption of cipher text G 302, produces a random chip ID, a random private key and a random digital certificate.
[0034] Subsequently, OEM sends request 352 to key request logic 350. Representatively, key request logic 350 directs block cipher 336 to generate a key update request (Rkey) 340. In one embodiment, key update request 340 is formed by encrypting random chip ID 240, chip secret key 250 and a pad value 332 to preserve privacy. In one embodiment a public key crypto-system is used to encrypt the information using a public key of a trusted key distribution facility, such as KDF 270 of FIG. 2 .
[0035] Once the key update request is received by OEM 300, OEM 300 signs random cipher text G 302 with a private key of the OEM (KOEM) to produce a digital signature (S(G)). As known to those skilled in the art, a digital signature represents a digital code that can be attached to an electronically transmitted message that uniquely identifies the sender of the message for security purposes. Once signed, OEM sends key request 322, signature S(G) and random cipher text G 302 to KDF 270, as further illustrated with reference to FIG. 5 .
[0036] As illustrated with reference to FIG. 5 , KDF 270 initially verifies S(G) using the OEM's public key (POEM) If the received digital signature is invalid, the request is ignored, otherwise, KDF 270, using request verification logic 272, decrypts chip secret key 250 and random chip ID within key request 322 using a private key of the key distribution facility (KKDF). In one embodiment, request verification logic 272 computes chip ID 240 by decrypting chip secret key 250 using key (K1) 234. Subsequently, KDF 270 computes manufacturing information 232 by decrypting chip ID 240 using a cryptographic block and key (k1) 234. Representatively, manufacturer 200 also functions as KDF 270. However, a CA or other like trusted third party may perform the generation and assignment of private key 290.
[0037] Accordingly, logic 272 may verify that chip secret key 250 within key request 340 is authentic by decrypting chip secret key 250 to form chip ID 240 to derive decrypted manufacturing information and compare the manufacturing information with the initial or original manufacturing information used to form chip ID 240. If matching information is detected, control flow is provided to key generation logic 280. Otherwise, invalid request logic 274 may invalidate trust in OEM 300 and subsequently suspend trust, pending an investigation of an attempt to obtain keys for false chips.
[0038] Assuming the OEM is trusted, key generation logic 280 computes private key (PKc) 282. Subsequently, PKc 282 is provided to cryptographic block 286. In one embodiment block 286 performs cipher block chaining (CBC mode) encryption using a random number or initialization vector (IV) to produce a message C. As known to those skilled in the art, cipher block chaining (CBC) is a confidential mode whose encryption features the combining (chaining) of the plain text blocks with previous cipher blocks. In one embodiment, the message C or cipher text 292 is comprised of PKc 282, a digital key certificate and chip ID 240, which are encrypted using chip secret key 250. Once formed, cipher text 292, along with initialization vector 294, are transmitted to OEM 300.
[0039] Referring again to FIG. 2 , OEM 300 stores cipher text C 292 and initialization vector 292 within off-chip persistent memory of the system. Representatively, the off-chip persistent memory is flash memory. Once the cipher text 292 and IV 294 are stored, OEM reinitializes chipset 310 by providing chipset 310 with cipher text 292 during, for example, initial system boot. Once received, key logic 320 once again decrypts cipher text C in order to form chip ID 240, a digital key certificate and the at least one private key. In one embodiment, the digital key certificate is used by chipset 310 during an authentication procedure to establish a secure authenticated channel, without disclosing the identity of chipset 310 (in those embodiments where each chip receives a unique sequence of non-unique keys, or uses an authentication protocol that does not establish identity).
[0040] As known to those skilled in the art, a digital certificate represents an attachment to an electronic message used for security purposes. Accordingly, an individual wishing to send an encrypted message applies for a digital certificate from a certificate authority (CA). As described herein, a CA is a trusted third-party organization or company that issues digital certificates used to create digital signature and public-private key pairs. Hence, attachment of a digital certificate to an encrypted message enables a recipient of the encrypted message, or cipher text, to verify that the sender of the cipher text is an authenticated, or trusted, individual. Procedural methods for implementing one or more of the above-mentioned embodiments are now described.
Operation
[0041] FIG. 6 is a flowchart illustrating a method 400 for installing a chip secret key within a manufactured chip to enable the manufactured chip to receive at least one assigned private key to enable the manufactured chip to perform an authentication procedure to establish a secure authenticated channel, in accordance with one embodiment. At process block 402, a chip secret key is programmed into a manufactured chip. At process block 422, the manufactured chip is sent to an original equipment manufacturer (OEM). Subsequently, at process block 430, at least one private key is generated for the manufactured chip according to a received key update request. In one embodiment, method 400 approximately describes private key distribution, as illustrated with reference to FIGS. 2-5 .
[0042] FIG. 7 is a flowchart illustrating a method 410 for programming the chip secret key into a manufactured chip, in accordance with one embodiment. At process block 412, unique identification (ID) information is gathered for the manufactured chip. In one embodiment, the identification information includes a wafer serial number of a wafer from which the manufactured chip is formed, as well as an X,Y coordinate location of the manufactured chip within the wafer. However, those skilled in the art will recognize that identification information may be generated from a wide array of sources in order to uniquely identify the manufactured chip.
[0043] At process block 414, the identification information is encrypted using a first key to form a chip ID for the manufactured chip, for example, as illustrated with reference to FIG. 3 , which depicts secret key logic 230 of manufacturer 200 of FIG. 2 , in accordance with one embodiment. At process block 416, the chip ID is encrypted using a second key to form the chip secret key. Once formed, at process block 418, the chip secret key is stored within fuses of the manufactured chip. Once stored, at process block 420, selected chip fuses of the manufactured chip are blown in order to prohibit reading of the chip fuses to disclose the chip secret key.
[0044] FIG. 8 is a flowchart illustrating a method 440 for generating the at least one private key of process block 430, in accordance with one embodiment. At process block 442, a key update request is received from the system OEM. Once received, at process block 444, the key update request is authenticated. At process block 468, if the key update request is authentic, process block 470 is performed. Otherwise, the key update request is disregarded and trust of the OEM is temporarily suspended, pending an investigation. At process block 470, cipher text including the at least one private key assigned to the manufactured chip is generated. Once generated, at process block 490, the cipher text is sent to the system OEM.
[0045] FIG. 9 is a flowchart illustrating a method 450 for authenticating the received key update request of process block 444 of FIG. 8 , in accordance with one embodiment. At process block 452, a digital signature of the system OEM included within the key update request is verified. At process block 454, if the digital signature of the OEM is verified, process block 456 is performed. Otherwise, the key update request is ignored. At process block 456, the key update request is decrypted to form an alleged chip ID. At process block 458, the chip ID of the manufactured chip is compared to the alleged chip ID to verify that the chip ID matches the alleged chip ID. At process block 460, if the alleged chip ID is verified, process block 462 is performed. Otherwise, at process block 466, the received key update request is disregarded. At process block 462, the alleged chip ID is decrypted in order to form alleged chip manufacturing information (AMc).
[0046] Referring again to FIG. 3 , decryption of alleged chip ID (AIDc) using key K1 234 should yield manufacturing information Mc 232. Accordingly, at process block 264, the alleged manufacturing information AMc is compared to chip manufacturing information Mc. Accordingly when Mc is equal to AMc, verification of the received key update request is complete. Once the key update request is verified, control flow returns to process block 444 of FIG. 8 . Otherwise, at process block 466, the key update request is disregarded.
[0047] FIG. 10 is a flowchart illustrating a method 470 for generating the cipher text, including the at least one private key of process block 460, in accordance with one embodiment. At process block 482, a unique secret value is encrypted using the chip secret key to form a key vector. In one embodiment, the key vector includes a unique series of non-unique public/private key crypto-system keys. Hence, by using a unique series of non-unique keys, the series of keys assigned to a comprised devise can be revoked without interrupting innocent devices. For such innocent devices, such devices will continue performing authentication using the first non-revoked key in their series to continue operation. The use of non-unique keys for authentication preserves the privacy of the manufactured chip.
[0048] Accordingly, in one embodiment, the initial installation of the chip secret key enables insulation of an order of magnitude more keys that would normally be used by a conventional crypto-system using less unique bits in the chip than are required to install even one asymmetric private key pair. Referring again to FIG. 10 , at process block 484, all revoked keys from the key vector are removed to form a private key vector. At process block 486, the private key vector, the chip ID and digital certificates corresponding to the vector of private keys are encrypted using the chip secret key and an initialization vector to form the cipher text. Accordingly, in some embodiments, a first non-revoked private key and its corresponding digital certificate are used to form the cipher text instead of the private key vector and corresponding digital certificates.
[0049] Referring now to FIG. 11 , FIG. 11 is a flowchart illustrating a method 500 for initializing an integrated chip, including a preprogrammed chip secret key to generate a key update request in order to receive an assigned, at least one private key from a key distribution facility (KDF). At process block 502, an integrated chip within a system is initialized to generate a key update request using a preprogrammed chip secret key stored within the integrated chip. At process block 530, the key update request is transmitted to a key distribution facility.
[0050] Once transmitted, the key distribution facility will generate cipher text including at least one private key assigned to the integrated chip from the KDF. Subsequently, the integrated chip may use the private key to send a received encrypted digital content in the form of cipher text, which may be decrypted using a private key of the integrated chip once received. Accordingly, by using the assigned private key, the integrated chip is capable of forming a secure authenticated channel in order to receive protected content from content protection applications.
[0051] FIG. 12 is a flowchart illustrating a method 510 for initializing the integrated chip of process block 502 of FIG. 11 , in accordance with one embodiment. At process block 512, random cipher text is provided to the integrated chip. At process block 514, the integrated chip decrypts the random cipher text using the chip secret key to form a random ID, a random key and a random digital certificate. At process block 516, the OEM requests the integrated chip to generate the key update request. In response, at process block 518, the integrated chip encrypts the random ID, the chip secret key and a pad value using a public key of the KDF to form the key update request. At process block 520, the OEM attaches a digital certificate of the OEM and a signature of the random cipher text used in step 512 to the random cipher text.
[0052] FIG. 13 is a flowchart illustrating a method 550 for initializing an integrated chip once an assigned at least one private key is received for the integrated chip, in accordance with one embodiment. At process block 552, received cipher text is provided to the integrated chip during initial boot. Once provided to the chip, the integrated chip decrypts the received cipher text using the chip secret key to form a chip ID and the at least one private key. Subsequently, at process block 556, the integrated chip authenticates with a content protection application to receive protected content. In one embodiment, during authentication, the integrated chip also provides a received digital key certificate during the authentication protocol.
[0053] Representatively, since the digital key certificate associated with, for example, a key vector, may be shared by many platforms, the digital certificate cannot be used as a platform identity. Hence, content protection applications cannot identify the recipient of content. As such, content protection applications are able to verify that the integrated chip is an authorized recipient using the private key digital certificate. Hence, privacy is maintained by using the private key digital certificate during authentication protocols. In one embodiment, privacy is best preserved if access to received cipher text is limited to access during initial boot. Subsequently, following initial boot, access to received cipher text, including the at least one private key assigned to the chip, is disabled. However, if access to the received cipher text may not be disabled following initial boot, the integrated chip may be further requested to generate a second key update request.
[0054] Referring to FIG. 14 , FIG. 14 is a flowchart illustrating a method 560 for generating a second key update request, in accordance with one embodiment. At process block 560, the received cipher text is provided to the integrated chip. Subsequently, the integrated chip is requested to generate a key update request. At process block 566, the integrated chip encrypts the chip ID, the chip secret key and a pad value using a public key of the KDF to form a second key update request. At process block 568, the second key update request is transmitted to the KDF.
[0055] As such, the KDF will generate a new private key for the integrated chip to enable integrated chip to use the private key for future authentication with content protection applications. Accordingly, the process of replacing the initially assigned at least one private key to the integrated chip may be repeated as desired. Furthermore, this process may be repeated in order to preserve privacy of the integrated chip from applications that may be able to access the received cipher text after device initialization or initial system boot.
[0056] Accordingly, conventional systems generally install a unique asymmetric crypto-system private key within a device. Unfortunately, such private keys take more space (bits) than a symmetric secret key, which is a cost problem for integrated chips since the space required to store such asymmetric or symmetric keys is costly. Furthermore, once a device authenticates with a content protection application, user privacy is generally violated since the identity of the device is made known to the authentication application. Accordingly, by using multiple, non-unique public/private key pairs to provide privacy, implementation of such a scheme would require significantly more space to store multiple keys.
[0057] Accordingly, in one embodiment, the chip secret key enables the minimum possible number of fuse bits, such as enough to prevent a hacker from attacking the compromised device by merely guessing the information, but less information than required to store a secret key of a public/private key pair. Hence, in one embodiment, the device receives an arbitrary number of keys within a key vector. Subsequently, an identify of the device is only revealed to a trusted party that distributes keys to legitimate devices during system initialization. Hence, an identity of the device is not revealed during normal use or authentication to receive protected content.
[0058] It is to be understood that even though numerous characteristics and advantages of various embodiments of the present invention have been set forth in the foregoing description, together with details of the structure and function of various embodiments of the invention, this disclosure is illustrative only. In some cases, certain subassemblies are only described in detail with one such embodiment. Nevertheless, it is recognized and intended that such subassemblies may be used in other embodiments of the invention. Changes may be made in detail, especially matters of structure and management of parts within the principles of the embodiments of the present invention to the full extent indicated by the broad general meaning of the terms in which the appended claims are expressed.
[0059] Having disclosed exemplary embodiments and the best mode, modifications and variations may be made to the disclosed embodiments while remaining within the scope of the embodiments of the invention as defined by the following claims.
Claims
What is claimed is:
1. A method comprising:
programming a chip secret key into a manufactured chip;
sending the manufactured chip to a system original equipment manufacturer (OEM); and
generating at least one private key for the manufactured chip in response to a received key update request, issued by the manufactured chip, if the received key update request is authenticated, to enable authentication of the manufactured chip without disclosure of the private key or any unique device identification information of the manufactured chip,
wherein the key update request is issued by the manufactured chip in response to chip initialization.
2. The method of claim 1, wherein prior to programming the chip, the method comprises:
gathering unique identification (ID) information of the manufactured chip;
encrypting the identification information using a first key to form a chip ID for the manufactured chip; and
encrypting the chip ID using a second key to form the chip secret key.
3. The method of claim 2, wherein the unique identification information includes a wafer serial number of a wafer from which the chip is formed and an X,Y coordinate location of the manufactured chip within the wafer.
4. The method of claim 1, wherein programming the chip secret key comprises:
storing the chip secret key within chip fuses of the manufactured chip; and
blowing selected fuses of the manufactured chip to prevent unauthorized access to the chip secret key.
5. The method of claim 1, wherein generating the private key further comprises:
receiving the key update request from the system OEM;
authenticating the received key update request;
generating cipher text including the at least one private key for the manufactured chip if the key update request is authentic; and
sending the cipher text to the system OEM.
6. The method of claim 5, wherein authenticating the received key update request comprises:
verifying a digital signature of the system OEM included within the key update request;
decrypting the key update request to form a decrypted chip ID if the digital signature of the OEM is verified;
verifying that the chip ID of the manufactured chip matches the decrypted chip ID; and
disregarding the received key update request if the decrypted chip ID is not verified.
7. The method of claim 5, wherein generating the cipher text comprises:
generating a key vector including the at least one private key.
8. An article of manufacture including a computer readable storage medium having stored thereon instructions which may be used to program a system to perform a method, comprising:
programming a chip secret key into a manufactured chip;
sending the manufactured chip to a system original equipment manufacturer (OEM); and
generating at least one private key for the manufactured chip in response to a received key update request, issued by the manufactured chip, if the received key update request is authenticated, to enable authentication of the manufactured chip without disclosure of the private key or any unique device identification information of the manufactured chip,
wherein the key update request is issued by the manufactured chip in response to chip initialization.
9. The article of manufacture of claim 8, wherein prior to programming the chip, the method comprises:
gathering unique identification (ID) information of the manufactured chip;
encrypting the identification information using a first key to form a chip ID for the manufactured chip; and
encrypting the chip ID using a second key to form the chip secret key.
10. The article of manufacture of claim 8, wherein generating the private further comprises:
receiving the key update request from the system OEM;
authenticating the received key update request;
generating cipher text including the at least one private key for the manufactured chip if the key update request is authentic; and
sending the cipher text to the system OEM.
11. The article of manufacture of claim 8, wherein authenticating the received key update request comprises:
verifying a digital signature of the system OEM included within the key update request;
decrypting the key update request to form a decrypted chip ID if the digital signature of the OEM is verified;
verifying that the chip ID of the manufactured chip matches the decrypted chip ID; and
disregarding the received key update request if the decrypted chip ID is not verified.
12. An integrated chip, comprising: key request logic to generate a key update request using a preprogrammed chip secret key stored within the integrated chip to receive at least one private key from a key distribution facility (KDF) if the key update request is authenticated by the KDF; and authentication logic to perform authentication with a content protection application to receive protected content using a received digital certificate to avoid disclosing the identity of the integrated chip during the authentication; and a first cryptographic block to decrypt received initialization cipher text using the chip secret key to form a chip ID, the at least one private key and a digital certificate.
13. The chip of claim 12, further comprising:
a first cryptographic block to decrypt received random cipher text using the chip secret key to form a random ID, a random private key and a random digital certificate; and
a second cryptographic block to encrypt the random ID, the chip secret key and a pad value using a public key of the KDF to form the key update request.
14. The integrated chip of claim 12, wherein:
the initialization cipher text includes a key vector including a series of non-unique private keys.
Patent Citations (367)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US3699532(A) | 1972-10-01 | Schaffer et al. | Applicant |
| US3996449(A) | 1976-12-01 | Attanasio et al. | Applicant |
| US4037214(A) | 1977-07-01 | Birney et al. | Applicant |
| US4162536(A) | 1979-07-01 | Morley | Applicant |
| US4207609(A) | 1980-06-01 | Luiz et al. | Applicant |
| US4247905(A) | 1981-01-01 | Yoshida et al. | Applicant |
| US4276594(A) | 1981-06-01 | Morley | Applicant |
| US4278837(A) | 1981-07-01 | Best | Applicant |
| US4307447(A) | 1981-12-01 | Provanzano et al. | Applicant |
| US4319233(A) | 1982-03-01 | Matsuoka et al. | Applicant |
| US4319323(A) | 1982-03-01 | Ermolovich et al. | Applicant |
| US4347565(A) | 1982-08-01 | Kaneda et al. | Applicant |
| US4366537(A) | 1982-12-01 | Heller et al. | Applicant |
| US4403283(A) | 1983-09-01 | Myntti et al. | Applicant |
| US4419724(A) | 1983-12-01 | Branigin et al. | Applicant |
| US4430709(A) | 1984-02-01 | Schleupen et al. | Applicant |
| US4521852(A) | 1985-06-01 | Guttag | Applicant |
| US4529870(A) | 1985-07-01 | Chaum | Applicant |
| US4571672(A) | 1986-02-01 | Hatada et al. | Applicant |
| US4621318(A) | 1986-11-01 | Maeda | Applicant |
| US4759064(A) | 1988-07-01 | Chaum | Applicant |
| US4795893(A) | 1989-01-01 | Ugon | Applicant |
| US4802084(A) | 1989-01-01 | Ikegaya et al. | Applicant |
| US4825052(A) | 1989-04-01 | Chemin et al. | Applicant |
| US4843541(A) | 1989-06-01 | Bean et al. | Applicant |
| US4907270(A) | 1990-03-01 | Hazard | Applicant |
| US4907272(A) | 1990-03-01 | Hazard | Applicant |
| US4910774(A) | 1990-03-01 | Barakat | Applicant |
| US4974159(A) | 1990-11-01 | Hargrove et al. | Applicant |
| US4975836(A) | 1990-12-01 | Hirosawa et al. | Applicant |
| US5007082(A) | 1991-04-01 | Cummins | Applicant |
| US5022077(A) | 1991-06-01 | Bealkowski et al. | Applicant |
| US5075842(A) | 1991-12-01 | Lai | Applicant |
| US5079737(A) | 1992-01-01 | Hackbarth | Applicant |
| US5187802(A) | 1993-02-01 | Inoue et al. | Applicant |
| US5230069(A) | 1993-07-01 | Brelsford et al. | Applicant |
| US5237616(A) | 1993-08-01 | Abraham et al. | Applicant |
| US5255379(A) | 1993-10-01 | Melo | Applicant |
| US5287363(A) | 1994-02-01 | Wolf et al. | Applicant |
| US5293424(A) | 1994-03-01 | Hotley et al. | Applicant |
| US5295251(A) | 1994-03-01 | Wakui et al. | Applicant |
| US5317705(A) | 1994-05-01 | Gannon et al. | Applicant |
| US5319760(A) | 1994-06-01 | Mason et al. | Applicant |
| US5361375(A) | 1994-11-01 | Ogi | Applicant |
| US5386552(A) | 1995-01-01 | Garney | Applicant |
| US5421006(A) | 1995-05-01 | Jablon et al. | Applicant |
| US5434999(A) | 1995-07-01 | Goire et al. | Applicant |
| US5437033(A) | 1995-07-01 | Inoue et al. | Applicant |
| US5442645(A) | 1995-08-01 | Ugon et al. | Applicant |
| US5455909(A) | 1995-10-01 | Blomgren et al. | Applicant |
| US5459867(A) | 1995-10-01 | Adams et al. | Applicant |
| US5459869(A) | 1995-10-01 | Spilo | Applicant |
| US5469557(A) | 1995-11-01 | Salt et al. | Applicant |
| US5473692(A) | 1995-12-01 | Davis | Applicant |
| US5479509(A) | 1995-12-01 | Ugon | Applicant |
| US5504922(A) | 1996-04-01 | Seki et al. | Applicant |
| US5506975(A) | 1996-04-01 | Onodera | Applicant |
| US5511217(A) | 1996-04-01 | Nakajima et al. | Applicant |
| US5515441(A) | 1996-05-01 | Faucher | Applicant |
| US5522075(A) | 1996-05-01 | Robinson et al. | Applicant |
| US5528231(A) | 1996-06-01 | Patarin | Applicant |
| US5533126(A) | 1996-07-01 | Hazard et al. | Applicant |
| US5555385(A) | 1996-09-01 | Osisek | Applicant |
| US5555414(A) | 1996-09-01 | Hough et al. | Applicant |
| US5560013(A) | 1996-09-01 | Scalzi et al. | Applicant |
| US5564040(A) | 1996-10-01 | Kubala | Applicant |
| US5566323(A) | 1996-10-01 | Ugon | Applicant |
| US5568552(A) | 1996-10-01 | Davis | Applicant |
| US5574936(A) | 1996-11-01 | Ryba et al. | Applicant |
| US5582717(A) | 1996-12-01 | Di Santo | Applicant |
| US5604805(A) | 1997-02-01 | Brands | Applicant |
| US5606617(A) | 1997-02-01 | Brands | Applicant |
| US5615263(A) | 1997-03-01 | Takahashi | Applicant |
| US5628022(A) | 1997-05-01 | Ueno et al. | Applicant |
| US5628023(A) | 1997-05-01 | Bryant et al. | Applicant |
| US5631961(A) | 1997-05-01 | Mills et al. | Applicant |
| US5633929(A) | 1997-05-01 | Kaliski, Jr. | Applicant |
| US5657445(A) | 1997-08-01 | Pearce | Applicant |
| US5668971(A) | 1997-09-01 | Neufeld | Applicant |
| US5680547(A) | 1997-10-01 | Chang | Applicant |
| US5684948(A) | 1997-11-01 | Johnson et al. | Applicant |
| US5699431(A) | 1997-12-01 | Van Oorschot et al. | Applicant |
| US5706469(A) | 1998-01-01 | Kobayashi | Applicant |
| US5717903(A) | 1998-02-01 | Bonola | Applicant |
| US5720609(A) | 1998-02-01 | Pfefferle | Applicant |
| US5721222(A) | 1998-02-01 | Bernstein et al. | Applicant |
| US5724425(A) | 1998-03-01 | Chang et al. | Applicant |
| US5729760(A) | 1998-03-01 | Poisner | Applicant |
| US5737604(A) | 1998-04-01 | Miller et al. | Applicant |
| US5737760(A) | 1998-04-01 | Grimmer, Jr. et al. | Applicant |
| US5740178(A) | 1998-04-01 | Jacks et al. | Applicant |
| US5752046(A) | 1998-05-01 | Oprescu et al. | Applicant |
| US5757918(A) | 1998-05-01 | Hopkins et al. | Applicant |
| US5757919(A) | 1998-05-01 | Herbert et al. | Applicant |
| US5764969(A) | 1998-06-01 | Kahle | Applicant |
| US5771291(A) | 1998-06-01 | Newton et al. | Applicant |
| US5796835(A) | 1998-08-01 | Saada | Applicant |
| US5796845(A) | 1998-08-01 | Serikawa et al. | Applicant |
| US5805712(A) | 1998-09-01 | Davis | Applicant |
| US5809546(A) | 1998-09-01 | Greenstein et al. | Applicant |
| US5815665(A) | 1998-09-01 | Teper et al. | Applicant |
| US5825875(A) | 1998-10-01 | Ugon | Applicant |
| US5825880(A) | 1998-10-01 | Sudia et al. | Applicant |
| US5835594(A) | 1998-11-01 | Albrecht et al. | Applicant |
| US5844986(A) | 1998-12-01 | Davis | Applicant |
| US5852717(A) | 1998-12-01 | Bhide et al. | Applicant |
| US5854913(A) | 1998-12-01 | Goetz et al. | Applicant |
| US5857021(A) | 1999-01-01 | Kataoka et al. | Applicant |
| US5867577(A) | 1999-02-01 | Patarin | Applicant |
| US5872994(A) | 1999-02-01 | Akiyama et al. | Applicant |
| US5890189(A) | 1999-03-01 | Nozue et al. | Applicant |
| US5900606(A) | 1999-05-01 | Rigal | Applicant |
| US5901225(A) | 1999-05-01 | Ireton et al. | Applicant |
| US5903752(A) | 1999-05-01 | Dingwall et al. | Applicant |
| US5919257(A) | 1999-07-01 | Trostle | Applicant |
| US5924094(A) | 1999-07-01 | Sutter | Applicant |
| US5935242(A) | 1999-08-01 | Madany et al. | Applicant |
| US5935247(A) | 1999-08-01 | Pai et al. | Applicant |
| US5937063(A) | 1999-08-01 | Davis | Applicant |
| US5944821(A) | 1999-08-01 | Angelo | Applicant |
| US5953502(A) | 1999-09-01 | Helbig, Sr. | Applicant |
| US5956408(A) | 1999-09-01 | Arnold | Applicant |
| US5970147(A) | 1999-10-01 | Davis et al. | Applicant |
| US5978475(A) | 1999-11-01 | Schneier et al. | Applicant |
| US5978481(A) | 1999-11-01 | Ganesan et al. | Applicant |
| US5987557(A) | 1999-11-01 | Ebrahim | Applicant |
| US6014745(A) | 2000-01-01 | Ashe | Applicant |
| US6032260(A) | 2000-02-01 | Sasmazel et al. | Applicant |
| US6032261(A) | 2000-02-01 | Hulyalkar | Applicant |
| US6035374(A) | 2000-03-01 | Panwar et al. | Applicant |
| US6036061(A) | 2000-03-01 | O'Donnell | Applicant |
| US6036601(A) | 2000-03-01 | Heckel | Applicant |
| US6038322(A) | 2000-03-01 | Harkins | Applicant |
| US6044478(A) | 2000-03-01 | Green | Applicant |
| US6055637(A) | 2000-04-01 | Hudson et al. | Applicant |
| US6058478(A) | 2000-05-01 | Davis | Applicant |
| US6061794(A) | 2000-05-01 | Angelo | Applicant |
| US6075938(A) | 2000-06-01 | Bugnion et al. | Applicant |
| US6078667(A) | 2000-06-01 | Johnson | Applicant |
| US6085296(A) | 2000-07-01 | Karkhanis et al. | Applicant |
| US6088262(A) | 2000-07-01 | Nasu | Applicant |
| US6092095(A) | 2000-07-01 | Maytal | Applicant |
| US6093213(A) | 2000-07-01 | Favor et al. | Applicant |
| US6101584(A) | 2000-08-01 | Satou et al. | Applicant |
| US6108644(A) | 2000-08-01 | Goldschlag et al. | Applicant |
| US6115816(A) | 2000-09-01 | Davis | Applicant |
| US6125430(A) | 2000-09-01 | Noel et al. | Applicant |
| US6131166(A) | 2000-10-01 | Wong-Isley | Applicant |
| US6138239(A) | 2000-10-01 | Veil. | Applicant |
| US6148379(A) | 2000-11-01 | Schimmel | Applicant |
| US6151676(A) | 2000-11-01 | Cuccia et al. | Applicant |
| US6154841(A) | 2000-11-01 | Oishi | Applicant |
| US6158546(A) | 2000-12-01 | Hanson et al. | Applicant |
| US6173417(B1) | 2001-01-01 | Merrill | Applicant |
| US6175924(B1) | 2001-01-01 | Arnold | Applicant |
| US6175925(B1) | 2001-01-01 | Nardone et al. | Applicant |
| US6178509(B1) | 2001-01-01 | Nardone | Applicant |
| US6182089(B1) | 2001-01-01 | Ganapathy et al. | Applicant |
| US6185316(B1) | 2001-02-01 | Buffam | Applicant |
| US6188257(B1) | 2001-02-01 | Buer | Applicant |
| US6192455(B1) | 2001-02-01 | Bogin et al. | Applicant |
| US6199152(B1) | 2001-03-01 | Kelly et al. | Applicant |
| US6205550(B1) | 2001-03-01 | Nardone et al. | Applicant |
| US6212635(B1) | 2001-04-01 | Reardon | Applicant |
| US6222923(B1) | 2001-04-01 | Schwenk | Applicant |
| US6246771(B1) | 2001-06-01 | Stanton et al. | Applicant |
| US6249872(B1) | 2001-06-01 | Wildgrube et al. | Applicant |
| US6252650(B1) | 2001-06-01 | Nakamura | Applicant |
| US6269392(B1) | 2001-07-01 | Cotichini et al. | Applicant |
| US6272533(B1) | 2001-08-01 | Browne et al. | Applicant |
| US6272637(B1) | 2001-08-01 | Little et al. | Applicant |
| US6275933(B1) | 2001-08-01 | Fine et al. | Applicant |
| US6278782(B1) | 2001-08-01 | Ober et al. | Examiner |
| US6282650(B1) | 2001-08-01 | Davis | Applicant |
| US6282651(B1) | 2001-08-01 | Ashe | Applicant |
| US6282657(B1) | 2001-08-01 | Kaplan et al. | Applicant |
| US6292874(B1) | 2001-09-01 | Barnett | Applicant |
| US6301646(B1) | 2001-10-01 | Hostetter | Applicant |
| US6308270(B1) | 2001-10-01 | Guthery et al. | Applicant |
| US6314409(B2) | 2001-11-01 | Schneck et al. | Applicant |
| US6321314(B1) | 2001-11-01 | Van Dyke | Applicant |
| US6327652(B1) | 2001-12-01 | England et al. | Applicant |
| US6330670(B1) | 2001-12-01 | England et al. | Applicant |
| US6339815(B1) | 2002-01-01 | Feng | Applicant |
| US6339816(B1) | 2002-01-01 | Bausch | Applicant |
| US6357004(B1) | 2002-03-01 | Davis | Applicant |
| US6363485(B1) | 2002-03-01 | Adams | Applicant |
| US6374286(B1) | 2002-04-01 | Gee et al. | Applicant |
| US6374317(B1) | 2002-04-01 | Ajanovic et al. | Applicant |
| US6378068(B1) | 2002-04-01 | Foster | Applicant |
| US6378072(B1) | 2002-04-01 | Collins et al. | Applicant |
| US6389403(B1) | 2002-05-01 | Dorak, Jr. | Applicant |
| US6389537(B1) | 2002-05-01 | Davis et al. | Applicant |
| US6397242(B1) | 2002-05-01 | Devine et al. | Applicant |
| US6397379(B1) | 2002-05-01 | Yates, Jr. et al. | Applicant |
| US6411715(B1) | 2002-06-01 | Liskov et al. | Applicant |
| US6412035(B1) | 2002-06-01 | Webber | Applicant |
| US6421702(B1) | 2002-07-01 | Gulick | Applicant |
| US6435416(B1) | 2002-08-01 | Slassi | Applicant |
| US6445797(B1) | 2002-09-01 | McGough et al. | Applicant |
| US6463535(B1) | 2002-10-01 | Drews et al. | Applicant |
| US6463537(B1) | 2002-10-01 | Tello | Applicant |
| US6473508(B1) | 2002-10-01 | Young et al. | Applicant |
| US6473800(B1) | 2002-10-01 | Jerger et al. | Applicant |
| US6496847(B1) | 2002-12-01 | Bugnion et al. | Applicant |
| US6499123(B1) | 2002-12-01 | McFarland et al. | Applicant |
| US6505279(B1) | 2003-01-01 | Phillips et al. | Applicant |
| US6507904(B1) | 2003-01-01 | Ellison et al. | Applicant |
| US6529909(B1) | 2003-03-01 | Bowman-Amuah | Applicant |
| US6535988(B1) | 2003-03-01 | Poisner | Applicant |
| US6557104(B2) | 2003-04-01 | Vu et al. | Applicant |
| US6560627(B1) | 2003-05-01 | McDonald et al. | Applicant |
| US6609199(B1) | 2003-08-01 | DeTreville | Applicant |
| US6615278(B1) | 2003-09-01 | Curtis | Applicant |
| US6633963(B1) | 2003-10-01 | Ellison et al. | Applicant |
| US6633981(B1) | 2003-10-01 | Davis | Applicant |
| US6651171(B1) | 2003-11-01 | England et al. | Applicant |
| US6678825(B1) | 2004-01-01 | Ellison et al. | Applicant |
| US6684326(B1) | 2004-01-01 | Cromer et al. | Applicant |
| US6711263(B1) | 2004-03-01 | Nordenstam et al. | Applicant |
| US6738904(B2) | 2004-05-01 | Linnartz et al. | Applicant |
| US6792113(B1) | 2004-09-01 | Ansell et al. | Applicant |
| US6826616(B2) | 2004-11-01 | Larson et al. | Applicant |
| US6987853(B2) | 2006-01-01 | Uner | Applicant |
| US6988250(B1) | 2006-01-01 | Proudler et al. | Applicant |
| US7028149(B2) | 2006-04-01 | Grawrock et al. | Applicant |
| US7133990(B2) | 2006-11-01 | Link et al. | Applicant |
| US7165181(B2) | 2007-01-01 | Brickell | Applicant |
| US7178030(B2) | 2007-02-01 | Scheidt et al. | Applicant |
| US7181620(B1) | 2007-02-01 | Hur | Examiner |
| US7216110(B1) | 2007-05-01 | Ogg et al. | Applicant |
| US7233666(B2) | 2007-06-01 | Lee et al. | Applicant |
| US7299500(B1) | 2007-11-01 | Klebe et al. | Applicant |
| US7526651(B2) | 2009-04-01 | Arditti Modiano et al. | Applicant |
| US2001/0011267(A1) | 2001-08-01 | Kihara et al. | Applicant |
| US2001/0021969(A1) | 2001-09-01 | Burger et al. | Applicant |
| US2001/0027511(A1) | 2001-10-01 | Wakabayashi et al. | Applicant |
| US2001/0027527(A1) | 2001-10-01 | Khidekel et al. | Applicant |
| US2001/0037450(A1) | 2001-11-01 | Metlitski et al. | Applicant |
| US2001/0044786(A1) | 2001-11-01 | Ishibashi | Applicant |
| US2001/0044886(A1) | 2001-11-01 | Cassagnol et al. | Applicant |
| US2002/0004900(A1) | 2002-01-01 | Patel | Applicant |
| US2002/0007456(A1) | 2002-01-01 | Peinado et al. | Applicant |
| US2002/0012432(A1) | 2002-01-01 | England et al. | Applicant |
| US2002/0023032(A1) | 2002-02-01 | Pearson et al. | Applicant |
| US2002/0044567(A1) | 2002-04-01 | Viot et al. | Applicant |
| US2002/0048369(A1) | 2002-04-01 | Ginter et al. | Applicant |
| US2002/0065136(A1) | 2002-05-01 | Day | Applicant |
| US2002/0080190(A1) | 2002-06-01 | Hamann et al. | Applicant |
| US2002/0147916(A1) | 2002-10-01 | Strongin et al. | Applicant |
| US2002/0166053(A1) | 2002-11-01 | Wilson | Applicant |
| US2002/0166061(A1) | 2002-11-01 | Falik et al. | Applicant |
| US2002/0169717(A1) | 2002-11-01 | Challener | Applicant |
| US2002/0178354(A1) | 2002-11-01 | Ogg et al. | Applicant |
| US2002/0178534(A1) | 2002-12-01 | Massaro | Applicant |
| US2002/0198302(A1) | 2002-12-01 | Rouse et al. | Applicant |
| US2003/0002668(A1) | 2003-01-01 | Graunke et al. | Applicant |
| US2003/0018892(A1) | 2003-01-01 | Tello | Applicant |
| US2003/0037237(A1) | 2003-02-01 | Abgrall et al. | Applicant |
| US2003/0041250(A1) | 2003-02-01 | Proudler | Applicant |
| US2003/0074548(A1) | 2003-04-01 | Cromer et al. | Applicant |
| US2003/0105718(A1) | 2003-06-01 | Hurtado et al. | Applicant |
| US2003/0112008(A1) | 2003-06-01 | Hennig | Applicant |
| US2003/0114144(A1) | 2003-06-01 | Minemura | Applicant |
| US2003/0115453(A1) | 2003-06-01 | Grawrock | Applicant |
| US2003/0126442(A1) | 2003-07-01 | Glew et al. | Applicant |
| US2003/0126453(A1) | 2003-07-01 | Glew et al. | Applicant |
| US2003/0159056(A1) | 2003-08-01 | Cromer et al. | Applicant |
| US2003/0182584(A1) | 2003-09-01 | Banes et al. | Applicant |
| US2003/0188156(A1) | 2003-10-01 | Yasala et al. | Applicant |
| US2003/0188179(A1) | 2003-10-01 | Challener et al. | Applicant |
| US2003/0195857(A1) | 2003-10-01 | Acquisti | Applicant |
| US2003/0196085(A1) | 2003-10-01 | Lampson et al. | Applicant |
| US2003/0231328(A1) | 2003-12-01 | Chapin et al. | Applicant |
| US2003/0235175(A1) | 2003-12-01 | Naghiam et al. | Applicant |
| US2004/0003324(A1) | 2004-01-01 | Uhlig et al. | Applicant |
| US2004/0039924(A1) | 2004-02-01 | Baldwin et al. | Applicant |
| US2004/0064694(A1) | 2004-04-01 | Lee et al. | Applicant |
| US2004/0103281(A1) | 2004-05-01 | Brickell | Applicant |
| US2004/0107286(A1) | 2004-06-01 | Larson et al. | Applicant |
| US2004/0117539(A1) | 2004-06-01 | Bennett et al. | Applicant |
| US2004/0123288(A1) | 2004-06-01 | Bennett et al. | Applicant |
| US2004/0240667(A1) | 2004-12-01 | Lee et al. | Applicant |
| US2004/0260926(A1) | 2004-12-01 | Arditti Modiano et al. | Applicant |
| US2005/0010535(A1) | 2005-01-01 | Camenisch | Applicant |
| US2005/0081038(A1) | 2005-04-01 | Arditti Modiano et al. | Applicant |
| US2005/0100161(A1) | 2005-05-01 | Husemann et al. | Applicant |
| US2005/0114682(A1) | 2005-05-01 | Zimmer et al. | Applicant |
| US2005/0154890(A1) | 2005-07-01 | Vembu | Applicant |
| US2005/0283586(A1) | 2005-12-01 | Mondal et al. | Applicant |
| US2006/0013399(A1) | 2006-01-01 | Brickell et al. | Applicant |
| US2006/0013400(A1) | 2006-01-01 | Sutton | Applicant |
| US2006/0013402(A1) | 2006-01-01 | Sutton et al. | Applicant |
| US2006/0020786(A1) | 2006-01-01 | Helms et al. | Applicant |
| US2006/0117181(A1) | 2006-06-01 | Brickell | Applicant |
| US2007/0100913(A1) | 2007-05-01 | Sumner et al. | Applicant |
| US2007/0192829(A1) | 2007-08-01 | Ford | Examiner |
| CN1985466 | 2007-06-01 | Applicant | |
| CN101019368 | 2007-08-01 | Applicant | |
| CN101019369 | 2007-08-01 | Applicant | |
| DE4217444 | 1992-12-01 | Applicant | |
| DE10218835(A1) | 2002-04-01 | Applicant | |
| DE112005001666(T5) | 2007-05-01 | Applicant | |
| DE112005001672(T) | 2007-05-01 | Applicant | |
| DE112005001654(T5) | 2007-11-01 | Applicant | |
| EP473913 | 1992-03-01 | Applicant | |
| EP492692 | 1992-07-01 | Applicant | |
| EP600112 | 1994-06-01 | Applicant | |
| EP602867 | 1994-06-01 | Applicant | |
| EP877314 | 1998-11-01 | Applicant | |
| EP892521 | 1999-01-01 | Applicant | |
| EP930567 | 1999-07-01 | Applicant | |
| EP961193 | 1999-12-01 | Applicant | |
| EP965902 | 1999-12-01 | Applicant | |
| EP1030237 | 2000-08-01 | Applicant | |
| EP1055989 | 2000-11-01 | Applicant | |
| EP1056014 | 2000-11-01 | Applicant | |
| EP1067470 | 2001-01-01 | Applicant | |
| EP1085396 | 2001-03-01 | Applicant | |
| EP1146715 | 2001-10-01 | Applicant | |
| EP1209563 | 2002-05-01 | Applicant | |
| EP1271277 | 2003-01-01 | Applicant | |
| EP1617587(A1) | 2006-01-01 | Applicant | |
| FR2620248 | 1989-03-01 | Applicant | |
| FR2700430 | 1994-07-01 | Applicant | |
| FR2714780 | 1995-07-01 | Applicant | |
| FR2742618 | 1997-06-01 | Applicant | |
| FR2752122 | 1998-02-01 | Applicant | |
| FR2763452 | 1998-11-01 | Applicant | |
| FR2830147 | 2003-03-01 | Applicant | |
| GB2439160 | 2007-12-01 | Applicant | |
| JP2000076139 | 2000-03-01 | Applicant | |
| JP2006293472 | 2006-10-01 | Applicant | |
| WO9524696 | 1995-09-01 | Applicant | |
| WO9729567 | 1997-08-01 | Applicant | |
| WO9812620 | 1998-03-01 | Applicant | |
| WO9834365 | 1998-08-01 | Applicant | |
| WO9844402 | 1998-10-01 | Applicant | |
| WO9905600 | 1999-02-01 | Applicant | |
| WO9918511 | 1999-04-01 | Applicant | |
| WO-9931842 | 1999-06-01 | Applicant | |
| WO99/65579 | 1999-12-01 | Applicant | |
| WO9965579 | 1999-12-01 | Applicant | |
| WO21238 | 2000-04-01 | Applicant | |
| WO-0049764 | 2000-08-01 | Applicant | |
| WO62232 | 2000-10-01 | Applicant | |
| WO-0069206 | 2000-11-01 | Applicant | |
| WO127723 | 2001-04-01 | Applicant | |
| WO127821 | 2001-04-01 | Applicant | |
| WO-0143476 | 2001-06-01 | Applicant | |
| WO-0163853 | 2001-08-01 | Applicant | |
| WO-0163954 | 2001-08-01 | Applicant | |
| WO163994 | 2001-08-01 | Applicant | |
| WO175564 | 2001-10-01 | Applicant | |
| WO175565 | 2001-10-01 | Applicant | |
| WO175595 | 2001-10-01 | Applicant | |
| WO201794 | 2002-01-01 | Applicant | |
| WO9909482 | 2002-01-01 | Applicant | |
| WO217555 | 2002-02-01 | Applicant | |
| WO-0245453 | 2002-06-01 | Applicant | |
| WO2060121 | 2002-08-01 | Applicant | |
| WO-0273928 | 2002-09-01 | Applicant | |
| WO2086684 | 2002-10-01 | Applicant | |
| WO3058412 | 2003-07-01 | Applicant | |
| WO-2006019614 | 2006-02-01 | Applicant | |
| WO-2006023151 | 2006-03-01 | Applicant | |
| WO-2006025952 | 2006-03-01 | Applicant |
Non-Patent Literature (78)
- Menezes, Vanstone, Oorschot: “Handbook of Applied Cryptography”, CRC Press LLC, USA 1997, pp. 405-406, 409-410, 433-435 and 576-580. XP002353062.Applicant
- ISR in related PCT application No. PCT/US2005/016559, mailed Dec. 8, 2005.Applicant
- Crawford, John , “Architecture of the Intel 80386”, Proceedings of the IEEE International Conference on Computer Design: VLSI in Computers and Processors (ICCD '83), (Oct. 6, 1986), 155-160.Applicant
- Fabry, R.S. , “Capability-Based Addressing”, Fabry, R.S., “Capability-Based Addressing,” Communications of the ACM, vol. 17, No. 7, (Jul. 1974),403-412.Applicant
- Frieder, Gideon , “The Architecture And Operational Characteristics of the VMX Host Machine”, The Architecture And Operational Characteristics of the VMX Host Machine, IEEE, (1982),9-16.Applicant
- HP Mobile Security Overview, “HP Mobile Security Overview”, (Sep. 2002),1-10.Applicant
- IBM Corporation, “IBM ThinkPad T30 Notebooks”, IBM Product Specification, located at www-1.ibm.com/services/files/cisco—t30—spec—sheet—070202.pdf, last visited Jun. 23, 2004,(Jul. 2, 2002),1-6.Applicant
- Intel Corporation, “Intel 82802AB/82802AC Firmware Hub (FWH)”, Intel Product Datasheet, Document No. 290658-004,(Nov. 2000),1-6, 17-28.Applicant
- Menezes, Alfred J., et al., “Handbook of Applied Cryptography”, CRC Press Series on Discrete Mathematics and its Applications, Boca Raton, FL, XP002165287, ISBN 0849385237,(Oct. 1996),403-405, 506-515, 570.Applicant
- Nanba, S. , et al., “VM/4: ACOS-4 Virtual Machine Architecture”, VM/4: ACOS-4 Virtual Machine Architecture, IEEE, (1985),171-178.Applicant
- RSA Security, “Hardware Authenticators”, www.rsasecurity.com/node.asp?id=1158, 1-2.Applicant
- RSA Security, “RSA SecurID Authenticators”, www.rsasecurity.com/products/securid/datasheets/SID—DS—0103.pdf, 1-2.Applicant
- RSA Security, “Software Authenticators”, www.srasecurity.com/node.asp?id=1313, 1-2.Applicant
- Schneier, Bruce , “Applied Cryptography: Protocols, Algorithm, and Source Code in C”, Wiley, John & Sons, Inc., XP002939871; ISBN 0471117099,(Oct. 1995),47-52.Applicant
- Schneier, Bruce , “Applied Cryptography: Protocols, Algorithm, and Source Code in C”, Wiley, John & Sons, Inc., XP002138607; ISBN 0471117099,(Oct. 1995),56-65.Applicant
- Schneier, Bruce , “Applied Cryptography: Protocols, Algorithms, and Source Code C”, Wiley, John & Sons, Inc., XP0021111449; ISBN 0471117099,(Oct. 1995),169-187.Applicant
- Schneier, Bruce , “Applied Cryptography: Protocols, Algorithms, and Source Code in C”, 2nd Edition; Wiley, John & Sons, Inc., XP002251738; ISBN 0471128457,(Nov. 1995),28-33; 176-177; 216-217; 461-473; 518-522.Applicant
- Berg, Cliff , “How Do I Create a Signed Applet?”, Dr. Dobb's Journal, (Aug. 1997),1-9.Applicant
- Brands, Stefan , “Restrictive Blinding of Secret-Key Certificates”, Springer-Verlag XP002201306, (1995),Chapter 3.Applicant
- Chien, Andrew A., et al., “Safe and Protected Execution for the Morph/AMRM Reconfigurable Processor”, 7th Annual IEEE Symposium, FCCM '99 Proceedings, XP010359180, ISBN 0-7695-0375-6, Los Alamitos, CA, (Apr. 21, 1999),209-221.Applicant
- Compaq Computer Corporation, et al., “Trusted Computing Platform Alliance (TCPA) Main Specification Version 1.1a”, (Dec. 2001),1-321.Applicant
- Coulouris, George , et al., “Distributed Systems, Concepts and Designs”, 2nd Edition, (1994),422-424.Applicant
- Davida, George I., et al., “Defending Systems Against Viruses through Cryptographic Authentication”, Proceedings of the Symposium on Security and Privacy, IEEE Comp. Soc. Press, ISBN 0-8186-1939-2,(May 1989).Applicant
- Goldberg, Robert P., “Survey of Virtual Machine Research”, Computer Magazine, (Jun. 1974),34-35.Applicant
- Gong, Li , et al., “Going Behond the Sandbox: An Overview of the New Security Architecture in the Java Development Kit 1.2”, Proceedings of the USENIX Symposium on Internet Technologies and Systems, Monterey, CA,(Dec. 1997).Applicant
- Gum, P. H., “System/370 Extended Architecture: Facilities for Virtual Machines”, IBM J. Research Development, vol. 27, No. 6, (Nov. 1983),530-544.Applicant
- Heinrich, Joe , “MIPS R4000 Microprocessor User's Manual, Second Edition”, Chapter 4 “Memory Management”, (Jun. 11, 1993),61-97.Applicant
- IBM, “Information Display Technique for a Terminate Stay Resident Program IBM Technical Disclosure Bulletin”, TDB-ACC-No. NA9112156, vol. 34, Issue 7A, (Dec. 1, 1991), 156-158.Applicant
- Intel, “IA-32 Intel Architecture Software Developer's Manual”, vol. 3: System Programming Guide, Intel Corporation—2003, 13-1 through 13-24.Applicant
- Intel, “Intel386 DX Microprocessor 32-Bit CHMOS Microprocessor With Integrated Memory Management”, (1995),5-56.Applicant
- Intel Corporation, “IA-64 System Abstraction Layer Specification”, Intel Product Specification, Order No. 245359-001, (Jan. 2000),1-112.Applicant
- Intel Corporation, “Intel IA-64 Architecture Software Developer's Manual”, vol. 2: IA-64 System Architecture, Order No. 245318-001, (Jan. 2000),i, ii, 5.1-5.3, 11.1-11.8, 11.23-11.26.Applicant
- Karger, Paul A., et al., “A VMM Security Kernal for the VAX Architecture”, Proceedings of the Symposium on Research in Security and Privacy, XP010020182, ISBN 0-8186-2060-9 Boxborough, MA, (May 7, 1990),2-19.Applicant
- Kashiwagi, Kazuhiko , et al., “Design and Implementation of Dynamically Reconstructing System Software”, Software Engineering Conference, Proceedings 1996 Asia-Pacific Seoul, South Korea Dec. 4-7, 1996, Los Alamitos, CA USA, IEEE Comput. Soc, US, ISBN 0-8186-7638-8,(1996).Applicant
- Lawton, Kevin , et al., “Running Multiple Operating Systems Concurrently on an IA32 PC Using Virtualization Techniques”, http://www.plex86.org/research/paper.txt, (Nov. 29, 1999),1-31.Applicant
- Luke, Jahn , et al., “Replacement Strategy for Aging Avionics Computers”, IEEE AES Systems Magazine, XP002190614,(Mar. 1999).Applicant
- Menezes, Oorschot , “Handbook of Applied Cryptography”, CRC Press LLC, USA XP002201307, (1997),475.Applicant
- Motorola, “M68040 User's Manual”, (1993),1-1 to 8-32.Applicant
- Richt, Stefan , et al., “In-Circuit-Emulator Wird Echtzeittauglich”, Elektronic, Franzis Verlag GMBH, Munchen, DE, vol. 40, No. 16, XP000259620,(100-103),Aug. 6, 1991.Applicant
- Robin, John S., et al., “Analysis of the Pentium's Ability to Support a Secure Virtual Machine Monitor”, Proceedings of the 9th USENIX Security Symposium, XP002247347, Denver, Colorado, (Aug. 14, 2000),1-17.Applicant
- Rosenblum, M. , “Virtual Platform: A Virtual Machine Monitor for Commodity PC”, Proceedings of the 11th Hotchips Conference, (Aug. 17, 1999),185-196.Applicant
- Saez, Sergio , et al., “A Hardware Scheduler for Complex Real-Time Systems”, Proceedings of the IEEE International Symposium on Industrial Electronics, XP002190615,(Jul. 1999),43-48.Applicant
- Sherwood, Timothy , et al., “Patchable Instruction ROM Architecture”, Department of Computer Science and Engineering, University of California, San Diego, La Jolla, CA, (Nov. 2001).Applicant
- Ateniese, Giuseppe , et al., “A Practical and Provably Secure Coalition-Resistant Group Signature Scheme”, Advances in Cryptology—CRYPTO2000, vol. 1880 of Lecture Notes in Computer Sciemce, Int'; Assoc for Crypt Res, Spring-Verlag, Berlin, Germany, (2000), 255-270.Applicant
- Chang, T.-W. , “Efficient Authentication Schemes Based on Group Certificate and Their Application on Mobile Communication Systems”, Thesis for Master of Science, Department of Electrical Engineering, National Cheng Kung University, Tainan, Taiwan, (Jun. 2003).Applicant
- Hall, Judith S., et al., “Virtualizing the VAX Architecture”, ACM SIGARCH Computer Architecture News, Proceedings of the 18th Annual International Symposium on Computer Architecture, vol. 19, Issue No. 3, (Apr. 1991), 10 pages.Applicant
- Hawthorne, W. M., “An Alternative to Public Key Encryption”, European Convention on Security and Detection, Found at: http://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=491615&isnumber=10615, (May 1995), 142-145.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Official Action in related U.S. Appl. No. 10/892,256 dated Sep. 29, 2008, with corresponding Reply to Official Action filed Dec. 24, 2008.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Official Action in related U.S. Appl. No. 10/892,280 dated Nov. 26, 2008.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Official Action in related U.S. Appl. No. 10/892,280 dated Sep. 12, 2007, with corresponding Reply to Official Action filed Jan. 24, 2008.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Final Official Action in related U.S. Appl. No. 10/892,280 dated May 14, 2008, with corresponding Reply to Final Official Action filed Jul. 9, 2008.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Official Action in related U.S. Appl. No. 10/892,256 dated Jul. 23, 2007, with corresponding Reply to Official Action filed Dec. 20, 2007.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Final Official Action in related U.S. Appl. No. 10/892,256 dated Apr. 1, 2008, with corresponding Reply to Final Official Action filed May 30, 2008, Advisory Action mailed on Jun. 16, 2008.Applicant
- Intel Corporation, PCT International Search Report and Written Opinion of the International Searching Authority, Application No. PCT/US2005/024486, mailed Sep. 18, 2006.Applicant
- Intel Corporation, PCT Preliminary Report on Patentability (Chapter 1 of the Patent Cooperation Treaty), Application No. PCT/US2005/024486, mailed Jan. 25, 2007.Applicant
- Intel Corporation, PCT International Search Report and Written Opinion of the International Searching Authority, Application No. PCT/US2005/024374, mailed Sep. 18, 2006.Applicant
- Intel Corporation, PCT Preliminary Report on Patentability (Chapter 1 of the Patent Cooperation Treaty), Application No. PCT/US2005/024374, mailed Jan. 25, 2007.Applicant
- Intel Corporation, PCT International Search Report and Written Opinion of the International Searching Authority, Application No. PCT/US2005/024251, mailed Oct. 6, 2005.Applicant
- Intel Corporation, PCT International Search Report and Written Opinion of the International Searching Authority, Application No. PCT/US2005/024253, mailed Sep. 18, 2006.Applicant
- Intel Corporation, PCT Preliminary Report on Patentability (Chapter 1 of the Patent Cooperation Treaty), Application No. PCT/US2005/024253, mailed Jan. 25, 2007.Applicant
- Intel Corporation, U.S. Patent and Trademark Office, Final Office Action dated Mar. 24, 2009 in related U.S. Appl. No. 10/892,256.Applicant
- Intel Corporation, U.S. Patent and Trademark Office, Office Action dated Jun. 15, 2009, with Reply to Office Action filed on Sep. 15, 2009, in related U.S. Appl. No. 10/892,265.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Official Action in related U.S. Appl. No. 10/892,265 dated Nov. 25, 2008, with corresponding Reply to Official Action filed Feb. 25, 2009.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Official Action in related U.S. Appl. No. 10/892,265 dated Sep. 12, 2007, with corresponding Reply to Official Action filed Jan. 24, 2008.Applicant
- Intel Corporation, U.S. Patent and Trademark Office Final Official Action in related U.S. Appl. No. 10/892,265 dated Apr. 17, 2008, with corresponding Reply to Final Official Action filed Jun. 17, 2008.Applicant
- Intel Corporation, Office Action for U.S. Appl. No. 10/185,123, dated Apr. 16, 2007, 10 pages.Applicant
- Intel Corporation, Office Action for U.S. Appl. No. 10/663,206, dated Apr. 19, 2007.Applicant
- Intel Corporation, Office Action for U.S. Appl. No. 10/814,569, dated Apr. 5, 2007, 5 pages.Applicant
- Intel Corporation, PCT Search Report for PCT/US2005/010156, dated Aug. 22, 2006, 6 pages.Applicant
- Intel Corporation, Non-Final Office Action mailed Jun. 2, 2009, U.S. Appl. No. 11/387,203, filed Mar. 22, 2006, First Named Inventor: Ernest Brickell.Applicant
- Intel Corporation, Final Office Action mailed Dec. 7, 2009, U.S. Appl. No. 11/387,203, filed Mar. 22, 2006.Applicant
- Intel Corporation, Notice of Allowance mailed Sep. 11, 2008, U.S. Appl. No. 10/866,252.Applicant
- Menezes, et al., “Handbook of Applied Cryptography”, CRC Press, LLC, pp. 321-322, 330-331, 388-390, 394-395, 397-398, 472, 515-516, 548-552, (1997).Applicant
- Menezes, et al., “Hash Functions and Data Integrity”, CRC Press Inc., 1997, Chapter 9.Applicant
- Rosenberg, Jonathan B., “How Debuggers Work (Algorithms, Data Structures, and Architecture”, Chapters 3 and 5 Hardware Debugger Facilities, Wiley Computer Publishing, United States, (1996), pp. 42-43, 95, 96 and 99.Applicant
- Schneier, Bruce, Applied Cryptography Second Edition, John Wiley & Sons, (1996), pp. 513-514.Applicant
- Intel Corporation, Office Action mailed Mar. 29, 2010, U.S. Appl. No. 11/387,203, 54 pages.Applicant
- Schneier, Bruce, “Applied Cryptography,” Wiley and Sons, (1996), p. 173.Applicant