Fix openssl pod docs to work with the very picky pod2man from perl-5.…

…18.0.

security/openssl/distinfo

@@ -1,4 +1,4 @@
-$NetBSD: distinfo,v 1.95 2013/02/13 14:35:19 taca Exp $
+$NetBSD: distinfo,v 1.96 2013/06/01 08:03:55 sbd Exp $
 
 SHA1 (openssl-1.0.1e.tar.gz) = 3f1b1223c9e8189bfe4e186d86449775bd903460
 RMD160 (openssl-1.0.1e.tar.gz) = 380827c16f18bed4f2eb3d54a387c7c089b2b299
@@ -10,4 +10,24 @@ SHA1 (patch-ae) = 7a58f1765a3761321dcc8dafc5fe2e33207be480
 SHA1 (patch-af) = 376f474f3809365a20a53cfe1c91eca4bc02a5cd
 SHA1 (patch-ag) = b407200455878a8a151fc9b4f771fe17552d04fc
 SHA1 (patch-ak) = 049250b9bd42e6f155145703135dab39a7ec17e0
+SHA1 (patch-doc_apps_cms.pod) = 24792a0db2d8566e0f8b52833de300f538f6a92e
+SHA1 (patch-doc_apps_smine.pod) = 277aee087892f867402ea73bae10383fe24d6e08
+SHA1 (patch-doc_crypto_X509__STORE__CTX__get__error.pod) = 39ceb8d8d88f47794c257286c958daa5c408dfd2
+SHA1 (patch-doc_ssl_SSL__COMP__add__compression__method.pod) = f3fcbe0eae26ac8e24fe937e529ea0dba6ea1639
+SHA1 (patch-doc_ssl_SSL__CTX__add__session.pod) = db72b7e04bb74595a78bc09379854957dcfaa4c7
+SHA1 (patch-doc_ssl_SSL__CTX__load__verify__locations.pod) = d0fd17e118a1bd19c729a0930a52925b9bb81d6d
+SHA1 (patch-doc_ssl_SSL__CTX__set__client__CA__list.pod) = 964ea426276741f89a9d02dd75baaaabc97e0943
+SHA1 (patch-doc_ssl_SSL__CTX__set__session__id__context.pod) = b5d711fcf9512c82ec2c7aa61303377006ebfca7
+SHA1 (patch-doc_ssl_SSL__CTX__set__ssl__version.pod) = 79340b3f4cfa4293362a79c336e0768711153930
+SHA1 (patch-doc_ssl_SSL__CTX__use__psk__identity__hint.pod) = e39c7f0ac0edaadf0462f78947fa40b11084cced
+SHA1 (patch-doc_ssl_SSL__accept.pod) = c5ca9e0333de10d2032d03cf3ce0d9e41b6b495f
+SHA1 (patch-doc_ssl_SSL__clear.pod) = c7d2eb126137ee642294466f0ea9019fcd5e9b92
+SHA1 (patch-doc_ssl_SSL__connect.pod) = 78a21f325f5749f0ed491ee71467a4a89848dfe3
+SHA1 (patch-doc_ssl_SSL__do__handshake.pod) = 7b8c392568ef965c1709fc3fefe572f591007b24
+SHA1 (patch-doc_ssl_SSL__read.pod) = 2a6db16242aceeee645f5b48a9725c5530fbbb8c
+SHA1 (patch-doc_ssl_SSL__session__reused.pod) = 0ed7425cf8b098c97ab223cd368c4b18f5187ae5
+SHA1 (patch-doc_ssl_SSL__set__fd.pod) = 68e3f6f3ff0fdfb2113cebb8f08e6d42c442fa2f
+SHA1 (patch-doc_ssl_SSL__set__session.pod) = e4d8442f4fc827520ca20f108050fcd6314dd41d
+SHA1 (patch-doc_ssl_SSL__shutdown.pod) = ca5b1fd9fda9405907697e848614f050978cfb90
+SHA1 (patch-doc_ssl_SSL__write.pod) = 67efd6d0de0a0db34c18c62e4a939c0ea49442ca
 SHA1 (patch-engines_ccgost_Makefile) = 08999f0f40969883482ad9ffc1aa9959ed7d402c

security/openssl/patches/patch-doc_apps_cms.pod

@@ -0,0 +1,36 @@
+$NetBSD: patch-doc_apps_cms.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/apps/cms.pod.orig	2013-02-11 15:26:04.000000000 +0000
++++ doc/apps/cms.pod
+@@ -454,24 +454,24 @@ remains DER.
+
+ 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.

security/openssl/patches/patch-doc_apps_smine.pod

@@ -0,0 +1,36 @@
+$NetBSD: patch-doc_apps_smine.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/apps/smime.pod.orig	2013-02-11 15:26:04.000000000 +0000
++++ doc/apps/smime.pod
+@@ -312,24 +312,24 @@ remains DER.
+
+ 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.

security/openssl/patches/patch-doc_crypto_X509__STORE__CTX__get__error.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_crypto_X509__STORE__CTX__get__error.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/crypto/X509_STORE_CTX_get_error.pod.orig	2013-02-11 15:26:04.000000000 +0000
++++ doc/crypto/X509_STORE_CTX_get_error.pod
+@@ -278,6 +278,8 @@ happen if extended CRL checking is enabl
+ 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

security/openssl/patches/patch-doc_ssl_SSL__COMP__add__compression__method.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__COMP__add__compression__method.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_COMP_add_compression_method.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_COMP_add_compression_method.pod
+@@ -57,7 +57,7 @@ SSL_COMP_add_compression_method() may re
+
+ The operation succeeded.
+
+-=item 1
++=item Z<>1
+
+ The operation failed. Check the error queue to find out the reason.
+

security/openssl/patches/patch-doc_ssl_SSL__CTX__add__session.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__CTX__add__session.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_CTX_add_session.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_CTX_add_session.pod
+@@ -58,7 +58,7 @@ The following values are returned by all
+  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.
+

security/openssl/patches/patch-doc_ssl_SSL__CTX__load__verify__locations.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__CTX__load__verify__locations.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_CTX_load_verify_locations.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_CTX_load_verify_locations.pod
+@@ -106,7 +106,7 @@ The operation failed because B<CAfile> a
+ 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.
+

security/openssl/patches/patch-doc_ssl_SSL__CTX__set__client__CA__list.pod

@@ -0,0 +1,20 @@
+$NetBSD: patch-doc_ssl_SSL__CTX__set__client__CA__list.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_CTX_set_client_CA_list.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_CTX_set_client_CA_list.pod
+@@ -66,11 +66,11 @@ values:
+
+ =over 4
+
+-=item 1
++=item Z<>1
+
+ The operation succeeded.
+
+-=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

security/openssl/patches/patch-doc_ssl_SSL__CTX__set__session__id__context.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__CTX__set__session__id__context.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_CTX_set_session_id_context.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_CTX_set_session_id_context.pod
+@@ -70,7 +70,7 @@ The length B<sid_ctx_len> of the session
+ 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.
+

security/openssl/patches/patch-doc_ssl_SSL__CTX__set__ssl__version.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__CTX__set__ssl__version.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_CTX_set_ssl_version.pod.orig	2013-02-11 15:26:04.000000000 +0000
++++ doc/ssl/SSL_CTX_set_ssl_version.pod
+@@ -46,7 +46,7 @@ and SSL_set_ssl_method():
+
+ The new choice failed, check the error stack to find out the reason.
+
+-=item 1
++=item Z<>1
+
+ The operation succeeded.
+

security/openssl/patches/patch-doc_ssl_SSL__CTX__use__psk__identity__hint.pod

@@ -0,0 +1,28 @@
+$NetBSD: patch-doc_ssl_SSL__CTX__use__psk__identity__hint.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_CTX_use_psk_identity_hint.pod.orig	2013-02-11 15:26:04.000000000 +0000
++++ doc/ssl/SSL_CTX_use_psk_identity_hint.pod
+@@ -81,6 +81,8 @@ SSL_CTX_use_psk_identity_hint() and SSL_
+
+ Return values from the server callback are interpreted as follows:
+
++=over 1
++
+ =item > 0
+
+ PSK identity was found and the server callback has provided the PSK
+@@ -94,9 +96,11 @@ data to B<psk> and return the length of
+ 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.
+
++=back
++
+ =cut

security/openssl/patches/patch-doc_ssl_SSL__accept.pod

@@ -0,0 +1,21 @@
+$NetBSD: patch-doc_ssl_SSL__accept.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_accept.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_accept.pod
+@@ -44,12 +44,12 @@ The following return values can occur:
+
+ =over 4
+
+-=item 1
++=item Z<>1
+
+ The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
+ established.
+
+-=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

security/openssl/patches/patch-doc_ssl_SSL__clear.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__clear.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_clear.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_clear.pod
+@@ -61,7 +61,7 @@ The following return values can occur:
+ 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.
+

security/openssl/patches/patch-doc_ssl_SSL__connect.pod

@@ -0,0 +1,28 @@
+$NetBSD: patch-doc_ssl_SSL__connect.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_connect.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_connect.pod
+@@ -41,18 +41,18 @@ The following return values can occur:
+
+ =over 4
+
+-=item 1
++=item Z<>1
+
+ The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
+ established.
+
+-=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 E<lt>0
++=item Z<>E<lt>0
+
+ The TLS/SSL handshake was not successful, because a fatal error occurred either
+ at the protocol level or a connection failure occurred. The shutdown was

security/openssl/patches/patch-doc_ssl_SSL__do__handshake.pod

@@ -0,0 +1,21 @@
+$NetBSD: patch-doc_ssl_SSL__do__handshake.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_do_handshake.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_do_handshake.pod
+@@ -45,12 +45,12 @@ The following return values can occur:
+
+ =over 4
+
+-=item 1
++=item Z<>1
+
+ The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
+ established.
+
+-=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

security/openssl/patches/patch-doc_ssl_SSL__read.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__read.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_read.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_read.pod
+@@ -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

security/openssl/patches/patch-doc_ssl_SSL__session__reused.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__session__reused.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_session_reused.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_session_reused.pod
+@@ -31,7 +31,7 @@ The following return values can occur:
+
+ A new session was negotiated.
+
+-=item 1
++=item Z<>1
+
+ A session was reused.
+

security/openssl/patches/patch-doc_ssl_SSL__set__fd.pod

@@ -0,0 +1,15 @@
+$NetBSD: patch-doc_ssl_SSL__set__fd.pod,v 1.1 2013/06/01 08:03:55 sbd Exp $
+
+Fix openssl pod docs to work with the very picky pod2man from perl-5.18.0.
+
+--- doc/ssl/SSL_set_fd.pod.orig	2013-02-11 15:02:48.000000000 +0000
++++ doc/ssl/SSL_set_fd.pod
+@@ -39,7 +39,7 @@ The following return values can occur:
+
+ The operation failed. Check the error stack to find out why.
+
+-=item 1
++=item Z<>1
+
+ The operation succeeded.
+