Update all links so they will be rendered better.

bb075f88 · Richard Levitte · 52732b38 · bb075f88 · bb075f88 · bb075f88
68 changed file
--- a/doc/apps/ca.pod
+++ b/doc/apps/ca.pod
@@ -467,6 +467,7 @@ create an empty file.
 =head1 SEE ALSO
-req(1), spkac(1), x509(1), CA.pl(1), config(5)
+L<req(1)|req(1)>, L<spkac(1)|spkac(1)>, L<x509(1)|x509(1)>, L<CA.pl(1)|CA.pl(1)>,
+L<config(5)|config(5)>
 =cut
--- a/doc/apps/ciphers.pod
+++ b/doc/apps/ciphers.pod
@@ -336,6 +336,6 @@ Include only 3DES ciphers and then place RSA ciphers last:
 =head1 SEE ALSO
-s_client(1), s_server(1), ssl(3)
+L<s_client(1)|s_client(1)>, L<s_server(1)|s_server(1)>, L<ssl(3)|ssl(3)>
 =cut
--- a/doc/apps/config.pod
+++ b/doc/apps/config.pod
@@ -133,6 +133,6 @@ file.
 =head1 SEE ALSO
-x509(1), req(1), ca(1)
+L<x509(1)|x509(1)>, L<req(1)|req(1)>, L<ca(1)|ca(1)>
 =cut
--- a/doc/apps/crl.pod
+++ b/doc/apps/crl.pod
@@ -105,6 +105,6 @@ and files too.
 =head1 SEE ALSO
-crl2pkcs7(1), ca(1), x509(1)
+L<crl2pkcs7(1)|crl2pkcs7(1)>, L<ca(1)|ca(1)>, L<x509(1)|x509(1)>
 =cut
--- a/doc/apps/crl2pkcs7.pod
+++ b/doc/apps/crl2pkcs7.pod
@@ -85,6 +85,6 @@ install user certificates and CAs in MSIE using the Xenroll control.
 =head1 SEE ALSO
-pkcs7(1)
+L<pkcs7(1)|pkcs7(1)>
 =cut
--- a/doc/apps/dhparam.pod
+++ b/doc/apps/dhparam.pod
@@ -109,6 +109,6 @@ There should be a way to generate and manipulate DH keys.
 =head1 SEE ALSO
-dsaparam(1)
+L<dsaparam(1)|dsaparam(1)>
 =cut
--- a/doc/apps/dsa.pod
+++ b/doc/apps/dsa.pod
@@ -149,6 +149,7 @@ To just output the public part of a private key:
 =head1 SEE ALSO
-dsaparam(1), gendsa(1), rsa(1), genrsa(1)
+L<dsaparam(1)|dsaparam(1)>, L<gendsa(1)|gendsa(1)>, L<rsa(1)|rsa(1)>,
+L<genrsa(1)|genrsa(1)>
 =cut
--- a/doc/apps/dsaparam.pod
+++ b/doc/apps/dsaparam.pod
@@ -95,6 +95,7 @@ DSA parameters is often used to generate several distinct keys.
 =head1 SEE ALSO
-gendsa(1), dsa(1), genrsa(1), rsa(1)
+L<gendsa(1)|gendsa(1)>, L<dsa(1)|dsa(1)>, L<genrsa(1)|genrsa(1)>,
+L<rsa(1)|rsa(1)>
 =cut
--- a/doc/apps/gendsa.pod
+++ b/doc/apps/gendsa.pod
@@ -51,6 +51,7 @@ much quicker that RSA key generation for example.
 =head1 SEE ALSO
-dsaparam(1), dsa(1), genrsa(1), rsa(1)
+L<dsaparam(1)|dsaparam(1)>, L<dsa(1)|dsa(1)>, L<genrsa(1)|genrsa(1)>,
+L<rsa(1)|rsa(1)>
 =cut
--- a/doc/apps/genrsa.pod
+++ b/doc/apps/genrsa.pod
@@ -69,4 +69,4 @@ be much larger (typically 1024 bits).
 =head1 SEE ALSO
-gendsa(1)
+L<gendsa(1)|gendsa(1)>
--- a/doc/apps/openssl.pod
+++ b/doc/apps/openssl.pod
@@ -226,11 +226,16 @@ RC5 Cipher
 =head1 SEE ALSO
-asn1parse(1), ca(1), config(1), crl(1), crl2pkcs7(1), dgst(1), dh(1),
+L<asn1parse(1)|asn1parse(1)>, L<ca(1)|ca(1)>, L<config(5)|config(5)>,
-dsa(1), dsaparam(1), enc(1), gendh(1), gendsa(1), genrsa(1), nseq(1),
+L<crl(1)|crl(1)>, L<crl2pkcs7(1)|crl2pkcs7(1)>, L<dgst(1)|dgst(1)>,
-openssl(1), pkcs12(1), pkcs7(1), pkcs8(1), req(1), rsa(1), s_client(1),
+L<dh(1)|dh(1)>, L<dsa(1)|dsa(1)>, L<dsaparam(1)|dsaparam(1)>,
-s_server(1), smime(1), spkac(1), verify(1), version(1), x509(1),
+L<enc(1)|enc(1)>, L<gendh(1)|gendh(1)>, L<gendsa(1)|gendsa(1)>,
-crypto(3), ssl(3)
+L<genrsa(1)|genrsa(1)>, L<nseq(1)|nseq(1)>, L<openssl(1)|openssl(1)>,
+L<pkcs12(1)|pkcs12(1)>, L<pkcs7(1)|pkcs7(1)>, L<pkcs8(1)|pkcs8(1)>,
+L<req(1)|req(1)>, L<rsa(1)|rsa(1)>, L<s_client(1)|s_client(1)>,
+L<s_server(1)|s_server(1)>, L<smime(1)|smime(1)>, L<spkac(1)|spkac(1)>,
+L<verify(1)|verify(1)>, L<version(1)|version(1)>, L<x509(1)|x509(1)>,
+L<crypto(3)|crypto(3)>, L<ssl(3)|ssl(3)> 
 =head1 HISTORY

--- a/doc/apps/pkcs12.pod
+++ b/doc/apps/pkcs12.pod
@@ -282,5 +282,5 @@ release.
 =head1 SEE ALSO
-pkcs8(1)
+L<pkcs8(1)|pkcs8(1)>
--- a/doc/apps/pkcs7.pod
+++ b/doc/apps/pkcs7.pod
@@ -80,6 +80,6 @@ cannot currently parse, for example, the new CMS as described in RFC2630.
 =head1 SEE ALSO
-crl2pkcs7(1)
+L<crl2pkcs7(1)|crl2pkcs7(1)>
 =cut
--- a/doc/apps/pkcs8.pod
+++ b/doc/apps/pkcs8.pod
@@ -219,6 +219,7 @@ the old format at present.
 =head1 SEE ALSO
-dsa(1), rsa(1), genrsa(1), gendsa(1)
+L<dsa(1)|dsa(1)>, L<rsa(1)|rsa(1)>, L<genrsa(1)|genrsa(1)>,
+L<gendsa(1)|gendsa(1)> 
 =cut
--- a/doc/apps/req.pod
+++ b/doc/apps/req.pod
@@ -525,6 +525,7 @@ address in subjectAltName should be input by the user.
 =head1 SEE ALSO
-x509(1), ca(1), genrsa(1), gendsa(1), config(5)
+L<x509(1)|x509(1)>, L<ca(1)|ca(1)>, L<genrsa(1)|genrsa(1)>,
+L<gendsa(1)|gendsa(1)>, L<config(5)|config(5)>
 =cut
--- a/doc/apps/rsa.pod
+++ b/doc/apps/rsa.pod
@@ -155,6 +155,7 @@ To just output the public part of a private key:
 =head1 SEE ALSO
-pkcs8(1), dsa(1), genrsa(1), gendsa(1)
+L<pkcs8(1)|pkcs8(1)>, L<dsa(1)|dsa(1)>, L<genrsa(1)|genrsa(1)>,
+L<gendsa(1)|gendsa(1)> 
 =cut
--- a/doc/apps/s_client.pod
+++ b/doc/apps/s_client.pod
@@ -208,6 +208,6 @@ information whenever a session is renegotiated.
 =head1 SEE ALSO
-sess_id(1), s_server(1), ciphers(1)
+L<sess_id(1)|sess_id(1)>, L<s_server(1)|s_server(1)>, L<ciphers(1)|ciphers(1)>
 =cut
--- a/doc/apps/s_server.pod
+++ b/doc/apps/s_server.pod
@@ -260,6 +260,6 @@ unknown cipher suites a client says it supports.
 =head1 SEE ALSO
-sess_id(1), s_client(1), ciphers(1)
+L<sess_id(1)|sess_id(1)>, L<s_client(1)|s_client(1)>, L<ciphers(1)|ciphers(1)>
 =cut
--- a/doc/apps/sess_id.pod
+++ b/doc/apps/sess_id.pod
@@ -146,6 +146,6 @@ The cipher and start time should be printed out in human readable form.
 =head1 SEE ALSO
-ciphers(1), s_server(1)
+L<ciphers(1)|ciphers(1)>, L<s_server(1)|s_server(1)>
 =cut
--- a/doc/apps/spkac.pod
+++ b/doc/apps/spkac.pod
@@ -110,6 +110,6 @@ to be used in a "replay attack".
 =head1 SEE ALSO
-ca(1)
+L<ca(1)|ca(1)>
 =cut
--- a/doc/apps/verify.pod
+++ b/doc/apps/verify.pod
@@ -268,6 +268,6 @@ an application specific error. Unused.
 =head1 SEE ALSO
-x509(1)
+L<x509(1)|x509(1)>
 =cut
--- a/doc/apps/x509.pod
+++ b/doc/apps/x509.pod
@@ -537,6 +537,7 @@ OpenSSL 0.9.5 and later.
 =head1 SEE ALSO
-req(1), ca(1), genrsa(1), gendsa(1), verify(1)
+L<req(1)|req(1)>, L<ca(1)|ca(1)>, L<genrsa(1)|genrsa(1)>,
+L<gendsa(1)|gendsa(1)>, L<verify(1)|verify(1)>
 =cut
--- a/doc/crypto/BN_CTX_new.pod
+++ b/doc/crypto/BN_CTX_new.pod
@@ -32,13 +32,13 @@ created by BN_CTX_new(), also the structure itself.
 BN_CTX_new() returns a pointer to the B<BN_CTX>. If the allocation fails,
 it returns B<NULL> and sets an error code that can be obtained by
-ERR_get_error(3).
+L<ERR_get_error(3)|ERR_get_error(3)>.
 BN_CTX_init() and BN_CTX_free() have no return values.
 =head1 SEE ALSO
-bn(3), err(3), BN_add(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<BN_add(3)|BN_add(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_add.pod
+++ b/doc/crypto/BN_add.pod
@@ -55,8 +55,8 @@ B<rem> (C<rem=a%m>).
 BN_mod_mul() multiplies B<a> by B<b> and finds the remainder when
 divided by B<m> (C<r=(a*b)%m>). B<r> may be the same B<BIGNUM> as B<a>
 or B<b>. For a more efficient algorithm, see
-L<BN_mod_mul_montgomery(3)>; for repeated computations using the same
+L<BN_mod_mul_montgomery(3)|BN_mod_mul_montgomery(3)>; for repeated
-modulus, see L<BN_mod_mul_reciprocal(3)>.
+computations using the same modulus, see L<BN_mod_mul_reciprocal(3)|BN_mod_mul_reciprocal(3)>.
 BN_exp() raises B<a> to the B<p>-th power and places the result in B<r>
 (C<r=a^p>). This function is faster than repeated applications of
@@ -70,7 +70,7 @@ places the result in B<r>. B<r> may be the same B<BIGNUM> as B<a> or
 B<b>.
 For all functions, B<ctx> is a previously allocated B<BN_CTX> used for
-temporary variables; see L<BN_CTX_new(3)>.
+temporary variables; see L<BN_CTX_new(3)|BN_CTX_new(3)>.
 Unless noted otherwise, the result B<BIGNUM> must be different from
 the arguments.
@@ -79,11 +79,12 @@ the arguments.
 For all functions, 1 is returned for success, 0 on error. The return
 value should always be checked (e.g., C<if (!BN_add(r,a,b)) goto err;>).
-The error codes can be obtained by ERR_get_error(3).
+The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-bn(3), err(3), BN_CTX_new(3), BN_add_word(3), BN_set_bit(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<BN_CTX_new(3)|BN_CTX_new(3)>,
+L<BN_add_word(3)|BN_add_word(3)>, L<BN_set_bit(3)|BN_set_bit(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_add_word.pod
+++ b/doc/crypto/BN_add_word.pod
@@ -40,13 +40,13 @@ For BN_div_word() and BN_mod_word(), B<w> must not be 0.
 =head1 RETURN VALUES
 BN_add_word(), BN_sub_word() and BN_mul_word() return 1 for success, 0
-on error. The error codes can be obtained by ERR_get_error(3).
+on error. The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 BN_mod_word() and BN_div_word() return B<a>%B<w>.
 =head1 SEE ALSO
-bn(3), err(3), BN_add(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<BN_add(3)|BN_add(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_bn2bin.pod
+++ b/doc/crypto/BN_bn2bin.pod
@@ -76,11 +76,13 @@ BN_print_fp() and BN_print() return 1 on success, 0 on write errors.
 BN_bn2mpi() returns the length of the representation. BN_mpi2bn()
 returns the B<BIGNUM>, and NULL on error.
-The error codes can be obtained by ERR_get_error(3).
+The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-bn(3), err(3), BN_zero(3), ASN1_INTEGER_to_BN(3), BN_num_bytes(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<BN_zero(3)|BN_zero(3)>,
+L<ASN1_INTEGER_to_BN(3)|ASN1_INTEGER_to_BN(3)>,
+L<BN_num_bytes(3)|BN_num_bytes(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_cmp.pod
+++ b/doc/crypto/BN_cmp.pod
@@ -37,7 +37,7 @@ the condition is true, 0 otherwise.
 =head1 SEE ALSO
-bn(3)
+L<bn(3)|bn(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_copy.pod
+++ b/doc/crypto/BN_copy.pod
@@ -21,11 +21,11 @@ containing the value B<from>.
 BN_copy() returns B<to> on success, NULL on error. BN_dup() returns
 the new B<BIGNUM>, and NULL on error. The error codes can be obtained
-by ERR_get_error(3).
+by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-bn(3), err(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_generate_prime.pod
+++ b/doc/crypto/BN_generate_prime.pod
@@ -72,11 +72,11 @@ BN_is_prime() returns 0 if the number is composite, 1 if it is
 prime with an error probability of less than 0.25^B<checks>, and
 -1 on error.
-The error codes can be obtained by ERR_get_error(3).
+The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-bn(3), err(3), rand(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_mod_inverse.pod
+++ b/doc/crypto/BN_mod_inverse.pod
@@ -22,11 +22,11 @@ variables. B<r> may be the same B<BIGNUM> as B<a> or B<n>.
 =head1 RETURN VALUES
 BN_mod_inverse() returns the B<BIGNUM> containing the inverse, and
-NULL on error. The error codes can be obtained by ERR_get_error(3).
+NULL on error. The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-bn(3), err(3), BN_add(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<BN_add(3)|BN_add(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_mod_mul_reciprocal.pod
+++ b/doc/crypto/BN_mod_mul_reciprocal.pod
@@ -22,7 +22,7 @@ reciprocal
 =head1 DESCRIPTION
 BN_mod_mul_reciprocal() can be used to perform an efficient
-BN_mod_mul(3) operation when the operation will be performed
+L<BN_mod_mul(3)|BN_mod_mul(3)> operation when the operation will be performed
 repeatedly with the same modulus. It computes B<r>=(B<a>*B<b>)%B<m>
 using B<recp>=1/B<m>, which is set as described below.  B<ctx> is a
 previously allocated B<BN_CTX> used for temporary variables.
@@ -58,11 +58,12 @@ on error.
 BN_RECP_CTX_init() and BN_RECP_CTX_free() have no return values.
 For the other functions, 1 is returned for success, 0 on error.
-The error codes can be obtained by ERR_get_error(3).
+The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-bn(3), err(3), BN_add(3), BN_CTX_new(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<BN_add(3)|BN_add(3)>,
+L<BN_CTX_new(3)|BN_CTX_new(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_new.pod
+++ b/doc/crypto/BN_new.pod
@@ -35,14 +35,14 @@ overwrites the data before the memory is returned to the system.
 BN_new() returns a pointer to the B<BIGNUM>. If the allocation fails,
 it returns B<NULL> and sets an error code that can be obtained
-by ERR_get_error(3).
+by L<ERR_get_error(3)|ERR_get_error(3)>.
 BN_init(), BN_clear(), BN_free() and BN_clear_free() have no return
 values.
 =head1 SEE ALSO
-bn(3), err(3)
+L<bn(3)|bn(3)>, L<err(3)|err(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_num_bytes.pod
+++ b/doc/crypto/BN_num_bytes.pod
@@ -27,7 +27,7 @@ The size.
 =head1 SEE ALSO
-bn(3)
+L<bn(3)|bn(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_rand.pod
+++ b/doc/crypto/BN_rand.pod
@@ -23,11 +23,12 @@ The PRNG must be seeded prior to calling BN_rand().
 =head1 RETURN VALUES
 BN_rand() returns 1 on success, 0 on error.
-The error codes can be obtained by ERR_get_error(3).
+The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-bn(3), err(3), rand(3), RAND_add(), RAND_bytes()
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>,
+L<RAND_add(3)|RAND_add(3)>, L<RAND_bytes(3)|RAND_bytes(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_set_bit.pod
+++ b/doc/crypto/BN_set_bit.pod
@@ -49,11 +49,11 @@ the result in B<r> (C<r=a/2>).
 BN_is_bit_set() returns 1 if the bit is set, 0 otherwise.
 All other functions return 1 for success, 0 on error. The error codes
-can be obtained by ERR_get_error(3).
+can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-bn(3), BN_num_bytes(3), BN_add(3)
+L<bn(3)|bn(3)>, L<BN_num_bytes(3)|BN_num_bytes(3)>, L<BN_add(3)|BN_add(3)>
 =head1 HISTORY

--- a/doc/crypto/BN_zero.pod
+++ b/doc/crypto/BN_zero.pod
@@ -41,7 +41,7 @@ Someone might change the constant.
 =head1 SEE ALSO
-bn(3), BN_bn2bin(3)
+L<bn(3)|bn(3)>, L<BN_bn2bin(3)|BN_bn2bin(3)>
 =head1 HISTORY

--- a/doc/crypto/DH_generate_key.pod
+++ b/doc/crypto/DH_generate_key.pod
@@ -36,11 +36,11 @@ DH_generate_key() returns 1 on success, 0 otherwise.
 DH_compute_key() returns the size of the shared secret on success, -1
 on error.
-The error codes can be obtained by ERR_get_error(3).
+The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-dh(3), err(3), rand(3), DH_size(3)
+L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<DH_size(3)|DH_size(3)>
 =head1 HISTORY

--- a/doc/crypto/DH_generate_parameters.pod
+++ b/doc/crypto/DH_generate_parameters.pod
@@ -25,7 +25,7 @@ B<generator> is a small number E<gt> 1, typically 2 or 5.
 A callback function may be used to provide feedback about the progress
 of the key generation. If B<callback> is not B<NULL>, it will be
-called as described in L<BN_generate_prime(3)> while a random prime
+called as described in L<BN_generate_prime(3)|BN_generate_prime(3)> while a random prime
 number is generated, and when a prime has been found, B<callback(3,
 0, cb_arg)> is called.
@@ -40,7 +40,7 @@ checked, i.e. it does not equal 2 or 5.
 DH_generate_parameters() returns a pointer to the DH structure, or
 NULL if the parameter generation fails. The error codes can be
-obtained by ERR_get_error(3).
+obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 DH_check() returns 1 if the check could be performed, 0 otherwise.
@@ -54,7 +54,7 @@ used in signature schemes.
 =head1 SEE ALSO
-dh(3), err(3), rand(3), DH_free(3)
+L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<DH_free(3)|DH_free(3)>
 =head1 HISTORY

--- a/doc/crypto/DH_new.pod
+++ b/doc/crypto/DH_new.pod
@@ -22,14 +22,16 @@ erased before the memory is returned to the system.
 =head1 RETURN VALUES
 If the allocation fails, DH_new() returns B<NULL> and sets an error
-code that can be obtained by ERR_get_error(3). Otherwise it returns
+code that can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>. Otherwise it returns
 a pointer to the newly allocated structure.
 DH_free() returns no value.
 =head1 SEE ALSO
-dh(3), err(3), DH_generate_parameters(3), DH_generate_key(3)
+L<dh(3)|dh(3)>, L<err(3)|err(3)>,
+L<DH_generate_parameters(3)|DH_generate_parameters(3)>,
+L<DH_generate_key(3)|DH_generate_key(3)>
 =head1 HISTORY

--- a/doc/crypto/DH_set_method.pod
+++ b/doc/crypto/DH_set_method.pod
@@ -84,12 +84,12 @@ DH_set_method() returns a pointer to the B<DH_METHOD> previously
 associated with B<dh>.
 DH_new_method() returns B<NULL> and sets an error code that can be
-obtained by ERR_get_error(3) if the allocation fails. Otherwise it
+obtained by L<ERR_get_error(3)|ERR_get_error(3)> if the allocation fails. Otherwise it
 returns a pointer to the newly allocated structure.
 =head1 SEE ALSO
-dh(3), DH_new(3)
+L<dh(3)|dh(3)>, L<DH_new(3)|DH_new(3)>
 =head1 HISTORY

--- a/doc/crypto/DH_size.pod
+++ b/doc/crypto/DH_size.pod
@@ -24,7 +24,7 @@ The size in bytes.
 =head1 SEE ALSO
-dh(3), DH_generate_key(3)
+L<dh(3)|dh(3)>, L<DH_generate_key(3)|DH_generate_key(3)>
 =head1 HISTORY

--- a/doc/crypto/RAND_add.pod
+++ b/doc/crypto/RAND_add.pod
@@ -33,7 +33,7 @@ OpenSSL makes sure that the PRNG state is unique for each thread. On
 systems that provide C</dev/urandom>, the randomness device is used
 to seed the PRNG transparently. However, on all other systems, the
 application is responsible for seeding the PRNG by calling RAND_add()
-or RAND_load_file(3).
+or L<RAND_load_file(3)|RAND_load_file(3)>.
 RAND_seed() is equivalent to RAND_add() when B<num == entropy>.
@@ -50,7 +50,7 @@ These functions do not return values.
 =head1 SEE ALSO
-rand(3), RAND_load_file(3), RAND_cleanup(3)
+L<rand(3)|rand(3)>, L<RAND_load_file(3)|RAND_load_file(3)>, L<RAND_cleanup(3)|RAND_cleanup(3)>
 =head1 HISTORY

--- a/doc/crypto/RAND_bytes.pod
+++ b/doc/crypto/RAND_bytes.pod
@@ -28,14 +28,14 @@ generation etc.
 =head1 RETURN VALUES
 RAND_bytes() returns 1 on success, 0 otherwise. The error code can be
-obtained by ERR_get_error(3). RAND_pseudo_bytes() returns 1 if the
+obtained by L<ERR_get_error(3)|ERR_get_error(3)>. RAND_pseudo_bytes() returns 1 if the
 bytes generated are cryptographically strong, 0 otherwise. Both
 functions return -1 if they are not supported by the current RAND
 method.
 =head1 SEE ALSO
-rand(3), err(3), RAND_add(3)
+L<rand(3)|rand(3)>, L<err(3)|err(3)>, L<RAND_add(3)|RAND_add(3)>
 =head1 HISTORY

--- a/doc/crypto/RAND_cleanup.pod
+++ b/doc/crypto/RAND_cleanup.pod
@@ -20,7 +20,7 @@ RAND_cleanup() returns no value.
 =head1 SEE ALSO
-rand(3)
+L<rand(3)|rand(3)>
 =head1 HISTORY

--- a/doc/crypto/RAND_load_file.pod
+++ b/doc/crypto/RAND_load_file.pod
@@ -43,7 +43,7 @@ error.
 =head1 SEE ALSO
-rand(3), RAND_add(3), RAND_cleanup(3)
+L<rand(3)|rand(3)>, L<RAND_add(3)|RAND_add(3)>, L<RAND_cleanup(3)|RAND_cleanup(3)>
 =head1 HISTORY

--- a/doc/crypto/RAND_set_rand_method.pod
+++ b/doc/crypto/RAND_set_rand_method.pod
@@ -47,7 +47,7 @@ RAND_SSLeay() return pointers to the respective methods.
 =head1 SEE ALSO
-rand(3)
+L<rand(3)|rand(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_blinding_on.pod
+++ b/doc/crypto/RSA_blinding_on.pod
@@ -34,7 +34,7 @@ RSA_blinding_off() returns no value.
 =head1 SEE ALSO
-rsa(3), rand(3)
+L<rsa(3)|rsa(3)>, L<rand(3)|rand(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_check_key.pod
+++ b/doc/crypto/RSA_check_key.pod
@@ -26,11 +26,11 @@ RSA_check_key() returns 1 if B<rsa> is a valid RSA key, and 0 otherwise.
 -1 is returned if an error occurs while checking the key.
 If the key is invalid or an error occurred, the reason code can be
-obtained using ERR_get_error(3).
+obtained using L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-rsa(3), err(3)
+L<rsa(3)|rsa(3)>, L<err(3)|err(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_generate_key.pod
+++ b/doc/crypto/RSA_generate_key.pod
@@ -30,7 +30,7 @@ will be called as follows:
 =item *
 While a random prime number is generated, it is called as
-described in L<BN_generate_prime(3)>.
+described in L<BN_generate_prime(3)|BN_generate_prime(3)>.
 =item *
@@ -49,7 +49,7 @@ The process is then repeated for prime q with B<callback(3, 1, cb_arg)>.
 =head1 RETURN VALUE
 If key generation fails, RSA_generate_key() returns B<NULL>; the
-error codes can be obtained by ERR_get_error(3).
+error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 BUGS
@@ -59,7 +59,7 @@ RSA_generate_key() goes into an infinite loop for illegal input values.
 =head1 SEE ALSO
-err(3), rand(3), rsa(3), RSA_free(3)
+L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<rsa(3)|rsa(3)>, L<RSA_free(3)|RSA_free(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_get_ex_new_index.pod
+++ b/doc/crypto/RSA_get_ex_new_index.pod
@@ -100,7 +100,7 @@ parameter.
 B<new_func()> and B<dup_func()> should return 0 for failure and 1 for success.
-On failure an error code can be obtained from B<ERR_get_error(3)>.
+On failure an error code can be obtained from L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 BUGS

--- a/doc/crypto/RSA_new.pod
+++ b/doc/crypto/RSA_new.pod
@@ -22,14 +22,14 @@ erased before the memory is returned to the system.
 =head1 RETURN VALUES
 If the allocation fails, RSA_new() returns B<NULL> and sets an error
-code that can be obtained by ERR_get_error(3). Otherwise it returns
+code that can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>. Otherwise it returns
 a pointer to the newly allocated structure.
 RSA_free() returns no value.
 =head1 SEE ALSO
-err(3), rsa(3), RSA_generate_key(3)
+L<err(3)|err(3)>, L<rsa(3)|rsa(3)>, L<RSA_generate_key(3)|RSA_generate_key(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_padding_add_PKCS1_type_1.pod
+++ b/doc/crypto/RSA_padding_add_PKCS1_type_1.pod
@@ -101,11 +101,13 @@ of length B<pl>. B<p> may be B<NULL> if B<pl> is 0.
 The RSA_padding_add_xxx() functions return 1 on success, 0 on error.
 The RSA_padding_check_xxx() functions return the length of the
 recovered data, -1 on error. Error codes can be obtained by calling
-ERR_get_error(3).
+L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-RSA_public_encrypt(3), RSA_private_decrypt(3), RSA_sign(3), RSA_verify(3)
+L<RSA_public_encrypt(3)|RSA_public_encrypt(3)>,
+L<RSA_private_decrypt(3)|RSA_private_decrypt(3)>,
+L<RSA_sign(3)|RSA_sign(3)>, L<RSA_verify(3)|RSA_verify(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_print.pod
+++ b/doc/crypto/RSA_print.pod
@@ -35,7 +35,7 @@ These functions return 1 on success, 0 on error.
 =head1 SEE ALSO
-dh(3), dsa(3), rsa(3), BN_bn2bin(3)
+L<dh(3)|dh(3)>, L<dsa(3)|dsa(3)>, L<rsa(3)|rsa(3)>, L<BN_bn2bin(3)|BN_bn2bin(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_private_encrypt.pod
+++ b/doc/crypto/RSA_private_encrypt.pod
@@ -31,7 +31,7 @@ B<padding> denotes one of the following modes:
 PKCS #1 v1.5 padding. This function does not handle the
 B<algorithmIdentifier> specified in PKCS #1. When generating or
-verifying PKCS #1 signatures, RSA_sign(3) and RSA_verify(3) should be
+verifying PKCS #1 signatures, L<RSA_sign(3)|RSA_sign(3)> and L<RSA_verify(3)|RSA_verify(3)> should be
 used.
 =item RSA_NO_PADDING
@@ -55,11 +55,11 @@ RSA_size(rsa)). RSA_public_decrypt() returns the size of the
 recovered message digest.
 On error, -1 is returned; the error codes can be
-obtained by ERR_get_error(3).
+obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 SEE ALSO
-err(3), rsa(3), RSA_sign(3), RSA_verify(3)
+L<err(3)|err(3)>, L<rsa(3)|rsa(3)>, L<RSA_sign(3)|RSA_sign(3)>, L<RSA_verify(3)|RSA_verify(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_public_encrypt.pod
+++ b/doc/crypto/RSA_public_encrypt.pod
@@ -64,7 +64,7 @@ RSA_size(rsa)). RSA_private_decrypt() returns the size of the
 recovered plaintext.
 On error, -1 is returned; the error codes can be
-obtained by ERR_get_error(3).
+obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 CONFORMING TO
@@ -72,11 +72,11 @@ SSL, PKCS #1 v2.0
 =head1 SEE ALSO
-err(3), rand(3), rsa(3), RSA_size(3)
+L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<rsa(3)|rsa(3)>, L<RSA_size(3)|RSA_size(3)>
 =head1 NOTES
-The RSA_PKCS1_RSAref(3) method supports only the RSA_PKCS1_PADDING mode.
+The L<RSA_PKCS1_RSAref(3)|RSA_PKCS1_RSAref(3)> method supports only the RSA_PKCS1_PADDING mode.
 =head1 HISTORY

--- a/doc/crypto/RSA_set_method.pod
+++ b/doc/crypto/RSA_set_method.pod
@@ -136,12 +136,12 @@ RSA_set_method() returns a pointer to the B<RSA_METHOD> previously
 associated with B<rsa>.
 RSA_new_method() returns B<NULL> and sets an error code that can be
-obtained by ERR_get_error(3) if the allocation fails. Otherwise it
+obtained by L<ERR_get_error(3)|ERR_get_error(3)> if the allocation fails. Otherwise it
 returns a pointer to the newly allocated structure.
 =head1 SEE ALSO
-rsa(3), RSA_new(3)
+L<rsa(3)|rsa(3)>, L<RSA_new(3)|RSA_new(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_sign.pod
+++ b/doc/crypto/RSA_sign.pod
@@ -23,7 +23,7 @@ must point to B<RSA_size(rsa)> bytes of memory.
 B<type> denotes the message digest algorithm that was used to generate
 B<m>. It usually is one of B<NID_sha1>, B<NID_ripemd160> and
-B<NID_md5>; see L<objects> for details. If B<type> is B<NID_md5_sha1>,
+B<NID_md5>; see L<objects(3)> for details. If B<type> is B<NID_md5_sha1>,
 an SSL signature (MD5 and SHA1 message digests with PKCS #1 padding
 and no algorithm identifier) is created.
@@ -37,7 +37,7 @@ B<rsa> is the signer's public key.
 RSA_sign() returns 1 on success, 0 otherwise.  RSA_verify() returns 1
 on successful verification, 0 otherwise.
-The error codes can be obtained by ERR_get_error(3).
+The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 BUGS
@@ -50,8 +50,9 @@ SSL, PKCS #1 v2.0
 =head1 SEE ALSO
-err(3), objects(3), rsa(3), RSA_private_encrypt(3),
+L<err(3)|err(3)>, L<objects(3)|objects(3)>, L<rsa(3)|rsa(3)>,
-RSA_public_decrypt(3)
+L<RSA_private_encrypt(3)|RSA_private_encrypt(3)>,
+L<RSA_public_decrypt(3)|RSA_public_decrypt(3)> 
 =head1 HISTORY

--- a/doc/crypto/RSA_sign_ASN1_OCTET_STRING.pod
+++ b/doc/crypto/RSA_sign_ASN1_OCTET_STRING.pod
@@ -39,7 +39,7 @@ RSA_sign_ASN1_OCTET_STRING() returns 1 on success, 0 otherwise.
 RSA_verify_ASN1_OCTET_STRING() returns 1 on successful verification, 0
 otherwise.
-The error codes can be obtained by ERR_get_error(3).
+The error codes can be obtained by L<ERR_get_error(3)|ERR_get_error(3)>.
 =head1 BUGS
@@ -47,7 +47,9 @@ These functions serve no recognizable purpose.
 =head1 SEE ALSO
-err(3), objects(3), rand(3), rsa(3), RSA_sign(3), RSA_verify(3)
+L<err(3)|err(3)>, L<objects(3)|objects(3)>, L<rand(3)|rand(3)>,
+L<rsa(3)|rsa(3)>, L<RSA_sign(3)|RSA_sign(3)>,
+L<RSA_verify(3)|RSA_verify(3)>
 =head1 HISTORY

--- a/doc/crypto/RSA_size.pod
+++ b/doc/crypto/RSA_size.pod
@@ -24,7 +24,7 @@ The size in bytes.
 =head1 SEE ALSO
-rsa(3)
+L<rsa(3)|rsa(3)>
 =head1 HISTORY

--- a/doc/crypto/bn.pod
+++ b/doc/crypto/bn.pod
@@ -123,13 +123,13 @@ The basic object in this library is a B<BIGNUM>. It is used to hold a
 single large integer. This type should be considered opaque and fields
 should not be modified or accessed directly.
-The creation of B<BIGNUM> objects is described in L<BN_new(3)>;
+The creation of B<BIGNUM> objects is described in L<BN_new(3)|BN_new(3)>;
-L<BN_add(3)> describes most of the arithmetic operations.
+L<BN_add(3)|BN_add(3)> describes most of the arithmetic operations.
-Comparision is described in L<BN_cmp(3)>; L<BN_zero(3)> describes
+Comparision is described in L<BN_cmp(3)|BN_cmp(3)>; L<BN_zero(3)|BN_zero(3)>
-certain assignments, L<BN_rand(3)> the generation of random numbers,
+describes certain assignments, L<BN_rand(3)|BN_rand(3)> the generation of
-L<BN_generate_prime(3)> deals with prime numbers and L<BN_set_bit(3)>
+random numbers, L<BN_generate_prime(3)|BN_generate_prime(3)> deals with prime
-with bit operations. The conversion of B<BIGNUM>s to external
+numbers and L<BN_set_bit(3)|BN_set_bit(3)> with bit operations. The conversion
-formats is described in L<BN_bn2bin(3)>.
+of B<BIGNUM>s to external formats is described in L<BN_bn2bin(3)|BN_bn2bin(3)>.
 =head1 INTERNALS
@@ -167,9 +167,14 @@ temporary B<BIGNUM>s any publicly exported function will use.
 =head1 SEE ALSO
-dh(3), err(3), rand(3), rsa(3), BN_new(3), BN_CTX_new(3), BN_copy(3),
+L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<rsa(3)|rsa(3)>,
-BN_num_bytes(3), BN_add(3), BN_add_word(3), BN_cmp(3), BN_zero(3),
+L<BN_new(3)|BN_new(3)>, L<BN_CTX_new(3)|BN_CTX_new(3)>,
-BN_rand(3), BN_generate_prime(3), BN_set_bit(3), BN_bn2bin(3),
+L<BN_copy(3)|BN_copy(3)>, L<BN_num_bytes(3)|BN_num_bytes(3)>,
-BN_mod_inverse(3), BN_mod_mul_reciprocal(3), BN_mod_mul_montgomery(3)
+L<BN_add(3)|BN_add(3)>, L<BN_add_word(3)|BN_add_word(3)>,
+L<BN_cmp(3)|BN_cmp(3)>, L<BN_zero(3)|BN_zero(3)>, L<BN_rand(3)|BN_rand(3)>,
+L<BN_generate_prime(3)|BN_generate_prime(3)>, L<BN_set_bit(3)|BN_set_bit(3)>,
+L<BN_bn2bin(3)|BN_bn2bin(3)>, L<BN_mod_inverse(3)|BN_mod_inverse(3)>,
+L<BN_mod_mul_reciprocal(3)|BN_mod_mul_reciprocal(3)>,
+L<BN_mod_mul_montgomery(3)|BN_mod_mul_montgomery(3)> 
 =cut
--- a/doc/crypto/crypto.pod
+++ b/doc/crypto/crypto.pod
@@ -27,36 +27,41 @@ hash functions and a cryptographic pseudo-random number generator.
 =item SYMMETRIC CIPHERS
-blowfish(3), cast(3), des(3), idea(3), rc2(3), rc4(3), rc5(3)
+L<blowfish(3)|blowfish(3)>, L<cast(3)|cast(3)>, L<des(3)|des(3)>,
+L<idea(3)|idea(3)>, L<rc2(3)|rc2(3)>, L<rc4(3)|rc4(3)>, L<rc5(3)|rc5(3)> 
 =item PUBLIC KEY CRYPTOGRAPHY AND KEY AGREEMENT
-dsa(3), dh(3), rsa(3)
+L<dsa(3)|dsa(3)>, L<dh(3)|dh(3)>, L<rsa(3)|rsa(3)>
 =item CERTIFICATES
-x509(3), x509v3(3)
+L<x509(3)|x509(3)>, L<x509v3(3)|x509v3(3)>
 =item AUTHENTICATION CODES, HASH FUNCTIONS
-hmac(3), md2(3), md5(3), mdc2(3), ripemd(3), sha(3)
+L<hmac(3)|hmac(3)>, L<md2(3)|md2(3)>, L<md5(3)|md5(3)>, L<mdc2(3)|mdc2(3)>,
+L<ripemd(3)|ripemd(3)>, L<sha(3)|sha(3)> 
 =item AUXILIARY FUNCTIONS
-err(3), rand(3)
+L<err(3)|err(3)>, L<rand(3)|rand(3)>
 =item INPUT/OUTPUT, DATA ENCODING
-asn1(3), bio(3), evp(3), pem(3), pkcs7(3), pkcs12(3)
+L<asn1(3)|asn1(3)>, L<bio(3)|bio(3)>, L<evp(3)|evp(3)>, L<pem(3)|pem(3)>,
+L<pkcs7(3)|pkcs7(3)>, L<pkcs12(3)|pkcs12(3)> 
 =item INTERNAL FUNCTIONS
-bn(3), buffer(3), lhash(3), objects(3), stack(3), threads(3), txt_db(3)
+L<bn(3)|bn(3)>, L<buffer(3)|buffer(3)>, L<lhash(3)|lhash(3)>,
+L<objects(3)|objects(3)>, L<stack(3)|stack(3)>, L<threads(3)|threads(3)>,
+L<txt_db(3)|txt_db(3)> 
 =back
 =head1 SEE ALSO
-openssl(1), ssl(3)
+L<openssl(1)|openssl(1)>, L<ssl(3)|ssl(3)>
 =cut
--- a/doc/crypto/d2i_DHparams.pod
+++ b/doc/crypto/d2i_DHparams.pod
@@ -6,7 +6,7 @@ d2i_DHparams, i2d_DHparams - ...
 =head1 SYNOPSIS
-#include <openssl/dh.h>
+ #include <openssl/dh.h>
 DH *d2i_DHparams(DH **a, unsigned char **pp, long length);
 int i2d_DHparams(DH *a, unsigned char **pp);

--- a/doc/crypto/d2i_RSAPublicKey.pod
+++ b/doc/crypto/d2i_RSAPublicKey.pod
@@ -6,7 +6,7 @@ d2i_RSAPublicKey, i2d_RSAPublicKey, d2i_RSAPrivateKey, i2d_RSAPrivateKey, i2d_Ne
 =head1 SYNOPSIS
-#include <openssl/rsa.h>
+ #include <openssl/rsa.h>
 RSA * d2i_RSAPublicKey(RSA **a, unsigned char **pp, long length);

--- a/doc/crypto/dh.pod
+++ b/doc/crypto/dh.pod
@@ -41,7 +41,7 @@ dh - Diffie-Hellman key agreement
 These functions implement the Diffie-Hellman key agreement protocol.
 The generation of shared DH parameters is described in
-L<DH_generate_parameters(3)>; L<DH_generate_key(3)> describes how
+L<DH_generate_parameters(3)|DH_generate_parameters(3)>; L<DH_generate_key(3)|DH_generate_key(3)> describes how
 to perform a key agreement.
 The B<DH> structure consists of several BIGNUM components.
@@ -58,8 +58,11 @@ The B<DH> structure consists of several BIGNUM components.
 =head1 SEE ALSO
-dhparam(1), bn(3), dsa(3), err(3), rand(3), rsa(3), DH_set_method(3),
+L<dhparam(1)|dhparam(1)>, L<bn(3)|bn(3)>, L<dsa(3)|dsa(3)>, L<err(3)|err(3)>,
-DH_new(3), DH_get_ex_new_index(3), DH_generate_parameters(3),
+L<rand(3)|rand(3)>, L<rsa(3)|rsa(3)>, L<DH_set_method(3)|DH_set_method(3)>,
-DH_compute_key(3), d2i_DHparams(3), RSA_print(3)
+L<DH_new(3)|DH_new(3)>, L<DH_get_ex_new_index(3)|DH_get_ex_new_index(3)>,
+L<DH_generate_parameters(3)|DH_generate_parameters(3)>,
+L<DH_compute_key(3)|DH_compute_key(3)>, L<d2i_DHparams(3)|d2i_DHparams(3)>,
+L<RSA_print(3)|RSA_print(3)> 
 =cut
--- a/doc/crypto/rand.pod
+++ b/doc/crypto/rand.pod
@@ -34,11 +34,12 @@ need randomness.
 A cryptographic PRNG must be seeded with unpredictable data such as
 mouse movements or keys pressed at random by the user. This is
-described in L<RAND_add(3)>. Its state can be saved in a seed file
+described in L<RAND_add(3)|RAND_add(3)>. Its state can be saved in a seed file
-(see L<RAND_load_file(3)>) to avoid having to go through the seeding
+(see L<RAND_load_file(3)|RAND_load_file(3)>) to avoid having to go through the
-process whenever the application is started.
+seeding process whenever the application is started.
-L<RAND_bytes(3)> describes how to obtain random data from the PRNG.
+L<RAND_bytes(3)|RAND_bytes(3)> describes how to obtain random data from the
+PRNG. 
 =head1 INTERNALS
@@ -141,11 +142,13 @@ overwritten) and 7 (by not using the 10 bytes given to the caller to
 update the 'state', but they are used to update 'md').
 So of the points raised, only 2 is not addressed (but see
-L<RAND_add(3)>).
+L<RAND_add(3)|RAND_add(3)>).
 =head1 SEE ALSO
-BN_rand(3), RAND_add(3), RAND_load_file(3), RAND_bytes(3),
+L<BN_rand(3)|BN_rand(3)>, L<RAND_add(3)|RAND_add(3)>,
-RAND_set_rand_method(3), RAND_cleanup(3)
+L<RAND_load_file(3)|RAND_load_file(3)>, L<RAND_bytes(3)|RAND_bytes(3)>,
+L<RAND_set_rand_method(3)|RAND_set_rand_method(3)>,
+L<RAND_cleanup(3)|RAND_cleanup(3)> 
 =cut
--- a/doc/crypto/rsa.pod
+++ b/doc/crypto/rsa.pod
@@ -116,10 +116,17 @@ RSA is covered by a US patent which expires in September 2000.
 =head1 SEE ALSO
-rsa(1), bn(3), dsa(3), dh(3), rand(3), RSA_new(3),
+L<rsa(1)|rsa(1)>, L<bn(3)|bn(3)>, L<dsa(3)|dsa(3)>, L<dh(3)|dh(3)>,
-RSA_public_encrypt(3), RSA_sign(3), RSA_size(3), RSA_generate_key(3),
+L<rand(3)|rand(3)>, L<RSA_new(3)|RSA_new(3)>,
-RSA_check_key(3), RSA_blinding_on(3), RSA_set_method(3), RSA_print(3),
+L<RSA_public_encrypt(3)|RSA_public_encrypt(3)>,
-RSA_get_ex_new_index(3), RSA_private_encrypt(3),
+L<RSA_sign(3)|RSA_sign(3)>, L<RSA_size(3)|RSA_size(3)>,
-RSA_sign_ASN_OCTET_STRING(3), RSA_padding_add_PKCS1_type_1(3)
+L<RSA_generate_key(3)|RSA_generate_key(3)>,
+L<RSA_check_key(3)|RSA_check_key(3)>,
+L<RSA_blinding_on(3)|RSA_blinding_on(3)>,
+L<RSA_set_method(3)|RSA_set_method(3)>, L<RSA_print(3)|RSA_print(3)>,
+L<RSA_get_ex_new_index(3)|RSA_get_ex_new_index(3)>,
+L<RSA_private_encrypt(3)|RSA_private_encrypt(3)>,
+L<RSA_sign_ASN_OCTET_STRING(3)|RSA_sign_ASN_OCTET_STRING(3)>,
+L<RSA_padding_add_PKCS1_type_1(3)|RSA_padding_add_PKCS1_type_1(3)> 
 =cut
--- a/doc/ssl/SSL_get_error.pod
+++ b/doc/ssl/SSL_get_error.pod
@@ -82,7 +82,7 @@ OpenSSL error queue contains more information on the error.
 =head1 SEE ALSO
-ssl(3), err(3)
+L<ssl(3)|ssl(3)>, L<err(3)|err(3)>
 =head1 HISTORY

--- a/doc/ssl/ssl.pod
+++ b/doc/ssl/ssl.pod
@@ -623,11 +623,11 @@ connection defined in the B<SSL> structure.
 =head1 SEE ALSO
-openssl(1), crypto(3)
+L<openssl(1)|openssl(1)>, L<crypto(3)|crypto(3)>
 =head1 HISTORY
-The ssl(3) document appeared in OpenSSL 0.9.2
+The L<ssl(3)|ssl(3)> document appeared in OpenSSL 0.9.2
 =cut