> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf
> Of Salz, Rich via openssl-users
> Sent: Wednesday, December 06, 2017 15:22
>
> ➢Or at least that used to be the case. TLSv1.3 got rid of renegotiation,
> so if
> you have a TLSv1.3 connection, it will never
➢Or at least that used to be the case. TLSv1.3 got rid of renegotiation, so
if you have a TLSv1.3 connection, it will never renegotiate.
But it could ask for a certificate, which would trigger SSL_WANT_WRITE
--
openssl-users mailing list
To unsubscribe:
> From: openssl-users [mailto:openssl-users-boun...@openssl.org] On Behalf Of
> pratyush parimal
> Sent: Wednesday, December 06, 2017 12:55
> But what I don't understand is, why does the library need to re-do the
> handshake?
I don't wish to sound rude, but this is answered right in the
Hi all,
I see a lot of questions and answers about how to
handle SSL_ERROR_WANT_READ / WRITE during SSL_read/write, and I understand
that the error is returned when the SSL library needs to do a handshake in
the middle of read/write operation, so we need to repeat the call when the
appropriate
