Re: Bad Armour Headers

David Shaw <dshaw@jabberwocky.com> Thu, 05 January 2006 15:25 UTC

Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuX00-0000oh-Ng for openpgp-archive@megatron.ietf.org; Thu, 05 Jan 2006 10:25:56 -0500
Received: from above.proper.com (above.proper.com [208.184.76.39]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA26297 for <openpgp-archive@lists.ietf.org>; Thu, 5 Jan 2006 10:24:39 -0500 (EST)
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id k05F6auq015295; Thu, 5 Jan 2006 07:06:36 -0800 (PST) (envelope-from owner-ietf-openpgp@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id k05F6aha015294; Thu, 5 Jan 2006 07:06:36 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from foobar.cs.jhu.edu (foobar.cs.jhu.edu [128.220.13.173]) by above.proper.com (8.12.11/8.12.9) with ESMTP id k05F6Z2e015284 for <ietf-openpgp@imc.org>; Thu, 5 Jan 2006 07:06:36 -0800 (PST) (envelope-from dshaw@jabberwocky.com)
Received: from walrus.hsd1.ma.comcast.net (walrus.hsd1.ma.comcast.net [24.60.132.70]) by foobar.cs.jhu.edu (8.11.6/8.11.6) with ESMTP id k05F6ZS10304 for <ietf-openpgp@imc.org>; Thu, 5 Jan 2006 10:06:35 -0500
Received: from grover.jabberwocky.com (grover.jabberwocky.com [172.24.84.28]) by walrus.hsd1.ma.comcast.net (8.12.8/8.12.8) with ESMTP id k05F6dX6026127 for <ietf-openpgp@imc.org>; Thu, 5 Jan 2006 10:06:39 -0500
Received: from grover.jabberwocky.com (grover.jabberwocky.com [127.0.0.1]) by grover.jabberwocky.com (8.13.1/8.13.1) with ESMTP id k05F6TKv024060 for <ietf-openpgp@imc.org>; Thu, 5 Jan 2006 10:06:29 -0500
Received: (from dshaw@localhost) by grover.jabberwocky.com (8.13.1/8.13.1/Submit) id k05F6TtM024059 for ietf-openpgp@imc.org; Thu, 5 Jan 2006 10:06:29 -0500
Date: Thu, 05 Jan 2006 10:06:29 -0500
From: David Shaw <dshaw@jabberwocky.com>
To: OpenPGP <ietf-openpgp@imc.org>
Subject: Re: Bad Armour Headers
Message-ID: <20060105150629.GB24021@jabberwocky.com>
Mail-Followup-To: OpenPGP <ietf-openpgp@imc.org>
References: <43BD2D04.6020203@algroup.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <43BD2D04.6020203@algroup.co.uk>
OpenPGP: id=99242560; url=http://www.jabberwocky.com/david/keys.asc
User-Agent: Mutt/1.5.11
Sender: owner-ietf-openpgp@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-openpgp/mail-archive/>
List-Unsubscribe: <mailto:ietf-openpgp-request@imc.org?body=unsubscribe>
List-ID: <ietf-openpgp.imc.org>

On Thu, Jan 05, 2006 at 02:28:20PM +0000, Ben Laurie wrote:
> 
> draft 15 says:
> 
> "    The format of an Armor Header is that of a key-value pair.  A colon
>     (':' 0x38) and a single space (0x20) separate the key and value.
>     OpenPGP should consider improperly formatted Armor Headers to be
>     corruption of the ASCII Armor. "
> 
> However, I see improperly formatted headers because of word wrapping.
> There doesn't appear to be a way to wrap a long line, so I must reject
> these as badly formatted (not that other implementations do, it seems).

GPG rejects these as well.  Word wrapping mangles clearsigned
documents as well, of course, so it's more than just an armor header
problem.

I'm not sure what can be done about that except to tell people "don't
corrupt the armor, please".

David