Skip to content
Advertisement

Java 11.0.11 SSL handshake fails with exception ‘No common named group’

We have developed a server application in Java 11 that accepts incoming HTTPS connections from clients. All was working fine up to/including Java 11.0.10 (AdoptOpenJDK).

After an upgrade to Java 11.0.11 we are having connection handshake issues (javax.net.ssl.SSLProtocolException: No common named group) with connections from Chrome clients. Firefox clients have no problems.
After enabling SSL logs (-Djavax.net.debug=ssl:handshake) we can see a difference between the 2 versions:

with 11.0.11:

JavaScript

with 11.0.10:

JavaScript

The new Java version seems to ignore the request for x25519.
Both Java runtimes are unchanged downloads from AdoptOpenJDK.

Here are some more detailed logs:

Fail from Chrome for Java 11.0.11:

JavaScript

Success from Chrome for Java 11.0.10:

JavaScript

Java 11.0.11 seems to have dropped out-of-the-box support for TLSv1 and TLSv1.1, but I am not sure if this is related. Enabling these do not solve the problem.

Any idea why x25519 is not supported anymore? Or how to enable it?

Advertisement

Answer

The cause of the problem was a single jar file in the module path. The jar itself was not related to networking, encryption or security, it was for changing UI look-and-feel. The jar was signed 7 years ago and it has not caused any problems before. Replacing this jar with an unsigned copy resolves all problems and makes Java 11.0.11 fully operational again, presenting the expected list of security providers (13 instead of 4).

Why this problem happened only on Java 11.0.11 remains a mystery. I did not see any error messages from the Java classloaders.

User contributions licensed under: CC BY-SA
7 People found this is helpful
Advertisement