Blame SOURCES/openssl-fips-0.9.8e-manfix.patch

c4366c
diff -up openssl-fips-0.9.8e/doc/apps/openssl.pod.manfix openssl-fips-0.9.8e/doc/apps/openssl.pod
c4366c
--- openssl-fips-0.9.8e/doc/apps/openssl.pod.manfix	2007-09-19 02:02:45.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/apps/openssl.pod	2013-07-17 16:53:35.344845801 +0200
c4366c
@@ -125,7 +125,7 @@ Generation of RSA Parameters.
c4366c
 
c4366c
 Online Certificate Status Protocol utility.
c4366c
 
c4366c
-=item L<B<passwd>|passwd(1)>
c4366c
+=item L<B<passwd>|sslpasswd(1)>
c4366c
 
c4366c
 Generation of hashed passwords.
c4366c
 
c4366c
@@ -137,7 +137,7 @@ PKCS#12 Data Management.
c4366c
 
c4366c
 PKCS#7 Data Management.
c4366c
 
c4366c
-=item L<B<rand>|rand(1)>
c4366c
+=item L<B<rand>|sslrand(1)>
c4366c
 
c4366c
 Generate pseudo-random bytes.
c4366c
 
c4366c
@@ -341,9 +341,9 @@ L<crl(1)|crl(1)>, L
c4366c
 L<dhparam(1)|dhparam(1)>, L<dsa(1)|dsa(1)>, L<dsaparam(1)|dsaparam(1)>,
c4366c
 L<enc(1)|enc(1)>, L<gendsa(1)|gendsa(1)>,
c4366c
 L<genrsa(1)|genrsa(1)>, L<nseq(1)|nseq(1)>, L<openssl(1)|openssl(1)>,
c4366c
-L<passwd(1)|passwd(1)>,
c4366c
+L<sslpasswd(1)|sslpasswd(1)>,
c4366c
 L<pkcs12(1)|pkcs12(1)>, L<pkcs7(1)|pkcs7(1)>, L<pkcs8(1)|pkcs8(1)>,
c4366c
-L<rand(1)|rand(1)>, L<req(1)|req(1)>, L<rsa(1)|rsa(1)>,
c4366c
+L<sslrand(1)|sslrand(1)>, L<req(1)|req(1)>, L<rsa(1)|rsa(1)>,
c4366c
 L<rsautl(1)|rsautl(1)>, L<s_client(1)|s_client(1)>,
c4366c
 L<s_server(1)|s_server(1)>, L<s_time(1)|s_time(1)>,
c4366c
 L<smime(1)|smime(1)>, L<spkac(1)|spkac(1)>,
c4366c
diff -up openssl-fips-0.9.8e/doc/apps/smime.pod.manfix openssl-fips-0.9.8e/doc/apps/smime.pod
c4366c
--- openssl-fips-0.9.8e/doc/apps/smime.pod.manfix	2006-06-09 17:42:16.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/apps/smime.pod	2013-07-17 16:53:35.345845817 +0200
c4366c
@@ -265,28 +265,28 @@ encrypted data is used for other purpose
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 the operation was completely successfully.
c4366c
 
c4366c
-=item 1 
c4366c
+=item C<1>
c4366c
 
c4366c
 an error occurred parsing the command options.
c4366c
 
c4366c
-=item 2
c4366c
+=item C<2>
c4366c
 
c4366c
 one of the input files could not be read.
c4366c
 
c4366c
-=item 3
c4366c
+=item C<3>
c4366c
 
c4366c
 an error occurred creating the PKCS#7 file or when reading the MIME
c4366c
 message.
c4366c
 
c4366c
-=item 4
c4366c
+=item C<4>
c4366c
 
c4366c
 an error occurred decrypting or verifying the message.
c4366c
 
c4366c
-=item 5
c4366c
+=item C<5>
c4366c
 
c4366c
 the message was verified correctly but an error occurred writing out
c4366c
 the signers certificates.
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_accept.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_accept.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_accept.pod.manfix	2003-06-03 11:59:44.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_accept.pod	2013-07-17 16:57:03.617836245 +0200
c4366c
@@ -44,12 +44,12 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
c4366c
 established.
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The TLS/SSL handshake was not successful but was shut down controlled and
c4366c
 by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_clear.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_clear.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_clear.pod.manfix	2002-02-27 09:08:57.000000000 +0100
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_clear.pod	2013-07-17 16:53:35.349845898 +0200
c4366c
@@ -50,12 +50,12 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The SSL_clear() operation could not be performed. Check the error stack to
c4366c
 find out the reason.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The SSL_clear() operation was successful.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_COMP_add_compression_method.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_COMP_add_compression_method.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_COMP_add_compression_method.pod.manfix	2013-07-17 12:30:39.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_COMP_add_compression_method.pod	2013-07-17 16:53:35.349845898 +0200
c4366c
@@ -60,11 +60,11 @@ SSL_COMP_add_compression_method() may re
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The operation succeeded.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The operation failed. Check the error queue to find out the reason.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_connect.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_connect.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_connect.pod.manfix	2003-06-03 11:59:44.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_connect.pod	2013-07-17 16:56:43.854426631 +0200
c4366c
@@ -41,12 +41,12 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
c4366c
 established.
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The TLS/SSL handshake was not successful but was shut down controlled and
c4366c
 by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_CTX_add_session.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_CTX_add_session.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_CTX_add_session.pod.manfix	2002-10-29 01:33:01.000000000 +0100
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_CTX_add_session.pod	2013-07-17 16:53:35.353845983 +0200
c4366c
@@ -52,13 +52,13 @@ The following values are returned by all
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
  The operation failed. In case of the add operation, it was tried to add
c4366c
  the same (identical) session twice. In case of the remove operation, the
c4366c
  session was not found in the cache.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
  
c4366c
  The operation succeeded.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_CTX_load_verify_locations.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_CTX_load_verify_locations.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_CTX_load_verify_locations.pod.manfix	2001-09-07 08:13:39.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_CTX_load_verify_locations.pod	2013-07-17 16:53:35.354846005 +0200
c4366c
@@ -100,13 +100,13 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The operation failed because B<CAfile> and B<CApath> are NULL or the
c4366c
 processing at one of the locations specified failed. Check the error
c4366c
 stack to find out the reason.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The operation succeeded.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_client_CA_list.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_client_CA_list.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_client_CA_list.pod.manfix	2001-04-12 18:02:34.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_client_CA_list.pod	2013-07-17 16:54:37.273839574 +0200
c4366c
@@ -66,11 +66,11 @@ values:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The operation succeeded.
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 A failure while manipulating the STACK_OF(X509_NAME) object occurred or
c4366c
 the X509_NAME could not be extracted from B<cacert>. Check the error stack
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_session_id_context.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_session_id_context.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_session_id_context.pod.manfix	2004-06-14 15:27:28.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_session_id_context.pod	2013-07-17 16:53:35.358846090 +0200
c4366c
@@ -64,13 +64,13 @@ return the following values:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The length B<sid_ctx_len> of the session id context B<sid_ctx> exceeded
c4366c
 the maximum allowed length of B<SSL_MAX_SSL_SESSION_ID_LENGTH>. The error
c4366c
 is logged to the error stack.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The operation succeeded.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_ssl_version.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_ssl_version.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_ssl_version.pod.manfix	2001-03-08 18:24:01.000000000 +0100
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_CTX_set_ssl_version.pod	2013-07-17 16:53:35.360846132 +0200
c4366c
@@ -42,11 +42,11 @@ and SSL_set_ssl_method():
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The new choice failed, check the error stack to find out the reason.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The operation succeeded.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_do_handshake.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_do_handshake.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_do_handshake.pod.manfix	2002-07-19 13:05:49.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_do_handshake.pod	2013-07-17 16:55:03.530386725 +0200
c4366c
@@ -45,12 +45,12 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
c4366c
 established.
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The TLS/SSL handshake was not successful but was shut down controlled and
c4366c
 by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_read.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_read.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_read.pod.manfix	2001-09-13 15:21:38.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_read.pod	2013-07-17 16:53:45.846069565 +0200
c4366c
@@ -81,7 +81,7 @@ The following return values can occur:
c4366c
 The read operation was successful; the return value is the number of
c4366c
 bytes actually read from the TLS/SSL connection.
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The read operation was not successful. The reason may either be a clean
c4366c
 shutdown due to a "close notify" alert sent by the peer (in which case
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_session_reused.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_session_reused.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_session_reused.pod.manfix	2001-07-20 20:57:15.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_session_reused.pod	2013-07-17 16:53:45.848069608 +0200
c4366c
@@ -27,11 +27,11 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 A new session was negotiated.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 A session was reused.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_set_fd.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_set_fd.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_set_fd.pod.manfix	2000-09-16 18:00:38.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_set_fd.pod	2013-07-17 16:53:45.849069630 +0200
c4366c
@@ -35,11 +35,11 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The operation failed. Check the error stack to find out why.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The operation succeeded.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_set_session.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_set_session.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_set_session.pod.manfix	2001-10-12 14:29:16.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_set_session.pod	2013-07-17 16:53:45.851069674 +0200
c4366c
@@ -37,11 +37,11 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The operation failed; check the error stack to find out the reason.
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The operation succeeded.
c4366c
 
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_shutdown.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_shutdown.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_shutdown.pod.manfix	2004-11-14 14:55:16.000000000 +0100
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_shutdown.pod	2013-07-17 16:56:04.569658682 +0200
c4366c
@@ -92,12 +92,12 @@ The following return values can occur:
c4366c
 
c4366c
 =over 4
c4366c
 
c4366c
-=item 1
c4366c
+=item C<1>
c4366c
 
c4366c
 The shutdown was successfully completed. The "close notify" alert was sent
c4366c
 and the peer's "close notify" alert was received.
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The shutdown is not yet finished. Call SSL_shutdown() for a second time,
c4366c
 if a bidirectional shutdown shall be performed.
c4366c
diff -up openssl-fips-0.9.8e/doc/ssl/SSL_write.pod.manfix openssl-fips-0.9.8e/doc/ssl/SSL_write.pod
c4366c
--- openssl-fips-0.9.8e/doc/ssl/SSL_write.pod.manfix	2002-07-19 13:53:54.000000000 +0200
c4366c
+++ openssl-fips-0.9.8e/doc/ssl/SSL_write.pod	2013-07-17 16:53:45.854069737 +0200
c4366c
@@ -79,7 +79,7 @@ The following return values can occur:
c4366c
 The write operation was successful, the return value is the number of
c4366c
 bytes actually written to the TLS/SSL connection.
c4366c
 
c4366c
-=item 0
c4366c
+=item C<0>
c4366c
 
c4366c
 The write operation was not successful. Probably the underlying connection
c4366c
 was closed. Call SSL_get_error() with the return value B<ret> to find out,