JDK-8077924 : sun/management/jmxremote/bootstrap/RmiSslBootstrapTest.sh has a dependence on RC4 ciphersuites
  • Type: Bug
  • Component: core-svc
  • Sub-Component: javax.management
  • Affected Version: 9
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2015-04-16
  • Updated: 2024-10-30
  • Resolved: 2015-07-16
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 9
9Resolved
Related Reports
Relates :  
JDK-8076221 - Disable RC4 cipher suites
Sub Tasks
JDK-8077952 :  
sun/management/jmxremote/bootstrap/RmiSslBootstrapTest.sh should be quarantined - Resolved
Description
sun/management/jmxremote/bootstrap/RmiSslBootstrapTest.sh start failing after JDK-8076221:

***
Connection failed for no credentials: java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: 
	javax.net.ssl.SSLHandshakeException: Received fatal alert: handshake_failure
Comments
Duplicated by JDK-8081386
16-07-2015
I updated the test in JDK-8081386 to reset "jdk.tls.disabledAlgorithms", now the test should pass on 9. There is also an enhancement to test more cipher suites in this test, please see JDK-8081518. This bug probably may be closed.
01-06-2015
[~sgupta], please file a new bug. JDK-8043202 is a security-libs bug. This bug is about a regression caused by JDK-8076221, which was never fixed in JDK 6.
28-05-2015
I checked ${JDK}/conf/management/management.properties, and if I understand correctly, there is not default value for com.sun.management.jmxremote.ssl.enabled.cipher.suites property http://docs.oracle.com/javase/8/docs/technotes/guides/management/agent.html That means: - we don't need to update the file to remove RC4 from the property - client code doesn't not make an assumption that RC4 is in the property Taking this into account, I think both ways are okay to fix the test: - reset "jdk.tls.disabledAlgorithms" in test to use RC4 cipher suites - use another enabled cipher suite, for example, SSL_RSA_WITH_3DES_EDE_CBC_SHA I would prefer the first way because even if RC4 cipher suites are disabled by default, they are still supported, and can be enabled.
20-04-2015
jmxremote/bootstrap/* tests use RC4 ciphering suite, which is removed following 8076221.
20-04-2015