JDK-8015275 : Resolve ambiguity in OCSPChecker & CrlRevocationChecker
  • Type: Bug
  • Status: Closed
  • Resolution: Fixed
  • Component: security-libs
  • Sub-Component: java.security
  • Priority: P3
  • Affected Version: 7
  • Submit Date: 2013-05-23
  • Updated Date: 2013-09-04
  • Resolved Date: 2013-05-24
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.
JDK 7
7u40 b28Fixed
Description
Reported by Andrew on the OpenJDK 7u-dev mailing list : 

====

Webrev: http://cr.openjdk.java.net/~andrew/7u/webrev/

There's an ambiguity that applies when building OpenJDK 7 with OpenJDK 6
(and hence I haven't posted this for 8 as it can't be built with 6).

OpenJDK 6 has a class sun.security.provider.certpath.CertificateRevokedException.
OpenJDK 7 has a class java.security.cert.CertificateRevokedException.

Two classes in sun.security.provider.certpath in OpenJDK 7 import
java.security.cert.CertificateRevokedException indirectly via
java.security.cert.*.  This appears to cause a compilation failure
in some cases if the ambiguity is resolved to the CertificateRevokedException
in the bootstrap JDK instead of the new one in java.security.cert.

This is easily fixed by explicitly importing the classes required as in the
above webrev.

Is this ok for 7u?  If so, can I have a bug ID for it?

====
Comments
noreg-other : build time change. changed classes were removed in JDK 8 : changeset: 5475:0c6830e7241f parent: 4964:d383b5d128e3 user: mullan date: Wed May 30 17:19:46 2012 -0400 summary: 6854712: Revocation checking enhancements (JEP-124)
2013-05-23