After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 224705 - PGP signature (mime and armored) verification in Evolution
PGP signature (mime and armored) verification in Evolution
Status: RESOLVED DUPLICATE of bug 217540
Product: evolution
Classification: Applications
Component: Contacts
unspecified
Other other
: Normal major
: ---
Assigned To: Evolution Triage Team
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2002-05-14 18:26 UTC by Guy Van Sanden
Modified: 2002-05-15 21:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Guy Van Sanden 2002-05-14 18:26:39 UTC
Description of Problem:  
Evolution mostly fails to verify PGP/GPG  
signatures, both ASCII armoured as MIME.  
 
PGP/MIME: 
1. Signatures from mailers other than evolution 
and mutt fail.  Although they are validated 
correctly by other mailers (e.g. Sylpheed). 
 
2. Signatures made with evolution fail in other 
mailers, except mutt (and evolution itself) 
 
 
ASCII-armoured: 
cat text.txt |gpg --clearsign | mail user 
the result fails in evolution  
 
"gpg: armor header: Version: GnuPG v1.0.6 
(GNU/Linux) 
gpg: armor header: Comment: For info see 
http://www.gnupg.org 
gpg: Signature made Tue 14 May 2002 19:32:28 
CEST using DSA key ID 28F16C35 
gpg: BAD signature from "Guy Van Sanden 
<Guy.Van.Sanden@Pandora.be>" 
 
'cat text.txt |gpg --clearsign | gpg --verify' 
gives: 
"gpg: Signature made Tue 14 May 2002 20:15:15 
CEST using DSA key ID 28F16C35 
gpg: Good signature from "Guy Van Sanden 
<Guy.Van.Sanden@Pandora.be>" 
 
or saving the file first to text also works. 
  
Steps to reproduce the problem:  
1.  PGP/Mime problem: subscribe an address to 
gnupg-users@gnupg.org (or check out the 
archives).  Most signatures will fail, they 
won't fail in mutt or sylpheed. 
 
2.  ASCII-armoured: follow the steps given 
above, the longer the text, the more likely the 
failure. 
 
3. ASCII-armoured: security announcements from 
SuSE always fail, they're fine from the command 
line. 
 
Actual Results:  
Signature failes (BAD signature from)  
  
Expected Results:  
Good signature, they can be verified outside 
evolution 
  
  
How often does this happen?  
95% of the time  
  
Additional Information:  
Verified with: 
GPG 1.0.6 and GPG 1.0.7 
Evolution 0.99 (on SuSE 7.3)  
Evolution 1.0.2 (on SuSE 7.3) 
Evolution 1.0.3 (on SuSE 8.0) 
Evolution 1.0.5 (on SuSE 8.0) 
 
The problems in bugreport #16738 differ from 
these.  Also because it covers only PGP/Mime, 
and seems to indicate that the problem lies with 
the other mailers, which I belief not to be the 
case. 
 
It may have something to do with end-line 
characters.  I saw that mutt and sylpheed ignore 
'^M' sequences in verification.
Comment 1 Gerardo Marin 2002-05-15 21:06:07 UTC

*** This bug has been marked as a duplicate of 217540 ***