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.
Considering the recent problems discovered in OpenSSL (and in general) one may be faced with the prospect of upgrading OpenSSL version to a newer one then the distro default.
Today this is applicable to Slackware-14.2 (which I know, it's old, but I have many migration details to solve before I can make the full distro upgrade), but later in 2023 it will apply to Slackware-15.0 as well (openssl-1.1.1 support ends in september).
Can Slackware-14.2 (maybe even 14.1) be upgraded to openssl-1.1.1 series?
What packages need to be rebuilt when doing such an upgrade, assuming there aren't many in the way of incompatibilities at source level.
Of course this is meant as a short term fix against the published security problems until a full migration can be perfected.
Can Slackware-14.2 (maybe even 14.1) be upgraded to openssl-1.1.1 series?
What packages need to be rebuilt when doing such an upgrade, assuming there aren't many in the way of incompatibilities at source level.
I guess there are lots of incompatibilities at source level. But anyway, in Slackware64-14.2, let's check directories /lib64, /usr/lib64, /usr/sbin, /bin, /usr/bin, /usr/libexec for files linked to libcrypto.so.1 of openssl. (There could be stuff elsewhere, too)
Last edited by Petri Kaukasoina; 02-11-2023 at 08:03 AM.
Reason: Fixes. The latest was to anchor the beginning and the end of the file name with ^ and $.
Just for fun, I built the parallel package from Slackware 15.0 in a clean, up to date Slackware 14.2 install, so that I could try the script originally posted by our BDFL. (There is a now a later version.)
After the initial hiccups of needing to run parallel on it's own to do the 'will cite' acceptance, and adapting the script to the previous package log location (sed -i 's:/var/lib/pkgtools/packages:/var/log/packages:g' find-whatlinksagainst.sh),
I ran './find-whatlinksagainst.sh openssl-1.0.2u-x86_64-4_slack14.2 | tee packagelist.txt' to generate the attached output.
Comments - The immediately interesting stuff is towards the end.
The UNKNOWN package mentioned in the output is sendmail, triggered by /usr/bin/sendmail being a symlink to /usr/sbin/sendmail.
Because I did not set up a PKGSOURCE, the package Series is not reported.
Oh, I see it now. I guess all (?) of these were false positives because they link to /usr/lib64/libgmp.so.10 and openssl contains a totally different /usr/lib64/engines/libgmp.so.
By the way, here is another version of my script. Now printing the names of the individual files linking to openssl, as was in the beginning of your output.
Code:
#!/bin/sh
LIB='libcrypto.so.1$|libssl.so.1$'
cd /var/adm/packages
for pkg in *; do
( cd /
while read line; do
[ "$line" == "FILE LIST:" ] && break
done
while read f; do
[ -x "$f" ] && objdump -x "$f" 2>/dev/null|grep NEEDED|grep -Eq $LIB && echo "$pkg": /"$f"
done
) < $pkg
done
The UNKNOWN package mentioned in the output is sendmail, triggered by /usr/bin/sendmail being a symlink to /usr/sbin/sendmail.
I think that's because it found /usr/sbin/sendmail which does not exist in /var/adm/packages/sendmail-8.15.2-x86_64-2 because it is originally /usr/sbin/sendmail.new and the install script moves it to /usr/sbin/sendmail. My script does not notice it at all, because it tries to check /usr/sbin/sendmail.new which does not exist. (But it finds several other binaries in the sendmail package.)
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.