Re: [quicwg/base-drafts] Make EOED transmission optional in QUIC, please (#1518)

ekr <notifications@github.com> Sat, 01 September 2018 18:26 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 B6828130E32 for <quic-issues@ietfa.amsl.com>; Sat, 1 Sep 2018 11:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.009
X-Spam-Level:
X-Spam-Status: No, score=-8.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 EhcGuBRS3Qpc for <quic-issues@ietfa.amsl.com>; Sat, 1 Sep 2018 11:26:22 -0700 (PDT)
Received: from out-5.smtp.github.com (out-5.smtp.github.com [192.30.252.196]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 149041277CC for <quic-issues@ietf.org>; Sat, 1 Sep 2018 11:26:21 -0700 (PDT)
Date: Sat, 01 Sep 2018 11:26:21 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1535826381; bh=oorvfT7cAPlMeJpDH30IE10Vow5Odcot8VWgBmgi8tk=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=V/b1KpMHpdoe7xCwi8c4vTYQrcNyB0nt0R7mQDfkCMnhUSAyU9ayyVoItLVYtlvoY PCnyDfLD+RrxlFdI5clZuxZIV/xCtnHzCzC0gKPUec1O7CbCqlJSFudiH9txIq5iNl d3JCbo1cpFw4iAGyJlIoq7GBeycEiCEIEwr5b5qk=
From: ekr <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abfdd1a88542d09772998e2635839af9aac86df74492cf0000000117a29bcd92a169ce1427404b@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1518/417878401@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1518@github.com>
References: <quicwg/base-drafts/issues/1518@github.com>
Subject: Re: [quicwg/base-drafts] Make EOED transmission optional in QUIC, please (#1518)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5b8ad9cdbca6_57cc3fb5702d45b415241e"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ekr
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/CY1jaOOnRGn-uOENxmGA2uJLG2U>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.27
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: Sat, 01 Sep 2018 18:26:24 -0000

Just to follow up on this point, removing EOED does allow a weak extension attack against data in the 0-RTT epoch. Consider the case where the client (a) sends EOED  and then (b) is compromised. Under these conditions an attacker will be able to send data which will appear to the server to be in 0-RTT. As I say, this is quite a weak attack because (a) the client could just delete the 0-RTT keys and (b) the attacker would presumably be able to instead send 1-RTT data instead. But it is a change in the properties of the system.


-- 
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/1518#issuecomment-417878401