Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of David Schwartz
Sent: Monday, February 07, 2005 6:35 PM
To: openssl-users@openssl.org
Subject: RE: Renegotiation with reader and writer threads.
>My client and server has two threads each: a reader thread and a writer
> Now coming to the first part of your comment. As I understand it, the
> manipulation of SSL connection
> needs mutex, but can the SSL_read(s) and SSL_write(s) be done from two
> threads independently?
It can be done from two threads, but it requires a mutex. Thus the two
threads are not
lto:[EMAIL PROTECTED] On Behalf Of Kumar, Sunil
> Sent: Tuesday, February 08, 2005 6:30 AM
> To: openssl-users@openssl.org
> Subject: RE: Renegotiation with reader and writer threads.
>
>
> >>>"I'm not sure what you mean by "reader" and "writ
>>>"I'm not sure what you mean by "reader" and "writer", but if you mean
that both threads call OpenSSL functions, you will need to associate a
mutex with each connection to ensure that the >>>reader thread and
writer thread are not trying to manipulate that SSL connection at the
same time."
The
>My client and server has two threads each: a reader thread and a writer
thread.
>I have put the renegotiation code in the reader thread. It works for most
>of the time but occasionally the client gets an "Encrypted Alert" message
>( I suspect that this happens when the application data somehow ge
