Comment # 9 on bug 1207963 from Michael Hamilton

(In reply to Yasuhiko Kamata from comment #8)
> Thanks for testing again, I've found one more problem.
> 
> Due to upgrading of openssl-3, "libssl.so.3" and "libcrypto.so.3" should be
> included in candidate file names.
> (Because they are dynamically (manually) loaded as mentioned above, these
> file names should be specified in source code).
> 
> So I updated the patch and submitted again.
> Could you upgrade it and test again?
> I'll leave this report open.

I see that it's building now.  I'll check again in the morning.

I've also found that the openssl command can work OK on TLSv1.2, but sometimes
it fails with an error (maybe 1 time in 5).  So perhaps I'm just seeing a
normal kind of handshake or timeout error.  So the openssl testing may just be
a false trail.