Re: [openpgp] Questions around AEAD packets

Derek Atkins <derek@ihtfp.com> Fri, 17 February 2017 16:19 UTC

Return-Path: <derek@ihtfp.com>
X-Original-To: openpgp@ietfa.amsl.com
Delivered-To: openpgp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 92D01127071 for <openpgp@ietfa.amsl.com>; Fri, 17 Feb 2017 08:19:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ihtfp.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 TCjlvCIOKWri for <openpgp@ietfa.amsl.com>; Fri, 17 Feb 2017 08:19:24 -0800 (PST)
Received: from mail2.ihtfp.org (mail2.ihtfp.org [IPv6:2001:470:e448:1::3a11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5680E129607 for <openpgp@ietf.org>; Fri, 17 Feb 2017 08:19:24 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by mail2.ihtfp.org (Postfix) with ESMTP id 65A0FE2044; Fri, 17 Feb 2017 11:19:23 -0500 (EST)
Received: from mail2.ihtfp.org ([127.0.0.1]) by localhost (mail2.ihtfp.org [127.0.0.1]) (amavisd-maia, port 10024) with ESMTP id 02481-02; Fri, 17 Feb 2017 11:19:22 -0500 (EST)
Received: from securerf.ihtfp.org (unknown [IPv6:2001:470:e448:2:ea2a:eaff:fe7d:235]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mocana.ihtfp.org", Issuer "IHTFP Consulting Certification Authority" (verified OK)) by mail2.ihtfp.org (Postfix) with ESMTPS id 32FE4E2043; Fri, 17 Feb 2017 11:19:22 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ihtfp.com; s=default; t=1487348362; bh=t/uCzgcuRSLB+z4aamMo0HAIGmnXgbNOG8ADPV27oK0=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=ss2mV2gimwU/szO/tSUWU9M1wAbnQRjcd1aP+bACfP2isB41XfI1LKX04ZJj256to wzxV6rzMx03lJl3+7b2WI9Xw6FBo0GuCPjwMB42pg6AmLdusMbysxX1GPxsZTwPHMS D7pGIDKVjedVT5HxlfhumeFwgHlb26UkIxFLQ8kA=
Received: (from warlord@localhost) by securerf.ihtfp.org (8.15.2/8.14.8/Submit) id v1HGJLqJ008521; Fri, 17 Feb 2017 11:19:21 -0500
From: Derek Atkins <derek@ihtfp.com>
To: openpgp@ietf.org
References: <87shnhxhah.fsf_-_@wheatstone.g10code.de>
Date: Fri, 17 Feb 2017 11:19:21 -0500
In-Reply-To: <87shnhxhah.fsf_-_@wheatstone.g10code.de> (Werner Koch's message of "Tue, 14 Feb 2017 10:17:42 +0100")
Message-ID: <sjmy3x44wom.fsf@securerf.ihtfp.org>
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: Maia Mailguard 1.0.2a
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/Wp6zos9Tq1pDRiOKHOMVSPwY9DQ>
Cc: Jon Callas <joncallas@icloud.com>, "brian m. carlson" <sandals@crustytoothpaste.net>
Subject: Re: [openpgp] Questions around AEAD packets
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <openpgp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/openpgp>, <mailto:openpgp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/openpgp/>
List-Post: <mailto:openpgp@ietf.org>
List-Help: <mailto:openpgp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/openpgp>, <mailto:openpgp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2017 16:19:25 -0000

+1 for your suggestions, Werner.

-derek

Werner Koch <wk@gnupg.org> writes:

> Hi,
>
> putting the patent mess aside, there are also a few other question
> involved in a new encryption mode:
>
>  1. Exactly one mode defined by a new packet number
>     or a new packet with a parameter to define the mode?
>  
>  2. Bind the mode to a certain cipher algorithm?  For example only allow
>     a mode with AES.
>
>  3. How can we do early detection of corruption?  When decrypting
>     several gigs we should be able to detect corrupted data after having
>     processed, say, one gig.  Shall such a feature be configurable?
>     Shall we link it to partial length headers.
>
> My ideas here are:
>
>  re 1. A new packet with a parameter to define the actual mode.  Make
>        one mode mandatory.  Additional parameters should have a length
>        header so that parsers have an easier way to parse the header
>        even if they don't implement that mode.
>    
>        The rational for this is to allow for some experimentation and
>        separate the packet format from the finally chosen mandatory
>        mode.
>
>  re 2: Binding a mode to an algorithm makes testing easier.  This will
>        also make implementing stream cipher modes easier because it
>        allows to blur the distinction between cipher algorithm and mode.
>
>  re 3: The simplest idea would be to use fixed chunks of the ciphertext
>        and either link them together using a counter or the hash of the
>        previous authentication tag.  The packet header would give the
>        length of the chunks in blocks.  It needs to be decided whether a
>        final one-block chunk is okay.
>
>
>
> Salam-Shalom,
>
>    Werner

-- 
       Derek Atkins                 617-623-3745
       derek@ihtfp.com             www.ihtfp.com
       Computer and Internet Security Consultant