IETF Logo Mail Archive

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

Nico Williams <nico@cryptonector.com> Sat, 09 April 2011 04:44 UTC

Return-Path: <nico@cryptonector.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 E507F3A69EA for <kitten@core3.amsl.com>; Fri, 8 Apr 2011 21:44:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.944
X-Spam-Level:
X-Spam-Status: No, score=-1.944 tagged_above=-999 required=5 tests=[AWL=0.032, 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 7IA8VF7KxQMR for <kitten@core3.amsl.com>; Fri, 8 Apr 2011 21:44:29 -0700 (PDT)
Received: from homiemail-a25.g.dreamhost.com (caiajhbdcaib.dreamhost.com [208.97.132.81]) by core3.amsl.com (Postfix) with ESMTP id 2CDC83A69A7 for <kitten@ietf.org>; Fri, 8 Apr 2011 21:44:29 -0700 (PDT)
Received: from homiemail-a25.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a25.g.dreamhost.com (Postfix) with ESMTP id EF5EB678056 for <kitten@ietf.org>; Fri, 8 Apr 2011 21:46:14 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; c=nofws; d=cryptonector.com; h=mime-version :in-reply-to:references:date:message-id:subject:from:to:cc: content-type; q=dns; s=cryptonector.com; b=UaMciiISfyzFZxYaYnl6y mQkRk1gzxwuta/u4fN61NrCZ87udQwNBrQXDpX+8uhcfEBc60t1WDODUgYRMmPAd PL1Jqb4QfVDQ+zA7bU8HKODqX5cOdYVVmvM9v634T4SukRNv6u4Kg1z6cW1xysmm 9ZzdfdH29eGTUKVT9VYJl8=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=31mO0kOr5wTD0TT2ezH7 0iDmDD0=; b=ox20LxbmS3YNutMCKKPzzVl3x5fMA4xapebF5Bhwbizo2uaKhUIb 25imQdXcetTMO/wDuIkInYobrmIzeaWamx42Gc2sE+6x1biKLYurL5adQ8pnBXwF vgwNgkkCfIxSdmm3TZk4EoL+lB+gqq0f6B8VSa4d+N8+z23cZ1d6i+I=
Received: from mail-vw0-f44.google.com (mail-vw0-f44.google.com [209.85.212.44]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a25.g.dreamhost.com (Postfix) with ESMTPSA id CD784678055 for <kitten@ietf.org>; Fri, 8 Apr 2011 21:46:14 -0700 (PDT)
Received: by vws12 with SMTP id 12so3875737vws.31 for <kitten@ietf.org>; Fri, 08 Apr 2011 21:46:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.180.9 with SMTP id dk9mr4256951vdc.134.1302324374034; Fri, 08 Apr 2011 21:46:14 -0700 (PDT)
Received: by 10.52.166.42 with HTTP; Fri, 8 Apr 2011 21:46:13 -0700 (PDT)
Received: by 10.52.166.42 with HTTP; Fri, 8 Apr 2011 21:46:13 -0700 (PDT)
In-Reply-To: <991228.73942.qm@web32303.mail.mud.yahoo.com>
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>
Date: Fri, 08 Apr 2011 23:46:13 -0500
Message-ID: <BANLkTikocC0_B8CYhjmSw+j-2vaTEHD=1g@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: "William J. Mills" <wmills@yahoo-inc.com>
Content-Type: multipart/alternative; boundary="bcaec5186a4cb25a2c04a075057c"
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
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 04:44:30 -0000

>On Apr 8, 2011 7:11 PM, "William J. Mills" <wmills@yahoo-inc.com> wrote:
> Related questions about channel binding data...
> CB data is prefixed with the channel binding scheme name and a colon, is
there BNF or a definition for what the rest of that looks like?  Do I need
to base64 it to make it safe to move in an HTML context?

No, there is no such thing.  Each channel defines its CB data.

> Also, how big will it end up?  I suppose an SSL certificate can be a few k
in the extreme case.

It can get large.  Mechanisms should either MAC the CB data or mix it into
key derivation.

Nico
--

v2.23.0 | Report a Bug | By Email