-
Bug
-
Resolution: Done
-
Major
-
10.0.0.Final
-
None
-
$ java -version openjdk version "1.8.0_222" OpenJDK Runtime Environment (build 1.8.0_222-b10) OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) $ openssl version OpenSSL 1.1.1d FIPS 10 Sep 2019 $ uname -r 5.3.6-200.fc30.x86_64
Note, I can see same behaviour also with JDK-11:
$ java -version java version "11.0.1" 2018-10-16 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
$ java -version openjdk version "1.8.0_222" OpenJDK Runtime Environment (build 1.8.0_222-b10) OpenJDK 64-Bit Server VM (build 25.222-b10, mixed mode) $ openssl version OpenSSL 1.1.1d FIPS 10 Sep 2019 $ uname -r 5.3.6-200.fc30.x86_64 Note, I can see same behaviour also with JDK-11: $ java -version java version "11.0.1" 2018-10-16 LTS Java(TM) SE Runtime Environment 18.9 (build 11.0.1+13-LTS) Java HotSpot(TM) 64-Bit Server VM 18.9 (build 11.0.1+13-LTS, mixed mode)
The 'enabled-protocols' attribute in legacy security seems not to be working if 'openssl.TLS' provider is in use. If regular JSSE provider with 'TLS' value is in use, it is working just fine, although not in case 'openssl.TLS'. See more info in reproduction steps.
- is incorporated by
-
WFCORE-4878 Upgrade WildFly OpenSSL to 1.0.10.Final
-
- Closed
-
- is related to
-
JBEAP-17893 TLSv1.3 via wildfly-openssl discrepancy between JBoss EAP and WildFly
-
- Closed
-
- relates to
-
JBEAP-14270 [GSS] (7.2.z) HTTP/2 with openssl library not working for openssl.TLSv1 or openssl.TLSv1.1
-
- Closed
-