Re: [secdir] review draft-ietf-httpbis-content-disp-06

Julian Reschke <julian.reschke@greenbytes.de> Mon, 14 March 2011 19:51 UTC

Return-Path: <julian.reschke@greenbytes.de>
X-Original-To: secdir@core3.amsl.com
Delivered-To: secdir@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 223233A6E8C; Mon, 14 Mar 2011 12:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Nw9xER+sLRIA; Mon, 14 Mar 2011 12:51:12 -0700 (PDT)
Received: from donbot.greenbytes.de (mail.greenbytes.de [217.91.35.233]) by core3.amsl.com (Postfix) with ESMTP id D5E763A6E9A; Mon, 14 Mar 2011 12:51:09 -0700 (PDT)
Received: from [192.168.178.33] (unknown [80.143.179.239]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) by donbot.greenbytes.de (Postfix) with ESMTPSA id 56532C4C0ED; Mon, 14 Mar 2011 20:52:31 +0100 (CET)
Message-ID: <4D7E71FD.7060208@greenbytes.de>
Date: Mon, 14 Mar 2011 20:52:29 +0100
From: Julian Reschke <julian.reschke@greenbytes.de>
Organization: greenbytes GmbH
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Alexey Melnikov <alexey.melnikov@isode.com>
References: <201103141758.p2EHwkmS032697@fermat.rhmr.com> <4D7E5ED7.9020404@cisco.com> <4D7E618A.6000007@isode.com>
In-Reply-To: <4D7E618A.6000007@isode.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: iesg@ietf.org, secdir@ietf.org, draft-ietf-httpbis-content-disp-06@tools.ietf.org, stbryant@cisco.com
Subject: Re: [secdir] review draft-ietf-httpbis-content-disp-06
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/secdir>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Mar 2011 19:51:13 -0000

On 14.03.2011 19:42, Alexey Melnikov wrote:
> Hi Hilarie/Stewart,
> A couple of quick comments:
>
> Stewart Bryant wrote:
>
>>> > From a security viewpoint, I think the protocol should restrict
>>> filenames to ascii alphabetic characters
>>
> I don't think this is realistic. Filenames should be allowed to be in
> non-ASCII, as pure ASCII is not sufficient for naming files in many
> languages.

Right. Fixing the I18N problem actually was the main motivation for 
writing this spec.

>>> (no "." or "/"), and that if
>>> the filename does not conform, the receiver SHOULD reject the message
>>> and send an error code back to the sender.
>>
> This value is coming in a HTTP response from a server, so the client
> can't do that.

Even if we *did* forbid these characters, we'd still need to advise 
recipients how to handle them.

> ...

Best regards, Julian