From fd9e244370d13606182a144833a1d3244cff5b85 Mon Sep 17 00:00:00 2001 From: Matt Caswell Date: Sat, 5 Jul 2014 22:31:05 +0100 Subject: [PATCH] Fixed error in pod files with latest versions of pod2man --- doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod b/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod index 0ea42bd8d1..da0dd0f597 100644 --- a/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod +++ b/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod @@ -76,7 +76,7 @@ further processing will occur. The following return values have meaning: =over 4 -=item 2 +=item Z<>2 This indicates that the I and I have been set and the session can continue on those parameters. Additionally it indicates that the session @@ -84,12 +84,12 @@ ticket is in a renewal period and should be replaced. The OpenSSL library will call I again with an enc argument of 1 to set the new ticket (see RFC5077 3.3 paragraph 2). -=item 1 +=item Z<>1 This indicates that the I and I have been set and the session can continue on those parameters. -=item 0 +=item Z<>0 This indicates that it was not possible to set/retrieve a session ticket and the SSL/TLS session will continue by by negiotationing a set of cryptographic -- 2.34.1