FYI, the complete set of the MD algorithms are now officially
informational RFCs.
I will update the RFC 1115 successor to reference the MD2 and MD5 RFCs.
-DB
------- Forwarded Message
Message-ID: <9204161710(_dot_)AA06268(_at_)akamai(_dot_)isi(_dot_)edu>
From: jkrey(_at_)ISI(_dot_)EDU (Joyce Reynolds)
To: ietf(_at_)ISI(_dot_)EDU, rfc-dist(_at_)nic(_dot_)ddn(_dot_)mil
cc: jkrey(_at_)ISI(_dot_)EDU
Date: Thu, 16 Apr 92 10:10:21 PDT
Subject: RFCs 1319, 1320, 1321 on MD2 Message-Digest Algorithm, MD4 Message-
Digest Algorithm, MD5 Message-Digest Algorithm
New Request for Comments are now available in online RFC libraries:
RFC 1319:
Title: The MD2 Message-Digest Algorithm
Author: B. Kaliski
Mailbox: burt(_at_)rsa(_dot_)com
Pages: 17
Characters: 25,661
Updates: RFC 1115
This document describes the MD2 message-digest algorithm. The
algorithm takes as input a message of arbitrary length and produces
as output a 128-bit "fingerprint" or "message digest" of the input.
It is conjectured that it is computationally infeasible to produce
two messages having the same message digest, or to produce any
message having a given prespecified target message digest. The MD2
algorithm is intended for digital signature applications, where a
large file must be "compressed" in a secure manner before being
signed with a private (secret) key under a public-key cryptosystem
such as RSA.
This memo provides information for the Internet community. It does
not specify an Internet standard. Distribution of this memo is
unlimited.
RFC 1320:
Title: The MD4 Message-Digest Algorithm
Author: R. Rivest
Mailbox: rivest(_at_)theory(_dot_)lcs(_dot_)mit(_dot_)edu
Pages: 20
Characters: 32,407
Obsoletes: RFC 1186
This document describes the MD4 message-digest algorithm. The
algorithm takes as input a message of arbitrary length and produces as
output a 128-bit "fingerprint" or "message digest" of the input. It
is conjectured that it is computationally infeasible to produce two
messages having the same message digest, or to produce any message
having a given prespecified target message digest. The MD4 algorithm
is intended for digital signature applications, where a large file
must be "compressed" in a secure manner before being encrypted with a
private (secret) key under a public-key cryptosystem such as RSA.
This memo provides information for the Internet community. It does
not specify an Internet standard. Distribution of this memo is
unlimited.
RFC 1321:
Title: The MD5 Message-Digest Algorithm
Author: R. Rivest
Mailbox: rivest(_at_)theory(_dot_)lcs(_dot_)mit(_dot_)edu
Pages: 21
Characters: 35,222
Obsoletes/Updates: none
This document describes the MD5 message-digest algorithm. The
algorithm takes as input a message of arbitrary length and produces
as output a 128-bit "fingerprint" or "message digest" of the input.
It is conjectured that it is computationally infeasible to produce
two messages having the same message digest, or to produce any
message having a given prespecified target message digest. The MD5
algorithm is intended for digital signature applications, where a
large file must be "compressed" in a secure manner before being
encrypted with a private (secret) key under a public-key cryptosystem
such as RSA.
This memo provides information for the Internet community. It does
not specify an Internet standard. Distribution of this memo is
unlimited.
RFCs can be obtained via FTP from FTP.NISC.SRI.COM, NIS.NSF.NET,
NISC.JVNC.NET, VENERA.ISI.EDU, WUARCHIVE.WUSTL.EDU, SRC.DOC.IC.AC.UK,
FTP.CONCERT.NET, or NIC.DDN.MIL.
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to "rfc-info(_at_)ISI(_dot_)EDU" with the message body
"help: ways_to_get_rfcs". For example:
To: rfc-info(_at_)ISI(_dot_)EDU
Subject: getting rfcs
help: ways_to_get_rfcs
Requests for special distribution should be addressed to either the
author of the RFC in question, or to NIC(_at_)NIC(_dot_)DDN(_dot_)MIL(_dot_)
Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
Submissions for Requests for Comments should be sent to
RFC-EDITOR(_at_)ISI(_dot_)EDU(_dot_) Please consult RFC 1111, "Instructions to
RFC
Authors", for further information.
Requests to be added to or deleted from this distribution list should
be sent to RFC-REQUEST(_at_)NIC(_dot_)DDN(_dot_)MIL(_dot_)
Joyce K. Reynolds
USC/Information Sciences Institute
------- End of Forwarded Message