IETF Logo Mail Archive

Re: [Sidrops] [internet-drafts@ietf.org: New Version Notification for draft-spaghetti-sidrops-cms-signing-time-00.txt]

Ties de Kock <tdekock@ripe.net> Fri, 09 June 2023 08:45 UTC

Return-Path: <tdekock@ripe.net>
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 85598C1519BA for <sidrops@ietfa.amsl.com>; Fri, 9 Jun 2023 01:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.097
X-Spam-Level:
X-Spam-Status: No, score=-7.097 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=ripe.net
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ONp0UD4cNtIV for <sidrops@ietfa.amsl.com>; Fri, 9 Jun 2023 01:45:45 -0700 (PDT)
Received: from mail-mx-2.ripe.net (mail-mx-2.ripe.net [IPv6:2001:67c:2e8:11::c100:1312]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95BA9C151709 for <sidrops@ietf.org>; Fri, 9 Jun 2023 01:45:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ripe.net; s=s1-ripe-net; h=To:Message-Id:Cc:Date:From:Subject:Mime-Version:Content-Type ; bh=b6Uu3IKW8jrmLPnC7mPZjYPGYvZK8s+7d83DwJKlQDA=; b=N721pmEIcJjInQvKE2u9kBLX KM6NDvKQsCONNWfLZtIBKKAhacbvOoEnppBtAwoQdImo5KOS97ZDv/pgdVJHDm+QGuaWhSZw8CqUx mAsO91CkeH17IMvxL8ziAO4JPdpQs61gtZw9gbMrlXE1TizTlqKi8ex5Vcpbx1lnw3Ua2GB0CMVGS v6JsHUTNttt0yjLCsduTZZTOMHI0N/sghlDuc8g7lrQn1UdPgwVMoTIbzijVKzuUnJCdXJ/dffmj+ qtObL4MasHMRQP1OZqPYT3b2WFpSMc434gtjKhQlF92LSKAPnREzJjjhgXhy2cd6WoJ3zWgvPhAmD /aBArcxHZw==;
Received: from allealle.ripe.net ([2001:67c:2e8:23::c100:170c]:57672) by mail-mx-2.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <tdekock@ripe.net>) id 1q7Xke-008Zs0-0I; Fri, 09 Jun 2023 08:45:44 +0000
Received: from sslvpn.ripe.net ([193.0.20.230] helo=smtpclient.apple) by allealle.ripe.net with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <tdekock@ripe.net>) id 1q7Xkd-00009o-3B; Fri, 09 Jun 2023 08:45:44 +0000
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\))
From: Ties de Kock <tdekock@ripe.net>
In-Reply-To: <ZIH4j5Olflncv8sB@snel>
Date: Fri, 09 Jun 2023 10:45:33 +0200
Cc: sidrops@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <3728DF42-EA10-4B2A-8BC2-D96769F98857@ripe.net>
References: <ZH/Q+ea0HO542GV3@snel> <710534A0-B529-4609-9845-96BCB9139381@ripe.net> <ZICfBbaLU7u5vzC4@snel> <8036B286-155B-498C-AFDA-5E718082A7B9@ripe.net> <ZIHZAHjur0nMhdVw@snel> <CA92E210-9EB6-4834-90D0-F052600CAD55@ripe.net> <ZIH4j5Olflncv8sB@snel>
To: Job Snijders <job@fastly.com>
X-Mailer: Apple Mail (2.3731.600.7)
X-RIPE-Signature: 059faafd1cc22ebb05e1592c815fe1e15228600f1dd22d168fe2224691a8cf24
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/kpbZvdOmh9VciIugy_GPHWBXbS0>
Subject: Re: [Sidrops] [internet-drafts@ietf.org: New Version Notification for draft-spaghetti-sidrops-cms-signing-time-00.txt]
X-BeenThere: sidrops@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 09 Jun 2023 08:45:49 -0000

> On 8 Jun 2023, at 17:49, Job Snijders <job@fastly.com> wrote:
> 
> On Thu, Jun 08, 2023 at 03:58:17PM +0200, Ties de Kock wrote:
>> The issue is in this type of ordering of events:
>>  * Publication {manifest_1, roa_1}, roa_1 is on manifest_1
>>  * repository write starts at this point on timeline
>>  * Publication {manifest_2, obj_2} in the same second
>>  * Publication {other_file_1, manifest_3} some time later
>>  * An RP retrieves {manifest_1, obj_1}, obj_1 is on manifest_1
>> 
>>  * repository written to disk at this point on timeline
>>  * An RP retrieves {manifest_3, other_file_1}, obj_2 is not fetched but on manifest, failed fetch.
> 
> I am not sure I can follow the above description - but I guess you are
> saying it is suboptimal for a CA to do multiple issuances for the same
> object within the same second if it is in any way visible to the RP?

That is the gist. The result is a failed fetch for the affected RPs [that
observed this ordering of events] that persists until the object causing the
invalid state is changed again (hours for manifests, many months for
certificates or other objects).

For signed objects, one-time-use EE certificates mitigate the issue. I am
unsure how to mitigate this for CA certificates [outside the scope here].

Kind regards,
Ties

v2.23.0 | Report a Bug | By Email