IETF Logo Mail Archive

Re: [Unbearable] 0-RTT Token Binding: When to switch exporters?

Eric Rescorla <ekr@rtfm.com> Tue, 21 March 2017 12:24 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: unbearable@ietfa.amsl.com
Delivered-To: unbearable@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C611612984B for <unbearable@ietfa.amsl.com>; Tue, 21 Mar 2017 05:24:45 -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=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zjrh-Cv3hl2B for <unbearable@ietfa.amsl.com>; Tue, 21 Mar 2017 05:24:39 -0700 (PDT)
Received: from mail-yw0-x22c.google.com (mail-yw0-x22c.google.com [IPv6:2607:f8b0:4002:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 63196129850 for <unbearable@ietf.org>; Tue, 21 Mar 2017 05:24:36 -0700 (PDT)
Received: by mail-yw0-x22c.google.com with SMTP id p77so108495310ywg.1 for <unbearable@ietf.org>; Tue, 21 Mar 2017 05:24:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Npe12h7z1ZuHass+x+bJtcf1DXItV/XgdzvYcWtKXE0=; b=FRkyi1OW8+7Xi8V5AKJyhJbf5bNn72QJvsGCfWsw2xrp/h1DI1DwJzbNPHSo6t99lb 65E8Ek5ECbl/z36MRD4k5nkXcNFJEcXhA9inBwQf4UdCo3/6w6xNCjwkLPb+qrXiHAh3 mdeOolDIcIu7JZk+I5p41ohQ/CL9mLHqqknLd8wfsjIb/+u30IfahkYlOnunuBhVOOm3 iRKyiYTJmz6Crn5ehILMoaErGJyTwufKLJ7elnmC5CuWy5AxwZt3lYZVSKUPEygdB3N1 Z0opFkHEGf0aHc/X1CnbVKLlepdXVGEccLcp1d37F5z2qPWSUYFnZph0/DK4K9QYszsT u5AA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Npe12h7z1ZuHass+x+bJtcf1DXItV/XgdzvYcWtKXE0=; b=UdvEts6lORpWkOIKd+Xjf1U1oC1wOQWt2L1rCJwEmJh1dMnC7GsodlyyFm5FH5yOG7 JSXZH7PAUBcU+5Y+Ytr8aTnNkiqUg0NRM+ODtY6OtTeMXNI/tKX/BZk167CzkDQ7LsdD MWWGshkOUtNTskY0202tmpB7gIl+SsfZpPSnxWb/0Eny9BKHzFpekGuL9XbjE//+uFge FbyMWONpRVdx34m8jBvHuE7Lrni3jH6DLV4PRqGa3ulB9Vh0/uQJq028jTJbjhVwr4Hv SMj5mGmxmiNCH36hyMYVEEqMXCknNP/RQPftYUCox5+RQ/QiXh/rGV6W7jKXcPJQ1hfl S4rQ==
X-Gm-Message-State: AFeK/H25KRI9PKqHvlqb0rU15ac+Natrzc8f6TIBKKrXAsLcurhyyao4V40R960TWuVqQ0Ep3ykJktDEaAl8rw==
X-Received: by 10.129.152.22 with SMTP id p22mr20118156ywg.276.1490099075605; Tue, 21 Mar 2017 05:24:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.154.210 with HTTP; Tue, 21 Mar 2017 05:23:55 -0700 (PDT)
In-Reply-To: <CABkgnnXBQEV4w7Zb=C9GE25-wp3oMVauKRZ21mCa+Qoby9XAPg@mail.gmail.com>
References: <CACdeXiK2Hs=Kz_5OFryWR+9_t6nDL_p7NKjw=CwRsua_E5S9Mw@mail.gmail.com> <DM2PR0301MB084793F58146F8574BF36EE18C780@DM2PR0301MB0847.namprd03.prod.outlook.com> <CACdeXiJGcsTxrSWmd5BZrfoWTHhFF3+RisQFD628iYNMzZakhQ@mail.gmail.com> <CACdeXiJFe7-jM9qEnNB+Wp3joGxF_X1z+-dPywb9SRZuSNmAzQ@mail.gmail.com> <DM2PR21MB0091E3F087E1AECA3A63A3788C560@DM2PR21MB0091.namprd21.prod.outlook.com> <CACdeXi+YjLaXtoX47LtVK4Ay2y-mCOOraV46gbbbuQPL40ngXg@mail.gmail.com> <DM2PR21MB00910C83983BEE885B0E04288C560@DM2PR21MB0091.namprd21.prod.outlook.com> <CACdeXiLON5OAjfFCNsenCeaGV3a_LDoi17VAk=fSzF0YA5=f7Q@mail.gmail.com> <CACdeXiLNCrPSz0_hZSpQ6tsoHB7ryJ2dCnHjUYwu5vu5fO4XBg@mail.gmail.com> <SN1PR21MB0096D7426A4E230E284F0D058C560@SN1PR21MB0096.namprd21.prod.outlook.com> <CACdeXiKuzNh0fP9b-jEF82m-6mX+i04To96GMa_tFNcuznGn+A@mail.gmail.com> <DM2PR21MB00914BA07BA984E931B88FEB8C290@DM2PR21MB0091.namprd21.prod.outlook.com> <CACdeXiKQjaoAArLBcjRj+kUJUqH+f1bA5yeCCiQ6GMXzWJURBw@mail.gmail.com> <CABkgnnV0+vumfkZAMRZ_8q5pTkwf_CqhZ+deeVWdbF9SFaHoJw@mail.gmail.com> <DM2PR21MB0091DE5B213D2363FAF353CF8C280@DM2PR21MB0091.namprd21.prod.outlook.com> <CACdeXiKweRaZEKi4kqmPfUc2JLyZLGbp8tFRpkTfmJisPCMWRg@mail.gmail.com> <CACdeXiL6riBRb1-UDhVK-R5CvopzisJnYTRjWsvpimWA2G3DhQ@mail.gmail.com> <CABcZeBN2RhBsyj8_1F6bBnw9j10qdABwdZVdgwVcUr4Tf6sLtA@mail.gmail.com> <CACdeXiLZQSMxSqTPSHVqUwZomUpaMadUNYEEzF2to9Rx6nLMWQ@mail.gmail.com> <CABcZeBPvxX-8PuoV1oV-k5BnH3sjbWuuHfeAfh7FRhgtuVPkCQ@mail.gmail.com> <CACdeXi+rbsKf7zbpe4n49BUmj1ay0GSg_A48ZrAztKPY9+Fm2A@mail.gmail.com> <CABkgnnXBQEV4w7Zb=C9GE25-wp3oMVauKRZ21mCa+Qoby9XAPg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 21 Mar 2017 05:23:55 -0700
Message-ID: <CABcZeBPpoex3axkkqgTRGWujGLbkC2GNqn+-50ipso3e9h8vJA@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Nick Harper <nharper@google.com>, Andrei Popov <Andrei.Popov@microsoft.com>, IETF Tokbind WG <unbearable@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c0b8fb41503ca054b3cba9c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/4NHkQpXjncjk-pra9q8qPJiHHjw>
Subject: Re: [Unbearable] 0-RTT Token Binding: When to switch exporters?
X-BeenThere: unbearable@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "\"This list is for discussion of proposals for doing better than bearer tokens \(e.g. HTTP cookies, OAuth tokens etc.\) for web applications. The specific goal is chartering a WG focused on preventing security token export and replay attacks.\"" <unbearable.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/unbearable>, <mailto:unbearable-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/unbearable/>
List-Post: <mailto:unbearable@ietf.org>
List-Help: <mailto:unbearable-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/unbearable>, <mailto:unbearable-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 21 Mar 2017 12:24:46 -0000

On Mon, Mar 20, 2017 at 7:23 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 21 March 2017 at 10:32, Nick Harper <nharper@google.com> wrote:
> > All HTTP requests which the client starts processing to send after the
> > client sends its Finished message MUST use the exporter_secret for
> > their token bindings.
>
> How would a server verify this?
>

I don't believe it can. It can verify some violations (effectively those
that Nick's
role detected) at the HTTP layer.

-Ekr

v2.23.0 | Report a Bug | By Email