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 592526 - Seahorse should warn the user when importang Revocation cert
Seahorse should warn the user when importang Revocation cert
Product: seahorse
Classification: Applications
Component: general
Other Linux
: Normal normal
: 2.26.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Reported: 2009-08-20 22:53 UTC by Andreas Moog
Modified: 2018-08-03 19:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Andreas Moog 2009-08-20 22:53:51 UTC
(Forwarded from

Package: seahorse
Version: 2.26.1-2
Severity: minor

1. Use GPG to generate revocation cert (Test.asc)
2. Double-click on Test.asc in Nautilus

Seahorse reports a spurious error (reported elsewhere), but still
revokes the key. I think it should notify the user that they're not
importing a normal key. Revocation is a pain to manually undo (from what
I've seen), and Seahorse does nothing to indicate that the file is about
to have an effect on existing keys. Obviously if you've just generated
it you should know what it does, BUT

- The user might not expect seahorse to run as the default action (I
used to have leafpad set to open .ASC files, forgot I hadn't changed

- The user might just find the revocation long after generating it,
forgets what it is, tries to import it..
Comment 1 Michael Düll 2009-10-12 13:08:12 UTC
Have filed same bug in launchpad for GNOME 2.28 and Ubuntu 9.10 beta
Comment 2 Michael Düll 2009-10-13 15:27:37 UTC
Could someone please set this bug to NEW?
Comment 3 GNOME Infrastructure Team 2018-08-03 19:15:51 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: