Date: Tue, 7 Nov 2023 16:38:20 -0800 From: "Jin Guojun[VFF]" <jguojun@gmail.com> To: questions@freebsd.org Subject: Re: Openssl errors on FreeBSD Message-ID: <c183ac9b-1540-9b76-f698-97cdca09ce84@gmail.com> In-Reply-To: <c88086d6-f0d5-6a1d-c20f-439bc500a5b7@gmail.com> References: <NiX8klV--3-9@tutanota.com> <26aa343c-e979-47d9-876a-40898c42242b@sentex.net> <NidPljq--3-9@tutanota.com> <9621db26-f97a-40ee-b1fe-6447c0175ddc@sentex.net> <Nif3VV0--J-9@tutanota.com> <CAFbbPuhwZwHJ1FKyNdexL9RkgQFkbP1f_a%2BR5SiGvOVuptwdxA@mail.gmail.com> <Nifjjh1--3-9@tutanota.com> <c88086d6-f0d5-6a1d-c20f-439bc500a5b7@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 11/7/23 16:36, Jin Guojun[VFF] wrote: > On 11/7/23 13:45, iio7@tutanota.com wrote: >> I have booted up two other FreeBSD machines on the same network, >> attached to the same switch as the other two boxes. Same version of >> FreeBSD and OpenSSL, and they work fine. >> >> On the two boxes that works, I get the following identical checksums >> for both: >> >> MD5 (/usr/lib/libssl.so.111) = c0acd4514415e93aeab75b7f4c557215 >> MD5 (/usr/local/lib/libssh2.so.1) = 8db4b65c0e970a9b770901417dadd802 >> MD5 (/usr/local/lib/libpsl.so.5) = 43354da8ffb91bee9e9b085c7220d00f >> MD5 (/lib/libcrypt.so.5) = cb4a7958dbaba1291c11384dbc36cd06 >> >> On the first failing box: >> >> MD5 (/usr/lib/libssl.so.111) = c0acd4514415e93aeab75b7f4c557215 >> MD5 (/usr/local/lib/libssh2.so.1) = de126372e3ca38ddc3a9aadf55d64d6d >> MD5 (/usr/local/lib/libpsl.so.5) = ed11fe03ea248b4e82202c5dabbfb77a >> MD5 (/lib/libcrypt.so.5) = cb4a7958dbaba1291c11384dbc36cd06 >> >> On the second failing box: >> >> MD5 (/usr/lib/libssl.so.111) = c0acd4514415e93aeab75b7f4c557215 >> MD5 (/usr/local/lib/libssh2.so.1) = de126372e3ca38ddc3a9aadf55d64d6d >> MD5 (/usr/local/lib/libpsl.so.5) = ed11fe03ea248b4e82202c5dabbfb77a >> MD5 (/lib/libcrypt.so.5) = cb4a7958dbaba1291c11384dbc36cd06 >> >> On one of the working boxes: >> >> -r--r--r-- 1 root wheel 52096 Apr 7 2023 /lib/libcrypt.so.5 >> -r--r--r-- 1 root wheel 611232 Apr 7 2023 /usr/lib/libssl.so.111 >> -rwxr-xr-x 1 root wheel 68952 Oct 5 03:16 >> /usr/local/lib/libpsl.so.5 >> -rwxr-xr-x 1 root wheel 262944 Aug 6 03:08 >> /usr/local/lib/libssh2.so.1 >> On the first failing box: >> >> -r--r--r-- 1 root wheel 52096 Apr 11 2023 /lib/libcrypt.so.5 >> -r--r--r-- 1 root wheel 611232 Apr 11 2023 /usr/lib/libssl.so.111 >> -rwxr-xr-x 1 root wheel 72168 Apr 15 2023 >> /usr/local/lib/libpsl.so.5 >> -rwxr-xr-x 1 root wheel 263296 Jun 1 03:15 >> /usr/local/lib/libssh2.so.1 >> >> On the second failing box: >> >> -r--r--r-- 1 root wheel 52096 Apr 11 2023 /lib/libcrypt.so.5 >> -r--r--r-- 1 root wheel 611232 Apr 11 2023 /usr/lib/libssl.so.111 >> -rwxr-xr-x 1 root wheel 72168 Apr 15 2023 >> /usr/local/lib/libpsl.so.5 >> -rwxr-xr-x 1 root wheel 263296 Jun 1 03:15 >> /usr/local/lib/libssh2.so.1 >> It should be notet that all four boxes only sits on LAN and only I >> have access. Whatever changes has occurred must be during some >> upgrade or something. >> >> > The libssl and libcrypto look the same on all machines, so they are > not the issue. But libss2 and libpsl are different. > > Since curl does not directly depend them but depends on libss2 and > libpsl, which depend on libssl and libcrypto, > > then maybe the issue is in libss2 and/or libpsl on the failing boxes. > > Try to save libss2 and libpsl on a failing machine, and replace them > with files from a working box to see if solving the issue. > Typo: libss2 -> libssh2
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?c183ac9b-1540-9b76-f698-97cdca09ce84>