[NCLUG] mailman wrapping message headers breaks GPG signatures

[Stephen Warren]

Sean Reifschneider wrote:
> On Mon, Apr 17, 2006 at 10:07:21AM -0600, Stephen Warren wrote:
>> Content-Type:<SPACE>multipart/mixed;<LINEBREAK><SPACE>boundary="------------030205050900000108000205"
>> To:
>> Content-Type:<SPACE>multipart/mixed;<SPACE>boundary="------------030205050900000108000205"
> 
> Is this in the main message header, or one of the MIME sub-parts?

One of the MIME sub-parts.

> As far
> as I know, it's totally RFC-legal to insert or remove line-breaks in long
> header lines.

Yes, it means semantically the same thing. That said, I would have hoped
that mailman would simply prepend/append extra data around the messages
it forwards, in order to avoid this kind of thing.

That said, perhaps GPG/Enigmail should collapse wrapped lines when
generating/validating signatures so that the signed data is always in a
canonical form, again to avoid this kind of thing.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
URL: <http://lists.nclug.org/pipermail/nclug/attachments/20060419/499072f2/attachment.pgp>