> The discussion below wherein the term "you're screwed" is used
> seems to indicate that there is a deadlock situation, which isn't
> the case. There may or may not be performance issues associated
> with the scenario/use-case, but there's no deadlock.
>
> R
There is a deadlock. You are blocked in 'read' even though there is no
data
to read.
Again, here's the scenario:
1) 'select' indicates that there's data to read, but it's protocol-level
data due to a renegotiation, not application-level data.
2) Thinking there's application-level data, you call 'SSL_read'.
3) SSL_read calls 'read', gets the protocol-level data. It calls 'read'
again to try to get application-level data.
If this occurs on the side that is expected to send application-level
data
next, you deadlock.
DS
______________________________________________________________________
OpenSSL Project http://www.openssl.org
User Support Mailing List openssl-users@openssl.org
Automated List Manager [EMAIL PROTECTED]
