JDK-4936763 : Diffie Hellman Key Agreement doesn't generate keys for AES cipher
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: javax.crypto
  • Affected Version: 1.4.2,5.0
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: windows_xp
  • CPU: x86
  • Submitted: 2003-10-13
  • Updated: 2018-04-16
  • Resolved: 2005-09-16
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 Availability Release.

To download the current JDK release, click here.
JDK 6
6 betaFixed
Related Reports
Duplicate :  
Relates :  
Description
Name: rmT116609			Date: 10/13/2003


A DESCRIPTION OF THE REQUEST :
Since there is AES support in the JCE which is included in J2SE 1.4.2 I think there has to be AES support for the KeyAgreement generateSecret Method.

JUSTIFICATION :
AES Support for DH Key Exchangement is worth to be implemented.

EXPECTED VERSUS ACTUAL BEHAVIOR :
EXPECTED -
I hope there will be AES support in next Version of JCE whizch can be userd with a KeyAgreement. Example: ka.generateSecret("AES-128").
ACTUAL -
Throws a NoSuchAlgorithmException
(Incident Review ID: 192051) 
======================================================================

Comments
WORK AROUND The last line of the workaround code listed above should read: SecretKey key = new SecretKeySpec(secret, 0, 16, "AES");
22-09-2005

EVALUATION Will fix. Note that the strongest key will be generated regardless of the currently installed jurisdiction policy file. This is also the case for blowfish (a various key length cipher algorithm).
09-09-2005

WORK AROUND ###@###.### 2003-10-21 Simple workaround: KeyAgreement ka = KeyAgreement.getInstance("DH"); ... byte[] secret = ka.generateSecret(); SecretKey key = new SecretKeySpec(secret, 0, 128, "AES");
21-10-2003

EVALUATION ###@###.### 2003-10-21 The requested functionality can easily be accomplished by only one additional line. Please see under "Work Around" section. Probably will fix this in a post-tiger release.
21-10-2003