Re: [Unbearable] sec-token-binding header in the wild
John Bradley <ve7jtb@ve7jtb.com> Wed, 15 February 2017 23:29 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 AD660129BCB for <unbearable@ietfa.amsl.com>; Wed, 15 Feb 2017 15:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 jopkDO9q44p8 for <unbearable@ietfa.amsl.com>; Wed, 15 Feb 2017 15:29:18 -0800 (PST)
Received: from mail-qt0-x234.google.com (mail-qt0-x234.google.com [IPv6:2607:f8b0:400d:c0d::234]) (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 E09B5129BC7 for <unbearable@ietf.org>; Wed, 15 Feb 2017 15:29:17 -0800 (PST)
Received: by mail-qt0-x234.google.com with SMTP id w20so1256335qtb.1 for <unbearable@ietf.org>; Wed, 15 Feb 2017 15:29:17 -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=deUPw2aEMHq9vWyuoRPPoCv4DUY83kzhJAiS/5jjHsk=; b=IJ+wBfa9UwmVYx5NrchTEr0lkIYayKc2XEMGUMz4SYwC6mE+H5rwrFyqKVyfhJe0+b rDinsd5tj+zDgKjpUKGHgqwy1LDJ/AVuyJUUtpHG41bVeaAaY9ZHksbJXbSMrNYvTlsn 6CuYow5byH7XTFQVTtlpYrAO5neZCcMCLqZvWboEx3e7o8vg9RL+AtjHNoXU5lBvGbcG mACD52bkjSoTSPWVykwUEDQOxyULP7FYsesVqOMWBKnhKrCL9Vc6jDJiKOcvfoLXKhNJ s8M0pUsOagj0WLSZoXo0UDquoukCWgantcawFCAem8f6Y7M0+XYrqz7OBBaS4oJR7ow3 USRQ==
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=deUPw2aEMHq9vWyuoRPPoCv4DUY83kzhJAiS/5jjHsk=; b=XkqlYKOUMeATWAmBYHveWPnWb8bLNo5EzyvrNyyTsUENXOJUnXF+AutXxnD5+2LJGl xKQPYRU28eXbZtASqrxDBgU4HQQALMzFMa1lpAZYtoxkHMN58vGlgf7/cvOgpFlY3CbA 2qPjxXNiYpTDG6SsaDznTmwSqnwdXOjAbf58dsNO29MF+8sAFCSJY+US4O9wxT83aVog 8kCRfNgHeUnXhKZyXzPaUxUwNzIsaan9/bQSN8rMrS0FYBK3ct1dv2MR7ZV2YcK3xhau sz71lRZNqLteLJtDnRJC++BdQ29C3bA02YPMeuSWYQHWeKhd+vSkJgl+kPMj8b0OdqzH Y97Q==
X-Gm-Message-State: AMke39lWVMPap+6NPyD+KH1HBqcVpXm/bwsyJTRHzrcys7kd/qjIL+3cf3IfZ5XvaSt06t2O
X-Received: by 10.200.35.124 with SMTP id b57mr37257676qtb.147.1487201356997; Wed, 15 Feb 2017 15:29:16 -0800 (PST)
Received: from [192.168.8.100] ([181.201.204.34]) by smtp.gmail.com with ESMTPSA id c144sm233094qkg.3.2017.02.15.15.29.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Feb 2017 15:29:16 -0800 (PST)
From: John Bradley <ve7jtb@ve7jtb.com>
Message-Id: <06A6B2F5-9026-4B30-A099-EB3B8F8AEFB4@ve7jtb.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_A5704236-D82A-41A4-96E6-D79D6AC1B159"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 15 Feb 2017 20:29:13 -0300
In-Reply-To: <0d90fcf0-0ec7-448c-d0ad-0385062400b9@KingsMountain.com>
To: =JeffH Hodges <Jeff.Hodges@KingsMountain.com>
References: <0d90fcf0-0ec7-448c-d0ad-0385062400b9@KingsMountain.com>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/fdSjFJtGlPLrwJrqICj2P0dkPUE>
Cc: IETF TokBind WG <unbearable@ietf.org>
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:29:20 -0000
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/ > > 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/, it seems developer tools only displays the below... > > Provisional headers are shown > Referer: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 > https://www.ietf.org/mailman/listinfo/unbearable
- [Unbearable] sec-token-binding header in the wild =JeffH
- Re: [Unbearable] sec-token-binding header in the … John Bradley
- Re: [Unbearable] sec-token-binding header in the … Nick Harper
- Re: [Unbearable] sec-token-binding header in the … John Bradley
- Re: [Unbearable] sec-token-binding header in the … Nick Harper
- Re: [Unbearable] sec-token-binding header in the … John Bradley
- Re: [Unbearable] sec-token-binding header in the … Nick Harper
- Re: [Unbearable] sec-token-binding header in the … =JeffH