[websec] fyi: State of HSTS Deployment in 2013-Oct
=JeffH <Jeff.Hodges@KingsMountain.com> Sun, 10 August 2014 05:53 UTC
Return-Path: <Jeff.Hodges@kingsmountain.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E75E11A0643 for <websec@ietfa.amsl.com>; Sat, 9 Aug 2014 22:53:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.033
X-Spam-Level: *
X-Spam-Status: No, score=1.033 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, IP_NOT_FRIENDLY=0.334, SPF_PASS=-0.001] autolearn=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 Fr1a0NFHb3R9 for <websec@ietfa.amsl.com>; Sat, 9 Aug 2014 22:53:42 -0700 (PDT)
Received: from gproxy4-pub.mail.unifiedlayer.com (gproxy4-pub.mail.unifiedlayer.com [69.89.23.142]) by ietfa.amsl.com (Postfix) with SMTP id AFC3D1A0640 for <websec@ietf.org>; Sat, 9 Aug 2014 22:53:42 -0700 (PDT)
Received: (qmail 17215 invoked by uid 0); 10 Aug 2014 05:53:39 -0000
Received: from unknown (HELO cmgw3) (10.0.90.84) by gproxy4.mail.unifiedlayer.com with SMTP; 10 Aug 2014 05:53:39 -0000
Received: from box514.bluehost.com ([74.220.219.114]) by cmgw3 with id cztX1o0012UhLwi01ztaJ6; Sun, 10 Aug 2014 05:53:38 -0600
X-Authority-Analysis: v=2.1 cv=DIUcvU9b c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=cNaOj0WVAAAA:8 a=f5113yIGAAAA:8 a=ekOJvlQLSnQA:10 a=YXR_0xDj8ZkA:10 a=AZJedDZmUUUA:10 a=3NT3xRclEPMA:10 a=8nJEP1OIZ-IA:10 a=ieNpE_y6AAAA:8 a=XYUc-DgfXtMA:10 a=aQyOShshic0A:10 a=gX9PHW2fAAAA:8 a=A1X0JdhQAAAA:8 a=NEAV23lmAAAA:8 a=cm27Pg_UAAAA:8 a=1XWaLZrsAAAA:8 a=s5MJRaXj4EHIG1AAJ-AA:9 a=wPNLvfGTeEIA:10 a=9qIKL8-R5rUA:10 a=VlZU0XKO32wA:10 a=zv9_9hqRWm8A:10
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=kingsmountain.com; s=default; h=Content-Transfer-Encoding:Content-Type:Subject:To:MIME-Version:From:Date:Message-ID; bh=SOL++2UmDyNwiqdWnUjbKqNvAvg5lo4oDaAtWpN6wZQ=; b=WEzZ5sduIxjZL/kGce+yDEhuraUlTwmoBqHq7mggbW2kkyy6HxRnJGRxe2zvA2D/XtoiTeNRxr8x2VFfDsLxmazx10s8y+o2+thJwYuWO3EhsOFSInqbi+7PESeoNb48;
Received: from [98.248.231.21] (port=54148 helo=[192.168.11.14]) by box514.bluehost.com with esmtpsa (TLSv1:DHE-RSA-AES128-SHA:128) (Exim 4.82) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1XGM4S-0003RL-9M for websec@ietf.org; Sat, 09 Aug 2014 23:53:32 -0600
Message-ID: <53E708DB.4010505@KingsMountain.com>
Date: Sat, 09 Aug 2014 22:53:31 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: IETF WebSec WG <websec@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Identified-User: {11025:box514.bluehost.com:kingsmou:kingsmountain.com} {sentby:smtp auth 98.248.231.21 authed with jeff.hodges+kingsmountain.com}
Archived-At: http://mailarchive.ietf.org/arch/msg/websec/caO9aKtOjZiorITuwDCrk30j_Gs
Subject: [websec] fyi: State of HSTS Deployment in 2013-Oct
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Web Application Security Minus Authentication and Transport <websec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/websec>, <mailto:websec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/websec/>
List-Post: <mailto:websec@ietf.org>
List-Help: <mailto:websec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/websec>, <mailto:websec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 10 Aug 2014 05:53:44 -0000
Here's an interesting & relevant draft paper by Lucas Garron (and Andrew Bortz & Dan Boneh).. The State of HSTS Deployment: A Survey and Common Pitfalls https://garron.net/crypto/hsts/hsts-2013.pdf Note that "S 8.5 Securing https://example.com from a subdomain" is essentially the issue that Eric Lawrence recently filed against RFC6797 HSTS. The paper is worth a read, and the scan code is here.. https://github.com/lgarron/HSTS/tree/scan ..see also the discussion in this thread on <security-dev@chromium.org>.. State of HSTS in on the Web (2013) https://groups.google.com/a/chromium.org/forum/#!topic/security-dev/Ibdf-x_uqEs HTH, =JeffH