JDK-6996769 : support AEAD ciphers
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: javax.crypto
  • Affected Version: 7
  • Priority: P2
  • Status: Closed
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2010-11-02
  • Updated: 2018-01-09
  • Resolved: 2013-01-08
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availabitlity Release.

To download the current JDK release, click here.
7u181Unresolved 8 b73Fixed
Related Reports
Blocks :  
Relates :  
Relates :  
Relates :  
Relates :  
TLS 1.2 [RFC 5246] defines AEAD (CCM/GCM) cipher structures, and RFC 5288/5289 defines GCM cipher suite specs.

According to "Suite B Profile for Transport Layer Security" [RFC 5430], "A Suite B compliant TLS version 1.2 or later client MUST offer at least two cipher suites for each supported security level.  For the 128-bit security level, TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 and TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA256 MUST be offered in this order in the ClientHello message.  For the 192-bit security level, TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 and TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA384 MUST be offered in this order in the ClientHello message.  One of these cipher suites MUST be the first (most preferred) cipher suite in the ClientHello message."

In order to be Suite-B compliant, GCM ciphers need to be supported in the default JSSE provider.

Test development for this feature is complete. Issues are being tracked by seperate issues. Marking this as verified.

Not following Nithya's request for this specific issue. AEAD were put in quite some time ago. AEAD Ciphersuites were pulled out due to a project developed in parallel, but then put back in.

written to brad, asking if the changes are put back in the repo

pending verification due to JDK-8009925

EVALUATION We'll see if there is time for JDK 7, but may need to wait for the next release.