1995-10-31 - Re: Keyed-MD5, ITAR, and HTTP-NG

Header Data

From: John Lull <lull@acm.org>
To: hallam@w3.org
Message Hash: f3b14d1ba1b45f6d5b369836836d51d1d3e8b2db3ee380d49a79b98db10ae54b
Message ID: <199510311650.IAA09144@ix2.ix.netcom.com>
Reply To: <9510310427.AA28252@zorch.w3.org>
UTC Datetime: 1995-10-31 18:22:27 UTC
Raw Date: Wed, 1 Nov 1995 02:22:27 +0800

Raw message

From: John Lull <lull@acm.org>
Date: Wed, 1 Nov 1995 02:22:27 +0800
To: hallam@w3.org
Subject: Re: Keyed-MD5, ITAR, and HTTP-NG
In-Reply-To: <9510310427.AA28252@zorch.w3.org>
Message-ID: <199510311650.IAA09144@ix2.ix.netcom.com>
MIME-Version: 1.0
Content-Type: text/plain


On Mon, 30 Oct 1995 23:27:36 -0500, you wrote:

> Hash functions		MD5, SHA

I presume you mean SHA-1.

I would prefer to see MD5 deleted.  A 128 bit hash simply seems too
marginal in length for long term use in most hash applications.  I
would much rather see something like Haval as a second hash algorithm.
It can be faster than MD5, and can easily be tailored to the hash
width you want.  If 128 bit hashes are really needed, use Haval's
128-bit option.

Thread

• Return to October 1995

• Return to “hallam@w3.org”
• Return to “John Lull <lull@acm.org>”
• Return to “Mike_Spreitzer.PARC@xerox.com”

• Return to “Rich Salz <rsalz@osf.org>”

• 1995-10-31 (Tue, 31 Oct 1995 12:05:03 +0800) - Re: Keyed-MD5, ITAR, and HTTP-NG - Rich Salz <rsalz@osf.org>
  • 1995-10-31 (Tue, 31 Oct 1995 12:54:37 +0800) - Re: Keyed-MD5, ITAR, and HTTP-NG - hallam@w3.org
    • 1995-10-31 (Wed, 1 Nov 1995 02:22:27 +0800) - Re: Keyed-MD5, ITAR, and HTTP-NG - John Lull <lull@acm.org>
      • 1995-10-31 (Wed, 1 Nov 1995 04:16:56 +0800) - Re: Keyed-MD5, ITAR, and HTTP-NG - hallam@w3.org
        • 1995-10-31 (Wed, 1 Nov 1995 07:13:35 +0800) - Re: Keyed-MD5, ITAR, and HTTP-NG - John Lull <lull@acm.org>
    • 1995-10-31 (Wed, 1 Nov 1995 04:59:25 +0800) - Re: Keyed-MD5, ITAR, and HTTP-NG - Mike_Spreitzer.PARC@xerox.com