GNOME Bugzilla – Bug 335403
Add Revoke signature support
Last modified: 2018-08-03 19:08:00 UTC
This can be added in seahorse-pgp-key-op.c using the "revsig" edit key action. In the UI it'll be hooked into the key properties dialogs (currently have placeholder buttons).
See Bug 335404#c1
Created attachment 74101 [details] [review] work so far I determined that this functionality was doable. However, It will revoke all signatures made by currently held private keys. This patch may not build and is a work in progress, but I made it to keep track of things. The key properties UI will need to be tweaked to -strike through- revoked signatures and make the user aware of the consequences of using this functionality. revuid can be implemented similarly.
Created attachment 74422 [details] [review] functions but needs polish To Do: * Add dialog warning the user that all signatures on this key will be revoked. * Gather revoke code and reason description from the user (probably the same dialog as above) Question: * Should the key's trust be set to revoked after this operation is performed?
I'd suggest listing all the signatures that will be revoked, if there are more than one. Or is that tough to do? Since we can't individually revoke a signature, we should probably expose this in the UI as more of a 'I think this key is bad/nasty' type thing. Not sure of the exact language. If there are signatures then they would be revoked. And then it would mark the key as untrusted in the appropriate way.
*** Bug 561151 has been marked as a duplicate of this bug. ***
I don't consider this a GNOME 2.28 target blocker. Setting the module specific target milestone instead.
*** Bug 720852 has been marked as a duplicate of this bug. ***
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/seahorse/issues/9.