-.\" $OpenBSD: md5.1,v 1.30 2010/07/13 06:57:37 jmc Exp $
+.\" $OpenBSD: md5.1,v 1.31 2010/07/13 22:34:45 tedu Exp $
.\"
.\" Copyright (c) 2003, 2004, 2006 Todd C. Miller <Todd.Miller@courtesan.com>
.\"
However, collisions have now been produced for
.Em MD5 ,
so the use of other message digest functions, such as
-.Xr sha1 1 ,
+.Xr sha256 1 ,
is now preferred.
.Pp
The
Since collisions have been found for
.Em MD5 ,
the use of
-.Xr sha1 1
+.Xr sha256 1
is recommended instead.
.\" this stuff is worth it, you can buy me a beer in return. Poul-Henning Kamp
.\" ----------------------------------------------------------------------------
.\"
-.\" $OpenBSD: mdX.3,v 1.10 2007/05/31 19:19:29 jmc Exp $
+.\" $OpenBSD: mdX.3,v 1.11 2010/07/13 22:34:45 tedu Exp $
.\"
-.Dd $Mdocdate: May 31 2007 $
+.Dd $Mdocdate: July 13 2010 $
.Dt MDX 3
.Os
.Sh NAME
.Dq fingerprint
of the input-data, which doesn't disclose the actual input.
.Pp
-MD4 has been broken; it should only be used where necessary for
+MD4 and MD5 have been broken; they should only be used where necessary for
backward compatibility.
-MD5 has not yet (1999-02-11) been broken, but recent attacks have cast
-some doubt on its security properties.
The attacks on both MD4 and MD5
are both in the nature of finding
.Dq collisions
.Sh BUGS
Collisions have been found for the full versions of both MD4 and MD5.
The use of
-.Xr sha1 3 ,
-.Xr sha2 3 ,
-or
-.Xr rmd160 3
+.Xr sha2 3
is recommended instead.