From d6b36fd385c226db07d064adc8bcf4ade3e1d818 Mon Sep 17 00:00:00 2001 From: flowher Date: Wed, 9 Oct 2013 00:21:47 +0200 Subject: [PATCH] A bit more of description --- README.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 0b22019..731a81d 100644 --- a/README.md +++ b/README.md @@ -3,6 +3,12 @@ buggy_openssl_with_fullduplex 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: @@ -35,4 +41,4 @@ How it works: TCP: 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 - is called \ No newline at end of file + is called