IETF Logo Mail Archive

[OAUTH-WG] Re: SD-JWT and Unlinkability

Daniel Fett <mail@danielfett.de> Sat, 21 September 2024 14:29 UTC

Return-Path: <mail@danielfett.de>
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 D972CC15198C for <oauth@ietfa.amsl.com>; Sat, 21 Sep 2024 07:29:13 -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, HTML_MESSAGE=0.001, 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_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=danielfett.de
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 e2x_P8__lRsO for <oauth@ietfa.amsl.com>; Sat, 21 Sep 2024 07:29:09 -0700 (PDT)
Received: from mout-p-201.mailbox.org (mout-p-201.mailbox.org [80.241.56.171]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E3697C14F6FE for <oauth@ietf.org>; Sat, 21 Sep 2024 07:29:08 -0700 (PDT)
Received: from smtp102.mailbox.org (smtp102.mailbox.org [10.196.197.102]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-201.mailbox.org (Postfix) with ESMTPS id 4X9s816Wvrz9sh8; Sat, 21 Sep 2024 16:29:05 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=danielfett.de; s=MBO0001; t=1726928945; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=5Gg4oud1621nAyKZqK8ixjzS8H93HYzFm66hz2bsujQ=; b=oQhsiiiCamp7Uzdx/BnxcwgIJLh3GghS7AZpW9Fi2nkZR7R13aVFfk//R+H2AeBYbYZ9WX wF+iCCh9f2uZDr1BQxp8cCaOFWL+qjveyn+/TwgWU/9MCA3aybwC+FG2o/AGdx2mF3cOvH wwbx5sZM6VO0lHP180soLDVSLGqJ76wn9RuR4yVL04yin1eXywyH7rDkhFfH4+IudkgEOz Mv631mPCGpLun5OudIrCfrtoL0qdsIRpe0p1OrkFT48Hzo4HE5hHZ5BwQrvCGkdtdT3qAI ref47TatNkXArDLKRyVDHkQk9266yVRHyhsutp+k8Ly/N7S7KfNhW3Edtd9i3w==
Content-Type: multipart/alternative; boundary="------------ieb77EkjyZ4Cvp96jtiOxaZS"
Message-ID: <51d9e2b2-e766-4eea-8b31-a0ae5b2cfae4@danielfett.de>
Date: Sat, 21 Sep 2024 16:29:04 +0200
MIME-Version: 1.0
Content-Language: en-US
To: Dick.Hardt@gmail.com, oauth@ietf.org
References: <CAD9ie-s_gFmkCC8uKXQXC0W1u_zcaktvvNV6wEC4RtJQMarnng@mail.gmail.com>
From: Daniel Fett <mail@danielfett.de>
Autocrypt: addr=mail@danielfett.de; keydata= xjMEZVtP1hYJKwYBBAHaRw8BAQdAnfQRnVGKVUpdbc4qBhwIfryncOMAa1XjIFTAysHFgmXN IERhbmllbCBGZXR0IDxtYWlsQGRhbmllbGZldHQuZGU+wo8EExYIADcWIQTZQBZqxnGfR0Z5 iv7gQ6HKpmkhyAUCZVtP1gUJBaOagAIbAwQLCQgHBRUICQoLBRYCAwEAAAoJEOBDocqmaSHI NzcA/iNXFgwxZqvdaCDTRNib4iq82zFwXl3KwKYgL06xityzAQDIe7hIw6KnGaztTZsRXSvi +9srzbMJdDqVtC1n4A+YCs44BGVbT9cSCisGAQQBl1UBBQEBB0AwPb4iR2rn5k5DT4vAbYNK Oe4CMgQnwWexMYZFlAL0MwMBCAfCfgQYFggAJhYhBNlAFmrGcZ9HRnmK/uBDocqmaSHIBQJl W0/XBQkFo5qAAhsMAAoJEOBDocqmaSHI0Z8A/jd8Id2bvz6/D71d6HPvXZ+2z2BXzOd7MemE 9hHN+y6kAP44pe/GY97tvIZQa8aSinFJzDfbIVph6cUDlnPiwLjJDg==
In-Reply-To: <CAD9ie-s_gFmkCC8uKXQXC0W1u_zcaktvvNV6wEC4RtJQMarnng@mail.gmail.com>
Message-ID-Hash: DMCSAU23NZGMP3IYHY2ZJHZS3W76ODX6
X-Message-ID-Hash: DMCSAU23NZGMP3IYHY2ZJHZS3W76ODX6
X-MailFrom: mail@danielfett.de
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: kristina@sfc.keio.ac.jp
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [OAUTH-WG] Re: SD-JWT and Unlinkability
List-Id: OAUTH WG <oauth.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/oauth/AMnnMtJ0OVoSu3KjV2396JBlgiA>
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>

Hi Dick,

Batch credential (not claims) issuing has become the default approach to 
circumvent the inherent limitations of salted-hash-based credentials 
formats. This was neither invented by us, nor is it unreasonable to ask 
implementers to do it. Protocols such as OpenID4VCI support it.

-Daniel

Am 21.09.24 um 06:42 schrieb Dick Hardt:
> Is it really going to be practical to batch issue claims, and have the 
> holder randomly choose between them on presentation?
>
> As an implementer, what is the right number of claims to be in a batch?
>
> This section of the draft reads as a hack to add a new capability 
> (unlinkability) to a mechanism that did not have that as a design 
> objective.
>
> This is going to be like the "alg":"null" for SD-JWT. :-)
>
>

v2.38.3 | Report a Bug | By Email | System Status