> It is very likely that your binary is actually loading the system's shared
> libraries instead of the ones you just compiled. You can verify whether this
> using the `ldd` command,
That was it. Thanks.
> There is a shared library wrapper called `shlib_wrap.sh` which can be used to
> run the
AM
> To: Hal Murray ; openssl-users@openssl.org
> Subject: RE: Confusion Configuring
>
> For OpenSSL 3.0, it's better to use util/wrap.pl instead.
>
> (Note: util/wrap.pl is created from util/wrap.pl.in by the Configure command)
>
> > -Original Message-
> > F
> To: Hal Murray ; openssl-users@openssl.org
> Subject: RE: Confusion Configuring
>
> Hal,
>
> > But when I run
> > ./apps/openssl version -d
> > it says:
> > OPENSSLDIR: "/usr/local/ssl"
> > I was expecting /etc/pki/tls from the Configure li
Hal,
> But when I run
> ./apps/openssl version -d
> it says:
> OPENSSLDIR: "/usr/local/ssl"
> I was expecting /etc/pki/tls from the Configure line above.
>
> What am I missing? How do I tell it where to find the default certificates?
It is very likely that your binary is actually loading the
I've been happily testing/using alpha, beta, 3.0.0 and 3.0.1, but I've run
into
an interesting quirk.
My problem is that it's not finding/using the default certificates that I'd
like it to use.
I'm running on Fedora. The installed version says:
$openssl version
OpenSSL 1.1.1l FIPS 24
