IETF Logo Mail Archive

Re: [kitten] CB data characteristics Re: Fw: New Version Notification for draft-mills-kitten-sasl-oauth-02

"William J. Mills" <wmills@yahoo-inc.com> Sat, 09 April 2011 23:12 UTC

Return-Path: <wmills@yahoo-inc.com>
X-Original-To: kitten@core3.amsl.com
Delivered-To: kitten@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 264E13A6977 for <kitten@core3.amsl.com>; Sat, 9 Apr 2011 16:12:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.598
X-Spam-Level:
X-Spam-Status: No, score=-17.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, USER_IN_DEF_WHITELIST=-15]
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 Wk4JBZLKEM7I for <kitten@core3.amsl.com>; Sat, 9 Apr 2011 16:12:11 -0700 (PDT)
Received: from web32303.mail.mud.yahoo.com (web32303.mail.mud.yahoo.com [68.142.207.151]) by core3.amsl.com (Postfix) with SMTP id 29BEA3A698F for <kitten@ietf.org>; Sat, 9 Apr 2011 16:12:11 -0700 (PDT)
Received: (qmail 10094 invoked by uid 60001); 9 Apr 2011 23:13:54 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo-inc.com; s=ginc1024; t=1302390834; bh=8WKVPt3dH0flqdjHexJNYpr6k2fJPryCcAFKM98/0r8=; h=Message-ID:X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=fpY1eF/OhSD7SwpZojfuElMvTnkQy86dZzGrQjVKDJDhKFyVtzhYRHknNkNQS468qlovUjqznoyZxLc+XWiviSen8S2csC1ZbOYvJhQTjQM8S7ikBrNLCMn09KosPKO4ba3xZfUwPnXKR4J2h/Sm9FToKdHJHlyHD3lsbPcEbtU=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=ginc1024; d=yahoo-inc.com; h=Message-ID:X-YMail-OSG:Received:X-RocketYMMF:X-Mailer:References:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type; b=SftAdYuZvJTGQP3RutnhekOKkIaZw7/kJIxKcY1QB1w0VVFAqha/k6aNJ5pjXoTVov88WmuWGbFWVqrwY16vGtgXLOgv6RKEpRqxTLL+dNdMhdNuH/n5Eg8BRFj3X6Z+LD6liuiXX7j4DjFq82ol8HUJ6pUvRXSDNhOzeGLM7NA=;
Message-ID: <800503.74700.qm@web32303.mail.mud.yahoo.com>
X-YMail-OSG: qB.RBhsVM1l1ThXFlHHh.L9W1WAMPfziFrRf_7sruqfXTb5 fsqRiWCyUxnfRhCuRZLijRbosV92uXF9cXa_u0BMmxwwTMK.a7ywB7qbHRLO WLlKqFqLK3qSXY4Zn0.pBvos89BPBozQRZcpvBNN92sA6ZqeBgAr6omrb3e7 8EZxZe5IBL3b5.RojSRxFibcFP0ossOFet1zTDeWSqIYqAegRv0A.qQvcW1e jl9G_UomdkVlxST_17wlungKgCtoqNg_wG8M1xRMtWnXBHs.lNv4gWjU8JRO gBFjIP9Q89FM26u71.IYiNX70.fT7TmreW24lykmQRRgx20D8b0rMS.C.ibp YizhgpN7I3F6w
Received: from [99.31.212.42] by web32303.mail.mud.yahoo.com via HTTP; Sat, 09 Apr 2011 16:13:54 PDT
X-RocketYMMF: william_john_mills
X-Mailer: YahooMailWebService/0.8.110.299900
References: <20110408070506.12ECB3A6A4C@core3.amsl.com> <416848.75882.qm__16525.0710481361$1302247955$gmane$org@web32314.mail.mud.yahoo.com> <87hba9b13i.fsf@latte.josefsson.org> <tsl4o684s5q.fsf@mit.edu> <754979.46407.qm@web32303.mail.mud.yahoo.com> <tslr59c3asv.fsf@mit.edu> <7EE86E89365CA94F8E7B8251F926071007AC12BC@CIO-KRC-D1MBX01.osuad.osu.edu> <tslipuo378b.fsf@mit.edu> <7EE86E89365CA94F8E7B8251F926071007AC141F@CIO-KRC-D1MBX01.osuad.osu.edu> <BANLkTi=XyB7cAF7wmC0mjQKgNsbWhT7QgA@mail.gmail.com> <991228.73942.qm@web32303.mail.mud.yahoo.com> <BANLkTik+=s2eQiNcLjTpzWNdwR--MLdOEQ@mail.gmail.com> <277844.39554.qm@web32314.mail.mud.yahoo.com> <BANLkTikqPT1m6gL47yBuFcjzArb1xHwhEw@mail.gmail.com> <878377.41252.qm@web32303.mail.mud.yahoo.com> <BANLkTin_Pb=bOm4S54geCTX+ZigFvfXKmw@mail.gmail.com>
Date: Sat, 09 Apr 2011 16:13:54 -0700
From: "William J. Mills" <wmills@yahoo-inc.com>
To: Nico Williams <nico@cryptonector.com>
In-Reply-To: <BANLkTin_Pb=bOm4S54geCTX+ZigFvfXKmw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="0-671118622-1302390834=:74700"
Cc: "kitten@ietf.org" <kitten@ietf.org>
Subject: Re: [kitten] CB data characteristics Re: Fw: New Version Notification for draft-mills-kitten-sasl-oauth-02
X-BeenThere: kitten@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: "William J. Mills" <wmills@yahoo-inc.com>
List-Id: Common Authentication Technologies - Next Generation <kitten.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/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: Sat, 09 Apr 2011 23:12:12 -0000

Well perhaps I'll get just fancy enough to say if the CB source data is > than 500 bytes then SHA-1 hash and pass the hash. 


I'm stuffing this in an HTML query parameter, and I don't want to end up with problems in client or servers that assume maximum lengths.



________________________________
From: Nico Williams <nico@cryptonector.com>
To: William J. Mills <wmills@yahoo-inc.com>
Cc: "kitten@ietf.org" <kitten@ietf.org>
Sent: Saturday, April 9, 2011 1:04 AM
Subject: Re: [kitten] CB data characteristics Re: Fw: New Version Notification for draft-mills-kitten-sasl-oauth-02


On Apr 9, 2011 2:27 AM, "William J. Mills" <wmills@yahoo-inc.com> wrote:
>
> So, I think the way to go in this mechanism is to send the channel binding type identifier and a SHA-1 hash of the channel binding data.  If the CB data is short I suppose we could optimise it, but I like simple for this. 
Uh, so i did tell you one thing wrong earlier: CB data will generally be small.  The TLS CB types are small...  If you assume they'll be small then you can dispense with the hash and any hash algorithm agility issues.  Sorry about that!
Nico
--

v2.23.0 | Report a Bug | By Email