I am try to generate a CSR on CentOS 6 based on the Splunk admin documentation for "Generate a CSR". I used the following command:
Command
$SPLUNK_HOME/bin/openssl req -newkey rsa:2048 -key [certificate name].pem -out [certificate name].csr
Result
$SPLUNK_HOME/bin/openssl: error while loading shared libraries: libssl.so.0.9.8: cannot open shared object file: No such file or directory
The $SPLUNK_HOME/lib/ shows the following in the directory ...
lrwxrwxrwx 1 splunk splunk 15 Sep 29 10:53 libssl.so -> libssl.so.0.9.8
-r-xr-xr-x 1 splunk splunk 324464 Sep 8 15:54 libssl.so.0.9.8
If you do not use Splunk's own packaged libraries then you will have circumvented the defects and security fixes that have been addressed with Splunk's use of those dependent libraries, i.e. those identified in the Splunk release notes.
I would add the Splunk library path, /opt/splunk/lib, as one line into a text file (such as spunk.conf) and place that file in the /etc/ld.so.conf.d directory.
Then with root privilege run ldconfig.
You should then be able to use Splunks own bundled OpenSSL at /opt/splunk/bin/openssl
Still works 6 years later. Thank you!
~T
You can also just export LD_LIBRARY_PATH=/opt/splunk/lib, if you don't want mess with getting root access.
This worked for me. @ashrafmr, you should accept this answer.
Worked great for me. Thanks!
try using the openssl located in /usr/bin or type the absolute path as below
/usr/bin/openssl genrsa -des3 -out mySplunkWebPrivateKey.key 2048