Re: [openpgp] Proposal to include AEAD OCB mode to 4880bis

Werner Koch <> Tue, 31 October 2017 15:49 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 3E54E13F76E for <>; Tue, 31 Oct 2017 08:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 9jgcUTxGrS7b for <>; Tue, 31 Oct 2017 08:49:26 -0700 (PDT)
Received: from ( [IPv6:2001:aa8:fff1:100::22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2F63E13F4E9 for <>; Tue, 31 Oct 2017 08:49:11 -0700 (PDT)
Received: from uucp by with local-rmail (Exim 4.89 #1 (Debian)) id 1e9Ymr-0001rL-Ld for <>; Tue, 31 Oct 2017 16:49:09 +0100
Received: from wk by with local (Exim 4.84 #3 (Debian)) id 1e9YiL-0006cQ-DR; Tue, 31 Oct 2017 16:44:29 +0100
From: Werner Koch <>
To: "brian m. carlson" <>
Cc: Ronald Tse <>, "openpgp\" <>
References: <> <> <> <> <> <> <> <>
Organisation: The GnuPG Project
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Mail-Followup-To: "brian m. carlson" <>, Ronald Tse <>, "openpgp\" <>
Date: Tue, 31 Oct 2017 16:44:23 +0100
In-Reply-To: <> (brian m. carlson's message of "Sat, 28 Oct 2017 00:33:46 +0000")
Message-ID: <>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=UFO_red_noise_JFK_high_security_kilderkin_ANZUS_credit_card_Sundevil"; micalg=pgp-sha256; protocol="application/pgp-signature"
Archived-At: <>
Subject: Re: [openpgp] Proposal to include AEAD OCB mode to 4880bis
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "Ongoing discussion of OpenPGP issues." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 31 Oct 2017 15:49:28 -0000


On Sat, 28 Oct 2017 02:33, said:

> GnuPG relies on libgcrypt for cryptographic functionality.  On Debian,
> libgcrypt is linked into Xorg, which is often linked to proprietary
> software such as graphics drivers.  Since Debian cannot avail itself of

There are no proprietary drivers in Debian.  Further it is not instantly
possible to decide what makes up a derivative work, "linking" would be
just one data point but even that term "linking" is not well defined.

> license 1 prohibits uses with proprietary software, Debian's GnuPG is
> unlikely to have support for OCB unless Debian ships two separate copies

GnuPG already uses OCB for the private key storage format and will
protect keys using this format if you use --enable-extended-key-format.
Eventually this will be the default key storage format for private keys.


> I remain wholly opposed to including OCB in the OpenPGP specification,

Do you prefer that we put a "2 - reserved for OCB" into the specs and
have an I-D to specify the oue of OCB in OpenPGP?  This would make the
life for implementors and auditors harder.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.