Re: [secdir] secdir review of draft-kuegler-ipsecme-pace-ikev2

Nico Williams <nico@cryptonector.com> Thu, 14 April 2011 16:57 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: secdir@ietfc.amsl.com
Delivered-To: secdir@ietfc.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfc.amsl.com (Postfix) with ESMTP id AC7C1E08E7 for <secdir@ietfc.amsl.com>; Thu, 14 Apr 2011 09:57:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.851
X-Spam-Level:
X-Spam-Status: No, score=-1.851 tagged_above=-999 required=5 tests=[AWL=0.126, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([208.66.40.236]) by localhost (ietfc.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xsUwq9hugu+G for <secdir@ietfc.amsl.com>; Thu, 14 Apr 2011 09:57:51 -0700 (PDT)
Received: from homiemail-a24.g.dreamhost.com (caiajhbdcaid.dreamhost.com [208.97.132.83]) by ietfc.amsl.com (Postfix) with ESMTP id EDD60E0718 for <secdir@ietf.org>; Thu, 14 Apr 2011 09:57:50 -0700 (PDT)
Received: from homiemail-a24.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTP id 255F22C807A for <secdir@ietf.org>; Thu, 14 Apr 2011 09:57:50 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=d+MN34JYLm8IiX7GXfGmr sjKHonj9uufidjLGdiFr3iinz0FhlyF9jPUpeSs35x+TUzc/EW8fmHCL7YG71j22 mNO9yIIvPqXHag488xBcyD5KwF1VGFSHY1RW6CEjA08hOSyQioK1PDg2YQjoCKG5 NAnInP4XNYiiYsDvFbl0HQ=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=K4Gnb2jYffrGHBY7K7zq ca7bqIU=; b=h2QwY2kecCk7uE+S9D48T7EMqzaPlN7cdA84vetbOPYAAJrwRR3+ g1ZM+xwRsvMNKfEt738k69WN/A9j/fiPeejbrIq0fxzNDrIXO3T4HT6gmlTT40UO f9gR+QW1ixVz5+vAKJxjXhub64KWMy1BMRyrZxUceSqJJ0JLAIHsz3w=
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTPSA id EDBC82C806C for <secdir@ietf.org>; Thu, 14 Apr 2011 09:57:49 -0700 (PDT)
Received: by vws12 with SMTP id 12so1844021vws.31 for <secdir@ietf.org>; Thu, 14 Apr 2011 09:57:49 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.73.130 with SMTP id l2mr1500353vdv.14.1302800269317; Thu, 14 Apr 2011 09:57:49 -0700 (PDT)
Received: by 10.52.163.228 with HTTP; Thu, 14 Apr 2011 09:57:49 -0700 (PDT)
In-Reply-To: <4DA72605.10506@gmail.com>
References: <AC6674AB7BC78549BB231821ABF7A9AEB530189991@EMBX01-WF.jnpr.net> <4DA69C8A.7000305@gmail.com> <BANLkTi=3WCvUgtLdNknDog--UniYM1G9Bg@mail.gmail.com> <4DA72605.10506@gmail.com>
Date: Thu, 14 Apr 2011 11:57:49 -0500
Message-ID: <BANLkTikXF=S3NugNBErZZGLngyCECh=jTw@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Yaron Sheffer <yaronf.ietf@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Cc: "draft-kuegler-ipsecme-pace-ikev2@tools.ietf.org" <draft-kuegler-ipsecme-pace-ikev2@tools.ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Subject: Re: [secdir] secdir review of draft-kuegler-ipsecme-pace-ikev2
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2011 16:57:51 -0000

On Thu, Apr 14, 2011 at 11:51 AM, Yaron Sheffer <yaronf.ietf@gmail.com> wrote:
> I'm amazed at the comparison of PACE with SCRAM. In a previous mail you
> pointed out yourself that SCRAM is vulnerable to on-the-wire dictionary
> attacks, which PACE is not. The IETF had never managed to standardize any
> ZKPP methods until just recently (with the exception of TLS-SRP), and
> finally we're doing something about it, even if on the Experimental track. I
> believe this counts as a positive contribution to the security of the
> Internet.

This betrays a fundamental misunderstanding of SCRAM and channel binding.

SCRAM with channel binding to a secure channel is as secure as PACE,
and arguably more so.

If you do not understand what I just wrote then you need to read RFCs
5056, 5929, and 5802 -- in that order.

> I agree that salting the stored password (SPwd) would have improved the
> security of this protocol (unlike iteration counts). And it can be added
> with no extra round trips, since it's not "negotiated", just sent by the
> responder. My coauthor and I need to consider the benefits vs. costs, since
> the major use case here is not open servers, more often it would be VPN
> gateways.

Salting with a username requires no negotiation, but then you can't
rename users without also changing their passwords (a minor issue).

Nico
--