-
Type:
Sub-task
-
Resolution: Delivered
-
Priority:
P4
-
Affects Version/s: 7u251, 8u241, 11
-
Component/s: security-libs
-
Verified
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8246012 | 8u241 | Clifford Wayne | P4 | Resolved | Delivered | |
| JDK-8246011 | 7u251 | Clifford Wayne | P4 | Resolved | Delivered |
Previously, when mutual authentication was not requested by the Kerberos 5 initiator, there was no mechanism to negotiate the acceptor's initial sequence number. With this release, if the system property `sun.security.krb5.acceptor.sequence.number.nonmutual` is set to `initiator`, the SunJGSS provider will use the initiator's initial sequence number as the acceptor's initial sequence number. If set to `zero` or `0`, 0 is used. The default value is `initiator`. All other values are illegal and will throw an Error when the system property is read.
- backported by
-
JDK-8246011 Release Note: Kerberos Sequence Number Issues
-
- Resolved
-
-
JDK-8246012 Release Note: Kerberos Sequence Number Issues
-
- Resolved
-