Using openssl-rsautl for verifying signatures

Hi, I did the following in trying to build some validation steps to use against my own rewrite of the crypto functions in Asterisk (to use EVP-PKEY). % echo -n "Mary had a little lamb." | openssl sha1 -binary > digest % od -t x1 digest 000 4e 07 b8 c7 aa f2 a4 ed 4c e3 9e 76 f6 5d 2a 04

Re: EC_POINT_get_affine_coordinates replacement in 3.0

You would have to use EVP_PKEY key type. You can use EVP_PKEY_get* to get key params. > On May 3, 2022, at 1:56 PM, Chris Bare wrote: > > Thanks, I'll check those out. > > On Tue, May 3, 2022 at 4:53 PM William Roberts > wrote: > On Tue, May 3, 2022 at

Re: EC_POINT_get_affine_coordinates replacement in 3.0

Thanks, I'll check those out. On Tue, May 3, 2022 at 4:53 PM William Roberts wrote: > On Tue, May 3, 2022 at 3:18 PM Chris Bare wrote: > > > > > > On Tue, May 3, 2022 at 3:10 PM William Roberts > wrote: > >> > >> On Tue, May 3, 2022 at 1:14 PM Chris Bare wrote: > >> > > >> > I'm converting

Re: EC_POINT_get_affine_coordinates replacement in 3.0

On Tue, May 3, 2022 at 3:18 PM Chris Bare wrote: > > > On Tue, May 3, 2022 at 3:10 PM William Roberts > wrote: >> >> On Tue, May 3, 2022 at 1:14 PM Chris Bare wrote: >> > >> > I'm converting some openssl 1.0 code to 3.0 and I don't know how to get >> > the coordinates >> > in a 3.0 way. >> >

Re: EC_POINT_get_affine_coordinates replacement in 3.0

On Tue, May 3, 2022 at 3:10 PM William Roberts wrote: > On Tue, May 3, 2022 at 1:14 PM Chris Bare wrote: > > > > I'm converting some openssl 1.0 code to 3.0 and I don't know how to get > the coordinates > > in a 3.0 way. > > The old code is: > > BN_CTX *ctx = BN_CTX_new (); > > BIGNUM *X =

Re: EC_POINT_get_affine_coordinates replacement in 3.0

On Tue, May 3, 2022 at 1:14 PM Chris Bare wrote: > > I'm converting some openssl 1.0 code to 3.0 and I don't know how to get the > coordinates > in a 3.0 way. > The old code is: > BN_CTX *ctx = BN_CTX_new (); > BIGNUM *X = NULL, *Y = NULL; > const EC_POINT *pubkey; > const EC_GROUP *group; >

EC_POINT_get_affine_coordinates replacement in 3.0

I'm converting some openssl 1.0 code to 3.0 and I don't know how to get the coordinates in a 3.0 way. The old code is: BN_CTX *ctx = BN_CTX_new (); BIGNUM *X = NULL, *Y = NULL; const EC_POINT *pubkey; const EC_GROUP *group; BN_CTX_start (ctx); X = BN_CTX_get (ctx); Y = BN_CTX_get (ctx); pubkey =

Re: openssl 3.0 fips provider and low level APIs

All the providers can use the low-level APIs internally to implement crypto algorithms. The FIPS provider however includes all the low level implementations as a separately built and statically linked code. That means you cannot use the low-level calls in an application and still be FIPS

openssl 3.0 fips provider and low level APIs

Hi, I understand that low-level APIs have been deprecated in version 3. I have been playing some with the fips provider trying to understand the config options to use with it. I noticed that the fips provider source code includes a few low level APIs like SHA256_Init(). Is it correct to conclude

OpenSSL Security Advisory

.0 is out of support and no longer receiving updates of any kind. The impact of these issues on OpenSSL 1.1.0 has not been analysed. Users of these versions should upgrade to OpenSSL 3.0 or 1.1.1. References == URL for this Security Advisory: https://www.openssl.org/news/secadv/20220503.t

OpenSSL version 1.1.1o published

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenSSL version 1.1.1o released === OpenSSL - The Open Source toolkit for SSL/TLS https://www.openssl.org/ The OpenSSL project team is pleased to announce the release of version 1.1.1o of our open

OpenSSL version 3.0.3 published

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 OpenSSL version 3.0.3 released == OpenSSL - The Open Source toolkit for SSL/TLS https://www.openssl.org/ The OpenSSL project team is pleased to announce the release of version 3.0.3 of our open source