diff options
| author | Scott Schaefer <saschaefer@neurodiverse.org> | 2014-08-13 14:42:23 -0400 |
|---|---|---|
| committer | Rich Salz <rsalz@openssl.org> | 2014-09-08 11:18:58 -0400 |
| commit | 61a44b76a0abfc96e9abd902000ad3f5b7945c6a (patch) | |
| tree | cc5a2afbeb5ce64715cc92df43a34bd2bc6251ac | |
| parent | 45236ed6a4639ae8c33ce8e8a7dff33ad727e993 (diff) | |
RT2518: fix pod2man errors
pod2man now complains when item tags are not sequential.
Also complains about missing =back and other tags.
Silence the warnings; most were already done.
Reviewed-by: Tim Hudson <tjh@openssl.org>
(cherry picked from commit fe7573042fa7f406fedb78d959659b39a7a1dcfb)
| -rw-r--r-- | doc/ssl/SSL_CTX_use_psk_identity_hint.pod | 12 | ||||
| -rw-r--r-- | doc/ssl/SSL_shutdown.pod | 2 |
2 files changed, 7 insertions, 7 deletions
diff --git a/doc/ssl/SSL_CTX_use_psk_identity_hint.pod b/doc/ssl/SSL_CTX_use_psk_identity_hint.pod index 9da7201a99..12db0daa19 100644 --- a/doc/ssl/SSL_CTX_use_psk_identity_hint.pod +++ b/doc/ssl/SSL_CTX_use_psk_identity_hint.pod @@ -83,7 +83,12 @@ Return values from the server callback are interpreted as follows: =over 4 -=item > 0 +=item Z<>0 + +PSK identity was not found. An "unknown_psk_identity" alert message +will be sent and the connection setup fails. + +=item E<gt>0 PSK identity was found and the server callback has provided the PSK successfully in parameter B<psk>. Return value is the length of @@ -96,11 +101,6 @@ data to B<psk> and return the length of the random data, so the connection will fail with decryption_error before it will be finished completely. -=item Z<>0 - -PSK identity was not found. An "unknown_psk_identity" alert message -will be sent and the connection setup fails. - =back =cut diff --git a/doc/ssl/SSL_shutdown.pod b/doc/ssl/SSL_shutdown.pod index 85d4a64b03..efbff5a0a3 100644 --- a/doc/ssl/SSL_shutdown.pod +++ b/doc/ssl/SSL_shutdown.pod @@ -104,7 +104,7 @@ erroneous SSL_ERROR_SYSCALL may be flagged even though no error occurred. The shutdown was successfully completed. The "close notify" alert was sent and the peer's "close notify" alert was received. -=item -1 +=item E<lt>0 The shutdown was not successful because a fatal error occurred either at the protocol level or a connection failure occurred. It can also occur if |