[SPICE] Re: is bstr encoding of the disclosure array really necessary?
Christopher Allen <christophera@lifewithalacrity.com> Fri, 28 February 2025 18:15 UTC
Return-Path: <christophera@lifewithalacrity.com>
X-Original-To: spice@mail2.ietf.org
Delivered-To: spice@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id 3AB213F0B2C for <spice@mail2.ietf.org>; Fri, 28 Feb 2025 10:15:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_SBL_A=0.1] autolearn=no autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=lifewithalacrity-com.20230601.gappssmtp.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H-u-2--SUTgk for <spice@mail2.ietf.org>; Fri, 28 Feb 2025 10:15:36 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 mail2.ietf.org (Postfix) with ESMTPS id 384803F0B16 for <spice@ietf.org>; Fri, 28 Feb 2025 10:15:36 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id 4fb4d7f45d1cf-5e4b410e48bso3610041a12.0 for <spice@ietf.org>; Fri, 28 Feb 2025 10:15:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lifewithalacrity-com.20230601.gappssmtp.com; s=20230601; t=1740766535; x=1741371335; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=QAGNM35Gbga6VugXPK8vINUtUjTe4BTZbV7aGG0A0Q0=; b=e4LVal61YSh9pQ8q2GTROHenEHidKl4GyhsWy0nhyTZz82ongFf5bDrD/O6gVFQ7N6 GX0EMzEdFuzprjLYb3LfC76/ylgh2TSP1Wln3Q42M3SjQDMV1AdDQ/IGusiKxFngfQ4Y gG3mwPmz+Ym7rsiucCF7bkhcg5fZJv7U2UWlsOFFG6K0oUCrw80edJmNt3GiPOC275IP f/awtTltizakWeVeUR3unm26FhXPKsUxcsc2TMpYbFg/n5vUDp5sPwpBuE9WDjIBEZff CMynUpJpnPHe6+x4LI0FjmLhVBnR90SDguc2V17pzbV53zOtcvdDNeA6ms3rHAUTEDus 7axg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1740766535; x=1741371335; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=QAGNM35Gbga6VugXPK8vINUtUjTe4BTZbV7aGG0A0Q0=; b=wSO9+E3IYmaiBc8Pl9laiqlGJll/LqcN6Nj3yDp5Sd9EgMgHsFfyqqZMf7tSkuEnWM HUWQ3+y0z2RopsWiwnpnuMPiA/LKvmZaVLjrfuZnJEwwjszYFvCpXWDvB6iQb6wP5pBS 57bmuCrk9kO2R34W2Ub8vl4RrvWtp8kqfy7coWsd3kmHmJli8d5vjPzMStWOVTNqF//y P7xzk7pkVKer6PuIF8UnnGsvNo9WrG2HTVxvlqCKR8g4hvAEIocT8kfJN5VovJXIKzF/ u8ZlIAGQM9dAQFh6PzjBnK2HHCu/Bt8sUc7oL8fSe+m3e6xfLe5kRmIa6Onc7DDo8ME+ 9S0A==
X-Forwarded-Encrypted: i=1; AJvYcCVZX6WhXahJTxiA3dxugiNHxoo5McVl1Xy2EMMVMmt0H1VDjCzq1ct4A1GdQ1CE6QwVWyS/DQ==@ietf.org
X-Gm-Message-State: AOJu0YxbtD/BleSACOWt4OhE0+bjs+thnmJaXy4wrmj6qa4K32tOW1fi xTUF5MF3ixVJmXcDlI4mStqNAm8l81/dajBeF+RGqpi5k0KXGg7UncULLdULdOrwNMaFcaCy4R0 2pXWMdsD4fdDxZSjQcIU0WgOAjG5naXMGGRLd
X-Gm-Gg: ASbGncuuDmHgSjBtinOTsr3+F/PkBOnXyGCKE+RMao7xQppXepV3hBCAYl0D68PYyym av8862+V37ZCEt7FImDQCGi7fw56SvfTzBeICkr3TDkoCCSZCnZBqYsHW1GktVR40qiTyBntDKI iyuYZTm3wzi2bJyawkX9C67iXFAcbvwr+3pj16LHJUcA==
X-Google-Smtp-Source: AGHT+IHeZ92TUOngXNv6PqhE8hkq1jcoEcDP/Pt/GHBlFeyiMxjUIngYwULcveNjPpU9eEEPA01zEY0XAbTSpzOFCm8=
X-Received: by 2002:a50:cc0c:0:b0:5e4:d75a:573e with SMTP id 4fb4d7f45d1cf-5e4d75a57fcmr2998859a12.32.1740766535035; Fri, 28 Feb 2025 10:15:35 -0800 (PST)
MIME-Version: 1.0
References: <CAKoiRubgcicR729Mj6SCFUrcB9K8hrZtTNgZuee1Yf5vocRn-Q@mail.gmail.com> <97CF3E02-2491-4777-B4E1-AD34C6E45C5F@tzi.org> <CAN8C-_L_d2ihi1fMiVuuyLzpXnsSJM+w7XpA1nkYSJz5k2bDZQ@mail.gmail.com> <DF87868F-1BCB-4FE9-B844-F5CE535A1923@tzi.org> <CAKoiRuYugUEZMJ0f=rTdDwgrQNG5aryRubvc=7EMe9j-hUbk_g@mail.gmail.com> <4687e073-c963-4583-ae1b-b77826e01487@gmail.com> <CAKoiRubtELDKLMnfdY48JZOwkHG-KhP80phkkfssAozeEW9ojA@mail.gmail.com> <56aab657-8362-4196-b8e0-7f795fd32de9@gmail.com>
In-Reply-To: <56aab657-8362-4196-b8e0-7f795fd32de9@gmail.com>
From: Christopher Allen <christophera@lifewithalacrity.com>
Date: Fri, 28 Feb 2025 10:15:23 -0800
X-Gm-Features: AQ5f1JrGPgt6YSBpB4ybteQFK5-G8-tuQH0ZGNuBj8RwjV1XMvvn7BZ2n9arhGM
Message-ID: <CAAse2dHeLUoiv+ggGZ+m0+vsVgDzKt1zx4hFBWP4FdBk-0=ZkQ@mail.gmail.com>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000f5507c062f37cafb"
Message-ID-Hash: XSCCHRZTBXUB6DLQOJWROPXHAMJIA5O3
X-Message-ID-Hash: XSCCHRZTBXUB6DLQOJWROPXHAMJIA5O3
X-MailFrom: christophera@lifewithalacrity.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Rohan Mahy <rohan.mahy@gmail.com>, spice@ietf.org, Orie Steele <orie@transmute.industries>, Rohan Mahy <rohan.ietf@gmail.com>, Wolf McNally <wolf@wolfmcnally.com>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [SPICE] Re: is bstr encoding of the disclosure array really necessary?
List-Id: Secure Patterns for Internet CrEdentials <spice.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/spice/lvP3x9S4H3xKCrkAzUY4_f3PM-E>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spice>
List-Help: <mailto:spice-request@ietf.org?subject=help>
List-Owner: <mailto:spice-owner@ietf.org>
List-Post: <mailto:spice@ietf.org>
List-Subscribe: <mailto:spice-join@ietf.org>
List-Unsubscribe: <mailto:spice-leave@ietf.org>
On Fri, Feb 28, 2025 at 9:50 AM Anders Rundgren < anders.rundgren.net@gmail.com> wrote: > > Do you have any objection to keping the bstr encoding of disclosures in > place in SD-CWT? > > The sole reason for disturbing the peace was to show that there is a > growing crowd of COSE "dissidents". > > Here is an example of a security and privacy solution that takes the > "anti-bstr" issue to a new level: > > https://cyberphone.github.io/doc/defensive-publications/partial-encryption-full-signature.pdf > I would very much like to see that in COSE! > At Blockchain Commons and within our community of privacy-centric developers, we also count ourselves among the COSE "dissidents." We grew increasingly frustrated with the "inclusion of payload" design pattern that COSE inherited from JWT. This approach often proves burdensome, particularly in cases where: * Complex parsing and interpretation are necessary, making it impractical to retain the full un-redacted original payload. * Data minimization is required—whether by avoiding unnecessary storage, elision, selective redaction, or encryption. Remember RFC-6973 - "Privacy Considerations for Internet Protocols": > Data minimization mitigates the following threats: surveillance, stored data compromise, correlation, identification, secondary use, and disclosure. We believe the ability to reconstruct stored data while verifying selected portions of the data should be a fundamental design consideration. The dCBOR I-D ( https://www.ietf.org/archive/id/draft-mcnally-deterministic-cbor-08.html) and Gordian Envelope I-D ( https://www.ietf.org/archive/id/draft-mcnally-envelope-08.html) and their working code in multiple languages, directly address these concerns, offering a practical solution already in production today. Would love to see COSE embrace this direction. -- Christopher Allen
- [SPICE] is bstr encoding of the disclosure array … Rohan Mahy
- [SPICE] Re: is bstr encoding of the disclosure ar… Carsten Bormann
- [SPICE] Re: is bstr encoding of the disclosure ar… Orie Steele
- [SPICE] Re: is bstr encoding of the disclosure ar… Carsten Bormann
- [SPICE] Re: is bstr encoding of the disclosure ar… Rohan Mahy
- [SPICE] Re: is bstr encoding of the disclosure ar… Orie Steele
- [SPICE] Re: is bstr encoding of the disclosure ar… Michael Prorock
- [SPICE] Re: is bstr encoding of the disclosure ar… Anders Rundgren
- [SPICE] Re: is bstr encoding of the disclosure ar… Rohan Mahy
- [SPICE] Re: is bstr encoding of the disclosure ar… Anders Rundgren
- [SPICE] Re: is bstr encoding of the disclosure ar… Christopher Allen
- [SPICE] Re: is bstr encoding of the disclosure ar… Anders Rundgren