generic-library/openssl
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

POD: Fix item numbering

Browse Source 
Newer pod2man considers =item [1-9] part of a numbered list, while =item
0 starts an unnumbered list. Add a zero effect formatting mark to override
this.

doc/apps/smime.pod around line 315: Expected text after =item, not a
number
...

PR#3146
This commit is contained in:
Lubomir Rintel 2013-10-21 11:03:01 +02:00 committed by Dr. Stephen Henson
parent 5fdeb58ccd
commit c8919dde09
19 changed files with 43 additions and 43 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/apps/cms.pod
View File

@ -463,28 +463,28 @@ remains DER.
=over 4
=item 0
=item Z<>0
the operation was completely successfully.
=item 1
=item Z<>1
an error occurred parsing the command options.
=item 2
=item Z<>2
one of the input files could not be read.
=item 3
=item Z<>3
an error occurred creating the CMS file or when reading the MIME
message.
=item 4
=item Z<>4
an error occurred decrypting or verifying the message.
=item 5
=item Z<>5
the message was verified correctly but an error occurred writing out
the signers certificates.

12
doc/apps/smime.pod
View File

@ -308,28 +308,28 @@ remains DER.
=over 4
=item 0
=item Z<>0
the operation was completely successfully.
=item 1
=item Z<>1
an error occurred parsing the command options.
=item 2
=item Z<>2
one of the input files could not be read.
=item 3
=item Z<>3
an error occurred creating the PKCS#7 file or when reading the MIME
message.
=item 4
=item Z<>4
an error occurred decrypting or verifying the message.
=item 5
=item Z<>5
the message was verified correctly but an error occurred writing out
the signers certificates.

4
doc/ssl/SSL_COMP_add_compression_method.pod
View File

@ -53,11 +53,11 @@ SSL_COMP_add_compression_method() may return the following values:
=over 4
=item 0
=item Z<>0
The operation succeeded.
=item 1
=item Z<>1
The operation failed. Check the error queue to find out the reason.

4
doc/ssl/SSL_CTX_add_session.pod
View File

@ -52,13 +52,13 @@ The following values are returned by all functions:
=over 4
=item 0
=item Z<>0
The operation failed. In case of the add operation, it was tried to add
the same (identical) session twice. In case of the remove operation, the
session was not found in the cache.
=item 1
=item Z<>1
The operation succeeded.

4
doc/ssl/SSL_CTX_load_verify_locations.pod
View File

@ -100,13 +100,13 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
The operation failed because B<CAfile> and B<CApath> are NULL or the
processing at one of the locations specified failed. Check the error
stack to find out the reason.
=item 1
=item Z<>1
The operation succeeded.

4
doc/ssl/SSL_CTX_set_client_CA_list.pod
View File

@ -66,13 +66,13 @@ values:
=over 4
=item 0
=item Z<>0
A failure while manipulating the STACK_OF(X509_NAME) object occurred or
the X509_NAME could not be extracted from B<cacert>. Check the error stack
to find out the reason.
=item 1
=item Z<>1
The operation succeeded.

4
doc/ssl/SSL_CTX_set_session_id_context.pod
View File

@ -64,13 +64,13 @@ return the following values:
=over 4
=item 0
=item Z<>0
The length B<sid_ctx_len> of the session id context B<sid_ctx> exceeded
the maximum allowed length of B<SSL_MAX_SSL_SESSION_ID_LENGTH>. The error
is logged to the error stack.
=item 1
=item Z<>1
The operation succeeded.

4
doc/ssl/SSL_CTX_set_ssl_version.pod
View File

@ -42,11 +42,11 @@ and SSL_set_ssl_method():
=over 4
=item 0
=item Z<>0
The new choice failed, check the error stack to find out the reason.
=item 1
=item Z<>1
The operation succeeded.

2
doc/ssl/SSL_CTX_use_psk_identity_hint.pod
View File

@ -96,7 +96,7 @@ 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 0
=item Z<>0
PSK identity was not found. An "unknown_psk_identity" alert message
will be sent and the connection setup fails.

4
doc/ssl/SSL_accept.pod
View File

@ -44,13 +44,13 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
The TLS/SSL handshake was not successful but was shut down controlled and
by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
return value B<ret> to find out the reason.
=item 1
=item Z<>1
The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
established.

4
doc/ssl/SSL_clear.pod
View File

@ -56,12 +56,12 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
The SSL_clear() operation could not be performed. Check the error stack to
find out the reason.
=item 1
=item Z<>1
The SSL_clear() operation was successful.

4
doc/ssl/SSL_connect.pod
View File

@ -41,13 +41,13 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
The TLS/SSL handshake was not successful but was shut down controlled and
by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
return value B<ret> to find out the reason.
=item 1
=item Z<>1
The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
established.

4
doc/ssl/SSL_do_handshake.pod
View File

@ -45,13 +45,13 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
The TLS/SSL handshake was not successful but was shut down controlled and
by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
return value B<ret> to find out the reason.
=item 1
=item Z<>1
The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
established.

2
doc/ssl/SSL_read.pod
View File

@ -86,7 +86,7 @@ The following return values can occur:
The read operation was successful; the return value is the number of
bytes actually read from the TLS/SSL connection.
=item 0
=item Z<>0
The read operation was not successful. The reason may either be a clean
shutdown due to a "close notify" alert sent by the peer (in which case

4
doc/ssl/SSL_session_reused.pod
View File

@ -27,11 +27,11 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
A new session was negotiated.
=item 1
=item Z<>1
A session was reused.

4
doc/ssl/SSL_set_fd.pod
View File

@ -35,11 +35,11 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
The operation failed. Check the error stack to find out why.
=item 1
=item Z<>1
The operation succeeded.

4
doc/ssl/SSL_set_session.pod
View File

@ -37,11 +37,11 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
The operation failed; check the error stack to find out the reason.
=item 1
=item Z<>1
The operation succeeded.

4
doc/ssl/SSL_shutdown.pod
View File

@ -92,14 +92,14 @@ The following return values can occur:
=over 4
=item 0
=item Z<>0
The shutdown is not yet finished. Call SSL_shutdown() for a second time,
if a bidirectional shutdown shall be performed.
The output of L<SSL_get_error(3)|SSL_get_error(3)> may be misleading, as an
erroneous SSL_ERROR_SYSCALL may be flagged even though no error occurred.
=item 1
=item Z<>1
The shutdown was successfully completed. The "close notify" alert was sent
and the peer's "close notify" alert was received.

2
doc/ssl/SSL_write.pod
View File

@ -79,7 +79,7 @@ The following return values can occur:
The write operation was successful, the return value is the number of
bytes actually written to the TLS/SSL connection.
=item 0
=item Z<>0
The write operation was not successful. Probably the underlying connection
was closed. Call SSL_get_error() with the return value B<ret> to find out,