summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authortb <>2018-07-23 18:30:29 +0000
committertb <>2018-07-23 18:30:29 +0000
commitbdf3e94d22b5b2f5e9af09ab9e63532e27f57819 (patch)
tree11c9314f5aad0e6dd571dfaae679cbba4980b29c
parenta414a4a58297604ed0b1b4f44bb62271788eb36c (diff)
downloadopenbsd-bdf3e94d22b5b2f5e9af09ab9e63532e27f57819.tar.gz
openbsd-bdf3e94d22b5b2f5e9af09ab9e63532e27f57819.tar.bz2
openbsd-bdf3e94d22b5b2f5e9af09ab9e63532e27f57819.zip
Document tls_peer_ocsp_result() and use it in place of the non-existent
tls_peer_ocsp_result_msg() in the documentation. input & ok jsing Reads fine to jmc and makes sense to schwarze
-rw-r--r--src/lib/libtls/man/tls_ocsp_process_response.318
1 files changed, 12 insertions, 6 deletions
diff --git a/src/lib/libtls/man/tls_ocsp_process_response.3 b/src/lib/libtls/man/tls_ocsp_process_response.3
index cb979e8088..b40e9a02d5 100644
--- a/src/lib/libtls/man/tls_ocsp_process_response.3
+++ b/src/lib/libtls/man/tls_ocsp_process_response.3
@@ -1,4 +1,4 @@
1.\" $OpenBSD: tls_ocsp_process_response.3,v 1.4 2017/01/29 18:00:21 beck Exp $ 1.\" $OpenBSD: tls_ocsp_process_response.3,v 1.5 2018/07/23 18:30:29 tb Exp $
2.\" 2.\"
3.\" Copyright (c) 2016 Bob Beck <beck@openbsd.org> 3.\" Copyright (c) 2016 Bob Beck <beck@openbsd.org>
4.\" 4.\"
@@ -14,7 +14,7 @@
14.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF 14.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
15.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. 15.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
16.\" 16.\"
17.Dd $Mdocdate: January 29 2017 $ 17.Dd $Mdocdate: July 23 2018 $
18.Dt TLS_OCSP_PROCESS_RESPONSE 3 18.Dt TLS_OCSP_PROCESS_RESPONSE 3
19.Os 19.Os
20.Sh NAME 20.Sh NAME
@@ -23,7 +23,7 @@
23.Nm tls_peer_ocsp_crl_reason , 23.Nm tls_peer_ocsp_crl_reason ,
24.Nm tls_peer_ocsp_next_update , 24.Nm tls_peer_ocsp_next_update ,
25.Nm tls_peer_ocsp_response_status , 25.Nm tls_peer_ocsp_response_status ,
26.Nm tls_peer_ocsp_result_msg , 26.Nm tls_peer_ocsp_result ,
27.Nm tls_peer_ocsp_revocation_time , 27.Nm tls_peer_ocsp_revocation_time ,
28.Nm tls_peer_ocsp_this_update , 28.Nm tls_peer_ocsp_this_update ,
29.Nm tls_peer_ocsp_url 29.Nm tls_peer_ocsp_url
@@ -45,7 +45,7 @@
45.Ft int 45.Ft int
46.Fn tls_peer_ocsp_response_status "struct tls *ctx" 46.Fn tls_peer_ocsp_response_status "struct tls *ctx"
47.Ft const char * 47.Ft const char *
48.Fn tls_peer_ocsp_result_msg "struct tls *ctx" 48.Fn tls_peer_ocsp_result "struct tls *ctx"
49.Ft time_t 49.Ft time_t
50.Fn tls_peer_ocsp_revocation_time "struct tls *ctx" 50.Fn tls_peer_ocsp_revocation_time "struct tls *ctx"
51.Ft time_t 51.Ft time_t
@@ -86,7 +86,13 @@ returns the OCSP next update time.
86.Fn tls_peer_ocsp_response_status 86.Fn tls_peer_ocsp_response_status
87returns the OCSP response status as per RFC 6960 section 2.3. 87returns the OCSP response status as per RFC 6960 section 2.3.
88.Pp 88.Pp
89.\" XXX Fn tls_peer_ocsp_result_msg does what? 89.Fn tls_peer_ocsp_result
90returns a string indicating the OCSP status.
91If the OCSP response was valid and the certificate was not
92revoked, the string indicates the OCSP certificate status.
93Otherwise, the string indicates
94the OCSP certificate revocation reason or the OCSP error.
95.Pp
90.Fn tls_peer_ocsp_revocation_time 96.Fn tls_peer_ocsp_revocation_time
91returns the OCSP revocation time. 97returns the OCSP revocation time.
92.Pp 98.Pp
@@ -139,7 +145,7 @@ and
139.Fn tls_peer_ocsp_this_update 145.Fn tls_peer_ocsp_this_update
140return a time in epoch-seconds on success or -1 on error. 146return a time in epoch-seconds on success or -1 on error.
141.Pp 147.Pp
142.Fn tls_peer_ocsp_result_msg 148.Fn tls_peer_ocsp_result
143and 149and
144.Fn tls_peer_ocsp_url 150.Fn tls_peer_ocsp_url
145return 151return