Details
-
Bug
-
Resolution: Done
-
Critical
-
httpd 2.4.23 ER1, httpd 2.4.23 ER2, httpd 2.4.23 CR5
-
None
-
1
-
Documentation (Ref Guide, User Guide, etc.), Release Notes, User Experience
-
?
Description
Default path to an OpenSSL configuration file seems to be broken. When I try to execute openssl on RHEL or Solaris, OpenSSL looks for the configuration file on absolute path in the system, which seems to be wrong:
WARNING: can't open config file: /opt/rh/jbcs-httpd24/root/etc/pki/tls/openssl.cnf
WARNING: can't open config file: /tmp/xbroot/BUILDROOT/openssl-1.0.2h-3.sun10.x86_64/etc/ssl/openssl.cnf
NOTE: one can workaround that by explicitly specifying own configuration file/path
I think these paths are not correct. It seems that they should be relative to the configuration file provided in zip archive for appropriate architecture - this is the way Windows seems to work (OpenSSL executed from different directory than zip/jbcs-httpd24-2.4/bin/openssl.exe):
WARNING: can't open config file: ../etc/ssl/openssl.cnf
If I execute OpenSSL in expected bin directory, configuration file seems to be loaded properly as no warning is generated then.
Note - there has been created also EAP6.4.10 Natives BZ (where the OpenSSL is actually taken right from the JBCS).