IETF Logo Mail Archive

Re: [quicwg/base-drafts] per-CID PN space to avoid PN leak becoming a privacy issue? (#1317)

Kazuho Oku <notifications@github.com> Tue, 01 May 2018 01:06 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ECAA126C0F for <quic-issues@ietfa.amsl.com>; Mon, 30 Apr 2018 18:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.605
X-Spam-Level:
X-Spam-Status: No, score=-6.605 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ELNP165SCzg2 for <quic-issues@ietfa.amsl.com>; Mon, 30 Apr 2018 18:06:22 -0700 (PDT)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EFFBF120727 for <quic-issues@ietf.org>; Mon, 30 Apr 2018 18:06:21 -0700 (PDT)
Date: Mon, 30 Apr 2018 18:06:21 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1525136781; bh=MQPrLwsuXNZZu1pMeW3N2u/hTT8TWVlngDJeCPhWRSU=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=u5CXIV3CT2BkxjGuLCnj/+VejJ7Y2/yuRsnrUaeV6IyhkCet7c8bGDWiPHuhITA9v Za1yZGd9aDUMLhAPCk21rJiOH/yJb+YTFK/oJHof2EiLTvU/VGMEz/ZkysjxGrxFaG CWC3IMg7cuMdh1cuspETdOtUh3w3eF1+PR2yM73g=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab6d68390a971200204983f366ba7238c62eddcfc692cf0000000116ff7f8d92a169ce12df98aa@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1317/385573851@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1317@github.com>
References: <quicwg/base-drafts/issues/1317@github.com>
Subject: Re: [quicwg/base-drafts] per-CID PN space to avoid PN leak becoming a privacy issue? (#1317)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ae7bd8d223fa_52363fa51d6b0f88612fb"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: kazuho
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/muriAUohHWoBwEZldviz15Nmjp8>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 01:06:23 -0000

@huitema 
> This is certainly a plausible design, but can you explain how it prevents the key phase bit linkage issue?

It does not. Having separate PN per CID provides resistance to side channels attacks that try to recover an encrypted PN.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/1317#issuecomment-385573851

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