×

Method and apparatus for fault tolerant TCP handshaking

  • US 7,454,614 B2
  • Filed: 03/25/2002
  • Issued: 11/18/2008
  • Est. Priority Date: 03/29/2001
  • Status: Expired due to Fees
First Claim
Patent Images

1. A method comprising:

  • receiving a message from a first node in a network at a second node in the network, the second node being one of at least two nodes in a cluster of nodes, the message including a cryptographic sequence number;

    wherein the message was sent by the first node subsequent to an initial message sent by the first node to a third node, and an initial reply sent by the third node to the first node, the third node being in the cluster of nodes,wherein each of the nodes in the cluster stores a cluster wide shared secret, wherein the cluster wide shared secret comprises a private key of the nodes in the cluster,wherein the initial message sent by the first node includes a sequence number, and wherein the initial reply sent by the third node includes a cryptographic sequence number generated by the third node, the cryptographic sequence number generated by replacing a portion of the sequence number received in the initial message with a fingerprint based on the cluster wide shared secret stored at the third node, wherein the fingerprint is generated using an Internet Protocol (IP) address of the first node, a port of the first node, a port of the second node, an IP address of the second node, and the cluster wide shared secret;

    processing the message at the second node to determine that the first node and the third node were involved in a connection setup procedure that has not yet been completed;

    verifying at the second node that the cryptographic sequence number sent by the first node was created by one of the nodes in the cluster, wherein the verifying comprises accessing the cluster wide shared secret stored at the second node, and wherein either;

    the second node builds a connection between the second node and the first node if the cryptographic sequence number was generated based on the cluster wide shared secret; and

    the second node determines that the first node was not legitimately attempting to create a connection with the third node if the cryptographic sequence number was not generated based on the cluster wide shared secret.

View all claims
  • 1 Assignment
Timeline View
Assignment View
    ×
    ×