Re: [Unbearable] sec-token-binding header in the wild
=JeffH <Jeff.Hodges@KingsMountain.com> Thu, 16 February 2017 01:15 UTC
Return-Path: <Jeff.Hodges@kingsmountain.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 8862B129461 for <unbearable@ietfa.amsl.com>; Wed, 15 Feb 2017 17:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.288
X-Spam-Level:
X-Spam-Status: No, score=-3.288 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-1.887, RCVD_IN_SORBS_SPAM=0.5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 5nzh27-foK_u for <unbearable@ietfa.amsl.com>; Wed, 15 Feb 2017 17:15:36 -0800 (PST)
Received: from gproxy8-pub.mail.unifiedlayer.com (gproxy8-pub.mail.unifiedlayer.com [67.222.33.93]) by ietfa.amsl.com (Postfix) with SMTP id 74CFF129444 for <unbearable@ietf.org>; Wed, 15 Feb 2017 17:15:36 -0800 (PST)
Received: (qmail 14912 invoked by uid 0); 16 Feb 2017 01:15:29 -0000
Received: from unknown (HELO cmgw2) (10.0.90.83) by gproxy8.mail.unifiedlayer.com with SMTP; 16 Feb 2017 01:15:29 -0000
Received: from box514.bluehost.com ([74.220.219.114]) by cmgw2 with id lDFS1u00G2UhLwi01DFVl9; Wed, 15 Feb 2017 18:15:29 -0700
X-Authority-Analysis: v=2.1 cv=H5NInYoi c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=n2v9WMKugxEA:10 a=KXSRst2svff6QrsAAjAA:9 a=QEXdDO2ut3YA:10
Received: from [173.224.162.69] (port=62743 helo=[10.225.80.64]) by box514.bluehost.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1ceAfO-0007g2-Av for unbearable@ietf.org; Wed, 15 Feb 2017 18:15:26 -0700
To: IETF TokBind WG <unbearable@ietf.org>
From: =JeffH <Jeff.Hodges@KingsMountain.com>
Message-ID: <62a0ad87-aa67-1a78-1a47-fe7624cf7492@KingsMountain.com>
Date: Wed, 15 Feb 2017 17:15:25 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - box514.bluehost.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - KingsMountain.com
X-BWhitelist: no
X-Source-IP: 173.224.162.69
X-Exim-ID: 1ceAfO-0007g2-Av
X-Source:
X-Source-Args:
X-Source-Dir:
X-Source-Sender: ([10.225.80.64]) [173.224.162.69]:62743
X-Source-Auth: jeff.hodges+kingsmountain.com
X-Email-Count: 12
X-Source-Cap: a2luZ3Ntb3U7a2luZ3Ntb3U7Ym94NTE0LmJsdWVob3N0LmNvbQ==
Archived-At: <https://mailarchive.ietf.org/arch/msg/unbearable/r0GFwUh7FG0c58Y88PNQFDUTV6Q>
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: Thu, 16 Feb 2017 01:15:37 -0000
Nick said: > I've occasionally seen the "Provisional headers are shown" message - > I think that comes up if the request is served from cache, yeah > in which case it makes sense that there's no sec-token-binding header > since there was no request that went to a server. ah. tho I'd turned caching off I'd thought... =JeffH
- [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