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

Stewart Bryant <stbryant@cisco.com> Mon, 14 March 2011 18:29 UTC

Message-ID: <4D7E5ED7.9020404@cisco.com>
Date: Mon, 14 Mar 2011 18:30:47 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Lightning/1.0b2 Thunderbird/3.1.9
MIME-Version: 1.0
To: Hilarie Orman <ho@alum.mit.edu>
References: <201103141758.p2EHwkmS032697@fermat.rhmr.com>
In-Reply-To: <201103141758.p2EHwkmS032697@fermat.rhmr.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: julian.reschke@greenbytes.de, draft-ietf-httpbis-content-disp-06@tools.ietf.org, iesg@ietf.org, secdir@ietf.org
Subject: Re: [secdir] review draft-ietf-httpbis-content-disp-06
Precedence: list
Reply-To: stbryant@cisco.com

> > From a security viewpoint, I think the protocol should restrict
> filenames to ascii alphabetic characters (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.  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.

- Stewart

[secdir] review draft-ietf-httpbis-content-disp-06 Hilarie Orman
Re: [secdir] review draft-ietf-httpbis-content-di… Stewart Bryant
Re: [secdir] review draft-ietf-httpbis-content-di… Hilarie Orman
Re: [secdir] review draft-ietf-httpbis-content-di… Alexey Melnikov
Re: [secdir] review draft-ietf-httpbis-content-di… Julian Reschke
Re: [secdir] review draft-ietf-httpbis-content-di… Julian Reschke