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 578277 - Revoked subkeys not appearing as revoked
Revoked subkeys not appearing as revoked
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
2.26.x
Other Linux
: Normal normal
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2009-04-07 18:25 UTC by Brandon Kraft
Modified: 2018-08-03 19:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
Screenshot of problem. (100.58 KB, image/png)
2009-04-07 18:49 UTC, Brandon Kraft
Details

Description Brandon Kraft 2009-04-07 18:25:49 UTC
As seen with a private/public personal key:

Two revoked subkeys that appeared as revoked in previous version (as seen in Ubuntu 8.10) now appear without the revoked strikethrough. In the properties menu, there is no indication that the subkey revoked.

Attempted to refresh with keyserver verified as having subkeys revoked failed to correct problem. Attempted to delete/import the key new from file with verified revoked signature, failed to correct problem.
Comment 1 Brandon Kraft 2009-04-07 18:27:42 UTC
Cross-posted to Launchpad for Ubuntu:
https://bugs.launchpad.net/bugs/357187
Comment 2 Adam Schreiber 2009-04-07 18:33:04 UTC
Since you submitted this bug against the applet could you attach a screenshot?  Also does the same behavior occur with seahorse?
Comment 3 Brandon Kraft 2009-04-07 18:49:12 UTC
I wasn't sure what component to select. It's in the GUI "Passwords and Encryption Keys" 

I'm attaching a screen shot of the GUI showing a subkey not revoked with a superimposed screenshot of keyserver.ubuntu.com showing the subkey with a revoked signature.
Comment 4 Brandon Kraft 2009-04-07 18:49:49 UTC
Created attachment 132290 [details]
Screenshot of problem.
Comment 5 Adam Schreiber 2009-04-07 19:20:49 UTC
$ gpg --edit-key bk@kraft.im
gpg (GnuPG) 1.4.9; Copyright (C) 2008 Free Software Foundation, Inc.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.


pub  1024D/700AA416  created: 2005-07-04  expires: never       usage: SC  
                     trust: unknown       validity: unknown
sub  2048g/DEBE4558  created: 2005-07-04  expires: never       usage: E   
[ unknown] (1). Brandon Kraft <bk@kraft.im>
[ unknown] (2)  Brandon Kraft <kraft@brandonkraft.com>
[ unknown] (3)  Brandon Kraft <kraftbj@gmail.com>
[ unknown] (4)  Brandon Kraft <bjg.kraft@gmail.com>
[ unknown] (5)  Brandon Kraft <brandon@casadekraft.com>
[ revoked] (6)  Brandon Kraft <kraftbj@brandonkraft.com>
[ unknown] (7)  Brandon Kraft <academics@brandonkraft.com>
[ revoked] (8)  Brandon Kraft (UT-Austin) <kraftbj@mail.utexas.edu>
[ unknown] (9)  Brandon Kraft (The Paulist Fathers) <bkraft@paulist.org>
[ unknown] (10)  Brandon Kraft (University Catholic Center) <kraft@utcatholic.org>
[ unknown] (11)  Brandon Kraft (The Brandon Kraft Foundation) <kraft@brandonkraft.org>
Comment 6 Adam Schreiber 2009-04-07 20:04:52 UTC
This appears to be a result of the status on revoked UID's being returned as SEAHORSE_VALIDITY_UNKNOWN instead of SEAHORSE_VALIDITY_REVOKED.  This can be seen if you have a revoked UID on a key you trust and append

 || pred->usage == SEAHORSE_USAGE_PRIVATE_KEY

to the if statement of line 845 in src/seahorse-key-manager-store.c.

For instance, my personal key has a revoked UID on it.  All of the other UID's are returned SEAHORSE_VALIDITY_ULTIMATE.  It is returned SEAHORSE_VALIDITY_UNKNOWN.

Stef, Could you give me a hint as to where the UID's are loaded?
Comment 7 GNOME Infrastructure Team 2018-08-03 19:14:40 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/31.