Hi everyone,
I have a TLS server application which the old OpenSSL library has no
problem connecting to it but the latest couldn't.
The problem occurs in the first client hello stage while the server only
returned two bytes 02 28 for the s_client from OpenSSL-v0.9.8l
afterwards. But the same
I could resolve the problem. It was not caused by a not correctly implemented
locking of the SSL object so that multiple threads would have been able to
operate concurrently on it. The problem was that I forked another process from
within one thread, that also used the SSL connection. When the
The man page for SSL_write() mentions that I should call
SSL_get_error() upon failure:
http://www.openssl.org/docs/ssl/SSL_write.html
Is that all I have to do? Or do I should I inspect the error stack too?
I guess I don't have any specific question here, just looking for discussion.
-Patrick
-Original Message-
From: Patrick Patterson
On 12/02/10 8:51 AM, skillz...@gmail.com wrote:
Is there a way (via the API rather than the tool) to tell
OpenSSL that
the sub-CA certificate is trusted and it doesn't need to
walk further
up the chain? For my case, I embed the sub-CA
Hi there
I have some trouble using ssl in Apples Mail.
I have two certificates, one for private (j...@me.com) and one for business
(j...@acme.com).
Both are valid certificates from Verisign.
With both certificates I can sign and encrypt (ok, encrypt not really depends
on my cert), but I can
Got it fixed by setting:
export LD_PRELOAD=/usr/lib/libpthread.1:/usr/lib/libcl.2
Regards,
--Vikram
-Original Message-
From: owner-openssl-us...@openssl.org
[mailto:owner-openssl-us...@openssl.org] On Behalf Of Vikram Arwade
Sent: Thursday, February 18, 2010 6:08 PM
To:
On Mon, Feb 22, 2010, Andre Dieball wrote:
Hi there
I have some trouble using ssl in Apples Mail.
I have two certificates, one for private (j...@me.com) and one for business
(j...@acme.com).
Both are valid certificates from Verisign.
With both certificates I can sign and encrypt (ok,
When 0.9.8m beta 1 was released 1 month ago, I presumed that
0.9.8m would follow shortly, presumably some time after the
renegotiation draft was approved, which happened ~2 weeks ago.
So, now that RFC5746 has been upgraded from draft to final,
can we anticipate that 0.9.8m will be released soon?
