Sorry for top-posting - still getting used to this webmail:
The only way I can see that the server is reponsible for this behaviour is
the certificate you are providing. Has that expired or been invalidated in any
way at the client?
Carl
From: owner-openssl-us...@openssl.org
Hi All,
When I am running my test code with IBM purify, my code was coredump. The same
code worked fine in openssl 1.0.0a release but coredump under 1.0.1c release.
Following is the debug message reported by IBM purify:
Purify instrumented testapp (pid 16764)
COR: Fatal core dump:
From: owner-openssl-us...@openssl.org On Behalf Of Gayathri Manoj
Sent: Tuesday, 06 November, 2012 22:56
I wanted to parse the x509 certificate using openssl-0.9.8l
which is signed by sha256WithRSAEncryption algorithm.
I am not explicitly calling EVP_DigestInit_ex() to initailse
From: owner-openssl-us...@openssl.org On Behalf Of thorso...@lavabit.com
Sent: Tuesday, 06 November, 2012 23:15
To: openssl-users@openssl.org
Subject: CA.pl, TLS encryption, Postfix
Hello,
I need help with CA.pl and this [1] guide in general.
(I've already tried to ask here [2].)
Just for everyone's benefit, there is a bug in OpenSSL that prevents ECDH-RSA
cipher suites to be negotiated and this has been fixed in the latest stable
snapshot.
For all the folks who recommends that ECDH-RSA and ECDH-ECDSA cipher suites
should not be supported, can you point to literature
Hello,
I have a server running that I am accepting both SSL and non SSL traffic.
Currently I check the traffic first and if the first part of the TCP data
looks like an SSL header, I send it off to an OpenSSL socket to be read. If
it's plaintext, I just read it right there on that socket.
Is it
