Hi Tomas,
It looks correct. This is on the ARM target:
sc3822> find / -name libcrypto.so.3 -print
/lib/libcrypto.so.3
sc3822> strings /lib/libcrypto.so.3 | grep /ssl
/ssl-3//ct_log_list.cnf
OPENSSLDIR: "/ssl-3/"
/ssl-3/
/ssl-3//private
/ssl-3//certs
/ssl-3//cert.pem
sc3822>
I will open an issue
This is really weird. The OPENSSLDIR as in the Makefile should be
applied during the build. If you do strings does
it show the ssl-3? Is it possible that you have some other build of
openssl-3.0 with incorrect (default) OPENSSLDIR lying on the system
somewhere?
Please open an GitHub issue so we c
> On Sep 14, 2021, at 12:03 AM, Tomas Mraz wrote:
>
> On Mon, 2021-09-13 at 16:13 -0700, Kory Hamzeh wrote:
>> I have cross-compiled OpenSSL 3.0.0 for the ARMv7. So far, everything
>> seems to be working fine, except for the fact that I cannot get
>> OpenSSL to load the legacy module when I co
On Mon, 2021-09-13 at 16:13 -0700, Kory Hamzeh wrote:
> I have cross-compiled OpenSSL 3.0.0 for the ARMv7. So far, everything
> seems to be working fine, except for the fact that I cannot get
> OpenSSL to load the legacy module when I configure /ssl/openssl.cnf
> as such. I can, however, load the m
I have cross-compiled OpenSSL 3.0.0 for the ARMv7. So far, everything seems to
be working fine, except for the fact that I cannot get OpenSSL to load the
legacy module when I configure /ssl/openssl.cnf as such. I can, however, load
the module explicitly at run time.
This is a diff of my config
