Re: [Hash] Charter discussion, round 1

Russ Housley <housley@vigilsec.com> Fri, 17 June 2005 15:43 UTC

Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjJ0E-0005pd-Or; Fri, 17 Jun 2005 11:43:30 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DjJ0C-0005oG-E4 for hash@megatron.ietf.org; Fri, 17 Jun 2005 11:43:28 -0400
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28347 for <hash@ietf.org>; Fri, 17 Jun 2005 11:43:25 -0400 (EDT)
Received: from woodstock.binhost.com ([144.202.243.4]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1DjJNH-0005bf-HC for hash@ietf.org; Fri, 17 Jun 2005 12:07:22 -0400
Received: (qmail 24012 invoked by uid 0); 17 Jun 2005 15:43:16 -0000
Received: from unknown (HELO Russ-Laptop.vigilsec.com) (138.88.18.238) by woodstock.binhost.com with SMTP; 17 Jun 2005 15:43:16 -0000
Message-Id: <6.2.1.2.2.20050617114209.0640e0d0@mail.binhost.com>
X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2
Date: Fri, 17 Jun 2005 11:43:16 -0400
To: Thomas Roessler <tlr@w3.org>
From: Russ Housley <housley@vigilsec.com>
Subject: Re: [Hash] Charter discussion, round 1
In-Reply-To: <20050617084345.GJ32581@raktajino.does-not-exist.org>
References: <6.2.1.2.2.20050609152413.078e8ac0@mail.binhost.com> <p06210245bece4ebbbea1@[10.20.30.249]> <20050616081143.GC32581@raktajino.does-not-exist.org> <p0621023abed742623640@[10.20.30.249]> <20050617084345.GJ32581@raktajino.does-not-exist.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
X-Spam-Score: 0.2 (/)
X-Scan-Signature: 9ed51c9d1356100bce94f1ae4ec616a9
Cc: w3t-archive@w3.org, hash@ietf.org
X-BeenThere: hash@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: hash.lists.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/hash>, <mailto:hash-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/hash>
List-Post: <mailto:hash@lists.ietf.org>
List-Help: <mailto:hash-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/hash>, <mailto:hash-request@lists.ietf.org?subject=subscribe>
Sender: hash-bounces@lists.ietf.org
Errors-To: hash-bounces@lists.ietf.org

Perhaps "as a parameter to the algorithm identifier" captures the intent 
even better.  It would read:

   2) Including a random value in the hash function computation. The
      random block used is transferred as a parameter to the algorithm
      identifier.  This approach is sometimes called a "salted" or
      "randomized" hash function.

Russ


At 04:43 AM 6/17/2005, Thomas Roessler wrote:
>On 2005-06-16 07:53:27 -0700, Paul Hoffman wrote:
>
> > >On 2005-06-09 13:02:47 -0700, Paul Hoffman wrote:
> > >
> > >>   2) Including a random value in the hash function computation. The
> > >>      random block used is transferred as a parameter in the algorithm
> > >>      identifier.  This approach is sometimes called a "salted" or
> > >>      "randomized" hash function.
>
> > >Is this meant to imply an approach where hash identifiers would look
> > >like, say, "shaN-0xdeadbeef", 0xdeadbeef being the salt?  Or is it
> > >merely meant to imply that the seed would be transferred along with
> > >the algorithm identifier, somehow?
>
> > The proposal is a -00 draft, so it has not yet been decided, but it
> > is extremely likely to be the latter. IETF protocols don't usually
> > carry the names of algorithms, but instead use numeric identifiers
> > for them. In the current case, it is likely that the salt would be
> > carried as a parameter in an ASN.1 construct, or something similar.
>
>Thanks for the clarification.
>
>Maybe you could change "in the algorithm identifier" to "with the
>algorithm identifier", to make a little clearer that this
>description is not tied to any particular assumption of what an
>algorithm identifier looks like?
>
>Thanks,
>--
>Thomas Roessler, W3C   <tlr@w3.org>


_______________________________________________
Hash mailing list
Hash@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/hash