IETF Logo Mail Archive

Re: [openpgp] The checksum may appear

Werner Koch <wk@gnupg.org> Fri, 19 March 2021 06:55 UTC

Return-Path: <wk@gnupg.org>
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 680873A147F for <openpgp@ietfa.amsl.com>; Thu, 18 Mar 2021 23:55:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, 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=gnupg.org
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 72zn1kHrTtwg for <openpgp@ietfa.amsl.com>; Thu, 18 Mar 2021 23:55:10 -0700 (PDT)
Received: from kerckhoffs.g10code.com (kerckhoffs.g10code.com [IPv6:2001:aa8:fff1:100::22]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 613463A147E for <openpgp@ietf.org>; Thu, 18 Mar 2021 23:55:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnupg.org; s=20181017; h=Content-Type:MIME-Version:Message-ID:In-Reply-To:Date: References:Subject:Cc:To:From:Sender:Reply-To:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=tDOMAhyuOvKqCATxOT36pY+rVWm2+YHa34ZZJ/Iu2FI=; b=emBVje7bB6NDZYoryovdvAq2Sj 4wVrjQhyQjUn0svHIPc3vNnvzGbOCd1IkKJEC75ijPHDyZIqE+2hRC7zhgUy8oXeepBcYZqiOp55T nHLbi8vg4QwOTaxTq7xileY5ywqT8spwHhNc4OFIJBbfpy3BXp3LFZpHAoFpbpacVPqs=;
Received: from uucp by kerckhoffs.g10code.com with local-rmail (Exim 4.89 #1 (Debian)) id 1lN92J-0002jo-C9 for <openpgp@ietf.org>; Fri, 19 Mar 2021 07:55:07 +0100
Received: from wk by wheatstone.g10code.de with local (Exim 4.92 #5 (Debian)) id 1lN929-0002xB-4K; Fri, 19 Mar 2021 07:54:57 +0100
From: Werner Koch <wk@gnupg.org>
To: Ángel <angel@16bits.net>
Cc: openpgp@ietf.org
References: <20210317145508.136021-1-dkg@fifthhorseman.net> <5a927ffed96b38efa08c58b6a29e565dff87a535.camel@16bits.net>
Organisation: GnuPG e.V.
X-message-flag: Mails containing HTML will not be read! Please send only plain text.
Mail-Followup-To: Ángel <angel@16bits.net>, openpgp@ietf.org
Date: Fri, 19 Mar 2021 07:54:56 +0100
In-Reply-To: <5a927ffed96b38efa08c58b6a29e565dff87a535.camel@16bits.net> ("Ángel"'s message of "Fri, 19 Mar 2021 00:19:15 +0100")
Message-ID: <87blbfpr9b.fsf@wheatstone.g10code.de>
User-Agent: Gnus/5.13 (Gnus v5.13)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=World_Health_Organization_Yukon_World_News_JUWTF_sneakers_Scammers=A"; micalg="pgp-sha256"; protocol="application/pgp-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/openpgp/WCXKPE4U8zB7dBViahZgfgwIVyk>
Subject: Re: [openpgp] The checksum may appear
X-BeenThere: openpgp@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Mar 2021 06:55:12 -0000

On Fri, 19 Mar 2021 00:19, Ángel said:

> -OpenPGP's Radix-64 encoding is composed of two parts: a base64
> encoding of the binary data and a checksum.
> +OpenPGP's Radix-64 encoding is composed of two parts: a base64
> encoding of the binary data and an optional checksum.

> -The checksum with its leading equal sign MAY appear on the first line
> after the base64 encoded data.
> +If present, the checksum with its leading equal sign SHALL appear on
> the next line after the base64 encoded data.

Adding "optional" and making the CRC a SHOULD create indeed clarifies
the intention of the RFC.  Thus I am in favor of this change.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

v2.23.0 | Report a Bug | By Email