Return-Path: 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 75C67129BDA for ; Fri, 20 Jan 2017 07:23:27 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=pingidentity.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 uxSsP9fJarV2 for ; Fri, 20 Jan 2017 07:23:25 -0800 (PST) Received: from mail-yw0-x236.google.com (mail-yw0-x236.google.com [IPv6:2607:f8b0:4002:c05::236]) (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 8BFDD129608 for ; Fri, 20 Jan 2017 07:23:25 -0800 (PST) Received: by mail-yw0-x236.google.com with SMTP id w75so90707011ywg.1 for ; Fri, 20 Jan 2017 07:23:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pingidentity.com; s=gmail; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=L/rSwXfLiGHWjIjbimJopSg7DnRLnMunnQhRSJy/wKA=; b=JOVhV28aNtLsEcfdtrY2daHxK0ZLjLQsxVXqHxSrDIV7bLexyZJSGEgrSEn65b36k0 OEaS7Xzko3LpFIeiSAol7f0Qsj9vtYOfTlbwyJXkF2ZMS7GICZ4djsye26RKPDIoRET3 vBGh2UodhauHSWPr6G7qhCyAVjttFQpo6U/qc= 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=L/rSwXfLiGHWjIjbimJopSg7DnRLnMunnQhRSJy/wKA=; b=Ufd8y49hc/XKRFbNdr99f+EDZZlaSutYL+hcENZipwHkI36M8Yt4BwygzUurr12gvw iBzneWkRSGU6NLVyJwfy8mpsEAS1Pj7iZcGu0fuPkbmoomrvMq6den8EZq9r4GgbYrtV SkYB8TCqzLbNDrLdSfP4rYwq1BxW8p5rKFZJZ2jvtrbsFxJAQRL1Q8yGfTpz3NhLeqxG ylIQ4oO+MqlNWt93+6sv6vMiZqtiNmvFLGnnolH4DBQ20MZiVSUvtXnCPTRPZKwdycl0 AvAyqefsqdNbnSnG1PNGMUqA1crLpQvxLTylq1Xtvi9SZ3WBialcft20x9m3dW9JW/3p Mqxg== X-Gm-Message-State: AIkVDXKDco/VG4GZGRBWPvKbQLqjsqbDh/OJUmAqHkqkedeoSaIfh8ZphwVZA/GGdviziRLL1UXErVj4wR44CNLd X-Received: by 10.129.98.70 with SMTP id w67mr11544594ywb.184.1484925804732; Fri, 20 Jan 2017 07:23:24 -0800 (PST) MIME-Version: 1.0 Received: by 10.37.90.133 with HTTP; Fri, 20 Jan 2017 07:22:54 -0800 (PST) In-Reply-To: References: <8074E906-BC37-42BF-8DE3-C2C797D71577@ve7jtb.com> From: Brian Campbell Date: Fri, 20 Jan 2017 08:22:54 -0700 Message-ID: To: John Bradley Content-Type: multipart/alternative; boundary=001a11471bae1c16470546883b75 Archived-At: Cc: Tokbind WG , token-binding-team , Bill Cox Subject: Re: [Unbearable] Token binding version (0, 10) support is global on google servers X-BeenThere: unbearable@ietf.org X-Mailman-Version: 2.1.17 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.\"" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 20 Jan 2017 15:23:27 -0000 --001a11471bae1c16470546883b75 Content-Type: text/plain; charset=UTF-8 chrome://flags/#enable-token-binding AFAIK is where one can flip the flag On Fri, Jan 20, 2017 at 6:45 AM, John Bradley wrote: > Can you remind people in the WG what the flag is. > > I think a test page is useful for PR. > > The browserauth.net page run my Dirk should be updated to point to it. > > I know that there is a test in the Chromium source but having some public > page will encourage testing. > > Thanks > John B. > > On Jan 20, 2017, at 10:35 AM, Bill Cox wrote: > > On Fri, Jan 20, 2017 at 5:01 AM, John Bradley wrote: > >> Great news. >> >> Is token binding not behind a feature flag for some of the newer builds >> of Chrome? >> > > It still is behind a feature flag. Nick Harper is doing a launch to turn > token binding on by default, IIUC. > > >> We should check if it is on in the Edge preview rings. I think Andrei >> mentioned that was about to happen in Korea. >> >> Do you have any test page that would show if the cookies are successfully >> token bound ? >> > > I don't think we've built such a page yet. Would it be useful? > > Bill > > > > _______________________________________________ > Unbearable mailing list > Unbearable@ietf.org > https://www.ietf.org/mailman/listinfo/unbearable > > --001a11471bae1c16470546883b75 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
chrome://flags/#enable-token-binding AFAIK is where one ca= n flip the flag

On Fri, Jan 20, 2017 at 6:45 AM, John Bradley &l= t;ve7jtb@ve7jtb.com<= /a>> wrote:
Can you remind people in the WG what the flag is.

=
I think a test page is useful for PR.

T= he browserauth.net= page run my Dirk should be updated to point to it.

I know that there is a test in the Chromium source but having some public= page will encourage testing.

Thanks=C2=A0
John B.

On Jan 20, 2017, at 10:35 AM, Bill Cox <waywardgeek@google.com> wrote:<= /div>
On Fri, = Jan 20, 2017 at 5:01 AM, John Bradley <ve7jtb@ve7jtb.com> wr= ote:
Great news.

Is token binding not behind a feature flag for some of the newer builds of = Chrome?

It still is behind a feature fl= ag.=C2=A0 Nick Harper is doing a launch to turn token binding on by default= , IIUC.
=C2=A0
We should check if it is on in the Edge preview rings.=C2=A0 =C2=A0I think = Andrei mentioned that was about to happen in Korea.

Do you have any test page that would show if the cookies are successfully t= oken bound ?

I don't think we'v= e built such a page yet.=C2=A0 Would it be useful?

Bill


__________________= _____________________________
Unbearable mailing list
Unbearable@ietf.org
https://www.ietf.org/mailman/listinfo/unbearabl= e


--001a11471bae1c16470546883b75--