Hi,
I'm a bit confused about usage of SSL_write()/SSL_read() in
non-blocking connectors. Let say I do SSL_write() and I get
SSL_ERROR_WANT_WRITE. It means I have to do SSL_write() again. But does
it mean that I can't do SSL_read() until SSL_write() returns with
success?
Any idea?
Kris
()/SSL_read() in non-blocking
connectors. Let say I do SSL_write() and I get SSL_ERROR_WANT_WRITE. It
means I have to do SSL_write() again. But does it mean that I can't do
SSL_read() until SSL_write() returns with success?
Any idea?
Kris
operation).
Good luck,
James
On Thu, Sep 19, 2013 at 2:02 AM, Krzysztof Kwiatkowski krzys...@leeds.pl
wrote:
Hi,
I'm a bit confused about usage of SSL_write()/SSL_read() in non-blocking
connectors. Let say I do SSL_write() and I get SSL_ERROR_WANT_WRITE. It
means I have to do SSL_write
:)
Thanks
soji.
-Original Message-
From: [EMAIL PROTECTED] on behalf of David Schwartz
Sent: Thu 4/12/2007 8:35 AM
To: [EMAIL PROTECTED]
Subject: RE: SSL_write and SSL_read
Apologies if this was already responded to:
Or if I put it in another way, if SSL_read() returns
Hi David,
Thanks for your sound replay :)
I'll take care of this caveat in action...
I understand that the same scenario would be applicable in the
case of multiple threads handling the same fd even though we
managed to get it synchronized using some mutex.
Please correct me if I'm
Apologies if this was already responded to:
Or if I put it in another way, if SSL_read() returns,
SSL_ERROR_WANT_READ or SSL_ERROR_WANT_WRITE (from SSL_get_error())
on the socket fd then, can I send data on the same socket using
SSL_write() ? (Provided, both read and write operations on the
Hi Friends,
I've an application which supports TLS communication in which, socket
descriptors are handled in threads.
Let's take an arbitrary socket descriptor fd and here we go,
Can I send data through fd using SSL_write() if I'm in the middle of
reading the data from the same fd?
and if the SSL_read return value is below zero
SSL_get_error returns only WANT_READ. In that case there was never someting
in the outgoing BIO. Therefore I assume that simply means: There is no more
data to decrypt.
Irrespective of whether you are doing SSL_read or
SSL_write... That is why you have to check
Girish Venkatachalam wrote:
But did you factor the fact that an SSL renegotiation
or handshake can happen anytime during the
conversation?
Thats not strictly true, the receiving end does have a tiny bit of
control over when to process it. From recent discussion in this list my
BIO. Therefore I assume that simply means: There is no more
data to decrypt.
Irrespective of whether you are doing SSL_read or
SSL_write... That is why you have to check for pending
write during a SSL_read and vice versa in the non
blocking case.
We check for pending read/write only if SSL_read
At 11:14 18.07.2006 +0100, you wrote:
I'm a little interested in the three_byte_header situation you raised.
If I understand the outline correctly you were questioning whether it is
safe to mix calls of SSL_read() and SSL_write() because when you looked
over the SSL library code you saw
Hi,
Our application sends/receives audio/video streams on a ssl connection. The
i/o is done by our application and we communicate with the ssl library via
BIO_read/BIO_write and SSL_write/SSL_read. All operations are non blocking.
Everything works fine until the processed packets per second
() as necessary to service inbound data.
It is safe to keep trying SSL_write() after every SSL_read() to see if
it can do more work, otherwise it will persist with the WANT_READ state.
If you are non-blocking the only special case is to start ignoring the
select/poll/read/write writability event
// at another place)
ERR_clear_error();
SendOutStandingSSLData();
}
}
}
...
}
It is safe to keep trying SSL_write() after every SSL_read() to see if
it can do more work, otherwise it will persist with the WANT_READ state.
I'm really
Excuse me if I am saying the obvious.
But did you factor the fact that an SSL renegotiation
or handshake can happen anytime during the
conversation?
Irrespective of whether you are doing SSL_read or
SSL_write... That is why you have to check for pending
write during a SSL_read and vice versa
15 matches
Mail list logo
