JDK-5091352 : Allow null localKeyID attribute in pkcs12 with one private key
  • Type: Bug
  • Component: security-libs
  • Sub-Component: javax.net.ssl
  • Affected Version: 6
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: sparc
  • Submitted: 2004-08-24
  • Updated: 2004-10-12
  • Resolved: 2004-09-10
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.
Other JDK 6
5.0u1Fixed 6 mustangFixed
Description
Currently our pkcs12 implementation requires localKeyID attribute
for the private key, and the corresponding end-entity certificate,
in order to match the public/private key pair.

However, in the case of pkcs12, which has only one private key with the
associated certificate chain, we could relax this restriction, and allow
entries with null localKeyID.

Note: This request comes from Borland. See comments for details.
###@###.### 10/12/04 16:44 GMT
Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: 1.5.0_01 mustang FIXED IN: mustang INTEGRATED IN: mustang
23-09-2004
EVALUATION ###@###.### 2004-08-24 Will fix it. ###@###.### 2004-09-03 Have fixed to allow null localKeyID when there is only one private key entry in pkcs12, with associated cert-chain.
24-08-2004