Yes, this is unfortunately a bug in 3.0.3 release. Calling
OPENSSL_init_crypto should not be necessary.
Tomas Mraz
On Wed, 2022-05-04 at 21:58 +0200, Klaus Keppler wrote:
> Hello,
>
> yesterday we updated OpenSSL from 3.0.2 to 3.0.3, what made some of
> our
> unit tests crash.
>
> I've boiled
Oh sorry, forgot to say that.
It's x86-64, compiled on Debian 10.12 (GCC 8.3.0) and CentOS 7 (GCC
8.3.1) - other distributions/GCC versions not tested yet.
OpenSSL was compiled with common hardening flags:
CFLAGS="-fstack-protector --param ssp-buffer-size=4 -fPIC -O2"
What platform?
$ bat ossl3-tst.c
───┬──
│ File: ossl3-tst.c
│ Size: 216 B
Hello,
yesterday we updated OpenSSL from 3.0.2 to 3.0.3, what made some of our
unit tests crash.
I've boiled the problem down to the following example code:
---cut---
#include
#include
#include
int main(int argc, const char *argv[]) {
//OPENSSL_init_crypto(0, NULL);
if (!
On 03/05/2022 23:29, Kory Hamzeh wrote:
You would have to use EVP_PKEY key type. You can use EVP_PKEY_get* to
get key params.
Yes this is probably the best way to do this.
Specifically you can use the function EVP_PKEY_get_bn_param() documented
here:
Bonjour,
The ASN.1 structure (it's a DigestInfo) is part of the PKCS#1 v1.5 padding
for signature operations.
PKCS#1v1.5 is rewritten in RFC2313.
Using the command line tool, you can reproduce this:
echo -n "Mary had a little lamb." > datatosign
either one of the following can be used to sign
