Bug 247973

Summary:	kde-base/kmail doesn't handle encrypted and signed messages properly (with OpenGPG/MIME)
Product:	Gentoo Linux	Reporter:	Matteo Sasso <matteo.sasso>
Component:	[OLD] KDE	Assignee:	Gentoo KDE team <kde>
Status:	RESOLVED FIXED
Severity:	major	CC:	dilfridge
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Attachments:	emerge --info

Description Matteo Sasso 2008-11-21 14:52:03 UTC

When I create an encrypted and signed message, it can be decrypted and verified only by KMail. Other clients can decrypt it but the signature seems invalid. I first experienced this problem in the 3.5 series (I can't remember which version exactly) and it persisted as I upgraded to kde-4.1.

Reproducible: Always

Steps to Reproduce:
1. Create an encrypted and signed email
2. Send it to yourself
3. See how KMail decrypts and verifies it
4. Find the message in your maildir folder
5. Run: gpg2 <filename>
6. Enter the key's passphrase for decryption
7. Enter the output filename

Actual Results:  
The message is decrypted but the signature is left there, unverified. The message headers are as follows:

Content-Type: multipart/signed;
  boundary="nextPart3542461.iKSYPfKBMc";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart3542461.iKSYPfKBMc
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


Expected Results:  
Running gpg2 on a message written using enigmail, I get the following output:
gpg: Signature made <timestamp> using DSA key ID <id>
gpg: Good signature from <sender>

The message headers are as follows:

Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable



KMail also cannot verify encrypted/signed messages created by enigmail. gpg2, as shown above, verifies them correctly.

Comment 1 Matteo Sasso 2008-11-21 14:56:24 UTC

Created attachment 172699 [details]
emerge --info

Comment 2 Tomáš Chvátal (RETIRED) gentoo-dev

2008-11-21 15:02:20 UTC

I can confirm this, but i have no idea now to fix that.

Guys any suggestions/solutions?

Comment 3 Andreas K. Hüttel archtester

2010-01-23 17:40:01 UTC

Have you set a signature digest algorithm different from sha1 in your gnupg options? If yes, you're hitting kde bug 128784 (fixed in 4.3.5).

http://bugs.kde.org/show_bug.cgi?id=128784

Comment 4 Theo Chatzimichos (RETIRED) archtester

2010-03-10 18:11:02 UTC

closing per comment #3, plz reopen if it is still valid