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

Alexey Melnikov <alexey.melnikov@isode.com> Mon, 14 March 2011 18:41 UTC

Return-Path: <alexey.melnikov@isode.com>
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 EB5213A6A03; Mon, 14 Mar 2011 11:41:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.344
X-Spam-Level:
X-Spam-Status: No, score=-102.344 tagged_above=-999 required=5 tests=[AWL=0.255, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 opoMrANd8hLx; Mon, 14 Mar 2011 11:41:26 -0700 (PDT)
Received: from rufus.isode.com (rufus.isode.com [62.3.217.251]) by core3.amsl.com (Postfix) with ESMTP id 1A0BA3A68CE; Mon, 14 Mar 2011 11:41:26 -0700 (PDT)
Received: from [192.168.1.124] ((unknown) [62.3.217.253]) by rufus.isode.com (submission channel) via TCP with ESMTPA id <TX5hqAADLzo0@rufus.isode.com>; Mon, 14 Mar 2011 18:42:48 +0000
X-SMTP-Protocol-Errors: NORDNS
Message-ID: <4D7E618A.6000007@isode.com>
Date: Mon, 14 Mar 2011 18:42:18 +0000
From: Alexey Melnikov <alexey.melnikov@isode.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915
X-Accept-Language: en-us, en
To: stbryant@cisco.com, Hilarie Orman <ho@alum.mit.edu>
References: <201103141758.p2EHwkmS032697@fermat.rhmr.com> <4D7E5ED7.9020404@cisco.com>
In-Reply-To: <4D7E5ED7.9020404@cisco.com>
MIME-Version: 1.0
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, julian.reschke@greenbytes.de
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 18:41:27 -0000

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.

>> (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.

>> The sender should not be
>> allowed to specify a file extension.  The receiver SHOULD write the
>> files into a quarantined disk area using a temporary filename, the
>> file to be released to the recommended name pending manual review.
>> But, that would break the world, as would so many security
>> recommendations.
>
> Surely you mean ascii alpha-numeric characters?
>
> Text fixing this would also address the security component of my Discuss.