-
Bug
-
Resolution: Fixed
-
P3
-
7
-
None
-
b77
-
generic
-
generic
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-2184349 | 6u21 | Weijun Wang | P3 | Resolved | Fixed | b01 |
In Kerberos, a server side program saves long term secret keys into a keytab file and uses it to authenticate AP_REQ messages sent by a client. The AP_REQ is encrypted by the KDC using a key stored in KDC's database. The key is identified by an encryption type and a key version number so that the server can locate the correct key from the keytab. Currently, Java only uses encrytion type to search for the key. If there are multiple keys with the same etype for a given server, it's quite likely that a wrong key is returned. The result is that the AP_REQ message cannot be authenticated and checksum error is thrown.
- backported by
-
JDK-2184349 AP_REQ check should use key version number (updated by 6907425)
-
- Resolved
-
- relates to
-
JDK-6913636 kvno check in JSSE
-
- Resolved
-
-
JDK-6895415 backout 6867665
-
- Closed
-
-
JDK-6907425 JCK Kerberos tests fail since b77
-
- Resolved
-
-
JDK-6867665 Problem with keytabs with multiple kvno's (key versions)
-
- Closed
-
-
JDK-6984764 kerberos fails if service side keytab is generated using JDK ktab
-
- Closed
-
(1 relates to)