[OAUTH-WG] Re: SD-JWT linkability

Tom Jones <thomasclinganjones@gmail.com> Tue, 17 December 2024 21:59 UTC

Return-Path: <thomasclinganjones@gmail.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 E1E8AC14CE51 for <oauth@ietfa.amsl.com>; Tue, 17 Dec 2024 13:59:23 -0800 (PST)
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, FREEMAIL_FROM=0.001, HTML_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 3rkNLP_EtHJx for <oauth@ietfa.amsl.com>; Tue, 17 Dec 2024 13:59:23 -0800 (PST)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD538C14F698 for <oauth@ietf.org>; Tue, 17 Dec 2024 13:59:21 -0800 (PST)
Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-30036310158so50834791fa.0 for <oauth@ietf.org>; Tue, 17 Dec 2024 13:59:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734472760; x=1735077560; darn=ietf.org; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=MowyFf4ebHebIAebLrWV4odlU+THXoRs07/WvmbXLtc=; b=eReCa1F7+2qklHZTxzMMs5xqr+dn+BtgbfqSZg9XTfXbde714dpNmk0UPnqTjMGAgv 1IenpGzmt08SxO5luGlzvNLRVBzKC6+eEBzgU26U8e1+Op39kYWdvhuzMgM+InqW2bCb 2XC5QLIkYwQWsLG8UP0/XbqLw710Bv7bQzjGkV7g/aal51WwCU3zajnAAfNvyG/fXMaW cDAWMIzSIgVW04suRUMq8u+Up9Df8qSaQbZ0XhSf3BwlVbg3iQuirnmrnEe1T8d/3XhH gW3opXdZoITWl6znwKmPt2nsrygcHhy99vxrFAQpAQqHVqdR3wib8krL4ElwPFBeKiYA /aoA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734472760; x=1735077560; h=cc:to:subject:message-id:date:from:reply-to:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=MowyFf4ebHebIAebLrWV4odlU+THXoRs07/WvmbXLtc=; b=FDCP/ZZqCPtqot/2WRunhDEcm93X6sHaMG+HjO8//gAMQ770ekryqgvTd9cgHXTS9v djhxBD6epfJkmQRwwos+EA4X4wPtCZ7bgrVrSxsku0QiuvsXkkmvTI4EEV2dq53o0ibX gDyJoFX/fuTMwZ3kt6s/Db6AQ2t1YeiAErlLWsQpOogD+jCfsLJf9Mre6E7Z4zxhK+eR CJGszqXLOYKOBW0YUY2hDYy2zvff0xhAKCuIsPmH9C2SuX7JIY3dMUbiv5VnwaztBgSd YSn+lyHQFJ0Pk5510u13IX0+sHHBhMCo0OArGz8YuwdiJE5hUbZsDO1tN+o9FuY8+Q+X puqA==
X-Gm-Message-State: AOJu0Yw19H5P10sW7w1oAKFrmykmOv3kD260znXnDH2JiU7WCEcrniUG kX/ztYHQ6PkKkCHymRomfLSDHSSDYW6kAKRzW2Oo8LEFiCxj8ZDzP/eVfb4SKy4qpdDptJVpdP+ C2szHlLJTNc/HIE83B8c8k4yzLmc=
X-Gm-Gg: ASbGncs2dXXcz2tiGFmzXDORJdIECcjesGZB2wGGDg50Rec0l6u/pa12kUz9z8o8K2D ah4YNVSmavwObP0lD9JoFg6Dg7mDqpgk2ZAeTlaODo6NDEr6IWT8JYu0ozaql29FG8TzsVuw=
X-Google-Smtp-Source: AGHT+IH9+d0S4PPLHFDLPtyu26NQIdKKaEewcwmRg9TznQ7FPAwJcTJcBV8XxEYdV7Rip1FFUhkiComI728Vep/hx0M=
X-Received: by 2002:a2e:2e0a:0:b0:300:3671:2f57 with SMTP id 38308e7fff4ca-3044db5cde7mr1645301fa.41.1734472759313; Tue, 17 Dec 2024 13:59:19 -0800 (PST)
MIME-Version: 1.0
References: <CACsn0ckGp4AocD1fQbMCs45P_Z5vjveggzDJw=-Vk5kxinM28Q@mail.gmail.com> <080c5dba-c3af-47d5-a773-ea41f5f720b4@danielfett.de> <3E1E5A8D-D6D8-41AA-8522-D5323143A1DB@tzi.org> <b8e4be44-465d-4603-8dd8-2628f4a9449c@posteo.de>
In-Reply-To: <b8e4be44-465d-4603-8dd8-2628f4a9449c@posteo.de>
From: Tom Jones <thomasclinganjones@gmail.com>
Date: Tue, 17 Dec 2024 13:59:08 -0800
Message-ID: <CAK2Cwb6opdObKBFq3x0Et5or40Oe2iLu_jRrN_+AF40u43B3Xg@mail.gmail.com>
To: Paul Bastian <paul.bastian@posteo.de>
Content-Type: multipart/alternative; boundary="000000000000b10ffe06297e683f"
Message-ID-Hash: HRXLWDASEPVCAC4YBC2CB6BCMAINXLEL
X-Message-ID-Hash: HRXLWDASEPVCAC4YBC2CB6BCMAINXLEL
X-MailFrom: thomasclinganjones@gmail.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
CC: oauth@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Reply-To: peace@acm.org
Subject: [OAUTH-WG] Re: SD-JWT linkability
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/FSoe9Bxy0m4Mf_Ks0I7n-UIid6o>
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 don't disagree with Paul - my comments addressed the text of the change.
Will "Disclosures" be a part of the standard (even security concerns?)
If that is the case, then the means to address the disclosures will need to
be realistic.

AFAIK the only proposed use of the SD-JWT is in OID4VP.  In that case the
selective disclosure will be irrelevant as the means to disclose the
selection will be inadequate.  So the SD-JWT may well technically work, but
the first use will be fraudulent as the selection will not be by informed
user consent.

Peace ..tom jones


On Tue, Dec 17, 2024 at 12:05 PM Paul Bastian <paul.bastian@posteo.de>
wrote:

> I think  people on this list are overly critical towards SD-JWT and I
> don't understand it. I'm not aware that these kind of statements have
> been done in other IETF standards in a comparable context. Please
> correct me why neither JWT, CWT, JOSE, COSE, CBOR nor X.509 have
> specific text about these kind of things. RFC7049 doesn't even have a
> privacy consideration section although it contains linkable data
> structures that may be utilized to track users.
>
> SD-JWT is a data container that brings some additional features to
> JWT/JWS, but nothing more than that and we shouldn't treat it
> differently. To me, SD-JWT includes a thourough privacy consideration
> section on unlinkability which is way beyond what other IETF
> specifications have done is looks sufficient to me.
>
> Best regards,
>
> Paul
>
> On 13.12.24 15:30, Carsten Bormann wrote:
> > This is all great, but it is informative text except for a few sprinkled
> interoperability keywords “for the implementer” (when, apparently, it
> already has been decided to use this mechanism).
> >
> > The point, however, is that this specification has a limited area of
> applicability.
> > Outsourcing security decisions about this to an unwitting user is never
> the right approach.
> > The assumption that a user will intuitively understand the consequences
> of disclosure is a tall order.
> > (“Intuitive” is code for “familiar”, and every second five people are
> born that are not familiar with the consequences.)
> >
> > Beyond the nice discussion, usage of the mechanism needs to be governed
> by a strong, fully actionable applicability statement.
> >
> > Grüße, Carsten
> >
> > _______________________________________________
> > OAuth mailing list -- oauth@ietf.org
> > To unsubscribe send an email to oauth-leave@ietf.org
>
> _______________________________________________
> OAuth mailing list -- oauth@ietf.org
> To unsubscribe send an email to oauth-leave@ietf.org
>