Cipher suites

Note: In the following list, the string "TLS" can be used instead of "SSL" (but not vice versa) when the cipher suite name is used with these methods: javax.net.SSLEngine.setEnabledCipherSuites, javax.net.ssl.SSLSocket.setEnabledCipherSuites, and javax.net.ssl.SSLParameters.setCipherSuites. In all other situations, the cipher suite name is as listed. You can use the com.ibm.jsse2.overrideDefaultCSName system property to specify whether to use the old cipher suite name (set the property to false, which is the default value) or the Oracle equivalent (set the property to true). For example, some cipher suite names begin with "TLS" when defined by Oracle but "SSL" in the IBM SDK. This difference is due to some cipher names being defined before the finalization of the first TSL specification.

1. TLS_AES_256_GCM_SHA384**¹
2. TLS_AES_128_GCM_SHA256**¹
3. TLS_CHACHA20_POLY1305_SHA256¹
4. SSL_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384** ²
5. SSL_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256²
6. SSL_ECDHE_RSA_WITH_AES_256_GCM_SHA384** ²
7. SSL_ECDHE_RSA_WITH_AES_128_GCM_SHA256²
8. SSL_DHE_RSA_WITH_AES_256_GCM_SHA384** ²
9. SSL_DHE_DSS_WITH_AES_256_GCM_SHA384** ²
10. SSL_DHE_RSA_WITH_AES_128_GCM_SHA256²
11. SSL_DHE_DSS_WITH_AES_128_GCM_SHA256²
12. SSL_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384** ²
13. SSL_ECDHE_RSA_WITH_AES_256_CBC_SHA384** ²
14. SSL_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256²
15. SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA256²
16. SSL_DHE_RSA_WITH_AES_256_CBC_SHA256** ²
17. SSL_DHE_DSS_WITH_AES_256_CBC_SHA256** ²
18. SSL_DHE_RSA_WITH_AES_128_CBC_SHA256²
19. SSL_DHE_DSS_WITH_AES_128_CBC_SHA256²
20. SSL_ECDH_ECDSA_WITH_AES_256_GCM_SHA384** ²
21. SSL_ECDH_RSA_WITH_AES_256_GCM_SHA384** ²
22. SSL_ECDH_ECDSA_WITH_AES_128_GCM_SHA256²
23. SSL_ECDH_RSA_WITH_AES_128_GCM_SHA256²
24. SSL_ECDH_ECDSA_WITH_AES_256_CBC_SHA384** ²
25. SSL_ECDH_RSA_WITH_AES_256_CBC_SHA384** ²
26. SSL_ECDH_ECDSA_WITH_AES_128_CBC_SHA256²
27. SSL_ECDH_RSA_WITH_AES_128_CBC_SHA256²
28. SSL_ECDHE_ECDSA_WITH_AES_256_CBC_SHA**
29. SSL_ECDHE_RSA_WITH_AES_256_CBC_SHA**
30. SSL_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
31. SSL_ECDHE_RSA_WITH_AES_128_CBC_SHA
32. SSL_DHE_RSA_WITH_AES_256_CBC_SHA**
33. SSL_DHE_DSS_WITH_AES_256_CBC_SHA**
34. SSL_DHE_RSA_WITH_AES_128_CBC_SHA
35. SSL_DHE_DSS_WITH_AES_128_CBC_SHA
36. SSL_ECDH_ECDSA_WITH_AES_256_CBC_SHA**
37. SSL_ECDH_RSA_WITH_AES_256_CBC_SHA**
38. SSL_ECDH_ECDSA_WITH_AES_128_CBC_SHA
39. SSL_ECDH_RSA_WITH_AES_128_CBC_SHA
40. SSL_RSA_WITH_AES_256_GCM_SHA384** ²
41. SSL_RSA_WITH_AES_128_GCM_SHA256²
42. SSL_RSA_WITH_AES_256_CBC_SHA256** ²
43. SSL_RSA_WITH_AES_128_CBC_SHA256²
44. SSL_RSA_WITH_AES_256_CBC_SHA**
45. SSL_RSA_WITH_AES_128_CBC_SHA
46. SSL_ECDHE_ECDSA_WITH_3DES_EDE_CBC_SHA³
47. SSL_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA³
48. SSL_RSA_WITH_3DES_EDE_CBC_SHA³
49. SSL_ECDH_ECDSA_WITH_3DES_EDE_CBC_SHA³
50. SSL_ECDH_RSA_WITH_3DES_EDE_CBC_SHA³
51. SSL_DHE_RSA_WITH_3DES_EDE_CBC_SHA³
52. SSL_DHE_DSS_WITH_3DES_EDE_CBC_SHA³
53. TLS_EMPTY_RENEGOTIATION_INFO_SCSV⁴

¹ These cipher suites are available only for TLS 1.3 or later. Use of these suites also requires use of the IBMJCEPlus provider.

² These cipher suites are available only for TLS 1.2.

³ These cipher suites are disabled by jdk.tls.disabledAlgorithms.

⁴ TLS_EMPTY_RENEGOTIATION_INFO_SCSV is a pseudo-cipher suite to support RFC 5746. See Transport Layer Security (TLS) Renegotiation Issue for more information.

** Cipher suites that use AES_256 require the JCE Unlimited Strength Jurisdiction Policy Files.

Note: In the following list, the string "TLS" can be used instead of "SSL" (but not vice versa) when the cipher suite name is used with these methods: javax.net.SSLEngine.setEnabledCipherSuites, javax.net.ssl.SSLSocket.setEnabledCipherSuites, and javax.net.ssl.SSLParameters.setCipherSuites. In all other situations, the cipher suite name is as listed. You can use the com.ibm.jsse2.overrideDefaultCSName system property to specify whether to use the old cipher suite name (set the property to false, which is the default value) or the Oracle equivalent (set the property to true). For example, some cipher suite names begin with "TLS" when defined by Oracle but "SSL" in the IBM SDK. This difference is due to some cipher names being defined before the finalization of the first TSL specification.

1. TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256 ^{1, 6}
2. TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256 ^{1, 6}
3. TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256 ^{1, 6}
4. SSL_DH_anon_WITH_AES_256_GCM_SHA384** ^{1, 4}
5. SSL_DH_anon_WITH_AES_128_GCM_SHA256** ^{1, 4}
6. SSL_DH_anon_WITH_AES_256_CBC_SHA256^{1, 4}
7. SSL_ECDH_anon_WITH_AES_256_CBC_SHA** ⁴
8. SSL_DH_anon_WITH_AES_256_CBC_SHA** ⁴
9. SSL_DH_anon_WITH_AES_128_CBC_SHA256^{1, 4}
10. SSL_ECDH_anon_WITH_AES_128_CBC_SHA⁴
11. SSL_DH_anon_WITH_AES_128_CBC_SHA⁴
12. SSL_ECDH_anon_WITH_3DES_EDE_CBC_SHA⁴
13. SSL_DH_anon_WITH_3DES_EDE_CBC_SHA⁴
14. SSL_ECDHE_ECDSA_WITH_RC4_128_SHA⁵
15. SSL_ECDHE_RSA_WITH_RC4_128_SHA⁵
16. SSL_RSA_WITH_RC4_128_SHA⁵
17. SSL_ECDH_ECDSA_WITH_RC4_128_SHA⁵
18. SSL_ECDH_RSA_WITH_RC4_128_SHA⁵
19. SSL_RSA_WITH_RC4_128_MD5⁵
20. SSL_ECDH_anon_WITH_RC4_128_SHA⁴
21. SSL_DH_anon_WITH_RC4_128_MD5⁴
22. SSL_RSA_WITH_DES_CBC_SHA²
23. SSL_DHE_RSA_WITH_DES_CBC_SHA²
24. SSL_DHE_DSS_WITH_DES_CBC_SHA²
25. SSL_DH_anon_WITH_DES_CBC_SHA^{2, 4}
26. SSL_RSA_EXPORT_WITH_DES40_CBC_SHA³
27. SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA³
28. SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA³
29. SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA^{3, 4}
30. SSL_RSA_EXPORT_WITH_RC4_40_MD5³
31. SSL_DH_anon_EXPORT_WITH_RC4_40_MD5^{3, 4}
32. SSL_DHE_DSS_WITH_RC4_128_SHA³
33. SSL_RSA_WITH_NULL_SHA256¹
34. SSL_ECDHE_ECDSA_WITH_NULL_SHA
35. SSL_ECDHE_RSA_WITH_NULL_SHA
36. SSL_RSA_WITH_NULL_SHA
37. SSL_ECDH_ECDSA_WITH_NULL_SHA
38. SSL_ECDH_RSA_WITH_NULL_SHA
39. SSL_ECDH_anon_WITH_NULL_SHA⁴
40. SSL_RSA_WITH_NULL_MD5
41. SSL_KRB5_WITH_3DES_EDE_CBC_SHA
42. SSL_KRB5_WITH_3DES_EDE_CBC_MD5
43. SSL_KRB5_WITH_RC4_128_SHA
44. SSL_KRB5_WITH_RC4_128_MD5
45. SSL_KRB5_WITH_DES_CBC_SHA²
46. SSL_KRB5_WITH_DES_CBC_MD5²
47. SSL_KRB5_EXPORT_WITH_DES_CBC_40_SHA³
48. SSL_KRB5_EXPORT_WITH_DES_CBC_40_MD5³
49. SSL_KRB5_EXPORT_WITH_RC4_40_SHA³
50. SSL_KRB5_EXPORT_WITH_RC4_40_MD5³

¹ Cipher suites with SHA384 and SHA256 are available only for TLS 1.2.

² RFC 5246 TLS 1.2 forbids the use of these suites. These can be used in the SSLv3/TLS1.0/TLS1.1 protocols, but cannot be used in TLS 1.2 and later.

³ RFC 4346 TLS 1.1 forbids the use of these suites. These can be used in the SSLv3/TLS1.0 protocols, but cannot be used in TLS 1.1 and later.

⁴ Although anonymous cipher suites are enabled, the IBMJSSE2 TrustManager does not allow anonymous cipher suites. The default implementation can be overridden by providing your own TrustManager that allows anonymous cipher suites. See Accepting Anonymous Cipher Suites for information about creating your own X509TrustManager.

⁵ These cipher suites are disabled to mitigate against CVE-2015-2808: Bar Mitzvah security vulnerability.

⁶ Use of the ChaCha suites also requires use of the IBMJCEPlus provider.

** Cipher suites that use AES_256 require the JCE Unlimited Strength Jurisdiction Policy Files.