|
Quick Lists
|
|
Bug ID:
|
6787645
|
|
Votes
|
0
|
|
Synopsis
|
CRL validation code should permit some clock skew when checking validity of CRLs
|
|
Category
|
java:classes_security
|
|
Reported Against
|
|
|
Release Fixed
|
6u14(b03)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
3-Medium
|
|
Related Bugs
|
6744888
|
|
Submit Date
|
19-DEC-2008
|
|
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.
Posted Date : 2008-12-19 19:31:22.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Increased the allowable OCSP and CRL validity check clock skew to 15 minutes.
Posted Date : 2009-02-20 15:56:18.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
 |