document the interaction with BIO_dup_chain(3)

1 files changed, 14 insertions, 2 deletions

diff --git a/lib/libssl/man/BIO_f_ssl.3 b/lib/libssl/man/BIO_f_ssl.3
index 5e18a85bd1c..7292e63f518 100644
--- a/lib/libssl/man/BIO_f_ssl.3
+++ b/lib/libssl/man/BIO_f_ssl.3
@@ -1,4 +1,4 @@
-.\" $OpenBSD: BIO_f_ssl.3,v 1.12 2022/03/31 17:27:18 naddy Exp $
+.\" $OpenBSD: BIO_f_ssl.3,v 1.13 2022/12/18 20:24:52 schwarze Exp $
 .\" full merge up to: OpenSSL f672aee4 Feb 9 11:52:40 2016 -0500
 .\" selective merge up to: OpenSSL 61f805c1 Jan 16 01:01:46 2018 +0800
 .\"
@@ -50,7 +50,7 @@
 .\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED
 .\" OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: March 31 2022 $
+.Dd $Mdocdate: December 18 2022 $
 .Dt BIO_F_SSL 3
 .Os
 .Sh NAME
@@ -305,6 +305,18 @@ should be used for non blocking connect
 to determine if the call should be retried.
 If an SSL connection has already been established, this call has no effect.
 .Pp
+When a chain containing an SSL BIO is copied with
+.Xr BIO_dup_chain 3 ,
+.Xr SSL_dup 3
+is called internally to copy the
+.Vt SSL
+object from the existing BIO object to the new BIO object,
+and the internal data related to
+.Fn BIO_set_ssl_renegotiate_bytes
+and
+.Fn BIO_set_ssl_renegotiate_timeout
+is also copied.
+.Pp
 .Vt SSL
 .Vt BIO Ns s
 are exceptional in that if the underlying transport is non-blocking they can