-
Bug
-
Resolution: Done
-
Minor
-
7.1.0.DR6
Version of wildfly-openssl used: 1.0.0.Alpha1.
When I set in EAP protocol to 'openssl.TLS' in /core-service=management/security-realm=ApplicationRealm/server-identity=ssl and start with:
./bin/standalone.sh
I can see printed version of used OpenSSL - OpenSSL version 1000207f in the server output in teminal. My version of OpenSSL in the system is OpenSSL 1.0.2j-fips 26 Sep 2016. Thus I am not sure how the version of openssl matches here (the 'j' character vs '7f').
When I use different location of prepared OpenSSL (version 1.0.2b) and start server again with:
LD_LIBRARY_PATH="/tmp/openssl-102b/lib" ./bin/standalone.sh -Dorg.wildfly.openssl.path=/tmp/openssl-102b/lib/
I can see that version of OpenSSL used that is printed in the terminal has not changed and still is OpenSSL version 1000207f
Problems I see:
- version of my OpenSSL is 1.0.2j-fips vs printed in terminal 1000207f <--- expected 100020af
- version of my OpenSSL is 1.0.2b vs printed in terminal 1000207f <--- expected 1000202f
EDIT: for clarification - added what versions I would expect; maybe I just badly interpreted given version...
- is incorporated by
-
JBEAP-6556 (7.1.0) Upgrade to WildFly Core 3.0.0.Alpha12
- Closed