From: Ulf Möller <ulf@openssl.org>
Date: Fri, 25 Feb 2000 16:00:24 +0000 (+0000)
Subject: links
X-Git-Tag: OpenSSL_0_9_5beta2~53
X-Git-Url: https://git.openssl.org/gitweb/?p=openssl.git;a=commitdiff_plain;h=d52c973498901e7cd6453ee1fcd75d7d770b0d3c

links
---

diff --git a/doc/crypto/blowfish.pod b/doc/crypto/blowfish.pod
index 80cb44edba..e8c7114311 100644
--- a/doc/crypto/blowfish.pod
+++ b/doc/crypto/blowfish.pod
@@ -90,8 +90,9 @@ None of the functions presented here return any value.
 
 =head1 NOTE
 
-Applications should use the higher level functions EVP_EncryptInit(3) etc.
-instead of calling the blowfish functions directly.
+Applications should use the higher level functions
+L<EVP_EncryptInit(3)|EVP_EncryptInit(3)> etc. instead of calling the
+blowfish functions directly.
 
 =head1 SEE ALSO
 
diff --git a/doc/crypto/md5.pod b/doc/crypto/md5.pod
index 2b084878cd..d7c120023d 100644
--- a/doc/crypto/md5.pod
+++ b/doc/crypto/md5.pod
@@ -51,7 +51,8 @@ for MD2_DIGEST_LENGTH == 16 bytes of output, and erases the B<MD2_CTX>.
 MD5_Init(), MD5_Update() and MD5_Final() are analogous using an
 B<MD5_CTX> structure.
 
-Applications should use the higher level functions EVP_DigestInit(3)
+Applications should use the higher level functions
+L<EVP_DigestInit(3)|EVP_DigestInit(3)>
 etc. instead of calling the hash functions directly.
 
 =head1 NOTE
diff --git a/doc/crypto/mdc2.pod b/doc/crypto/mdc2.pod
index d991a05972..11dc303e04 100644
--- a/doc/crypto/mdc2.pod
+++ b/doc/crypto/mdc2.pod
@@ -38,15 +38,16 @@ be hashed (B<len> bytes at B<data>).
 MDC2_Final() places the message digest in B<md>, which must have space
 for MDC2_DIGEST_LENGTH == 16 bytes of output, and erases the B<MDC2_CTX>.
 
+Applications should use the higher level functions
+L<EVP_DigestInit(3)|EVP_DigestInit(3)> etc. instead of calling the
+hash functions directly.
+
 =head1 RETURN VALUES
 
 MDC2() returns a pointer to the hash value. 
 
 MDC2_Init(), MDC2_Update() and MDC2_Final() do not return values.
 
-Applications should use the higher level functions EVP_DigestInit(3) etc.
-instead of calling the hash functions directly.
-
 =head1 CONFORMING TO
 
 ISO/IEC 10118-2, with DES
diff --git a/doc/crypto/rc4.pod b/doc/crypto/rc4.pod
index aaab850afd..b6d3a4342c 100644
--- a/doc/crypto/rc4.pod
+++ b/doc/crypto/rc4.pod
@@ -37,7 +37,8 @@ Since RC4 is a stream cipher (the input is XORed with a pseudo-random
 key stream to produce the output), decryption uses the same function
 calls as encryption.
 
-Applications should use the higher level functions EVP_EncryptInit(3)
+Applications should use the higher level functions
+L<EVP_EncryptInit(3)|EVP_EncryptInit(3)>
 etc. instead of calling the RC4 functions directly.
 
 =head1 RETURN VALUES
diff --git a/doc/crypto/ripemd.pod b/doc/crypto/ripemd.pod
index 9656bb0980..31054b6a8c 100644
--- a/doc/crypto/ripemd.pod
+++ b/doc/crypto/ripemd.pod
@@ -39,8 +39,9 @@ RIPEMD160_Final() places the message digest in B<md>, which must have
 space for RIPEMD160_DIGEST_LENGTH == 20 bytes of output, and erases
 the B<RIPEMD160_CTX>.
 
-Applications should use the higher level functions EVP_DigestInit(3) etc.
-instead of calling the hash functions directly.
+Applications should use the higher level functions
+L<EVP_DigestInit(3)|EVP_DigestInit(3)> etc. instead of calling the
+hash functions directly.
 
 =head1 RETURN VALUES
 
diff --git a/doc/crypto/sha.pod b/doc/crypto/sha.pod
index 57b0fb6da4..0ba315d6d7 100644
--- a/doc/crypto/sha.pod
+++ b/doc/crypto/sha.pod
@@ -37,7 +37,8 @@ be hashed (B<len> bytes at B<data>).
 SHA1_Final() places the message digest in B<md>, which must have space
 for SHA_DIGEST_LENGTH == 20 bytes of output, and erases the B<SHA_CTX>.
 
-Applications should use the higher level functions EVP_DigestInit(3)
+Applications should use the higher level functions
+L<EVP_DigestInit(3)|EVP_DigestInit(3)>
 etc. instead of calling the hash functions directly.
 
 The predecessor of SHA-1, SHA, is also implemented, but it should be