RE: API to get BIGNUM member "top" in openssl 3.0

2021-10-07 Thread Dr. Matthias St. Pierre
> Can you give a MWE for what you are trying to achieve? I guess that "minimal working example" is the correct choice from the gazillions of possible meanings of "MWE"? šŸ˜‰ Regards, Matthias [1] https://www.acronymattic.com/MWE.html [2] https://www.abbreviations.com/MWE smime.p7s Descriptio

Re: API to get BIGNUM member "top" in openssl 3.0

2021-10-07 Thread Billy Brumley
>In our application we are accessing BIGNUM member top as bn->top. > Now we are trying > >to migrate to OPENSSL 3.0. I am unable to find API to access this > member. > >Please let me know if there is any get API to get the ā€œtopā€ member > of BIGNUM. Since the

API to get BIGNUM member "top" in openssl 3.0

2021-10-07 Thread Paramashivaiah, Sunil
Hi All, In our application we are accessing BIGNUM member top as bn->top. Now we are trying to migrate to OPENSSL 3.0. I am unable to find API to access this member. Please let me know if there is any get API to get the "top" member of BIGNUM. Thanks and Regard

Re: OpenSSL 3.0.0 FIPS compatible ECDH-KAS

2021-10-07 Thread Dr Paul Dale
Kory, The situation is more complicated but your solution below is the one I'd have suggested. SP800-90B says bad things about /dev/random but this is modified by IG 7.14 indicates that it is okay to use /dev/random. Then IG 7.19 says that it isn't.Ā  The current FIPS 140-2 validation is side

Re: OpenSSL 3.0.0 enabling SSLv3 support

2021-10-07 Thread Viktor Dukhovni
On Thu, Oct 07, 2021 at 09:38:30AM -0500, Mark Hack wrote: > Added to all the weaknesses in SSLv3, the only supported cipher suites > are either vulnerable or deprecated and not advisable. If we set aside browsers where CBC padding oracles are a problem, the below are in practice still reasonabl

Re: OpenSSL 3.0.0 enabling SSLv3 support

2021-10-07 Thread Mark Hack
Added to all the weaknesses in SSLv3, the only supported cipher suites are either vulnerable or deprecated and not advisable. SSL_RSA_WITH_NULL_MD5 NULL-MD5 SSL_RSA_WITH_NULL_SHA NULL-SHA SSL_RSA_EXPORT_WITH_RC4_40_MD5 EXP-RC4-MD5 SSL_RSA_WITH_RC4_

Re: Store Mgmt and keys loading ( keyform ENG )

2021-10-07 Thread Antonio Santagiuliana
It is because of prototypes of methods.. On Thu, 7 Oct 2021, 08:49 Antonio Santagiuliana, wrote: > Hello, > just continuing on this.. > I defined my store mgmt as : > static const OSSL_ALGORITHM test_store[] = { > { "handle", "provider=test", mystore_functions}, > {NULL, NULL, NULL} > }; > > ech

Re: [EXTERNAL] Re: Replacement for BIO_get_port(), BIO_get_host_ip()

2021-10-07 Thread Matt Caswell
The functions I suggested support both IPv4 and IPv6. For example in the BIO_lookup() call the 4th parameter would be AF_INET for IPv4 and AF_INET6 for IPv6. Matt On 07/10/2021 08:18, Shivakumar Poojari wrote: HiĀ Matt, The steps suggested are similarly to the deprecated function so simply I

Re: Store Mgmt and keys loading ( keyform ENG )

2021-10-07 Thread Antonio Santagiuliana
Hello, just continuing on this.. I defined my store mgmt as : static const OSSL_ALGORITHM test_store[] = { { "handle", "provider=test", mystore_functions}, {NULL, NULL, NULL} }; echo "test" | LD_LIBRARY_PATH=.apps/openssl dgst --provider-path=./providers --provider=test --sign handle:1 -out

Re: [EXTERNAL] Re: Replacement for BIO_get_port(), BIO_get_host_ip()

2021-10-07 Thread Shivakumar Poojari
Hi Matt, The steps suggested are similarly to the deprecated function so simply I used the same code in static function, But i need support for IPV6 as well in the same function The function needs to have compatibility to support for both ipv6 and ipv4, do we have any new function to support b