> # Using SSL Encryption

> If your SequeLink environment requires greater data privacy than that provided by fixed-key DES, fixed-key 3DES, or byteswap, you can use the Secure Socket Layer (SSL) to encrypt data exchanged between the JDBC Client and the SequeLink Server.

> SequeLink supports the use of anonymous ciphers. Anonymous ciphers allow the SSL connection to succeed without proper authentication of the peer by using the DH algorithm. The JDBC Client supports the following cryptographic strong SSL cipher suites:

> - SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
> - SSL_DH_anon_EXPORT_WITH_DES_40_CBC_SHA
> - SSL_DH_anon_WITH_RC4_128_MD5
> - SSL_DH_anon_WITH_DES_CBC_SHA
> - SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
> - TLS_DH_anon_WITH_AES_128_CBC_SHA
> - TLS_DH_anon_WITH_AES_256_CBC_SHA

> The JDBC Client adds a direct encryption mechanism using the `encrypted` option. For example:

>     jdbc:sequelink://mysecurehost:9503;encrypted=1

> This type of encryption is directly configured on the SequeLink Server 6.0 and does not require the use of SequeLink Proxy Server.

> NOTE: In previous releases of SequeLink, encryption for the JDBC Client was configured through the SequeLink Proxy Server. The SequeLink Proxy Server is still used for certificate-based authentication for JDBC applications (see "Configuring the SequeLink® Proxy Server"). The SequeLink Proxy Server is also used to provide SSL encryption when using SequeLink in a DB2 for z/OS environment.

> For details on configuring SSL for SequeLink, see "Configuring SequeLink® Security on Linux, UNIX, and Windows".