IETF Logo Mail Archive

Re: [saag] SHA-1 to SHA-n transition

Jeffrey Hutzelman <jhutz@cmu.edu> Wed, 04 March 2009 16:31 UTC

Return-Path: <jhutz@cmu.edu>
X-Original-To: saag@core3.amsl.com
Delivered-To: saag@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 573553A6CD5 for <saag@core3.amsl.com>; Wed, 4 Mar 2009 08:31:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N-5bXT6CWH0l for <saag@core3.amsl.com>; Wed, 4 Mar 2009 08:31:44 -0800 (PST)
Received: from jackfruit.srv.cs.cmu.edu (JACKFRUIT.SRV.CS.CMU.EDU [128.2.201.16]) by core3.amsl.com (Postfix) with ESMTP id 73A0D3A6D01 for <saag@ietf.org>; Wed, 4 Mar 2009 08:31:44 -0800 (PST)
Received: from 68-247-180-249.pools.spcsdns.net (174-147-215-117.pools.spcsdns.net [174.147.215.117]) (authenticated bits=0) by jackfruit.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id n24GW5Ko010137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 4 Mar 2009 11:32:06 -0500 (EST)
Date: Wed, 04 Mar 2009 11:32:04 -0500
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: "Hallam-Baker, Phillip" <pbaker@verisign.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>, saag@ietf.org
Message-ID: <1A3A77AE3B3614022A6C60C3@atlantis.pc.cs.cmu.edu>
In-Reply-To: <2788466ED3E31C418E9ACC5C3166155768B2F7@mou1wnexmb09.vcorp.ad.vrsn.com>
References: <E1Lekmy-0001Zx-KD@wintermute01.cs.auckland.ac.nz> <2788466ED3E31C418E9ACC5C3166155768B2F7@mou1wnexmb09.vcorp.ad.vrsn.com>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.201.16
Subject: Re: [saag] SHA-1 to SHA-n transition
X-BeenThere: saag@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Advisory Group <saag.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/saag>
List-Post: <mailto:saag@ietf.org>
List-Help: <mailto:saag-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/saag>, <mailto:saag-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Mar 2009 16:31:45 -0000

--On Wednesday, March 04, 2009 05:34:43 AM -0800 "Hallam-Baker, Phillip" 
<pbaker@verisign.com> wrote:

> We are now into the identity issue which has precisley nothing to do with
> algorithm transitions.

Thanks for bringing us back around to the original point.  I'm not sure how 
we got into talking about identity and user credentials, but I seem to 
recall this thread started with a discussion of hash algorithm transition, 
and rather quickly moved away from that topic without any real resolution. 
Can we perhaps get back to discussing a technical problem we can solve, 
instead of one that is outside our expertise?

-- Jeff

v2.23.0 | Report a Bug | By Email