From b0d8c2e5aa0a91148f7233a0f09e2308a390be43 Mon Sep 17 00:00:00 2001 From: jsing <> Date: Sat, 10 Feb 2018 06:07:43 +0000 Subject: Be more specific about when the session file will be updated. --- src/lib/libtls/man/tls_config_set_session_id.3 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src') diff --git a/src/lib/libtls/man/tls_config_set_session_id.3 b/src/lib/libtls/man/tls_config_set_session_id.3 index e8a5e60cd7..d969e01e33 100644 --- a/src/lib/libtls/man/tls_config_set_session_id.3 +++ b/src/lib/libtls/man/tls_config_set_session_id.3 @@ -1,4 +1,4 @@ -.\" $OpenBSD: tls_config_set_session_id.3,v 1.4 2018/02/10 04:43:16 jsing Exp $ +.\" $OpenBSD: tls_config_set_session_id.3,v 1.5 2018/02/10 06:07:43 jsing Exp $ .\" .\" Copyright (c) 2017 Claudio Jeker .\" Copyright (c) 2018 Joel Sing @@ -58,7 +58,7 @@ write the file (0600). If the file has a non-zero length, the client will attempt to read session data from this file and resume the previous TLS session with the server. Upon a successful handshake the file will be updated with current session -data. +data, if available. The caller is responsible for closing this file descriptor, after all TLS contexts that have been configured to use it have been freed via .Fn tls_free . -- cgit v1.2.3-55-g6feb