Re: OpenSSL 3.0 different behaviour on smaller DH groups?
Simon Chopin wrote: > This test suite fails several times with a failed call to > EVP_PKEY_derive_set_peer, without much more details: > https://github.com/net-ssh/net-ssh/blob/master/test/transport/kex/test_diffie_hellman_group14_sha1.rb > However, the *exact same* test suite works, with the only difference > being that the failing suite uses the DH group 14, which is 2048bits, > whereas the one that passes uses the group 1, which the Internet tells > me is 768bits. DH groups of 768bits are considered too weak. I wonder if openssl 3 is declining to do anymore, and/or has been compiled with an option to drop support for that size. (I have no knowledge of that part of openssl) signature.asc Description: PGP signature
OpenSSL 3.0 different behaviour on smaller DH groups?
Hi, I'm working on migrating the Ruby net-ssh package to OpenSSL 3.0 as part of our larger transition in Ubuntu, but there's an issue that I can't figure out. This test suite fails several times with a failed call to EVP_PKEY_derive_set_peer, without much more details: https://github.com/net-ssh/net-ssh/blob/master/test/transport/kex/test_diffie_hellman_group14_sha1.rb However, the *exact same* test suite works, with the only difference being that the failing suite uses the DH group 14, which is 2048bits, whereas the one that passes uses the group 1, which the Internet tells me is 768bits. I'm working on trying to come up with a pure-C reproducer, but I'm sending this in the hopes that someone out there has a sudden epiphany and knows what is causing this? For the curious out there, we're tracking this work at https://bugs.launchpad.net/ubuntu/+source/vagrant/+bug/1964025 Cheers, -- Simon Chopin Foundations Team Ubuntu MOTU simon.cho...@canonical.comscho...@ubuntu.com
Re: OpenSSL 3.0.2 PKCS12_parse Failure
How do you load the legacy provider? Into which library context? It needs to be loaded into the default (NULL) library context for the PKCS12_parse() function. The workaround would be to not use the certificate/key pair for the server in the PKCS12 format but in the PEM format with separate key and certificate files. Tomas Mraz On Fri, 2022-04-01 at 18:14 +, vchiliquinga--- via openssl-users wrote: > Hello, > > Connection between a Openssl 3.0.2 server and a 1.1.1g client is > proving to be unsuccessful. > > According to the logs collected we seem to be having an issue with > the loading of the legacy providers. > We are loading both the default and legacy providers programmatically > as per the steps outlined in the Wiki for OpenSSL 3.0 – 6.2 > Providers. > > We are seeing the following error.. > > error:0308010C:digital envelope > routines:inner_evp_generic_fetch:unsupported:crypto\evp\evp_fetch.c:3 > 46:Global default library context, Algorithm (RC2-40-CBC : 0), > Properties () > PKCS12_parse() failed = 183. (Using GetLastError from > errhandlingapi.h, the 183 error code is obtained) > > Worth mentioning that we are only seeing this issue occur when the > server is a Windows 2012 server. > > Thank you, > Victor C. -- Tomáš Mráz, OpenSSL
