Re: [quicwg/base-drafts] Timing side-channel on key updates (#2792)
Nick Banks <notifications@github.com> Fri, 14 June 2019 14:18 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 EF45C120224 for <quic-issues@ietfa.amsl.com>; Fri, 14 Jun 2019 07:18:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.463
X-Spam-Level:
X-Spam-Status: No, score=-6.463 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 4L4DmhCyx1L5 for <quic-issues@ietfa.amsl.com>; Fri, 14 Jun 2019 07:18:32 -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 007F9120221 for <quic-issues@ietf.org>; Fri, 14 Jun 2019 07:18:31 -0700 (PDT)
Date: Fri, 14 Jun 2019 07:18:31 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1560521911; bh=rYUJVpgKo3GXp1nd9xIE2FR3T3LcQgZ2d87k3HzqSHo=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=ni6u15gyZbOhup9Qy51EvLkUPmX9awIugqGPkwTZf83/jSSeFWOn+8ZQOrW9v1WbP qakqNxqgu2rfygww4ix/jB0cAFCS9st1a1XrGUuJX2eA2cq1oE9U5UTariE7AsWXk8 BPgIYLJYRqCjDsM/PcgO3PdKdAwPACYgJjCh9qbo=
From: Nick Banks <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK3NQPFL27PHUAFUJEF3CDPTPEVBNHHBWL37RY@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2792/502126987@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2792@github.com>
References: <quicwg/base-drafts/issues/2792@github.com>
Subject: Re: [quicwg/base-drafts] Timing side-channel on key updates (#2792)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d03acb711196_613f3f87682cd95c3660f0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: nibanks
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/IljCz-H8TKENWL1KKyeiYtEIVNE>
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: Fri, 14 Jun 2019 14:18:34 -0000
Does anyone have any ideas what kind of actual attack could take advantage of this? The attacker can only cause you to install your keys early once per key phase change. Assuming you hardly every change key phase, what then? I agree it's a way the unauthenticated attacker can change your state, but I don't think it's a big enough problem we need to worry about fixing. -- 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/2792#issuecomment-502126987
- [quicwg/base-drafts] Timing side-channel on key u… Marten Seemann
- Re: [quicwg/base-drafts] Timing side-channel on k… Kazuho Oku
- Re: [quicwg/base-drafts] Timing side-channel on k… Marten Seemann
- Re: [quicwg/base-drafts] Timing side-channel on k… MikkelFJ
- Re: [quicwg/base-drafts] Timing side-channel on k… ianswett
- Re: [quicwg/base-drafts] Timing side-channel on k… Marten Seemann
- Re: [quicwg/base-drafts] Timing side-channel on k… ianswett
- Re: [quicwg/base-drafts] Timing side-channel on k… Nick Banks
- Re: [quicwg/base-drafts] Timing side-channel on k… Marten Seemann
- Re: [quicwg/base-drafts] Timing side-channel on k… Kazuho Oku
- Re: [quicwg/base-drafts] Timing side-channel on k… Mike Bishop
- Re: [quicwg/base-drafts] Timing side-channel on k… Kazuho Oku
- Re: [quicwg/base-drafts] Timing side-channel on k… ekr
- Re: [quicwg/base-drafts] Timing side-channel on k… Lars Eggert
- Re: [quicwg/base-drafts] Timing side-channel on k… Christopher Wood
- Re: [quicwg/base-drafts] Timing side-channel on k… Lars Eggert
- Re: [quicwg/base-drafts] Timing side-channel on k… Martin Thomson
- Re: [quicwg/base-drafts] Timing side-channel on k… Mark Nottingham
- Re: [quicwg/base-drafts] Timing side-channel on k… Mark Nottingham
- Re: [quicwg/base-drafts] Timing side-channel on k… Martin Thomson