From 623acb90cc7fdd5bd51a850ee6acc45b661daa83 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 (cherry picked from commit 07255f0a76d9d349d915e14f969b9ff2ee0d1953) --- 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 610523407a..b9371d7697 100644 --- a/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod +++ b/doc/ssl/SSL_CTX_set_tlsext_ticket_key_cb.pod @@ -74,7 +74,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 @@ -82,12 +82,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