[quicwg/base-drafts] Specify Version Negotiation and Crypto Failure (#1069)
Christian Huitema <notifications@github.com> Thu, 25 January 2018 01:55 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 9EE4C1270AB for <quic-issues@ietfa.amsl.com>; Wed, 24 Jan 2018 17:55:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.595
X-Spam-Level:
X-Spam-Status: No, score=-5.595 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, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, 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 Q7TVgXvbOqyN for <quic-issues@ietfa.amsl.com>; Wed, 24 Jan 2018 17:55:40 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1BE212D88C for <quic-issues@ietf.org>; Wed, 24 Jan 2018 17:55:40 -0800 (PST)
Date: Wed, 24 Jan 2018 17:55:40 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1516845340; bh=q2C6cN2DEMnaPOtU/tOrM2V4nDAKk4zA2dy1pTxKRM8=; h=From:Reply-To:To:Cc:Subject:List-ID:List-Archive:List-Post: List-Unsubscribe:From; b=eK5NjMI950m/QUYhmEnsz/4VeYU2vsQGyZOTVCu6eiKz6HMqDD42jkMZDDk0m1n3d 4BDJpl9A0dun7eLDArtdoxCB88rOUO4pOd+EeObo9oJ8Jik2dYsHur0ccUKB/I1a5q yJsaMnY710N0z/KtHrdiVFz5qZor80OuyAvWW074=
From: Christian Huitema <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abd86db29ae15ff4c699c00cf858e42d1e588797f692cf000000011680fb1b92a169ce115ec7f1@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1069@github.com>
Subject: [quicwg/base-drafts] Specify Version Negotiation and Crypto Failure (#1069)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a69391bf3ca0_2f852aeb50fe6ecc211413"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: huitema
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/UmyQe5KWciU8LRhp5KNPcZyz1z0>
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: Thu, 25 Jan 2018 01:55:42 -0000
During the recent interop tests, we have seen a number of version negotiation failures, which goes like that:
1) Client sends packet with a test version number, e.g., 1a1a1a1a. Content of packet is encrypted with
some version dependent "cleartext key" -- note the same a specified in draft-08.
2) Server receives packet, and fails to decrypt the content.
3) Server thus ignores the packet. No version negotiation.
The TLS spec seems unambiguous:
~~~
The salt value is a 20 octet sequence shown in the figure in hexadecimal notation. Future versions of QUIC SHOULD generate a new salt value, thus ensuring that the keys are different for each version of QUIC. This prevents a middlebox that only recognizes one version of QUIC from seeing or modifying the contents of handshake packets from future versions.
~~~
Yet, several implementations missed that. Is the spec clear enough?
--
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/1069
- [quicwg/base-drafts] Specify Version Negotiation … Christian Huitema
- Re: [quicwg/base-drafts] Specify Version Negotiat… Mike Bishop
- Re: [quicwg/base-drafts] Specify Version Negotiat… Christian Huitema
- Re: [quicwg/base-drafts] Specify Version Negotiat… Mike Bishop
- Re: [quicwg/base-drafts] Specify Version Negotiat… Martin Thomson
- Re: [quicwg/base-drafts] Specify Version Negotiat… Christian Huitema
- Re: [quicwg/base-drafts] Specify Version Negotiat… Martin Thomson