The man patch I was talking about.
diff -urN openssl-0.9.5-orig/Makefile.org openssl-0.9.5/Makefile.org
--- openssl-0.9.5-orig/Makefile.org Fri Feb 25 16:34:55 2000
+++ openssl-0.9.5/Makefile.org Sat Mar 11 20:36:58 2000
@@ -370,10 +370,11 @@
@for i in doc/apps/*.pod; do \
(cd `dirname $$i`; \
fn=`basename $$i .pod`; \
- sec=`[ "$$fn" = "config" ] && echo 5 || echo 1`; \
+ sec=`case $$fn in openssl|CA.pl) echo 1;; config) echo 5s;; *) echo
+1s;; esac`; \
+ sec1st=`echo $$sec | cut -c1`; \
$(PERL) ../../util/pod2man.pl --section=$$sec --center=OpenSSL \
--release=$(VERSION) `basename $$i` \
- > $(INSTALL_PREFIX)$(MANDIR)/man$$sec/`basename $$i
.pod`.$$sec); \
+ > $(INSTALL_PREFIX)$(MANDIR)/man$$sec1st/`basename $$i
+.pod`.$$sec); \
done
@echo installing man 3 and man 7
@for i in doc/crypto/*.pod doc/ssl/*.pod; do \
diff -urN openssl-0.9.5-orig/doc/apps/CA.pl.pod openssl-0.9.5/doc/apps/CA.pl.pod
--- openssl-0.9.5-orig/doc/apps/CA.pl.pod Fri Feb 4 01:23:16 2000
+++ openssl-0.9.5/doc/apps/CA.pl.pod Sat Mar 11 20:36:58 2000
@@ -132,7 +132,7 @@
=head1 SEE ALSO
-L<x509(1)|x509(1)>, L<ca(1)|ca(1)>, L<req(1)|req(1)>, L<pkcs12(1)|pkcs12(1)>,
-L<config(5)|config(5)>
+L<x509(1s)|x509(1s)>, L<ca(1s)|ca(1s)>, L<req(1s)|req(1s)>,
+L<pkcs12(1s)|pkcs12(1s)>, L<config(5s)|config(5s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/ca.pod openssl-0.9.5/doc/apps/ca.pod
--- openssl-0.9.5-orig/doc/apps/ca.pod Thu Feb 24 19:18:48 2000
+++ openssl-0.9.5/doc/apps/ca.pod Sat Mar 11 20:36:58 2000
@@ -473,7 +473,7 @@
=head1 SEE ALSO
-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)>
+L<req(1s)|req(1s)>, L<spkac(1s)|spkac(1s)>, L<x509(1s)|x509(1s)>,
+L<CA.pl(1)|CA.pl(1)>, L<config(5s)|config(5s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/ciphers.pod openssl-0.9.5/doc/apps/ciphers.pod
--- openssl-0.9.5-orig/doc/apps/ciphers.pod Wed Feb 23 03:10:58 2000
+++ openssl-0.9.5/doc/apps/ciphers.pod Sat Mar 11 20:36:58 2000
@@ -337,6 +337,6 @@
=head1 SEE ALSO
-L<s_client(1)|s_client(1)>, L<s_server(1)|s_server(1)>, L<ssl(3)|ssl(3)>
+L<s_client(1s)|s_client(1s)>, L<s_server(1s)|s_server(1s)>, L<ssl(3)|ssl(3)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/config.pod openssl-0.9.5/doc/apps/config.pod
--- openssl-0.9.5-orig/doc/apps/config.pod Fri Feb 4 01:23:16 2000
+++ openssl-0.9.5/doc/apps/config.pod Sat Mar 11 20:36:58 2000
@@ -133,6 +133,6 @@
=head1 SEE ALSO
-L<x509(1)|x509(1)>, L<req(1)|req(1)>, L<ca(1)|ca(1)>
+L<x509(1s)|x509(1s)>, L<req(1s)|req(1s)>, L<ca(1s)|ca(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/crl.pod openssl-0.9.5/doc/apps/crl.pod
--- openssl-0.9.5-orig/doc/apps/crl.pod Tue Feb 8 15:37:07 2000
+++ openssl-0.9.5/doc/apps/crl.pod Sat Mar 11 20:36:58 2000
@@ -112,6 +112,6 @@
=head1 SEE ALSO
-L<crl2pkcs7(1)|crl2pkcs7(1)>, L<ca(1)|ca(1)>, L<x509(1)|x509(1)>
+L<crl2pkcs7(1s)|crl2pkcs7(1s)>, L<ca(1s)|ca(1s)>, L<x509(1s)|x509(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/crl2pkcs7.pod
openssl-0.9.5/doc/apps/crl2pkcs7.pod
--- openssl-0.9.5-orig/doc/apps/crl2pkcs7.pod Thu Jan 27 03:24:52 2000
+++ openssl-0.9.5/doc/apps/crl2pkcs7.pod Sat Mar 11 20:36:58 2000
@@ -85,6 +85,6 @@
=head1 SEE ALSO
-L<pkcs7(1)|pkcs7(1)>
+L<pkcs7(1s)|pkcs7(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/dgst.pod openssl-0.9.5/doc/apps/dgst.pod
--- openssl-0.9.5-orig/doc/apps/dgst.pod Fri Jan 21 04:16:19 2000
+++ openssl-0.9.5/doc/apps/dgst.pod Sat Mar 11 20:36:58 2000
@@ -6,7 +6,7 @@
=head1 SYNOPSIS
-[B<dgst>]
+B<openssl> B<dgst>
[B<-md5|-md2|-sha1|-sha|mdc2|-ripemd160>]
[B<-c>]
[B<-d>]
diff -urN openssl-0.9.5-orig/doc/apps/dhparam.pod openssl-0.9.5/doc/apps/dhparam.pod
--- openssl-0.9.5-orig/doc/apps/dhparam.pod Thu Feb 24 19:18:49 2000
+++ openssl-0.9.5/doc/apps/dhparam.pod Sat Mar 11 20:36:58 2000
@@ -110,6 +110,6 @@
=head1 SEE ALSO
-L<dsaparam(1)|dsaparam(1)>
+L<dsaparam(1s)|dsaparam(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/dsa.pod openssl-0.9.5/doc/apps/dsa.pod
--- openssl-0.9.5-orig/doc/apps/dsa.pod Thu Feb 17 01:16:00 2000
+++ openssl-0.9.5/doc/apps/dsa.pod Sat Mar 11 20:36:58 2000
@@ -144,7 +144,7 @@
=head1 SEE ALSO
-L<dsaparam(1)|dsaparam(1)>, L<gendsa(1)|gendsa(1)>, L<rsa(1)|rsa(1)>,
-L<genrsa(1)|genrsa(1)>
+L<dsaparam(1s)|dsaparam(1s)>, L<gendsa(1s)|gendsa(1s)>, L<rsa(1s)|rsa(1s)>,
+L<genrsa(1s)|genrsa(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/dsaparam.pod openssl-0.9.5/doc/apps/dsaparam.pod
--- openssl-0.9.5-orig/doc/apps/dsaparam.pod Thu Feb 24 19:18:49 2000
+++ openssl-0.9.5/doc/apps/dsaparam.pod Sat Mar 11 20:36:58 2000
@@ -96,7 +96,7 @@
=head1 SEE ALSO
-L<gendsa(1)|gendsa(1)>, L<dsa(1)|dsa(1)>, L<genrsa(1)|genrsa(1)>,
-L<rsa(1)|rsa(1)>
+L<gendsa(1s)|gendsa(1s)>, L<dsa(1s)|dsa(1s)>, L<genrsa(1s)|genrsa(1s)>,
+L<rsa(1s)|rsa(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/gendsa.pod openssl-0.9.5/doc/apps/gendsa.pod
--- openssl-0.9.5-orig/doc/apps/gendsa.pod Thu Feb 24 19:18:49 2000
+++ openssl-0.9.5/doc/apps/gendsa.pod Sat Mar 11 20:36:58 2000
@@ -52,7 +52,7 @@
=head1 SEE ALSO
-L<dsaparam(1)|dsaparam(1)>, L<dsa(1)|dsa(1)>, L<genrsa(1)|genrsa(1)>,
-L<rsa(1)|rsa(1)>
+L<dsaparam(1s)|dsaparam(1s)>, L<dsa(1s)|dsa(1s)>, L<genrsa(1s)|genrsa(1s)>,
+L<rsa(1s)|rsa(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/genrsa.pod openssl-0.9.5/doc/apps/genrsa.pod
--- openssl-0.9.5-orig/doc/apps/genrsa.pod Thu Feb 24 19:18:50 2000
+++ openssl-0.9.5/doc/apps/genrsa.pod Sat Mar 11 20:36:58 2000
@@ -82,4 +82,6 @@
=head1 SEE ALSO
-L<gendsa(1)|gendsa(1)>
+L<gendsa(1s)|gendsa(1s)>
+
+=cut
diff -urN openssl-0.9.5-orig/doc/apps/openssl.pod openssl-0.9.5/doc/apps/openssl.pod
--- openssl-0.9.5-orig/doc/apps/openssl.pod Wed Feb 23 19:09:49 2000
+++ openssl-0.9.5/doc/apps/openssl.pod Sat Mar 11 20:36:58 2000
@@ -278,17 +278,17 @@
=head1 SEE ALSO
-L<asn1parse(1)|asn1parse(1)>, L<ca(1)|ca(1)>, L<config(5)|config(5)>,
-L<crl(1)|crl(1)>, L<crl2pkcs7(1)|crl2pkcs7(1)>, L<dgst(1)|dgst(1)>,
-L<dhparam(1)|dhparam(1)>, L<dsa(1)|dsa(1)>, L<dsaparam(1)|dsaparam(1)>,
-L<enc(1)|enc(1)>, L<gendsa(1)|gendsa(1)>,
-L<genrsa(1)|genrsa(1)>, L<nseq(1)|nseq(1)>, L<openssl(1)|openssl(1)>,
-L<passwd(1)|passwd(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)>
+L<asn1parse(1s)|asn1parse(1s)>, L<ca(1s)|ca(1s)>, L<crl(1s)|crl(1s)>,
+L<crl2pkcs7(1s)|crl2pkcs7(1s)>, L<dgst(1s)|dgst(1s)>,
+L<dhparam(1s)|dhparam(1s)>, L<dsa(1s)|dsa(1s)>, L<dsaparam(1s)|dsaparam(1s)>,
+L<enc(1s)|enc(1s)>, L<gendsa(1s)|gendsa(1s)>, L<genrsa(1s)|genrsa(1s)>,
+L<nseq(1s)|nseq(1s)>, L<passwd(1s)|passwd(1s)>, L<pkcs12(1s)|pkcs12(1s)>,
+L<pkcs7(1s)|pkcs7(1s)>, L<pkcs8(1s)|pkcs8(1s)>, L<req(1s)|req(1s)>,
+L<rsa(1s)|rsa(1s)>, L<s_client(1s)|s_client(1s)>, L<s_server(1s)|s_server(1s)>,
+L<smime(1s)|smime(1s)>, L<sess_id(1s)|sess_id(1s)>, L<speed(1s)|speed(1s)>,
+L<spkac(1s)|spkac(1s)>, L<verify(1s)|verify(1s)>, L<version(1s)|version(1s)>,
+L<x509(1s)|x509(1s)>, L<crypto(3)|crypto(3)>, L<ssl(3)|ssl(3)>,
+L<config(5s)|config(5s)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/apps/pkcs12.pod openssl-0.9.5/doc/apps/pkcs12.pod
--- openssl-0.9.5-orig/doc/apps/pkcs12.pod Thu Feb 24 19:18:50 2000
+++ openssl-0.9.5/doc/apps/pkcs12.pod Sat Mar 11 20:36:58 2000
@@ -306,5 +306,6 @@
=head1 SEE ALSO
-L<pkcs8(1)|pkcs8(1)>
+L<pkcs8(1s)|pkcs8(1s)>
+=cut
diff -urN openssl-0.9.5-orig/doc/apps/pkcs7.pod openssl-0.9.5/doc/apps/pkcs7.pod
--- openssl-0.9.5-orig/doc/apps/pkcs7.pod Wed Feb 23 03:10:58 2000
+++ openssl-0.9.5/doc/apps/pkcs7.pod Sat Mar 11 20:36:58 2000
@@ -92,6 +92,6 @@
=head1 SEE ALSO
-L<crl2pkcs7(1)|crl2pkcs7(1)>
+L<crl2pkcs7(1s)|crl2pkcs7(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/pkcs8.pod openssl-0.9.5/doc/apps/pkcs8.pod
--- openssl-0.9.5-orig/doc/apps/pkcs8.pod Thu Feb 17 01:16:00 2000
+++ openssl-0.9.5/doc/apps/pkcs8.pod Sat Mar 11 20:36:58 2000
@@ -229,7 +229,7 @@
=head1 SEE ALSO
-L<dsa(1)|dsa(1)>, L<rsa(1)|rsa(1)>, L<genrsa(1)|genrsa(1)>,
-L<gendsa(1)|gendsa(1)>
+L<dsa(1s)|dsa(1s)>, L<rsa(1s)|rsa(1s)>, L<genrsa(1s)|genrsa(1s)>,
+L<gendsa(1s)|gendsa(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/req.pod openssl-0.9.5/doc/apps/req.pod
--- openssl-0.9.5-orig/doc/apps/req.pod Thu Feb 24 19:18:51 2000
+++ openssl-0.9.5/doc/apps/req.pod Sat Mar 11 20:36:58 2000
@@ -522,7 +522,7 @@
=head1 SEE ALSO
-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)>
+L<x509(1s)|x509(1s)>, L<ca(1s)|ca(1s)>, L<genrsa(1s)|genrsa(1s)>,
+L<gendsa(1s)|gendsa(1s)>, L<config(5s)|config(5s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/rsa.pod openssl-0.9.5/doc/apps/rsa.pod
--- openssl-0.9.5-orig/doc/apps/rsa.pod Thu Feb 17 01:16:01 2000
+++ openssl-0.9.5/doc/apps/rsa.pod Sat Mar 11 20:36:58 2000
@@ -150,7 +150,7 @@
=head1 SEE ALSO
-L<pkcs8(1)|pkcs8(1)>, L<dsa(1)|dsa(1)>, L<genrsa(1)|genrsa(1)>,
-L<gendsa(1)|gendsa(1)>
+L<pkcs8(1s)|pkcs8(1s)>, L<dsa(1s)|dsa(1s)>, L<genrsa(1s)|genrsa(1s)>,
+L<gendsa(1s)|gendsa(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/s_client.pod openssl-0.9.5/doc/apps/s_client.pod
--- openssl-0.9.5-orig/doc/apps/s_client.pod Fri Feb 4 01:23:16 2000
+++ openssl-0.9.5/doc/apps/s_client.pod Sat Mar 11 20:36:58 2000
@@ -208,6 +208,6 @@
=head1 SEE ALSO
-L<sess_id(1)|sess_id(1)>, L<s_server(1)|s_server(1)>, L<ciphers(1)|ciphers(1)>
+L<sess_id(1s)|sess_id(1s)>, L<s_server(1s)|s_server(1s)>, L<ciphers(1s)|ciphers(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/s_server.pod openssl-0.9.5/doc/apps/s_server.pod
--- openssl-0.9.5-orig/doc/apps/s_server.pod Fri Feb 4 01:23:16 2000
+++ openssl-0.9.5/doc/apps/s_server.pod Sat Mar 11 20:36:58 2000
@@ -260,6 +260,6 @@
=head1 SEE ALSO
-L<sess_id(1)|sess_id(1)>, L<s_client(1)|s_client(1)>, L<ciphers(1)|ciphers(1)>
+L<sess_id(1s)|sess_id(1s)>, L<s_client(1s)|s_client(1s)>, L<ciphers(1s)|ciphers(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/sess_id.pod openssl-0.9.5/doc/apps/sess_id.pod
--- openssl-0.9.5-orig/doc/apps/sess_id.pod Fri Feb 4 01:23:16 2000
+++ openssl-0.9.5/doc/apps/sess_id.pod Sat Mar 11 20:36:58 2000
@@ -146,6 +146,6 @@
=head1 SEE ALSO
-L<ciphers(1)|ciphers(1)>, L<s_server(1)|s_server(1)>
+L<ciphers(1s)|ciphers(1s)>, L<s_server(1s)|s_server(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/spkac.pod openssl-0.9.5/doc/apps/spkac.pod
--- openssl-0.9.5-orig/doc/apps/spkac.pod Thu Feb 17 01:16:01 2000
+++ openssl-0.9.5/doc/apps/spkac.pod Sat Mar 11 20:36:58 2000
@@ -122,6 +122,6 @@
=head1 SEE ALSO
-L<ca(1)|ca(1)>
+L<ca(1s)|ca(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/verify.pod openssl-0.9.5/doc/apps/verify.pod
--- openssl-0.9.5-orig/doc/apps/verify.pod Thu Jan 27 03:24:53 2000
+++ openssl-0.9.5/doc/apps/verify.pod Sat Mar 11 20:36:58 2000
@@ -268,6 +268,6 @@
=head1 SEE ALSO
-L<x509(1)|x509(1)>
+L<x509(1s)|x509(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/apps/x509.pod openssl-0.9.5/doc/apps/x509.pod
--- openssl-0.9.5-orig/doc/apps/x509.pod Fri Feb 4 01:23:16 2000
+++ openssl-0.9.5/doc/apps/x509.pod Sat Mar 11 20:36:58 2000
@@ -537,7 +537,7 @@
=head1 SEE ALSO
-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)>
+L<req(1s)|req(1s)>, L<ca(1s)|ca(1s)>, L<genrsa(1s)|genrsa(1s)>,
+L<gendsa(1s)|gendsa(1s)>, L<verify(1s)|verify(1s)>
=cut
diff -urN openssl-0.9.5-orig/doc/crypto/BN_generate_prime.pod
openssl-0.9.5/doc/crypto/BN_generate_prime.pod
--- openssl-0.9.5-orig/doc/crypto/BN_generate_prime.pod Thu Feb 24 13:55:05 2000
+++ openssl-0.9.5/doc/crypto/BN_generate_prime.pod Sat Mar 11 20:40:25 2000
@@ -90,7 +90,7 @@
=head1 SEE ALSO
-L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>
+L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<RAND(3)|RAND(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/BN_rand.pod
openssl-0.9.5/doc/crypto/BN_rand.pod
--- openssl-0.9.5-orig/doc/crypto/BN_rand.pod Thu Feb 24 13:55:06 2000
+++ openssl-0.9.5/doc/crypto/BN_rand.pod Sat Mar 11 20:40:35 2000
@@ -34,7 +34,7 @@
=head1 SEE ALSO
-L<bn(3)|bn(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>,
+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
diff -urN openssl-0.9.5-orig/doc/crypto/DH_generate_key.pod
openssl-0.9.5/doc/crypto/DH_generate_key.pod
--- openssl-0.9.5-orig/doc/crypto/DH_generate_key.pod Thu Feb 24 13:55:06 2000
+++ openssl-0.9.5/doc/crypto/DH_generate_key.pod Sat Mar 11 20:40:47 2000
@@ -40,7 +40,7 @@
=head1 SEE ALSO
-L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<DH_size(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
diff -urN openssl-0.9.5-orig/doc/crypto/DH_generate_parameters.pod
openssl-0.9.5/doc/crypto/DH_generate_parameters.pod
--- openssl-0.9.5-orig/doc/crypto/DH_generate_parameters.pod Thu Feb 24 13:55:06
2000
+++ openssl-0.9.5/doc/crypto/DH_generate_parameters.pod Sat Mar 11 20:40:56 2000
@@ -59,7 +59,7 @@
=head1 SEE ALSO
-L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<DH_free(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
diff -urN openssl-0.9.5-orig/doc/crypto/DSA_do_sign.pod
openssl-0.9.5/doc/crypto/DSA_do_sign.pod
--- openssl-0.9.5-orig/doc/crypto/DSA_do_sign.pod Thu Feb 24 13:55:06 2000
+++ openssl-0.9.5/doc/crypto/DSA_do_sign.pod Sat Mar 11 20:41:07 2000
@@ -36,7 +36,7 @@
=head1 SEE ALSO
-L<dsa(3)|dsa(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>,
+L<dsa(3)|dsa(3)>, L<err(3)|err(3)>, L<RAND(3)|RAND(3)>,
L<DSA_SIG_new(3)|DSA_SIG_new(3)>,
L<DSA_sign(3)|DSA_sign(3)>
diff -urN openssl-0.9.5-orig/doc/crypto/DSA_generate_key.pod
openssl-0.9.5/doc/crypto/DSA_generate_key.pod
--- openssl-0.9.5-orig/doc/crypto/DSA_generate_key.pod Thu Feb 24 13:55:07 2000
+++ openssl-0.9.5/doc/crypto/DSA_generate_key.pod Sat Mar 11 20:41:19 2000
@@ -24,7 +24,7 @@
=head1 SEE ALSO
-L<dsa(3)|dsa(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>,
L<DSA_generate_parameters(3)|DSA_generate_parameters(3)>
+L<dsa(3)|dsa(3)>, L<err(3)|err(3)>, L<RAND(3)|RAND(3)>,
+L<DSA_generate_parameters(3)|DSA_generate_parameters(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/DSA_generate_parameters.pod
openssl-0.9.5/doc/crypto/DSA_generate_parameters.pod
--- openssl-0.9.5-orig/doc/crypto/DSA_generate_parameters.pod Thu Feb 24 13:55:07
2000
+++ openssl-0.9.5/doc/crypto/DSA_generate_parameters.pod Sat Mar 11 20:41:28
+2000
@@ -90,7 +90,7 @@
=head1 SEE ALSO
-L<dsa(3)|dsa(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>,
+L<dsa(3)|dsa(3)>, L<err(3)|err(3)>, L<RAND(3)|RAND(3)>,
L<DSA_free(3)|DSA_free(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/DSA_sign.pod
openssl-0.9.5/doc/crypto/DSA_sign.pod
--- openssl-0.9.5-orig/doc/crypto/DSA_sign.pod Mon Jan 31 00:16:45 2000
+++ openssl-0.9.5/doc/crypto/DSA_sign.pod Sat Mar 11 20:41:38 2000
@@ -55,7 +55,7 @@
=head1 SEE ALSO
-L<dsa(3)|dsa(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>,
+L<dsa(3)|dsa(3)>, L<err(3)|err(3)>, L<RAND(3)|RAND(3)>,
L<DSA_do_sign(3)|DSA_do_sign(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/RAND.pod openssl-0.9.5/doc/crypto/RAND.pod
--- openssl-0.9.5-orig/doc/crypto/RAND.pod Thu Jan 1 02:00:00 1970
+++ openssl-0.9.5/doc/crypto/RAND.pod Thu Feb 24 13:55:13 2000
@@ -0,0 +1,158 @@
+=pod
+
+=head1 NAME
+
+rand - pseudo-random number generator
+
+=head1 SYNOPSIS
+
+ #include <openssl/rand.h>
+
+ int RAND_bytes(unsigned char *buf,int num);
+ int RAND_pseudo_bytes(unsigned char *buf,int num);
+
+ void RAND_seed(const void *buf,int num);
+ void RAND_add(const void *buf,int num,int entropy);
+ int RAND_status(void);
+ void RAND_screen(void);
+
+ int RAND_load_file(const char *file,long max_bytes);
+ int RAND_write_file(const char *file);
+ const char *RAND_file_name(char *file,int num);
+
+ int RAND_egd(const char *path);
+
+ void RAND_set_rand_method(RAND_METHOD *meth);
+ RAND_METHOD *RAND_get_rand_method(void);
+ RAND_METHOD *RAND_SSLeay(void);
+
+ void RAND_cleanup(void);
+
+=head1 DESCRIPTION
+
+These functions implement a cryptographically secure pseudo-random
+number generator (PRNG). It is used by other library functions for
+example to generate random keys, and applications can use it when they
+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)|RAND_add(3)>. Its state can be saved in a seed file
+(see L<RAND_load_file(3)|RAND_load_file(3)>) to avoid having to go through the
+seeding process whenever the application is started.
+
+L<RAND_bytes(3)|RAND_bytes(3)> describes how to obtain random data from the
+PRNG.
+
+=head1 INTERNALS
+
+The RAND_SSLeay() method implements a PRNG based on a cryptographic
+hash function.
+
+The following description of its design is based on the SSLeay
+documentation:
+
+First up I will state the things I believe I need for a good RNG.
+
+=over 4
+
+=item 1
+
+A good hashing algorithm to mix things up and to convert the RNG 'state'
+to random numbers.
+
+=item 2
+
+An initial source of random 'state'.
+
+=item 3
+
+The state should be very large. If the RNG is being used to generate
+4096 bit RSA keys, 2 2048 bit random strings are required (at a minimum).
+If your RNG state only has 128 bits, you are obviously limiting the
+search space to 128 bits, not 2048. I'm probably getting a little
+carried away on this last point but it does indicate that it may not be
+a bad idea to keep quite a lot of RNG state. It should be easier to
+break a cipher than guess the RNG seed data.
+
+=item 4
+
+Any RNG seed data should influence all subsequent random numbers
+generated. This implies that any random seed data entered will have
+an influence on all subsequent random numbers generated.
+
+=item 5
+
+When using data to seed the RNG state, the data used should not be
+extractable from the RNG state. I believe this should be a
+requirement because one possible source of 'secret' semi random
+data would be a private key or a password. This data must
+not be disclosed by either subsequent random numbers or a
+'core' dump left by a program crash.
+
+=item 6
+
+Given the same initial 'state', 2 systems should deviate in their RNG state
+(and hence the random numbers generated) over time if at all possible.
+
+=item 7
+
+Given the random number output stream, it should not be possible to determine
+the RNG state or the next random number.
+
+=back
+
+The algorithm is as follows.
+
+There is global state made up of a 1023 byte buffer (the 'state'), a
+working hash value ('md'), and a counter ('count').
+
+Whenever seed data is added, it is inserted into the 'state' as
+follows.
+
+The input is chopped up into units of 20 bytes (or less for
+the last block). Each of these blocks is run through the hash
+function as follows: The data passed to the hash function
+is the current 'md', the same number of bytes from the 'state'
+(the location determined by in incremented looping index) as
+the current 'block', the new key data 'block', and 'count'
+(which is incremented after each use).
+The result of this is kept in 'md' and also xored into the
+'state' at the same locations that were used as input into the
+hash function. I
+believe this system addresses points 1 (hash function; currently
+SHA-1), 3 (the 'state'), 4 (via the 'md'), 5 (by the use of a hash
+function and xor).
+
+When bytes are extracted from the RNG, the following process is used.
+For each group of 10 bytes (or less), we do the following:
+
+Input into the hash function the top 10 bytes from the local 'md'
+(which is initialized from the global 'md' before any bytes are
+generated), the bytes that are to be overwritten by the random bytes,
+and bytes from the 'state' (incrementing looping index). From this
+digest output (which is kept in 'md'), the top (up to) 10 bytes are
+returned to the caller and the bottom (up to) 10 bytes are xored into
+the 'state'.
+
+Finally, after we have finished 'num' random bytes for the caller,
+'count' (which is incremented) and the local and global 'md' are fed
+into the hash function and the results are kept in the global 'md'.
+
+I believe the above addressed points 1 (use of SHA-1), 6 (by hashing
+into the 'state' the 'old' data from the caller that is about to be
+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)|RAND_add(3)>).
+
+=head1 SEE ALSO
+
+L<BN_rand(3)|BN_rand(3)>, L<RAND_add(3)|RAND_add(3)>,
+L<RAND_load_file(3)|RAND_load_file(3)>, L<RAND_egd(3)|RAND_egd(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
diff -urN openssl-0.9.5-orig/doc/crypto/RAND_add.pod
openssl-0.9.5/doc/crypto/RAND_add.pod
--- openssl-0.9.5-orig/doc/crypto/RAND_add.pod Fri Feb 25 17:43:33 2000
+++ openssl-0.9.5/doc/crypto/RAND_add.pod Sat Mar 11 20:41:49 2000
@@ -56,7 +56,7 @@
=head1 SEE ALSO
-L<rand(3)|rand(3)>, L<RAND_egd(3)|RAND_egd(3)>,
+L<RAND(3)|RAND(3)>, L<RAND_egd(3)|RAND_egd(3)>,
L<RAND_load_file(3)|RAND_load_file(3)>, L<RAND_cleanup(3)|RAND_cleanup(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/RAND_bytes.pod
openssl-0.9.5/doc/crypto/RAND_bytes.pod
--- openssl-0.9.5-orig/doc/crypto/RAND_bytes.pod Thu Feb 24 13:55:10 2000
+++ openssl-0.9.5/doc/crypto/RAND_bytes.pod Sat Mar 11 20:41:58 2000
@@ -35,7 +35,7 @@
=head1 SEE ALSO
-L<rand(3)|rand(3)>, L<err(3)|err(3)>, L<RAND_add(3)|RAND_add(3)>
+L<RAND(3)|RAND(3)>, L<err(3)|err(3)>, L<RAND_add(3)|RAND_add(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/RAND_cleanup.pod
openssl-0.9.5/doc/crypto/RAND_cleanup.pod
--- openssl-0.9.5-orig/doc/crypto/RAND_cleanup.pod Thu Jan 27 03:25:06 2000
+++ openssl-0.9.5/doc/crypto/RAND_cleanup.pod Sat Mar 11 20:42:07 2000
@@ -20,7 +20,7 @@
=head1 SEE ALSO
-L<rand(3)|rand(3)>
+L<RAND(3)|RAND(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/RAND_egd.pod
openssl-0.9.5/doc/crypto/RAND_egd.pod
--- openssl-0.9.5-orig/doc/crypto/RAND_egd.pod Thu Feb 24 21:33:58 2000
+++ openssl-0.9.5/doc/crypto/RAND_egd.pod Sat Mar 11 20:42:16 2000
@@ -29,7 +29,7 @@
=head1 SEE ALSO
-L<rand(3)|rand(3)>, L<RAND_add(3)|RAND_add(3)>, L<RAND_cleanup(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
diff -urN openssl-0.9.5-orig/doc/crypto/RAND_load_file.pod
openssl-0.9.5/doc/crypto/RAND_load_file.pod
--- openssl-0.9.5-orig/doc/crypto/RAND_load_file.pod Thu Feb 24 20:19:46 2000
+++ openssl-0.9.5/doc/crypto/RAND_load_file.pod Sat Mar 11 20:42:26 2000
@@ -43,7 +43,7 @@
=head1 SEE ALSO
-L<rand(3)|rand(3)>, L<RAND_add(3)|RAND_add(3)>, L<RAND_cleanup(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
diff -urN openssl-0.9.5-orig/doc/crypto/RAND_set_rand_method.pod
openssl-0.9.5/doc/crypto/RAND_set_rand_method.pod
--- openssl-0.9.5-orig/doc/crypto/RAND_set_rand_method.pod Thu Feb 24 13:55:10
2000
+++ openssl-0.9.5/doc/crypto/RAND_set_rand_method.pod Sat Mar 11 20:42:36 2000
@@ -47,7 +47,7 @@
=head1 SEE ALSO
-L<rand(3)|rand(3)>
+L<RAND(3)|RAND(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/RSA_blinding_on.pod
openssl-0.9.5/doc/crypto/RSA_blinding_on.pod
--- openssl-0.9.5-orig/doc/crypto/RSA_blinding_on.pod Thu Feb 24 13:55:10 2000
+++ openssl-0.9.5/doc/crypto/RSA_blinding_on.pod Sat Mar 11 20:42:46 2000
@@ -34,7 +34,7 @@
=head1 SEE ALSO
-L<rsa(3)|rsa(3)>, L<rand(3)|rand(3)>
+L<rsa(3)|rsa(3)>, L<RAND(3)|RAND(3)>
=head1 HISTORY
diff -urN openssl-0.9.5-orig/doc/crypto/RSA_generate_key.pod
openssl-0.9.5/doc/crypto/RSA_generate_key.pod
--- openssl-0.9.5-orig/doc/crypto/RSA_generate_key.pod Thu Feb 24 13:55:10 2000
+++ openssl-0.9.5/doc/crypto/RSA_generate_key.pod Sat Mar 11 20:42:56 2000
@@ -59,7 +59,7 @@
=head1 SEE ALSO
-L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<rsa(3)|rsa(3)>, L<RSA_free(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
diff -urN openssl-0.9.5-orig/doc/crypto/RSA_public_encrypt.pod
openssl-0.9.5/doc/crypto/RSA_public_encrypt.pod
--- openssl-0.9.5-orig/doc/crypto/RSA_public_encrypt.pod Fri Feb 25 16:19:17
2000
+++ openssl-0.9.5/doc/crypto/RSA_public_encrypt.pod Sat Mar 11 20:43:05 2000
@@ -72,7 +72,7 @@
=head1 SEE ALSO
-L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<rsa(3)|rsa(3)>, L<RSA_size(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
diff -urN openssl-0.9.5-orig/doc/crypto/RSA_sign_ASN1_OCTET_STRING.pod
openssl-0.9.5/doc/crypto/RSA_sign_ASN1_OCTET_STRING.pod
--- openssl-0.9.5-orig/doc/crypto/RSA_sign_ASN1_OCTET_STRING.pod Thu Jan 27
03:25:07 2000
+++ openssl-0.9.5/doc/crypto/RSA_sign_ASN1_OCTET_STRING.pod Sat Mar 11 20:43:16
+2000
@@ -47,7 +47,7 @@
=head1 SEE ALSO
-L<err(3)|err(3)>, L<objects(3)|objects(3)>, L<rand(3)|rand(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)>
diff -urN openssl-0.9.5-orig/doc/crypto/bn.pod openssl-0.9.5/doc/crypto/bn.pod
--- openssl-0.9.5-orig/doc/crypto/bn.pod Sun Feb 27 00:16:45 2000
+++ openssl-0.9.5/doc/crypto/bn.pod Sat Mar 11 20:43:31 2000
@@ -135,7 +135,7 @@
=head1 SEE ALSO
L<bn_internal(3)|bn_internal(3)>,
-L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>, L<rsa(3)|rsa(3)>,
+L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<RAND(3)|RAND(3)>, L<rsa(3)|rsa(3)>,
L<BN_new(3)|BN_new(3)>, L<BN_CTX_new(3)|BN_CTX_new(3)>,
L<BN_copy(3)|BN_copy(3)>, L<BN_num_bytes(3)|BN_num_bytes(3)>,
L<BN_add(3)|BN_add(3)>, L<BN_add_word(3)|BN_add_word(3)>,
diff -urN openssl-0.9.5-orig/doc/crypto/crypto.pod openssl-0.9.5/doc/crypto/crypto.pod
--- openssl-0.9.5-orig/doc/crypto/crypto.pod Wed Feb 23 19:09:50 2000
+++ openssl-0.9.5/doc/crypto/crypto.pod Sat Mar 11 20:43:45 2000
@@ -45,7 +45,7 @@
=item AUXILIARY FUNCTIONS
-L<err(3)|err(3)>, L<threads(3)|threads(3)>, L<rand(3)|rand(3)>
+L<err(3)|err(3)>, L<threads(3)|threads(3)>, L<RAND(3)|RAND(3)>
=item INPUT/OUTPUT, DATA ENCODING
diff -urN openssl-0.9.5-orig/doc/crypto/dh.pod openssl-0.9.5/doc/crypto/dh.pod
--- openssl-0.9.5-orig/doc/crypto/dh.pod Thu Jan 27 21:31:25 2000
+++ openssl-0.9.5/doc/crypto/dh.pod Sat Mar 11 20:43:54 2000
@@ -59,7 +59,7 @@
=head1 SEE ALSO
L<dhparam(1)|dhparam(1)>, L<bn(3)|bn(3)>, L<dsa(3)|dsa(3)>, L<err(3)|err(3)>,
-L<rand(3)|rand(3)>, L<rsa(3)|rsa(3)>, L<DH_set_method(3)|DH_set_method(3)>,
+L<RAND(3)|RAND(3)>, L<rsa(3)|rsa(3)>, L<DH_set_method(3)|DH_set_method(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)>,
diff -urN openssl-0.9.5-orig/doc/crypto/dsa.pod openssl-0.9.5/doc/crypto/dsa.pod
--- openssl-0.9.5-orig/doc/crypto/dsa.pod Thu Feb 3 20:22:00 2000
+++ openssl-0.9.5/doc/crypto/dsa.pod Sat Mar 11 20:44:05 2000
@@ -91,7 +91,7 @@
=head1 SEE ALSO
-L<bn(3)|bn(3)>, L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<rand(3)|rand(3)>,
+L<bn(3)|bn(3)>, L<dh(3)|dh(3)>, L<err(3)|err(3)>, L<RAND(3)|RAND(3)>,
L<rsa(3)|rsa(3)>, L<sha(3)|sha(3)>, L<DSA_new(3)|DSA_new(3)>,
L<DSA_size(3)|DSA_size(3)>,
L<DSA_generate_parameters(3)|DSA_generate_parameters(3)>,
diff -urN openssl-0.9.5-orig/doc/crypto/rand.pod openssl-0.9.5/doc/crypto/rand.pod
--- openssl-0.9.5-orig/doc/crypto/rand.pod Thu Feb 24 13:55:13 2000
+++ openssl-0.9.5/doc/crypto/rand.pod Thu Jan 1 02:00:00 1970
@@ -1,158 +0,0 @@
-=pod
-
-=head1 NAME
-
-rand - pseudo-random number generator
-
-=head1 SYNOPSIS
-
- #include <openssl/rand.h>
-
- int RAND_bytes(unsigned char *buf,int num);
- int RAND_pseudo_bytes(unsigned char *buf,int num);
-
- void RAND_seed(const void *buf,int num);
- void RAND_add(const void *buf,int num,int entropy);
- int RAND_status(void);
- void RAND_screen(void);
-
- int RAND_load_file(const char *file,long max_bytes);
- int RAND_write_file(const char *file);
- const char *RAND_file_name(char *file,int num);
-
- int RAND_egd(const char *path);
-
- void RAND_set_rand_method(RAND_METHOD *meth);
- RAND_METHOD *RAND_get_rand_method(void);
- RAND_METHOD *RAND_SSLeay(void);
-
- void RAND_cleanup(void);
-
-=head1 DESCRIPTION
-
-These functions implement a cryptographically secure pseudo-random
-number generator (PRNG). It is used by other library functions for
-example to generate random keys, and applications can use it when they
-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)|RAND_add(3)>. Its state can be saved in a seed file
-(see L<RAND_load_file(3)|RAND_load_file(3)>) to avoid having to go through the
-seeding process whenever the application is started.
-
-L<RAND_bytes(3)|RAND_bytes(3)> describes how to obtain random data from the
-PRNG.
-
-=head1 INTERNALS
-
-The RAND_SSLeay() method implements a PRNG based on a cryptographic
-hash function.
-
-The following description of its design is based on the SSLeay
-documentation:
-
-First up I will state the things I believe I need for a good RNG.
-
-=over 4
-
-=item 1
-
-A good hashing algorithm to mix things up and to convert the RNG 'state'
-to random numbers.
-
-=item 2
-
-An initial source of random 'state'.
-
-=item 3
-
-The state should be very large. If the RNG is being used to generate
-4096 bit RSA keys, 2 2048 bit random strings are required (at a minimum).
-If your RNG state only has 128 bits, you are obviously limiting the
-search space to 128 bits, not 2048. I'm probably getting a little
-carried away on this last point but it does indicate that it may not be
-a bad idea to keep quite a lot of RNG state. It should be easier to
-break a cipher than guess the RNG seed data.
-
-=item 4
-
-Any RNG seed data should influence all subsequent random numbers
-generated. This implies that any random seed data entered will have
-an influence on all subsequent random numbers generated.
-
-=item 5
-
-When using data to seed the RNG state, the data used should not be
-extractable from the RNG state. I believe this should be a
-requirement because one possible source of 'secret' semi random
-data would be a private key or a password. This data must
-not be disclosed by either subsequent random numbers or a
-'core' dump left by a program crash.
-
-=item 6
-
-Given the same initial 'state', 2 systems should deviate in their RNG state
-(and hence the random numbers generated) over time if at all possible.
-
-=item 7
-
-Given the random number output stream, it should not be possible to determine
-the RNG state or the next random number.
-
-=back
-
-The algorithm is as follows.
-
-There is global state made up of a 1023 byte buffer (the 'state'), a
-working hash value ('md'), and a counter ('count').
-
-Whenever seed data is added, it is inserted into the 'state' as
-follows.
-
-The input is chopped up into units of 20 bytes (or less for
-the last block). Each of these blocks is run through the hash
-function as follows: The data passed to the hash function
-is the current 'md', the same number of bytes from the 'state'
-(the location determined by in incremented looping index) as
-the current 'block', the new key data 'block', and 'count'
-(which is incremented after each use).
-The result of this is kept in 'md' and also xored into the
-'state' at the same locations that were used as input into the
-hash function. I
-believe this system addresses points 1 (hash function; currently
-SHA-1), 3 (the 'state'), 4 (via the 'md'), 5 (by the use of a hash
-function and xor).
-
-When bytes are extracted from the RNG, the following process is used.
-For each group of 10 bytes (or less), we do the following:
-
-Input into the hash function the top 10 bytes from the local 'md'
-(which is initialized from the global 'md' before any bytes are
-generated), the bytes that are to be overwritten by the random bytes,
-and bytes from the 'state' (incrementing looping index). From this
-digest output (which is kept in 'md'), the top (up to) 10 bytes are
-returned to the caller and the bottom (up to) 10 bytes are xored into
-the 'state'.
-
-Finally, after we have finished 'num' random bytes for the caller,
-'count' (which is incremented) and the local and global 'md' are fed
-into the hash function and the results are kept in the global 'md'.
-
-I believe the above addressed points 1 (use of SHA-1), 6 (by hashing
-into the 'state' the 'old' data from the caller that is about to be
-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)|RAND_add(3)>).
-
-=head1 SEE ALSO
-
-L<BN_rand(3)|BN_rand(3)>, L<RAND_add(3)|RAND_add(3)>,
-L<RAND_load_file(3)|RAND_load_file(3)>, L<RAND_egd(3)|RAND_egd(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
diff -urN openssl-0.9.5-orig/doc/crypto/rsa.pod openssl-0.9.5/doc/crypto/rsa.pod
--- openssl-0.9.5-orig/doc/crypto/rsa.pod Tue Feb 22 14:01:50 2000
+++ openssl-0.9.5/doc/crypto/rsa.pod Sat Mar 11 20:44:18 2000
@@ -100,7 +100,7 @@
=head1 SEE ALSO
L<rsa(1)|rsa(1)>, L<bn(3)|bn(3)>, L<dsa(3)|dsa(3)>, L<dh(3)|dh(3)>,
-L<rand(3)|rand(3)>, L<RSA_new(3)|RSA_new(3)>,
+L<RAND(3)|RAND(3)>, L<RSA_new(3)|RSA_new(3)>,
L<RSA_public_encrypt(3)|RSA_public_encrypt(3)>,
L<RSA_sign(3)|RSA_sign(3)>, L<RSA_size(3)|RSA_size(3)>,
L<RSA_generate_key(3)|RSA_generate_key(3)>,
