Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-signing-time-03.txt
Job Snijders <job@fastly.com> Fri, 19 January 2024 10:41 UTC
Return-Path: <job@fastly.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 58CE2C14F601 for <sidrops@ietfa.amsl.com>; Fri, 19 Jan 2024 02:41:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 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_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=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 (1024-bit key) header.d=fastly.com
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 6kS1TcmT5EmI for <sidrops@ietfa.amsl.com>; Fri, 19 Jan 2024 02:41:34 -0800 (PST)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 994C1C14F5F1 for <sidrops@ietf.org>; Fri, 19 Jan 2024 02:41:34 -0800 (PST)
Received: by mail-ej1-x62b.google.com with SMTP id a640c23a62f3a-a2ac304e526so57645866b.0 for <sidrops@ietf.org>; Fri, 19 Jan 2024 02:41:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; t=1705660892; x=1706265692; darn=ietf.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=pHiDtYqKGrVPcjdeHq9VgepEUqux1gY97g8d3/kf0tU=; b=fb8oIyoG/WYvz/TPUuJFXenr1N9KFCehI9ZpcbusDFzWaF8/3da9To8usEWDWGkg54 Oawv+zbCjhGv5QmgqINJ2iuvTaEAl5PnzsW7Wn3LN+MD5XyuqIoH5OGa4B4HrCrZuzoY 2LIaQsdhOgZfSuep/BkR+67jldcu5iSP0SO/Q=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705660892; x=1706265692; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=pHiDtYqKGrVPcjdeHq9VgepEUqux1gY97g8d3/kf0tU=; b=X3P+2I9e66kTUaN4fizyzkzji1xhvv/vdCnqIfHPg5tWLSl0Gle6C3ljIOVdhe+kWZ nY3mdblj4JYpoAzE/woK+3w/N9+7RyJ6V+u1HGGVuRhqJbA2emCho6K+pbaATISaEdbU fWby2FpLsTPMCsxRwOXUdEx4zBA4N3NXNDyKQkaY+m0EZ2al7YmjocGyOOp06lEcVAv8 hWD11wg98omL/NMm+fsTLiJsW60K5cgi6vYEKheCHpPUrSs4JvLw/+EYNvfOpoyNgUp8 u9ib/mltZGOGZ1MAUux1Upioa9JQeipTESnWjfJF3wGW7a06Y+gawF8qLsDwQKGlrJW+ kjAQ==
X-Gm-Message-State: AOJu0YwuxdXApTdQNx6Q8Uhr72G7egGae2ZNQ8lYtkd1xf/PwuDx4JfM w70sWT6KhfghYd1ytMRUp3HSz0na/XLttpI6Lbb3k146YR23g98jlknH+YSdErs=
X-Google-Smtp-Source: AGHT+IHVyQ3HfRhXrQcEGOw0vltQJuZG3FwTYyoaM02gOrSSrzQ6Xdk2UY8pu7n+eGo9DNm961wxDQ==
X-Received: by 2002:a17:906:af8c:b0:a2a:4a9e:6bfe with SMTP id mj12-20020a170906af8c00b00a2a4a9e6bfemr1244414ejb.81.1705660892572; Fri, 19 Jan 2024 02:41:32 -0800 (PST)
Received: from snel ([2a10:3781:276:3:16f6:d8ff:fe47:2eb7]) by smtp.gmail.com with ESMTPSA id vk6-20020a170907cbc600b00a2dbc664e2asm6328410ejc.89.2024.01.19.02.41.31 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 19 Jan 2024 02:41:32 -0800 (PST)
Date: Fri, 19 Jan 2024 11:41:30 +0100
From: Job Snijders <job@fastly.com>
To: Ties de Kock <tdekock@ripe.net>
Cc: sidrops@ietf.org
Message-ID: <ZapR2qVBAu7lECFB@snel>
References: <170561454824.54895.360140302624981870@ietfa.amsl.com> <ZamgKc5PTJPDcISD@snel> <C10EC4E3-9A59-4BBA-B5DC-DB4680AD0B0D@ripe.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <C10EC4E3-9A59-4BBA-B5DC-DB4680AD0B0D@ripe.net>
X-Clacks-Overhead: GNU Terry Pratchett
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/JeP4XTG0zdJvbqt6c3vz-wcu7-U>
Subject: Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-signing-time-03.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, 19 Jan 2024 10:41:38 -0000
On Fri, Jan 19, 2024 at 10:52:58AM +0100, Ties de Kock wrote: > > On 18 Jan 2024, at 23:03, Job Snijders <job=40fastly.com@dmarc.ietf.org> wrote: > > Another pass was made over the text to improve the structure of the > > document and complete the surgery updates to RFC 6488. The > > "Implementation Status" section was also updated. > > Can you clarify why the document now mandates that binary signing is > disallowed? The document has consistently contained a proposal to disallow the binary signing-time attribute since its very first version, even before working group adoption (draft-spaghetti-sidrops-cms-signing-time-00, June 2023). The working group adopted that proposal. > This has significantimpact on implementations that are fully > conforming to rfc6488 and has a significant impact on those > implementations, effectively invalidating their test set of objects. Indeed, RFC 6488 is updated and simpified. Preventing invalidation of a set of private objects which solely exist for regression testing seems a non-goal to me? It seems unsurprising to me that a full coverage test suite for 6488 objects may need to be updated if 6488 is updated. > It also invalidates objects generated by public CA implementations if > a feature is enabled. Extensive long-term quantitative research showed that no public Certification Authorities issue and publish Signed Object with a CMS binary signing-time attribute. The complete absence of the binary signing-time attribute in the global RPKI is a positive signal that it is feasible to formally disallow the attribute. I suspect that lack of support for binary signing-time in commonly used libraries contributed to binary signing-time's lackluster fashionability in the field. > Please elaborate on the improvement in security posture this gives iff > any. There are more angles to consider than just security posture: disallowing the binary signing-time attribute simplifies implementations on both the signer and the RP side: instead of enumerating, parsing, checking for duplicate attributes, and also comparing the encoded timestamps against each other for both normal & binary signing-time attributes; after publication of this draft RPs merely need to confirm the absence of the binary signing-time attribute. To me this seems is a welcome simplification. Kind regards, Job
- [Sidrops] I-D Action: draft-ietf-sidrops-cms-sign… internet-drafts
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Job Snijders
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Ties de Kock
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Job Snijders
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Ties de Kock
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Job Snijders
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Ties de Kock
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Job Snijders
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Ties de Kock
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Russ Housley
- Re: [Sidrops] I-D Action: draft-ietf-sidrops-cms-… Job Snijders