Bug 295043

Summary:	openpgp signature of expired key is shown as invalid
Product:	[Applications] kmail2	Reporter:	Hauke Laging <hauke>
Component:	crypto	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	minor	CC:	asala, kde, montel
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Hauke Laging 2012-02-29 01:32:12 UTC

Version:           unspecified (using KDE 4.6.0) 
OS:                Linux

After the expiration of the signing key the signature is shown as invalid. Not even the details give any hint to the real problem. Even worse: It is as far as I can see exactly the same behaviour like with a bad signature.

GnuPG knows these statuses for signatures (see /usr/share/doc/packages/gpg2/DETAILS):
GOODSIG
EXPSIG
EXPKEYSIG
REVKEYSIG
BADSIG
ERRSIG
VALIDSIG

It seems to me that kmail tells apart only GOODSIG on the one hand and the rest on the other. And for the first case the different TRUST_* levels.

I think this can be considered a bug.

Reproducible: Always

Steps to Reproduce:
Click on the mail.


Expected Results:  
EXPSIG and EXPKEYSIG should be treated like the combination GOODSIG/TRUST_UNDEFINED i.e. show the mail border in yellow and tell the user about the problem in the details section.

Comment 1 Laurent Montel 2012-08-16 14:23:10 UTC

Will look at.

Comment 2 A. Sala 2013-02-26 15:07:27 UTC

I confirm this occurs also in Kmail 4.9.5, in Ubuntu 12.10.

Comment 3 A. Sala 2013-03-07 13:42:02 UTC

And in Kmail shipped with KDE 4.10.1, too.

Comment 4 Rolf Eike Beer 2013-03-08 18:55:23 UTC

Strongly related to bug 64424

Comment 5 Denis Kurz 2016-09-24 18:11:20 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 6 Denis Kurz 2017-01-07 22:33:20 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.