Systems and methods for encoding the core identifier in the session identifier

• US 9,654,505 B2
• Filed: 06/22/2009
• Issued: 05/16/2017
• Est. Priority Date: 06/22/2009
• Status: Active Grant

• Current Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Original Assignee: Citrix Systems, Inc. (Cloud Software Group)
• Inventors: Kanekar, Tushar
• Primary Examiner(s): Davis, Zachary A
• Application Number:
  US12/489,325
• Publication Number:
  US 20100325419A1
• Time in Patent Office: 2,885 Days
• Field of Search: 713151, 713160, 713164, 726 3- 7, 726 10, 709227, 709228, 709230, 709237
• CPC Class Codes: H04L 2209/043 of tables, e.g. lookup, substitution or mapping
• CPC Class Codes: H04L 2209/30 Compression, e.g. Merkle-Damgard construction
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 2209/60 Digital content management, e.g. content distribution
• CPC Class Codes: H04L 2209/76 Proxy, i.e. using intermediary entity to perform cryptographic operations
• CPC Class Codes: H04L 2209/80 Wireless
• CPC Class Codes: H04L 63/0464 using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
• CPC Class Codes: H04L 63/0471 applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
• CPC Class Codes: H04L 63/0485 Networking architectures for enhanced packet encryption processing, e.g. offloading of IPsec packet processing or efficient security association look-up
• 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/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 63/166 at the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/1027 Persistence of sessions during load balancing
• CPC Class Codes: H04L 67/1036 Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
• CPC Class Codes: H04L 67/146 Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168
• CPC Class Codes: H04L 9/3268 using certificate validation, registration, distribution or revocation, e.g. certificate revocation list [CRL]
• CPC Class Codes: H04L 9/3271 : using challenge-response
• CPC Class Codes: H04L 9/3297 : involving time stamps, e.g. generation of time stamps

Abstract

The present invention is directed towards systems and methods for managing SSL session persistence and reuse in a multi-core system. A first core may indicate that an SSL session established by the first core is non-resumable. Responsive to the indication, the core may set an indicator at a location in memory accessible by each core of the multi-core system, the indicator indicating that the SSL session is non-resumable. A second core of the multi-core system may receive a request to reuse the SSL session. The request may include a session identifier of the SSL session. In addition, the session identifier may identify the first core as an establisher of the SSL session. The second core can identify from encoding of the session identifier whether the second core is not the establisher of the SSL session. Responsive to the identification, the second core may determine whether to resume the SSL session.

Claims

1. A method of identifying a core establishing a secure socket layer (SSL) connection in a multi-core system via an SSL identifier, the method comprising:

a) receiving, by a packet engine executing on a first core of a multi-core system, a request from a client to establish a secure socket layer (SSL) session with a server via the multi-core system, the first core assigned a core identifier, the multi-core system deployed as an intermediary between the client and the server;

b) determining, by the packet engine executing on the first core, a first session identifier for the SSL session, the first session identifier generated by the server and used by the server and the multi-core system to identify the SSL session established by the multi-core system between the client and the server, the first session identifier communicated from the server to the multi-core system;

c) encoding, by the packet engine, the core identifier in the first session identifier to form a second session identifier, the second session identifier included in communications between the multi-core system and the client;

d) setting, by the packet engine, an indicator of the multi-core system specifying whether the SSL session is resumable;

e) receiving, by the multi-core system, a second request from the client including the second session identifier to access the SSL session;

f) decoding, by the multi-core system, the second session identifier of the second request to obtain the first session identifier; and

g) identifying, by the multi-core system, the SSL session according to the first session identifier decoded from the second session identifier, and determining whether the identified SSL session is resumable based on the indicator of the multi-core system.

2. The method of claim 1, wherein step (a) further comprises assigning the core identifier based on an identifier of a processing unit.

3. The method of claim 1, wherein step (a) further comprises assigning the first core a one-byte core identifier.

4. The method of claim 1, wherein step (b) further comprises generating, by the packet engine, the first session identifier for the SSL session.

5. The method of claim 1, wherein step (b) further comprises obtaining, by the packet engine, the first session identifier from the server.

6. The method of claim 1, wherein step (c) further comprises encoding a byte of the first session identifier with the core identifier to form the second session identifier.

7. The method of claim 1, wherein step (c) further comprises encoding with a block cipher the core identifier and a validity identifier with the first session identifier to form the second session identifier.

8. The method of claim 1, wherein step (c) further comprises encoding the core identifier into a plurality of bits of the first session identifier to form the second session identifier.

9. The method of claim 1, wherein step (c) further comprises determining, by the packet engine, at a predetermined frequency a predetermined set of one or more bytes of the first session identifier to encode to form the second session identifier.

10. The method of claim 1, wherein step (e) comprises receiving, by a second packet engine executing on a second core of the multi-core system, the second request from the client including the second session identifier;

and wherein step (f) further comprises;

decoding, by the second packet engine, the second session identifier to obtain the first session identifier; and

determining, by the second packet engine responsive to the decoding, that the first core established the SSL session.

11. A method of identifying a core establishing a secure socket layer (SSL) connection in a multi-core system via an identifier, the method comprising:

a) receiving, by a packet engine executing on a first core of a multi-core system, a request from a client to establish a secure socket layer (SSL) session with a server, the first core assigned a core identifier, the multi-core system deployed as an intermediary between the client and the server;

b) determining, by the packet engine executing on the first core, a first session identifier for the SSL session, the first session identifier generated by the server and used by the server and the multi-core system to identify the SSL session established by the multi-core system between the client and the server, the first session identifier communicated from the server to the multi-core system;

c) encoding, by the packet engine, the core identifier and a validity identifier in the first session identifier to form a second session identifier, the validity identifier identifying the SSL session as comprising a session for reuse upon establishment of the SSL session, the second session identifier included in communications between the multi-core system and the client;

d) setting, by the packet engine, an indicator of the multi-core system specifying whether the session is resumable;

e) receiving, by the multi-core system, a second request from the client including the second session identifier to access the SSL session;

f) decoding, by the multi-core system, the second session identifier of the second request to obtain the first session identifier; and

g) identifying, by the multi-core system, the SSL session according to the first session identifier decoded from the second session identifier, and determining whether the identified SSL session is resumable based on the indicator of the multi-core system.