I know that we need
* ocsp responder cert for verifying the signature of ocsp response,
* CA issuer cert to generate CERTID for ocsp request
and
* ocsp requestor can choose to sign ocsp request using a signer certificate.
But instead of having users set that as 3 different settings, I am
thinking
It is not an issue in OpenSSL that the getentropy somehow does not
work. I could imagine adding a define that disables use of getentropy.
Tomas
On Thu, 2022-06-02 at 15:26 +0530, Minal Patil wrote:
> Hello Tomas,
>
> Thanks Man.
> It started working when compiled with your suggestions.
>
> Coul
Hello Tomas,
Thanks Man.
It started working when compiled with your suggestions.
Could it be an issue with openssl or with the compile ?
Thanks,
Minal
On Thu, Jun 2, 2022 at 2:32 PM Tomas Mraz wrote:
> This is crashing inside the getentropy call in glibc or the weak symbol
> binding does not
This is crashing inside the getentropy call in glibc or the weak symbol
binding does not work correctly for some reason.
I'd suggest changing the line 359 of
providers/implementations/rands/seeding/rand_unix.c
from:
# if !defined(__DragonFly__) && !defined(__NetBSD__)
to:
# if 0
That might help
here is the backtrace with debug.
Program received signal SIGILL, Illegal instruction.
0x1004 in ?? ()
Missing separate debuginfos, use: dnf debuginfo-install
libgcc-8.3.1-4.5.el8.ppc64le libstdc++-8.3.1-4.5.el8.ppc64le
(gdb) bt
#0 0x1004 in ?? ()
#1 0x1006da60 in