IETF Logo Mail Archive

Re: [Unbearable] sec-token-binding header in the wild

John Bradley <ve7jtb@ve7jtb.com> Wed, 15 February 2017 23:46 UTC

Return-Path: <ve7jtb@ve7jtb.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 7AFEE129BEE for <unbearable@ietfa.amsl.com>; Wed, 15 Feb 2017 15:46:50 -0800 (PST)
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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ve7jtb-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 eVxqBDSm7h0d for <unbearable@ietfa.amsl.com>; Wed, 15 Feb 2017 15:46:48 -0800 (PST)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (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 327B8129BEA for <unbearable@ietf.org>; Wed, 15 Feb 2017 15:46:48 -0800 (PST)
Received: by mail-qt0-x22b.google.com with SMTP id v23so1569257qtb.0 for <unbearable@ietf.org>; Wed, 15 Feb 2017 15:46:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ve7jtb-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=EfhEBRJLJBGsrF+sFT0tSkQ/qapJObKqPt8stuEQiYk=; b=TtbYcpXb6t5v5tdisj0BsfCtLTH9v3Y3azQezoE9tdRuSfFMj8rNgRwzBs0/WTlu0F IJcNNh0M39McnsPuFTVMGRwop+aNZRpW8voCNQfpfbapdcZb+c5WXYazbeTaqNB79nhC k50GHT8/Ezui/7+WghnJ5/9ElFznVtCfxjWGIQyLn6770WD7gXO1++X7unzzpjic9+k5 qmrCiRRbZXxyNnfQOhWV5tZr9VB0+4bh4coFaXpY1C9hKCR8Noqq+y+jjuJXsDHOLZg4 MBUnajV6Dkpy7zm48UKdbDwcvascMc7Y+wEWlLLN/J9LilSB+Nz9ePGN2VpCvyti6RxO TfUA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=EfhEBRJLJBGsrF+sFT0tSkQ/qapJObKqPt8stuEQiYk=; b=WU6H1bBbCg4ZE5BUI/rJoQ3BUZWAkEMDXiDygevG0KFpVnIvoMzbpk9lbJJYBM7Tss ML7lqLU4SMBD5taLqugpCUpUDFecf1dikkkyZw3PTyZZFkic70Gh0C8hiolI2xDwhaUJ VzTbj90F1B1jzkim3mTEdyYXo5jteYVTOwmo3H+J8WhcaAW9vBS7TNQq7rCyblsbnd/G SgEWUiNfihJ8+EAWnpvbyCVUpEUIINnzFb7fA24Qe+8TAxe0maqxjurixzYDhWD7Q2fS FLRQOPlZqy266cmh16vOMNN4omzzM2S38vz9hk+Q8oobcw41aFDUxachiVxtwo5K5zDL J9ew==
X-Gm-Message-State: AMke39mQYfBhqkgIbTurDrFIztUkATz0DLjtRH0YmUxo3beiWHVkhn+gsQs7pkOp10nQRO7K
X-Received: by 10.200.45.103 with SMTP id o36mr37789278qta.266.1487202407177; Wed, 15 Feb 2017 15:46:47 -0800 (PST)
Received: from [192.168.8.100] ([181.201.204.34]) by smtp.gmail.com with ESMTPSA id k19sm3298764qtf.37.2017.02.15.15.46.45 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 15:46:46 -0800 (PST)
From: John Bradley <ve7jtb@ve7jtb.com>
Message-Id: <0A2CF74F-D5FE-48EF-B9AC-0F06BA1DE1D7@ve7jtb.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_EDF814DA-4181-4831-803F-AA1B233E00FE"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 15 Feb 2017 20:46:43 -0300
In-Reply-To: <CACdeXi+3dnOcnWffc3wP2WMs3VhWGcmvG2StXKM1JZ8bMVebgQ@mail.gmail.com>
To: Nick Harper <nharper@google.com>
References: <0d90fcf0-0ec7-448c-d0ad-0385062400b9@KingsMountain.com> <06A6B2F5-9026-4B30-A099-EB3B8F8AEFB4@ve7jtb.com> <CACdeXi+3dnOcnWffc3wP2WMs3VhWGcmvG2StXKM1JZ8bMVebgQ@mail.gmail.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/69TIxYeqD1jsLKZXcsaVDsrP8CE>
Cc: IETF TokBind WG <unbearable@ietf.org>, =JeffH Hodges <Jeff.Hodges@kingsmountain.com>
Subject: Re: [Unbearable] sec-token-binding header in the wild
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.\"" <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: Wed, 15 Feb 2017 23:46:50 -0000

I tried 56.0.2924.87 and 58.0.3013.0 OSX  and 58,0,3007 (ChromeOS) with no luck.

It might be the extension to capture headers that is messing me up.

What are you using.  I used the HTTP trace extension.

John B.

> On Feb 15, 2017, at 8:36 PM, Nick Harper <nharper@google.com> wrote:
> 
> I see the sec-token-binding header for both www.google.com <http://www.google.com/> and www.chromium.org <http://www.chromium.org/> from chrome on os x (version 56.0.2924.87).
> 
> On Wed, Feb 15, 2017 at 3:29 PM, John Bradley <ve7jtb@ve7jtb.com <mailto:ve7jtb@ve7jtb.com>> wrote:
> Strange I see them on both sites with Edge.
> 
> With chrome on osx and windows I am not seeing them after turning on the flag and restarting.
> 
> I don’t know if the header capture is messing with it somehow.
> 
> Google.cl negotiated TB with Edge.
> 
> John B.
> 
> > On Feb 15, 2017, at 6:12 PM, =JeffH <Jeff.Hodges@KingsMountain.com> wrote:
> >
> > fyi/fwiw...
> >
> > target: https://www.chromium.org/ <https://www.chromium.org/>
> >
> > sec-token-binding:AIkAAgBBQMaFRvLPy1uUBZer64ZluK8oBJ8kpcnO84kmCX29demwilh57_4gqlqRLBcZ_dh8x9KdN6TQQZWciZlGmhZp3sUAQFWhQBmwYSLGqlQ59KCOsYpn7Ex1dB_L5bAUTdEjd98Y5CY7NY6aczxi2gC7I6xEMAC4tONGdNOjoALTLt72REUAAA
> >
> > I used the built-in chrome developer tools to examine the request headers and obtain the above STB
> >
> >
> > [ innarestingly enuff, if one targets https://www.google.com/ <https://www.google.com/>, it seems developer tools only displays the below...
> >
> > Provisional headers are shown
> > Referer:https://www.google.com/ <https://www.google.com/>
> > User-Agent:Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36
> > ]
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > _______________________________________________
> > Unbearable mailing list
> > Unbearable@ietf.org <mailto:Unbearable@ietf.org>
> > https://www.ietf.org/mailman/listinfo/unbearable <https://www.ietf.org/mailman/listinfo/unbearable>
> 
> 
> _______________________________________________
> Unbearable mailing list
> Unbearable@ietf.org <mailto:Unbearable@ietf.org>
> https://www.ietf.org/mailman/listinfo/unbearable <https://www.ietf.org/mailman/listinfo/unbearable>
> 
>

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