Re: [websec] "This site is testing HSTS" directive (was Issue #41 add parameter indicating whether to hardfail or not)

=JeffH <Jeff.Hodges@KingsMountain.com> Fri, 29 June 2012 20:43 UTC

Return-Path: <Jeff.Hodges@KingsMountain.com>
X-Original-To: websec@ietfa.amsl.com
Delivered-To: websec@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F22811E8072 for <websec@ietfa.amsl.com>; Fri, 29 Jun 2012 13:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.495
X-Spam-Level:
X-Spam-Status: No, score=-101.495 tagged_above=-999 required=5 tests=[AWL=-1.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NCUB4EBqgJ95 for <websec@ietfa.amsl.com>; Fri, 29 Jun 2012 13:43:09 -0700 (PDT)
Received: from oproxy5-pub.bluehost.com (oproxy5.bluehost.com [IPv6:2605:dc00:100:2::a5]) by ietfa.amsl.com (Postfix) with SMTP id C04C121F8483 for <websec@ietf.org>; Fri, 29 Jun 2012 13:43:01 -0700 (PDT)
Received: (qmail 1644 invoked by uid 0); 29 Jun 2012 20:43:01 -0000
Received: from unknown (HELO box514.bluehost.com) (74.220.219.114) by cpoproxy2.bluehost.com with SMTP; 29 Jun 2012 20:43:01 -0000
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:CC:To:MIME-Version:From:Date:Message-ID; bh=Xjs7Gv1jJZxfRnSfSkrm6ixKP/XysiYxtcfl/yZYjxA=; b=S4DR4Qp5OVTbv7woMXVz33N/2hj43v8deQX7ISuPS/01KPkSk0nL6cjMyS3Zy+n8OHe+yUmIYb8KyJAbx4Nt7Qn7aTO6G58ULjXB7snIGlu9n085rmRS3M5z+WqRLcP+;
Received: from [216.113.168.128] (port=37582 helo=[10.244.136.119]) by box514.bluehost.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.76) (envelope-from <Jeff.Hodges@KingsMountain.com>) id 1Ski1s-0001OA-My; Fri, 29 Jun 2012 14:43:00 -0600
Message-ID: <4FEE1353.2070506@KingsMountain.com>
Date: Fri, 29 Jun 2012 13:42:59 -0700
From: =JeffH <Jeff.Hodges@KingsMountain.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: Eric Rescorla <ekr@rtfm.com>
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 216.113.168.128 authed with jeff.hodges+kingsmountain.com}
Cc: IETF WebSec WG <websec@ietf.org>
Subject: Re: [websec] "This site is testing HSTS" directive (was Issue #41 add parameter indicating whether to hardfail or not)
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
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: Fri, 29 Jun 2012 20:43:10 -0000

[ updated subject ]

 > It's not so much with existing HSTS as with something like
 > draft-evans-palmer-hsts-pinning.
 > Consider the case where I operate a site that load balances between
 > two certs, A and B
 > but I inadvertantly advertise a pin for A only. If I understand S 2.1
 > correctly, ...

just fyi on a meta level, note that draft-evans-palmer-hsts-pinning is 
superseded by draft-ietf-websec-key-pinning, and no longer is an extension to 
the STS header field.

=JeffH