Bug 325760

Summary:	Invalid error "The certificate could not be certified. Error: Certificate expired"
Product:	[Applications] kleopatra	Reporter:	Franz Schrober <franzschrober>
Component:	general	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	aheinecke, dan, franzschrober, mutz
Priority:	NOR
Version First Reported In:	2.1.1
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Franz Schrober 2013-10-08 08:45:31 UTC

I've tried to create a local signature for key F8AFFCB75FDD45C903643D5A238EF63272A88AC0. The kleopatra ui stopped the certify process with following error:

The certificate could not be certified. Error: Certificate expired

This is weird because the certificate part of the key is still valid (until 2014-15-18) and only the encryption key is expired (which i never wanted to sign anyway)

Reproducible: Always

Steps to Reproduce:
1. Get key F8AFFCB75FDD45C903643D5A238EF63272A88AC0
2. create local signature using kleopatra
3. wait until the actual sign process should start
Actual Results:  
Error "The certificate could not be certified. Error: Certificate expired"

Expected Results:  
Certification successful

No output in the gnupg log viewer.

Comment 1 Franz Schrober 2013-10-08 08:48:26 UTC

Sorry wrong key id. Correct one was F515D74E6F88CE3B1ADAEC08A468312243FD7307. And small correction: It has expired sign and encrypt keys but also valid ones

Comment 2 dan 2014-04-04 12:21:46 UTC

Same issue with key F6F709F3E9A6B9FAB010F673B8B27E71C844941D.

Comment 3 Andre Heinecke 2016-04-08 16:59:12 UTC

Yes. Kleo fails to certify a certificate if one of the subkeys is expired. I've realized it thanks to issue 358392 this bug is about the same problem. In issue 358392 was a bit more activity so I'm closing this one here as a duplicate although the other issue is newer.

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