Methods for secure enrollment and backup of personal identity credentials into electronic devices

- Apple

A method and system for securely enrolling personal identity credentials into personal identification devices. The system of the invention comprises the manufacturer of the device and an enrollment authority. The manufacturer is responsible for recording serial numbers or another unique identifier for each device that it produces, along with a self-generated public key for each device. The enrollment authority is recognized by the manufacturer or another suitable institution as capable of validating an individual before enrolling him into the device. The enrollment authority maintains and operates the appropriate equipment for enrollment, and provides its approval of the enrollment. The methods described herein discuss post-manufacturing, enrollment, backup, and recovery processes for the device.

Skip to: Description  ·  Claims  ·  References Cited  · Patent History  ·  Patent History
Description
CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 13/849,985, filed on Mar. 25, 2013, entitled, “Methods for Secure Enrollment and Backup of Personal Identity Credentials Into Electronic Devices,” which is a continuation of U.S. patent application Ser. No. 13/210,022, now U.S. Pat. No. 8,407,480, filed on Aug. 15, 2011, entitled, “Methods For Secure Enrollment And Backup Of Personal Identity Credentials Into Electronic Devices,” which is a continuation of U.S. patent application Ser. No. 12/560,254, filed on Sep. 15, 2009, entitled “Methods For Secure Enrollment And Backup Of Personal Identity Credentials Into Electronic Devices,” now U.S. Pat. No. 8,001,372, which is a continuation of U.S. patent application Ser. No. 10/635,762, filed on Aug. 6, 2003, entitled “Methods For Secure Enrollment And Backup Of Personal Identity Credentials Into Electronic Devices,” now U.S. Pat. No. 7,590,861, which claims priority under 35 U.S.C. §119(e) to provisional patent application Ser. No. 60/401,399 filed on Aug. 6, 2002 entitled, “A Secure Enrollment Process for a Biometric Personal Identification Device,” each of which is hereby incorporated by reference in its entirety.

This application is related to U.S. patent application Ser. No. 12/190,058, entitled “Methods for Secure Enrollment Of Personal Identity Credentials Into Electronic Devices,” now U.S. Pat. No. 8,127,143, and U.S. patent application Ser. No. 12/190,061, entitled “Methods for Secure Backup of Personal Identity Credentials for Electronic Devices,” now U.S. Pat. No. 7,788,501, and U.S. patent application Ser. No. 12/190,064, entitled “Methods for Secure Restoration of Personal Identity Credentials Into Electronic Devices,” now U.S. Pat. No. 8,055,906, each filed on Aug. 12, 2008, and each of which is incorporated herein by reference its entirety.

BACKGROUND OF THE INVENTION

1. Field of the Invention

This invention relates generally to the field of information security, and more particularly to an enrollment process for devices capable of storing and releasing personal identity credentials based on authentication of a human fingerprint.

2. Necessity of the Invention

Devices and applications that use biometric authentication are increasing in popularity and frequency of use in applications where information security and privacy is critical. The success rates of devices that use biometrics as a form of authorization are dependent on the accuracy of the process by which information is associated with the biometric; for example, it must not be possible for John Doe to intercept Jane Doe's enrollment process and enroll Jane Doe's credentials into a device with his fingerprint. A generalized enrollment process includes capturing a biometric sample, ensuring the legitimacy of the sample and the individual providing the sample, storing the biometric sample in the appropriate location in the device, and enabling access rights to the enrolled individual. If this enrollment process is performed incorrectly or ineffectively then the process of biometric authentication and the implicit guarantee of enhanced security are easily defeated.

A variety of portable electronic devices with biometric authentication are available to consumers. These include Hewlett Packard's iPAQ Pocket PC h5450, 3M-AiT's VeriMe, Privaris' BPID™ Security Device, and Sony's FIU-900 Puppy®. Each device is capable of storing fingerprints and performing on-board matching. Several of these products are configurable to allow use of cryptographic keys after proof of biometric identification. As discussed in the following section, ownership of cryptographic keys is typically used as a form of remote identification when individuals are communicating digitally. It is imperative, then, that the fingerprint is definitively linked to an individual, so that the cryptographic keys cannot be misused.

Furthermore, because the enrollment process must necessarily be stringent, and likely time-consuming, it is desirable to have a simple method of archiving and restoring enrolled credentials and fingerprints. Clearly the method must be inherently secure, because the entire enrollment process could be overridden by a compromise of the backup process.

DESCRIPTION OF THE RELATED ART

Public Key Infrastructure

The public key infrastructure (PKI) and digital certificates are very common and, when used correctly, can be used to guarantee a ‘cryptographic identity’ of an individual. The most common form of the PKI uses the RSA algorithm, which is now freely available to the public.

To use the PKI, an individual—Alice—applies for a digital certificate from a trusted authority. After a substantive background investigatory process, the trusted authority decides that Alice is who she claims to be and decides to issue a digital certificate. The certificate includes a public key, one half of an asymmetric key pair, which is assigned only to Alice. She retains the other half of the key pair, the private key. Due to the fundamental principles of public key cryptography, anything encrypted by the Alice's private key can only be decrypted using her public key, and vice versa. Alice is free to distribute the digital certificate and the public key to whomever she wishes.

When another individual, Bob, wishes to send a message to Alice, he encrypts it with her public key. Alice receives the encrypted message and uses her private key to decrypt it. Because Alice is the unique owner of her public key, Bob knows that she possesses the unique and accompanying private key. Additionally, Bob sees that a trusted authority, which he knows performs substantive background checks, issued the digital certificate issued to Alice. He is assured that the only person who can read the message is truly Alice. This assures one-way security.

However, Alice cannot be sure that Bob sent her the message, because her public key is freely accessible. To combat this problem, Bob also requests and receives a digital certificate from a trusted authority. Bob writes his message and then creates a digital signature for the message. He first creates a hash of the message; this process creates a fixed-length string that is unique to the message but cannot be used to deduce the message. He then encrypts this hash using his private key and appends the encrypted hash to his message. The message and encrypted hash are now encrypted with Alice's public key, and transmitted to her.

Alice first decrypts the message with her private key. She can now read the message, as described above. However, she also has the encrypted hash, which she can use to verify that Bob sent the message. She uses Bob's public key to decrypt the digital signature and obtain the hash. Alice then hashes the received message herself, using the same hash algorithm as Bob. If she obtains the same hash value as the one transmitted by Bob, she is assured that the message has not changed, and that he did actually send the message.

Enrollment Processes

3M-AiT's VeriMe stores a biometric template and a cryptographic private key for one user. When the user wishes to use the cryptographic private key, he or she must supply the correct biometric template. According to the VeriMe fact sheet, the private key is generated at the time of “secure registration” of the fingerprint. However, the fact sheet does not describe the secure registration or what it entails; it also does not discuss a secure backup and recovery process.

Biometric Associates (BAI) produces a fingerprint sensor that can be embedded into a smartcard. The smartcard can then be used to perform local biometric authentication, like the devices described above. According to BAI's website, the cards can enroll up to eight users with the use of a BAI Enrollment Station. The Enrollment Station provides external equipment necessary to instruct the smartcard to start enrolling fingerprints and personal credentials. However, the published information does not describe a secure cryptographic process for accomplishing this. It also does not describe secure backup and recovery processes.

BRIEF SUMMARY OF THE INVENTION

The invention disclosed herein describes processes for securely enrolling personal identity credentials into devices with means for personal identification. For example, a handheld computer with a biometric sensor may use enrolled fingerprints to identify a user when he requests access to stored information. The enrollment of the fingerprint must tie the user definitively to the fingerprint so that future authorizations are valid.

The invention described herein provides a process for enrollment wherein a manufacturer of a personal identification device records serial numbers or another unique identifier for each device that it produces, along with a self-generated public key for each device. An enrollment authority is recognized by the manufacturer or another suitable institution as capable of validating an individual before enrolling him into the device-maintains and operates the appropriate equipment for enrollment, and provides its approval of the enrollment.

The methods described herein are directed to post-manufacturing processes for the device, as well as the enrollment itself. Additionally, the invention describes methods for securely archiving enrolled personal identity credentials. This is to allow users to restore previously validated credentials into a new device without requiring a completely new enrollment. Correspondingly, the invention describes the restoration process, in which the stored credentials are securely downloaded into the new device.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1: Post-manufacturing process

101 Provide manufacturer's public key to device

102 Generate key pair for device

103 Provide device′ public key and unique ID to manufacturer

104 Create digital certificate for device

105 Provide digital certificate to device

106 Store device′ public key and unique ID

107 Disable device

FIG. 2: Enrollment

201 Request permission from enrollment authority to enroll credentials into device

202 Validate the request

203 Present device′ digital certificate

204 Verify that device is true owner of the certificate

205 Present enrollment authority's digital certificate

206 Verify that enrollment authority is true owner of the certificate

207 Create a session key

208 Complete enrollment, encrypting with the session key

FIG. 3: Backup

301 Create symmetric biometric encryption and decryption key

302 Encrypt the biometric with the symmetric biometric encryption and decryption key

303 Divide the symmetric biometric encryption and decryption key into two parts

304 Encrypt first part with a passphrase

305 Digitally sign second part with primary device′ private key

306 Encrypt digital signature and second part of symmetric biometric encryption and decryption key with the controller's public key

307 Create symmetric personal identity credential encryption and decryption key

308 Digitally sign personal identity credential with primary device′ private key

309 Encrypt credential with symmetric personal identity credential encryption and decryption key

310 Divide symmetric personal identity credential encryption and decryption key

311 Encrypt first part of symmetric personal identity credential encryption and decryption key with passphrase

312 Digitally sign second part of symmetric personal identity credential encryption and decryption key with primary device′ private key

313 Encrypt digital signature and second part of symmetric personal identity credential encryption and decryption key with controller's public key

314 Store the encrypted biometric, encrypted credentials, and encrypted symmetric biometric encryption and decryption key and symmetric personal identity credential encryption and decryption key in an electronic storage repository

315 Provide user with a digital certificate containing the primary device′ public key

FIG. 4: Restoration

401 Access the electronic storage repository

402 Obtain both parts of the symmetric biometric encryption and decryption key

403 Decrypt the first part with a passphrase

404 Decrypt the second part and the digital signature with the controller's private key

405 Verify the digital signature using the primary device′ public key

406 Combine both parts of the symmetric biometric encryption and decryption key

407 Decrypt the biometric

408 Store the biometric in the secondary device

409 Obtain both parts of the symmetric personal identity credential encryption and decryption key

410 Decrypt the first part with a passphrase

411 Decrypt the second part and the digital signature with the controller's private key

412 Verify the digital signature using the primary device′ public key

413 Combine both parts of the symmetric personal identity credential encryption and decryption key

414 Decrypt the personal identity credential and the associated digital signature

415 Verify the digital signature using the primary device′ public key

416 Store the personal identity credential in the secondary device

FIG. 1 is a flow chart illustrating the post-manufacturing process for a personal identification device.

FIG. 2 is a flow chart illustrating the process for enrolling personal identity credentials into the personal identification device.

FIG. 3 is a flow chart illustrating the backup process for securely storing personal identity credentials for future restoration.

FIG. 4 is a flow chart illustrating the restoration process.

 DETAILED DESCRIPTION

The following detailed description is of the best presently contemplated modes of carrying out the invention. This description is not to be taken in a limiting sense, but is made merely for the purpose of illustrating general principles of embodiments of the invention.

The invention disclosed herein provides a process for securely enrolling individuals into devices with means for personal identification via use of biometric authentication (hereafter referred to as ‘personal identification devices’). Because these devices are intended for use as trusted authentication devices, it is imperative that all of the information stored within the device be placed there in such a manner that it cannot be altered without proper authorization. There are two participants in the enrollment process, the manufacturer of the personal identification device and an enrollment authority.

The enrollment process includes identifying the device post-manufacturing and enrolling personal identity credentials and an associated biometric into the personal identification device. Furthermore, the invention also discloses methods for creating secure backup and recovery processes, such that an individual may securely store the enrolled information in an electronic storage repository, such as a hard drive. If his personal identification device fails he can use the recovery process to transfer the stored, enrolled information to a new device.

The two participants in the enrollment process must be definitely and separately identified for proper enrollment. The first participant in the enrollment system is the manufacturer of the personal identification device. The manufacturer is responsible for maintaining a database of unique identifiers, such as serial numbers, for all of the devices that it produces. This enables it later to determine if it manufactured a particular device. The second party is an enrollment authority, which is responsible for investigating, authorizing and performing individuals' requests for enrollment into a personal identification device. This participant may be a Department of Motor Vehicles, a building security officer, or any other person or organization responsible for issuing personal identification devices.

Initial Enrollment

This enrollment system uses the PKI described above. Each manufacturer and enrollment authority is provided with at least one asymmetric key pair that can be used for identification and encryption. The key pairs may be self generated, but the public key for each must be placed in a digital certificate signed by a trusted authority. Additionally, the manufacturer may wish to sign digital certificates owned by the enrollment authority as means for guaranteeing its approval of the enrollment authority.

FIG. 1 demonstrates the post-manufacturing process that begins the enrollment process for a personal identification device. Immediately following manufacturing, each personal identification device receives a public key possessed by its manufacturer (step 101). In the preferred embodiment this key is received as part of a digital certificate. The personal identification device can use this public key to verify the digital signature on messages transmitted from the manufacturer and accept them as legitimate instructions. This step requires that the manufacturing process be secure and tamper-resistant; receiving a key other than a trusted manufacturer's would directly compromise future security verifications.

The personal identification device now generates an asymmetric key pair for itself (step 102). The public key and the device's unique identifier are sent to the manufacturer (step 103). The manufacturer, or other legitimate certificate authority, generates a digital certificate for the device (step 104). This is now sent back to the device, and can be signed by the manufacturer as a token of its legitimacy (step 105). The manufacturer keeps a record of the device's public key and its unique identifier for future reference (step 106). At this point all functionality within the personal identification device is disabled, such that it is in a state waiting for future enrollment (step 107).

As seen in FIG. 2, upon receipt of a personal identification device, an individual requests enrollment rights from an enrollment authority (step 201). This may require that the individual be physically present in a specified location, or may be performed remotely. The enrollment authority may establish all rules pertaining to the applicant verification process. The security and authenticity of the personal identification device is only as good as that of the verification process, so it is anticipated that these processes will be as stringent as required by the end application.

After approving the applicant, the enrollment authority receives the personal identification device's digital certificate (steps 202 and 203). The enrollment authority validates the digital certificate by prompting the device to encrypt a predetermined string with its private key (step 204). The enrollment authority now decrypts the encrypted string using the public key stored in the device′ digital certificate, and verifies that the decrypted string matches the predetermined string. At this point the personal identification device will receive and verify the validity of the enrollment authority's digital certificate (steps 206 and 206). It performs the same prompt and verification process described above, and can also verify the manufacturer's signature on the certificate if one exists. After confirming the legitimacy of the enrollment authority, the personal identification device creates a session key and securely releases it to the enrollment authority (step 207). The personal identification device and the enrollment authority can now communicate freely using the session key (step 208). The biometric may be downloaded into the personal identification device along with the personal identity credentials, or may alternatively be sensed locally using the device and stored locally. The enrollment process, at this stage, is application-dependent and requires the establishment of requisite credentials, etc., which are not covered within the scope of this invention.

Restoration Processes

It may be necessary in some cases to provide a backup of at least one enrolled personal identity credential and biometric. The backup may be used in the event that the personal identification device fails, such that the individual may re-enroll a new personal identification device without undergoing the entire process described above; these devices are referred to as the ‘primary personal identification device’ and the ‘secondary personal identification device,’ respectively.

Backup

There are two distinct parts of the restoration process. The first part describes a method for archiving the enrolled personal identity credential, which allows an enrolled individual to securely store his personal identity credential and biometric to a user-accessible computer disk or other electronic storage repository. This data is only accessible with permission from a device manufacturer, an enrollment authority, or a recovery authority, as specified by the implementer of the system. In the primary embodiment, this system controller will be the manufacturer of the primary personal identification device. The second part of the restoration process describes a method for restoring the stored data to the secondary personal identification device.

As seen in FIG. 3, the primary personal identification device generates a symmetric biometric encryption and decryption key (step 301). This key is used for encrypting a digital representation of the enrolled biometric (step 302), which can be used to unlock the archived personal identity credential(s). After encryption of the biometric, the symmetric biometric encryption and decryption key is divided into two unique and distinct parts (step 303); the scheme of separation may be selected at the discretion of the system implementer. The first part of the symmetric biometric encryption and decryption key is encrypted with a user-selected passphrase (step 304). The second part of the symmetric biometric encryption and decryption key is signed by a private key possessed by the primary personal identification device (step 305), and is then encrypted with a public key owned by the system controller (step 306). As described above, in this embodiment the system controller is the primary personal identification device manufacturer. Using the manufacturer's public key forces an individual to request restoration privileges from the manufacturer during restoration, because the individual needs the manufacturer to decrypt the data with its private key. This is discussed in further detail below.

The primary personal identification device then generates a symmetric personal identity credential encryption and decryption key (step 307), which is used for encrypting at least one enrolled personal identity credential. The primary personal identification device first digitally signs the personal identity credential, using a private key (step 308), and then encrypts the personal identity credential and associated digital signature (step 309). Similarly to the scheme described above, the symmetric personal identity credential encryption and decryption key is divided (step 310) into two unique and distinct parts. The first part is encrypted with a user-selected passphrase (step 311), which may or may not be the same passphrase as used above. The second part is again signed by the device′ private key (step 312) and encrypted with the manufacturer's public key (step 313).

All of the encrypted and/or signed data—the biometric, the symmetric biometric encryption and decryption key, the personal identity credential, and the symmetric personal identity credential encryption and decryption key—are now stored in an electronic storage repository (step 314). In typical embodiments the electronic storage repository could be a computer hard drive, floppy disk, or network drive. The primary personal identification device releases its digital certificate to the individual for future use of its public key (step 315).

Restoration

As seen in FIG. 4, when an individual receives a secondary personal identification device, and wishes to restore data from a primary personal identification device, he must access the electronic storage repository (step 401). The individual must first acquire the two encrypted and/or signed parts of the symmetric biometric encryption and decryption key (step 402). The secondary personal identification device decrypts the first part of the symmetric biometric encryption and decryption key with the user's passphrase (step 403). It then requests the system controller, the manufacturer of the primary personal identification device, to decrypt the second part of the symmetric biometric encryption and decryption key and the associated digital signature using its (the manufacturer's) private key (step 404). Once the data has been decrypted, the secondary personal identification device verifies the digital signature using a public key possessed by the primary personal identification device (step 405). The two parts of the symmetric biometric encryption and decryption key are now combined appropriately (step 406), and can be used to decrypt the biometric (step 407). The biometric is now stored in an appropriate location within the secondary personal identification device (step 408).

The individual now obtains the two encrypted and/or signed parts of the symmetric personal identity credential encryption and decryption key (step 409). Similarly to the process described above, the secondary personal identification device decrypts the first part of the symmetric personal identity credential encryption and decryption key using a user-selected passphrase (step 410). It now requests the system controller, the manufacturer of the primary personal identification device, to decrypt the second part of the symmetric personal identity credential encryption and decryption key and the accompanying digital signature using its private key (step 411). Again, the secondary personal identification device verifies the digital signature using a public key possessed by the primary personal identification device (step 412). The two parts of the key are reconstructed to form one key (step 413). The key is now used to decrypt the personal identity credential and the associated digital signature (step 414), and the signature is verified using a public key owned by the primary personal identification device (step 415). The decrypted personal identity credential can now be stored appropriately within the secondary personal identification device (step 416).

While the description above refers to particular embodiments of the present invention, it will be understood that many modifications may be made without departing from the spirit thereof. The accompanying claims are intended to cover such modifications as would fall within the true scope and spirit of the present invention.

Claims

1. A method, comprising:

receiving at a personal identification device a public key before biometric data associated with enrollment is received;
sending an identifier from the personal identification device to a party based on the public key before biometric data associated with enrollment is received, the identifier being uniquely associated with the personal identification device;
receiving at the personal identification device a digital certificate from the party based on the identifier before biometric data associated with enrollment is received; and
disabling functionality within the personal identification device except that the personal identification device is in a wait state associated with future enrollment.

2. The method of claim 1, further comprising sending the public key from the personal identification device to the party after the receiving the public key.

3. The method of claim 1, wherein the receiving the digital certificate from the party is based on the public key and the identifier.

4. The method of claim 1, wherein the identifier is associated with an asymmetric key pair including a personal identification device public key and a personal identification device private key.

5. The method of claim 1, further comprising producing the identifier at the personal identification device.

6. The method of claim 1, further comprising receiving at the personal identification device the identifier from the party.

7. The method of claim 1, wherein the digital certificate includes the public key.

8. The method of claim 1, wherein the party is a manufacturer of the personal identification device and separate from an enrollment party authorized to enable enrollment of the biometric data at the personal identification device.

9. The method of claim 1, wherein the party is a first party, the personal identification device being configured to enroll the biometric data from a second party different from the first party after the receiving at the personal identification device the digital certificate.

10. The method of claim 1, wherein the digital certificate includes data associated with the personal identification device.

11. A method, comprising:

sending a public key to a personal identification device;
receiving an identifier from the personal identification device, the identifier being uniquely associated with the personal identification device;
producing a digital certificate based on the identifier and before enrollment of biometric data; and
sending the digital certificate to the personal identification device such that functionality of the personal identification device is disabled except that the personal identification device is configured to send the digital certificate to an enrollment party during future enrollment.

12. The method of claim 11, wherein the producing of the digital certificate is based, at least in part, on the public key.

13. The method of claim 11, wherein the receiving and the producing is performed by a first party, the method further comprising: adding a public key of the first party to the digital certificate associated with the second party; and

receiving at the first party a digital certificate uniquely associated with a second party different from the first party;
sending the digital certificate associated with the second party from the first party to the second party.

14. The method of claim 11, wherein the digital certificate includes the public key.

15. The method of claim 11, further comprising producing at the party an asymmetric key pair uniquely associated with the party.

16. The method of claim 11, wherein the public key is associated with a manufacturer of the personal identification device and separate from the enrollment party authorized to enable enrollment of the biometric data at the personal identification device.

17. The method of claim 11, wherein the personal identification device is configured to enroll biometric data from the enrollment party after the sending the digital certificate.

18. The method of claim 11, wherein the producing the digital certificate is based on data associated with the personal identification device.

19. A method, comprising:

receiving an encryption identifier at a personal identification device from a party during pre-enrollment;
receiving a digital signature at the personal identification device from the party during pre-enrollment;
the encryption identifier and the digital signature collectively configured to enable verification of the party by the personal identification device; and
disabling functionality within the personal identification device except for functionality associated with future enrollment.

20. The method of claim 19, wherein:

the encryption identifier is a public key; and
the receiving the digital signature including receiving a digital certificate including the digital signature.

21. A non-transitory computer-readable medium programmed with executable instructions that, when executed by a processing system, perform a method comprising:

receiving at a personal identification device a public key before biometric data associated with enrollment is received;
sending an identifier from the personal identification device to a party based on the public key before biometric data associated with enrollment is received, the identifier being uniquely associated with the personal identification device;
receiving at the personal identification device a digital certificate from the party based on the identifier before biometric data associated with enrollment is received; and
disabling functionality within the personal identification device except that the personal identification device is in a wait state associated with future enrollment.

22. The medium of claim 21, further comprising sending the public key from the personal identification device to the party after the receiving the public key.

23. The medium of claim 21, wherein the receiving the digital certificate from the party is based on the public key and the identifier.

24. The medium of claim 21, wherein the identifier is associated with an asymmetric key pair including a personal identification device public key and a personal identification device private key.

25. The medium of claim 21, further comprising producing the identifier at the personal identification device.

26. The medium of claim 21, further comprising receiving at the personal identification device the identifier from the party.

27. The medium of claim 21, wherein the digital certificate includes the public key.

28. The medium of claim 21, wherein the party is a manufacturer of the personal identification device and separate from an enrollment party authorized to enable enrollment of the biometric data at the personal identification device.

29. The medium of claim 21, wherein the party is a first party, the personal identification device being configured to enroll the biometric data from a second party different from the first party after the receiving at the personal identification device the digital certificate.

30. The medium of claim 21, wherein the digital certificate includes data associated with the personal identification device.

31. A non-transitory computer-readable medium programmed with executable instructions that, when executed by a processing system, perform a method comprising:

sending a public key to a personal identification device;
receiving an identifier from the personal identification device, the identifier being uniquely associated with the personal identification device;
producing a digital certificate based on the identifier and before enrollment of biometric data; and
sending the digital certificate to the personal identification device such that functionality of the personal identification device is disabled except that the personal identification device is configured to send the digital certificate to an enrollment party during future enrollment.

32. The medium of claim 31, wherein the producing of the digital certificate is based, at least in part, on the public key.

33. The medium of claim 31, wherein the receiving and the producing is performed by a first party, the method further comprising: adding a public key of the first party to the digital certificate associated with the second party; and

receiving at the first party a digital certificate uniquely associated with a second party different from the first party;
sending the digital certificate associated with the second party from the first party to the second party.

34. The medium of claim 31, wherein the digital certificate includes the public key.

35. The medium of claim 31, further comprising producing at the party an asymmetric key pair uniquely associated with the party.

36. The medium of claim 31, wherein the public key is associated with a manufacturer of the personal identification device and separate from the enrollment party authorized to enable enrollment of the biometric data at the personal identification device.

37. The medium of claim 31, wherein the personal identification device is configured to enroll biometric data from the enrollment party after the sending the digital certificate.

38. The medium of claim 31, wherein the producing the digital certificate is based on data associated with the personal identification device.

39. A non-transitory computer-readable medium programmed with executable instructions that, when executed by a processing system, perform a method comprising:

receiving an encryption identifier at a personal identification device from a party during pre-enrollment;
receiving a digital signature at the personal identification device from the party during pre-enrollment;
the encryption identifier and the digital signature collectively configured to enable verification of the party by the personal identification device; and
disabling functionality within the personal identification device except for functionality associated with future enrollment.

40. The medium of claim 39, wherein:

the encryption identifier is a public key; and
the receiving the digital signature including receiving a digital certificate including the digital signature.
Referenced Cited
U.S. Patent Documents
4993068 February 12, 1991 Piosenka et al.
5053608 October 1, 1991 Senanayake
5131038 July 14, 1992 Puhl et al.
5280527 January 18, 1994 Gullman et al.
5469506 November 21, 1995 Berson et al.
5473692 December 5, 1995 Davis
5481265 January 2, 1996 Russell
5526428 June 11, 1996 Arnold
5591949 January 7, 1997 Bernstein
5613012 March 18, 1997 Hoffman et al.
5615277 March 25, 1997 Hoffman
5659616 August 19, 1997 Sudia
5729220 March 17, 1998 Russell
5784463 July 21, 1998 Chen et al.
5805719 September 8, 1998 Pare, Jr. et al.
5838812 November 17, 1998 Pare, Jr. et al.
5870723 February 9, 1999 Pare, Jr. et al.
5872848 February 16, 1999 Romney et al.
5920640 July 6, 1999 Salatino et al.
5930804 July 27, 1999 Yu et al.
5952641 September 14, 1999 Korshun
5991408 November 23, 1999 Pearson et al.
6038666 March 14, 2000 Hsu et al.
6041410 March 21, 2000 Hsu et al.
6076167 June 13, 2000 Borza
6084967 July 4, 2000 Kennedy et al.
6084968 July 4, 2000 Kennedy et al.
6154879 November 2000 Pare, Jr. et al.
6167517 December 26, 2000 Gilchrist et al.
6181803 January 30, 2001 Davis
6182221 January 30, 2001 Hsu et al.
6185316 February 6, 2001 Buffam
6201484 March 13, 2001 Russell
6202151 March 13, 2001 Musgrave et al.
6219793 April 17, 2001 Li et al.
6256737 July 3, 2001 Bianco et al.
6268788 July 31, 2001 Gray
6282649 August 28, 2001 Lambert et al.
6310966 October 30, 2001 Dulude et al.
6317834 November 13, 2001 Gennaro et al.
6353889 March 5, 2002 Hollingshead
6356753 March 12, 2002 Kolev et al.
6366682 April 2, 2002 Hoffman et al.
6367013 April 2, 2002 Bisbee et al.
6367017 April 2, 2002 Gray
6397198 May 28, 2002 Hoffman et al.
6446210 September 3, 2002 Borza
6466781 October 15, 2002 Bromba et al.
6484260 November 19, 2002 Scott et al.
6487662 November 26, 2002 Kharon et al.
6490680 December 3, 2002 Scheidt et al.
6505193 January 7, 2003 Musgrave et al.
6529885 March 4, 2003 Johnson
6532298 March 11, 2003 Cambier et al.
6581161 June 17, 2003 Byford
6601172 July 29, 2003 Epstein
6609198 August 19, 2003 Wood et al.
6615264 September 2, 2003 Stoltz et al.
6618806 September 9, 2003 Brown et al.
6636973 October 21, 2003 Novoa et al.
6657538 December 2, 2003 Ritter
6662166 December 9, 2003 Pare, Jr. et al.
6668332 December 23, 2003 McNeil
6671808 December 30, 2003 Abbott et al.
6681034 January 20, 2004 Russo
6719200 April 13, 2004 Wiebe
6728881 April 27, 2004 Karamchetty
6735695 May 11, 2004 Gopalakrishnan et al.
6751734 June 15, 2004 Uchida
6757411 June 29, 2004 Chau
6765470 July 20, 2004 Shinzaki
6766040 July 20, 2004 Catalano et al.
6775776 August 10, 2004 Vogt et al.
6786397 September 7, 2004 Silverbrook et al.
6816970 November 9, 2004 Morgan et al.
6819219 November 16, 2004 Bolle et al.
6820202 November 16, 2004 Wheeler et al.
6829711 December 7, 2004 Kwok et al.
6832317 December 14, 2004 Strongin et al.
6834351 December 21, 2004 Kabenjian
6836765 December 28, 2004 Sussman
6836843 December 28, 2004 Seroussi et al.
6839688 January 4, 2005 Drummond et al.
6844660 January 18, 2005 Scott
6848052 January 25, 2005 Hamid et al.
6850147 February 1, 2005 Prokoski et al.
6850252 February 1, 2005 Hoffberg
6853739 February 8, 2005 Kyle
6853988 February 8, 2005 Dickinson et al.
6857073 February 15, 2005 French et al.
6862443 March 1, 2005 Witte
6870946 March 22, 2005 Teng et al.
6870966 March 22, 2005 Silverbrook et al.
6871193 March 22, 2005 Campbell et al.
6871287 March 22, 2005 Ellingson
6871784 March 29, 2005 Jayaratne
6876757 April 5, 2005 Yau et al.
6877097 April 5, 2005 Hamid et al.
6879243 April 12, 2005 Booth et al.
6879966 April 12, 2005 Lapsley et al.
6880749 April 19, 2005 Green et al.
6880750 April 19, 2005 Pentel
6883709 April 26, 2005 Joseph
6886096 April 26, 2005 Appenzeller et al.
6886101 April 26, 2005 Glazer et al.
6886104 April 26, 2005 McClurg et al.
6888445 May 3, 2005 Gotfried et al.
6898577 May 24, 2005 Johnson
6901154 May 31, 2005 Dunn
6901155 May 31, 2005 Xia et al.
6901266 May 31, 2005 Henderson
6901382 May 31, 2005 Richards et al.
6914517 July 5, 2005 Kinsella
6957185 October 18, 2005 Labaton
6957337 October 18, 2005 Chainer et al.
6963659 November 8, 2005 Tumey et al.
6985502 January 10, 2006 Bunton
6990444 January 24, 2006 Hind et al.
7024562 April 4, 2006 Flink et al.
7028191 April 11, 2006 Michener et al.
7035442 April 25, 2006 Ha et al.
7069444 June 27, 2006 Lowensohn et al.
7111173 September 19, 2006 Scheidt
7287158 October 23, 2007 Futamura et al.
7305562 December 4, 2007 Bianco et al.
7310734 December 18, 2007 Boate et al.
7590861 September 15, 2009 Abdallah et al.
7613659 November 3, 2009 Hoffman et al.
7788501 August 31, 2010 Abdallah et al.
8001372 August 16, 2011 Abdallah et al.
8055906 November 8, 2011 Abdallah et al.
8127143 February 28, 2012 Abdallah et al.
8407480 March 26, 2013 Abdallah et al.
20010001876 May 24, 2001 Morgan et al.
20010034836 October 25, 2001 Matsumoto
20020003892 January 10, 2002 Iwanaga
20020018585 February 14, 2002 Kim
20020023217 February 21, 2002 Wheeler et al.
20020026427 February 28, 2002 Kon et al.
20020031230 March 14, 2002 Sweet et al.
20020034319 March 21, 2002 Tumey et al.
20020056043 May 9, 2002 Glass
20020087857 July 4, 2002 Tsao et al.
20020095586 July 18, 2002 Doyle et al.
20020104006 August 1, 2002 Boate et al.
20020104025 August 1, 2002 Wrench, Jr.
20020129236 September 12, 2002 Nuutinen
20020129251 September 12, 2002 Itakura et al.
20020133716 September 19, 2002 Harif
20020174344 November 21, 2002 Ting
20020186838 December 12, 2002 Brandys
20030005310 January 2, 2003 Shinzaki
20030089764 May 15, 2003 Meadow et al.
20030097586 May 22, 2003 Mok
20030101349 May 29, 2003 Wang
20030115475 June 19, 2003 Russo et al.
20030115490 June 19, 2003 Russo et al.
20030200257 October 23, 2003 Milgramm et al.
20030233556 December 18, 2003 Angelo et al.
20040015958 January 22, 2004 Veil et al.
20040044627 March 4, 2004 Russell et al.
20090031140 January 29, 2009 Abdallah et al.
20090037745 February 5, 2009 Abdallah et al.
20090037746 February 5, 2009 Abdallah et al.
20100005315 January 7, 2010 Abdallah et al.
20120047370 February 23, 2012 Abdallah et al.
Foreign Patent Documents
2002-73566 February 2002 JP
WO 99/08238 February 1999 WO
00/65770 November 2000 WO
WO 0192994 December 2001 WO
WO2004/014017 February 2004 WO
Other references
  • International Search Report for PCT/US2003/024472 dated Nov. 20, 2003, 2 pages.
  • European Search Report for European Patent Application No. 03767206.0 mailed Jul. 4, 2011, 3 pages.
  • Schneier, Bruce, “Applied Crytography: Protocols, Algorithms, and Source Code in C,” Second Edition, 1996, John Wiley & Sons, Inc., pp. 31-34.
  • Fumiko Komatsu, PKI Handbook, Japan, Soft Research Center Inc., Nov. 25, 2000, pp. 105-108.
  • Isobe, Y et al., “Development of personal authentication system using fingerprint with digital signature technologies,” Proceedings of the 34th Hawaii International Conference on System Sciences, Jan. 3, 2001, pp. 4039-4047.
  • Davida, G. et al., “On enabling secure applications through off-line biometric identification,” Security and Privacy, May 3, 1998. Proceedings of the 1998 IEEE Symposium, pp. 148-157.
Patent History
Patent number: 9270464
Type: Grant
Filed: Jul 29, 2014
Date of Patent: Feb 23, 2016
Patent Publication Number: 20140344583
Assignee: Apple Inc. (Cupertino, CA)
Inventors: David S. Abdallah (Charlottesville, VA), Barry W. Johnson (Charlottesville, VA)
Primary Examiner: Techane Gergiso
Application Number: 14/445,853
Classifications
Current U.S. Class: Cellular Telephone Cryptographic Authentication (380/247)
International Classification: G06F 11/30 (20060101); H04L 9/32 (20060101); G06F 21/32 (20130101); G06K 9/00 (20060101); H04L 29/06 (20060101); G06Q 20/40 (20120101);