[SOLVED] OpenSSL upgrade for possible security vulnerabilities
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.
OpenSSL upgrade for possible security vulnerabilities
I was alerted this morning to possible vulnerabilities in this article. According to the article, -current has the latest patches which are recommended, but for the sake of peace of mind, I went to the OpenSSL site, downloaded the latest sources, and built the package(s). As a public service for all Slackers utilizing this forum, I have uploaded the packages, and am offering it for download to anyone interested.
Thanks but I wouldn't recommend to replace the patched openssl{,-solibs} official Slackware package, released on Fri, 9 Jan 2015 with a third-party one. Furthermore you don't say for which Slackware version it is build (is it for -current?), nor provide build material at time of writing.
I'd suggest instead to just follow the official Security Advisory or for a very sensitive installation rebuild the packages with one of the patched versions linked to by mancha in this post.
Last edited by Didier Spaier; 03-22-2015 at 10:46 AM.
Didier: I used PV's SlackBuild from a mirror site, and I am using -current. I should have made that clear. As for 'build material', it is unclear exactly what you mean, unless you are referring to the SlackBuild (I didn't compile it manually).
veerain: Trust has to start somewhere, and although I am not mancha and have not, as yet, have a proven reputation for reliability, I do have a vested interest in seeing my system run smoothly, as I am a fellow Slacker. The packages are available; do with it (or not) as you will. If you want to wait for an official source to come out with the patched version, that is your prerogative. I am merely making updated packages available for download because I thought fellow Slackers would be interested in knowing about the vulnerability, and upgrading. Perhaps I assumed too much in building the package myself, given the emphasis on security; using a trusted site is far preferred to a random site (such as how mine would be perceived at the present).
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.