Re: Latest idea to force usage of custom engine

2019-11-07 Thread Frederick Gotham
Frederick wrote: > > CRYPTO_THREAD_write_lock(rand_meth_lock); > CRYPTO_THREAD_write_lock(rand_engine_lock); This is what's causing the segfault in libpthread.so I can only imagine that the same thread is trying to re-lock a single-lock mutex. So my code should be something like

Re: Latest idea to force usage of custom engine

2019-11-07 Thread Frederick Gotham
> I'm going to keep at this until every process (including ssh-keygen) is > using my custom engine for random numbers. Now every process that links with 'libcrypto.so' is segfaulting in libpthread-2.28.so. Here's the error: openssl[1744]: segfault at 18 ip 7f1798d44930 sp 7ffcf46