
From owner-ietf-sasl@mail.imc.org  Tue Jun  2 22:25:05 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2002E28C142 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue,  2 Jun 2009 22:25:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[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 W1fJ4imr92p0 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue,  2 Jun 2009 22:25:03 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id CE3F13A6909 for <sasl-archive-Zoh8yoh9@ietf.org>; Tue,  2 Jun 2009 22:23:47 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n535Hiqm074160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jun 2009 22:17:44 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n535HicH074159; Tue, 2 Jun 2009 22:17:44 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n535HWC2074150 for <ietf-sasl@imc.org>; Tue, 2 Jun 2009 22:17:42 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n535HVGp005934 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 05:17:32 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n535HVJR037544 for <ietf-sasl@imc.org>; Tue, 2 Jun 2009 23:17:31 -0600 (MDT)
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 n5357c1J026281; Wed, 3 Jun 2009 00:07:38 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5357WYv026280; Wed, 3 Jun 2009 00:07:32 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 3 Jun 2009 00:07:32 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090603050732.GA22446@Sun.COM>
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <878wkfu5ih.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Fri, May 29, 2009 at 08:29:42PM +0200, Simon Josefsson wrote:
>                         ...  The changes can be summarized into:
> 
> 1) Add text to say that with 'p' one cb type name is included (normally
> tls-unique)
> 
> 2) Add text to say that with 'y' a list of cb type names supported by
> the client is included

There is a slightly better way that would simplify the client: define
new GS2 CB flags to go with the 'n', 'y', and 'p' that we have now
(which would stay as they have been, w/o any additional GS2 header
fields).  The three flags we have now:

 - 'n' (client can't do CB)
 - 'y' (client can only do tls-unique but thinks the server can't do CB)
 - 'p' (client used CB of the default type)

plus two new ones that today's servers would have to understand but
today's clients wouldn't have to:

 - 'Y' and a list of CB types in GS2 header (client can do CB and CB
   type negotiation and thinks the server advertives the given, possibly
   empty list of CB types)

 - 'P' and a single CB type in GS2 header (client used CB of the given
   type)

This way the server needs to know about the new bits in GS2 for future
downgrade protection in the face of CB type nego, but the client doesn't
have to know anything at all about future CB type nego.

Simplifying the client strikes me as a good thing.

Nico
-- 


From owner-ietf-sasl@mail.imc.org  Tue Jun  2 22:34:41 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D30C03A6A51 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue,  2 Jun 2009 22:34:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 8lSD+YYF0xJY for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue,  2 Jun 2009 22:34:41 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id ABA313A6891 for <sasl-archive-Zoh8yoh9@ietf.org>; Tue,  2 Jun 2009 22:34:40 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n535W3jj074894 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jun 2009 22:32:03 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n535W3M0074893; Tue, 2 Jun 2009 22:32:03 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n535Vo6i074881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Tue, 2 Jun 2009 22:32:02 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (c80-216-29-127.bredband.comhem.se [80.216.29.127]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n535VjdI019536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 3 Jun 2009 07:31:48 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090603:nicolas.williams@sun.com::HjKGMKrcrINml8CB:2dzR
X-Hashcash: 1:22:090603:alexey.melnikov@isode.com::2sxvuI2rI0zTyjeH:AGOn
X-Hashcash: 1:22:090603:ietf-sasl@imc.org::VJigFXs2vHUEGqZ1:0S81i
Date: Wed, 03 Jun 2009 07:31:45 +0200
In-Reply-To: <20090603050732.GA22446@Sun.COM> (Nicolas Williams's message of "Wed, 3 Jun 2009 00:07:32 -0500")
Message-ID: <8763fdnari.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

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

> On Fri, May 29, 2009 at 08:29:42PM +0200, Simon Josefsson wrote:
>>                         ...  The changes can be summarized into:
>> 
>> 1) Add text to say that with 'p' one cb type name is included (normally
>> tls-unique)
>> 
>> 2) Add text to say that with 'y' a list of cb type names supported by
>> the client is included
>
> There is a slightly better way that would simplify the client: define
> new GS2 CB flags to go with the 'n', 'y', and 'p' that we have now
> (which would stay as they have been, w/o any additional GS2 header
> fields).  The three flags we have now:
>
>  - 'n' (client can't do CB)
>  - 'y' (client can only do tls-unique but thinks the server can't do CB)
>  - 'p' (client used CB of the default type)
>
> plus two new ones that today's servers would have to understand but
> today's clients wouldn't have to:
>
>  - 'Y' and a list of CB types in GS2 header (client can do CB and CB
>    type negotiation and thinks the server advertives the given, possibly
>    empty list of CB types)
>
>  - 'P' and a single CB type in GS2 header (client used CB of the given
>    type)
>
> This way the server needs to know about the new bits in GS2 for future
> downgrade protection in the face of CB type nego, but the client doesn't
> have to know anything at all about future CB type nego.
>
> Simplifying the client strikes me as a good thing.

It adds more text to the specification, and some complexity, but it
seems like a reasonable compromise to simplify client implementations.

Before I update GS2 with that, what is the chance of making these
changes to SCRAM?  Alexey?

/Simon


From owner-ietf-sasl@mail.imc.org  Wed Jun  3 06:42:38 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D95103A6F22 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Wed,  3 Jun 2009 06:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[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 ab6uol4Szcbh for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Wed,  3 Jun 2009 06:42:38 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id BE1003A6CAD for <sasl-archive-Zoh8yoh9@ietf.org>; Wed,  3 Jun 2009 06:42:37 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n53DckVx025664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Jun 2009 06:38:46 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n53Dckg1025663; Wed, 3 Jun 2009 06:38:46 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from sca-ea-mail-1.sun.com (sca-ea-mail-1.Sun.COM [192.18.43.24]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n53DcY4l025647 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 06:38:45 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n53DcYS3008974 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 13:38:34 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n53DcXLH029530 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 07:38:34 -0600 (MDT)
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 n53DSe49026732; Wed, 3 Jun 2009 08:28:40 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n53DSbsP026731; Wed, 3 Jun 2009 08:28:37 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 3 Jun 2009 08:28:37 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090603132837.GA26728@Sun.COM>
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8763fdnari.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Wed, Jun 03, 2009 at 07:31:45AM +0200, Simon Josefsson wrote:
> Nicolas Williams <Nicolas.Williams@sun.com> writes:
> > There is a slightly better way that would simplify the client: define
> > new GS2 CB flags to go with the 'n', 'y', and 'p' that we have now
> > (which would stay as they have been, w/o any additional GS2 header
> > fields).  The three flags we have now:
> >
> > ...
> >
> > Simplifying the client strikes me as a good thing.
> 
> It adds more text to the specification, and some complexity, but it
> seems like a reasonable compromise to simplify client implementations.

It does add more text to the spec, but server-side complexity is not
really changed, and the client is simplified.  I'm OK with either plan,
though I think I prefer this one.

> Before I update GS2 with that, what is the chance of making these
> changes to SCRAM?  Alexey?

We'll know soon enough.  The poll ends this week.

Nico
-- 


From owner-ietf-sasl@mail.imc.org  Wed Jun  3 12:31:38 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AA99A3A6E01 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Wed,  3 Jun 2009 12:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[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 RDglVA8KVOFZ for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Wed,  3 Jun 2009 12:31:37 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 3E7073A6D0E for <sasl-archive-Zoh8yoh9@ietf.org>; Wed,  3 Jun 2009 12:31:35 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n53InKmg061528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Jun 2009 11:49:20 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n53InKwI061527; Wed, 3 Jun 2009 11:49:20 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n53In9dg061513 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 11:49:19 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n53In8V5027878 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 18:49:08 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n53In8VE017883 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 12:49:08 -0600 (MDT)
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 n53IdFas001870; Wed, 3 Jun 2009 13:39:15 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n53IdE4O001869; Wed, 3 Jun 2009 13:39:14 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 3 Jun 2009 13:39:14 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090603183914.GB1480@Sun.COM>
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org> <20090603132837.GA26728@Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090603132837.GA26728@Sun.COM>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Huh, I think we can do something far simpler still: just add enough ABNF
to define non-critical GS2 header extensions.  (That's what I get for
posting late at night instead of sleeping on the idea.)

;; Non-critical GS2 extension headers; servers MUST ignore if they don't
;; understand them
gs2-ext-attr     = "gs2-" 1*ALPHA
gs2-ext-attr-val = gs2-ext-attr "=" value
gs2-ext-attrs    = gs2-ext-attr-val *("," gs2-ext-attr-val)

;; GS2 header
gs2-cbind-flag   = "n" / "y" / "p"
gs2-header       = gs2-cbind-flag [ authzid ] "," [ gs2-ext-attrs "," ]
                                                  ^^^^^^^^^^^^^^^^^^^^^

Or something like that.  (One might prefer something slightly different
that makes it easier to find the end of the GS2 header.)

So today SCRAM/GS2 would be essentially unmodified from what we had
going into this poll.  Later, when we add CB type negotiation we can add
an attribute for listing the CB types that the client saw in the 'y' and
'p' cases, and an attribute for specifying the CB type chosen by the
client in the 'p' case.

(And if we really wanted to we could add critical GS2 header extensions,
which, if present, cause the server to reply with an error if the server
doesn't understand the extension, else with a normal GSS context token
prefixed with a small header to distinguish from such errors.  Then even
Kurt's multi-level negotiation scheme could be added.)

Nico
-- 


From owner-ietf-sasl@mail.imc.org  Thu Jun  4 01:12:58 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 159E03A6B4D for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu,  4 Jun 2009 01:12:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 gfIpuE-9yo2r for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu,  4 Jun 2009 01:12:57 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id DCCC63A68E3 for <sasl-archive-Zoh8yoh9@ietf.org>; Thu,  4 Jun 2009 01:12:56 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5488bf7024535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Jun 2009 01:08:37 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5488bOJ024534; Thu, 4 Jun 2009 01:08:37 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5488Nlk024499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Thu, 4 Jun 2009 01:08:36 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (c80-216-29-127.bredband.comhem.se [80.216.29.127]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n5488J3e021546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 4 Jun 2009 10:08:21 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org> <20090603132837.GA26728@Sun.COM> <20090603183914.GB1480@Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090604:ietf-sasl@imc.org::RwEI6D0zbZ6rYoIz:9k5V
X-Hashcash: 1:22:090604:nicolas.williams@sun.com::FeS/WVEbZBhdl/it:TZoF
X-Hashcash: 1:22:090604:alexey.melnikov@isode.com::j2EUXzcsBgbfygiq:0JC7D
Date: Thu, 04 Jun 2009 10:08:19 +0200
Message-ID: <87ws7ss9os.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

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

> Huh, I think we can do something far simpler still: just add enough ABNF
> to define non-critical GS2 header extensions.  (That's what I get for
> posting late at night instead of sleeping on the idea.)
>
> ;; Non-critical GS2 extension headers; servers MUST ignore if they don't
> ;; understand them
> gs2-ext-attr     = "gs2-" 1*ALPHA
> gs2-ext-attr-val = gs2-ext-attr "=" value
> gs2-ext-attrs    = gs2-ext-attr-val *("," gs2-ext-attr-val)
>
> ;; GS2 header
> gs2-cbind-flag   = "n" / "y" / "p"
> gs2-header       = gs2-cbind-flag [ authzid ] "," [ gs2-ext-attrs "," ]
>                                                   ^^^^^^^^^^^^^^^^^^^^^
>
> Or something like that.  (One might prefer something slightly different
> that makes it easier to find the end of the GS2 header.)

Right, you need a reliable way to identify the end of the gs2-header.  I
also dislike the complexity in a parser that always will have to ignore
any number of gs2-* parameters, so how about this instead:

string     = 1*(UTF8-char-safe / "=2C" / "=3D")
gs2-authzid  = "a=" string
gs2-cbind-flag   = "n" / "y" / "p"
gs2-nonstd-flag = "F"
gs2-header       = [gs2-nonstd-flag "," ] gs2-cbind-flag "," [ gs2-authzid ] "," [ "gs2-ext" "=" string ] ","

Servers that doesn't understand a gs2-ext token MUST fail
authentication.

Having thought about this proposal (briefly), I don't think an extension
idea is a good idea.  What you propose is an extension mechanism inside
a SASL mechanism.  I have a fairly strong general preference against
that -- SASL is an extensible protocol, and the way to negotiate
extensions is to specify a new SASL mechanism name and have clients
prefer that mechanism.  The new mechanism can be a cut'n'paste of the
old mechanism, plus some new wording.  I don't see a need for an
extension mechanism inside GS2 here?

So, my preferences are:

1) GS2 -13 but remove tls-server-end-point and only support tls-unique.

2) GS2 -13 plus the changes I proposed earlier to send a list of channel
binding types.  This allows tls-server-end-point to work if there is
someone that is willing to do the work (specify an outer negotiation
protocol) for that.

3/4) GS2 -13.
3/4) GS2 plus your Y/P proposal.
  Not sure how to rate these two against each other.  The Y/P scheme is
  close to an extension scheme.

5) GS2 plus the above extension scheme.

/Simon


From owner-ietf-sasl@mail.imc.org  Thu Jun  4 09:10:39 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 80D8F3A683D for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu,  4 Jun 2009 09:10:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.046
X-Spam-Level: 
X-Spam-Status: No, score=-6.046 tagged_above=-999 required=5 tests=[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 c69qMsmsCtJa for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu,  4 Jun 2009 09:10:38 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 409E23A6B04 for <sasl-archive-Zoh8yoh9@ietf.org>; Thu,  4 Jun 2009 09:10:38 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n54Frtrs058957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Jun 2009 08:53:55 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n54Frt9l058956; Thu, 4 Jun 2009 08:53:55 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n54FrhIT058941 for <ietf-sasl@imc.org>; Thu, 4 Jun 2009 08:53:53 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n54FrgDH003671 for <ietf-sasl@imc.org>; Thu, 4 Jun 2009 15:53:43 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n54FrgcE020698 for <ietf-sasl@imc.org>; Thu, 4 Jun 2009 09:53:42 -0600 (MDT)
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 n54Fhfo1002132; Thu, 4 Jun 2009 10:43:41 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n54Fhe8R002131; Thu, 4 Jun 2009 10:43:41 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Thu, 4 Jun 2009 10:43:40 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090604154340.GN1049@Sun.COM>
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org> <20090603132837.GA26728@Sun.COM> <20090603183914.GB1480@Sun.COM> <87ws7ss9os.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87ws7ss9os.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Thu, Jun 04, 2009 at 10:08:19AM +0200, Simon Josefsson wrote:
> Nicolas Williams <Nicolas.Williams@sun.com> writes:
> > gs2-header       = gs2-cbind-flag [ authzid ] "," [ gs2-ext-attrs "," ]
> >                                                   ^^^^^^^^^^^^^^^^^^^^^
> > Or something like that.  (One might prefer something slightly different
> > that makes it easier to find the end of the GS2 header.)
> 
> Right, you need a reliable way to identify the end of the gs2-header.  I
> also dislike the complexity in a parser that always will have to ignore
> any number of gs2-* parameters, so how about this instead:
> 
> string     = 1*(UTF8-char-safe / "=2C" / "=3D")
> gs2-authzid  = "a=" string
> gs2-cbind-flag   = "n" / "y" / "p"
> gs2-nonstd-flag = "F"
> gs2-header       = [gs2-nonstd-flag "," ] gs2-cbind-flag "," [ gs2-authzid ] "," [ "gs2-ext" "=" string ] ","
> 
> Servers that doesn't understand a gs2-ext token MUST fail
> authentication.

The extension doesn't have to be critical to do what we want it to.
More importantly, we don't have an error message defiedn so any failure
could only be communicated through the SASL outcome of authentication
message, and that need not provide machine-readable mechanism-specific
information, so the mechanism on the client can't use any failure
information for, say, Kurt's multi-level negotiation proposal (though I
am not sure that he meant that seriously -- I certainly don't take it
seriously).

So I think "MUST ignore unknown" is good enough.

> Having thought about this proposal (briefly), I don't think an extension
> idea is a good idea.  What you propose is an extension mechanism inside
> a SASL mechanism.  I have a fairly strong general preference against
> that -- SASL is an extensible protocol, and the way to negotiate
> extensions is to specify a new SASL mechanism name and have clients
> prefer that mechanism.  The new mechanism can be a cut'n'paste of the
> old mechanism, plus some new wording.  I don't see a need for an
> extension mechanism inside GS2 here?

This is not an extension in that sense -- we're not negotiating new
features.  We're merely providing future downgrade protection against a
future negotiation that could be done via SASL mech name nego.


From owner-ietf-sasl@mail.imc.org  Fri Jun  5 13:36:01 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 546803A6AC1 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 13:36:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level: 
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=-0.241, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 C8cX4Kui29-v for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 13:35:59 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 93BB83A67F6 for <sasl-archive-Zoh8yoh9@ietf.org>; Fri,  5 Jun 2009 13:35:58 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55KVdk0053194 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 13:31:39 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55KVdUK053193; Fri, 5 Jun 2009 13:31:39 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55KVR0H053186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 13:31:38 -0700 (MST) (envelope-from hartmans@mit.edu)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E790C4141; Fri,  5 Jun 2009 16:31:24 -0400 (EDT)
To: ietf-sasl@imc.org
Subject: GS2 and SCRAM channel bindings
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 05 Jun 2009 16:31:24 -0400
Message-ID: <tslr5xytobn.fsf@mit.edu>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Hi.  I believe I've read enough of the mail and swapped in enough
state to have an informed opinion on the current channel bindings
discussions.

I believe that gs2 and scram should specify TLS unique channel
bindings as mandatory to implement when TLS channel bindings are used.

I believe that what we standardize today needs to support other
channel binding types besides tls-unique.  I'm not particularly
concerned with tls-server-endpoint although I believe we should keep
options open for that.  I believe that GS2 may be used in environments
where the channel type is not TLS, so the standard needs to support
that.  I cannot support publication of a GS2 or SCRAM standard that is
limited to TLS channel binding.

I'm dubious that we will ever need TLS channel binding negotiation, or
that if we do that it should happen in SASL rather than TLS.  In most
cases I think that the application will know what channel will be used
before SASL starts.  I've heard Kurt's arguments that we want to
negotiate channel binding type and allow a server to have SASL
mechanism selection influence channel binding type selection.  I do
not find these arguments compelling.



As such, I support a proposal where we carry the type of the channel
to be bound in GS2/SCRAM.  I'm fine carrying that all the time; I'm
fine carrying that only when it is not tls-unique.

I think it would be a good idea to have a way to carry additional
channel types without needing to generate new GS2 mechanisms.  I'm
happy with non-critical extensions at the GS2 layer as a way to do
that.  While I prefer having this option, I could support publication
of GS2/SCRAM that did not support additional channel binding types
being carried.

I'm reasonably happy with all the ABNF thrown around on the list that
is consistent with my goals.


From owner-ietf-sasl@mail.imc.org  Fri Jun  5 14:50:03 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id A569E3A697C for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 14:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 S2sldFz5Xi-l for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 14:50:02 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 611CD3A68D1 for <sasl-archive-Zoh8yoh9@ietf.org>; Fri,  5 Jun 2009 14:50:02 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55Ll6ZF056891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:47:06 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55Ll6On056890; Fri, 5 Jun 2009 14:47:06 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LksW1056875 for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 14:47:05 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [94.197.221.233] (94.197.221.233.threembb.co.uk [94.197.221.233])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SimSSgAh5GSc@rufus.isode.com>; Fri, 5 Jun 2009 22:46:52 +0100
Message-ID: <4A299227.6040802@isode.com>
Date: Fri, 05 Jun 2009 22:46:15 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Nicolas Williams <Nicolas.Williams@sun.com>
CC: Simon Josefsson <simon@josefsson.org>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090529202232.GT29258@Sun.COM>
In-Reply-To: <20090529202232.GT29258@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams wrote:

>On Fri, May 29, 2009 at 08:29:42PM +0200, Simon Josefsson wrote:
>  
>
 [...]

>>Check the examples, they are updated and hopefully give you a quick idea
>>of how the protocol will look like.
>>
>>Thoughts?
>>    
>>
>Awesome.  Thanks!
>
>Alexey, can you adapt Simon's changes to GS2 to SCRAM?
>  
>
Yes, your proposal seems fine to me. (I might have some minor comments 
later).


From owner-ietf-sasl@mail.imc.org  Fri Jun  5 14:54:14 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C6B0E3A67E3 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 14:54:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 v+BLcfbJFcdI for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 14:54:14 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id AFC2C3A676A for <sasl-archive-Zoh8yoh9@ietf.org>; Fri,  5 Jun 2009 14:54:13 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55Lq3g9057039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:52:03 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55Lq3IU057038; Fri, 5 Jun 2009 14:52:03 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55Lq2vN057032 for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 14:52:03 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [94.197.221.233] (94.197.221.233.threembb.co.uk [94.197.221.233])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SimTfwAh5G-5@rufus.isode.com>; Fri, 5 Jun 2009 22:52:01 +0100
Message-ID: <4A29935F.1050200@isode.com>
Date: Fri, 05 Jun 2009 22:51:27 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Simon Josefsson <simon@josefsson.org>
CC: Nicolas Williams <Nicolas.Williams@sun.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090529202232.GT29258@Sun.COM> <874ov3tyl6.fsf@mocca.josefsson.org>
In-Reply-To: <874ov3tyl6.fsf@mocca.josefsson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Simon Josefsson wrote:

>Nicolas Williams <Nicolas.Williams@sun.com> writes:
>  
>
>>On Fri, May 29, 2009 at 08:29:42PM +0200, Simon Josefsson wrote:
>>    
>>
>>>Nicolas Williams <Nicolas.Williams@sun.com> writes:
>>>      
>>>
 [...]

>>Also, I like your ABNF.  I had in mind using something like t=<type> and
>>t=<type>[:<type>[:...]], but your approach strikes me as better.
>>    
>>
>I'm glad you like it.  I'm not entirely happy with it: you can't parse
>it using a var[=value] parser, you need to inspect the string character
>by character in the beginning.  One alternative would be (compare with
>the examples in the document):
>
>Example #1: n,a=someuser,...
>Example #2: n,...
>Example #3: F,n,...
>  
>
I think we need comma after "n" (for consistency and ease of parsing) 
and we don't need a comma after F.

>Example #4: p=tls-unique,a=someuser,...
>Example #5: p=tls-unique,...
>Example #6: p=tls-server-end-point,...
>Example #7: y=tls-unique:tls-server-end-point,a=someuser,...
>
>However I didn't want to make unrelated changes at this point.
>
>Also, that SCRAM uses var[=value] doesn't mean GS2 needs to.
>
>I'm not sure.
>
>Thoughts?
>  
>


From owner-ietf-sasl@mail.imc.org  Fri Jun  5 14:57:11 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F5643A6894 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 14:57:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.299
X-Spam-Level: 
X-Spam-Status: No, score=-2.299 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, J_CHICKENPOX_17=0.6]
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 1EucADhq-AzE for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 14:57:10 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id F11083A685B for <sasl-archive-Zoh8yoh9@ietf.org>; Fri,  5 Jun 2009 14:57:09 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LsDb5057096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:54:13 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55LsDX2057095; Fri, 5 Jun 2009 14:54:13 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LsCXm057089 for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 14:54:12 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [94.197.221.233] (94.197.221.233.threembb.co.uk [94.197.221.233])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SimUAAAh5FHF@rufus.isode.com>; Fri, 5 Jun 2009 22:54:10 +0100
Message-ID: <4A2993DD.1010005@isode.com>
Date: Fri, 05 Jun 2009 22:53:33 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Jeffrey Hutzelman <jhutz@cmu.edu>
CC: Simon Josefsson <simon@josefsson.org>, Nicolas Williams <Nicolas.Williams@sun.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090529202232.GT29258@Sun.COM> <874ov3tyl6.fsf@mocca.josefsson.org> <DC91912DC3C8FC8317B3C150@atlantis.pc.cs.cmu.edu>
In-Reply-To: <DC91912DC3C8FC8317B3C150@atlantis.pc.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Jeffrey Hutzelman wrote:

> --On Friday, May 29, 2009 10:59:17 PM +0200 Simon Josefsson 
> <simon@josefsson.org> wrote:

 [...]

>> I'm glad you like it.  I'm not entirely happy with it: you can't parse
>> it using a var[=value] parser, you need to inspect the string character
>> by character in the beginning.  One alternative would be (compare with
>> the examples in the document):
>
> I see a couple of problems with the grammar.  One is that in the 'p' 
> and 'y' cases, you get two consecutive commas if there is no authzid.

-1. I think it would be better to use 2 commas, because this is a sure 
sign that the GS2 header has ended.

> The other is that in the 'n' case, you get no comma before the 
> authzid, if there is one.

+1.

> I think it would be better to always have a comma after the [pny] 
> field, and another after the a=authzid iff it is present.
>
> I have no objection to the [py]= syntax you suggest; that might make 
> parsing easier, and we're changing the format of that field anyway.
>
> I see no reason to include a comma after the 'F' prefix.

+1.


From owner-ietf-sasl@mail.imc.org  Fri Jun  5 14:59:34 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F4393A6894 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 14:59:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.569
X-Spam-Level: 
X-Spam-Status: No, score=-2.569 tagged_above=-999 required=5 tests=[AWL=0.030, 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 WsaQl82p+YqE for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri,  5 Jun 2009 14:59:33 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id E743E3A67E3 for <sasl-archive-Zoh8yoh9@ietf.org>; Fri,  5 Jun 2009 14:59:32 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LvG66057231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:57:16 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55LvGYV057230; Fri, 5 Jun 2009 14:57:16 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LvF5u057224 for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 14:57:16 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [94.197.221.233] (94.197.221.233.threembb.co.uk [94.197.221.233])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SimUuAAh5Lzp@rufus.isode.com>; Fri, 5 Jun 2009 22:57:14 +0100
Message-ID: <4A299498.8020703@isode.com>
Date: Fri, 05 Jun 2009 22:56:40 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Simon Josefsson <simon@josefsson.org>
CC: Nicolas Williams <Nicolas.Williams@sun.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org> <20090603132837.GA26728@Sun.COM>
In-Reply-To: <20090603132837.GA26728@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams wrote:

>On Wed, Jun 03, 2009 at 07:31:45AM +0200, Simon Josefsson wrote:
>  
>
>>Before I update GS2 with that, what is the chance of making these
>>changes to SCRAM?  Alexey?
>>    
>>
Simon, I suggest you do changes to GS2 (hopefully taking into 
consideration a couple of minor comments I've just sent out), then I 
copy them to SCRAM.
If I dislike something, I will complain :-)


From owner-ietf-sasl@mail.imc.org  Sun Jun  7 05:17:24 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 536513A68D6 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Sun,  7 Jun 2009 05:17:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.111
X-Spam-Level: 
X-Spam-Status: No, score=-4.111 tagged_above=-999 required=5 tests=[AWL=2.488, BAYES_00=-2.599, 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 fy0xDDqI4Zq9 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Sun,  7 Jun 2009 05:17:23 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 1B56C3A67E4 for <sasl-archive-Zoh8yoh9@ietf.org>; Sun,  7 Jun 2009 05:17:22 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n57CCZpP042104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Jun 2009 05:12:35 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n57CCZKR042103; Sun, 7 Jun 2009 05:12:35 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from boole.openldap.org (boole.openldap.org [204.152.186.50]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n57CCO2F042064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-sasl@imc.org>; Sun, 7 Jun 2009 05:12:35 -0700 (MST) (envelope-from Kurt.Zeilenga@Isode.com)
Received: from [192.168.1.102] (75-141-233-128.dhcp.nv.charter.com [75.141.233.128] (may be forged)) (authenticated bits=0) by boole.openldap.org (8.14.3/8.14.3) with ESMTP id n57CCKsh031194; Sun, 7 Jun 2009 12:12:21 GMT (envelope-from Kurt.Zeilenga@Isode.com)
Cc: SASL WG <ietf-sasl@imc.org>
Message-Id: <75FB32D2-2238-442D-A741-8DF1174970FF@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <4A1F06CF.80505@isode.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Date: Sun, 7 Jun 2009 05:12:20 -0700
References: <4A1F06CF.80505@isode.com>
X-Mailer: Apple Mail (2.935.3)
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

After some additional thought and consideration, I change my  
preference to:

4a (just change the text to require tls-unique)
5 (adds some words that additional text that channel bind type agility  
is provided via mechanism name).

I have decided not to support providing any channeling binding  
"downgrade" protection in the mechanism.  This because I believe the  
mechanism downgrade mechanism is sufficient to protect against attacks  
I think would be likely, and the suggested approaches not necessarily  
sufficient to cover attacks that might eventual come.   For instance,  
if we were to not only have a channel binding type negotiation  
facility (such as what Jeffrey proposed) but a Security Label  
negotiation facility, and maybe a hash algorithm negotiation facility,  
or maybe a combined "mechanism property" negotiation facility, I would  
want that negotiation facility to provide a downgrade protection.  Off  
hand, I cannot think of how to deal with downgrade now without  
discussing the particulars of the negotiation facility, so I rather  
defer this (and just hope we have enough extension capability in GS2/ 
SCRAM) to deal with such).

-- Kurt

On May 28, 2009, at 2:49 PM, Alexey Melnikov wrote:

>
> I've discussed channel bindings with Nico in jabber and we agreed  
> that we need to get WG consensus on how TLS channel bindings should  
> be used with SCRAM.
> Please provide an orded list of alternatives you find acceptable  
> from the choices listed below. (Please restrict discussions of  
> variants of these choices at the moment. I will do another poll on  
> such choices later, depending on the outcome of this poll. Also,  
> please read notes for the choices before answering). Please answer  
> the poll by the end of June 7th.
>
> 1). SCRAM should just use a single allowed TLS channel binding and  
> don't have any negotiation of other TLS channel bindings (*) (**)
> a). the default is tls-unique
> b). the default is tls-server-end-point
> 2). SCRAM should just use tls-server-end-point, fallback to tls- 
> unique, no negotiation of other TLS channel bindings (*)
> 3). SCRAM should always use channel binding negotiation (*)
> 4). SCRAM should have a default TLS channel binding with optional  
> negotiation of TLS channel bindings (*)
> a). the default is tls-unique
> b). the default is
> 5). I have another opinion [this is for the case when there is some  
> valid choice which you think should be considered by the WG]
>
> Notes:
> (*) - whether such negotiation happens inside or outside of SCRAM
> (**) - channel binding negotiation can be added later on
>


From owner-ietf-sasl@mail.imc.org  Mon Jun  8 07:25:32 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 74DF13A6AE6 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon,  8 Jun 2009 07:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level: 
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=-0.217, BAYES_00=-2.599, IP_NOT_FRIENDLY=0.334]
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 QDN543gZxq87 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon,  8 Jun 2009 07:25:31 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 2E0333A6878 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon,  8 Jun 2009 07:25:30 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n58ELqAF003737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jun 2009 07:21:52 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n58ELqcA003736; Mon, 8 Jun 2009 07:21:52 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n58ELfMC003726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-sasl@imc.org>; Mon, 8 Jun 2009 07:21:52 -0700 (MST) (envelope-from hartmans@mit.edu)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id F0FC74141; Mon,  8 Jun 2009 10:21:31 -0400 (EDT)
To: Kurt Zeilenga <Kurt.Zeilenga@isode.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <75FB32D2-2238-442D-A741-8DF1174970FF@Isode.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 08 Jun 2009 10:21:31 -0400
In-Reply-To: <75FB32D2-2238-442D-A741-8DF1174970FF@Isode.com> (Kurt Zeilenga's message of "Sun\, 7 Jun 2009 05\:12\:20 -0700")
Message-ID: <tsl8wk2rel0.fsf@mit.edu>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

>>>>> "Kurt" == Kurt Zeilenga <Kurt.Zeilenga@isode.com> writes:

    Kurt> After some additional thought and consideration, I change my
    Kurt> preference to:

    Kurt> 4a (just change the text to require tls-unique) 

As I indicate, I believe support for channel binding types other than
tls-unique is an absolute requirement.  While I prefer for us to have
downgrade protection, I don't see that as an absolute requirement.
So, I think we at least need a mechanism to say what channel binding
type we've used if it is not tls-unique.  That's not downgrade
protection; it is consistency with 5056.

    Kurt> 5 (adds some
    Kurt> words that additional text that channel bind type agility is
    Kurt> provided via mechanism name).

I'm fairly strongly against this option.


    Kurt> I have decided not to support providing any channeling
    Kurt> binding "downgrade" protection in the mechanism.  

As I indicated, I believe this would be a good idea, and would
certainly rather the WG consensus be that we had such a mechanism, but
understand if we don't go there.


From owner-ietf-sasl@mail.imc.org  Mon Jun  8 09:21:41 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6BA673A6B51 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon,  8 Jun 2009 09:21:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.027
X-Spam-Level: 
X-Spam-Status: No, score=-6.027 tagged_above=-999 required=5 tests=[AWL=0.019, 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 L8DD236mYqiV for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon,  8 Jun 2009 09:21:40 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 563773A68E5 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon,  8 Jun 2009 09:21:40 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n58GEB19009184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jun 2009 09:14:11 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n58GEB00009183; Mon, 8 Jun 2009 09:14:11 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from sca-ea-mail-2.sun.com (sca-ea-mail-2.Sun.COM [192.18.43.25]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n58GDuwl009162 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-sasl@imc.org>; Mon, 8 Jun 2009 09:14:07 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n58GDu1p008967 for <ietf-sasl@imc.org>; Mon, 8 Jun 2009 16:13:56 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 n58GDtB6018642 for <ietf-sasl@imc.org>; Mon, 8 Jun 2009 10:13:55 -0600 (MDT)
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 n58G3wAg004273; Mon, 8 Jun 2009 11:03:58 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n58G3vJ6004272; Mon, 8 Jun 2009 11:03:57 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 8 Jun 2009 11:03:57 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Cc: Kurt Zeilenga <Kurt.Zeilenga@isode.com>, Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090608160357.GX1049@Sun.COM>
References: <4A1F06CF.80505@isode.com> <75FB32D2-2238-442D-A741-8DF1174970FF@Isode.com> <tsl8wk2rel0.fsf@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <tsl8wk2rel0.fsf@mit.edu>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Mon, Jun 08, 2009 at 10:21:31AM -0400, Sam Hartman wrote:
>     Kurt> After some additional thought and consideration, I change my
>     Kurt> preference to:
> 
>     Kurt> 4a (just change the text to require tls-unique) 
> 
> As I indicate, I believe support for channel binding types other than
> tls-unique is an absolute requirement.  While I prefer for us to have
> downgrade protection, I don't see that as an absolute requirement.
> So, I think we at least need a mechanism to say what channel binding
> type we've used if it is not tls-unique.  That's not downgrade
> protection; it is consistency with 5056.

Technically we don't even need that much, but I'd very much like to have
at least that much.

I too think that future downgrade protection is not critical right now.
In fact, I can think of ways to do all three (or is it four?) proposed
future CB type nego schemes without adding downgrade protection now
(it's just that to me the security analysis seemed easier with explicit
downgrade protection).

Nico
-- 


From owner-ietf-sasl@mail.imc.org  Thu Jun 11 11:44:55 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 6A2A13A6C20 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu, 11 Jun 2009 11:44:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.734
X-Spam-Level: 
X-Spam-Status: No, score=-5.734 tagged_above=-999 required=5 tests=[AWL=0.312, 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 dBxIaie0yj2N for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu, 11 Jun 2009 11:44:53 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 5F5563A6B3D for <sasl-archive-Zoh8yoh9@ietf.org>; Thu, 11 Jun 2009 11:44:53 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5BIaLEF038579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Jun 2009 11:36:21 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5BIaLCM038578; Thu, 11 Jun 2009 11:36:21 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from sca-ea-mail-3.sun.com (sca-ea-mail-3.Sun.COM [192.18.43.21]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5BIaAiI038566 for <ietf-sasl@imc.org>; Thu, 11 Jun 2009 11:36:21 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5BIaA3S017360 for <ietf-sasl@imc.org>; Thu, 11 Jun 2009 18:36:10 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 n5BIaAeX046799 for <ietf-sasl@imc.org>; Thu, 11 Jun 2009 12:36:10 -0600 (MDT)
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 n5BIQAvZ006800 for <ietf-sasl@imc.org>; Thu, 11 Jun 2009 13:26:10 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5BIQ8ak006799 for ietf-sasl@imc.org; Thu, 11 Jun 2009 13:26:08 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Thu, 11 Jun 2009 13:26:08 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: ietf-sasl@imc.org
Subject: New version of draft-altman-tls-channel-bindings
Message-ID: <20090611182608.GU1049@Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

I've just posted draft-altman-tls-channel-bindings-04.  This version
re-submits the existing three TLS channel bindings types following
Larry's note to the IESG transferring "ownership" of his channel binding
types (Jeff will do so soon for his as well, I think).

References were added, applicability text (based, in part, on
discussions in this WG) and security considerations text was added, as
well as minor clarifications.

Please review.  Thanks,

Nico
-- 


From owner-ietf-sasl@mail.imc.org  Fri Jun 12 02:28:28 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DC2593A6C7F for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri, 12 Jun 2009 02:28:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.584
X-Spam-Level: 
X-Spam-Status: No, score=-2.584 tagged_above=-999 required=5 tests=[AWL=0.015, 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 9w12eH8eLoaP for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri, 12 Jun 2009 02:28:28 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id D103A3A6BEB for <sasl-archive-Zoh8yoh9@ietf.org>; Fri, 12 Jun 2009 02:28:27 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5C9NrEE083150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jun 2009 02:23:53 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5C9Nrpx083149; Fri, 12 Jun 2009 02:23:53 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5C9NddZ083137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Fri, 12 Jun 2009 02:23:51 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (c80-216-24-60.bredband.comhem.se [80.216.24.60]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n5C9NZfR000877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 12 Jun 2009 11:23:37 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: ietf-sasl@imc.org
Subject: Re: New version of draft-altman-tls-channel-bindings
References: <20090611182608.GU1049@Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090612:nicolas.williams@sun.com::7mmrQf4j2IhaUc/X:3JxV
X-Hashcash: 1:22:090612:ietf-sasl@imc.org::6Vdo2D/qY7fBTOhn:8KK2
Date: Fri, 12 Jun 2009 11:23:33 +0200
In-Reply-To: <20090611182608.GU1049@Sun.COM> (Nicolas Williams's message of "Thu, 11 Jun 2009 13:26:08 -0500")
Message-ID: <87ski5erfu.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

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

> I've just posted draft-altman-tls-channel-bindings-04.  This version
> re-submits the existing three TLS channel bindings types following
> Larry's note to the IESG transferring "ownership" of his channel binding
> types (Jeff will do so soon for his as well, I think).
>
> References were added, applicability text (based, in part, on
> discussions in this WG) and security considerations text was added, as
> well as minor clarifications.
>
> Please review.  Thanks,

The registration sections 3-5 looks fine to me.

I have two mild concerns on section 6 and 7:

Section 6 mandate rather general restrictions on application protocol
specifications that appear to apply beyond the channel binding types
defined in the document.  It this the document to do that?  It appears
as if the text is written to apply to draft-josefsson-sasl-tls-cb too.

Section 7 suggests implementation requirements on TLS implementations.
GnuTLS has APIs that allows applications to implement tls-unique and
tls-server-end-point, but these interfaces would not follow the MUST in
section 7 at least the way I read them.  I'd prefer to leave API design
to implementers, and hence remove the RFC 2119 keywords from this
section, and have the section provide guidance rather than norms.

Thanks,
/Simon


From owner-ietf-sasl@mail.imc.org  Fri Jun 12 11:42:33 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 23FB528C0E3 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri, 12 Jun 2009 11:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.746
X-Spam-Level: 
X-Spam-Status: No, score=-5.746 tagged_above=-999 required=5 tests=[AWL=0.300, 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 FCfmfiSexLyH for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Fri, 12 Jun 2009 11:42:32 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id E80033A6C0C for <sasl-archive-Zoh8yoh9@ietf.org>; Fri, 12 Jun 2009 11:42:31 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5CIbUhW017984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jun 2009 11:37:30 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5CIbUap017983; Fri, 12 Jun 2009 11:37:30 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from sca-ea-mail-3.sun.com (sca-ea-mail-3.Sun.COM [192.18.43.21]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5CIbJNG017958 for <ietf-sasl@imc.org>; Fri, 12 Jun 2009 11:37:29 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5CIbIfY022065 for <ietf-sasl@imc.org>; Fri, 12 Jun 2009 18:37:18 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5CIbHv0040149 for <ietf-sasl@imc.org>; Fri, 12 Jun 2009 12:37:18 -0600 (MDT)
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 n5CIRDuv007729; Fri, 12 Jun 2009 13:27:13 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5CIRCiO007728; Fri, 12 Jun 2009 13:27:12 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Fri, 12 Jun 2009 13:27:12 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: ietf-sasl@imc.org
Subject: Re: New version of draft-altman-tls-channel-bindings
Message-ID: <20090612182712.GA1049@Sun.COM>
References: <20090611182608.GU1049@Sun.COM> <87ski5erfu.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87ski5erfu.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Fri, Jun 12, 2009 at 11:23:33AM +0200, Simon Josefsson wrote:
> The registration sections 3-5 looks fine to me.
> 
> I have two mild concerns on section 6 and 7:
> 
> Section 6 mandate rather general restrictions on application protocol
> specifications that appear to apply beyond the channel binding types
> defined in the document.  It this the document to do that?  It appears
> as if the text is written to apply to draft-josefsson-sasl-tls-cb too.

What it mandates should be entirely non-controversial, I thought:

   Specifically, application protocol specifications MUST indicate at
   least one mandatory to implement channel binding type, MAY specify a
   negotiation protocol, MAY allow for out-of-band negotiation or
   configuration, and SHOULD prefer 'tls-unique' over 'tls-server-end-
   point'.

This doesn't say what the apps must require, just that they must require
something.  It doesn't dictate specifics.

There's also a recommendation:

                                      ...  However, it is RECOMMENDED
   that application protocols making use of TLS channel bindings, use
   'tls-unique' exclusively, except, perhaps, where server-side proxies
   are common in deployments of an application protocol.  ...

I thought that too would be non-controversial as it is just a
recommendation.

> Section 7 suggests implementation requirements on TLS implementations.

Yes.

> GnuTLS has APIs that allows applications to implement tls-unique and
> tls-server-end-point, but these interfaces would not follow the MUST in
> section 7 at least the way I read them.  I'd prefer to leave API design
> to implementers, and hence remove the RFC 2119 keywords from this
> section, and have the section provide guidance rather than norms.

The section 7 text says that either the TLS implementation must either
provide an interface for extracting channel bindings by channel binding
type (something like: getCB(connection, cb_type) -> CB data), or
interfaces for extracting those items that are used to construct the CB
data (something like: getFirstClientFinishedMsg(connection),
getFirstServerFinishedMsg(connection), getServerEECert(connection)).

Are there other possibilities that I did not consider?  Why is what I
wrote controversial?

Nico
-- 


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 11:35:32 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C2F273A67A1 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 11:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.976
X-Spam-Level: 
X-Spam-Status: No, score=-1.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=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 mpUEezlakgiP for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 11:35:32 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 950093A68DE for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 11:35:31 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FIRsAB034704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 11:27:54 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FIRsgQ034703; Mon, 15 Jun 2009 11:27:54 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from mail-ew0-f217.google.com (mail-ew0-f217.google.com [209.85.219.217]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FIRg3D034683 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 11:27:53 -0700 (MST) (envelope-from tmarkmann@googlemail.com)
Received: by ewy17 with SMTP id 17so4509304ewy.10 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 11:27:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=V9vX8NIqHE1lrSwR78SiaYYPz1QU+O9W7k5w4rdOTOI=; b=GLvb5QLvXMM7oFZZpza3efI30ZQC4J1FZPuFC6LnUqpPq2McPL0MraUyatuY3NgAAq 87FVFRK2hy5pOhjSs0YB7Jvfqnb5184JfKYSfjG8pNcHtmF/F2LoQBGOfs0cNjfnA1YT tOcLE9z35oTtGQDitAwuBOWag9lh87GLo9EGw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ADhonyKOAbyQLkeulmeNJN5cS7ZdBAcjO7qJ9ndLFi6SgeuZudc8ec7pfR7yZcVvEL 5fMhuHYrwwP/cNvpCZDdtAwh00wCoYRH9s2Kh9312/Omw5igBJbT0DmadiwN7L9KjzGr 3wHI/bUUlsZkS8hW/MFOvRSPUKDo1eudDNB2g=
MIME-Version: 1.0
Received: by 10.210.17.14 with SMTP id 14mr3640433ebq.71.1245090461676; Mon,  15 Jun 2009 11:27:41 -0700 (PDT)
Date: Mon, 15 Jun 2009 20:27:41 +0200
Message-ID: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
Subject: Sequence of attributes in a SCRAM message
From: Tobias Markmann <tmarkmann@googlemail.com>
To: ietf-sasl@imc.org
Content-Type: multipart/alternative; boundary=0015174be6eaae74ad046c673681
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--0015174be6eaae74ad046c673681
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,
>From Section 5.1 of the latest draft:

> Note that the order of attributes in client or server messages is
>    fixed, with the exception of extension attributes (described by the
>    "extensions" ABNF production), which can appear in any order in the
>    designated positions.  See the ABNF section for authoritative
>    reference.
>
>
Does this mean that during serialization, attribute 'a' goes first, then
'n', 'm', 'r' and so on? If so why the restriction on sequence?
Cheers,
Tobias Markmann

--0015174be6eaae74ad046c673681
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>From Section 5.1 of the latest draft:</div><blockquo=
te class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0px; margi=
n-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-colo=
r: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<span class=3D"Apple-style-span" style=3D"font-family: &#39;Hoefler Text&#3=
9;; font-size: medium; "><pre style=3D"word-wrap: break-word; white-space: =
pre-wrap; ">Note that the order of attributes in client or server messages =
is
   fixed, with the exception of extension attributes (described by the
   &quot;extensions&quot; ABNF production), which can appear in any order i=
n the
   designated positions.  See the ABNF section for authoritative
   reference.</pre></span></blockquote><div>=C2=A0</div>Does this mean that=
 during serialization, attribute &#39;a&#39; goes first, then &#39;n&#39;, =
&#39;m&#39;, &#39;r&#39; and so on? If so why the restriction on sequence?<=
div>
<br>Cheers,<br>Tobias Markmann</div>

--0015174be6eaae74ad046c673681--


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 12:09:31 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 63FAA3A6C3F for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 12:09:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.768
X-Spam-Level: 
X-Spam-Status: No, score=-5.768 tagged_above=-999 required=5 tests=[AWL=0.278, 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 ybwwBp7yVAqY for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 12:09:30 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 35E6C3A6A74 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 12:09:29 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FJ5Fne036714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 12:05:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FJ5Fu6036713; Mon, 15 Jun 2009 12:05:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FJ53Wt036701 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 12:05:13 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5FJ52UU007335 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 19:05:03 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 n5FJ526G048971 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:05:02 -0600 (MDT)
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 n5FIlXB4001604; Mon, 15 Jun 2009 13:47:33 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5FIlWWV001603; Mon, 15 Jun 2009 13:47:32 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 15 Jun 2009 13:47:32 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Tobias Markmann <tmarkmann@googlemail.com>
Cc: ietf-sasl@imc.org
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <20090615184732.GL1308@Sun.COM>
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Mon, Jun 15, 2009 at 08:27:41PM +0200, Tobias Markmann wrote:
> Hi,
> From Section 5.1 of the latest draft:
> 
> > Note that the order of attributes in client or server messages is
> >    fixed, with the exception of extension attributes (described by the
> >    "extensions" ABNF production), which can appear in any order in the
> >    designated positions.  See the ABNF section for authoritative
> >    reference.
> >
> >
> Does this mean that during serialization, attribute 'a' goes first, then
> 'n', 'm', 'r' and so on? If so why the restriction on sequence?

The ABNF itself provides the order.  See the ABNF.


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 12:33:52 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4AB053A67A1 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 12:33:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.398
X-Spam-Level: 
X-Spam-Status: No, score=-2.398 tagged_above=-999 required=5 tests=[AWL=0.201, 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 b356WBNeAbMP for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 12:33:51 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id E01353A6C58 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 12:33:50 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FJSV3Z037836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 12:28:31 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FJSVLT037835; Mon, 15 Jun 2009 12:28:31 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FJSTcP037828 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 12:28:30 -0700 (MST) (envelope-from dave@cridland.net)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <Sjag2AAnObBw@peirce.dave.cridland.net>; Mon, 15 Jun 2009 20:28:25 +0100
X-SMTP-Protocol-Errors: NORDNS
Subject: Re: Sequence of attributes in a SCRAM message
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM>
In-Reply-To: <20090615184732.GL1308@Sun.COM>
MIME-Version: 1.0
Message-Id: <27893.1245094100.834041@puncture>
Date: Mon, 15 Jun 2009 20:28:20 +0100
From: Dave Cridland <dave@cridland.net>
To: Nicolas Williams <Nicolas.Williams@sun.com>, <ietf-sasl@imc.org>, Tobias Markmann <tmarkmann@googlemail.com>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Mon Jun 15 19:47:32 2009, Nicolas Williams wrote:
> On Mon, Jun 15, 2009 at 08:27:41PM +0200, Tobias Markmann wrote:
> > Hi,
> > From Section 5.1 of the latest draft:
> >
> > > Note that the order of attributes in client or server messages  
> is
> > >    fixed, with the exception of extension attributes (described  
> by the
> > >    "extensions" ABNF production), which can appear in any order  
> in the
> > >    designated positions.  See the ABNF section for authoritative
> > >    reference.
> > >
> > >
> > Does this mean that during serialization, attribute 'a' goes  
> first, then
> > 'n', 'm', 'r' and so on? If so why the restriction on sequence?
> 
> The ABNF itself provides the order.  See the ABNF.

That's not answering the question, though - what is the purpose of  
this rule? (I don't recall it existing before, except that 'r' was at  
the end).

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 13:47:29 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id D023C3A6D1E for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 13:47:29 -0700 (PDT)
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_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 buyRC7JymjLQ for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 13:47:28 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 767C73A67F4 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 13:47:28 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKgc0c042323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 13:42:38 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FKgcLW042322; Mon, 15 Jun 2009 13:42:38 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from jackfruit.srv.cs.cmu.edu (JACKFRUIT.SRV.CS.CMU.EDU [128.2.201.16]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKgQt7042302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:42:37 -0700 (MST) (envelope-from jhutz@cmu.edu)
Received: from [192.168.1.113] (SIRIUS.FAC.CS.CMU.EDU [128.2.216.216]) (authenticated bits=0) by jackfruit.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id n5FKfUle012296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 16:42:21 -0400 (EDT)
Date: Mon, 15 Jun 2009 16:40:17 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Dave Cridland <dave@cridland.net>, Nicolas Williams <Nicolas.Williams@sun.com>, ietf-sasl@imc.org, Tobias Markmann <tmarkmann@googlemail.com>
cc: jhutz@cmu.edu
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <6FD5DE7A2124A5BB31623DEC@B182BF00AF5DB930FC0FAF33>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.201.16
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--On Monday, June 15, 2009 08:28:20 PM +0100 Dave Cridland 
<dave@cridland.net> wrote:

>
> On Mon Jun 15 19:47:32 2009, Nicolas Williams wrote:
>> On Mon, Jun 15, 2009 at 08:27:41PM +0200, Tobias Markmann wrote:
>> > Hi,
>> > From Section 5.1 of the latest draft:
>> >
>> > > Note that the order of attributes in client or server messages
>> is
>> > >    fixed, with the exception of extension attributes (described
>> by the
>> > >    "extensions" ABNF production), which can appear in any order
>> in the
>> > >    designated positions.  See the ABNF section for authoritative
>> > >    reference.
>> > >
>> > >
>> > Does this mean that during serialization, attribute 'a' goes
>> first, then
>> > 'n', 'm', 'r' and so on? If so why the restriction on sequence?
>>
>> The ABNF itself provides the order.  See the ABNF.
>
> That's not answering the question, though - what is the purpose of this
> rule? (I don't recall it existing before, except that 'r' was at the end).

It's not new -- the ABNF has always specified a sequence of particular 
attributes, some of which might be optional, not a sequence of aribtrary 
"key=value" pairs and a set of permissible keys.

There are several reasons for the ordering requirement, but much of it 
boils down to the fact that some of the attributes come from the GS2 layer, 
while others are SCRAM-specific.  The modularity needed to allow GS2 + 
GSS-SCRAM to interoperate with a pure-SASL SCRAM implementation imposes 
certain requirements.  One is that all of the bits of a message that are 
SCRAM-specific are grouped together and easily separable, so that GS2 can 
treat them as a single opaque string, since it cannot know the details of 
SCRAM.  Another has to do with the hash calculation; we need to be sure 
that the value being hashed is the same on both sides, which means either 
requiring a particular order for attributes or requiring implementations to 
pick out the attributes to be hashed and assembling them together in the 
right order.  This is probably doable, but "the right order" would have to 
group together everything passed down from the GS2 layer, including the 
actual channel bindings, because GSS-SCRAM cannot know that it is being 
called by GS2 and thus must treat the GSS-API CB application data (where 
GS2 puts the actual channel bindings and also things like the authzid and 
CB indicator flag) as an opaque string.

In short, we don't have to require a specific sequence of attributes, but 
allowing them to be reordered completely arbitrarily would break the 
protocol, and the constraints on how they can be reordered would be complex 
to describe and to implement.

I don't believe there is anything that would break if an implementation 
were to accept out-of-order attributes, as long as the hashes are computed 
in the same way by both sides (either in the order sent, or in the order 
specified in the protocol).  But I'd have to read the document fairly 
carefully to be sure there were no security ramifications.

-- Jeff


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 13:52:02 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 248F23A68BF for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 13:52:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.454
X-Spam-Level: 
X-Spam-Status: No, score=-2.454 tagged_above=-999 required=5 tests=[AWL=0.145, 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 LoJyWFBLet4Z for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 13:52:01 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 018D33A6CFF for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 13:52:00 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKlhXj042571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 13:47:43 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FKlhAO042570; Mon, 15 Jun 2009 13:47:43 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKlVS8042561 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:47:42 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [92.40.11.139] (92.40.11.139.sub.mbb.three.co.uk [92.40.11.139])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SjazYAAh5JsW@rufus.isode.com>; Mon, 15 Jun 2009 21:47:29 +0100
Message-ID: <4A36B325.5030908@isode.com>
Date: Mon, 15 Jun 2009 21:46:29 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Tobias Markmann <tmarkmann@googlemail.com>
CC: ietf-sasl@imc.org
Subject: Re: Sequence of attributes in a SCRAM message
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
In-Reply-To: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Tobias Markmann wrote:

> Hi,
>
> From Section 5.1 of the latest draft:
>
>Note that the order of attributes in client or server messages is
>   fixed, with the exception of extension attributes (described by the
>   "extensions" ABNF production), which can appear in any order in the
>   designated positions.  See the ABNF section for authoritative
>   reference.
>
>  Does this mean that during serialization, attribute 'a' goes first, 
> then 'n', 'm', 'r' and so on? If so why the restriction on sequence?

This restriction is to simplify implementations.


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 14:02:59 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 642BC28C13F for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 14:02:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=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 jqbvuuxA1r-Y for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 14:02:56 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 204A83A6D34 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 14:02:55 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKwFuX043226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 13:58:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FKwFY4043225; Mon, 15 Jun 2009 13:58:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from mail-px0-f177.google.com (mail-px0-f177.google.com [209.85.216.177]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKw48A043212 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:58:14 -0700 (MST) (envelope-from toomuchit@gmail.com)
Received: by pxi7 with SMTP id 7so51770pxi.16 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=W4itGpge+Jofuf+ebLBMNFZ6GUWRClRjpDC6hDF8OWk=; b=gTv65gdeB4xwVfCTL2WZKhG8TvPTmvaS5M8S+TMioWNms2UVZGswdFzgTyB0qAe9O5 UVkzH0YaLDInm9jHem2fJ9SaF4+FL3v1fhBo+M9PTDRSa585b5GnOCWhwxJOLGLuwJof hed4kS+SVPJunwMUuakTF7MsQoiokpHdSZG+0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; b=gwCAG4yancel9uwc/PelBU2VvsCedSgxMRa9RWuR72FH0Aull+jy2RI6+hQwVjLN9X 5+VD5wAvnssCuUxiXYzLZYRlwR6QoxraMjyn7SMNjPcizsQ3c/76N13C+Y7ak/N1dWx1 mk3foA5wnl2atDDhZFRV/fvhdPPMUUS3vYrwY=
Received: by 10.142.144.9 with SMTP id r9mr3661965wfd.187.1245099483583; Mon, 15 Jun 2009 13:58:03 -0700 (PDT)
Received: from BrianPC (c-98-234-66-100.hsd1.ca.comcast.net [98.234.66.100]) by mx.google.com with ESMTPS id 30sm181484wfc.38.2009.06.15.13.58.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Jun 2009 13:58:03 -0700 (PDT)
From: "Brian Andrus" <toomuchit@gmail.com>
To: <ietf-sasl@imc.org>
Subject: sasl authentication
Date: Mon, 15 Jun 2009 13:57:57 -0700
Message-ID: <003701c9edfb$f7071320$e5153960$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0038_01C9EDC1.4AA83B20"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acnt+/XizdzMlT1eTXeQamq2zKa35A==
Content-Language: en-us
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

This is a multipart message in MIME format.

------=_NextPart_000_0038_01C9EDC1.4AA83B20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello all.

New to the list because I am trying to find out if/how I can authenticate
via sasl for accounts whose username has the '@' sign in them.

There are a number in our ldap directory, which do authenticate for ssh,
ftp, etc however when I try setting up postfix, it will not authenticate. It
seems to be breaking the username up into a realm as well.

 

So, is it possible to get sasl to authenticate using an email looking
username against pam/ldap?

Or

Where is the proper place to ask this?

 

Thanks in advance for any insight.

 

Brian

 


------=_NextPart_000_0038_01C9EDC1.4AA83B20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hello all.<o:p></o:p></p>

<p class=3DMsoNormal>New to the list because I am trying to find out =
if/how I can
authenticate via sasl for accounts whose username has the =
&#8216;@&#8217; sign
in them.<o:p></o:p></p>

<p class=3DMsoNormal>There are a number in our ldap directory, which do
authenticate for ssh, ftp, etc however when I try setting up postfix, it =
will
not authenticate. It seems to be breaking the username up into a realm =
as well.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>So, is it possible to get sasl to authenticate =
using an
email looking username against pam/ldap?<o:p></o:p></p>

<p class=3DMsoNormal>Or<o:p></o:p></p>

<p class=3DMsoNormal>Where is the proper place to ask =
this?<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Thanks in advance for any insight.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Brian<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0038_01C9EDC1.4AA83B20--


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 14:10:00 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0E5CA3A6833 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 14:10:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.976
X-Spam-Level: 
X-Spam-Status: No, score=-101.976 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, USER_IN_WHITELIST=-100]
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 NvYhXjyzgqnI for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 14:09:59 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id E6DF53A6812 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 14:09:58 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FL5bN2043712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:05:37 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FL5bbF043711; Mon, 15 Jun 2009 14:05:37 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from smtp-out.google.com (smtp-out.google.com [216.239.45.13]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FL5Pj1043694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:05:36 -0700 (MST) (envelope-from robsiemb@google.com)
Received: from spaceape24.eur.corp.google.com (spaceape24.eur.corp.google.com [172.28.16.76]) by smtp-out.google.com with ESMTP id n5FL5Ode017512 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:05:25 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1245099925; bh=ZGcrlrokEChRfnF91bRuZb9N/tM=; h=DomainKey-Signature:MIME-Version:In-Reply-To:References:From:Date: Message-ID:Subject:To:Cc:Content-Type:X-System-Of-Record; b=stbJyd vR6dbNI8ZRrcKf43jzdzAerGze5wdujEOmWU6hkAPRSHiUSKcAIqtbUKE2yqwyLbXdF 4RaWM42Cdp1pw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=dUnpFsKOet3FMsu9OcBJzcSOQ4SXjWQ9HC17icStO0T55YWzXEB+v9UkTLoNKmeqq tAL+/Hhl5gz6M4YQN2M6g==
Received: from yxe2 (yxe2.prod.google.com [10.190.2.2]) by spaceape24.eur.corp.google.com with ESMTP id n5FL57dJ024990 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:05:22 -0700
Received: by yxe2 with SMTP id 2so523130yxe.24 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:05:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.72.1 with SMTP id z1mr14134438ybk.15.1245099921155; Mon,  15 Jun 2009 14:05:21 -0700 (PDT)
In-Reply-To: <003701c9edfb$f7071320$e5153960$@com>
References: <003701c9edfb$f7071320$e5153960$@com>
From: Rob Siemborski <robsiemb@google.com>
Date: Mon, 15 Jun 2009 14:05:01 -0700
Message-ID: <5b93232d0906151405j35b11dd0wb7e7d3558a180e9a@mail.gmail.com>
Subject: Re: sasl authentication
To: Brian Andrus <toomuchit@gmail.com>
Cc: ietf-sasl@imc.org
Content-Type: multipart/alternative; boundary=001e680f181882a7f4046c696ad3
X-System-Of-Record: true
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--001e680f181882a7f4046c696ad3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 15, 2009 at 1:57 PM, Brian Andrus <toomuchit@gmail.com> wrote:

>  Hello all.
>
> New to the list because I am trying to find out if/how I can authenticate
> via sasl for accounts whose username has the =91@=92 sign in them.
>
> There are a number in our ldap directory, which do authenticate for ssh,
> ftp, etc however when I try setting up postfix, it will not authenticate.=
 It
> seems to be breaking the username up into a realm as well.
>
>
>
> So, is it possible to get sasl to authenticate using an email looking
> username against pam/ldap?
>
> Or
>
> Where is the proper place to ask this?
>

cyrus-sasl@andrew.cmu.edu

-Rob

--=20
Rob Siemborski        |     PGP:0x5CE32FCC    |     robsiemb@google.com
Software Engineer     |                       |            650-623-6925

--001e680f181882a7f4046c696ad3
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Jun 15, 2009 at 1:57 PM, Brian A=
ndrus <span dir=3D"ltr">&lt;<a href=3D"mailto:toomuchit@gmail.com">toomuchi=
t@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">










<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">

<div>

<p>Hello all.</p>

<p>New to the list because I am trying to find out if/how I can
authenticate via sasl for accounts whose username has the =91@=92 sign
in them.</p>

<p>There are a number in our ldap directory, which do
authenticate for ssh, ftp, etc however when I try setting up postfix, it wi=
ll
not authenticate. It seems to be breaking the username up into a realm as w=
ell.</p>

<p>=A0</p>

<p>So, is it possible to get sasl to authenticate using an
email looking username against pam/ldap?</p>

<p>Or</p>

<p>Where is the proper place to ask this?</p></div></div></blockquote><div>=
<br></div><div><a href=3D"mailto:cyrus-sasl@andrew.cmu.edu">cyrus-sasl@andr=
ew.cmu.edu</a></div><div><br></div><div>-Rob</div><div><br></div></div>-- <=
br>

Rob Siemborski =A0 =A0 =A0 =A0| =A0 =A0 PGP:0x5CE32FCC =A0 =A0| =A0 =A0 <a =
href=3D"mailto:robsiemb@google.com">robsiemb@google.com</a><br>Software Eng=
ineer =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 =A0 =
=A0 =A0 =A0650-623-6925<br><br>

--001e680f181882a7f4046c696ad3--


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 14:25:41 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 98AFB3A697D for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 14:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.778
X-Spam-Level: 
X-Spam-Status: No, score=-5.778 tagged_above=-999 required=5 tests=[AWL=0.268, 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 AHQsM-I1gUPy for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 14:25:40 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 63FAD3A6953 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 14:25:40 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FLLMqU044690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:21:22 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FLLMTb044689; Mon, 15 Jun 2009 14:21:22 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FLLLam044683 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:21:22 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5FLLLwh009004 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 21:21:21 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5FLLLBp024770 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 15:21:21 -0600 (MDT)
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 n5FKuN0D001712; Mon, 15 Jun 2009 15:56:23 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5FKuKP3001711; Mon, 15 Jun 2009 15:56:20 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 15 Jun 2009 15:56:20 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Dave Cridland <dave@cridland.net>
Cc: ietf-sasl@imc.org, Tobias Markmann <tmarkmann@googlemail.com>
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <20090615205620.GR1308@Sun.COM>
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <27893.1245094100.834041@puncture>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Mon, Jun 15, 2009 at 08:28:20PM +0100, Dave Cridland wrote:
> That's not answering the question, though - what is the purpose of  
> this rule? (I don't recall it existing before, except that 'r' was at  
> the end).

Sorry.  See Jeff's reply about the GS2 header vs. the SCRAM messages --
at least that much order is required.  Within each of those order is not
crucial.  The GS2 header is simple enough that having order in it
actually simplifies things.

As for order within the SCRAM messages, I don't know the reason for nor
history of that, nor do I much care whether there's order in the SCRAM
messages.  But I agree that having order _and_ attribute=value adds
unnecessary redundance -- one could have order and no attribute=, or
attribute=value and no order, still have things work out.

Nico
-- 


From owner-ietf-sasl@mail.imc.org  Mon Jun 15 14:48:27 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 429293A69BC for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 14:48:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.459
X-Spam-Level: 
X-Spam-Status: No, score=-2.459 tagged_above=-999 required=5 tests=[AWL=0.140, 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 xolqt5nwIWkO for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Mon, 15 Jun 2009 14:48:26 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 1A0DD3A6889 for <sasl-archive-Zoh8yoh9@ietf.org>; Mon, 15 Jun 2009 14:48:25 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FLiGZ2046015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:44:16 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FLiGvG046014; Mon, 15 Jun 2009 14:44:16 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FLiFI4046008 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:44:16 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [92.40.11.139] (92.40.11.139.sub.mbb.three.co.uk [92.40.11.139])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SjbArAAh5A95@rufus.isode.com>; Mon, 15 Jun 2009 22:44:13 +0100
Message-ID: <4A36C07D.4030604@isode.com>
Date: Mon, 15 Jun 2009 22:43:25 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Nicolas Williams <Nicolas.Williams@sun.com>
CC: ietf-sasl@imc.org, Tobias Markmann <tmarkmann@googlemail.com>
Subject: Re: Sequence of attributes in a SCRAM message
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture> <20090615205620.GR1308@Sun.COM>
In-Reply-To: <20090615205620.GR1308@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams wrote:

>On Mon, Jun 15, 2009 at 08:28:20PM +0100, Dave Cridland wrote:
>  
>
>>That's not answering the question, though - what is the purpose of  
>>this rule? (I don't recall it existing before, except that 'r' was at  
>>the end).
>>    
>>
>Sorry.  See Jeff's reply about the GS2 header vs. the SCRAM messages --
>at least that much order is required.  Within each of those order is not
>crucial.  The GS2 header is simple enough that having order in it
>actually simplifies things.
>  
>
Right.

>As for order within the SCRAM messages, I don't know the reason for nor
>history of that, nor do I much care whether there's order in the SCRAM
>messages.  But I agree that having order _and_ attribute=value adds
>unnecessary redundance -- one could have order and no attribute=, or
>attribute=value and no order, still have things work out.
>  
>
This was discussed on the mailing list (before SCRAM became a GS2 
mechanism) and there were some arguments made for making the order fixed.
While I don't really care about the issue, I would rather not revisit 
it, unless people have good arguments while the fixed order is harmful.

(Also note that there is no order enforced on extensions.)


From owner-ietf-sasl@mail.imc.org  Tue Jun 16 05:56:35 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4C03B3A698B for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue, 16 Jun 2009 05:56:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 5RsGZGD3U9AA for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue, 16 Jun 2009 05:56:34 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 022E03A6D70 for <sasl-archive-Zoh8yoh9@ietf.org>; Tue, 16 Jun 2009 05:56:33 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GCoT0t005540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 05:50:29 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5GCoTut005539; Tue, 16 Jun 2009 05:50:29 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GCoGNZ005519 for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 05:50:28 -0700 (MST) (envelope-from arnt@oryx.com)
Received: from kalyani.oryx.com (localhost [127.0.0.1]) by kalyani.oryx.com (Postfix) with ESMTP id 960C82E160; Tue, 16 Jun 2009 14:49:09 +0200 (CEST)
Received: from arnt@oryx.com (HELO lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with esmtp id 1245156549-34806-34805/6/44 (5 recipients); Tue, 16 Jun 2009 14:49:09 +0200
Message-Id: <XZX0VWTahmAG/E+Qnehh4Q.md5@lochnagar.oryx.com>
Date: Tue, 16 Jun 2009 14:50:24 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: Sequence of attributes in a SCRAM message
Cc: Tobias Markmann <tmarkmann@googlemail.com>, Dave Cridland <dave@cridland.net>, ietf-sasl@imc.org
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture> <20090615205620.GR1308@Sun.COM>
In-Reply-To: <20090615205620.GR1308@Sun.COM>
Content-Type: text/plain; format=flowed
Mime-Version: 1.0
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams writes:
> As for order within the SCRAM messages, I don't know the reason for 
> nor history of that, nor do I much care whether there's order in the 
> SCRAM messages. But I agree that having order _and_ attribute=value 
> adds unnecessary redundance

As far as I can tell, the order is necessary for the computer. The a=v 
stuff makes scram messages easier to read for people, and it's only 
about eight bytes.

> -- one could have order and no attribute=, or attribute=value and no 
> order, still have things work out.

Yeah, but it would be more strain on the brain. 
x=43241,43214,4321423,,4321432,432 is harder to decipher than 
x=43214,y=34123,=4324132,w=,e=421. Perhaps not THAT much harder, but I 
think it's worth eight bytes.

Might be good to add a parenthetical remark, perhaps "this ordering 
simplifies some implementation aspects, e.g. the hash calculation".

Arnt


From owner-ietf-sasl@mail.imc.org  Tue Jun 16 10:08:02 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 06EA83A6DA0 for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue, 16 Jun 2009 10:08:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.739
X-Spam-Level: 
X-Spam-Status: No, score=-5.739 tagged_above=-999 required=5 tests=[AWL=0.307, 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 zQx2DudjZO8K for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue, 16 Jun 2009 10:08:01 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id DB8083A6D8B for <sasl-archive-Zoh8yoh9@ietf.org>; Tue, 16 Jun 2009 10:08:00 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GH2Ons026128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 10:02:24 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5GH2NbR026127; Tue, 16 Jun 2009 10:02:23 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GH2BT3026100 for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 10:02:21 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5GH2Arc013099 for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 17:02:10 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5GH2A5U034998 for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 11:02:10 -0600 (MDT)
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 n5GGbAwt002426; Tue, 16 Jun 2009 11:37:10 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5GGb7Hx002425; Tue, 16 Jun 2009 11:37:07 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Tue, 16 Jun 2009 11:37:07 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Arnt Gulbrandsen <arnt@oryx.com>
Cc: Tobias Markmann <tmarkmann@googlemail.com>, Dave Cridland <dave@cridland.net>, ietf-sasl@imc.org
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <20090616163706.GV1308@Sun.COM>
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture> <20090615205620.GR1308@Sun.COM> <XZX0VWTahmAG/E+Qnehh4Q.md5@lochnagar.oryx.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <XZX0VWTahmAG/E+Qnehh4Q.md5@lochnagar.oryx.com>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Tue, Jun 16, 2009 at 02:50:24PM +0200, Arnt Gulbrandsen wrote:
> Nicolas Williams writes:
> >As for order within the SCRAM messages, I don't know the reason for 
> >nor history of that, nor do I much care whether there's order in the 
> >SCRAM messages. But I agree that having order _and_ attribute=value 
> >adds unnecessary redundance
> 
> As far as I can tell, the order is necessary for the computer. The a=v 
> stuff makes scram messages easier to read for people, and it's only 
> about eight bytes.

It's possible to write a program that doesn't care about the order in
which the attrs appear.  That'd be programming 102 :)

> >-- one could have order and no attribute=, or attribute=value and no 
> >order, still have things work out.
> 
> Yeah, but it would be more strain on the brain. 

We're having the age-old argument about redundancy.  How much redundancy
do we want in an on-the-wire encoding of a message?  ASN.1's BER's TLV
encodings have been problematic, in terms of bugs, meanwhile everyone is
always re-inventing PER and XML, which means that the debate never ends.

Let's not have this argument.  Instead let's agree that SCRAM is the way
it is and be done.  And keep in mind that several implementors have
prototypes already, or even code that awaits only consensus to get
deployed.  Changing SCRAM now for this little issue will cause those
implementors much hassle.

Nico
-- 


From owner-ietf-sasl@mail.imc.org  Tue Jun 16 10:25:34 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 408923A68BC for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue, 16 Jun 2009 10:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.266
X-Spam-Level: 
X-Spam-Status: No, score=-5.266 tagged_above=-999 required=5 tests=[AWL=1.333, BAYES_00=-2.599, 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 FFNeLp9zuU9v for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Tue, 16 Jun 2009 10:25:33 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 269A628C182 for <sasl-archive-Zoh8yoh9@ietf.org>; Tue, 16 Jun 2009 10:25:31 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GHIWlK027643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 10:18:32 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5GHIWZN027642; Tue, 16 Jun 2009 10:18:32 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from jackfruit.srv.cs.cmu.edu (JACKFRUIT.SRV.CS.CMU.EDU [128.2.201.16]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GHIKrr027626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 10:18:31 -0700 (MST) (envelope-from jhutz@cmu.edu)
Received: from [192.168.1.113] (SIRIUS.FAC.CS.CMU.EDU [128.2.216.216]) (authenticated bits=0) by jackfruit.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id n5GHI66a024936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 13:18:07 -0400 (EDT)
Date: Tue, 16 Jun 2009 13:18:06 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Nicolas Williams <Nicolas.Williams@sun.com>, Arnt Gulbrandsen <arnt@oryx.com>
cc: Tobias Markmann <tmarkmann@googlemail.com>, Dave Cridland <dave@cridland.net>, ietf-sasl@imc.org, jhutz@cmu.edu
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <027878D80AE2A4F581CA1CCA@atlantis.pc.cs.cmu.edu>
In-Reply-To: <20090616163706.GV1308@Sun.COM>
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture> <20090615205620.GR1308@Sun.COM> <XZX0VWTahmAG/E+Qnehh4Q.md5@lochnagar.oryx.com> <20090616163706.GV1308@Sun.COM>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.201.16
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--On Tuesday, June 16, 2009 11:37:07 AM -0500 Nicolas Williams 
<Nicolas.Williams@sun.com> wrote:

>> As far as I can tell, the order is necessary for the computer. The a=v
>> stuff makes scram messages easier to read for people, and it's only
>> about eight bytes.
>
> It's possible to write a program that doesn't care about the order in
> which the attrs appear.  That'd be programming 102 :)

Right.  The ordering is necessary for the _protocol_, to a certain extent. 
Beyond that, it simplifies implementation but is not essential.

> Let's not have this argument.  Instead let's agree that SCRAM is the way
> it is and be done.  And keep in mind that several implementors have
> prototypes already, or even code that awaits only consensus to get
> deployed.  Changing SCRAM now for this little issue will cause those
> implementors much hassle.

+1


From owner-ietf-sasl@mail.imc.org  Thu Jun 25 10:24:34 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EB54D3A659B for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu, 25 Jun 2009 10:24:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.499
X-Spam-Level: 
X-Spam-Status: No, score=-2.499 tagged_above=-999 required=5 tests=[AWL=0.100, 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 XkyNB4uWZPDn for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Thu, 25 Jun 2009 10:24:34 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 94C563A68B6 for <sasl-archive-Zoh8yoh9@ietf.org>; Thu, 25 Jun 2009 10:24:33 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5PHGFU7009056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Jun 2009 10:16:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5PHGFVS009055; Thu, 25 Jun 2009 10:16:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5PHG1dR009038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Thu, 25 Jun 2009 10:16:13 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (m90-137-82-10.cust.tele2.se [90.137.82.10]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n5PHFqnw023677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf-sasl@imc.org>; Thu, 25 Jun 2009 19:15:58 +0200
X-Hashcash: 1:22:090625:ietf-sasl@imc.org::dRae5ffjj+oyYNzt:5dX7
From: Simon Josefsson <simon@josefsson.org>
To: ietf-sasl@imc.org
Subject: GS2 update
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
Date: Thu, 25 Jun 2009 19:15:51 +0200
Message-ID: <87my7wfd4o.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

All,

I've made further GS2 changes based on various on and off list
discussions.  I think it is time to submit a new version to the IETF,
and I will do that tomorrow.  If you want, you can review what I'm going
to submit early, to help me catch embarrassing problems.

Text:
http://josefsson.org/sasl-gs2/draft-ietf-sasl-gs2.txt

HTML:
http://josefsson.org/sasl-gs2/draft-ietf-sasl-gs2.html

Changes since -13:
http://josefsson.org/sasl-gs2/draft-ietf-sasl-gs2-from--13.diff.html

/Simon


From owner-ietf-sasl@mail.imc.org  Sat Jun 27 09:35:28 2009
Return-Path: <owner-ietf-sasl@mail.imc.org>
X-Original-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Delivered-To: ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C86803A67FF for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Sat, 27 Jun 2009 09:35:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.708
X-Spam-Level: 
X-Spam-Status: No, score=-103.708 tagged_above=-999 required=5 tests=[AWL=1.808, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, URIBL_RHS_DOB=1.083, USER_IN_WHITELIST=-100]
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 TNkXIblGOaZk for <ietfarch-sasl-archive-Zoh8yoh9@core3.amsl.com>; Sat, 27 Jun 2009 09:35:15 -0700 (PDT)
Received: from balder-227.proper.com (properopus-pt.tunnel.tserv3.fmt2.ipv6.he.net [IPv6:2001:470:1f04:392::2]) by core3.amsl.com (Postfix) with ESMTP id 72D2E3A6403 for <sasl-archive-Zoh8yoh9@ietf.org>; Sat, 27 Jun 2009 09:35:15 -0700 (PDT)
Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5RGUM7E068695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 27 Jun 2009 09:30:23 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5RGUMAq068694; Sat, 27 Jun 2009 09:30:22 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5RGULhP068688 for <ietf-sasl@imc.org>; Sat, 27 Jun 2009 09:30:22 -0700 (MST) (envelope-from root@core3.amsl.com)
Received: by core3.amsl.com (Postfix, from userid 0) id 0AA243A67FF; Sat, 27 Jun 2009 09:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: ietf-sasl@imc.org
Subject: I-D Action:draft-ietf-sasl-gs2-14.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090627163002.0AA243A67FF@core3.amsl.com>
Date: Sat, 27 Jun 2009 09:30:02 -0700 (PDT)
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Simple Authentication and Security Layer Working Group of the IETF.


	Title           : Using GSS-API Mechanisms in SASL: The GS2 Mechanism Family
	Author(s)       : S. Josefsson, N. Williams
	Filename        : draft-ietf-sasl-gs2-14.txt
	Pages           : 23
	Date            : 2009-06-27

This document describes how to use a Generic Security Service
Application Program Interface (GSS-API) mechanism in the the Simple
Authentication and Security Layer (SASL) framework.  This is done by
defining a new SASL mechanism family, called GS2.  This mechanism
family offers a number of improvements over the previous "SASL/
GSSAPI" mechanism: it is more general, uses fewer messages for the
authentication phase in some cases, and supports negotiable use of
channel binding.  Only GSS-API mechanisms that support channel
binding are supported.

See <http://josefsson.org/sasl-gs2-*/> for more information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sasl-gs2-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-sasl-gs2-14.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2009-06-27092642.I-D@ietf.org>

--NextPart--


Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5RGUM7E068695 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 27 Jun 2009 09:30:23 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5RGUMAq068694; Sat, 27 Jun 2009 09:30:22 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from mail.ietf.org (mail.ietf.org [64.170.98.32]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5RGULhP068688 for <ietf-sasl@imc.org>; Sat, 27 Jun 2009 09:30:22 -0700 (MST) (envelope-from root@core3.amsl.com)
Received: by core3.amsl.com (Postfix, from userid 0) id 0AA243A67FF; Sat, 27 Jun 2009 09:30:01 -0700 (PDT)
From: Internet-Drafts@ietf.org
To: i-d-announce@ietf.org
Cc: ietf-sasl@imc.org
Subject: I-D Action:draft-ietf-sasl-gs2-14.txt 
Content-Type: Multipart/Mixed; Boundary="NextPart"
Mime-Version: 1.0
Message-Id: <20090627163002.0AA243A67FF@core3.amsl.com>
Date: Sat, 27 Jun 2009 09:30:02 -0700 (PDT)
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Simple Authentication and Security Layer Working Group of the IETF.


	Title           : Using GSS-API Mechanisms in SASL: The GS2 Mechanism Family
	Author(s)       : S. Josefsson, N. Williams
	Filename        : draft-ietf-sasl-gs2-14.txt
	Pages           : 23
	Date            : 2009-06-27

This document describes how to use a Generic Security Service
Application Program Interface (GSS-API) mechanism in the the Simple
Authentication and Security Layer (SASL) framework.  This is done by
defining a new SASL mechanism family, called GS2.  This mechanism
family offers a number of improvements over the previous "SASL/
GSSAPI" mechanism: it is more general, uses fewer messages for the
authentication phase in some cases, and supports negotiable use of
channel binding.  Only GSS-API mechanisms that support channel
binding are supported.

See <http://josefsson.org/sasl-gs2-*/> for more information.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-sasl-gs2-14.txt

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Message/External-body;
	name="draft-ietf-sasl-gs2-14.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:     <2009-06-27092642.I-D@ietf.org>

--NextPart--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5PHGFU7009056 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 25 Jun 2009 10:16:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5PHGFVS009055; Thu, 25 Jun 2009 10:16:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5PHG1dR009038 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Thu, 25 Jun 2009 10:16:13 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (m90-137-82-10.cust.tele2.se [90.137.82.10]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n5PHFqnw023677 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <ietf-sasl@imc.org>; Thu, 25 Jun 2009 19:15:58 +0200
X-Hashcash: 1:22:090625:ietf-sasl@imc.org::dRae5ffjj+oyYNzt:5dX7
From: Simon Josefsson <simon@josefsson.org>
To: ietf-sasl@imc.org
Subject: GS2 update
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
Date: Thu, 25 Jun 2009 19:15:51 +0200
Message-ID: <87my7wfd4o.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, score=0.1 required=5.0 tests=AWL,BAYES_00, DATE_IN_FUTURE_96_XX,RCVD_IN_PBL,RDNS_DYNAMIC,SPF_FAIL autolearn=no version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on yxa-v.extundo.com
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

All,

I've made further GS2 changes based on various on and off list
discussions.  I think it is time to submit a new version to the IETF,
and I will do that tomorrow.  If you want, you can review what I'm going
to submit early, to help me catch embarrassing problems.

Text:
http://josefsson.org/sasl-gs2/draft-ietf-sasl-gs2.txt

HTML:
http://josefsson.org/sasl-gs2/draft-ietf-sasl-gs2.html

Changes since -13:
http://josefsson.org/sasl-gs2/draft-ietf-sasl-gs2-from--13.diff.html

/Simon



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GHIWlK027643 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 10:18:32 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5GHIWZN027642; Tue, 16 Jun 2009 10:18:32 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from jackfruit.srv.cs.cmu.edu (JACKFRUIT.SRV.CS.CMU.EDU [128.2.201.16]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GHIKrr027626 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 10:18:31 -0700 (MST) (envelope-from jhutz@cmu.edu)
Received: from [192.168.1.113] (SIRIUS.FAC.CS.CMU.EDU [128.2.216.216]) (authenticated bits=0) by jackfruit.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id n5GHI66a024936 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 13:18:07 -0400 (EDT)
Date: Tue, 16 Jun 2009 13:18:06 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Nicolas Williams <Nicolas.Williams@sun.com>, Arnt Gulbrandsen <arnt@oryx.com>
cc: Tobias Markmann <tmarkmann@googlemail.com>, Dave Cridland <dave@cridland.net>, ietf-sasl@imc.org, jhutz@cmu.edu
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <027878D80AE2A4F581CA1CCA@atlantis.pc.cs.cmu.edu>
In-Reply-To: <20090616163706.GV1308@Sun.COM>
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture> <20090615205620.GR1308@Sun.COM> <XZX0VWTahmAG/E+Qnehh4Q.md5@lochnagar.oryx.com> <20090616163706.GV1308@Sun.COM>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.201.16
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--On Tuesday, June 16, 2009 11:37:07 AM -0500 Nicolas Williams 
<Nicolas.Williams@sun.com> wrote:

>> As far as I can tell, the order is necessary for the computer. The a=v
>> stuff makes scram messages easier to read for people, and it's only
>> about eight bytes.
>
> It's possible to write a program that doesn't care about the order in
> which the attrs appear.  That'd be programming 102 :)

Right.  The ordering is necessary for the _protocol_, to a certain extent. 
Beyond that, it simplifies implementation but is not essential.

> Let's not have this argument.  Instead let's agree that SCRAM is the way
> it is and be done.  And keep in mind that several implementors have
> prototypes already, or even code that awaits only consensus to get
> deployed.  Changing SCRAM now for this little issue will cause those
> implementors much hassle.

+1



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GH2Ons026128 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 10:02:24 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5GH2NbR026127; Tue, 16 Jun 2009 10:02:23 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-1.sun.com (brmea-mail-1.Sun.COM [192.18.98.31]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GH2BT3026100 for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 10:02:21 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5GH2Arc013099 for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 17:02:10 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5GH2A5U034998 for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 11:02:10 -0600 (MDT)
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 n5GGbAwt002426; Tue, 16 Jun 2009 11:37:10 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5GGb7Hx002425; Tue, 16 Jun 2009 11:37:07 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Tue, 16 Jun 2009 11:37:07 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Arnt Gulbrandsen <arnt@oryx.com>
Cc: Tobias Markmann <tmarkmann@googlemail.com>, Dave Cridland <dave@cridland.net>, ietf-sasl@imc.org
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <20090616163706.GV1308@Sun.COM>
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture> <20090615205620.GR1308@Sun.COM> <XZX0VWTahmAG/E+Qnehh4Q.md5@lochnagar.oryx.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <XZX0VWTahmAG/E+Qnehh4Q.md5@lochnagar.oryx.com>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Tue, Jun 16, 2009 at 02:50:24PM +0200, Arnt Gulbrandsen wrote:
> Nicolas Williams writes:
> >As for order within the SCRAM messages, I don't know the reason for 
> >nor history of that, nor do I much care whether there's order in the 
> >SCRAM messages. But I agree that having order _and_ attribute=value 
> >adds unnecessary redundance
> 
> As far as I can tell, the order is necessary for the computer. The a=v 
> stuff makes scram messages easier to read for people, and it's only 
> about eight bytes.

It's possible to write a program that doesn't care about the order in
which the attrs appear.  That'd be programming 102 :)

> >-- one could have order and no attribute=, or attribute=value and no 
> >order, still have things work out.
> 
> Yeah, but it would be more strain on the brain. 

We're having the age-old argument about redundancy.  How much redundancy
do we want in an on-the-wire encoding of a message?  ASN.1's BER's TLV
encodings have been problematic, in terms of bugs, meanwhile everyone is
always re-inventing PER and XML, which means that the debate never ends.

Let's not have this argument.  Instead let's agree that SCRAM is the way
it is and be done.  And keep in mind that several implementors have
prototypes already, or even code that awaits only consensus to get
deployed.  Changing SCRAM now for this little issue will cause those
implementors much hassle.

Nico
-- 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GCoT0t005540 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 16 Jun 2009 05:50:29 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5GCoTut005539; Tue, 16 Jun 2009 05:50:29 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from kalyani.oryx.com (kalyani.oryx.com [195.30.37.30]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5GCoGNZ005519 for <ietf-sasl@imc.org>; Tue, 16 Jun 2009 05:50:28 -0700 (MST) (envelope-from arnt@oryx.com)
Received: from kalyani.oryx.com (localhost [127.0.0.1]) by kalyani.oryx.com (Postfix) with ESMTP id 960C82E160; Tue, 16 Jun 2009 14:49:09 +0200 (CEST)
Received: from arnt@oryx.com (HELO lochnagar.oryx.com) by kalyani.oryx.com (Archiveopteryx 3.1.0) with esmtp id 1245156549-34806-34805/6/44 (5 recipients); Tue, 16 Jun 2009 14:49:09 +0200
Message-Id: <XZX0VWTahmAG/E+Qnehh4Q.md5@lochnagar.oryx.com>
Date: Tue, 16 Jun 2009 14:50:24 +0200
From: Arnt Gulbrandsen <arnt@oryx.com>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Subject: Re: Sequence of attributes in a SCRAM message
Cc: Tobias Markmann <tmarkmann@googlemail.com>, Dave Cridland <dave@cridland.net>, ietf-sasl@imc.org
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture> <20090615205620.GR1308@Sun.COM>
In-Reply-To: <20090615205620.GR1308@Sun.COM>
Content-Type: text/plain; format=flowed
Mime-Version: 1.0
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams writes:
> As for order within the SCRAM messages, I don't know the reason for 
> nor history of that, nor do I much care whether there's order in the 
> SCRAM messages. But I agree that having order _and_ attribute=value 
> adds unnecessary redundance

As far as I can tell, the order is necessary for the computer. The a=v 
stuff makes scram messages easier to read for people, and it's only 
about eight bytes.

> -- one could have order and no attribute=, or attribute=value and no 
> order, still have things work out.

Yeah, but it would be more strain on the brain. 
x=43241,43214,4321423,,4321432,432 is harder to decipher than 
x=43214,y=34123,=4324132,w=,e=421. Perhaps not THAT much harder, but I 
think it's worth eight bytes.

Might be good to add a parenthetical remark, perhaps "this ordering 
simplifies some implementation aspects, e.g. the hash calculation".

Arnt



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FLiGZ2046015 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:44:16 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FLiGvG046014; Mon, 15 Jun 2009 14:44:16 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FLiFI4046008 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:44:16 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [92.40.11.139] (92.40.11.139.sub.mbb.three.co.uk [92.40.11.139])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SjbArAAh5A95@rufus.isode.com>; Mon, 15 Jun 2009 22:44:13 +0100
Message-ID: <4A36C07D.4030604@isode.com>
Date: Mon, 15 Jun 2009 22:43:25 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Nicolas Williams <Nicolas.Williams@sun.com>
CC: ietf-sasl@imc.org, Tobias Markmann <tmarkmann@googlemail.com>
Subject: Re: Sequence of attributes in a SCRAM message
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture> <20090615205620.GR1308@Sun.COM>
In-Reply-To: <20090615205620.GR1308@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams wrote:

>On Mon, Jun 15, 2009 at 08:28:20PM +0100, Dave Cridland wrote:
>  
>
>>That's not answering the question, though - what is the purpose of  
>>this rule? (I don't recall it existing before, except that 'r' was at  
>>the end).
>>    
>>
>Sorry.  See Jeff's reply about the GS2 header vs. the SCRAM messages --
>at least that much order is required.  Within each of those order is not
>crucial.  The GS2 header is simple enough that having order in it
>actually simplifies things.
>  
>
Right.

>As for order within the SCRAM messages, I don't know the reason for nor
>history of that, nor do I much care whether there's order in the SCRAM
>messages.  But I agree that having order _and_ attribute=value adds
>unnecessary redundance -- one could have order and no attribute=, or
>attribute=value and no order, still have things work out.
>  
>
This was discussed on the mailing list (before SCRAM became a GS2 
mechanism) and there were some arguments made for making the order fixed.
While I don't really care about the issue, I would rather not revisit 
it, unless people have good arguments while the fixed order is harmful.

(Also note that there is no order enforced on extensions.)



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FLLMqU044690 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:21:22 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FLLMTb044689; Mon, 15 Jun 2009 14:21:22 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FLLLam044683 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:21:22 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5FLLLwh009004 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 21:21:21 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5FLLLBp024770 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 15:21:21 -0600 (MDT)
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 n5FKuN0D001712; Mon, 15 Jun 2009 15:56:23 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5FKuKP3001711; Mon, 15 Jun 2009 15:56:20 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 15 Jun 2009 15:56:20 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Dave Cridland <dave@cridland.net>
Cc: ietf-sasl@imc.org, Tobias Markmann <tmarkmann@googlemail.com>
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <20090615205620.GR1308@Sun.COM>
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM> <27893.1245094100.834041@puncture>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <27893.1245094100.834041@puncture>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Mon, Jun 15, 2009 at 08:28:20PM +0100, Dave Cridland wrote:
> That's not answering the question, though - what is the purpose of  
> this rule? (I don't recall it existing before, except that 'r' was at  
> the end).

Sorry.  See Jeff's reply about the GS2 header vs. the SCRAM messages --
at least that much order is required.  Within each of those order is not
crucial.  The GS2 header is simple enough that having order in it
actually simplifies things.

As for order within the SCRAM messages, I don't know the reason for nor
history of that, nor do I much care whether there's order in the SCRAM
messages.  But I agree that having order _and_ attribute=value adds
unnecessary redundance -- one could have order and no attribute=, or
attribute=value and no order, still have things work out.

Nico
-- 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FL5bN2043712 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 14:05:37 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FL5bbF043711; Mon, 15 Jun 2009 14:05:37 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from smtp-out.google.com (smtp-out.google.com [216.239.45.13]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FL5Pj1043694 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:05:36 -0700 (MST) (envelope-from robsiemb@google.com)
Received: from spaceape24.eur.corp.google.com (spaceape24.eur.corp.google.com [172.28.16.76]) by smtp-out.google.com with ESMTP id n5FL5Ode017512 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:05:25 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=google.com; s=beta; t=1245099925; bh=ZGcrlrokEChRfnF91bRuZb9N/tM=; h=DomainKey-Signature:MIME-Version:In-Reply-To:References:From:Date: Message-ID:Subject:To:Cc:Content-Type:X-System-Of-Record; b=stbJyd vR6dbNI8ZRrcKf43jzdzAerGze5wdujEOmWU6hkAPRSHiUSKcAIqtbUKE2yqwyLbXdF 4RaWM42Cdp1pw==
DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=mime-version:in-reply-to:references:from:date:message-id: subject:to:cc:content-type:x-system-of-record; b=dUnpFsKOet3FMsu9OcBJzcSOQ4SXjWQ9HC17icStO0T55YWzXEB+v9UkTLoNKmeqq tAL+/Hhl5gz6M4YQN2M6g==
Received: from yxe2 (yxe2.prod.google.com [10.190.2.2]) by spaceape24.eur.corp.google.com with ESMTP id n5FL57dJ024990 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:05:22 -0700
Received: by yxe2 with SMTP id 2so523130yxe.24 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 14:05:21 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.151.72.1 with SMTP id z1mr14134438ybk.15.1245099921155; Mon,  15 Jun 2009 14:05:21 -0700 (PDT)
In-Reply-To: <003701c9edfb$f7071320$e5153960$@com>
References: <003701c9edfb$f7071320$e5153960$@com>
From: Rob Siemborski <robsiemb@google.com>
Date: Mon, 15 Jun 2009 14:05:01 -0700
Message-ID: <5b93232d0906151405j35b11dd0wb7e7d3558a180e9a@mail.gmail.com>
Subject: Re: sasl authentication
To: Brian Andrus <toomuchit@gmail.com>
Cc: ietf-sasl@imc.org
Content-Type: multipart/alternative; boundary=001e680f181882a7f4046c696ad3
X-System-Of-Record: true
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--001e680f181882a7f4046c696ad3
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 15, 2009 at 1:57 PM, Brian Andrus <toomuchit@gmail.com> wrote:

>  Hello all.
>
> New to the list because I am trying to find out if/how I can authenticate
> via sasl for accounts whose username has the =91@=92 sign in them.
>
> There are a number in our ldap directory, which do authenticate for ssh,
> ftp, etc however when I try setting up postfix, it will not authenticate.=
 It
> seems to be breaking the username up into a realm as well.
>
>
>
> So, is it possible to get sasl to authenticate using an email looking
> username against pam/ldap?
>
> Or
>
> Where is the proper place to ask this?
>

cyrus-sasl@andrew.cmu.edu

-Rob

--=20
Rob Siemborski        |     PGP:0x5CE32FCC    |     robsiemb@google.com
Software Engineer     |                       |            650-623-6925

--001e680f181882a7f4046c696ad3
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<br><br><div class=3D"gmail_quote">On Mon, Jun 15, 2009 at 1:57 PM, Brian A=
ndrus <span dir=3D"ltr">&lt;<a href=3D"mailto:toomuchit@gmail.com">toomuchi=
t@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">










<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">

<div>

<p>Hello all.</p>

<p>New to the list because I am trying to find out if/how I can
authenticate via sasl for accounts whose username has the =91@=92 sign
in them.</p>

<p>There are a number in our ldap directory, which do
authenticate for ssh, ftp, etc however when I try setting up postfix, it wi=
ll
not authenticate. It seems to be breaking the username up into a realm as w=
ell.</p>

<p>=A0</p>

<p>So, is it possible to get sasl to authenticate using an
email looking username against pam/ldap?</p>

<p>Or</p>

<p>Where is the proper place to ask this?</p></div></div></blockquote><div>=
<br></div><div><a href=3D"mailto:cyrus-sasl@andrew.cmu.edu">cyrus-sasl@andr=
ew.cmu.edu</a></div><div><br></div><div>-Rob</div><div><br></div></div>-- <=
br>

Rob Siemborski =A0 =A0 =A0 =A0| =A0 =A0 PGP:0x5CE32FCC =A0 =A0| =A0 =A0 <a =
href=3D"mailto:robsiemb@google.com">robsiemb@google.com</a><br>Software Eng=
ineer =A0 =A0 | =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 | =A0 =A0 =A0 =
=A0 =A0 =A0650-623-6925<br><br>

--001e680f181882a7f4046c696ad3--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKwFuX043226 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 13:58:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FKwFY4043225; Mon, 15 Jun 2009 13:58:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from mail-px0-f177.google.com (mail-px0-f177.google.com [209.85.216.177]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKw48A043212 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:58:14 -0700 (MST) (envelope-from toomuchit@gmail.com)
Received: by pxi7 with SMTP id 7so51770pxi.16 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:58:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:subject:date :message-id:mime-version:content-type:x-mailer:thread-index :content-language; bh=W4itGpge+Jofuf+ebLBMNFZ6GUWRClRjpDC6hDF8OWk=; b=gTv65gdeB4xwVfCTL2WZKhG8TvPTmvaS5M8S+TMioWNms2UVZGswdFzgTyB0qAe9O5 UVkzH0YaLDInm9jHem2fJ9SaF4+FL3v1fhBo+M9PTDRSa585b5GnOCWhwxJOLGLuwJof hed4kS+SVPJunwMUuakTF7MsQoiokpHdSZG+0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:subject:date:message-id:mime-version:content-type:x-mailer :thread-index:content-language; b=gwCAG4yancel9uwc/PelBU2VvsCedSgxMRa9RWuR72FH0Aull+jy2RI6+hQwVjLN9X 5+VD5wAvnssCuUxiXYzLZYRlwR6QoxraMjyn7SMNjPcizsQ3c/76N13C+Y7ak/N1dWx1 mk3foA5wnl2atDDhZFRV/fvhdPPMUUS3vYrwY=
Received: by 10.142.144.9 with SMTP id r9mr3661965wfd.187.1245099483583; Mon, 15 Jun 2009 13:58:03 -0700 (PDT)
Received: from BrianPC (c-98-234-66-100.hsd1.ca.comcast.net [98.234.66.100]) by mx.google.com with ESMTPS id 30sm181484wfc.38.2009.06.15.13.58.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Jun 2009 13:58:03 -0700 (PDT)
From: "Brian Andrus" <toomuchit@gmail.com>
To: <ietf-sasl@imc.org>
Subject: sasl authentication
Date: Mon, 15 Jun 2009 13:57:57 -0700
Message-ID: <003701c9edfb$f7071320$e5153960$@com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_0038_01C9EDC1.4AA83B20"
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: Acnt+/XizdzMlT1eTXeQamq2zKa35A==
Content-Language: en-us
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

This is a multipart message in MIME format.

------=_NextPart_000_0038_01C9EDC1.4AA83B20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hello all.

New to the list because I am trying to find out if/how I can authenticate
via sasl for accounts whose username has the '@' sign in them.

There are a number in our ldap directory, which do authenticate for ssh,
ftp, etc however when I try setting up postfix, it will not authenticate. It
seems to be breaking the username up into a realm as well.

 

So, is it possible to get sasl to authenticate using an email looking
username against pam/ldap?

Or

Where is the proper place to ask this?

 

Thanks in advance for any insight.

 

Brian

 


------=_NextPart_000_0038_01C9EDC1.4AA83B20
Content-Type: text/html;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Hello all.<o:p></o:p></p>

<p class=3DMsoNormal>New to the list because I am trying to find out =
if/how I can
authenticate via sasl for accounts whose username has the =
&#8216;@&#8217; sign
in them.<o:p></o:p></p>

<p class=3DMsoNormal>There are a number in our ldap directory, which do
authenticate for ssh, ftp, etc however when I try setting up postfix, it =
will
not authenticate. It seems to be breaking the username up into a realm =
as well.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>So, is it possible to get sasl to authenticate =
using an
email looking username against pam/ldap?<o:p></o:p></p>

<p class=3DMsoNormal>Or<o:p></o:p></p>

<p class=3DMsoNormal>Where is the proper place to ask =
this?<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Thanks in advance for any insight.<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Brian<o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</body>

</html>

------=_NextPart_000_0038_01C9EDC1.4AA83B20--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKlhXj042571 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 13:47:43 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FKlhAO042570; Mon, 15 Jun 2009 13:47:43 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKlVS8042561 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:47:42 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [92.40.11.139] (92.40.11.139.sub.mbb.three.co.uk [92.40.11.139])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SjazYAAh5JsW@rufus.isode.com>; Mon, 15 Jun 2009 21:47:29 +0100
Message-ID: <4A36B325.5030908@isode.com>
Date: Mon, 15 Jun 2009 21:46:29 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Tobias Markmann <tmarkmann@googlemail.com>
CC: ietf-sasl@imc.org
Subject: Re: Sequence of attributes in a SCRAM message
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
In-Reply-To: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Tobias Markmann wrote:

> Hi,
>
> From Section 5.1 of the latest draft:
>
>Note that the order of attributes in client or server messages is
>   fixed, with the exception of extension attributes (described by the
>   "extensions" ABNF production), which can appear in any order in the
>   designated positions.  See the ABNF section for authoritative
>   reference.
>
>  Does this mean that during serialization, attribute 'a' goes first, 
> then 'n', 'm', 'r' and so on? If so why the restriction on sequence?

This restriction is to simplify implementations.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKgc0c042323 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 13:42:38 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FKgcLW042322; Mon, 15 Jun 2009 13:42:38 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from jackfruit.srv.cs.cmu.edu (JACKFRUIT.SRV.CS.CMU.EDU [128.2.201.16]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FKgQt7042302 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:42:37 -0700 (MST) (envelope-from jhutz@cmu.edu)
Received: from [192.168.1.113] (SIRIUS.FAC.CS.CMU.EDU [128.2.216.216]) (authenticated bits=0) by jackfruit.srv.cs.cmu.edu (8.13.6/8.13.6) with ESMTP id n5FKfUle012296 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 16:42:21 -0400 (EDT)
Date: Mon, 15 Jun 2009 16:40:17 -0400
From: Jeffrey Hutzelman <jhutz@cmu.edu>
To: Dave Cridland <dave@cridland.net>, Nicolas Williams <Nicolas.Williams@sun.com>, ietf-sasl@imc.org, Tobias Markmann <tmarkmann@googlemail.com>
cc: jhutz@cmu.edu
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <6FD5DE7A2124A5BB31623DEC@B182BF00AF5DB930FC0FAF33>
X-Mailer: Mulberry/4.0.8 (Linux/x86)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Scanned-By: mimedefang-cmuscs on 128.2.201.16
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--On Monday, June 15, 2009 08:28:20 PM +0100 Dave Cridland 
<dave@cridland.net> wrote:

>
> On Mon Jun 15 19:47:32 2009, Nicolas Williams wrote:
>> On Mon, Jun 15, 2009 at 08:27:41PM +0200, Tobias Markmann wrote:
>> > Hi,
>> > From Section 5.1 of the latest draft:
>> >
>> > > Note that the order of attributes in client or server messages
>> is
>> > >    fixed, with the exception of extension attributes (described
>> by the
>> > >    "extensions" ABNF production), which can appear in any order
>> in the
>> > >    designated positions.  See the ABNF section for authoritative
>> > >    reference.
>> > >
>> > >
>> > Does this mean that during serialization, attribute 'a' goes
>> first, then
>> > 'n', 'm', 'r' and so on? If so why the restriction on sequence?
>>
>> The ABNF itself provides the order.  See the ABNF.
>
> That's not answering the question, though - what is the purpose of this
> rule? (I don't recall it existing before, except that 'r' was at the end).

It's not new -- the ABNF has always specified a sequence of particular 
attributes, some of which might be optional, not a sequence of aribtrary 
"key=value" pairs and a set of permissible keys.

There are several reasons for the ordering requirement, but much of it 
boils down to the fact that some of the attributes come from the GS2 layer, 
while others are SCRAM-specific.  The modularity needed to allow GS2 + 
GSS-SCRAM to interoperate with a pure-SASL SCRAM implementation imposes 
certain requirements.  One is that all of the bits of a message that are 
SCRAM-specific are grouped together and easily separable, so that GS2 can 
treat them as a single opaque string, since it cannot know the details of 
SCRAM.  Another has to do with the hash calculation; we need to be sure 
that the value being hashed is the same on both sides, which means either 
requiring a particular order for attributes or requiring implementations to 
pick out the attributes to be hashed and assembling them together in the 
right order.  This is probably doable, but "the right order" would have to 
group together everything passed down from the GS2 layer, including the 
actual channel bindings, because GSS-SCRAM cannot know that it is being 
called by GS2 and thus must treat the GSS-API CB application data (where 
GS2 puts the actual channel bindings and also things like the authzid and 
CB indicator flag) as an opaque string.

In short, we don't have to require a specific sequence of attributes, but 
allowing them to be reordered completely arbitrarily would break the 
protocol, and the constraints on how they can be reordered would be complex 
to describe and to implement.

I don't believe there is anything that would break if an implementation 
were to accept out-of-order attributes, as long as the hashes are computed 
in the same way by both sides (either in the order sent, or in the order 
specified in the protocol).  But I'd have to read the document fairly 
carefully to be sure there were no security ramifications.

-- Jeff



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FJSV3Z037836 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 12:28:31 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FJSVLT037835; Mon, 15 Jun 2009 12:28:31 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from peirce.dave.cridland.net (peirce.dave.cridland.net [217.155.137.61]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FJSTcP037828 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 12:28:30 -0700 (MST) (envelope-from dave@cridland.net)
Received: from puncture ((unknown) [217.155.137.60]) by peirce.dave.cridland.net (submission) via TCP with ESMTPA id <Sjag2AAnObBw@peirce.dave.cridland.net>; Mon, 15 Jun 2009 20:28:25 +0100
X-SMTP-Protocol-Errors: NORDNS
Subject: Re: Sequence of attributes in a SCRAM message
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com> <20090615184732.GL1308@Sun.COM>
In-Reply-To: <20090615184732.GL1308@Sun.COM>
MIME-Version: 1.0
Message-Id: <27893.1245094100.834041@puncture>
Date: Mon, 15 Jun 2009 20:28:20 +0100
From: Dave Cridland <dave@cridland.net>
To: Nicolas Williams <Nicolas.Williams@sun.com>, <ietf-sasl@imc.org>, Tobias Markmann <tmarkmann@googlemail.com>
Content-Type: text/plain; delsp="yes"; charset="us-ascii"; format="flowed"
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Mon Jun 15 19:47:32 2009, Nicolas Williams wrote:
> On Mon, Jun 15, 2009 at 08:27:41PM +0200, Tobias Markmann wrote:
> > Hi,
> > From Section 5.1 of the latest draft:
> >
> > > Note that the order of attributes in client or server messages  
> is
> > >    fixed, with the exception of extension attributes (described  
> by the
> > >    "extensions" ABNF production), which can appear in any order  
> in the
> > >    designated positions.  See the ABNF section for authoritative
> > >    reference.
> > >
> > >
> > Does this mean that during serialization, attribute 'a' goes  
> first, then
> > 'n', 'm', 'r' and so on? If so why the restriction on sequence?
> 
> The ABNF itself provides the order.  See the ABNF.

That's not answering the question, though - what is the purpose of  
this rule? (I don't recall it existing before, except that 'r' was at  
the end).

Dave.
-- 
Dave Cridland - mailto:dave@cridland.net - xmpp:dwd@dave.cridland.net
  - acap://acap.dave.cridland.net/byowner/user/dwd/bookmarks/
  - http://dave.cridland.net/
Infotrope Polymer - ACAP, IMAP, ESMTP, and Lemonade



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FJ5Fne036714 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 12:05:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FJ5Fu6036713; Mon, 15 Jun 2009 12:05:15 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FJ53Wt036701 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 12:05:13 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5FJ52UU007335 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 19:05:03 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 n5FJ526G048971 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 13:05:02 -0600 (MDT)
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 n5FIlXB4001604; Mon, 15 Jun 2009 13:47:33 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5FIlWWV001603; Mon, 15 Jun 2009 13:47:32 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 15 Jun 2009 13:47:32 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Tobias Markmann <tmarkmann@googlemail.com>
Cc: ietf-sasl@imc.org
Subject: Re: Sequence of attributes in a SCRAM message
Message-ID: <20090615184732.GL1308@Sun.COM>
References: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Mon, Jun 15, 2009 at 08:27:41PM +0200, Tobias Markmann wrote:
> Hi,
> From Section 5.1 of the latest draft:
> 
> > Note that the order of attributes in client or server messages is
> >    fixed, with the exception of extension attributes (described by the
> >    "extensions" ABNF production), which can appear in any order in the
> >    designated positions.  See the ABNF section for authoritative
> >    reference.
> >
> >
> Does this mean that during serialization, attribute 'a' goes first, then
> 'n', 'm', 'r' and so on? If so why the restriction on sequence?

The ABNF itself provides the order.  See the ABNF.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FIRsAB034704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 15 Jun 2009 11:27:54 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5FIRsgQ034703; Mon, 15 Jun 2009 11:27:54 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from mail-ew0-f217.google.com (mail-ew0-f217.google.com [209.85.219.217]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5FIRg3D034683 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 11:27:53 -0700 (MST) (envelope-from tmarkmann@googlemail.com)
Received: by ewy17 with SMTP id 17so4509304ewy.10 for <ietf-sasl@imc.org>; Mon, 15 Jun 2009 11:27:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=V9vX8NIqHE1lrSwR78SiaYYPz1QU+O9W7k5w4rdOTOI=; b=GLvb5QLvXMM7oFZZpza3efI30ZQC4J1FZPuFC6LnUqpPq2McPL0MraUyatuY3NgAAq 87FVFRK2hy5pOhjSs0YB7Jvfqnb5184JfKYSfjG8pNcHtmF/F2LoQBGOfs0cNjfnA1YT tOcLE9z35oTtGQDitAwuBOWag9lh87GLo9EGw=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ADhonyKOAbyQLkeulmeNJN5cS7ZdBAcjO7qJ9ndLFi6SgeuZudc8ec7pfR7yZcVvEL 5fMhuHYrwwP/cNvpCZDdtAwh00wCoYRH9s2Kh9312/Omw5igBJbT0DmadiwN7L9KjzGr 3wHI/bUUlsZkS8hW/MFOvRSPUKDo1eudDNB2g=
MIME-Version: 1.0
Received: by 10.210.17.14 with SMTP id 14mr3640433ebq.71.1245090461676; Mon,  15 Jun 2009 11:27:41 -0700 (PDT)
Date: Mon, 15 Jun 2009 20:27:41 +0200
Message-ID: <5cfc0a8e0906151127q391654bbm9d2cd375fce0d034@mail.gmail.com>
Subject: Sequence of attributes in a SCRAM message
From: Tobias Markmann <tmarkmann@googlemail.com>
To: ietf-sasl@imc.org
Content-Type: multipart/alternative; boundary=0015174be6eaae74ad046c673681
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

--0015174be6eaae74ad046c673681
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,
>From Section 5.1 of the latest draft:

> Note that the order of attributes in client or server messages is
>    fixed, with the exception of extension attributes (described by the
>    "extensions" ABNF production), which can appear in any order in the
>    designated positions.  See the ABNF section for authoritative
>    reference.
>
>
Does this mean that during serialization, attribute 'a' goes first, then
'n', 'm', 'r' and so on? If so why the restriction on sequence?
Cheers,
Tobias Markmann

--0015174be6eaae74ad046c673681
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi,<div><br></div><div>From Section 5.1 of the latest draft:</div><blockquo=
te class=3D"gmail_quote" style=3D"margin-top: 0px; margin-right: 0px; margi=
n-bottom: 0px; margin-left: 0.8ex; border-left-width: 1px; border-left-colo=
r: rgb(204, 204, 204); border-left-style: solid; padding-left: 1ex; ">
<span class=3D"Apple-style-span" style=3D"font-family: &#39;Hoefler Text&#3=
9;; font-size: medium; "><pre style=3D"word-wrap: break-word; white-space: =
pre-wrap; ">Note that the order of attributes in client or server messages =
is
   fixed, with the exception of extension attributes (described by the
   &quot;extensions&quot; ABNF production), which can appear in any order i=
n the
   designated positions.  See the ABNF section for authoritative
   reference.</pre></span></blockquote><div>=C2=A0</div>Does this mean that=
 during serialization, attribute &#39;a&#39; goes first, then &#39;n&#39;, =
&#39;m&#39;, &#39;r&#39; and so on? If so why the restriction on sequence?<=
div>
<br>Cheers,<br>Tobias Markmann</div>

--0015174be6eaae74ad046c673681--



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5CIbUhW017984 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jun 2009 11:37:30 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5CIbUap017983; Fri, 12 Jun 2009 11:37:30 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from sca-ea-mail-3.sun.com (sca-ea-mail-3.Sun.COM [192.18.43.21]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5CIbJNG017958 for <ietf-sasl@imc.org>; Fri, 12 Jun 2009 11:37:29 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5CIbIfY022065 for <ietf-sasl@imc.org>; Fri, 12 Jun 2009 18:37:18 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n5CIbHv0040149 for <ietf-sasl@imc.org>; Fri, 12 Jun 2009 12:37:18 -0600 (MDT)
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 n5CIRDuv007729; Fri, 12 Jun 2009 13:27:13 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5CIRCiO007728; Fri, 12 Jun 2009 13:27:12 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Fri, 12 Jun 2009 13:27:12 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: ietf-sasl@imc.org
Subject: Re: New version of draft-altman-tls-channel-bindings
Message-ID: <20090612182712.GA1049@Sun.COM>
References: <20090611182608.GU1049@Sun.COM> <87ski5erfu.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87ski5erfu.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Fri, Jun 12, 2009 at 11:23:33AM +0200, Simon Josefsson wrote:
> The registration sections 3-5 looks fine to me.
> 
> I have two mild concerns on section 6 and 7:
> 
> Section 6 mandate rather general restrictions on application protocol
> specifications that appear to apply beyond the channel binding types
> defined in the document.  It this the document to do that?  It appears
> as if the text is written to apply to draft-josefsson-sasl-tls-cb too.

What it mandates should be entirely non-controversial, I thought:

   Specifically, application protocol specifications MUST indicate at
   least one mandatory to implement channel binding type, MAY specify a
   negotiation protocol, MAY allow for out-of-band negotiation or
   configuration, and SHOULD prefer 'tls-unique' over 'tls-server-end-
   point'.

This doesn't say what the apps must require, just that they must require
something.  It doesn't dictate specifics.

There's also a recommendation:

                                      ...  However, it is RECOMMENDED
   that application protocols making use of TLS channel bindings, use
   'tls-unique' exclusively, except, perhaps, where server-side proxies
   are common in deployments of an application protocol.  ...

I thought that too would be non-controversial as it is just a
recommendation.

> Section 7 suggests implementation requirements on TLS implementations.

Yes.

> GnuTLS has APIs that allows applications to implement tls-unique and
> tls-server-end-point, but these interfaces would not follow the MUST in
> section 7 at least the way I read them.  I'd prefer to leave API design
> to implementers, and hence remove the RFC 2119 keywords from this
> section, and have the section provide guidance rather than norms.

The section 7 text says that either the TLS implementation must either
provide an interface for extracting channel bindings by channel binding
type (something like: getCB(connection, cb_type) -> CB data), or
interfaces for extracting those items that are used to construct the CB
data (something like: getFirstClientFinishedMsg(connection),
getFirstServerFinishedMsg(connection), getServerEECert(connection)).

Are there other possibilities that I did not consider?  Why is what I
wrote controversial?

Nico
-- 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5C9NrEE083150 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 12 Jun 2009 02:23:53 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5C9Nrpx083149; Fri, 12 Jun 2009 02:23:53 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5C9NddZ083137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Fri, 12 Jun 2009 02:23:51 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (c80-216-24-60.bredband.comhem.se [80.216.24.60]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n5C9NZfR000877 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 12 Jun 2009 11:23:37 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: ietf-sasl@imc.org
Subject: Re: New version of draft-altman-tls-channel-bindings
References: <20090611182608.GU1049@Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090612:nicolas.williams@sun.com::7mmrQf4j2IhaUc/X:3JxV
X-Hashcash: 1:22:090612:ietf-sasl@imc.org::6Vdo2D/qY7fBTOhn:8KK2
Date: Fri, 12 Jun 2009 11:23:33 +0200
In-Reply-To: <20090611182608.GU1049@Sun.COM> (Nicolas Williams's message of "Thu, 11 Jun 2009 13:26:08 -0500")
Message-ID: <87ski5erfu.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, score=-0.0 required=5.0 tests=AWL,BAYES_00, DATE_IN_FUTURE_24_48,RDNS_DYNAMIC,SPF_FAIL autolearn=no version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on yxa-v.extundo.com
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

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

> I've just posted draft-altman-tls-channel-bindings-04.  This version
> re-submits the existing three TLS channel bindings types following
> Larry's note to the IESG transferring "ownership" of his channel binding
> types (Jeff will do so soon for his as well, I think).
>
> References were added, applicability text (based, in part, on
> discussions in this WG) and security considerations text was added, as
> well as minor clarifications.
>
> Please review.  Thanks,

The registration sections 3-5 looks fine to me.

I have two mild concerns on section 6 and 7:

Section 6 mandate rather general restrictions on application protocol
specifications that appear to apply beyond the channel binding types
defined in the document.  It this the document to do that?  It appears
as if the text is written to apply to draft-josefsson-sasl-tls-cb too.

Section 7 suggests implementation requirements on TLS implementations.
GnuTLS has APIs that allows applications to implement tls-unique and
tls-server-end-point, but these interfaces would not follow the MUST in
section 7 at least the way I read them.  I'd prefer to leave API design
to implementers, and hence remove the RFC 2119 keywords from this
section, and have the section provide guidance rather than norms.

Thanks,
/Simon



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5BIaLEF038579 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 11 Jun 2009 11:36:21 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5BIaLCM038578; Thu, 11 Jun 2009 11:36:21 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from sca-ea-mail-3.sun.com (sca-ea-mail-3.Sun.COM [192.18.43.21]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5BIaAiI038566 for <ietf-sasl@imc.org>; Thu, 11 Jun 2009 11:36:21 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by sca-ea-mail-3.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n5BIaA3S017360 for <ietf-sasl@imc.org>; Thu, 11 Jun 2009 18:36:10 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 n5BIaAeX046799 for <ietf-sasl@imc.org>; Thu, 11 Jun 2009 12:36:10 -0600 (MDT)
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 n5BIQAvZ006800 for <ietf-sasl@imc.org>; Thu, 11 Jun 2009 13:26:10 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5BIQ8ak006799 for ietf-sasl@imc.org; Thu, 11 Jun 2009 13:26:08 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Thu, 11 Jun 2009 13:26:08 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: ietf-sasl@imc.org
Subject: New version of draft-altman-tls-channel-bindings
Message-ID: <20090611182608.GU1049@Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

I've just posted draft-altman-tls-channel-bindings-04.  This version
re-submits the existing three TLS channel bindings types following
Larry's note to the IESG transferring "ownership" of his channel binding
types (Jeff will do so soon for his as well, I think).

References were added, applicability text (based, in part, on
discussions in this WG) and security considerations text was added, as
well as minor clarifications.

Please review.  Thanks,

Nico
-- 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n58GEB19009184 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jun 2009 09:14:11 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n58GEB00009183; Mon, 8 Jun 2009 09:14:11 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from sca-ea-mail-2.sun.com (sca-ea-mail-2.Sun.COM [192.18.43.25]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n58GDuwl009162 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-sasl@imc.org>; Mon, 8 Jun 2009 09:14:07 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-02.central.sun.com ([129.147.62.5]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n58GDu1p008967 for <ietf-sasl@imc.org>; Mon, 8 Jun 2009 16:13:56 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 n58GDtB6018642 for <ietf-sasl@imc.org>; Mon, 8 Jun 2009 10:13:55 -0600 (MDT)
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 n58G3wAg004273; Mon, 8 Jun 2009 11:03:58 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n58G3vJ6004272; Mon, 8 Jun 2009 11:03:57 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Mon, 8 Jun 2009 11:03:57 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Sam Hartman <hartmans-ietf@mit.edu>
Cc: Kurt Zeilenga <Kurt.Zeilenga@isode.com>, Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090608160357.GX1049@Sun.COM>
References: <4A1F06CF.80505@isode.com> <75FB32D2-2238-442D-A741-8DF1174970FF@Isode.com> <tsl8wk2rel0.fsf@mit.edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <tsl8wk2rel0.fsf@mit.edu>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Mon, Jun 08, 2009 at 10:21:31AM -0400, Sam Hartman wrote:
>     Kurt> After some additional thought and consideration, I change my
>     Kurt> preference to:
> 
>     Kurt> 4a (just change the text to require tls-unique) 
> 
> As I indicate, I believe support for channel binding types other than
> tls-unique is an absolute requirement.  While I prefer for us to have
> downgrade protection, I don't see that as an absolute requirement.
> So, I think we at least need a mechanism to say what channel binding
> type we've used if it is not tls-unique.  That's not downgrade
> protection; it is consistency with 5056.

Technically we don't even need that much, but I'd very much like to have
at least that much.

I too think that future downgrade protection is not critical right now.
In fact, I can think of ways to do all three (or is it four?) proposed
future CB type nego schemes without adding downgrade protection now
(it's just that to me the security analysis seemed easier with explicit
downgrade protection).

Nico
-- 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n58ELqAF003737 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 8 Jun 2009 07:21:52 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n58ELqcA003736; Mon, 8 Jun 2009 07:21:52 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n58ELfMC003726 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-sasl@imc.org>; Mon, 8 Jun 2009 07:21:52 -0700 (MST) (envelope-from hartmans@mit.edu)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id F0FC74141; Mon,  8 Jun 2009 10:21:31 -0400 (EDT)
To: Kurt Zeilenga <Kurt.Zeilenga@isode.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <75FB32D2-2238-442D-A741-8DF1174970FF@Isode.com>
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Mon, 08 Jun 2009 10:21:31 -0400
In-Reply-To: <75FB32D2-2238-442D-A741-8DF1174970FF@Isode.com> (Kurt Zeilenga's message of "Sun\, 7 Jun 2009 05\:12\:20 -0700")
Message-ID: <tsl8wk2rel0.fsf@mit.edu>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

>>>>> "Kurt" == Kurt Zeilenga <Kurt.Zeilenga@isode.com> writes:

    Kurt> After some additional thought and consideration, I change my
    Kurt> preference to:

    Kurt> 4a (just change the text to require tls-unique) 

As I indicate, I believe support for channel binding types other than
tls-unique is an absolute requirement.  While I prefer for us to have
downgrade protection, I don't see that as an absolute requirement.
So, I think we at least need a mechanism to say what channel binding
type we've used if it is not tls-unique.  That's not downgrade
protection; it is consistency with 5056.

    Kurt> 5 (adds some
    Kurt> words that additional text that channel bind type agility is
    Kurt> provided via mechanism name).

I'm fairly strongly against this option.


    Kurt> I have decided not to support providing any channeling
    Kurt> binding "downgrade" protection in the mechanism.  

As I indicated, I believe this would be a good idea, and would
certainly rather the WG consensus be that we had such a mechanism, but
understand if we don't go there.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n57CCZpP042104 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sun, 7 Jun 2009 05:12:35 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n57CCZKR042103; Sun, 7 Jun 2009 05:12:35 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from boole.openldap.org (boole.openldap.org [204.152.186.50]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n57CCO2F042064 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-sasl@imc.org>; Sun, 7 Jun 2009 05:12:35 -0700 (MST) (envelope-from Kurt.Zeilenga@Isode.com)
Received: from [192.168.1.102] (75-141-233-128.dhcp.nv.charter.com [75.141.233.128] (may be forged)) (authenticated bits=0) by boole.openldap.org (8.14.3/8.14.3) with ESMTP id n57CCKsh031194; Sun, 7 Jun 2009 12:12:21 GMT (envelope-from Kurt.Zeilenga@Isode.com)
Cc: SASL WG <ietf-sasl@imc.org>
Message-Id: <75FB32D2-2238-442D-A741-8DF1174970FF@Isode.com>
From: Kurt Zeilenga <Kurt.Zeilenga@isode.com>
To: Alexey Melnikov <alexey.melnikov@isode.com>
In-Reply-To: <4A1F06CF.80505@isode.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Mime-Version: 1.0 (Apple Message framework v935.3)
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Date: Sun, 7 Jun 2009 05:12:20 -0700
References: <4A1F06CF.80505@isode.com>
X-Mailer: Apple Mail (2.935.3)
X-Spam-Status: No, score=-4.4 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 autolearn=ham version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on boole.openldap.org
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

After some additional thought and consideration, I change my  
preference to:

4a (just change the text to require tls-unique)
5 (adds some words that additional text that channel bind type agility  
is provided via mechanism name).

I have decided not to support providing any channeling binding  
"downgrade" protection in the mechanism.  This because I believe the  
mechanism downgrade mechanism is sufficient to protect against attacks  
I think would be likely, and the suggested approaches not necessarily  
sufficient to cover attacks that might eventual come.   For instance,  
if we were to not only have a channel binding type negotiation  
facility (such as what Jeffrey proposed) but a Security Label  
negotiation facility, and maybe a hash algorithm negotiation facility,  
or maybe a combined "mechanism property" negotiation facility, I would  
want that negotiation facility to provide a downgrade protection.  Off  
hand, I cannot think of how to deal with downgrade now without  
discussing the particulars of the negotiation facility, so I rather  
defer this (and just hope we have enough extension capability in GS2/ 
SCRAM) to deal with such).

-- Kurt

On May 28, 2009, at 2:49 PM, Alexey Melnikov wrote:

>
> I've discussed channel bindings with Nico in jabber and we agreed  
> that we need to get WG consensus on how TLS channel bindings should  
> be used with SCRAM.
> Please provide an orded list of alternatives you find acceptable  
> from the choices listed below. (Please restrict discussions of  
> variants of these choices at the moment. I will do another poll on  
> such choices later, depending on the outcome of this poll. Also,  
> please read notes for the choices before answering). Please answer  
> the poll by the end of June 7th.
>
> 1). SCRAM should just use a single allowed TLS channel binding and  
> don't have any negotiation of other TLS channel bindings (*) (**)
> a). the default is tls-unique
> b). the default is tls-server-end-point
> 2). SCRAM should just use tls-server-end-point, fallback to tls- 
> unique, no negotiation of other TLS channel bindings (*)
> 3). SCRAM should always use channel binding negotiation (*)
> 4). SCRAM should have a default TLS channel binding with optional  
> negotiation of TLS channel bindings (*)
> a). the default is tls-unique
> b). the default is
> 5). I have another opinion [this is for the case when there is some  
> valid choice which you think should be considered by the WG]
>
> Notes:
> (*) - whether such negotiation happens inside or outside of SCRAM
> (**) - channel binding negotiation can be added later on
>



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LvG66057231 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:57:16 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55LvGYV057230; Fri, 5 Jun 2009 14:57:16 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LvF5u057224 for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 14:57:16 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [94.197.221.233] (94.197.221.233.threembb.co.uk [94.197.221.233])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SimUuAAh5Lzp@rufus.isode.com>; Fri, 5 Jun 2009 22:57:14 +0100
Message-ID: <4A299498.8020703@isode.com>
Date: Fri, 05 Jun 2009 22:56:40 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Simon Josefsson <simon@josefsson.org>
CC: Nicolas Williams <Nicolas.Williams@sun.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org> <20090603132837.GA26728@Sun.COM>
In-Reply-To: <20090603132837.GA26728@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams wrote:

>On Wed, Jun 03, 2009 at 07:31:45AM +0200, Simon Josefsson wrote:
>  
>
>>Before I update GS2 with that, what is the chance of making these
>>changes to SCRAM?  Alexey?
>>    
>>
Simon, I suggest you do changes to GS2 (hopefully taking into 
consideration a couple of minor comments I've just sent out), then I 
copy them to SCRAM.
If I dislike something, I will complain :-)



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LsDb5057096 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:54:13 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55LsDX2057095; Fri, 5 Jun 2009 14:54:13 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LsCXm057089 for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 14:54:12 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [94.197.221.233] (94.197.221.233.threembb.co.uk [94.197.221.233])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SimUAAAh5FHF@rufus.isode.com>; Fri, 5 Jun 2009 22:54:10 +0100
Message-ID: <4A2993DD.1010005@isode.com>
Date: Fri, 05 Jun 2009 22:53:33 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Jeffrey Hutzelman <jhutz@cmu.edu>
CC: Simon Josefsson <simon@josefsson.org>, Nicolas Williams <Nicolas.Williams@sun.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090529202232.GT29258@Sun.COM> <874ov3tyl6.fsf@mocca.josefsson.org> <DC91912DC3C8FC8317B3C150@atlantis.pc.cs.cmu.edu>
In-Reply-To: <DC91912DC3C8FC8317B3C150@atlantis.pc.cs.cmu.edu>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Jeffrey Hutzelman wrote:

> --On Friday, May 29, 2009 10:59:17 PM +0200 Simon Josefsson 
> <simon@josefsson.org> wrote:

 [...]

>> I'm glad you like it.  I'm not entirely happy with it: you can't parse
>> it using a var[=value] parser, you need to inspect the string character
>> by character in the beginning.  One alternative would be (compare with
>> the examples in the document):
>
> I see a couple of problems with the grammar.  One is that in the 'p' 
> and 'y' cases, you get two consecutive commas if there is no authzid.

-1. I think it would be better to use 2 commas, because this is a sure 
sign that the GS2 header has ended.

> The other is that in the 'n' case, you get no comma before the 
> authzid, if there is one.

+1.

> I think it would be better to always have a comma after the [pny] 
> field, and another after the a=authzid iff it is present.
>
> I have no objection to the [py]= syntax you suggest; that might make 
> parsing easier, and we're changing the format of that field anyway.
>
> I see no reason to include a comma after the 'F' prefix.

+1.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55Lq3g9057039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:52:03 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55Lq3IU057038; Fri, 5 Jun 2009 14:52:03 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55Lq2vN057032 for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 14:52:03 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [94.197.221.233] (94.197.221.233.threembb.co.uk [94.197.221.233])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SimTfwAh5G-5@rufus.isode.com>; Fri, 5 Jun 2009 22:52:01 +0100
Message-ID: <4A29935F.1050200@isode.com>
Date: Fri, 05 Jun 2009 22:51:27 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Simon Josefsson <simon@josefsson.org>
CC: Nicolas Williams <Nicolas.Williams@sun.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090529202232.GT29258@Sun.COM> <874ov3tyl6.fsf@mocca.josefsson.org>
In-Reply-To: <874ov3tyl6.fsf@mocca.josefsson.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Simon Josefsson wrote:

>Nicolas Williams <Nicolas.Williams@sun.com> writes:
>  
>
>>On Fri, May 29, 2009 at 08:29:42PM +0200, Simon Josefsson wrote:
>>    
>>
>>>Nicolas Williams <Nicolas.Williams@sun.com> writes:
>>>      
>>>
 [...]

>>Also, I like your ABNF.  I had in mind using something like t=<type> and
>>t=<type>[:<type>[:...]], but your approach strikes me as better.
>>    
>>
>I'm glad you like it.  I'm not entirely happy with it: you can't parse
>it using a var[=value] parser, you need to inspect the string character
>by character in the beginning.  One alternative would be (compare with
>the examples in the document):
>
>Example #1: n,a=someuser,...
>Example #2: n,...
>Example #3: F,n,...
>  
>
I think we need comma after "n" (for consistency and ease of parsing) 
and we don't need a comma after F.

>Example #4: p=tls-unique,a=someuser,...
>Example #5: p=tls-unique,...
>Example #6: p=tls-server-end-point,...
>Example #7: y=tls-unique:tls-server-end-point,a=someuser,...
>
>However I didn't want to make unrelated changes at this point.
>
>Also, that SCRAM uses var[=value] doesn't mean GS2 needs to.
>
>I'm not sure.
>
>Thoughts?
>  
>



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55Ll6ZF056891 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 14:47:06 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55Ll6On056890; Fri, 5 Jun 2009 14:47:06 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55LksW1056875 for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 14:47:05 -0700 (MST) (envelope-from alexey.melnikov@isode.com)
Received: from [94.197.221.233] (94.197.221.233.threembb.co.uk [94.197.221.233])  by rufus.isode.com (submission channel) via TCP with ESMTPA  id <SimSSgAh5GSc@rufus.isode.com>; Fri, 5 Jun 2009 22:46:52 +0100
Message-ID: <4A299227.6040802@isode.com>
Date: Fri, 05 Jun 2009 22:46:15 +0100
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: Nicolas Williams <Nicolas.Williams@sun.com>
CC: Simon Josefsson <simon@josefsson.org>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090529202232.GT29258@Sun.COM>
In-Reply-To: <20090529202232.GT29258@Sun.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Nicolas Williams wrote:

>On Fri, May 29, 2009 at 08:29:42PM +0200, Simon Josefsson wrote:
>  
>
 [...]

>>Check the examples, they are updated and hopefully give you a quick idea
>>of how the protocol will look like.
>>
>>Thoughts?
>>    
>>
>Awesome.  Thanks!
>
>Alexey, can you adapt Simon's changes to GS2 to SCRAM?
>  
>
Yes, your proposal seems fine to me. (I might have some minor comments 
later).



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55KVdk0053194 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 5 Jun 2009 13:31:39 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n55KVdUK053193; Fri, 5 Jun 2009 13:31:39 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from carter-zimmerman.suchdamage.org (carter-zimmerman.suchdamage.org [69.25.196.178]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n55KVR0H053186 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <ietf-sasl@imc.org>; Fri, 5 Jun 2009 13:31:38 -0700 (MST) (envelope-from hartmans@mit.edu)
Received: by carter-zimmerman.suchdamage.org (Postfix, from userid 8042) id E790C4141; Fri,  5 Jun 2009 16:31:24 -0400 (EDT)
To: ietf-sasl@imc.org
Subject: GS2 and SCRAM channel bindings
From: Sam Hartman <hartmans-ietf@mit.edu>
Date: Fri, 05 Jun 2009 16:31:24 -0400
Message-ID: <tslr5xytobn.fsf@mit.edu>
User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Hi.  I believe I've read enough of the mail and swapped in enough
state to have an informed opinion on the current channel bindings
discussions.

I believe that gs2 and scram should specify TLS unique channel
bindings as mandatory to implement when TLS channel bindings are used.

I believe that what we standardize today needs to support other
channel binding types besides tls-unique.  I'm not particularly
concerned with tls-server-endpoint although I believe we should keep
options open for that.  I believe that GS2 may be used in environments
where the channel type is not TLS, so the standard needs to support
that.  I cannot support publication of a GS2 or SCRAM standard that is
limited to TLS channel binding.

I'm dubious that we will ever need TLS channel binding negotiation, or
that if we do that it should happen in SASL rather than TLS.  In most
cases I think that the application will know what channel will be used
before SASL starts.  I've heard Kurt's arguments that we want to
negotiate channel binding type and allow a server to have SASL
mechanism selection influence channel binding type selection.  I do
not find these arguments compelling.



As such, I support a proposal where we carry the type of the channel
to be bound in GS2/SCRAM.  I'm fine carrying that all the time; I'm
fine carrying that only when it is not tls-unique.

I think it would be a good idea to have a way to carry additional
channel types without needing to generate new GS2 mechanisms.  I'm
happy with non-critical extensions at the GS2 layer as a way to do
that.  While I prefer having this option, I could support publication
of GS2/SCRAM that did not support additional channel binding types
being carried.

I'm reasonably happy with all the ABNF thrown around on the list that
is consistent with my goals.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n54Frtrs058957 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Jun 2009 08:53:55 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n54Frt9l058956; Thu, 4 Jun 2009 08:53:55 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n54FrhIT058941 for <ietf-sasl@imc.org>; Thu, 4 Jun 2009 08:53:53 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n54FrgDH003671 for <ietf-sasl@imc.org>; Thu, 4 Jun 2009 15:53:43 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n54FrgcE020698 for <ietf-sasl@imc.org>; Thu, 4 Jun 2009 09:53:42 -0600 (MDT)
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 n54Fhfo1002132; Thu, 4 Jun 2009 10:43:41 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n54Fhe8R002131; Thu, 4 Jun 2009 10:43:41 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Thu, 4 Jun 2009 10:43:40 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090604154340.GN1049@Sun.COM>
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org> <20090603132837.GA26728@Sun.COM> <20090603183914.GB1480@Sun.COM> <87ws7ss9os.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87ws7ss9os.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Thu, Jun 04, 2009 at 10:08:19AM +0200, Simon Josefsson wrote:
> Nicolas Williams <Nicolas.Williams@sun.com> writes:
> > gs2-header       = gs2-cbind-flag [ authzid ] "," [ gs2-ext-attrs "," ]
> >                                                   ^^^^^^^^^^^^^^^^^^^^^
> > Or something like that.  (One might prefer something slightly different
> > that makes it easier to find the end of the GS2 header.)
> 
> Right, you need a reliable way to identify the end of the gs2-header.  I
> also dislike the complexity in a parser that always will have to ignore
> any number of gs2-* parameters, so how about this instead:
> 
> string     = 1*(UTF8-char-safe / "=2C" / "=3D")
> gs2-authzid  = "a=" string
> gs2-cbind-flag   = "n" / "y" / "p"
> gs2-nonstd-flag = "F"
> gs2-header       = [gs2-nonstd-flag "," ] gs2-cbind-flag "," [ gs2-authzid ] "," [ "gs2-ext" "=" string ] ","
> 
> Servers that doesn't understand a gs2-ext token MUST fail
> authentication.

The extension doesn't have to be critical to do what we want it to.
More importantly, we don't have an error message defiedn so any failure
could only be communicated through the SASL outcome of authentication
message, and that need not provide machine-readable mechanism-specific
information, so the mechanism on the client can't use any failure
information for, say, Kurt's multi-level negotiation proposal (though I
am not sure that he meant that seriously -- I certainly don't take it
seriously).

So I think "MUST ignore unknown" is good enough.

> Having thought about this proposal (briefly), I don't think an extension
> idea is a good idea.  What you propose is an extension mechanism inside
> a SASL mechanism.  I have a fairly strong general preference against
> that -- SASL is an extensible protocol, and the way to negotiate
> extensions is to specify a new SASL mechanism name and have clients
> prefer that mechanism.  The new mechanism can be a cut'n'paste of the
> old mechanism, plus some new wording.  I don't see a need for an
> extension mechanism inside GS2 here?

This is not an extension in that sense -- we're not negotiating new
features.  We're merely providing future downgrade protection against a
future negotiation that could be done via SASL mech name nego.



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5488bf7024535 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 4 Jun 2009 01:08:37 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n5488bOJ024534; Thu, 4 Jun 2009 01:08:37 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n5488Nlk024499 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Thu, 4 Jun 2009 01:08:36 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (c80-216-29-127.bredband.comhem.se [80.216.29.127]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n5488J3e021546 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 4 Jun 2009 10:08:21 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org> <20090603132837.GA26728@Sun.COM> <20090603183914.GB1480@Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090604:ietf-sasl@imc.org::RwEI6D0zbZ6rYoIz:9k5V
X-Hashcash: 1:22:090604:nicolas.williams@sun.com::FeS/WVEbZBhdl/it:TZoF
X-Hashcash: 1:22:090604:alexey.melnikov@isode.com::j2EUXzcsBgbfygiq:0JC7D
Date: Thu, 04 Jun 2009 10:08:19 +0200
Message-ID: <87ws7ss9os.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_00, DATE_IN_FUTURE_48_96,RDNS_DYNAMIC,SPF_FAIL autolearn=no version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on yxa-v.extundo.com
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

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

> Huh, I think we can do something far simpler still: just add enough ABNF
> to define non-critical GS2 header extensions.  (That's what I get for
> posting late at night instead of sleeping on the idea.)
>
> ;; Non-critical GS2 extension headers; servers MUST ignore if they don't
> ;; understand them
> gs2-ext-attr     = "gs2-" 1*ALPHA
> gs2-ext-attr-val = gs2-ext-attr "=" value
> gs2-ext-attrs    = gs2-ext-attr-val *("," gs2-ext-attr-val)
>
> ;; GS2 header
> gs2-cbind-flag   = "n" / "y" / "p"
> gs2-header       = gs2-cbind-flag [ authzid ] "," [ gs2-ext-attrs "," ]
>                                                   ^^^^^^^^^^^^^^^^^^^^^
>
> Or something like that.  (One might prefer something slightly different
> that makes it easier to find the end of the GS2 header.)

Right, you need a reliable way to identify the end of the gs2-header.  I
also dislike the complexity in a parser that always will have to ignore
any number of gs2-* parameters, so how about this instead:

string     = 1*(UTF8-char-safe / "=2C" / "=3D")
gs2-authzid  = "a=" string
gs2-cbind-flag   = "n" / "y" / "p"
gs2-nonstd-flag = "F"
gs2-header       = [gs2-nonstd-flag "," ] gs2-cbind-flag "," [ gs2-authzid ] "," [ "gs2-ext" "=" string ] ","

Servers that doesn't understand a gs2-ext token MUST fail
authentication.

Having thought about this proposal (briefly), I don't think an extension
idea is a good idea.  What you propose is an extension mechanism inside
a SASL mechanism.  I have a fairly strong general preference against
that -- SASL is an extensible protocol, and the way to negotiate
extensions is to specify a new SASL mechanism name and have clients
prefer that mechanism.  The new mechanism can be a cut'n'paste of the
old mechanism, plus some new wording.  I don't see a need for an
extension mechanism inside GS2 here?

So, my preferences are:

1) GS2 -13 but remove tls-server-end-point and only support tls-unique.

2) GS2 -13 plus the changes I proposed earlier to send a list of channel
binding types.  This allows tls-server-end-point to work if there is
someone that is willing to do the work (specify an outer negotiation
protocol) for that.

3/4) GS2 -13.
3/4) GS2 plus your Y/P proposal.
  Not sure how to rate these two against each other.  The Y/P scheme is
  close to an extension scheme.

5) GS2 plus the above extension scheme.

/Simon



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n53InKmg061528 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Jun 2009 11:49:20 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n53InKwI061527; Wed, 3 Jun 2009 11:49:20 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-4.sun.com (brmea-mail-4.Sun.COM [192.18.98.36]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n53In9dg061513 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 11:49:19 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-4.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n53In8V5027878 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 18:49:08 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n53In8VE017883 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 12:49:08 -0600 (MDT)
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 n53IdFas001870; Wed, 3 Jun 2009 13:39:15 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n53IdE4O001869; Wed, 3 Jun 2009 13:39:14 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 3 Jun 2009 13:39:14 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090603183914.GB1480@Sun.COM>
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org> <20090603132837.GA26728@Sun.COM>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20090603132837.GA26728@Sun.COM>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

Huh, I think we can do something far simpler still: just add enough ABNF
to define non-critical GS2 header extensions.  (That's what I get for
posting late at night instead of sleeping on the idea.)

;; Non-critical GS2 extension headers; servers MUST ignore if they don't
;; understand them
gs2-ext-attr     = "gs2-" 1*ALPHA
gs2-ext-attr-val = gs2-ext-attr "=" value
gs2-ext-attrs    = gs2-ext-attr-val *("," gs2-ext-attr-val)

;; GS2 header
gs2-cbind-flag   = "n" / "y" / "p"
gs2-header       = gs2-cbind-flag [ authzid ] "," [ gs2-ext-attrs "," ]
                                                  ^^^^^^^^^^^^^^^^^^^^^

Or something like that.  (One might prefer something slightly different
that makes it easier to find the end of the GS2 header.)

So today SCRAM/GS2 would be essentially unmodified from what we had
going into this poll.  Later, when we add CB type negotiation we can add
an attribute for listing the CB types that the client saw in the 'y' and
'p' cases, and an attribute for specifying the CB type chosen by the
client in the 'p' case.

(And if we really wanted to we could add critical GS2 header extensions,
which, if present, cause the server to reply with an error if the server
doesn't understand the extension, else with a normal GSS context token
prefixed with a small header to distinguish from such errors.  Then even
Kurt's multi-level negotiation scheme could be added.)

Nico
-- 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n53DckVx025664 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 3 Jun 2009 06:38:46 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n53Dckg1025663; Wed, 3 Jun 2009 06:38:46 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from sca-ea-mail-1.sun.com (sca-ea-mail-1.Sun.COM [192.18.43.24]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n53DcY4l025647 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 06:38:45 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by sca-ea-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id n53DcYS3008974 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 13:38:34 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n53DcXLH029530 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 07:38:34 -0600 (MDT)
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 n53DSe49026732; Wed, 3 Jun 2009 08:28:40 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n53DSbsP026731; Wed, 3 Jun 2009 08:28:37 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 3 Jun 2009 08:28:37 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090603132837.GA26728@Sun.COM>
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM> <8763fdnari.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <8763fdnari.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Wed, Jun 03, 2009 at 07:31:45AM +0200, Simon Josefsson wrote:
> Nicolas Williams <Nicolas.Williams@sun.com> writes:
> > There is a slightly better way that would simplify the client: define
> > new GS2 CB flags to go with the 'n', 'y', and 'p' that we have now
> > (which would stay as they have been, w/o any additional GS2 header
> > fields).  The three flags we have now:
> >
> > ...
> >
> > Simplifying the client strikes me as a good thing.
> 
> It adds more text to the specification, and some complexity, but it
> seems like a reasonable compromise to simplify client implementations.

It does add more text to the spec, but server-side complexity is not
really changed, and the client is simplified.  I'm OK with either plan,
though I think I prefer this one.

> Before I update GS2 with that, what is the chance of making these
> changes to SCRAM?  Alexey?

We'll know soon enough.  The poll ends this week.

Nico
-- 



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n535W3jj074894 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jun 2009 22:32:03 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n535W3M0074893; Tue, 2 Jun 2009 22:32:03 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from yxa-v.extundo.com (yxa-v.extundo.com [83.241.177.39]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n535Vo6i074881 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <ietf-sasl@imc.org>; Tue, 2 Jun 2009 22:32:02 -0700 (MST) (envelope-from simon@josefsson.org)
Received: from mocca.josefsson.org (c80-216-29-127.bredband.comhem.se [80.216.29.127]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5) with ESMTP id n535VjdI019536 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Wed, 3 Jun 2009 07:31:48 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Nicolas Williams <Nicolas.Williams@sun.com>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org> <20090603050732.GA22446@Sun.COM>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:090603:nicolas.williams@sun.com::HjKGMKrcrINml8CB:2dzR
X-Hashcash: 1:22:090603:alexey.melnikov@isode.com::2sxvuI2rI0zTyjeH:AGOn
X-Hashcash: 1:22:090603:ietf-sasl@imc.org::VJigFXs2vHUEGqZ1:0S81i
Date: Wed, 03 Jun 2009 07:31:45 +0200
In-Reply-To: <20090603050732.GA22446@Sun.COM> (Nicolas Williams's message of "Wed, 3 Jun 2009 00:07:32 -0500")
Message-ID: <8763fdnari.fsf@mocca.josefsson.org>
User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.0.94 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, score=0.0 required=5.0 tests=AWL,BAYES_00, DATE_IN_FUTURE_48_96,RDNS_DYNAMIC,SPF_FAIL autolearn=no version=3.2.5
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on yxa-v.extundo.com
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

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

> On Fri, May 29, 2009 at 08:29:42PM +0200, Simon Josefsson wrote:
>>                         ...  The changes can be summarized into:
>> 
>> 1) Add text to say that with 'p' one cb type name is included (normally
>> tls-unique)
>> 
>> 2) Add text to say that with 'y' a list of cb type names supported by
>> the client is included
>
> There is a slightly better way that would simplify the client: define
> new GS2 CB flags to go with the 'n', 'y', and 'p' that we have now
> (which would stay as they have been, w/o any additional GS2 header
> fields).  The three flags we have now:
>
>  - 'n' (client can't do CB)
>  - 'y' (client can only do tls-unique but thinks the server can't do CB)
>  - 'p' (client used CB of the default type)
>
> plus two new ones that today's servers would have to understand but
> today's clients wouldn't have to:
>
>  - 'Y' and a list of CB types in GS2 header (client can do CB and CB
>    type negotiation and thinks the server advertives the given, possibly
>    empty list of CB types)
>
>  - 'P' and a single CB type in GS2 header (client used CB of the given
>    type)
>
> This way the server needs to know about the new bits in GS2 for future
> downgrade protection in the face of CB type nego, but the client doesn't
> have to know anything at all about future CB type nego.
>
> Simplifying the client strikes me as a good thing.

It adds more text to the specification, and some complexity, but it
seems like a reasonable compromise to simplify client implementations.

Before I update GS2 with that, what is the chance of making these
changes to SCRAM?  Alexey?

/Simon



Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n535Hiqm074160 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 2 Jun 2009 22:17:44 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n535HicH074159; Tue, 2 Jun 2009 22:17:44 -0700 (MST) (envelope-from owner-ietf-sasl@mail.imc.org)
X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-sasl@mail.imc.org using -f
Received: from brmea-mail-2.sun.com (brmea-mail-2.Sun.COM [192.18.98.43]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n535HWC2074150 for <ietf-sasl@imc.org>; Tue, 2 Jun 2009 22:17:42 -0700 (MST) (envelope-from Nicolas.Williams@sun.com)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by brmea-mail-2.sun.com (8.13.6+Sun/8.12.9) with ESMTP id n535HVGp005934 for <ietf-sasl@imc.org>; Wed, 3 Jun 2009 05:17:32 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id n535HVJR037544 for <ietf-sasl@imc.org>; Tue, 2 Jun 2009 23:17:31 -0600 (MDT)
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 n5357c1J026281; Wed, 3 Jun 2009 00:07:38 -0500 (CDT)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id n5357WYv026280; Wed, 3 Jun 2009 00:07:32 -0500 (CDT)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 3 Jun 2009 00:07:32 -0500
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Simon Josefsson <simon@josefsson.org>
Cc: Alexey Melnikov <alexey.melnikov@isode.com>, SASL WG <ietf-sasl@imc.org>
Subject: Re: Poll: use of TLS channel bindings in SCRAM
Message-ID: <20090603050732.GA22446@Sun.COM>
References: <4A1F06CF.80505@isode.com> <87k540napw.fsf@mocca.josefsson.org> <20090529051317.GD29258@Sun.COM> <878wkfu5ih.fsf@mocca.josefsson.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <878wkfu5ih.fsf@mocca.josefsson.org>
User-Agent: Mutt/1.5.7i
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

On Fri, May 29, 2009 at 08:29:42PM +0200, Simon Josefsson wrote:
>                         ...  The changes can be summarized into:
> 
> 1) Add text to say that with 'p' one cb type name is included (normally
> tls-unique)
> 
> 2) Add text to say that with 'y' a list of cb type names supported by
> the client is included

There is a slightly better way that would simplify the client: define
new GS2 CB flags to go with the 'n', 'y', and 'p' that we have now
(which would stay as they have been, w/o any additional GS2 header
fields).  The three flags we have now:

 - 'n' (client can't do CB)
 - 'y' (client can only do tls-unique but thinks the server can't do CB)
 - 'p' (client used CB of the default type)

plus two new ones that today's servers would have to understand but
today's clients wouldn't have to:

 - 'Y' and a list of CB types in GS2 header (client can do CB and CB
   type negotiation and thinks the server advertives the given, possibly
   empty list of CB types)

 - 'P' and a single CB type in GS2 header (client used CB of the given
   type)

This way the server needs to know about the new bits in GS2 for future
downgrade protection in the face of CB type nego, but the client doesn't
have to know anything at all about future CB type nego.

Simplifying the client strikes me as a good thing.

Nico
-- 


