Re: [quicwg/base-drafts] RETIRE_KEYS proposal (#2492)

Kazuho Oku <notifications@github.com> Thu, 07 March 2019 21:12 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 9873212DF72 for <quic-issues@ietfa.amsl.com>; Thu, 7 Mar 2019 13:12:57 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8
X-Spam-Level:
X-Spam-Status: No, score=-8 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_32=0.001, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-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 aH4OxtSa2x0m for <quic-issues@ietfa.amsl.com>; Thu, 7 Mar 2019 13:12:56 -0800 (PST)
Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2DAC12D4EB for <quic-issues@ietf.org>; Thu, 7 Mar 2019 13:12:55 -0800 (PST)
Date: Thu, 07 Mar 2019 13:12:54 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1551993174; bh=stNFI3ZrnLSt84rJk75j1fDZ7ZYkEDhysoy1YskLJjE=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=1x9K+fiDprxANUzUD+vcCHROkaID8j89m4Vuuk+4tOsPP9PDmTYElKjbZqQsesAGO wdu1NTEshbNv50If927s8m0WMolfkcaUz8FtX8zgVH47pZCPs86dELYtvb8oziRPdt XjSSX5vJzdJ/htSAuPXPmBAlNWLNzhL9zvVxHLKU=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab9831cbe7708dbcf1d0054f018b9a53b63cce83de92cf0000000118994b5692a169ce18c9ea95@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2492/c470696256@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2492@github.com>
References: <quicwg/base-drafts/pull/2492@github.com>
Subject: Re: [quicwg/base-drafts] RETIRE_KEYS proposal (#2492)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c818956cdb95_54813f9dbaed45bc474d5"; 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/g3OXjOk3OGuRfVL3qJIhE2ru87Y>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 07 Mar 2019 21:12:57 -0000

> Wouldn't it be safer to still discard initial/handshake keys after some time?

I can see that argument for Initial keys. At the moment, we require endpoints to drop the Initial keys at the earliest moments. There's a trade-off between relying on an explicit signal (that might get missed) vs. having a uniform way of retiring keys.

OTOH, I think we should solely rely on an explicit signal for dropping handshake keys. There is no risk in keeping the key forever (because only the peer can send Handshake packets that successfully validates), and because there is a tail.

-- 
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/pull/2492#issuecomment-470696256