[Rats] Re: Freshness with Nonces

Michael Richardson <mcr+ietf@sandelman.ca> Mon, 24 June 2024 18:38 UTC

Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: rats@ietfa.amsl.com
Delivered-To: rats@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D8A4DC14F69E; Mon, 24 Jun 2024 11:38:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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, 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 (2048-bit key) header.d=sandelman.ca
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 nig_tr7S9oyA; Mon, 24 Jun 2024 11:38:37 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 8261AC1840DB; Mon, 24 Jun 2024 11:38:37 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 84C583898D; Mon, 24 Jun 2024 14:38:36 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6qizuAO4KnJS; Mon, 24 Jun 2024 14:38:36 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id DACC63898C; Mon, 24 Jun 2024 14:38:35 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1719254315; bh=SieZjCt0TAl6NLRcBD5o0Ca31R7BLCKY4DI/zlLvLPs=; h=From:To:Subject:In-Reply-To:References:Date:From; b=LeSwmgCiaHvy3nm0h6vyOUwaaFede9ICSBBX+Oq4TUC/ujVIsn5X5jLRD5rZmELxl GCPXadW0m9Bkb9PlY5N3U5n3DnfAXuLqDSaBNAJnAsCioqX5Tr9iQJ/ys8ZRyomA77 C6IwlBTGxS33M3bZH0RKbA9P3bXLix5R5rqSeSN59Vv2jIYZNG1aKI9HZy9H705EmG v0hWAemyDgPAWAe3u2YGNDmYTz7c52RS9F0YuHkFlQx0/bY4nzV46Pwz1eSWhJvHti Y6YRat135vmUpiRYeYVoYstqwn1f8HiMhvNbggPDzWQDidWZ6EKoFE83jt89j3FIs/ EbOMov6sxVfzA==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D68317F4; Mon, 24 Jun 2024 14:38:35 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "spasm@ietf.org" <spasm@ietf.org>, rats <rats@ietf.org>
In-Reply-To: <48394D3C-AE2C-4D5B-9FA9-1D508DC07795@redhoundsoftware.com>
References: <3D0F8C7D-D1C6-4014-B69B-714771152A7E@redhoundsoftware.com> <trinity-e9d548b8-7cfa-4b36-a9d3-a304d09cba32-1719211973692@3c-app-gmx-bs24> <D13A6B1A-37B5-413B-9D8A-9368F24B7827@redhoundsoftware.com> <fb269c87-c360-827b-f108-a5f952f6f107@ietf.contact> <48394D3C-AE2C-4D5B-9FA9-1D508DC07795@redhoundsoftware.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Mon, 24 Jun 2024 14:38:35 -0400
Message-ID: <18637.1719254315@obiwan.sandelman.ca>
Message-ID-Hash: CHTRYYMYRQ74THHS3JLW3GBLIOMW6FHI
X-Message-ID-Hash: CHTRYYMYRQ74THHS3JLW3GBLIOMW6FHI
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-rats.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Rats] Re: Freshness with Nonces
List-Id: Remote ATtestation procedureS <rats.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rats/Dqq_vlFt4OwR9qCHh0ZQ08aCWmE>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rats>
List-Help: <mailto:rats-request@ietf.org?subject=help>
List-Owner: <mailto:rats-owner@ietf.org>
List-Post: <mailto:rats@ietf.org>
List-Subscribe: <mailto:rats-join@ietf.org>
List-Unsubscribe: <mailto:rats-leave@ietf.org>

I wanted to add that for CSR-transporting protocols that run over TLS, such
as RFC7030 (EST), (and perhaps SCEP), that a nonce could be derived from a
TLS exporter.

Maybe!
In the case of 7030 (or RFC8995) then the TLS connection is with the
Registrar, which is sometimes the CA.
But, it's likely *not* the verifier, but rather the Relying party.
If it's acceptable for the RP to generate the nonce, then it can be provided
to the Verifier by the RP.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide