> 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
Hal,
I just reread your initial post and noticed that my explanation is somewhat
inconsistent
with your observations, since in your case the system openssl prints the
expected path.
Nevertheless, using
util/wrap.pl apps/openssl ...
is the correct way to test your self-built application.
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-
> From: openssl-users On Behalf Of Dr.
> Matthias St. Pierre
> Sent: Saturday, December 18, 2021 9:11 AM
> To: Hal Murray ; opens
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
