From 7adc5f91cff836324150e37db070cf854b475e73 Mon Sep 17 00:00:00 2001 From: brucec Date: Sat, 11 Sep 2010 10:49:56 +0000 Subject: Revert changes of 'assure' to 'ensure' made in r211936. Approved by: rrs (mentor) --- secure/lib/libcrypto/man/BIO_s_bio.3 | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'secure/lib/libcrypto/man') diff --git a/secure/lib/libcrypto/man/BIO_s_bio.3 b/secure/lib/libcrypto/man/BIO_s_bio.3 index 956f3f6..34345d1 100644 --- a/secure/lib/libcrypto/man/BIO_s_bio.3 +++ b/secure/lib/libcrypto/man/BIO_s_bio.3 @@ -317,7 +317,7 @@ find out, how many bytes must be written into the buffer before the .IX Header "WARNING" As the data is buffered, \fISSL_operation()\fR may return with a \s-1ERROR_SSL_WANT_READ\s0 condition, but there is still data in the write buffer. An application must -not rely on the error value of \fISSL_operation()\fR but must ensure that the +not rely on the error value of \fISSL_operation()\fR but must assure that the write buffer is always flushed first. Otherwise a deadlock may occur as the peer might be waiting for the data before being able to continue. .SH "SEE ALSO" -- cgit v1.1