JDK-6787645 : CRL validation code should permit some clock skew when checking validity of CRLs
  • Type: Bug
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 7
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • OS: solaris_10
  • CPU: sparc
  • Submitted: 2008-12-19
  • Updated: 2010-05-06
  • Resolved: 2009-03-07
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 JDK 7
6u14 b03Fixed 7Fixed
Related Reports
Relates :  
JDK-6744888 - OCSP validation code should permit some clock skew when checking validity of OCSP responses
Description
The CRL validation code should permit some clock skew when checking the validity
of CRLs. Currently, the system clock and the CRL server's clock have to be exactly synchronized or the validity check may fail if the system's clock is skewed such that it
is either before the CRL's this update field or after the CRL's next update field.
Comments
EVALUATION Increased the allowable OCSP and CRL validity check clock skew to 15 minutes.
20-02-2009