JSSE Oracle Provider Default Disabled TLS Cipher Suites

The following TLS cipher suites are supported by Oracle provider, SunJSSE. These cipher suites are disabled by default because of one of the following reasons:
  • obsoleted weak cipher suites
  • anonymous cipher suites
  • no encryption cipher suites (null cipher)
  • Kerberos cipher suites
Cipher suites for Kerberos (KRB5) need additional KRB5 service configuration, and these cipher suites are not common in practice.

You are NOT supposed to use these cipher suites unless you really know what you're doing from a standpoint.

Perference Value Description
1 0x00,0x6D TLS_DH_anon_WITH_AES_256_CBC_SHA256
2 0xC0,0x19 TLS_ECDH_anon_WITH_AES_256_CBC_SHA
3 0x00,0x3A TLS_DH_anon_WITH_AES_256_CBC_SHA
4 0x00,0x6C TLS_DH_anon_WITH_AES_128_CBC_SHA256
5 0xC0,0x18 TLS_ECDH_anon_WITH_AES_128_CBC_SHA
6 0x00,0x34 TLS_DH_anon_WITH_AES_128_CBC_SHA
7 0xC0,0x16 TLS_ECDH_anon_WITH_RC4_128_SHA
8 0x00,0x18 SSL_DH_anon_WITH_RC4_128_MD5
9 0xC0,0x17 TLS_ECDH_anon_WITH_3DES_EDE_CBC_SHA
10 0x00,0x1B SSL_DH_anon_WITH_3DES_EDE_CBC_SHA
11 0xC0,0x3B TLS_RSA_WITH_NULL_SHA256
12 0xC0,0x06 TLS_ECDHE_ECDSA_WITH_NULL_SHA
13 0xC0,0x10 TLS_ECDHE_RSA_WITH_NULL_SHA
14 0x00,0x02 SSL_RSA_WITH_NULL_SHA
15 0xC0,0x01 TLS_ECDH_ECDSA_WITH_NULL_SHA
16 0xC0,0x05 TLS_ECDH_RSA_WITH_NULL_SHA
17 0x00,0x15 TLS_ECDH_anon_WITH_NULL_SHA
18 0x00,0x01 SSL_RSA_WITH_NULL_MD5
19 0x00,0x09 SSL_RSA_WITH_DES_CBC_SHA
20 0x00,0x15 SSL_DHE_RSA_WITH_DES_CBC_SHA
21 0x00,0x12 SSL_DHE_DSS_WITH_DES_CBC_SHA
22 0x00,0x03 SSL_RSA_EXPORT_WITH_RC4_40_MD5
23 0x00,0x17 SSL_DH_anon_EXPORT_WITH_RC4_40_MD5
24 0x00,0x08 SSL_RSA_EXPORT_WITH_DES40_CBC_SHA
25 0x00,0x14 SSL_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA
26 0x00,0x11 SSL_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA
27 0x00,0x19 SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA
28 0x00,0x32 TLS_DHE_DSS_WITH_AES_128_CBC_SHA
29 0x00,0x20 TLS_KRB5_WITH_RC4_128_SHA
30 0x00,0x24 TLS_KRB5_WITH_RC4_128_MD5
31 0x00,0x1F TLS_KRB5_WITH_3DES_EDE_CBC_SHA
32 0x00,0x23 TLS_KRB5_WITH_3DES_EDE_CBC_MD5
33 0x00,0x1E TLS_KRB5_WITH_DES_CBC_SHA
34 0x00,0x22 TLS_KRB5_WITH_DES_CBC_MD5
35 0x00,0x28 TLS_KRB5_EXPORT_WITH_RC4_40_SHA
36 0x00,0x2B TLS_KRB5_EXPORT_WITH_RC4_40_MD5
37 0x00,0x26 TLS_KRB5_EXPORT_WITH_DES_CBC_40_SHA
38 0x00,0x29 TLS_KRB5_EXPORT_WITH_DES_CBC_40_MD5

Note that the data was from the Java SE doc of SunJSSE provider.

Popular posts from this blog

TLS Server Name Indication Extension and Unrecognized_name

Image
Heavy Pond, Jianfengling National Forest Park, Ledong, Hainan, China It's getting hot that some TLS/HTTPS server failed with "unrecognized_name". For example, the Adobe AIR 3 Code Signing Certificate Problem , the ADT handshake alert , and the jarsigner issue with timestamp.geotrust.com , etc. This entry will discussion some background of the "unrecognized_name" alert, and the TLS Server Name Indication (SNI) extension. Background "Unrecognized_name" is an error alert, define by RFC4366 .  In section 4 of RFC4366 : - "unrecognized_name": this alert is sent by servers that receive a server_name extension request, but do not recognize the server name. This message MAY be fatal. And in section 3.1 of of RFC4366 : If the server understood the client hello extension but does not recognize the server name, it SHOULD send an "unrecognized_name" alert (which MAY be fatal). From above sections, we see that "unrecognized...
Read more

Java™ SE 7 Release Security Enhancements - Weak Cryptography Control

Weak cryptographic algorithms can now be disabled in Java SE 7 release. The MD2 Message-Digest Algorithm was disabled by default in Sun PKIX provider and SunJSSE provider. The MD2 algorithm is a cryptographic hash function developed by Ronald Rivest in 1989 , and was published in 1992 as an Informational RFC (RFC 1319) .; RFC 6149 moves RFC 1319/MD2 to historic status, "Since its publication, MD2 has been shown to not be collision-free, albeit successful collision attacks for properly implemented MD2 are not that damaging. Successful pre-image and second pre-image attacks against MD2 have been shown." Although MD2 is no longer considered secure, it remains in use in public key infrastructures as part of certificates generated with MD2 and RSA. An a countermeasure of the vulnerability, Java SE has disabled MD2 algorithm in certification path building and validation. You may wonder, Java SE has disabled MD2 algorithm in certification path building and validation in ...
Read more

JEP 115: AES-GCM CipherSuites in JDK 8

Image
Chengdu, China RFC 5288 describes the use of AES in Galois Counter Mode ( GCM ) (AES-GCM) with various key exchange mechanisms as a cipher suite for TLS. AES-GCM is an authenticated encryption with associated data (AEAD) cipher (as defined in TLS 1.2 ) providing both confidentiality and data origin authentication. Java SE had already defined the AES-GCM interfaces in Java SE 7 .  In the coming Java SE 8, as an implementation of JEP 115 , AES-GCM algorithms is implemented in SunJCE provider, and AES-GCM cipher suites are implemented in SunJSSE provider. The following SSL/TLS AEAD/GCM cipher suites, in preference order, are enabled by default in SunJSSE provider for TLS version 1.2: TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (RFC 5289) TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (RFC 5289) TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (RFC 5289) TLS_RSA_WITH_AES_256_GCM_SHA384 (RFC 5288) TLS_ECDH_ECDSA_WITH_AES_256_GCM_SHA384 (RFC 5289) TLS_ECDH_RSA_WITH_AES_...
Read more