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

Eric Rescorla <ekr@networkresonance.com> Mon, 02 March 2009 18:37 UTC

Return-Path: <ekr@networkresonance.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 5661028C285 for <saag@core3.amsl.com>; Mon, 2 Mar 2009 10:37:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.538
X-Spam-Level:
X-Spam-Status: No, score=-2.538 tagged_above=-999 required=5 tests=[AWL=0.061, BAYES_00=-2.599]
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 5Hj3UUjSWPF8 for <saag@core3.amsl.com>; Mon, 2 Mar 2009 10:37:38 -0800 (PST)
Received: from romeo.rtfm.com (romeo.rtfm.com [74.95.2.173]) by core3.amsl.com (Postfix) with ESMTP id 920E228C1DC for <saag@ietf.org>; Mon, 2 Mar 2009 10:37:38 -0800 (PST)
Received: from romeo.rtfm.com (localhost.rtfm.com [127.0.0.1]) by romeo.rtfm.com (Postfix) with ESMTP id 6E11550822; Mon, 2 Mar 2009 11:00:55 -0800 (PST)
Date: Mon, 02 Mar 2009 11:00:55 -0800
From: Eric Rescorla <ekr@networkresonance.com>
To: Nicolas Williams <Nicolas.Williams@sun.com>
In-Reply-To: <20090302181657.GV9992@Sun.COM>
References: <0c2301c9979f$8a1cd770$0600a8c0@china.huawei.com> <2788466ED3E31C418E9ACC5C3166155768B2CE@mou1wnexmb09.vcorp.ad.vrsn.com> <20090226143809.GF7227@mit.edu> <1235663917.3293.16.camel@localhost> <20090226165448.GK9992@Sun.COM> <20090227022359.8D45150822@romeo.rtfm.com> <20090302161134.GG9992@Sun.COM> <20090302172135.DA43650822@romeo.rtfm.com> <20090302171122.GM9992@Sun.COM> <20090302181143.2B7B550822@romeo.rtfm.com> <20090302181657.GV9992@Sun.COM>
User-Agent: Wanderlust/2.14.0 (Africa) Emacs/21.3 Mule/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="US-ASCII"
Message-Id: <20090302190055.6E11550822@romeo.rtfm.com>
Cc: der Mouse <mouse@Rodents-Montreal.ORG>, 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: Mon, 02 Mar 2009 18:37:39 -0000

At Mon, 2 Mar 2009 12:16:57 -0600,
Nicolas Williams wrote:
> 
> On Mon, Mar 02, 2009 at 10:11:43AM -0800, Eric Rescorla wrote:
> > And the attacker will just pop up a dialog that says "our cool new UI
> > system is broken. Type your password into the form for now." This is
> > quite clear from [SDO+07].
> 
> Clearly.  Eventually this would no longer be true -- but we'll never get
> there if we don't provide any mechanisms that can overcome this.
> Certificates won't do because passwords remain, and will remain the
> lowest common denominator for a long time.
> 
> Unless small, portable devices with UIs (mobile phones!) become so
> ubiquitous (they're getting there) that they are as portable and ever
> present as passwords.  But I suspect the same will apply to that
> alternative: it will be years before we stop relying on passwords.
> 
> > > Any solution will require training, if nothing else because otherwise
> > > everyone will continue doing what we all do today: typing passwords into
> > > HTML forms, so that servers get cleartext passwords, and MITMs get all
> > > our money.
> > 
> > "We must do something. This is something. We must do this."
> 
> There are so many "this" we can do, and any one will take time.  Choose
> an approach.  Requiring that everyone have bluetooth- and NFC-equipped
> cell phones (and probably data rate service) and desktops and laptops
> (terminals of any kind) will certainly do, provided that such a
> requirement is reasonable -- we're getting closer to where it is.

We're now in the discussion I told myself I didn't want to have.
Suffice to say that for the reasons I've alredy indicated I don't
think the technical direction you propose is at all promising.

-Ekr