[OAUTH-WG] SD-JWT disclosure ordering
David Waite <david@alkaline-solutions.com> Tue, 24 September 2024 16:51 UTC
Return-Path: <david@alkaline-solutions.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8E83EC1F5884 for <oauth@ietfa.amsl.com>; Tue, 24 Sep 2024 09:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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, HTML_MESSAGE=0.001, 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=alkaline-solutions.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 tcDIZFmAUWy7 for <oauth@ietfa.amsl.com>; Tue, 24 Sep 2024 09:50:56 -0700 (PDT)
Received: from mail.alkaline-solutions.com (caesium6.alkaline.solutions [157.230.133.164]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 90B0FC17C8B3 for <oauth@ietf.org>; Tue, 24 Sep 2024 09:50:56 -0700 (PDT)
From: David Waite <david@alkaline-solutions.com>
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alkaline-solutions.com; s=dkim; t=1727196655; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=Z7TjJBWgspK6oqi4jdWePpzA/8YGzBpB11z7XHedrwI=; b=RCO4VhPfLv4WsSLfg1gSxur1qLL7glHS/N+5iryznpP7wBEAiLyqNm6NcNagmqjGs281GN w6b5fDIzBm7irXjmWAKNpYWnyMOqnFtIH4iABQfIBTlZqtUCFwu34p+ubE/1NKueXexUCf y7pMBUYEZxw0gzLA2Rjci+U9sFFkZTtB1QisvEnWHLNihQXK/G6hg4PWt642240wVKCqK6 HigWSIc5dngUAyThf+L308kL19ZZZOReeislSboiRK/iOYLbydTxlDI30B6vEfzW6mc6ZH +u/iR7M+J3k/25ERi2Ish4wDbn3E9h7GZKbLmb23gx34miobGrnrZWu0PgytLQ==
Authentication-Results: mail.alkaline-solutions.com; auth=pass smtp.mailfrom=david@alkaline-solutions.com
Content-Type: multipart/alternative; boundary="Apple-Mail=_50361C5A-AA3A-452B-AC84-87E48786920F"
Mime-Version: 1.0
Message-Id: <2CE8DA08-0992-413D-9810-B85986B3E828@alkaline-solutions.com>
Date: Tue, 24 Sep 2024 10:50:45 -0600
To: "oauth@ietf.org" <oauth@ietf.org>
X-Spamd-Bar: /
Message-ID-Hash: KKDWKFKVIJ4KDEKC6Y2JGTGVTME7AZHQ
X-Message-ID-Hash: KKDWKFKVIJ4KDEKC6Y2JGTGVTME7AZHQ
X-MailFrom: david@alkaline-solutions.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-oauth.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: [OAUTH-WG] SD-JWT disclosure ordering
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/Us7UCX8mDvPB-6S56L7GyYYsI-M>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Owner: <mailto:oauth-owner@ietf.org>
List-Post: <mailto:oauth@ietf.org>
List-Subscribe: <mailto:oauth-join@ietf.org>
List-Unsubscribe: <mailto:oauth-leave@ietf.org>
I didn’t see anything in SD-JWT about a canonical disclosure ordering. Disclosures from the issuer (and after selective disclosure) are to the best of my understanding an unordered set - they are expressed in an order, but that order is not meaningful for processing. The disclosures may be sorted or randomized as part of the presentation process at the holder’s leisure. However, once you do key binding JWTs, that order is meaningful because shuffling the disclosures will break that signature. Can I suggest 5.3.1 be tweaked to represent this, perhaps to: > The sd_hash value MUST be taken over the US-ASCII bytes of the encoded SD-JWT, i.e., the Issuer-signed JWT, a tilde character, and any Disclosures selected for presentation to the Verifier in presented order, each followed by a tilde character: -DW
- [OAUTH-WG] SD-JWT disclosure ordering David Waite
- [OAUTH-WG] Re: SD-JWT disclosure ordering Brian Campbell