Re: [Sidrops] Manifest entry filename validation

Erik Rozendaal <> Thu, 19 November 2020 15:53 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id ECEAB3A0C15; Thu, 19 Nov 2020 07:53:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ouKlEc4Omajj; Thu, 19 Nov 2020 07:53:38 -0800 (PST)
Received: from ( [IPv6:2001:67c:2e8:11::c100:1371]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id B8EE53A0C0A; Thu, 19 Nov 2020 07:53:38 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=s1-ripe-net; h=To:Message-Id:Cc:Date:From:Subject:Mime-Version: Content-Type; bh=2nHuUItGRDDzt4VDEQT0R8KT9zHx+wmOCP/wYvCv/Z4=; b=HSDi/nEjXOWw 30Mi78UNqPOKQYvIMIL+4zexWYCtTAgBjW0fQBIw3/U8vlKeNRGN3drj7lPvuXRs4fTgjmVHg6R0d CEyK9GyX60SQYLrZUQ7ED8szbg3sJjEdhdu+efKrS0ogBPRL/HlkzwuytQQx59S985JouM9jclLmp PsDH2spwiLrZIDV0meFfl6b5CWSNaGGJDdxgtSet3XlOtM/vwcJiuerFuEdYtUpTR7uvjT9bUfuy5 Gm8coq73VOest9ks3lJ31XSHkbtEwV2BJzPqOnalXabmzH44SKZ0GzJSnGKpa9LO8KJEN/yvmXHwv jzqmtmsxX1lDkwmoAB6MHw==;
Received: from ([]:44072) by with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from <>) id 1kfmFd-0000Tx-Gj; Thu, 19 Nov 2020 16:53:37 +0100
Received: from ([2001:67c:2e8:9::c100:14e6] helo=[IPv6:2001:67c:2e8:1200::14e]) by with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from <>) id 1kfmFd-0001FN-Cl; Thu, 19 Nov 2020 16:53:37 +0100
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.\))
From: Erik Rozendaal <>
In-Reply-To: <>
Date: Thu, 19 Nov 2020 16:53:36 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Stephen Kent <>
X-Mailer: Apple Mail (2.3608.
X-ACL-Warn: Delaying message
X-RIPE-Signature: 3081e9bfa2e75d9dc8fe5e8110458a3898ac02a6125958ee1ab94cf393f3f1f0
Archived-At: <>
Subject: Re: [Sidrops] Manifest entry filename validation
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: A list for the SIDR Operations WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 19 Nov 2020 15:53:40 -0000

Hi Steve,

> On 19 Nov 2020, at 15:59, Stephen Kent <> wrote:
> I believe the character set restrictions are appropriate, as is prohibiting single and double period directory entry names, and mandating the presence of the 3-character suffix. I also have no problem with prohibiting a specific set of names, such as the Windows-centric ones you mention.
> The proposal to prohibit entries that differ only due to capitalization is worrisome. All of the other syntactic tests are easy to perform on individual entries. This test seems to require examining all entries at once to detect a violation. I'd rather not include this rule, because of the added complexity. Would folks like to mandate use of only upper or lower case characters as an alternative?

Most of the additional proposed rules are an (probably incomplete) attempt to make rsync work on non-Unix systems. Maybe we can just make this a recommendation or SHOULD, or just forget about this. RRDP should not be affected unless you directly map object URIs to filenames on a file system. 

Only allowing lower- or uppercase characters will break existing objects in the RPKI and require changes at the CA level, so that's probably a no-go.

Kind regards,