[OAUTH-WG] Re: SD-JWT linkability

Tom Jones <thomasclinganjones@gmail.com> Mon, 16 December 2024 18:50 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 E18B6C14CF1E for <oauth@ietfa.amsl.com>; Mon, 16 Dec 2024 10:50:11 -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 auU8qWGwDRDf for <oauth@ietfa.amsl.com>; Mon, 16 Dec 2024 10:50:09 -0800 (PST)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::231]) (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 B66DAC14F71C for <oauth@ietf.org>; Mon, 16 Dec 2024 10:50:09 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id 38308e7fff4ca-30229d5b1caso44867291fa.2 for <oauth@ietf.org>; Mon, 16 Dec 2024 10:50:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1734375007; x=1734979807; 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=AiIdKQBBDVmDtoSyHTRbulEb9H0H1sE2OD8FdLgmmKw=; b=BN9px5FRrHkk/7gr/GXvvl/ErgtyrFRMLMuDhXHGME0L3iotv4SX3CQXaQ+VWff8XX li3z6lc8m5jHhzSd2J5wJEvqtMwv2QtcE2fhrnJVdWHP3/g1Z1HF7MrKV3APpmG5vAmB p/pFKb5bECsPr4T2NaLWWN9b3QevUaq5v1VuKAoDeA+17eR62FDgYXdg0peE+NhOMrfR /LgEGBYU5W3Grj6BCZKqw5uV3E1U6zBmvU32nwPuVncIDkgV0pfBiw+AAq1BpCjS+8SK HQ2el2NVJ6naPlNDr0jYVTL9xOvOx/LpYIozOMqLlLrkGavxK2BCZBU/hTJ0ja9p7Wrx TE4g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1734375007; x=1734979807; 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=AiIdKQBBDVmDtoSyHTRbulEb9H0H1sE2OD8FdLgmmKw=; b=RpUCyGBrDuIVrbmazeUAbQJSKuN2CWc68M8Paqe5yilRnauU+gxn4RZ3SjiTt8Yc4B prZ8ENuCDy/IOy/r+H1DZJkn/KK+0V+a3ilMotDZMCbMs9a3GsKj+p+Jq6hdWxeMKuRy GnXwjNVgYvscbcNNQqRXSxacHAyQYStmPSiyQzAGO1p4pZ8S5M8Jz3JAdzX9qt7fSsLr MjLATdg+pWz+WaxzVl4WOmobsURdAasWVs/OwkrK3dQnY8Vnx5GXAtYOr9HEthbMGj4F 7gH9XnEEFrZM610pehk98RqdOXZrNzQgYtAGNc7OCtIewiGyss3oVvvzOd9TCEshn4an PnFg==
X-Gm-Message-State: AOJu0YyQQQtOWIv5LKYWRdeUqMJaiCMUq2dCJZhXjO/utYXWSIG5Y/Bx Tykg1FeWthesd38QuAWbgt3GYdITljap7M90AvscgZynLTF+dpvebxAXFhkxsLVURYqwQZqJUdA 9JGsjrwBXMPSWhnpwkGj/EqWPnws=
X-Gm-Gg: ASbGncupzOr8sIYaQo8S0Ydi7TjL4rSPF3CSt03R1r3xoXjO0WL2+J/6XAjReBen7hT D1oreN63RtU1QpfxA3SMc4X1/DHO45hqAybPgH7JdeMD+U3sZrewUoyLGlYLdY6o43FDAisw=
X-Google-Smtp-Source: AGHT+IH7DgKjga5E5e203LoMDvLihXYRVevKALbrRLAaEy9BUDiOq2Sd4klbgB9lGAnuSs3uiUsE09aLDFv48viAmyI=
X-Received: by 2002:a2e:a99c:0:b0:300:38ff:f8ee with SMTP id 38308e7fff4ca-30254530c8dmr45264001fa.9.1734375007065; Mon, 16 Dec 2024 10:50:07 -0800 (PST)
MIME-Version: 1.0
References: <CACsn0ckGp4AocD1fQbMCs45P_Z5vjveggzDJw=-Vk5kxinM28Q@mail.gmail.com>
In-Reply-To: <CACsn0ckGp4AocD1fQbMCs45P_Z5vjveggzDJw=-Vk5kxinM28Q@mail.gmail.com>
From: Tom Jones <thomasclinganjones@gmail.com>
Date: Mon, 16 Dec 2024 10:49:55 -0800
Message-ID: <CAK2Cwb7OSHHh8DrO3FsBa7szJRpu+v-Zau4bonfPiXbVwNo5NA@mail.gmail.com>
To: Watson Ladd <watsonbladd@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000342352062967a6d4"
Message-ID-Hash: 4EM3M4WXW3BZZQ76CFLPIDMYFML7DGTR
X-Message-ID-Hash: 4EM3M4WXW3BZZQ76CFLPIDMYFML7DGTR
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: IETF oauth WG <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/HkB3i3h6Xo0rxyJTvkWo-byYdsU>
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>

The entire premise of SD-JWT in a VP transaction is basically fraudulent as
there is not sufficient information in the VP to allow the user to make an
informed consent decision. It gives the illusion of user control without
the ability to deliver on the promise. For this proposal to have any value
to the user it must be part of a transaction that tells the user agent
(wallet) who is asking for the data and what the purpose of the request is.
Absent that, this give the impression of user control of release of data
without the fact.

BTW - the idea of dealing with the UX of the transaction is admirable, but
there are no UX people involved in the discussion.

Peace ..tom jones


On Wed, Dec 11, 2024 at 5:01 PM Watson Ladd <watsonbladd@gmail.com> wrote:

> Dear all,
>
> I'd like to propose the following edit to resolve the concerns I have
> around endorsing dangerous applications of SD-JWT:
>
> Delete last two lines of
> https://github.com/oauth-wg/oauth-selective-disclosure-jwt/pull/451/files
> in 1338 and 1339
>
> Add new paragraph right before the end of the section.
>
> "When disclosures include information easily understood to be
> identifying, users intuitive view of what they are revealing largely
> matches the underlying technical reality. In cases where the
> information being disclosed is not identifying, SD-JWT
> MUST NOT be used as this confusion leads to users making the wrong
> choices. Applications cannot assume Verifiers behave properly (RFC
> 3514) and MUST analyze the consequences for such linkage with each
> credential that could be used."
>
> I think this agrees with many of the comments made about my initially
> stronger edit, while addressing the core danger.
>
> Also, it seems this section only really treats issuer/verifier despite
> promising more. Do we need to rework it?
>
> Sincerely,
> Watson Ladd
> --
> Astra mortemque praestare gradatim
>
> _______________________________________________
> OAuth mailing list -- oauth@ietf.org
> To unsubscribe send an email to oauth-leave@ietf.org
>