Comment # 5 on bug 1078825 from V��t��zslav ������ek

I can no longer reproduce the bug. Is it still an issue?

I see that the openssl initialization has been changed a bit in the upstream
git.

Firstly, libcrypto.OPENSSL_init_crypto() runs without parameters to use the
default, so the LOAD_CONFIG and NO_LOAD_CONFIG options should no longer clash.
And secondly, libcrypto.OPENSSL_init_crypto() is now even run only when OpenSSL
version is lower than 1.1.

So maybe a salt update fixed it?
Could you please verify?