Re: Openssl errors on FreeBSD

On Tue, Nov 7, 2023 at 1:36 PM <iio7@tutanota.com> wrote:

>
>
> > Yes, but what about
> >
> > ldd curl
> >
> > ? What does it show
> >
> Sorry, forgot ldd.
>
> $ ldd /usr/local/bin/curl
> /usr/local/bin/curl:
>         libcurl.so.4 => /usr/local/lib/libcurl.so.4 (0x1fc15c2cd000)
>         libz.so.6 => /lib/libz.so.6 (0x1fc15d337000)
>         libkrb5.so.11 => /usr/lib/libkrb5.so.11 (0x1fc15ddbf000)
>         libgssapi.so.10 => /usr/lib/libgssapi.so.10 (0x1fc15ec46000)
>         libgssapi_krb5.so.10 => /usr/lib/libgssapi_krb5.so.10
> (0x1fc15fc91000)
>         libthr.so.3 => /lib/libthr.so.3 (0x1fc15f095000)
>         libc.so.7 => /lib/libc.so.7 (0x1fc15fed8000)
>         libnghttp2.so.14 => /usr/local/lib/libnghttp2.so.14
> (0x1fc160f02000)
>         libssh2.so.1 => /usr/local/lib/libssh2.so.1 (0x1fc1624ba000)
>         libpsl.so.5 => /usr/local/lib/libpsl.so.5 (0x1fc161dcc000)
>         libssl.so.111 => /usr/lib/libssl.so.111 (0x1fc163cab000)
>         libheimntlm.so.11 => /usr/lib/libheimntlm.so.11 (0x1fc162630000)
>         libhx509.so.11 => /usr/lib/libhx509.so.11 (0x1fc162acc000)
>         libcom_err.so.5 => /usr/lib/libcom_err.so.5 (0x1fc162f7d000)
>         libcrypto.so.111 => /lib/libcrypto.so.111 (0x1fc165235000)
>         libasn1.so.11 => /usr/lib/libasn1.so.11 (0x1fc163e69000)
>         libwind.so.11 => /usr/lib/libwind.so.11 (0x1fc1649eb000)
>         libheimbase.so.11 => /usr/lib/libheimbase.so.11 (0x1fc166551000)
>         libroken.so.11 => /usr/lib/libroken.so.11 (0x1fc16573f000)
>         libcrypt.so.5 => /lib/libcrypt.so.5 (0x1fc167452000)
>         libprivateheimipcc.so.11 => /usr/lib/libprivateheimipcc.so.11
> (0x1fc16877f000)
>         libidn2.so.0 => /usr/local/lib/libidn2.so.0 (0x1fc1683b6000)
>         libunistring.so.5 => /usr/local/lib/libunistring.so.5
> (0x1fc1695eb000)
>         [vdso] (0x7ffffffff000)
>
> > And I am guessing you have nothing in /etc/libmap*
> >
> $ ls /etc/libmap*
> /etc/libmap.conf
>
> $ cat /etc/libmap.conf
> # $FreeBSD$
> includedir /usr/local/etc/libmap.d
>
> $ ls /usr/local/etc/libmap.d
> ls: /usr/local/etc/libmap.d: No such file or directory
>
>
Is the time correct on your machine?

The problem with this specific error is that it can be caused by anything
from the source machine to the destination machine.
No one is going to have a silver bullet.  It can be anything from a bad
switch port, to offloading features of the nic, to a TLS Proxy is sorts
sitting in between machines, etc.

~Paul
-- 
__________________

:(){ :|:& };: