A bit more of description
This commit is contained in:
parent
f6b77e1b27
commit
d6b36fd385
@ -3,6 +3,12 @@ buggy_openssl_with_fullduplex
|
|||||||
|
|
||||||
Toy code which shows problems with non-blocking, fullduplex I/O & renegotiation in OpenSSL
|
Toy code which shows problems with non-blocking, fullduplex I/O & renegotiation in OpenSSL
|
||||||
|
|
||||||
|
What is it:
|
||||||
|
This code shows that it is not possible to use SSL_write() and SSL_read() functions in the same
|
||||||
|
way as ::send() and ::recv().
|
||||||
|
The main difference between SSL_write/read functions and send/recv system calls is that
|
||||||
|
SSL_write function may in fact read data from the socket in some situations (similary
|
||||||
|
SSL_read may need to write data to the socket).
|
||||||
|
|
||||||
How it works:
|
How it works:
|
||||||
|
|
||||||
@ -35,4 +41,4 @@ How it works:
|
|||||||
TCP:
|
TCP:
|
||||||
In TCP exchange we can see that transfer between client & server is OK until
|
In TCP exchange we can see that transfer between client & server is OK until
|
||||||
client sends "Client Hello" packet. This packet is sent when SSL_renegotiate
|
client sends "Client Hello" packet. This packet is sent when SSL_renegotiate
|
||||||
is called
|
is called
|
||||||
|
Loading…
Reference in New Issue
Block a user