On 15-08-2010 03:11, Stefan de Konink wrote:
-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
On 08/14/2010 09:11 PM, Stefan de Konink wrote:
-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
On Sun, Aug 15, 2010, Stefan de Konink wrote:
-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
On Sat, Aug 14, 2010, Stefan de Konink wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hello,
I have a very odd problem with respect to my recent upgrade to 1.0.0;
In principle this is the problem:
openssl s_client -connect server.db.kvk.nl:443 -debug
CONNECTED(0003)
-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
