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

Peter Gutmann <pgut001@cs.auckland.ac.nz> Tue, 03 March 2009 15:39 UTC

Return-Path: <pgut001@cs.auckland.ac.nz>
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 A8A6C3A6452 for <saag@core3.amsl.com>; Tue, 3 Mar 2009 07:39:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.099
X-Spam-Level:
X-Spam-Status: No, score=-5.099 tagged_above=-999 required=5 tests=[AWL=-1.500, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 tSpusMk7Mk5P for <saag@core3.amsl.com>; Tue, 3 Mar 2009 07:39:54 -0800 (PST)
Received: from mailhost.auckland.ac.nz (curly.its.auckland.ac.nz [130.216.12.33]) by core3.amsl.com (Postfix) with ESMTP id D88EC3A6359 for <saag@ietf.org>; Tue, 3 Mar 2009 07:39:51 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id DFF9B9E803; Wed, 4 Mar 2009 04:40:17 +1300 (NZDT)
X-Virus-Scanned: by amavisd-new at mailhost.auckland.ac.nz
Received: from mailhost.auckland.ac.nz ([127.0.0.1]) by localhost (curly.its.auckland.ac.nz [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BWO1dc+8+lxR; Wed, 4 Mar 2009 04:40:17 +1300 (NZDT)
Received: from iris.cs.auckland.ac.nz (iris.cs.auckland.ac.nz [130.216.33.152]) by mailhost.auckland.ac.nz (Postfix) with ESMTP id A86A89E7EF; Wed, 4 Mar 2009 04:40:16 +1300 (NZDT)
Received: from wintermute01.cs.auckland.ac.nz (wintermute01.cs.auckland.ac.nz [130.216.34.38]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by iris.cs.auckland.ac.nz (Postfix) with ESMTP id 79D2A1DE4001; Wed, 4 Mar 2009 04:40:15 +1300 (NZDT)
Received: from pgut001 by wintermute01.cs.auckland.ac.nz with local (Exim 4.63) (envelope-from <pgut001@wintermute01.cs.auckland.ac.nz>) id 1LeWj9-0006nD-Ad; Wed, 04 Mar 2009 04:40:15 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Nicolas.Williams@sun.com, pgut001@cs.auckland.ac.nz
In-Reply-To: <20090302171646.GN9992@Sun.COM>
Message-Id: <E1LeWj9-0006nD-Ad@wintermute01.cs.auckland.ac.nz>
Sender: pgut001 <pgut001@cs.auckland.ac.nz>
Date: Wed, 04 Mar 2009 04:40:15 +1300
Cc: 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: Tue, 03 Mar 2009 15:39:54 -0000

Nicolas Williams <Nicolas.Williams@sun.com> writes:

>TLS-PSK is not sufficient by itself, and for two reasons:
>
>a) As the RFC says: "[h]owever, this document is not intended for web
>   password authentication, but rather for other uses of TLS."

That was added as a sop to the "<whine>we already have PKI in all its infinite
perfection and splendor, why provide an alternative?</whine>" crowd.

>Thus there is nothing about how to derive PSKs from passwords.

Yeah, my fault, I've had an RFC draft prepared but not quite posted yet for
ages.

>b) For any solution to scale that adds mutual authentication we'll need
>either the user to use the same password for all identities or federation.

Huh?  Where did this requirement come from?  You need neither of those two.

Peter.