Method of bootstrapping an authenticated data session configuration

• US 20090210696A1
• Filed: 02/12/2009
• Published: 08/20/2009
• Est. Priority Date: 02/15/2008
• Status: Active Grant

• Current Assignee: Connotech Experts-Conseils Incorporated
• Original Assignee: Connotech Experts-Conseils Incorporated
• Inventors: Moreau, Thierry
• Granted Patent: US 8,423,759 B2
• Time in Patent Office: Days
• US Class Current: 713/151
• CPC Class Codes: H04L 2209/08 Randomization, e.g. dummy operations or using noise
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2463/102 applying security measure for e-commerce
• CPC Class Codes: H04L 63/0435 wherein the sending and receiving network entities apply symmetric encryption, i.e. same key used for encryption and decryption cryptographic mechanisms or cryptographic arrangements for symmetric key encryption H04L9/06
• CPC Class Codes: H04L 63/0442 wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263
• CPC Class Codes: H04L 63/123 received data contents, e.g. message integrity
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 9/302 involving the integer factorization problem, e.g. RSA or quadratic sieve [QS] schemes
• CPC Class Codes: H04L 9/3249 using RSA or related signature schemes, e.g. Rabin scheme
• CPC Class Codes: H04L 9/3265 using certificate chains, trees or paths; Hierarchical trust model

Abstract

An inventive method is disclosed for bootstrapping a trusted client public key at the server side in a client-server model of e-commerce or distributed computer applications. Generally, the invention integrates security technique elements and user procedural elements in such a way that no vulnerability arises due to the decoupling of elements. It is thus aimed at high security application areas. The readily available support of X.509 client security certificates in web browsers is advantageous for easy deployment at the client side. However, serious usability flaws deter the use of client certificates despite their potential for high security client authentication. The invention circumvents this contradiction at the client registration phase, and extends the benefits of simplified reliance on client public-private key pair to production use of the circumvention. Many variations of the inventive idea are disclosed, including the use of a dummy client security certificate that addresses the interoperability pitfalls of the X.509 technology while the trust in the client public key rests on other elements of the inventive method.

Claims

1. A Method of bootstrapping configuration for TLS-type data sessions comprising steps of:

a) procuring a client public key having a private key counterpart,

b) generating at the client entity a registration cryptogram according to a registration procedure to establish a symmetric secret key, and a second cryptogram that binds said client public key and said symmetric secret key,

c) sending at least said client public key, said registration cryptogram, and said second cryptogram to a registration server entity,

d) supplying from the client entity identification data elements for the client entity through at least one TLS-type data session instance connected to the registration server entity in which the client entity uses said private key counterpart, whereas temporary client entity authentication uses said client public key,

e) completing at the registration server entity the server procedures for said registration procedure using said registration cryptogram, whereas this step includes verification of identification data for the client entity including at least one of said data elements supplied from the client entity,

f) verifying at the registration server entity said second cryptogram, and

g) affixing a validity indication to said client public key at the registration server entity, contingent upon successful completion of said registration procedure and said verifying of said second cryptogram.

2. The method as in claim 1 further comprising the use configuration for TLS-type data sessions with the step of

h) transmitting data between the client entity and a production server entity using at least one TLS-type data session instance in which the client entity uses said private key counterpart, whereas client entity authentication uses said client public key and said validity indication.

3. The method as in claim 2, where said TLS-type data session instance connected to the registration server entity and said TLS-type data session instance in the transmitting step h) use during protocol parameter negotiations a client security certificate chain in which at least one signature uses a private key of which the signature capability is available without authentication formalities to the client entity.

4. The method as in claim 3, where said client security certificate chain is generated at the client entity.

5. The method as in claim 4, where step b) and said generation of client security certificate chain are effected by means of a single software utility.

6. The method as in claim 3, where said client security certificate chain is generated by an on-line service provider.

7. The method as in claim 1, where steps a) and b) are effected by means of a single software utility.

8. The method as in claim 1, where said temporary client entity authentication using said client public key and said validity indication is effected by means of an HTTP server script procedure.

9. The method as in claim 1, where said client public key is stored in a database at the registration server entity.

10. The method as in claim 1, where said identification data for the client entity at the registration procedure completion step e) includes out-of-band assertions of identification data made by an agent of the client entity.

11. The method as in claim 1, where said verification of identification data for the client entity is operator-assisted.

12. A Method of bootstrapping configuration for TLS-type data sessions comprising steps of:

a) receiving from a client entity at a registration server entity at least

a.1) a client public key of said client, where said client public key has a private key counterpart,

a.2) a registration cryptogram generated by the client entity according to a registration procedure to establish a symmetric secret key, and

a.3) a second cryptogram that binds said client public key and said symmetric key,

b) accepting identification data elements for the client entity through at least one TLS-type data session instance connected to the client entity in which the client entity uses said private key counterpart, whereas temporary client entity authentication uses said client public key,

c) completing at the registration server entity the server procedures for said registration procedure using said registration cryptogram, whereas this step includes verification of identification data for the client entity including at least one of said data elements accepted from the client entity,

d) verifying at the registration server entity said second cryptogram, and

e) affixing a validity indication to said client public key at the registration server entity, contingent upon successful completion of said registration procedure and said verifying of said second cryptogram.

13. The method as in claim 12 further comprising the use configuration for TLS-type data sessions with the step of

f) transmitting data between a production server entity and the client entity using at least one TLS-type data session instance in which the client entity uses said private key counterpart, whereas client entity authentication uses said client public key and said validity indication.

14. The method as in claim 13, where said TLS-type data session instance at the registration server entity and said TLS-type data session instance at the production server entity uses during protocol parameter negotiations a client security certificate chain, the verification of which does not contribute to the client entity authentication.

15. The method as in claim 12, where said temporary client entity authentication using said client public key and said validity indication is effected by means of an HTTP server script procedure.

16. The method as in claim 12, where said client public key is stored in a database at the registration server entity.

17. The method as in claim 12, where said identification data for the client entity at the registration procedure completion step c) includes out-of-band assertions of identification data made by an agent of the client entity.

18. The method as in claim 12, where said verification of identification data for the client entity is operator-assisted.

19. A Method of bootstrapping configuration for TLS-type data sessions and using said configuration in at least one TLS-type data session instance connected to a production server entity that enforce client entity authentication, the method comprising steps of:

a) procuring a client public key having a private key counterpart,

b) generating a registration cryptogram according to a registration procedure to establish a symmetric secret key, and a second cryptogram that binds said client public key and said symmetric secret key,

c) sending at least said client public key, said registration cryptogram, and said second cryptogram to the registration server entity,

d) supplying identification data elements for the client entity through at least one TLS-type data session instance connected to the registration server entity in which the client entity uses said private key counterpart, and

e) transmitting data between the client entity and a production server entity, after said sending step c) and said supplying step d) are completed, using at least one TLS-type data session instance in which the client entity uses said private key counterpart.

20. The method as in claim 19, where said TLS-type data session instance connected to the registration server entity and said TLS-type data session instance connected to the production server entity use during protocol parameter negotiations a client security certificate chain in which at least one signature uses a private key of which the signature capability is available without authentication formalities to the client entity.

21. The method as in claim 20, where said client security certificate chain is generated at the client entity.

22. The method as in claim 21, where step b) and said generation of client security certificate chain are effected by means of a single software utility.

23. The method as in claim 20, where said client security certificate chain is generated by an on-line service provider.

24. The method as in claim 19, where steps a) and b) are effected by means of a single software utility.

25. The method as in claim 19, where said transmitting step e) is preceded by out-of-band assertions of identification data made by an agent of the client entity.