IP Library Granted Patent US 8,464,059
Granted Patent B2
US 8,464,059 · App. 12/329,419 · Granted Jun 11, 2013

System and method for device bound public key infrastructure

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,464,059
App. No.
12/329,419
Granted
Jun 11, 2013
Kind
B2
Abstract

Techniques are provided secured communication of data, such as in the context of a public key infrastructure (PKI). In one embodiment, the technique may involve using a private key that is bound to the device requesting the secure data, thereby making it harder for someone to copy, steal or fake. The private key may be generated by adding a filler code to a unique device identifier. The identifier may be based on at least one user-configurable parameter and at least one non-user-configurable parameter of the device.

Claims (52)

1. A device for sending data via secured communication in a public key infrastructure, comprising:

a communication module for communicating with a data requesting device;

at least one processor in operative communication with the communication module; and

a memory in operative communication with the at least one processor and comprising executable code for the at least one processor to:

generate a requester key pair for the data requesting device, the requester key pair comprising a requester private key and a requester public key; and

in response to receiving a unique device identifier from the data requesting device, calculate a difference between the unique device identifier and the requester private key.

2. The device of claim 1 , wherein the at least one processor stores the calculated difference as a filler code in the memory.

3. The device of claim 1 , wherein the at least one processor is adapted to:

in response to a request for a data from the data requesting device, identify the data requesting device;

encrypt the data using a sender private key and the requester public key; and

send the encrypted data and a filler code to the data requesting device.

4. The device of claim 3 , wherein the at least one processor publishes a sender public key, such that the data requesting device is able to (i) compute the requester private key by adding the filler code to the unique device identifier and (ii) use the computed requester private key to decrypt the encrypted data.

5. A device for requesting data via secured communication in a public key infrastructure, comprising:

a communication module for communicating with a data sender;

at least one processor in operative communication with the communication module; and

a memory in operative communication with the at least one processor and comprising executable code for the at least one processor to:

receive a request for a unique device identifier of a requesting device from the data sender;

in response to the request from the data sender, compile unique identifying information from a computing environment of the requesting device;

generate the unique device identifier based at least in part on the compiled unique identifying information; and

instruct the communication module to transmit the generated unique device identifier to the data sender.

6. The device of claim 5 , wherein the at least one processor is adapted to:

in response to receiving encrypted data and a filler code from the data sender, compute a requester private key by adding the filler code to the unique device identifier; and

use the computed requester private key to decrypt the encrypted data.

7. The device of claim 5 , wherein the at least one processor compiles the unique identifying information by compiling at least one user-configurable parameter and at least one non-user-configurable parameter of the device.

8. The device of claim 7 , wherein the at least one non-user-configurable parameter comprises at least one of hard drive serial number, CPU ID, CPU model, CPU manufacturer, and CPU voltage for the device.

9. The device of claim 7 , wherein the at least one non-user-configurable parameter is based on a carbon degradation characteristic of a computer chip of the device.

10. The device of claim 7 , wherein the at least one non-user-configurable parameter is based on a silicone degradation characteristic of a computer chip of the device.

11. The device of claim 7 , wherein the at least one user-configurable parameter comprises at least one of hard disk volume name, user name, device name, user password, and hard disk initialization date for the device.

12. A method for secured communication in a public key infrastructure, comprising:

generating a requester key pair for a data requesting device, the requester key pair comprising a requester private key and a requester public key;

receiving a unique device identifier from the data requesting device;

calculating a difference between the unique device identifier and the requester private key; and

storing the difference as a filler code.

13. The method of claim 12 , further comprising:

in response to a request for data from the data requesting device, identifying the data requesting device;

encrypting the data using a sender private key and the requester public key; and

sending the encrypted data and the filler code to the data requesting device.

14. The method of claim 12 , further comprising publishing a sender public key, such that the data requesting device is able to (i) compute the requester private key by adding the filler code to the unique device identifier and (ii) use the computed requester private key to decrypt the encrypted data.

15. A method for secured communication in a public key infrastructure, comprising:

receiving from a data sender a request for a unique device identifier of a requesting device;

in response to the request from the data sender, compiling unique identifying information from a computing environment of the requesting device;

generating the unique device identifier based at least in part on the compiled unique identifying information; and

providing the generated unique device identifier to the data sender.

16. The method of claim 15 , further comprising:

receiving encrypted data and a filler code from the data sender;

computing a requester private key by adding the filler code to the unique device identifier; and

using the computed requester private key to decrypt the encrypted data.

17. The method of claim 15 , wherein compiling the unique identifying information comprises compiling at least one user-configurable parameter and at least one non-user-configurable parameter of the device.

18. The method of claim 17 , wherein compiling the at least one non-user-configurable parameter comprises compiling at least one of hard drive serial number, CPU ID, CPU model, CPU manufacturer, and CPU voltage for the device.

19. The method of claim 17 , wherein compiling the at least one non-user-configurable parameter comprises compiling a carbon degradation characteristic of a computer chip of the device.

20. The method of claim 17 , wherein compiling the at least one non-user-configurable parameter comprises compiling a silicone degradation characteristic of a computer chip of the device.

21. The method of claim 17 , wherein compiling the at least one user-configurable parameter comprises compiling at least one of hard disk volume name, user name, device name, user password, and hard disk initialization date for the device.

Assignments (10)
CHANGE OF NAME Recorded Sep 28, 2018
From: CRYPTOSOFT LIMITED
To: DEVICE AUTHORITY LTD
Reel/Frame 047003/0102 →
MERGER Recorded Sep 28, 2018
From: DEVICEAUTHORITY, INC.
To: CRYPTOSOFT LIMITED
Reel/Frame 047003/0084 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING AND RECEIVING REVERSED PREVIOUSLY RECORDED AT REEL: 042123 FRAME: 0864. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST. Recorded May 31, 2017
From: FORTRESS CREDIT CO LLC
To: UNILOC LUXEMBOURG S.A.
Reel/Frame 042644/0085 →
RELEASE OF SECURITY INTEREST Recorded Apr 24, 2017
From: UNILOC LUXEMBOURG, S.A.
To: FORTRESS CREDIT CO LLC
Reel/Frame 042123/0864 →
SECURITY INTEREST Recorded Jan 9, 2015
From: UNILOC LUXEMBOURG, S.A.; UNILOC CORPORATION PTY LIMITED; UNILOC USA, INC.
To: FORTRESS CREDIT CO LLC
Reel/Frame 034747/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 16, 2014
From: UNILOC LUXEMBOURG, S.A.
To: DEVICEAUTHORITY, INC.
Reel/Frame 031989/0239 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 16, 2013
From: NETAUTHORITY, INC.
To: UNILOC LUXEMBOURG S. A.
Reel/Frame 031209/0010 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 26, 2013
From: UNILOC LUXEMBOURG S. A.
To: NETAUTHORITY, INC.
Reel/Frame 029879/0951 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 28, 2011
From: UNILOC USA, INC.
To: UNILOC LUXEMBOURG S. A.
Reel/Frame 026032/0862 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 3, 2009
From: RICHARDSON, RIC B.; ETCHEGOYEN, CRAIG S.; HARJANTO, DONO; DAVIS, BRADLEY C.
To: UNILOC USA INC.
Reel/Frame 022197/0557 →