[Tickets #12952] Re: PGP/MIME signed message with user signature fails in thunderbird

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/12952
------------------------------------------------------------------------------
  Ticket             | 12952
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | PGP/MIME signed message with user signature fails in
                     | thunderbird
  Queue              | IMP
  Version            | 6.1.6
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             |
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2014-02-09 22:50) wrote:

> "--[SP]" is just the problem. To make thunderbird/enigmail run pgp  
> validation successfully you have to deselecet the usenet style  
> signature tag. For the user this dependency is not obvious and  
> causes mistrust to the horde/pgp-functions.

Why do you have to do this?  There's no reason to.  In fact, we could  
send signature separators as "--[SP][SP][SP][SP][SP][SP][SP]" if we  
wanted to.  It's totally irrelevant.  There is no limitation on  
trailing spaces within the actual PGP-MIME data itself.  (There's a  
limitation on trailing spaces **AFTER** content-transfer encoding has  
been employed.  But that's a totally different topic, and not an issue  
here since we protect trailing spaces by using q-p encoding.)

> Thunderbird/Enigmal refers to RFC3156 and Horde quotes from RFC3676  
> and the problem persists.

Please read 3676.  It refers to precisely this issue, while directly  
referencing 3156.  In short, there is nothing wrong with trailing  
spaces for ANY data (let alone signature separators) as long as you  
are using OpenPGP-MIME (instead of raw OpenPGP format).