While looking into T7790: Kleopatra: "no trusted certification" should have precedence over "expired" in signature verification I noticed that Kleopatra reports good signatures as "invalid" if the signing key is expired or revoked. I don't think that this is done intentionally. gpg reports such signatures as good signatures. See T7790#210769 (for output of gpg) and T7790#211521 (for screenshots of Kleopatra).
Description
Description
Revisions and Commits
Revisions and Commits
| rLIBKLEO Libkleo | |||
| rLIBKLEO5068e461be73 Adapt test to new signature verification texts | |||
| rLIBKLEO9b09f94aed6e Fix and improve handling of good but not fully valid signatures | |||
Related Objects
Related Objects
Event Timeline
Comment Actions
Fixed. Some examples for the improved texts which are based on the texts that gpg prints.
- good signature with expired key
- good signature with revoked key
- good signature with uncertified key
- expired signature with certified key
- expired signature with uncertified key
Hint: Create expired signatures with gpg --default-sig-expire seconds=5 --detach-sign ...
This ticket is mostly about fixing the problem that good signatures were reported as invalid. Unless there are actual errors in the new texts there's T7786: Draft: Kleopatra: improvements of signature verification result messages for improving the messages.