Please take a look at my blog post that gives an update on OpenSSL 3.0
development, FIPS and 1.0.2 EOL:
https://www.openssl.org/blog/blog/2019/11/07/3.0-update/
Matt
On 11/6/2019 11:42 PM, Frederick Gotham wrote:
> Jordan Brown wrote:
>
>> Note that __pthread_once_slow is in the stack twice, called from
>> OPENSSL_init_crypto and CRYPTO_THREAD_run_once.
>>
>> "once" functions ensure that they call their function argument exactly
>> once, even if they are
From: Frederick Gotham
To: openssl-users@openssl.org
Date: 11/07/2019 10:39 AM
Subject:[EXTERNAL] Re: SOLVED: Force use of engine all the time
Sent by:"openssl-users"
Frederick Gotham wrote:
> I don't think any code other than "libcrypto.so" is using the TPM2,
Frederick Gotham wrote:
> I don't think any code other than "libcrypto.so" is using the TPM2, and so
> I don't know why I'm getting "device or resource busy" (considering I'm
> using a global named mutex)". I see that there's also a TPM2 tcti called
> "abrmd", and I'm not sure if this purpose
I know I've called this "solved", but I've achieved my objective about 98%
so there's only a little bit left to go.
My changes to the source code for LibOpenSSL are confined to the file
"rand_lib.c".
Firstly, I've added the following code:
#include
#include
#include
static int
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
> 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
