[openssl-users] [ANN] M2Crypto 0.25.0

Hi, everybody, after trials and tribulations I have the honor to announce new release of M2Crypto 0.25.0. This is an intermediary version on our way towards port to python 3 (or rather to the bi-versional state of both py2k and py3k compatibility). Particularly we have made these achievements

Re: [openssl-users] Openssl software failure for RSA 16K modulus

> 2: if anyway I want to use 16k modulus, Do we have solution to avoid this > issue so that it won't harm to other application or create any new attack? No. -- openssl-users mailing list To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users

Re: [openssl-users] Openssl software failure for RSA 16K modulus

1: I didn't get it, Why this behaviour is not coming for other ciphers while doing the server/client handshake? It should fail for other ciphers also. Ciphers: working DHE-RSA-AES128-SHA ECDHE-RSA-AES256-GCM-SHA384 .. etc Ciphers: Not working AES128-SHA AES256-SHA .. etc

Re: [openssl-users] Openssl software failure for RSA 16K modulus

> The DoS issue is still there. How can you prevent the "other side" from > consuming all your CPU with a large key? > Who needs 16K RSA keys, such that openssl by default should support that for > everyone? We have cryptographic accelerators on cavium platforms which minimize CPU usage. So

Re: [openssl-users] Openssl software failure for RSA 16K modulus

Bonjour, Le 22 juil. 2016 à 08:44, Gupta, Saurabh > a écrit : 1: I didn't get it, Why this behaviour is not coming for other ciphers while doing the server/client handshake? It should fail for other ciphers also. Ciphers: working

Re: [openssl-users] Openssl software failure for RSA 16K modulus

> We have cryptographic accelerators on cavium platforms which minimize CPU > usage. So our customers are looking for 16K support. Well, sorry, but by default most other sides won't be able to use them. Not sure anything else to say. -- openssl-users mailing list To unsubscribe: