Translation of secure communications for handshake protocols

• US 7,302,564 B2
• Filed: 12/24/2003
• Issued: 11/27/2007
• Est. Priority Date: 12/24/2003
• Status: Active Grant

• Current Assignee: Snowflake, Inc.
• Original Assignee: i-net software GmbH
• Inventors: Berlin, Volker Jens
• Primary Examiner(s): Song; Hosuk
• Application Number:
  US10/743,772
• Publication Number:
  US 20050149718A1
• Time in Patent Office: 1,434 Days
• Field of Search: 726 2- 3, 726/14, 713/168, 713/189, 713150-152
• US Class Current: 713/151
• 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/166 at the transport layer

Abstract

Systems and methods of the invention provide translation of secure communications for handshake protocols. A system is provided that includes a first client application, a server application, and a translation component. The first client application is configured to transmit and receive communications via a network. The server application configured to receive queries from at least one client application via the network and to transmit responses to at least one client application via the network. The translation component is configured to receive communications from the first client application and translate the received communications into queries that are understandable to the server application.

Claims

1. A method, comprising:

receiving data transmitted over a network, the receiving occurring via a Java client using a standard secure protocol library including a Java Database Connectivity (JDBC) Type 4 driver;

determining whether a Tabular Data Stream (TDS) handshake protocol is required to handle the received data;

initiating a TDS handshake protocol by the client, if it is determined that a TDS handshake protocol is required;

determining whether the at least one portion of the data is encrypted; and

initiating a secure protocol to handle the at least one portion of the data, if it is determined that the at least one portion of the data is encrypted.

2. The method of claim 1, wherein the initiating a secure protocol includes initiating a secure socket layer (SSL) protocol.

3. The method of claim 1, wherein the client is a pure Java client.

4. The method of claim 1, wherein the standard secure protocol library includes a Java Secure Socket Extension (JSSE).

5. The method of claim 1, wherein the secure protocol includes a secure socket layer (SSL) protocol, and the standard secure protocol library includes a standard SSL library.

6. The method of claim 1, wherein the received data is received from a server that uses a structured query language and a TDS handshake protocol.

7. The method of claim 1, wherein the data is received from a Microsoft Structured Query Language (MS SQL) server.

8. A method, comprising:

receiving data transmitted by a Microsoft Structured Query Language (MS SQL) server over a network, the receiving occurring via a Java client using a standard secure protocol library including a Java Database Connectivity (JDBC) Type 4 driver;

determining whether an MS SQL handshake protocol is required to handle the received data;

initiating an MS SQL handshake protocol by the client, if it is determined that an MS SQL handshake protocol is required;

determining whether the at least one portion of the data is encrypted; and

initiating a secure protocol to handle the at least one portion of the data, if it is determined that the at least one portion of the data is encrypted.

9. The method of claim 8, wherein the initiating a secure protocol includes initiating a secure socket layer (SSL) protocol.

10. The method of claim 8, wherein the client is a pure Java client.

11. The method of claim 8, wherein the standard secure protocol library includes a Java Secure Socket Extension (JSSE).

12. The method of claim 8, wherein the secure protocol includes a secure socket layer (SSL) protocol, and the standard secure protocol library includes a standard SSL library.

13. A processor-readable medium storing code representing instructions to cause a processor to perform a process, the code comprising code to:

receive data transmitted over a network via a Java client using a standard secure protocol library including a Java Database Connectivity (JDBC) Type 4 driver;

determine whether a Tabular Data Stream (TDS) handshake protocol is required to handle the received data;

initiate a TDS handshake protocol by the client, if it is determined that a TDS handshake protocol is required;

determine whether the at least one portion of the data is encrypted; and

initiate a secure protocol to handle the at least one portion of the data, if it is determined that the at least one portion of the data is encrypted.

14. The processor-readable medium of claim 13, wherein the client using a standard secure protocol library includes a pure Java client using a standard secure socket layer (SSL) library.

15. A processor-readable medium storing code representing instructions to cause a processor to perform a process, the code comprising code to:

receive data transmitted by a Microsoft Structured Query Language (MS SQL) server over a network via a Java client using a standard secure protocol library including a Java Database Connectivity (JDBC) Type 4 driver;

determine whether an MS SQL handshake protocol is required to handle the received data;

initiate an MS SQL handshake protocol by the client, if it is determined that an MS SQL handshake protocol is required;

determine whether the at least one portion of the data is encrypted; and

initiate a secure protocol to handle the at least one portion of the data, if it is determined that the at least one portion of the data is encrypted.

16. The processor-readable medium of claim 15, wherein the client using a standard secure protocol library includes a pure Java client using a standard secure socket layer (SSL) library.

17. A method, comprising:

preparing data to be transmitted to a server from a Java client using a standard secure protocol library including a Java Database Connectivity (JDBC) Type 4 driver;

determining if a Tabular Data Stream (TDS) handshake protocol is required to communicate with the server;

initiating a TDS handshake protocol, if it is determined that a TDS handshake protocol is required;

determining if data to be transmitted is to be encrypted using a standard secure protocol associated with the standard secure protocol library; and

initiating the standard secure protocol, if it is determined that the data is to be encrypted using the standard secure protocol.

18. The method of claim 17, further comprising:

transmitting encrypted data using the standard secure protocol.

19. The method of claim 17, wherein the initiating the standard secure protocol includes initiating a secure socket layer (SSL) protocol.

20. The method of claim 17, wherein the client is a pure Java client.

21. The method of claim 17, wherein the standard secure protocol library includes a Java Secure Socket Extension (JSSE).

22. The method of claim 17, wherein the standard secure protocol includes a secure socket layer (SSL) protocol, and the standard secure protocol library includes a standard SSL library.

23. The method of claim 17, wherein the data is received from a Microsoft Structured Query Language (MS SQL) server.

24. A method, comprising:

preparing data to be transmitted to a server from a Java client using a standard secure protocol library including a Java Database Connectivity (JDBC) Type 4 driver;

determining if a Microsoft Structured Query Language (MS SQL) server handshake protocol is required to communicate with the server;

initiating an MS SQL handshake protocol, if it is determined that an MS SQL handshake protocol is required;

determining if data to be transmitted is to be encrypted using a standard secure protocol associated with the standard secure protocol library; and

initiating the standard secure protocol, if it is determined that the data is to be encrypted using the standard secure protocol.

25. The method of claim 24, further comprising:

transmitting encrypted data using the standard secure protocol.

26. The method of claim 24, wherein the initiating the standard secure protocol includes initiating a secure socket layer (SSL) protocol.

27. The method of claim 24, wherein the client is a pure Java client.

28. The method of claim 24, wherein the standard secure protocol library includes a Java Secure Socket Extension (JSSE).

29. The method of claim 24, wherein the standard secure protocol includes a secure socket layer (SSL) protocol, and the standard secure protocol library includes a standard SSL library.

30. A processor-readable medium storing code representing instructions to cause a processor to perform a process, the code comprising code to:

prepare data to be transmitted to a server from a Java client using a standard secure protocol library including a Java Database Connectivity (JDBC) Type 4 driver;

determine if a Tabular Data Stream (TDS) handshake protocol is required to communicate with the server;

initiate a TDS handshake protocol, if it is determined that a TDS handshake protocol is required;

determine if data to be transmitted is to be encrypted using a standard secure protocol associated with the standard secure protocol library; and

initiate the standard secure protocol, if it is determined that the data is to be encrypted using the standard secure protocol.

31. The processor-readable medium of claim 30, wherein the client using a standard secure protocol library includes a pure Java client using a standard secure socket layer (SSL) library.

32. A processor-readable medium storing code representing instructions to cause a processor to perform a process, the code comprising code to:

prepare data to be transmitted to a server from a Java client using a standard secure protocol library including a Java Database Connectivity (JDBC) Type 4 driver;

determine if a Microsoft Structured Query Language (MS SQL) server handshake protocol is required to communicate with the server;

initiate an MS SQL handshake protocol, if it is determined that an MS SQL handshake protocol is required;

determine if data to be transmitted is to be encrypted using a standard secure protocol associated with the standard secure protocol library; and

initiate the standard secure protocol, if it is determined that the data is to be encrypted using the standard secure protocol.

33. The processor-readable medium of claim 32, wherein the client using a standard secure protocol library includes a pure Java client using a standard secure socket layer (SSL) library.

34. A system, comprising:

a first client application configured to transmit and to receive secure communications via a network using a standard secure protocol library, the secure communications including queries sent by the first client application and responses received by the first client application;

a server application configured to receive the queries sent by the first client application via the network and to transmit the responses received by the first client application via the network, the server application requiring a proprietary server handshake protocol to communicate with the first client application using a standard secure protocol associated with the standard secure protocol library;

a translation component configured to receive the queries sent by the first client application and to translate the queries into queries that use the proprietary server handshake protocol of the server application so that they are understandable to the server application, the translation component further configured to receive the responses transmitted by the server application and to translate the responses into responses that do not require use of the proprietary server handshake protocol such that they are understandable by the first client.

35. The system of claim 34, wherein the standard secure protocol library includes a standard secure socket layer (SSL) library.

36. The system of claim 34, wherein the first client application includes a pure Java client.

37. The system of claim 34, wherein the first client application includes a Java client using a Java Database Connectivity (JDBC) Type 4 driver.

38. The system of claim 34, wherein the standard secure protocol library includes a Java Secure Socket Extension (JSSE).

39. The system of claim 34, wherein the server application uses a structured query language and the proprietary server handshake protocol includes a Tabular Data Stream (TDS) handshake protocol.

40. The system of claim 34, wherein the server application is a Microsoft Structured Query Language (MS SQL) server and the proprietary server handshake protocol includes an MS SQL server handshake protocol.

41. The system of claim 34, wherein the first client application is further configured to communicate using sockets, the server application is configured to communicate using named pipes, and the translation component is configured to translate communications between sockets and named pipes.

42. An apparatus, comprising:

a secure data communication object configured to receive secure communication data as input and to output secure communication data;

a socket communication object configured to receive socket communication data as input and to output socket communication data;

a named pipe communication object configured to receive named pipe communication data as input and to output named pipe communication data; and

a translation communication object in communication with each of the secure data communication object, the socket communication object, and the named pipe communication object, the translation communication object configured to translate named pipe communication data received via the named pipe communication object for handling by the secure data communication object, the translation communication object being further configured to send socket communication data received via the socket communication object to the secure data communication object, the translation communication object including a Tabular Data Stream (TDS) handshake object configured to perform a TDS handshake with a TDS client, the TDS handshake object further configured to translate TDS data to a non-TDS data format and non-TDS data to TDS data format.

43. The apparatus of claim 42, wherein the translation component is further configured to translate secure communication data received via the secure communication object for handling by the named pipe communication object, the translation communication object being further configured to send secure communication data received via the secure communication object to the socket data communication object.

44. The apparatus of claim 42, wherein the secure communication object includes a Secure Socket Layer (SSL) communication object.

45. The apparatus of claim 42, wherein the secure communication object includes a Java client using a standard Secure Socket Layer (SSL) library.

46. A method, comprising:

receiving data transmitted over a network, the receiving occurring via a client using a standard secure protocol library, the standard secure protocol library including a Java Secure Socket Extension (JSSE);

detennining whether a Tabular Data Stream (TDS) handshake protocol is required to handle the received data;

initiating a TDS handshake protocol by the client, if it is determined that a TDS handshake protocol is required;

determining whether the at least one portion of the data is encrypted; and

initiating a secure protocol to handle the at least one portion of the data, if it is determined that the at least one portion of the data is encrypted.

47. A method, comprising:

receiving data transmitted by a Microsoft Structured Query Language (MS SQL) server over a network, the receiving occurring via a client using a standard secure protocol library, the standard secure protocol library including a Java Secure Socket Extension (JSSE);

determining whether an MS SQL handshake protocol is required to handle the received data;

initiating an MS SQL handshake protocol by the client, if it is determined that an MS SQL handshake protocol is required;

determining whether the at least one portion of the data is encrypted; and

initiating a secure protocol to handle the at least one portion of the data, if it is determined that the at least one portion of the data is encrypted.

48. A method, comprising:

preparing data to be transmitted to a server from a client using a standard secure protocol library, the standard secure protocol library including a Java Secure Socket Extension (JSSE);

determining if a Tabular Data Stream (TDS) handshake protocol is required to communicate with the server;

initiating a TDS handshake protocol, if it is determined that a TDS handshake protocol is required;

determining if data to be transmitted is to be encrypted using a standard secure protocol associated with the standard secure protocol library; and

initiating the standard secure protocol, if it is determined that the data is to be encrypted using the standard secure protocol.

49. A method, comprising:

preparing data to be transmitted to a server from a client using a standard secure protocol library, the standard secure protocol library including a Java Secure Socket Extension (JSSE);

determining if a Microsoft Structured Query Language (MS SQL) server handshake protocol is required to communicate with the server;

initiating an MS SQL handshake protocol, if it is determined that an MS SQL handshake protocol is required;

determining if data to be transmitted is to be encrypted using a standard secure protocol associated with the standard secure protocol library; and

initiating the standard secure protocol, if it is determined that the data is to be encrypted using the standard secure protocol.

50. A system, comprising:

a first client application configured to transmit and to receive secure communications via a network using a standard secure protocol library, the first client application including a Java client using a Java Database Connectivity (JDBC) Type 4 driver, the secure communications including queries sent by the first client application and responses received by the first client application;

a server application configured to receive the queries sent by the first client application via the network and to transmit the responses received by the first client application via the network, the server application requiring a proprietary server handshake protocol to communicate with the first client application using a standard secure protocol associated with the standard secure protocol library;

a translation component configured to receive the queries sent by the first client application and to translate the queries into queries that use the proprietary server handshake protocol of the server application so that they are understandable to the server application.

51. A system, comprising:

a first client application configured to transmit and to receive secure communications via a network using a standard secure protocol library, the standard secure protocol library including a Java Secure Socket Extension (JSSE), the secure communications including queries sent by the first client application and responses received by the first client application;

a server application configured to receive the queries sent by the first client application via the network and to transmit the responses received by the first client application via the network, the server application requiring a proprietary server handshake protocol to communicate with the first client application using a standard secure protocol associated with the standard secure protocol library;

a translation component configured to receive the queries sent by the first client application and to translate the queries into queries that use the proprietary server handshake protocol of the server application so that they are understandable to the server application.

52. A system, comprising:

a first client application configured to transmit and to receive secure communications via a network using a standard secure protocol library, the secure communications including queries sent by the first client application and responses received by the first client application;

a server application configured to receive the queries sent by the first client application via the network and to transmit the responses received by the first client application via the network, the server application requiring a proprietary server handshake protocol to communicate with the first client application using a standard secure protocol associated with the standard secure protocol library;

a translation component configured to receive the queries sent by the first client application and to translate the queries into queries that use the proprietary server handshake protocol of the server application so that they are understandable to the server application,

the first client application configured to communicate using sockets, the server application is configured to communicate using named pipes, and the translation component is configured to translate communications between sockets and named pipes.

53. An apparatus, comprising:

a secure data communication object configured to receive secure communication data as input and to output secure communication data;

a socket communication object configured to receive socket communication data as input and to output socket communication data;

a named pipe communication object configured to receive named pipe communication data as input and to output named pipe communication data; and

a translation communication object in communication with each of the secure data communication object, the socket communication object, and the named pipe communication object, the translation communication object configured to translate named pipe communication data received via the named pipe communication object for handling by the secure data communication object, the translation communication object being further configured to send socket communication data received via the socket communication object to the secure data communication object, the translation component being further configured to translate secure communication data received via the secure communication object for handling by the named pipe communication object, the translation communication object being further configured to send secure communication data received via the secure communication object to the socket data communication object.