Be explicit about when it is safe to call tls_config_free().

Discussed with beck@

1 files changed, 8 insertions, 3 deletions

diff --git a/src/lib/libtls/man/tls_init.3 b/src/lib/libtls/man/tls_init.3
index 7c461cbcb7..c83c0375ab 100644
--- a/src/lib/libtls/man/tls_init.3
+++ b/src/lib/libtls/man/tls_init.3
@@ -1,4 +1,4 @@
-.\" $OpenBSD: tls_init.3,v 1.6 2017/04/27 20:41:08 schwarze Exp $
+.\" $OpenBSD: tls_init.3,v 1.7 2017/05/06 21:18:48 jsing Exp $
 .\"
 .\" Copyright (c) 2014 Ted Unangst <tedu@openbsd.org>
 .\" Copyright (c) 2016 Joel Sing <jsing@openbsd.org>
@@ -16,7 +16,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: April 27 2017 $
+.Dd $Mdocdate: May 6 2017 $
 .Dt TLS_INIT 3
 .Os
 .Sh NAME
@@ -97,9 +97,14 @@ After use, a TLS connection should be closed with
 and then freed by calling
 .Xr tls_free 3 .
 .Pp
-When no more contexts are to be created,
+When no more contexts are to be configured,
 the configuration object should be freed by calling
 .Fn tls_config_free .
+It is safe to call
+.Fn tls_config_free
+as soon as the final call to
+.Fn tls_configure
+has been made.
 If
 .Fa config
 is