Re: [apps-discuss] [kitten] [saag] HTTP authentication: the next generation

Nicolas Williams <Nicolas.Williams@oracle.com> Mon, 13 December 2010 23:18 UTC

Return-Path: <Nicolas.Williams@oracle.com>
X-Original-To: apps-discuss@core3.amsl.com
Delivered-To: apps-discuss@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 048B53A6E08; Mon, 13 Dec 2010 15:18:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.54
X-Spam-Level:
X-Spam-Status: No, score=-6.54 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, UNPARSEABLE_RELAY=0.001]
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 6sxbTWuIL3ji; Mon, 13 Dec 2010 15:18:45 -0800 (PST)
Received: from rcsinet10.oracle.com (rcsinet10.oracle.com [148.87.113.121]) by core3.amsl.com (Postfix) with ESMTP id E7FC23A6D4A; Mon, 13 Dec 2010 15:18:44 -0800 (PST)
Received: from acsinet15.oracle.com (acsinet15.oracle.com [141.146.126.227]) by rcsinet10.oracle.com (Switch-3.4.2/Switch-3.4.2) with ESMTP id oBDNK9sd024453 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 13 Dec 2010 23:20:10 GMT
Received: from acsmt355.oracle.com (acsmt355.oracle.com [141.146.40.155]) by acsinet15.oracle.com (Switch-3.4.2/Switch-3.4.1) with ESMTP id oBDNDrdP001633; Mon, 13 Dec 2010 23:20:05 GMT
Received: from abhmt005.oracle.com by acsmt355.oracle.com with ESMTP id 870947501292282318; Mon, 13 Dec 2010 15:18:38 -0800
Received: from oracle.com (/10.135.188.51) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 13 Dec 2010 15:18:37 -0800
Date: Mon, 13 Dec 2010 17:18:36 -0600
From: Nicolas Williams <Nicolas.Williams@oracle.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Message-ID: <20101213231836.GC1091@oracle.com>
References: <4D02AF81.6000907@stpeter.im> <p06240809c928635499e8@[10.20.30.150]> <ADDEC353-8DE6-408C-BC75-A50B795E2F6C@checkpoint.com> <78BD0B98-0F20-478B-85F1-DBB45691EB0D@padl.com> <4D0479E3.4050508@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4D0479E3.4050508@gmail.com>
User-Agent: Mutt/1.5.20 (2010-03-02)
X-Mailman-Approved-At: Tue, 14 Dec 2010 08:58:53 -0800
Cc: "apps-discuss@ietf.org" <apps-discuss@ietf.org>, "pgut001@cs.auckland.ac.nz" <pgut001@cs.auckland.ac.nz>, Yoav Nir <ynir@checkpoint.com>, websec <websec@ietf.org>, Paul Hoffman <paul.hoffman@vpnc.org>, "kitten@ietf.org" <kitten@ietf.org>, "http-auth@ietf.org" <http-auth@ietf.org>, Luke Howard <lukeh@padl.com>, "saag@ietf.org" <saag@ietf.org>, Hannes Tschofenig <Hannes.Tschofenig@gmx.net>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
Subject: Re: [apps-discuss] [kitten] [saag] HTTP authentication: the next generation
X-BeenThere: apps-discuss@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: General discussion of application-layer protocols <apps-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/apps-discuss>
List-Post: <mailto:apps-discuss@ietf.org>
List-Help: <mailto:apps-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apps-discuss>, <mailto:apps-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Dec 2010 23:18:46 -0000

On Sun, Dec 12, 2010 at 09:29:39AM +0200, Yaron Sheffer wrote:
> I am not a big fan of EAP myself (although I am a co-author on
> Yoav's TLS-EAP), but no, for pragmatic reasons SASL is not the moral
> equivalent.
> 
> There is a number of EAP methods that provide zero-knowledge
> password based mutual authentication (i.e. password based auth
> that's *not* susceptible to dictionary attacks). These include (see http://www.iana.org/assignments/eap-numbers/eap-numbers.xml#eap-numbers-3):
> EAP-SRP-SHA1, EAP-pwd, EAP-EKE and EAP-SPEKE.

You missed the ABFAB thing...  ABFAB WG is producing [drumroll please] a
GSS-API mechanism that uses EAP.  And SASL can use GSS mechanisms (via
"GS2" [RFC5801]).

So, I believe that the answer is "yes".

Nico
--