-
Enhancement
-
Resolution: Fixed
-
P4
-
6u26, 7
-
b97
-
generic, x86
-
generic, windows_xp
-
Not verified
Recently I notice a Kerberos test fails on CYGWIN saying an AP-REQ is a "replay detected". It turns out that the Windows time (returned by new Date()) is too coarse (15 millisecond precision) and the two AP-REQs in the test have the same KerberosTime value.
Also, the KerberosTime class is the source of microseconds value used in Authenticator etc. Since Date only provides milliseconds, this means even if on a system with ideal Date, the microsecond value is always a multiple of 1000.
Also, the KerberosTime class is the source of microseconds value used in Authenticator etc. Since Date only provides milliseconds, this means even if on a system with ideal Date, the microsecond value is always a multiple of 1000.
- duplicates
-
JDK-6950930 test failure windows sun/security/krb5/auto/IgnoreChannelBinding.java
-
- Closed
-
-
JDK-7085018 Kerberos replay attack detection due to low JDK clock resolution
-
- Closed
-
- relates to
-
JDK-7077172 KerberosTime does not take into account system clock adjustement
-
- Closed
-
-
JDK-2217345 KerberosTime does not take into account system clock adjustement
-
- Closed
-