Re: Bad Armour Headers
nagydani@epointsystem.org (Daniel A. Nagy) Thu, 05 January 2006 17:11 UTC
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1EuYdk-0004tw-E6 for openpgp-archive@megatron.ietf.org; Thu, 05 Jan 2006 12:11:04 -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 MAA11492 for <openpgp-archive@lists.ietf.org>; Thu, 5 Jan 2006 12:09:48 -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 k05GqgIO031254; Thu, 5 Jan 2006 08:52:42 -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 k05Gqg5d031253; Thu, 5 Jan 2006 08:52:42 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-openpgp@mail.imc.org using -f
Received: from mail.epointsystem.org ([195.228.156.120]) by above.proper.com (8.12.11/8.12.9) with ESMTP id k05GqfBq031245 for <ietf-openpgp@imc.org>; Thu, 5 Jan 2006 08:52:41 -0800 (PST) (envelope-from nagydani@epointsystem.org)
Received: by mail.epointsystem.org (Postfix, from userid 1001) id 70D3C2B47A3; Thu, 5 Jan 2006 17:52:40 +0100 (CET)
Date: Thu, 05 Jan 2006 17:52:40 +0100
To: ietf-openpgp@imc.org
Subject: Re: Bad Armour Headers
Message-ID: <20060105165240.GA19354@epointsystem.org>
References: <43BD2D04.6020203@algroup.co.uk> <20060105151541.GA12372@epointsystem.org> <20060105162421.GC24021@jabberwocky.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <20060105162421.GC24021@jabberwocky.com>
User-Agent: Mutt/1.5.6+20040907i
From: nagydani@epointsystem.org
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>
I wrote: > > In order to > > prevent arbitrary wraps, the length of actual lines should be maximized in > > 64 characters You wrote: > This would give a valid encoding for long header lines, but does not > fix the problem at hand. Word wrapping would still result in broken > armor as word wrapping wouldn't know to put whitespace before the > lines it reformats. There would be no word wrapping, if everything I propose becomes standard. The concern of Werner is more of an issue, though. I will address it in a separate posting. -- Daniel
- Bad Armour Headers Ben Laurie
- Re: Bad Armour Headers David Shaw
- Re: Bad Armour Headers Daniel A. Nagy
- Re: Bad Armour Headers Ben Laurie
- Re: Bad Armour Headers Werner Koch
- Re: Bad Armour Headers David Shaw
- Re: Bad Armour Headers Ian G
- Re: Bad Armour Headers Daniel A. Nagy
- Re: Bad Armour Headers Ben Laurie
- Re: Bad Armour Headers David Shaw
- Re: Bad Armour Headers David Shaw
- Re: Bad Armour Headers vedaal
- Re: Bad Armour Headers David Shaw
- Re: Bad Armour Headers Ian G
- Re: Bad Armour Headers Matthew Byng-Maddick
- Re: Bad Armour Headers Werner Koch
- Re: Bad Armour Headers Daniel A. Nagy
- Re: Bad Armour Headers Ben Laurie
- Re: Bad Armour Headers Werner Koch
- Re: Bad Armour Headers Daniel A. Nagy
- Re: Bad Armour Headers David Shaw
- Re: Bad Armour Headers Jon Callas
- Re: Bad Armour Headers Jon Callas
- Re: Bad Armour Headers Ian G
- Re: Bad Armour Headers David Shaw