JDK-8242008 : SSLSession inconsistencies
- Type: Bug
- Component: security-libs
- Sub-Component: javax.net.ssl
- Affected Version: 14
- Priority: P4
- Status: Closed
- Resolution: Fixed
- Submitted: 2020-04-01
- Updated: 2020-12-07
- Resolved: 2020-04-15
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 15 |
|---|
15 b20Fixed  |
Related Reports
|
Relates :
|
|
|
Relates :
|
Description
SSLSessions obtained after an initial connection may return a null value when its getSessionContext() method is called. This appears to happen with both SSLSocket and SSLEngine objects. Pulling the SSLSession after a resumption does return a non-null SSLSessionContext object when getSessionContext is called. Setting jdk.tls.server.enableSessionTicketExtension=false also appears to work around the issue. A modified version of the original reproducer code has been attached. The original reproducer can be found at: https://github.com/normanmaurer/jdk_ssl_session_context_reproducer ---- Also added to this bug not related to netty: - An unnecessary add to the session cache for 1.3 w/ state - Fix to the stateless session data that can corrupt the SSLSession getPeerHost and getPeerPort
Comments
|