Re: [websec] #42: STS exception for CRL fetching

"websec issue tracker" <trac+websec@trac.tools.ietf.org> Tue, 27 March 2012 17:43 UTC

Return-Path: <trac+websec@trac.tools.ietf.org>
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 6D23D21F8674 for <websec@ietfa.amsl.com>; Tue, 27 Mar 2012 10:43:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, 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 EUPQjtJzLVI2 for <websec@ietfa.amsl.com>; Tue, 27 Mar 2012 10:43:23 -0700 (PDT)
Received: from gamay.tools.ietf.org (gamay.tools.ietf.org [208.66.40.242]) by ietfa.amsl.com (Postfix) with ESMTP id BB81B21F8673 for <websec@ietf.org>; Tue, 27 Mar 2012 10:43:23 -0700 (PDT)
Received: from localhost ([::1] helo=gamay.tools.ietf.org) by gamay.tools.ietf.org with esmtp (Exim 4.77) (envelope-from <trac+websec@trac.tools.ietf.org>) id 1SCaQC-0006r0-80; Tue, 27 Mar 2012 13:43:04 -0400
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: "websec issue tracker" <trac+websec@trac.tools.ietf.org>
X-Trac-Version: 0.12.2
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.2, by Edgewall Software
To: draft-ietf-websec-strict-transport-sec@tools.ietf.org, tobias.gondrom@gondrom.org
X-Trac-Project: websec
Date: Tue, 27 Mar 2012 17:43:04 -0000
X-URL: http://tools.ietf.org/websec/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/websec/trac/ticket/42#comment:1
Message-ID: <085.277475f92b732ba314163f70e5ead576@trac.tools.ietf.org>
References: <070.4815d0321df1c7e00f76c8e99a03ba9d@trac.tools.ietf.org>
X-Trac-Ticket-ID: 42
In-Reply-To: <070.4815d0321df1c7e00f76c8e99a03ba9d@trac.tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: draft-ietf-websec-strict-transport-sec@tools.ietf.org, tobias.gondrom@gondrom.org, websec@ietf.org
X-SA-Exim-Mail-From: trac+websec@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on gamay.tools.ietf.org); SAEximRunCond expanded to false
Resent-To:
Resent-Message-Id: <20120327174323.BB81B21F8673@ietfa.amsl.com>
Resent-Date: Tue, 27 Mar 2012 10:43:23 -0700 (PDT)
Resent-From: trac+websec@trac.tools.ietf.org
Cc: websec@ietf.org
Subject: Re: [websec] #42: STS exception for CRL fetching
X-BeenThere: websec@ietf.org
X-Mailman-Version: 2.1.12
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: Tue, 27 Mar 2012 17:43:24 -0000

#42: STS exception for CRL fetching


Comment (by tobias.gondrom@…):

 just a personal comment:
 Just to be complete: CRL fetching does not necessarily mean a complete
 break of HSTS if CRLs come from the same server. A server could still use
 HSTS without the subdomain directive and publish the CRLs/OCSP on a
 different subdomain. Though I admit that would be a significant limitation
 of HSTS. :-(

-- 
-------------------------+-------------------------------------------------
 Reporter:               |       Owner:  draft-ietf-websec-strict-
  jeff.hodges@…          |  transport-sec@…
     Type:  enhancement  |      Status:  new
 Priority:  major        |   Milestone:
Component:  strict-      |     Version:
  transport-sec          |  Resolution:
 Severity:  In WG Last   |
  Call                   |
 Keywords:               |
-------------------------+-------------------------------------------------

Ticket URL: <http://trac.tools.ietf.org/wg/websec/trac/ticket/42#comment:1>
websec <http://tools.ietf.org/websec/>