Seahorse's configured keyservers are not the same as those in gpg.conf

config/chroot_local-includes/etc/dconf/db/local.d/00_Tails_defaults contains the following

[org/gnome/crypto/pgp]
keyservers = ['hkp://pool.sks-keyservers.net']

In Tails itself, however, there are two keyservers configured in Seahorse

$ gsettings get org.gnome.crypto.pgp keyservers 
['hkp://pool.sks-keyservers.net', 'ldap://keyserver.pgp.com']

(While testing my fixes for #9095 (closed) it seemed that sometimes—but not always—a fair amount of time in the test is spent waiting for keyserver.pgp.com to resolve; at least that’s the domain referenced in the Seahorse status bar. Maybe it’s a red herring of sorts.)

Anyhow, $HOME/.gnupg/gpg.conf is configured with hkps://hkps.pool.sks-keyservers.net but of course Seahorse does not speak hkps. Should it be restricted to just communicating with hkp://hkps.pool.sks-keyservers.net? If so, how?

Feature Branch: kytv:bugfix/9233-seahorse

Related issues

• Related to #9339 (closed)
• Blocks #9095 (closed)

Original created by @kytv on 9233 (Redmine)