OpenSSL version and libssl.so/libcrypto.so version mismatch
I'm cross-compiling the latest (1.0.1c) version of OpenSSL. The entire process goes well, but for some reason, the two lib files come out as libcrypto.so.1.0.0 and libssl.so.1.0.0. The new version of OpenSSL seems to run well also with no real problems.
I grabbed another virgin copy of the 1.0.1c OpenSSL tarball, and it seems that the SHLIB_VERSION numbers are hardcoded into Makefile.org as 1.0.0.
1. What is the reason for this? I've looked through the provided documentation, but I do not see any discussion of the library version numbers being different.
2. How can I change it? It has the potential to confuse the other engineers I work with. I tried to change the values in Makefile.org, but when I try to see the SSL and SSH version, I get the typical "OpenSSL version mismatch. Built against XXXXXX, you have YYYYYYY".
Welcome to LQ.
All versions, openssl-1.0.x.x : The 'names' are lib***.so.1.0.0
Why would you want to change the name ?
Thanks for the quick reply.
We are upgrading from version 1.0.0 to 1.0.1, and the fact that the library names don't change with the OpenSSL upgrade just makes it a bit more difficult to tell if we are using the new libs or not.
If this is simply the way OpenSSL does it, I won't bother with trying to change it.
Thanks again, marking as solved.
Well, it wouldn't be very convenient,
if the 'so name' changed for every update.
Then you'd also have to recompile the "300" libraries
and applications depending on libssl.so.*, libcrypto.so.*.
|All times are GMT -5. The time now is 10:55 AM.|