It was decided to add an action to disable/enable a certificate in the context menu of the certificate list. It should go after "Change Certification Power" as it is similar.
The following command should be used: https://dev.gnupg.org/rG21f7ad563d9bcb6d295e8f313f29b14238e7481f
I'm not sure about the name of that action. Maybe simply "Disable/Enable"?
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Testing | None | T7216 Kleopatra: Integrate "disabled" feature from gpg | ||
| Testing | • TobiasFella | T7234 Kleopatra: add disable/enable certificate in context menu | ||
| Resolved | • ikloecker | T7239 GpgME: Add job for disabling/enabling a certificate |
gpg4win-Beta-70: works.
I disabled a certificate, it was not shown anymore in the "all" view. Change to the "Disabled" filter and enabled it again -> it shows again with the "All" filter.
Disabling a private certificate does not allow it for signing and not for encrypting to it. It is also not offered for these any more.
But verifying files which were signed by it works.
The only thing which is not as I would expect it: the certificate with secret key is not listed with a bold font, which would be the usual presentation, if the secret key exists locally or on a known card.
Is this something which can not be handled otherwise? Because the certificate is deactivated we can not know if the secret key exists locally?
Because if not, I would like to see this information.
You mean that a disabled certificate with secret key isn't listed with bold font? That's probably because we have an appearance filter for disabled certificates which takes precedence.
Yeah. so lets ditch that appearance filter. But that's for ticket T7217. So I'm setting this ticket to done for 4win.
Removing the appearance filter won't fix own disabled certificates not being bold; the problem here is that the "My certificates" filter doesn't trigger at all anymore for disabled certificates