After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335403 - Add Revoke signature support
Add Revoke signature support
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
unspecified
Other Linux
: Normal enhancement
: 2.28.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
: 561151 720852 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-03-21 19:14 UTC by Stef Walter
Modified: 2018-08-03 19:08 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
work so far (6.44 KB, patch)
2006-10-05 23:24 UTC, Adam Schreiber 		none Details | Review
functions but needs polish (10.02 KB, patch)
2006-10-10 16:14 UTC, Adam Schreiber 		needs-work Details | Review

Description Stef Walter 2006-03-21 19:14:08 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).
Comment 1 Adam Schreiber 2006-03-28 23:24:05 UTC 
See Bug 335404#c1
Comment 2 Adam Schreiber 2006-10-05 23:24:51 UTC 
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.
Comment 3 Adam Schreiber 2006-10-10 16:14:02 UTC 
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?
Comment 4 Stef Walter 2007-05-10 22:53:41 UTC 
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.
Comment 5 Stef Walter 2009-03-03 03:59:58 UTC 
*** Bug 561151 has been marked as a duplicate of this bug. ***
Comment 6 André Klapper 2009-03-15 16:46:49 UTC 
I don't consider this a GNOME 2.28 target blocker. Setting the module specific target milestone instead.
Comment 7 David King 2014-05-14 10:45:31 UTC 
*** Bug 720852 has been marked as a duplicate of this bug. ***
Comment 8 GNOME Infrastructure Team 2018-08-03 19:08:00 UTC 
-- 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.