-
Bug
-
Resolution: Won't Fix
-
P2
-
6u10
-
None
-
sparc
-
solaris_10
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-2166740 | 7 | Sean Mullan | P4 | Closed | Fixed | b41 |
| JDK-2166696 | 6u10 | Sean Mullan | P2 | Resolved | Fixed | b32 |
| JDK-2186994 | OpenJDK6 | Sean Mullan | P4 | Resolved | Fixed | b18 |
The OCSP validation code should permit some clock skew when checking the validity
of OCSP responses. Currently, the system clock and the OCSP server clock have to
be exactly synchronized or the following exception will be thrown:
throw new IOException("Response is unreliable: its validity " +
"interval is out-of-date");
of OCSP responses. Currently, the system clock and the OCSP server clock have to
be exactly synchronized or the following exception will be thrown:
throw new IOException("Response is unreliable: its validity " +
"interval is out-of-date");
- backported by
-
JDK-2166696 OCSP validation code should permit some clock skew when checking validity of OCSP responses
-
- Resolved
-
-
-
- Resolved
-
-
-
- Closed
-
- relates to
-
JDK-6569795 Don't present security dialog for Sun-signed binaries
-
- Resolved
-
-
-
- Resolved
-