Technologies for trusted device on-boarding

• US 10,326,590 B2
• Filed: 03/27/2015
• Issued: 06/18/2019
• Est. Priority Date: 11/11/2014
• Status: Active Grant

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Smith, Ned M., Walker, Jesse, Agerstam, Mats, Subramaniam, Ravi S., Cabre, Eduardo
• Primary Examiner(s): King, John B
• Assistant Examiner(s): Golriz, Arya
• Application Number:
  US14/670,874
• Publication Number:
  US 20160134419A1
• Time in Patent Office: 1,544 Days
• CPC Class Codes: H04L 2209/127 Trusted platform modules [TPM]
• CPC Class Codes: H04L 9/0833 involving conference or group key network architectures or network communication protocols for key management in group communication in a packet data network H04L63/065
• CPC Class Codes: H04L 9/0841 involving Diffie-Hellman or related key agreement protocols
• CPC Class Codes: H04L 9/0844 with user authentication or key authentication, e.g. ElGamal, MTI, MQV-Menezes-Qu-Vanstone protocol or Diffie-Hellman protocols using implicitly-certified keys
• CPC Class Codes: H04L 9/0866 involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics
• CPC Class Codes: H04L 9/14 using a plurality of keys or algorithms
• CPC Class Codes: H04L 9/30 Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
• CPC Class Codes: H04L 9/3013 involving the discrete logarithm problem, e.g. ElGamal or Diffie-Hellman systems
• CPC Class Codes: H04W 12/041 Key generation or derivation
• CPC Class Codes: H04W 12/0431 Key distribution or pre-distribution; Key agreement
• CPC Class Codes: H04W 12/0433 Key management protocols

Abstract

Technologies for trusted device on-boarding include a first computing device to generate a first public Diffie-Hellman key based on a private Diffie-Hellman key and a first unique identifier of the first computing device. The first unique identifier is retrieved from secure memory of the first computing device. The first computing device transmits the first public Diffie-Hellman key to a second computing device and receives, from the second computing device, a second public Diffie-Hellman key of the second computing device. The second public Diffie-Hellman key incorporates a second unique identifier of the second computing device. Further, the first computing device removes a contribution of the second unique identifier from the second public Diffie-Hellman key to generate a modified public Diffie-Hellman key and generates a shared Diffie-Hellman key based on the modified public Diffie-Hellman key and the private Diffie-Hellman key of the first computing device.

Claims

1. A first computing device for trusted device on-boarding, the first computing device comprising:

a processor;

a memory coupled to the processor;

a protocol execution module to (i) retrieve a first unique identifier from the memory and (ii) generate a first public Diffie-Hellman key based on a private Diffie-Hellman key and the first unique identifier of the first computing device, wherein the first unique identifier is provisioned into a secure portion of the memory; and

a communication module to (i) transmit the first public Diffie-Hellman key to a second computing device and (ii) receive, from the second computing device, a second public Diffie-Hellman key of the second computing device, wherein the second public Diffie-Hellman key incorporates a second unique identifier of the second computing device,

wherein the protocol execution module is further to (i) remove a contribution of the second unique identifier from the second public Diffie-Hellman key to generate a modified public Diffie-Hellman key (ii) generate a shared Diffie-Hellman key based on the modified public Diffie-Hellman key and the private Diffie-Hellman key of the first computing device and (iii) open a secure session with the second computing device using the shared Diffie-Hellman key, wherein to remove the contribution of the second unique identifier comprises to generate the modified public Diffie-Hellman key according to g^b=g^b+p/g^p, wherein;

g^b is the modified public Diffie-Hellman key;

g^b+p is the second public Diffie-Hellman key;

p is the second unique identifier;

g is a generator for an Abelian group;

g^p is a member of the Abelian group corresponding to g, and

/ is a division operator.

2. The first computing device of claim 1, wherein the protocol execution module is further to retrieve a known identifier for the second computing device over an out-of-band communication channel;

and

wherein the known identifier is the second unique identifier.

3. The first computing device of claim 1, wherein to generate the shared Diffie-Hellman key comprises to generate the shared Diffie-Hellman key according to g^ab=(g^b)^a, wherein a is the private Diffie-Hellman key of the first computing device.

4. The first computing device of claim 1, wherein the protocol execution module is further to generate a first keyed hash based on the shared Diffie-Hellman key, a first direct anonymous attestation group identifier of the first computing device, and the first public Diffie-Hellman key;

and

wherein the communication module is further to transmit the first public Diffie-Hellman key, the first direct anonymous attestation group identifier, and the first keyed hash to the second computing device.

5. The first computing device of claim 4, wherein the first direct anonymous attestation group identifier comprises an Enhanced Privacy Identification (EPID) group name.

6. The first computing device of claim 4, wherein the communication module is further to receive a second direct anonymous attestation group identifier and a second keyed hash from the second computing device;

and

wherein the protocol execution module is further to verify the second direct anonymous attestation group identifier and the second keyed hash.

7. The first computing device of claim 6, wherein to verify the second direct anonymous attestation group identifier comprises to verify that the second direct anonymous attestation group identifier identifies a direct anonymous attestation group having a known public key.

8. The first computing device of claim 6, wherein the protocol execution module is further to generate a first signature of the first public Diffie-Hellman key and the second public Diffie-Hellman key based on a private direct anonymous attestation key of the first computing device;

and

wherein the communication module is further to transmit the first signature to the second computing device.

9. The first computing device of claim 8, wherein the first signature comprises a first signature of the first public Diffie-Hellman key, the second public Diffie-Hellman key, and a first attestation digest of the first computing device based on the private direct anonymous attestation key of the first computing device.

10. The first computing device of claim 8, wherein the communication module is further to receive, from the second computing device, a second signature of the second computing device;

and

wherein the communication module is further to verify the second signature based on a public key corresponding with the second direct anonymous attestation group identifier.

11. The first computing device of claim 10, wherein the public key comprises a public Enhanced Privacy Identification (EPID) key that corresponds with an EPID group of the second computing device.

12. The first computing device of claim 10, wherein the second signature comprises a second signature of the first public Diffie-Hellman key, the second Diffie-Hellman key, and a second attestation digest of the second computing device;

and

wherein to verify the second signature comprises to verify that the second attestation digest corresponds with an attestation digest expected of a computing device having the second direct anonymous attestation group identifier.

13. The first computing device of claim 6, wherein opening the secure session comprises:

generate a session key based on the shared Diffie-Hellman key; and

generate a session identifier based on the first public Diffie-Hellman key, the second public Diffie-Hellman key, the first direct anonymous attestation group identifier, and the second direct anonymous attestation group identifier.

14. The first computing device of claim 1, further comprising:

a discovery module to (i) broadcast an existence of the first computing device to nearby computing devices and (ii) discover the second computing device; and

a connection handling module to open a communication connection to the second computing device,

wherein to generate the first public Diffie-Hellman key comprises to generate the first public Diffie-Hellman key in response to opening the communication connection.

15. One or more non-transitory machine-readable storage media comprising a plurality of instructions stored thereon that, in response to execution by a first computing device, cause the first computing device to:

retrieve a first unique identifier from memory of the first computing device, wherein the first unique identifier is provisioned into a secure portion of the memory;

generate a first public Diffie-Hellman key based on a private Diffie-Hellman key and the first unique identifier of the first computing device;

transmit the first public Diffie-Hellman key to a second computing device;

receive, from the second computing device, a second public Diffie-Hellman key of the second computing device, wherein the second public Diffie-Hellman key incorporates a second unique identifier of the second computing device;

remove a contribution of the second unique identifier from the second public Diffie-Hellman key to generate a modified public Diffie-Hellman key, wherein to remove the contribution of the second unique identifier comprises to generate the modified public Diffie-Hellman key according to g^b=g^b+p/g^p, wherein;

g^b is the modified public Diffie-Hellman key;

g^b+p is the second public Diffie-Hellman key;

p is the second unique identifier;

g is a generator for an Abelian group;

g^p is a member of the Abelian group corresponding to g, and

/ is a division operator;

generate a shared Diffie-Hellman key based on the modified public Diffie-Hellman key and the private Diffie-Hellman key of the first computing device; and

open a secure session with the second computing device using the shared Diffie-Hellman key.

16. The one or more non-transitory machine-readable storage media of claim 15, wherein the plurality of instructions further cause the first computing device to:

generate a first keyed hash based on the shared Diffie-Hellman key, a first direct anonymous attestation group identifier of the first computing device, and the first public Diffie-Hellman key;

transmit the first public Diffie-Hellman key, the first direct anonymous attestation group identifier, and the first keyed hash to the second computing device;

receive a second direct anonymous attestation group identifier and a second keyed hash from the second computing device; and

verify the second direct anonymous attestation group identifier and the second keyed hash.

17. The one or more non-transitory machine-readable storage media of claim 16, wherein the plurality of instructions further cause the first computing device to:

generate a first signature of the first public Diffie-Hellman key and the second public Diffie-Hellman key based on a private direct anonymous attestation key of the first computing device; and

transmit the first signature to the second computing device.

18. The one or more non-transitory machine-readable storage media of claim 17, wherein to generate the first signature comprises to generate a first signature of the first public Diffie-Hellman key, the second public Diffie-Hellman key, and a first attestation digest of the first computing device based on the private direct anonymous attestation key of the first computing device.

19. The one or more non-transitory machine-readable storage media of claim 17, wherein the plurality of instructions further cause the first computing device to:

receive, from the second computing device, a second signature of the first public Diffie-Hellman key, the second Diffie-Hellman key, and a second attestation digest of the second computing device; and

verify the second signature based on a public key corresponding with the second direct anonymous attestation group identifier by verifying that the second attestation digest corresponds with an attestation digest expected of a computing device having the second direct anonymous attestation group identifier.

20. A computer-implemented method for trusted device on-boarding, the method comprising:

retrieving a first unique identifier from memory of a first computing device, wherein the first unique identifier is provisioned into a secure portion of the memory;

generating, by the first computing device, a first public Diffie-Hellman key based on (i) a private Diffie-Hellman key and (ii) the first unique identifier of the first computing device;

transmitting, by the first computing device, the first public Diffie-Hellman key to a second computing device;

receiving, by the first computing device and from the second computing device, a second public Diffie-Hellman key of the second computing device, wherein the second public Diffie-Hellman key incorporates a second unique identifier of the second computing device;

removing, by the first computing device, a contribution of the second unique identifier from the second public Diffie-Hellman key to generate a modified public Diffie-Hellman key, wherein removing the contribution of the second unique identifier comprises generating the modified public Diffie-Hellman key according to g^b=g^b+p/g^p, wherein;

g^b is the modified public Diffie-Hellman key;

g^b+p is the second public Diffie-Hellman key;

p is the second unique identifier;

g is a generator for an Abelian group;

g^p is a member of the Abelian group corresponding to g, and

/ is a division operator;

generating, by the first computing device, a shared Diffie-Hellman key based on the modified public Diffie-Hellman key and the private Diffie-Hellman key of the first computing device; and

opening a secure session with the second computing device using the shared Diffie-Hellman key.

21. The method of claim 20, further comprising:

generating, by the first computing device, a first keyed hash based on the shared Diffie-Hellman key, a first direct anonymous attestation group identifier of the first computing device, and the first public Diffie-Hellman key;

transmitting, by the first computing device, the first public Diffie-Hellman key, the first direct anonymous attestation group identifier, and the first keyed hash to the second computing device;

receiving, by the first computing device, a second direct anonymous attestation group identifier and a second keyed hash from the second computing device; and

verifying, by the first computing device, the second direct anonymous attestation group identifier and the second keyed hash.

22. The method of claim 21, further comprising:

generating, by the first computing device, a first signature of the first public Diffie-Hellman key and the second public Diffie-Hellman key based on a private direct anonymous attestation key of the first computing device;

transmitting, by the first computing device, the first signature to the second computing device;

receiving, by the first computing device and from the second computing device, a second signature of the first public Diffie-Hellman key, the second Diffie-Hellman key, and a second attestation digest of the second computing device; and

verifying, by the first computing device, the second signature based on a public key corresponding with the second direct anonymous attestation group identifier by verifying that the second attestation digest corresponds with an attestation digest expected of a computing device having the second direct anonymous attestation group identifier.