-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear Steve,
Op 15-08-10 01:52, Dr. Stephen Henson schreef: > OpenSSL 1.0.0 doesn't include any SSLv2 cipersuites by default and new logic > means it doesn't send out an SSLv2 compatible client hello if it will never > use SSLv2. That effectively disables SSLv2 by default. Try a cipher > string that explicitly enables some SSLv2 ciphers. Could you elaborate why this did work out of the box in 0.9.8 and breaks with 1.0.0. Basically I found out that this site only seems to accept SSLv2. Of course I can specify what protocol to use manually, (I actually hacked the httplib in Python for it already), but from usability point of view: why did this break? Is it possible to configure to use SSLv2 anyway? Stefan -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.15 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEAREKAAYFAkxnPrwACgkQYH1+F2Rqwn0Q7wCePHZasr1Qu9unbMTEctgTnf2/ +fwAn0yDTfDM/pr4jOXeKePPR7nqCfoy =QokX -----END PGP SIGNATURE----- ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager majord...@openssl.org
