diff options
author | brucec <brucec@FreeBSD.org> | 2010-08-28 16:32:01 +0000 |
---|---|---|
committer | brucec <brucec@FreeBSD.org> | 2010-08-28 16:32:01 +0000 |
commit | 76d72447281953457a8a3a319fdc80070bc5152c (patch) | |
tree | 63ce23a3afd66a826b4c91820bd78ab505f92089 /secure | |
parent | 7ce28b7066d5299134f831d522470bcecba74fce (diff) | |
download | FreeBSD-src-76d72447281953457a8a3a319fdc80070bc5152c.zip FreeBSD-src-76d72447281953457a8a3a319fdc80070bc5152c.tar.gz |
Fix incorrect usage of 'assure' and 'insure'.
Approved by: rrs (mentor)
Diffstat (limited to 'secure')
-rw-r--r-- | secure/lib/libcrypto/man/BIO_s_bio.3 | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/secure/lib/libcrypto/man/BIO_s_bio.3 b/secure/lib/libcrypto/man/BIO_s_bio.3 index 34345d1..956f3f6 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 assure that the +not rely on the error value of \fISSL_operation()\fR but must ensure 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" |