openssl 3.0.0 legacy provider won't lload via config file

[Tomas Mraz]

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 module explicitly at run time.
> 
...
> 
> The EVP_DecryptInit_ex() fails if I compile without -DLOAD_PROVIDER.
> The other flag, CRYPTO_INIT does not make any difference. What is
> puzzling is that I can build OpenSSL natively on an x86_64 machine
> and using the same openssl.cnf file, the code above works and the
> legacy module loads without the code to explicitly load it.
> 
> Any thoughts on what I may have done wrong or how to track this down?

Could it be that your cross-compiled build expects the configuration
file to be somewhere else? Have you tried to strace the application to
see where it searches for the openssl.cnf?

-- 
Tomáš Mráz
No matter how far down the wrong road you've gone, turn back.
                                              Turkish proverb
[You'll know whether the road is wrong if you carefully listen to your
conscience.]