JDK-5056170 : Unspecified NPE in Cipher init(int, Key) and init(int, Key,
  • Type: Bug
  • Component: security-libs
  • Sub-Component: javax.crypto
  • Affected Version: 5.0
  • Priority: P3
  • Status: Closed
  • Resolution: Duplicate
  • OS: generic
  • CPU: generic
  • Submitted: 2004-06-02
  • Updated: 2005-05-26
  • Resolved: 2005-05-26
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
6Resolved
Related Reports
Duplicate :  
Description

Name: ipR10067			Date: 06/02/2004




The description of the Cipher.init(int opmode, java.security.Key key)
and Cipher.init(int opmode, java.security.Key key, java.security.SecureRandom 
random)
methods does not describe any exception, but java.security.InvalidKeyException.

However the implementation throws NullPointerException 
when the parameter "key" is null.


======================================================================

Comments
EVALUATION probably too late to fix in tiger, defering this to 1.5.1. ###@###.### 2004-06-03 The fix for bug 5056438 will also fix this, i.e. the modified impl will throw InvalidKeyException instead of NPE just as javadoc specified. Thus, will add this bug id to the fix for 5056438. ###@###.### 2005-1-11 19:24:41 GMT It's probably less confusing to have one fix associated with one bug id. Since the fix is already delivered under bug 5056438, will close this as duplicate instead. ###@###.### 2005-05-26 01:29:28 GMT
26-05-2005

CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: dragon
01-09-2004