JDK-8201627 : Kerberos sequence number issues
- Type: Bug
- Component: security-libs
- Sub-Component: org.ietf.jgss:krb5
- Affected Version: 6-pool,7-pool,8,8-pool,11
- Priority: P3
- Status: Closed
- Resolution: Fixed
- Submitted: 2018-04-17
- Updated: 2020-02-26
- Resolved: 2018-05-19
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 11 | JDK 7 | JDK 8 | Other |
|---|---|---|---|
11 b15Fixed  |
7u251Fixed | 8u241Fixed |
openjdk7uFixed |
Related Reports
|
CSR :
|
Sub Tasks
|
JDK-8202681 :
|
Description
MessageToken_v2 is not reading the correct sequence number and InitSecContextToken has a problem set the peer's initial sequence number when mutual auth is off.
Comments
|