IETF Logo Mail Archive

Re: [quicwg/base-drafts] Don't allow use of AEAD_AES_128_CCM_8 (#2029)

Kazuho Oku <notifications@github.com> Thu, 22 November 2018 00: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 3F557130E6D for <quic-issues@ietfa.amsl.com>; Wed, 21 Nov 2018 16:55:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.46
X-Spam-Level:
X-Spam-Status: No, score=-9.46 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.46, 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] 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 1CZGwe_BvS6T for <quic-issues@ietfa.amsl.com>; Wed, 21 Nov 2018 16:55:35 -0800 (PST)
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 284AF130E52 for <quic-issues@ietf.org>; Wed, 21 Nov 2018 16:55:35 -0800 (PST)
Date: Wed, 21 Nov 2018 16:55:34 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1542848134; bh=E0YcF8u1GppW/n3tf/1H39isToQK+baPghfDa4bE6gY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=IlbMl0JzKCJCEssYrXgFkqdpnVylMNNSOrPWRaPz/R5SIS3ZwF6GRmaRJWulLr9fQ KLBxS2YeakizdZveHdt0rue8+vmRKxZ/BB4wetjXm3ZfJXGiBKE5z9ui5Ji2FYzx8e za52J96U6XAQ04hy8QyYVSggube/LwipwNKTdb4k=
From: Kazuho Oku <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab705c1a0291aa7d7c320ebd75492a148781781d4592cf00000001180dc08692a169ce16d3575c@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/2029/c440871757@github.com>
In-Reply-To: <quicwg/base-drafts/pull/2029@github.com>
References: <quicwg/base-drafts/pull/2029@github.com>
Subject: Re: [quicwg/base-drafts] Don't allow use of AEAD_AES_128_CCM_8 (#2029)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5bf5fe8624cdd_243a3fee036d45bc718b1"; 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/fYvO58MYzuwhN-9VvOCCbJFUi1k>
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, 22 Nov 2018 00:55:37 -0000

@mikkelfj I do not think we have an agreement on how we support AES128-CCM8.

One option is to require `len(pn) + len(payload)` to be 20 for the cipher-suite. The downside is that you would be required to pad a certain amount of bytes when the message is small.

The other option in to require `len(pn) + len(payload)` to be less than that, however we would be required to state that the connection cannot send more than 2<sup>32</sup> packets to avoid birthday attack on header protection (note: header protection key is not updated by Key Update).

I think it would be wise to leave the discussion to the people who are really interested in having AES128-CCM, rather than debating among us who are not really interested in supporting the ciphersuite.

-- 
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/2029#issuecomment-440871757

v2.23.0 | Report a Bug | By Email