JDK-8074462 : Handshake messages can be strictly ordered
- Type: Bug
- Component: security-libs
- Sub-Component: javax.net.ssl
- Affected Version: 5.0,6,7,8
- Priority: P2
- Status: Closed
- Resolution: Fixed
- Submitted: 2015-03-05
- Updated: 2019-10-15
- Resolved: 2018-07-24
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 7 | JDK 8 | Other |
|---|---|---|
| 7u211Fixed | 8u191 b03Fixed  |
openjdk7uFixed |
Related Reports
|
Relates :
|
Description
Per the spec of SSL/TLS specification, the handshake message is ordered. We have checked the sequence of key handshake messages. It's better to check the sequence of all handshake messages in case of any state issues.
Comments
|