--- 1/doc/apps/cms.pod +++ 1/doc/apps/cms.pod @@ -450,28 +450,28 @@ =over 4 -=item 0 +=item B<0> the operation was completely successfully. -=item 1 +=item B<1> an error occurred parsing the command options. -=item 2 +=item B<2> one of the input files could not be read. -=item 3 +=item B<3> an error occurred creating the CMS file or when reading the MIME message. -=item 4 +=item B<4> an error occurred decrypting or verifying the message. -=item 5 +=item B<5> the message was verified correctly but an error occurred writing out the signers certificates. --- 1/doc/apps/smime.pod +++ 1/doc/apps/smime.pod @@ -308,28 +308,28 @@ =over 4 -=item 0 +=item B<0> the operation was completely successfully. -=item 1 +=item B<1> an error occurred parsing the command options. -=item 2 +=item B<2> one of the input files could not be read. -=item 3 +=item B<3> an error occurred creating the PKCS#7 file or when reading the MIME message. -=item 4 +=item B<4> an error occurred decrypting or verifying the message. -=item 5 +=item B<5> the message was verified correctly but an error occurred writing out the signers certificates. --- 1/doc/apps/ts.pod +++ 1/doc/apps/ts.pod @@ -58,19 +58,19 @@ =over 4 -=item 1. +=item B<1.> The TSA client computes a one-way hash value for a data file and sends the hash to the TSA. -=item 2. +=item B<2.> The TSA attaches the current date and time to the received hash value, signs them and sends the time stamp token back to the client. By creating this token the TSA certifies the existence of the original data file at the time of response generation. -=item 3. +=item B<3.> The TSA client receives the time stamp token and verifies the signature on it. It also checks if the token contains the same hash --- 1/doc/crypto/X509_STORE_CTX_get_error.pod +++ 1/doc/crypto/X509_STORE_CTX_get_error.pod @@ -278,6 +278,8 @@ an application specific error. This will never be returned unless explicitly set by an application. +=back + =head1 NOTES The above functions should be used instead of directly referencing the fields --- 1/doc/ssl/SSL_COMP_add_compression_method.pod +++ 1/doc/ssl/SSL_COMP_add_compression_method.pod @@ -53,11 +53,11 @@ =over 4 -=item 0 +=item B<0> The operation succeeded. -=item 1 +=item B<1> The operation failed. Check the error queue to find out the reason. --- 1/doc/ssl/SSL_CTX_add_session.pod +++ 1/doc/ssl/SSL_CTX_add_session.pod @@ -52,13 +52,13 @@ =over 4 -=item 0 +=item B<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 B<1> The operation succeeded. --- 1/doc/ssl/SSL_CTX_load_verify_locations.pod +++ 1/doc/ssl/SSL_CTX_load_verify_locations.pod @@ -100,13 +100,13 @@ =over 4 -=item 0 +=item B<0> The operation failed because B and B are NULL or the processing at one of the locations specified failed. Check the error stack to find out the reason. -=item 1 +=item B<1> The operation succeeded. --- 1/doc/ssl/SSL_CTX_set_client_CA_list.pod +++ 1/doc/ssl/SSL_CTX_set_client_CA_list.pod @@ -66,11 +66,11 @@ =over 4 -=item 1 +=item B<1> The operation succeeded. -=item 0 +=item B<0> A failure while manipulating the STACK_OF(X509_NAME) object occurred or the X509_NAME could not be extracted from B. Check the error stack --- 1/doc/ssl/SSL_CTX_set_session_id_context.pod +++ 1/doc/ssl/SSL_CTX_set_session_id_context.pod @@ -64,13 +64,13 @@ =over 4 -=item 0 +=item B<0> The length B of the session id context B exceeded the maximum allowed length of B. The error is logged to the error stack. -=item 1 +=item B<1> The operation succeeded. --- 1/doc/ssl/SSL_CTX_set_ssl_version.pod +++ 1/doc/ssl/SSL_CTX_set_ssl_version.pod @@ -42,11 +42,11 @@ =over 4 -=item 0 +=item B<0> The new choice failed, check the error stack to find out the reason. -=item 1 +=item B<1> The operation succeeded. --- 1/doc/ssl/SSL_CTX_use_psk_identity_hint.pod +++ 1/doc/ssl/SSL_CTX_use_psk_identity_hint.pod @@ -94,7 +94,7 @@ connection will fail with decryption_error before it will be finished completely. -=item 0 +=item B<0> PSK identity was not found. An "unknown_psk_identity" alert message will be sent and the connection setup fails. --- 1/doc/ssl/SSL_accept.pod +++ 1/doc/ssl/SSL_accept.pod @@ -44,12 +44,12 @@ =over 4 -=item 1 +=item B<1> The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established. -=item 0 +=item B<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 --- 1/doc/ssl/SSL_clear.pod +++ 1/doc/ssl/SSL_clear.pod @@ -56,12 +56,12 @@ =over 4 -=item 0 +=item B<0> The SSL_clear() operation could not be performed. Check the error stack to find out the reason. -=item 1 +=item B<1> The SSL_clear() operation was successful. --- 1/doc/ssl/SSL_connect.pod +++ 1/doc/ssl/SSL_connect.pod @@ -41,12 +41,12 @@ =over 4 -=item 1 +=item B<1> The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established. -=item 0 +=item B<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 --- 1/doc/ssl/SSL_do_handshake.pod +++ 1/doc/ssl/SSL_do_handshake.pod @@ -45,12 +45,12 @@ =over 4 -=item 1 +=item B<1> The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been established. -=item 0 +=item B<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 --- 1/doc/ssl/SSL_read.pod +++ 1/doc/ssl/SSL_read.pod @@ -86,7 +86,7 @@ The read operation was successful; the return value is the number of bytes actually read from the TLS/SSL connection. -=item 0 +=item B<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 --- 1/doc/ssl/SSL_session_reused.pod +++ 1/doc/ssl/SSL_session_reused.pod @@ -27,11 +27,11 @@ =over 4 -=item 0 +=item B<0> A new session was negotiated. -=item 1 +=item B<1> A session was reused. --- 1/doc/ssl/SSL_set_fd.pod +++ 1/doc/ssl/SSL_set_fd.pod @@ -35,11 +35,11 @@ =over 4 -=item 0 +=item B<0> The operation failed. Check the error stack to find out why. -=item 1 +=item B<1> The operation succeeded. --- 1/doc/ssl/SSL_set_session.pod +++ 1/doc/ssl/SSL_set_session.pod @@ -37,11 +37,11 @@ =over 4 -=item 0 +=item B<0> The operation failed; check the error stack to find out the reason. -=item 1 +=item B<1> The operation succeeded. --- 1/doc/ssl/SSL_set_shutdown.pod +++ 1/doc/ssl/SSL_set_shutdown.pod @@ -24,7 +24,7 @@ =over 4 -=item 0 +=item B<0> No shutdown setting, yet. --- 1/doc/ssl/SSL_shutdown.pod +++ 1/doc/ssl/SSL_shutdown.pod @@ -92,12 +92,12 @@ =over 4 -=item 1 +=item B<1> The shutdown was successfully completed. The "close notify" alert was sent and the peer's "close notify" alert was received. -=item 0 +=item B<0> The shutdown is not yet finished. Call SSL_shutdown() for a second time, if a bidirectional shutdown shall be performed. --- 1/doc/ssl/SSL_write.pod +++ 1/doc/ssl/SSL_write.pod @@ -79,7 +79,7 @@ The write operation was successful, the return value is the number of bytes actually written to the TLS/SSL connection. -=item 0 +=item B<0> The write operation was not successful. Probably the underlying connection was closed. Call SSL_get_error() with the return value B to find out, --- 1/doc/ssl/SSL_CTX_use_psk_identity_hint.pod +++ 1/doc/ssl/SSL_CTX_use_psk_identity_hint.pod @@ -81,6 +81,8 @@ Return values from the server callback are interpreted as follows: +=over 4 + =item > 0 PSK identity was found and the server callback has provided the PSK @@ -99,4 +101,6 @@ PSK identity was not found. An "unknown_psk_identity" alert message will be sent and the connection setup fails. +=back + =cut