SSL encryption is available in the following DataDirect Connect Series forODBC drivers:
DB2 Wire Protocol
Greenplum Wire Protocol
MySQL Wire Protocol
Oracle Wire Protocol
PostgreSQL Wire Protocol
Progress OpenEdge Wire Protocol
Salesforce
SQL Server Wire Protocol
Sybase Wire Protocol
Note: Communication between the Salesforce driver and Salesforce.com, Force.com, and Database.com is always SSL encrypted.
SSL works by allowing the client and server to send each other encrypted data that only they can decrypt. SSL negotiates the terms of the encryption in a sequence of events known as the SSL handshake. The drivers support the SSL v2, SSL v3, and TLS v1 protocols using OpenSSL cipher suites, and negotiate the highest SSL/TLS protocol available during the handshake. The result of this negotiation determines the encryption cipher suite to be used for the SSL session.
The encryption cipher suite defines the type of encryption that is used for any data exchanged through an SSL connection. Some cipher suites are very secure and, therefore, require more time and resources to encrypt and decrypt data, while others provide less security, but are also less resource intensive. Refer to "SSL Encryption Cipher Suites" in the DataDirect Connect Series for ODBC Reference for a list of the encryption cipher suites supported by the drivers.
The handshake involves the following types of authentication:
SSL server authentication requires the server to authenticate itself to the client.
SSL client authentication is optional and requires the client to authenticate itself to the server after the server has authenticated itself to the client. Not all databases support SSL client authentication.
DB2 Wire Protocol