IETF Logo Mail Archive

Re: [kitten] [Ietf-krb-wg] Channel bindings -- interop issue with GSS_C_AF_*

Nico Williams <nico@cryptonector.com> Wed, 08 June 2011 17:44 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: kitten@ietfa.amsl.com
Delivered-To: kitten@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C8C411E8125 for <kitten@ietfa.amsl.com>; Wed, 8 Jun 2011 10:44:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.14
X-Spam-Level:
X-Spam-Status: No, score=-3.14 tagged_above=-999 required=5 tests=[AWL=-1.163, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ER2Qyr+GCnbH for <kitten@ietfa.amsl.com>; Wed, 8 Jun 2011 10:44:24 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (caiajhbdcbbj.dreamhost.com [208.97.132.119]) by ietfa.amsl.com (Postfix) with ESMTP id B868B11E8076 for <kitten@ietf.org>; Wed, 8 Jun 2011 10:44:24 -0700 (PDT)
Received: from homiemail-a31.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTP id 567FB202017 for <kitten@ietf.org>; Wed, 8 Jun 2011 10:44:24 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc :content-type:content-transfer-encoding; q=dns; s= cryptonector.com; b=v9yfiblj8CYmfQWAkHAGQtXGKEJ02Jqelzx78bqS3vYN GrKVZCTvki7QDDafoCE3xzHpfRA6OZqH9/vT5Bt4XPiXNC/bXcStxmlp4XEO7LeA UbSjn2vr5KQFu09DsIUBvVthucHMzmMuEsr3F++fD9BbWQYEFaMF+Pne0hweY1s=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type:content-transfer-encoding; s= cryptonector.com; bh=QOeVo6d+NXZEbfseus/Kzfya+9Y=; b=C0zCrit5K49 3tshthmV5rkXn7NL7ln1TgOZVTKbstXy6b3q7qUJhCi6h6gzQBMgMvuw6XVJiHel 245PhzB89yi/qJ1lEa+tgniSmfNTvDAbYgVqyyi2aBHpq4Ezbbf3jfhMJT+eF5VP tYxJn4vY8VJ+NWZ+C1XWh0sxb08wTGQ0=
Received: from mail-pw0-f44.google.com (mail-pw0-f44.google.com [209.85.160.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a31.g.dreamhost.com (Postfix) with ESMTPSA id 9D7C3202038 for <kitten@ietf.org>; Wed, 8 Jun 2011 10:44:23 -0700 (PDT)
Received: by pwi5 with SMTP id 5so394539pwi.31 for <kitten@ietf.org>; Wed, 08 Jun 2011 10:44:23 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.31.135 with SMTP id a7mr1043198pbi.54.1307555063156; Wed, 08 Jun 2011 10:44:23 -0700 (PDT)
Received: by 10.68.50.39 with HTTP; Wed, 8 Jun 2011 10:44:23 -0700 (PDT)
In-Reply-To: <D5847DD823005F4E9DB94FE77DCEDF680FEE7953@ALVMBXW01.prod.quest.corp>
References: <201106071831.p57IVNmb010502@fs4113.wdf.sap.corp> <201106071900.p57J0uCN012135@fs4113.wdf.sap.corp> <D5847DD823005F4E9DB94FE77DCEDF680FEE75C2@ALVMBXW01.prod.quest.corp> <87oc29xrtn.fsf@latte.josefsson.org> <BANLkTinvrZioQjwgqy9_jmFqHFvFMyCyaw@mail.gmail.com> <tslvcwg2rdo.fsf@mit.edu> <BANLkTimy2ZQCHc6JUK4GaaxJj8BSHfJymA@mail.gmail.com> <D5847DD823005F4E9DB94FE77DCEDF680FEE7953@ALVMBXW01.prod.quest.corp>
Date: Wed, 08 Jun 2011 12:44:23 -0500
Message-ID: <BANLkTi=A4rKaUUkT=ShYR4aKV6y5ULQ94A@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Thomas Maslen <Thomas.Maslen@quest.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: "kitten@ietf.org" <kitten@ietf.org>, Simon Josefsson <simon@josefsson.org>, Sam Hartman <hartmans-ietf@mit.edu>, "ietf-krb-wg@anl.gov" <ietf-krb-wg@anl.gov>
Subject: Re: [kitten] [Ietf-krb-wg] Channel bindings -- interop issue with GSS_C_AF_*
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/kitten>, <mailto:kitten-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/kitten>
List-Post: <mailto:kitten@ietf.org>
List-Help: <mailto:kitten-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/kitten>, <mailto:kitten-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jun 2011 17:44:25 -0000

On Wed, Jun 8, 2011 at 12:38 PM, Thomas Maslen <Thomas.Maslen@quest.com> wrote:
> Nico Williams wrote:
>> [...] We then need only determine which one Windows is using now.
>
> My understanding -- based both on some Microsoft documentation and on
> tweaking our implementation to validate a CB hash generated by a Windows
> HTTPS-SPNEGO client -- is that Microsoft does exactly the same thing that
> you specified in RFC5801:  set the address-type to zero (and of course the
> address-length is also zero).

Thanks, this is great information.

> And I agree with Sam + you:  we shouldn't break Microsoft's implementation,
> nor should we break RFC5801.  Instead we should update RFC2744 /
> RFC5554 / whatever to use 0, not 255, as the address-type for omitted addresses.

RFC5554 is basically an update to RFC2743 adding to the abstract API
what RFC2744 had effectively done.  So I think an update or erratum to
RFC5554 will suffice.  An erratum to RFC2744 would not hurt though.

v2.43.4 | Report a Bug | By Email | System Status