On 7/28/19 12:26 PM, Dave Howorth wrote:
On Sun, 28 Jul 2019 03:05:03 +0200 Oleksii Vilchanskyi <oleksii.vilchanskyi@gmail.com> wrote:
On 7/27/19 11:44 PM, Mathias Homann wrote:
Am Samstag, 27. Juli 2019, 22:36:00 CEST schrieb Dave Howorth:
Searching hasn't provided me with any enlightenment and the man page doesn't list or explain the error messages. So can anybody point me to an idiot's guide to what's supposed to happen and how to make it so?
the shortest possible version: you are trying to fetch the key from a keyserver that is broken / dead, or you don't have a keyserver listed in ~/.gnupg/gpg.conf
edit the file ~/.gnupg/gpg.conf and find the line that starts with the keyword "keyserver", and make sure you list one that works. Then gpg --recv-keys should work as expected.
I have this in my gpg.conf: keyserver hkp://pool.sks-keyservers.net
keyserver option should be put in ~/.gunpg/dirmngr.conf now.
Also, considering recent news[0], it should be keyserver hkps://keys.openpgp.org
[0]: <https://gist.github.com/rjhansen/67ab921ffb4084c865b3618d6955275f>
Thanks, yes I remember seeing that news about key poisoning. So I've commented out the default keyserver line in gpg.conf and created a dirmngr.conf with just that line in it. It has changed what happens; now I see:
$ /usr/bin/gpg2 --batch --no-tty --recv-keys B533181C6D8D47D5 gpg: key B533181C6D8D47D5: no user ID gpg: Total number processed: 1
and Claws still says the key is not available
In my case:
% gpg -v --recv-keys B533181C6D8D47D5 gpg: data source: https://keys.openpgp.org:443 Notice the data source ^ gpg: pub dsa1024/0xB533181C6D8D47D5 2004-03-22 gpg: key 0xB533181C6D8D47D5: no user ID gpg: Total number processed: 1
You might also see in there
gpg: no running Dirmngr - starting '/usr/bin/dirmngr' gpg: waiting for the dirmngr to come up ... (5s) gpg: connection to dirmngr established
My configuration:
% gpg --version gpg (GnuPG) 2.2.17 libgcrypt 1.8.4 % grep -ve "^#" ~/.gnupg/gpg-agent.conf enable-ssh-support pinentry-program /usr/bin/pinentry-qt default-cache-ttl 60 max-cache-ttl 120
% grep -ve "^#" ~/.gnupg/gpg.conf personal-cipher-preferences AES256 AES192 AES personal-digest-preferences SHA512 SHA384 SHA256 personal-compress-preferences ZLIB BZIP2 ZIP Uncompressed default-preference-list SHA512 SHA384 SHA256 AES256 AES192 AES ZLIB BZIP2 ZIP Uncompressed cert-digest-algo SHA512 s2k-digest-algo SHA512 s2k-cipher-algo AES256 charset utf-8 fixed-list-mode no-comments no-emit-version keyid-format 0xlong list-options show-uid-validity verify-options show-uid-validity with-fingerprint with-key-origin require-cross-certification no-symkey-cache throw-keyids use-agent
% grep -ve "^#" ~/.gnupg/dirmngr.conf> keyserver hkps://keys.openpgp.org verbose log-file /home/user/gnupg.log
If you won't figure it out after this message, you should probably ask gnupg mailing lists. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org