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 484159 - disable automatic retreival of PGP keys by default
disable automatic retreival of PGP keys by default
Status: RESOLVED FIXED
Product: seahorse
Classification: Applications
Component: general
2.20.x
Other All
: Normal normal
: 2.22.0
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2007-10-06 15:31 UTC by Sam Morris
Modified: 2007-10-29 17:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description Sam Morris 2007-10-06 15:31:03 UTC
Please describe the problem:
The option mentioned in http://bugzilla.gnome.org/show_bug.cgi?id=366798#c7 is really great--it makes it possible to use Seahorse for management of my PGP keyring. :)

I really think that this option should be disabled by default. It is certainly not *this* user's expectation that viewing a key's properties causes the rest of the web of trust to be downloaded into his public keyring.

Another reason to disable it is because Seahorse appears to lock up entirely while key retreival is taking place. Initially I thought that Seahorse was simply locking up entirely when this happened... it was only when I later ran gpg and saw that I had a few hundred new keys present on my keyring that I realised what was going on.

Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Adam Schreiber 2007-10-29 17:51:44 UTC
I also disabled auto key uploading for much the same reason.  It also provides a bit of a safety net for new users that may be unsure what they did was correct.

2007-10-29  Adam Schreiber  <sadam@clemson.edu>

    * data/seahorse.schemas.in: Disabled automatic key uploading 
    retrieval by default.  Fixes bug #484159