Re: [Sidrops] Manifest entry filename validation

Russ Housley <housley@vigilsec.com> Mon, 23 November 2020 15:22 UTC

Return-Path: <housley@vigilsec.com>
X-Original-To: sidrops@ietfa.amsl.com
Delivered-To: sidrops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20EA23A0365 for <sidrops@ietfa.amsl.com>; Mon, 23 Nov 2020 07:22:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.004
X-Spam-Level:
X-Spam-Status: No, score=0.004 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4XNO8LMeQh0H for <sidrops@ietfa.amsl.com>; Mon, 23 Nov 2020 07:21:59 -0800 (PST)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7224F3A03EE for <sidrops@ietf.org>; Mon, 23 Nov 2020 07:21:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id C5C61300BB2 for <sidrops@ietf.org>; Mon, 23 Nov 2020 10:21:56 -0500 (EST)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id TPNtayW_H1MJ for <sidrops@ietf.org>; Mon, 23 Nov 2020 10:21:54 -0500 (EST)
Received: from a860b60074bd.fios-router.home (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id C7D22300B22; Mon, 23 Nov 2020 10:21:54 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <a37fbf04-e8d6-3a37-4664-4e35cbb2f8ce@verizon.net>
Date: Mon, 23 Nov 2020 10:21:56 -0500
Cc: Job Snijders <job@ntt.net>, sidrops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <EBDEC8B5-5B38-4ADD-8604-A5E6280FAF9B@vigilsec.com>
References: <18CC986C-97FA-41F6-A530-F782D3104A31@ripe.net> <73eae8a5-a400-cb45-7fbc-9cc7f79be804@verizon.net> <X7aywnRgq3ubVUBu@bench.sobornost.net> <a37fbf04-e8d6-3a37-4664-4e35cbb2f8ce@verizon.net>
To: Stephen Kent <stkent=40verizon.net@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/aQa0hohWjtlgYUTsFDIbbHaMGNk>
Subject: Re: [Sidrops] Manifest entry filename validation
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <sidrops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidrops>, <mailto:sidrops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sidrops/>
List-Post: <mailto:sidrops@ietf.org>
List-Help: <mailto:sidrops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidrops>, <mailto:sidrops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2020 15:22:01 -0000

If no one is useing multiple DOTs in their filenames, this this is clear and straightforward.

Russ

> On Nov 23, 2020, at 9:43 AM, Stephen Kent <stkent=40verizon.net@dmarc.ietf.org> wrote:
> 
> Job,
> 
> I like your more concise phrasing of the file name restrictions. I note, however, that they are not identical to what was initially proposed. For example, the original proposal did not prohibit more than one "." in a file name, except for the ".." case.
> 
> Before I adopt your suggested text I'd like to see comments from the WG that confirm agreement with your version of the constraints.
> 
> Thanks,
> 
> Steve
>> On Thu, Nov 19, 2020 at 12:32:42PM -0500, Stephen Kent wrote:
>>> How about the following text:
>>> 
>>> Section 4.2.2
>>> 
>>> To promote interoperability across file systems, the following restrictions
>>> are imposed on the file names that appear in the fileList:
>>> 
>>> 1.Only a subset of IA5string characters are permitted: a-z, A-Z, 0-9, .
>>> (dot), - (dash), and _ (underscore).
>>> 
>>> 2.No blank file names are permitted.
>>> 
>>> 3.Single and double dot (. and ..) file names are prohibited.
>>> 
>>> 4.The three-character filename extension defined for each object type MUST
>>> be present and MUST be lowercase, e.g., cer, roa, and crl.
>> I reworded things a bit:
>> 
>> -----------
>> 
>> The following restrictions are imposed on the names that appear in the fileList:
>> 
>> 1. Only a subset of IA5string characters are permitted: a-z, A-Z, 0-9, . (DOT), - (HYPHEN), and _ (UNDERSCORE).
>> 
>> 2. Each name MUST be suffixed with the appropriate filename extension defined the object type and MUST be lowercase, e.g., '.cer', '.roa', or '.crl'.
>> 
>> 3. The . (DOT) character MUST appear exactly once in a name.
> 
> 
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops