When selecting certify on an expired key I then get an error. Kleopatra should not even offer this action.
Revisions and Commits
|rKLEOPATRAa0f79d1f10ad Add possibility to require valid keys for a command|
|rKLEOPATRA4e596c03813b Require a valid key for the Certify command|
|rKLEOPATRA6c387232bdfc Don't ask user to certify an imported expired or revoked OpenPGP key|
|rKLEOPATRAc72081d7f427 Disable Certify action if key cannot be certified|
|rKLEOPATRA82d513813124 Short-circuit check for revoked or expired user ID|
|rKLEOPATRA1545acf09493 Add helper to check if a key can be certified|
|rKLEOPATRA7ceef3e16d64 Do not offer expired user ID for certification|
|rKLEOPATRA39d9c325c50f Refuse to certify revoked or expired keys|
|rMeedaaf70167f cpp: Reject signing expired keys|
The Certify action is now disabled everywhere for revoked and expired keys, i.e. in the main menu and the certificate list context menu, in the Certficate Details dialog, and in the Certifications dialog. Moreover, after importing a revoked or expired public OpenPGP key, the user isn't asked anymore whether they want to certify it.