SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have just updated my openssl package on Slackware14.1. I use stunnel on this box for sendmail, httpd and imap. When I started the stunnel I have noticed that the Log message is showing an older Openssl library is used:
Quote:
Compiled/running with OpenSSL 1.0.1c 10 May 2012
Does it mean that although I updated the openssl for openssl-1.0.1k, as far as I use stunnel I use an outdated version of SSL library?
Hello
I have just updated my openssl package on Slackware14.1. I use stunnel on this box for sendmail, httpd and imap. When I started the stunnel I have noticed that the Log message is showing an older Openssl library is used:
Does it mean that although I updated the openssl for openssl-1.0.1k, as far as I use stunnel I use an outdated version of SSL library?
Correct...that is the version of openssl that was compiled in to the stunnel program you're using. The easiest way to do this is to just re-compile your stunnel program from source, which will pick up the newly-installed library.
You can check and see if there is a way to dynamically link openssl to stunnel instead of the static link that was done when you recompile. Possibly as a --enable-shared option in the ./configure options.
No. You are using version 1.01k. From the build script used to build OpenSSL:
Code:
# OpenSSL has a (nasty?) habit of bumping the internal version number with
# every release. This wouldn't be so bad, but some applications are so
# paranoid that they won't run against a different OpenSSL version than
# what they were compiled against, whether or not the ABI has changed.
#
# So, we will use the OPENSSL_VERSION_NUMBER from openssl-1.0.1c unless ABI
# breakage forces it to change. Yes, we're finally using this old trick. :)
sed -i "s/#define OPENSSL_VERSION_NUMBER.*/\/* Use 0x1000103fL (1.0.1c) below to avoid pointlessly breaking the ABI *\/\n#define OPENSSL_VERSION_NUMBER 0x1000103fL/g" crypto/opensslv.h || exit 1
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.