JDK-8215430 : Remove the internal package com.sun.net.ssl
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: javax.net.ssl
  • Priority: P3
  • Status: Resolved
  • Resolution: Fixed
  • Submitted: 2018-12-14
  • Updated: 2024-02-14
  • Resolved: 2019-03-01
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.
JDK 13
13 b11Fixed
Related Reports
CSR :  
Duplicate :  
Relates :  
Relates :  
Relates :  
Relates :  
Relates :  
Sub Tasks
JDK-8219479 :  
The full package "com.sun.net.ssl" had been deprecated since JDK 1.4, and the codes have not been updated for a while. There is only two external dependency of the code.  They are external JSSE provider (Security.java) and the RSA Signature provider (Signature.java).

This package is not exported in the java.base module, and application cannot use them directly any more.  It should be safe to remove them now, and reorg the provider impl code to sun.security.ssl.
Before it was possible to set "from outside" a FIPS crypto provider. This was done that way by our JDK users: >Provider tlsProvider = new com.sun.net.ssl.internal.ssl.Provider("MYFIPS"); >sslCtx = SSLContext.getInstance("TLS", tlsProvider); How should this be done after the com.sun.net.ssl.internal.ssl.Provider removal?

URL: http://hg.openjdk.java.net/jdk/jdk/rev/43c2ab1bdfd3 User: xuelei Date: 2019-03-01 16:35:55 +0000