ENABLING STATELESS SERVER-BASED PRE-SHARED SECRETS

• US 20070288743A1
• Filed: 08/22/2007
• Published: 12/13/2007
• Est. Priority Date: 01/12/2004
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Cam-Winget, Nancy, Zhou, Hao, Salowey, Joseph, McGrew, David, Jakkahalli, Padmanabha
• Granted Patent: US 8,166,301 B2
• Time in Patent Office: Days
• US Class Current: 713/150
• 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/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 9/0822 using key encryption key
• CPC Class Codes: H04L 9/0841 involving Diffie-Hellman or related key agreement protocols

Abstract

A method is disclosed for enabling stateless server-based pre-shared secrets. Based on a local key that is not known to a client, a server encrypts the client'"'"'s state information. The client'"'"'s state information may include, for example, the client'"'"'s authentication credentials, the client'"'"'s authorization characteristics, and a shared secret key that the client uses to derive session keys. By any of a variety of mechanisms, the encrypted client state information is provided to the client. The server may free memory that stored the client'"'"'s state information. When the server needs the client'"'"'s state information, the client sends, to the server, the encrypted state information that the client stored. The server decrypts the client state information using the local key. Because each client stores that client'"'"'s own state information in encrypted form, the server does not need to store any client'"'"'s state information permanently.

Claims

1. A method of storing client states on a client, the method comprising the computer-implemented steps of:

receiving, by the client from a first server, first encrypted state information of the client, wherein the first encrypted state information has been produced by the first server using a first local key that is not known to the client and wherein the first encrypted state information includes a first shared secret key;

sending the first encrypted state information to the first server;

sending a first message that has been encrypted based on a first derived key that was derived from the first shared secret key;

based on the first derived key, further protecting an ensuing first conversation between the client and the first server.

2. A method as recited in claim 1, further comprising storing, at the client, the first encrypted state information that has been received by the client.

3. A method as recited in claim 1, wherein sending the first encrypted state information to the first server includes sending the first encrypted state information in response to receiving a request, from the first server, for the first encrypted state information.

4. A method as recited in claim 1, wherein sending the first encrypted state information to the first server includes sending the first encrypted state information when the client initiates communication with the first server.

5. A method as recited in claim 1, wherein the first encrypted state information includes a lifetime value that indicates a future time at which the first server should deem the first encrypted state information to be expired.

6. A method as recited in claim 1, wherein the first encrypted state information includes a value that uniquely identifies the client.

7. A method as recited in claim 1, further comprising sending, by the client to the first server, an index value that is associated with the local key and an identity of the first server.

8. A method as recited in claim 1, further comprising:

receiving, by the client from a second server, second encrypted state information of the client, wherein the second encrypted state information has been produced by the second server using a second local key that is not known to the client and wherein the second encrypted state information includes a second shared secret key;

sending the second encrypted state information to the second server;

sending a second message that has been encrypted based on a second derived key that was derived from the second shared secret key;

based on the second derived key, further protecting an ensuing second conversation between the client and the second server.

9. A computer-readable storage medium carrying one or more sequences of instructions for storing client states on a client, which instructions, when executed by one or more processors, cause the one or more processors to carry out the steps of:

receiving, by the client from a first server, first encrypted state information of the client, wherein the first encrypted state information has been produced by the first server using a first local key that is not known to the client and wherein the first encrypted state information includes a first shared secret key;

sending the first encrypted state information to the first server;

sending a first message that has been encrypted based on a first derived key that was derived from the first shared secret key;

based on the first derived key, further protecting an ensuing conversation between the client and the first server.

10. An apparatus for storing client states on a client, comprising:

means for receiving, by the client from a first server, first encrypted state information of the client, wherein the first encrypted state information has been produced by the first server using a first local key that is not known to the client and wherein the first encrypted state information includes a first shared secret key;

means for sending the first encrypted state information to the first server;

means for sending a first message that has been encrypted based on a first derived key that was derived from the first shared secret key;

means for further protecting, based on the first derived key, an ensuing conversation between the client and the first server.

11. An apparatus as recited in claim 10, further comprising means for storing, at the client, the first encrypted state information that has been received by the client.

12. An apparatus as recited in claim 10, wherein the first encrypted state information includes a value that uniquely identifies the client.

13. An apparatus for avoiding the storage of client state on a server, comprising:

a network interface that is coupled to a data network for receiving one or more packet flows therefrom;

a processor;

one or more stored sequences of instructions which, when executed by the processor, cause the processor to carry out the steps of;

receiving, by the client from a first server, first encrypted state information of the client, wherein the first encrypted state information has been produced by the first server using a first local key that is not known to the client and wherein the first encrypted state information includes a first shared secret key;

sending the first encrypted state information to the first server;

sending a first message that has been encrypted based on a first derived key that was derived from the first shared secret key;

based on the first derived key, further protecting an ensuing first conversation between the client and the first server.

14. An apparatus as recited in claim 13, wherein the one or more stored sequences of instructions comprise instructions which, when executed by the processor, cause the processor to further carry out storing, at the client, the first encrypted state information that has been received by the client.

15. An apparatus as recited in claim 13, wherein sending the first encrypted state information to the first server includes sending the first encrypted state information in response to receiving a request, from the first server, for the first encrypted state information.

16. An apparatus as recited in claim 13, wherein sending the first encrypted state information to the first server includes sending the first encrypted state information when the client initiates communication with the first server.

17. An apparatus as recited in claim 13, wherein the first encrypted state information includes a lifetime value that indicates a future time at which the first server should deem the first encrypted state information to be expired.

18. An apparatus as recited in claim 13, wherein the first encrypted state information includes a value that uniquely identifies the client.

19. An apparatus as recited in claim 13, wherein the one or more stored sequences of instructions comprise instructions which, when executed by the processor, cause the processor to further carry out sending, by the client to the first server, an index value that is associated with the local key and an identity of the first server.

20. An apparatus as recited in claim 13, wherein the one or more stored sequences of instructions comprise instructions which, when executed by the processor, cause the processor to further carry out:

receiving, by the client from a second server, second encrypted state information of the client, wherein the second encrypted state information has been produced by the second server using a second local key that is not known to the client and wherein the second encrypted state information includes a second shared secret key;

sending the second encrypted state information to the second server;

sending a second message that has been encrypted based on a second derived key that was derived from the second shared secret key;

based on the second derived key, further protecting an ensuing second conversation between the client and the second server.