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

Nicolas Williams <Nicolas.Williams@sun.com> Tue, 03 March 2009 17:04 UTC

Return-Path: <Nicolas.Williams@sun.com>
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 800FA3A6917 for <saag@core3.amsl.com>; Tue, 3 Mar 2009 09:04:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.85
X-Spam-Level:
X-Spam-Status: No, score=-5.85 tagged_above=-999 required=5 tests=[AWL=0.196, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, 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 KrRbIyCm0IiY for <saag@core3.amsl.com>; Tue, 3 Mar 2009 09:04:05 -0800 (PST)
Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by core3.amsl.com (Postfix) with ESMTP id 865B03A679C for <saag@ietf.org>; Tue, 3 Mar 2009 09:04:05 -0800 (PST)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n23H4WnF008014 for <saag@ietf.org>; Tue, 3 Mar 2009 17:04:32 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-02.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL, v2.2) with ESMTP id n23H4WpU044583 for <saag@ietf.org>; Tue, 3 Mar 2009 10:04:32 -0700 (MST)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id n23GeVpV014232; Tue, 3 Mar 2009 10:40:31 -0600 (CST)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n23GeV5Y014231; Tue, 3 Mar 2009 10:40:31 -0600 (CST)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Tue, 03 Mar 2009 10:40:31 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Message-ID: <20090303164030.GD9992@Sun.COM>
References: <0DE6E86D395C657BABF43B97@minbar.fac.cs.cmu.edu> <E1LeXZP-0000x0-NP@wintermute01.cs.auckland.ac.nz>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <E1LeXZP-0000x0-NP@wintermute01.cs.auckland.ac.nz>
User-Agent: Mutt/1.5.7i
Cc: saag@ietf.org
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: Tue, 03 Mar 2009 17:04:06 -0000

On Wed, Mar 04, 2009 at 05:34:15AM +1300, Peter Gutmann wrote:
> Jeffrey Hutzelman <jhutz@cmu.edu> writes:
> >How do you expect users to remember not to give away their passwords when
> >they can't be bothered to remember to wash their hands or look both ways
> >before crossing a street?
> 
>  site_password = HMAC( user_password || 128-bit salt, site_URL );

I've had sundry such browser plugins installed and I still don't use
them.  I tried, but I stopped when I noticed that using such passwords
in my cell phone was a royal PITA.

Thanks, you've managed to depress me :)

You've also disproved my point and proved EKR's.  The clarity is welcomed.