Re: Git segfaulting in libcrypto.so when trying to clone.

On 17/10/2018 7:14 pm, Brennan Vincent wrote:
> Hi Kubilay (or do you prefer "koobs"?). Thanks for the response.
> 
> To answer your questions:
> * I am using latest packages
> * My /etc/make.conf was empty when I built the system, and now just has `WITH_DEBUG=yes`.
> 
> # uname -a
> FreeBSD freebsd 12.0-ALPHA9 FreeBSD 12.0-ALPHA9 #3 r339359: Tue Oct 16 03:28:51 UTC 2018     root_at_freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC  amd64
> # ldd /usr/local/bin/curl
> /usr/local/bin/curl:
>          libcurl.so.4 => /usr/local/lib/libcurl.so.4 (0x800268000)
>          libz.so.6 => /lib/libz.so.6 (0x8002e7000)
>          libkrb5.so.11 => /usr/lib/libkrb5.so.11 (0x800301000)
>          libgssapi.so.10 => /usr/lib/libgssapi.so.10 (0x800382000)
>          libgssapi_krb5.so.10 => /usr/lib/libgssapi_krb5.so.10 (0x80038f000)
>          libthr.so.3 => /lib/libthr.so.3 (0x8003b1000)
>          libc.so.7 => /lib/libc.so.7 (0x8003dc000)
>          libnghttp2.so.14 => /usr/local/lib/libnghttp2.so.14 (0x8007e7000)
>          libssl.so.8 => /usr/lib/libssl.so.8 (0x800812000)
>          libheimntlm.so.11 => /usr/lib/libheimntlm.so.11 (0x800888000)
>          libhx509.so.11 => /usr/lib/libhx509.so.11 (0x800891000)
>          libcom_err.so.5 => /usr/lib/libcom_err.so.5 (0x8008e2000)
>          libcrypto.so.8 => /lib/libcrypto.so.8 (0x8008e7000)
>          libasn1.so.11 => /usr/lib/libasn1.so.11 (0x800b59000)
>          libwind.so.11 => /usr/lib/libwind.so.11 (0x800bfd000)
>          libheimbase.so.11 => /usr/lib/libheimbase.so.11 (0x800c27000)
>          libroken.so.11 => /usr/lib/libroken.so.11 (0x800c2e000)
>          libcrypt.so.5 => /lib/libcrypt.so.5 (0x800c43000)
>          libcrypto.so.9 => /lib/libcrypto.so.9 (0x800c65000)
>          libprivateheimipcc.so.11 => /usr/lib/libprivateheimipcc.so.11 (0x800f52000)
> # ldd /usr/local/lib/libcurl.so.4
> /usr/local/lib/libcurl.so.4:
>          libnghttp2.so.14 => /usr/local/lib/libnghttp2.so.14 (0x800707000)
>          libssl.so.8 => /usr/lib/libssl.so.8 (0x800732000)
>          libheimntlm.so.11 => /usr/lib/libheimntlm.so.11 (0x8007a8000)
>          libhx509.so.11 => /usr/lib/libhx509.so.11 (0x800e00000)
>          libcom_err.so.5 => /usr/lib/libcom_err.so.5 (0x8007b1000)
>          libcrypto.so.8 => /lib/libcrypto.so.8 (0x800e51000)
>          libasn1.so.11 => /usr/lib/libasn1.so.11 (0x8010c3000)
>          libwind.so.11 => /usr/lib/libwind.so.11 (0x8007b6000)
>          libheimbase.so.11 => /usr/lib/libheimbase.so.11 (0x8007e0000)
>          libroken.so.11 => /usr/lib/libroken.so.11 (0x8007e7000)
>          libcrypt.so.5 => /lib/libcrypt.so.5 (0x801167000)
>          libz.so.6 => /lib/libz.so.6 (0x801189000)
>          libkrb5.so.11 => /usr/lib/libkrb5.so.11 (0x8011a3000)
>          libgssapi.so.10 => /usr/lib/libgssapi.so.10 (0x801224000)
>          libgssapi_krb5.so.10 => /usr/lib/libgssapi_krb5.so.10 (0x801231000)
>          libthr.so.3 => /lib/libthr.so.3 (0x801253000)
>          libc.so.7 => /lib/libc.so.7 (0x800248000)
>          libcrypto.so.9 => /lib/libcrypto.so.9 (0x80127e000)
>          libprivateheimipcc.so.11 => /usr/lib/libprivateheimipcc.so.11 (0x80156b000)
> 
> (aha - libcurl depends on .8 , and the curl binary depends on .9)
> 
>  From a cursory glance at the source tree, it seems libcrypto is part of openssl, is this right? It seems the openssl version is in flux right now, that might explain things...

OpenSSL 1.1.1 import happened 7 days ago [1], which may partially 
explain the cause.

Having two versions of the shared libraries in base is unexpected 
though, unless its intentional for some reason, or I'm 
missing/forgetting something.

Do you run the delete-old / delete-old-lib targets during your
upgrades?

[1] https://svnweb.freebsd.org/changeset/base/339270