summaryrefslogtreecommitdiff
path: root/src/lib/libcrypto/doc/MD5.pod
diff options
context:
space:
mode:
authordoug <>2015-09-13 23:36:21 +0000
committerdoug <>2015-09-13 23:36:21 +0000
commit5e0ea5055e21b1f3526587a5a17702ab3fee3e49 (patch)
tree804e21f7971977c17340feffa6cc8840e09b3cfe /src/lib/libcrypto/doc/MD5.pod
parentc221c5094439136f46f34e398f2908ca9b5bfb1d (diff)
downloadopenbsd-5e0ea5055e21b1f3526587a5a17702ab3fee3e49.tar.gz
openbsd-5e0ea5055e21b1f3526587a5a17702ab3fee3e49.tar.bz2
openbsd-5e0ea5055e21b1f3526587a5a17702ab3fee3e49.zip
Remove MD4 support from LibreSSL.
MD4 should have been removed a long time ago. Also, RFC 6150 moved it to historic in 2011. Rides the major crank from removing SHA-0. Discussed with many including beck@, millert@, djm@, sthen@ ok jsing@, input + ok bcook@
Diffstat (limited to 'src/lib/libcrypto/doc/MD5.pod')
-rw-r--r--src/lib/libcrypto/doc/MD5.pod67
1 files changed, 13 insertions, 54 deletions
diff --git a/src/lib/libcrypto/doc/MD5.pod b/src/lib/libcrypto/doc/MD5.pod
index b0edd5416f..056f94bd9e 100644
--- a/src/lib/libcrypto/doc/MD5.pod
+++ b/src/lib/libcrypto/doc/MD5.pod
@@ -2,33 +2,10 @@
2 2
3=head1 NAME 3=head1 NAME
4 4
5MD2, MD4, MD5, MD2_Init, MD2_Update, MD2_Final, MD4_Init, MD4_Update, 5MD5, MD5_Init, MD5_Update, MD5_Final - MD5 hash functions
6MD4_Final, MD5_Init, MD5_Update, MD5_Final - MD2, MD4, and MD5 hash functions
7 6
8=head1 SYNOPSIS 7=head1 SYNOPSIS
9 8
10 #include <openssl/md2.h>
11
12 unsigned char *MD2(const unsigned char *d, unsigned long n,
13 unsigned char *md);
14
15 int MD2_Init(MD2_CTX *c);
16 int MD2_Update(MD2_CTX *c, const unsigned char *data,
17 unsigned long len);
18 int MD2_Final(unsigned char *md, MD2_CTX *c);
19
20
21 #include <openssl/md4.h>
22
23 unsigned char *MD4(const unsigned char *d, unsigned long n,
24 unsigned char *md);
25
26 int MD4_Init(MD4_CTX *c);
27 int MD4_Update(MD4_CTX *c, const void *data,
28 unsigned long len);
29 int MD4_Final(unsigned char *md, MD4_CTX *c);
30
31
32 #include <openssl/md5.h> 9 #include <openssl/md5.h>
33 10
34 unsigned char *MD5(const unsigned char *d, unsigned long n, 11 unsigned char *MD5(const unsigned char *d, unsigned long n,
@@ -41,61 +18,43 @@ MD4_Final, MD5_Init, MD5_Update, MD5_Final - MD2, MD4, and MD5 hash functions
41 18
42=head1 DESCRIPTION 19=head1 DESCRIPTION
43 20
44MD2, MD4, and MD5 are cryptographic hash functions with a 128 bit output. 21MD5 is a cryptographic hash function with a 128 bit output.
45 22
46MD2(), MD4(), and MD5() compute the MD2, MD4, and MD5 message digest 23MD5() computes the MD5 message digest of the B<n> bytes at B<d> and
47of the B<n> bytes at B<d> and place it in B<md> (which must have space 24places it in B<md> (which must have space for MD5_DIGEST_LENGTH == 16
48for MD2_DIGEST_LENGTH == MD4_DIGEST_LENGTH == MD5_DIGEST_LENGTH == 16
49bytes of output). If B<md> is NULL, the digest is placed in a static 25bytes of output). If B<md> is NULL, the digest is placed in a static
50array. 26array.
51 27
52The following functions may be used if the message is not completely 28The following functions may be used if the message is not completely
53stored in memory: 29stored in memory:
54 30
55MD2_Init() initializes a B<MD2_CTX> structure.
56
57MD2_Update() can be called repeatedly with chunks of the message to
58be hashed (B<len> bytes at B<data>).
59
60MD2_Final() places the message digest in B<md>, which must have space
61for MD2_DIGEST_LENGTH == 16 bytes of output, and erases the B<MD2_CTX>.
62
63MD4_Init(), MD4_Update(), MD4_Final(), MD5_Init(), MD5_Update(), and
64MD5_Final() are analogous using an B<MD4_CTX> and B<MD5_CTX> structure.
65
66Applications should use the higher level functions 31Applications should use the higher level functions
67L<EVP_DigestInit(3)|EVP_DigestInit(3)> 32L<EVP_DigestInit(3)|EVP_DigestInit(3)>
68etc. instead of calling the hash functions directly. 33etc. instead of calling the hash functions directly.
69 34
70=head1 NOTE 35=head1 NOTE
71 36
72MD2, MD4, and MD5 are recommended only for compatibility with existing 37MD5 is recommended only for compatibility with legacy applications.
73applications. In new applications, SHA-1 or RIPEMD-160 should be 38In new applications, SHA-2 should be preferred.
74preferred.
75 39
76=head1 RETURN VALUES 40=head1 RETURN VALUES
77 41
78MD2(), MD4(), and MD5() return pointers to the hash value. 42MD5() returns a pointer to the hash value.
79 43
80MD2_Init(), MD2_Update(), MD2_Final(), MD4_Init(), MD4_Update(), 44MD5_Init(), MD5_Update(), and MD5_Final() return 1 for success, 0
81MD4_Final(), MD5_Init(), MD5_Update(), and MD5_Final() return 1 for 45otherwise.
82success, 0 otherwise.
83 46
84=head1 CONFORMING TO 47=head1 CONFORMING TO
85 48
86RFC 1319, RFC 1320, RFC 1321 49RFC 1321
87 50
88=head1 SEE ALSO 51=head1 SEE ALSO
89 52
90L<sha(3)|sha(3)>, L<ripemd(3)|ripemd(3)>, L<EVP_DigestInit(3)|EVP_DigestInit(3)> 53L<EVP_DigestInit(3)|EVP_DigestInit(3)>
91 54
92=head1 HISTORY 55=head1 HISTORY
93 56
94MD2(), MD2_Init(), MD2_Update() MD2_Final(), MD5(), MD5_Init(), 57MD5(), MD5_Init(), MD5_Update() and MD5_Final() are available in all
95MD5_Update() and MD5_Final() are available in all versions of SSLeay 58versions of OpenSSL.
96and OpenSSL.
97
98MD4(), MD4_Init(), and MD4_Update() are available in OpenSSL 0.9.6 and
99above.
100 59
101=cut 60=cut