Re: [Privacy-pass] context unlinkability

Christopher Wood <caw@heapingbits.net> Wed, 10 May 2023 18:39 UTC

Return-Path: <caw@heapingbits.net>
X-Original-To: privacy-pass@ietfa.amsl.com
Delivered-To: privacy-pass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9309C14CE2F for <privacy-pass@ietfa.amsl.com>; Wed, 10 May 2023 11:39:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.795
X-Spam-Level:
X-Spam-Status: No, score=-2.795 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, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, 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=heapingbits.net header.b="WRvdxjKm"; dkim=pass (2048-bit key) header.d=messagingengine.com header.b="FJlMyytT"
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 oVNN2aIpUWFK for <privacy-pass@ietfa.amsl.com>; Wed, 10 May 2023 11:39:42 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DB5F8C1DF96D for <privacy-pass@ietf.org>; Wed, 10 May 2023 11:38:02 -0700 (PDT)
Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.nyi.internal (Postfix) with ESMTP id A6EA25C0558; Wed, 10 May 2023 14:38:01 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute5.internal (MEProxy); Wed, 10 May 2023 14:38:01 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=heapingbits.net; h=cc:cc:content-transfer-encoding:content-type:content-type :date:date:from:from:in-reply-to:in-reply-to:message-id :mime-version:references:reply-to:sender:subject:subject:to:to; s=fm3; t=1683743881; x=1683830281; bh=7KXaky8Ubrh/gf4K0rxRljvXO d7CLr7m74+pYlC9Tjw=; b=WRvdxjKmZ8cqVcT5T3HCe8kFoYIb/icuzJ0UOLkB2 uAXc/PkcsTaB7nxpc2Qhypq1sddmf/FdHT285N6j9fT9B0yksDULa/iAFtAto6eq 4G1x17J0jsvTotxsqkKECpWL1sA75MyJsDtanxxfC/2uFlIWClXNOTDHJQuOYTZG OABD45MuywQVFnubKY3yVKDB0wceYsNDr2cyKiOaGt+jvpnNakJh7bl8fU0AsCHy g3ndt+QK6Rzd+IOH7NrqG9kh7Y4c2r0MG66sdjDXnLNZDCv8FlgT2u7Y9cSkT81a JNmDOzFVos6sKHxI+5JQNNlLSCCD5alJV71VD6w2TNKUQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1683743881; x=1683830281; bh=7KXaky8Ubrh/gf4K0rxRljvXOd7CLr7m74+ pYlC9Tjw=; b=FJlMyytTt+68bpgela8y7ChUmzVagZ3ZWqHjAYS0vZqU2YI9C3A pOpJeGTjjcwDw28cFUUY/l22mFyGJr+eAgqHmNdDFYLtvAnTKjct83cR33btiB1l Cu0RvKJjZQWbWNwovx3KNTtj/TD+j7PwOWzO0ArmRKoYEH68xPlycCVxek0cSzO0 uRxDdyU1wYmF5nfMNTyXBcy2IRT81A6ugGbMP5f8H63IVR1kn5CiI1Gt8hxQSzo1 xtPCl8dsVVUB5OTP4e4eafc4yFcREfPh9z8+mv5IhjJ1Id8sSc2FWdn0jGQgKzgt EOKgqqhnFXxY4CBexzXW5DEMyQlF146dzQw==
X-ME-Sender: <xms:ieRbZCjqBBITyyKWrPH22WR51DaoawjKeJB5BhiQKBHchOrheoYhIw> <xme:ieRbZDC_Tesvd1yb9MKCh2ZQ3WWa5jhWTXLZm7VDpataYnl28GicXSuE-tfwXtTkb kQ5OG2D9xFdk53ZlQA>
X-ME-Received: <xmr:ieRbZKHff-H0kwb1cGNHdkm8sWdSzy0OGXMLjzBwR7GqI5q5p4mSn9ZWllyCRxWiJTlB>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrfeegiedguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggguffhjgffvefgkfhfvffose htqhhmtdhhtdejnecuhfhrohhmpeevhhhrihhsthhophhhvghrucghohhougcuoegtrgif sehhvggrphhinhhgsghithhsrdhnvghtqeenucggtffrrghtthgvrhhnpeffudetlefhhe dtleeuteeuueehkeefffdtgeefvdetveehjefgheevfeetgedvvdenucffohhmrghinhep ihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilh hfrhhomheptggrfieshhgvrghpihhnghgsihhtshdrnhgvth
X-ME-Proxy: <xmx:ieRbZLRJrPH1xkpid60gwdfefL726sAIMzYuRjM4cYfqTlswl_XrXA> <xmx:ieRbZPzdxvb8F2aKeXoCs5EsZQZBr0HEkDlNcbHKbbMKwyi-eEPeyQ> <xmx:ieRbZJ6IU2tU5jV8z1r9D9nrvR3yHJvyihM-Z0mCWKjNhjDpTYrACQ> <xmx:ieRbZNbv8vaP4ogOOlq28VjZycEWbHlLvmut8RTkmyy1DfulvV_rxg>
Feedback-ID: i2f494406:Fastmail
Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 10 May 2023 14:38:00 -0400 (EDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.1\))
From: Christopher Wood <caw@heapingbits.net>
In-Reply-To: <CACTKa0D75u=95Vpov4aK4BGXeisL08KF-Dddi5HBXE69erbOoA@mail.gmail.com>
Date: Wed, 10 May 2023 11:37:59 -0700
Cc: privacy-pass@ietf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <F39963CC-1AE1-4BA2-905D-ECAA9B66F65E@heapingbits.net>
References: <CACTKa0D75u=95Vpov4aK4BGXeisL08KF-Dddi5HBXE69erbOoA@mail.gmail.com>
To: Nikita Borisov <nikita.borisov=40cloudflare.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3696.120.41.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/privacy-pass/PStduRY35npkr3G0KguvLDxb0wA>
Subject: Re: [Privacy-pass] context unlinkability
X-BeenThere: privacy-pass@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Privacy Pass Protocol <privacy-pass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/privacy-pass>, <mailto:privacy-pass-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/privacy-pass/>
List-Post: <mailto:privacy-pass@ietf.org>
List-Help: <mailto:privacy-pass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/privacy-pass>, <mailto:privacy-pass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 May 2023 18:39:46 -0000

Thanks, Nikita! This is a nice, succinct change that I think we should include. I merged the PR into the architecture document.

Chairs, we can rev the document again if needed. Please let us know how you’d like to deal with this.

Best,
Chris

> On May 9, 2023, at 9:47 AM, Nikita Borisov <nikita.borisov=40cloudflare.com@dmarc.ietf.org> wrote:
> 
> The current architecture document defines three types of unlinkability (Origin-Client, Attester-Origin, and Issuer-Client). These maintain client privacy within any single context. However, I think an important property of privacy pass protocols is that the issuance (and attestation!) contexts should be unlinkable to the redemption context. This is actually mentioned in the Overview under point 5, but it isn't listed among privacy goals. I added a pull request (361) to add this property to the architecture document.
> 
> I think this is important because without it, an issuance protocol that adds, e.g., a serial number to each issued token which MUST be shown at redemption time would still satisfy the three original unlinkability properties. 
> 
> Thanks,
> - Nikita
> -- 
> Privacy-pass mailing list
> Privacy-pass@ietf.org
> https://www.ietf.org/mailman/listinfo/privacy-pass