IETF Logo Mail Archive

Re: [quicwg/base-drafts] Add retry integrity tag (#3120)

MikkelFJ <notifications@github.com> Thu, 31 October 2019 08:52 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 71607120883 for <quic-issues@ietfa.amsl.com>; Thu, 31 Oct 2019 01:52:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.382
X-Spam-Level:
X-Spam-Status: No, score=-1.382 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_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=no 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 QjkmGYh--aNW for <quic-issues@ietfa.amsl.com>; Thu, 31 Oct 2019 01:52:36 -0700 (PDT)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9E1412086A for <quic-issues@ietf.org>; Thu, 31 Oct 2019 01:52:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=SZnzRbv8QQf9nr6aKRbSfvWorh2pzzdYIxswPgbSKY4=; b= QHXUXYzjOHKvXw/a//TdBUlFLkNqPTyskv4hWLGqej4exGwcNEyz+KjcQhZwe3nn mnP6JPr6WCOsHn69MwMUB+2NBxtX4zY0t7/B/fp73mz+2mMTVO3KJiwdiTwAbbCr yeFUlexY3OQK9ILynXQIEvK2efScs93Ov1Z5VbzmESA=
Received: by filter1439p1las1.sendgrid.net with SMTP id filter1439p1las1-15147-5DBAA0D2-15 2019-10-31 08:52:34.670619897 +0000 UTC m=+225014.343830264
Received: from github-lowworker-cef7735.cp1-iad.github.net (unknown [140.82.115.12]) by ismtpd0057p1iad1.sendgrid.net (SG) with ESMTP id EA_JXLzYTi6Quwb0aKxGaA for <quic-issues@ietf.org>; Thu, 31 Oct 2019 08:52:34.542 +0000 (UTC)
Received: from github.com (localhost [127.0.0.1]) by github-lowworker-cef7735.cp1-iad.github.net (Postfix) with ESMTP id 75C241E06D1 for <quic-issues@ietf.org>; Thu, 31 Oct 2019 01:52:34 -0700 (PDT)
Date: Thu, 31 Oct 2019 08:52:34 +0000
From: MikkelFJ <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK72NMEMHMQEUZT63Z53Y7JVFEVBNHHB4UZE54@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/3120/c548270968@github.com>
In-Reply-To: <quicwg/base-drafts/pull/3120@github.com>
References: <quicwg/base-drafts/pull/3120@github.com>
Subject: Re: [quicwg/base-drafts] Add retry integrity tag (#3120)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5dbaa0d274046_31c13fd1cbccd96885740"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mikkelfj
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak32Vcpt3lOzTUsZAeVRSzjPVUE6BNdGJzHxag ALL95k+n74z2pKry1E93qak+0pMg9YymoM8zJ85hM7YHM8JniAy07OSVM1agnKHjjhiEPxVFNdMJGC 8RbZHPoQuWMdYKLy9rHNMJ75OfL6yDctY9tYz8TocKo0yWbpvw2lKejxJIdpn30Plu5apA/4sgjFG/ o=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/CbxxsdXT_NJ5tyFG7BcMbjIg6dA>
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, 31 Oct 2019 08:52:37 -0000

XOR'ing with zero keys provides no confidentiality and just adds overhead. It is fine to use AES-GCM to tap into the GHASH logic by adding only authenticated additional data. But requiring a large static buffer of zero encrypted data is just overhead. For servers it harms expensive L1 cache and for embedded devices it would require encryption as usual.

As I said before GHASH is not the ideal hash for broader use, but given what we have it makes sense for authenticated additional data.

-- 
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/3120#issuecomment-548270968

v2.23.0 | Report a Bug | By Email