IETF Logo Mail Archive

Re: [websec] Strict-Transport-Security syntax redux

Julian Reschke <julian.reschke@gmx.de> Thu, 05 January 2012 18:06 UTC

Return-Path: <julian.reschke@gmx.de>
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 90DD021F882D for <websec@ietfa.amsl.com>; Thu, 5 Jan 2012 10:06:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.87
X-Spam-Level:
X-Spam-Status: No, score=-103.87 tagged_above=-999 required=5 tests=[AWL=-1.271, 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 oc-Y540MKcgI for <websec@ietfa.amsl.com>; Thu, 5 Jan 2012 10:06:46 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id A7B6C21F875F for <websec@ietf.org>; Thu, 5 Jan 2012 10:06:45 -0800 (PST)
Received: (qmail invoked by alias); 05 Jan 2012 18:06:44 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp034) with SMTP; 05 Jan 2012 19:06:44 +0100
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+A3W9QI3WAgaX3la5ARCfg5RboU7V8NHdcfxhz+m jI/wdt9pOyXaLd
Message-ID: <4F05E6B2.8050301@gmx.de>
Date: Thu, 05 Jan 2012 19:06:42 +0100
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: Anne van Kesteren <annevk@opera.com>
References: <4EAB66B3.4090404@KingsMountain.com> <4EABB25E.9000900@gmx.de> <4EFC5F7B.7050304@gmx.de> <CAJE5ia_HhenArVey=5-ttLqh4-vbBE01TFZKuzAmAtHQJQJ3kQ@mail.gmail.com> <4EFCD7E4.5060507@gmx.de> <CAJE5ia-w47HHhnTBAE_PMApAAdCu=6PJexaaoJO0MZ23Ae-vcw@mail.gmail.com> <4EFCDA9C.90308@gmx.de> <CAJE5ia-E1nhN1YGV6uy3uEq4oboQowDm4FboKbWV1kunHQmXPw@mail.gmail.com> <4EFCDDD5.6040005@gmx.de> <CAJE5ia8CL9ozRJgRNCdu6XwVT0paVuVUreB12f-BiMvH+wiq6A@mail.gmail.com> <4EFD73E6.1060506@gmx.de> <CAJE5ia8RBa8iCd_9TjXyzG54VASa6qqGomsO9gL-qQ2ia=BKLg@mail.gmail.com> <4EFD7C09.9050702@gmx.de> <CAJE5ia8aN_MKUX_7ehp6siw=CY7nC4aSRPoPcsaDX8+emwaFVw@mail.gmail.com> <4EFD8BCE.7010909@gmx.de> <CAJE5ia9cziSx-xb6nCEFXJkbu2Ls_ZQmYHpfrC7UK3ig3ZmM2g@mail.gmail.com> <4F052D2E.5050200@gondrom.org> <op.v7lqsdyu64w2qv@annevk-macbookpro.local> <4F056553.9030409@gmx.de> <553F526C-4433-489B-80B5-4C29E5FB0DC4@vpnc.org> <op.v7mg5ns564w2qv@annevk-macbookpro.local>
In-Reply-To: <op.v7mg5ns564w2qv@annevk-macbookpro.local>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: websec@ietf.org
Subject: Re: [websec] Strict-Transport-Security syntax redux
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: Thu, 05 Jan 2012 18:06:46 -0000

On 2012-01-05 18:50, Anne van Kesteren wrote:
> On Thu, 05 Jan 2012 16:59:58 +0100, Paul Hoffman <paul.hoffman@vpnc.org>
> wrote:
>> FWIW, I'm with Julian on this, particularly:
>>
>>> - principle of least surprise and consistency - if quoted-string
>>> works in other header fields with param syntax, why not here?
>>
>> "We invented a header that your message-producing software must
>> special-case" is not a good way to get security.
>
> If the header-consuming software works that way, it might be the only
> way. What the right way to go here is kind of depends on how header
> field values are typically implemented in practice. I suspect it to be
> rather messy.

It is indeed messy. And I think one of the reasons it is that there are 
too many different formats, and too many special cases within a single 
format; thus my proposal to allow token/quoted-string for all 
parameters, and not only some.

Best regards, Julian

v2.23.0 | Report a Bug | By Email