JDK-8237977 : Further update javax/net/ssl/compatibility/Compatibility.java
- Type: Bug
- Component: security-libs
- Sub-Component: javax.net.ssl
- Affected Version: 15
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2020-01-28
- Updated: 2021-05-04
- Resolved: 2020-03-25
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 13 | JDK 15 | JDK 8 |
|---|---|---|---|
| 11.0.9-oracleFixed | 13.0.7Fixed | 15 b16Fixed  |
8u-tls13-repoFixed |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
Description
Compatibility.java test currently uses setEnabledProtocols on server side as well to enable one protocol. Instead, test should be updated to use SSLContext to create server socket as this will enable list of protocols and is more likely server configuration to be used. This will also provide additional test coverage from client side. The server side doesn't need to specify the cipher suites either. It also should cover SSLv3. And it's unnecessary to run cases between the jdk builds in jdkList. This test should only focus on the testing JDK build specified by jtreg option "-jdk". Also enhance report to show the cause of failure, either protocol not supported or ciphersuite not supported.
Comments
|