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 736754 - should respect gpg.conf
should respect gpg.conf
Status: RESOLVED OBSOLETE
Product: seahorse
Classification: Applications
Component: general
git master
Other All
: Normal enhancement
: ---
Assigned To: Seahorse Maintainer
Seahorse Maintainer
Depends on:
Blocks:
 
 
Reported: 2014-09-16 15:39 UTC by Christian Stadelmann
Modified: 2018-08-03 19:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Christian Stadelmann 2014-09-16 15:39:20 UTC 
Seahorse does not respect gpg.conf which is a very bad idea since the user may have other security preferences specified than seahorse is using.
Comment 1 Stef Walter 2014-09-17 07:04:50 UTC 
Please provide specific information about which options are not respected. By the way, we use GPGME (which is produced by gnupg.org) and so in theory should be well integrated with gpg.conf.

That said, please not specific problems, as well as the exact steps you used to reach the problem. Without such information this bug will be closed as INCOMPLETE.
Comment 2 Christian Stadelmann 2014-09-21 17:44:54 UTC 
Sorry, that was too unspecific.

Everything I can change in Edit -> Preferences (key servers, key publication, recieving and auto-updating keys) are preferences separate from gpg.conf. Configuring them has no effect on gpg.conf and gpg.conf has no effect on those values.

Setting the keyid-format to long has no effect for seahorse either.
Comment 3 Stef Walter 2014-09-23 07:37:49 UTC 
Interesting. I wouldn't be against gpg.conf integration. It would be a useful feature. If you or someone you know is interested in contributing the work.
Comment 4 GNOME Infrastructure Team 2018-08-03 19:41:59 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/109.