On 28/07/2019 12.26, Dave Howorth wrote:
On Sun, 28 Jul 2019 03:05:03 +0200 Oleksii Vilchanskyi <> wrote:
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
I'll try with a new user. cer-g@Telcontar:~> l /usr/bin/gpg lrwxrwxrwx 1 root root 4 Jan 7 2019 /usr/bin/gpg -> gpg2* cer-g@Telcontar:~> gpg --list-keys cer-g@Telcontar:~> File .gnupg/dirmngr.conf saved cer-g@Telcontar:~> gpg --recv-keys B533181C6D8D47D5 gpg: key B533181C6D8D47D5: 27 signatures not checked due to missing keys gpg: lookup_hashtable failed: Unknown system error gpg: trustdb: searching trust record failed: Unknown system error gpg: Error: The trustdb is corrupted. gpg: You may try to re-create the trustdb using the commands: gpg: cd ~/.gnupg gpg: gpg --export-ownertrust > otrust.tmp gpg: rm trustdb.gpg gpg: gpg --import-ownertrust < otrust.tmp gpg: If that does not work, please consult the manual cer-g@Telcontar:~> l .gnupg/trustdb.gpg -rw------- 1 cer-g cer 40 Sep 28 2014 .gnupg/trustdb.gpg cer-g@Telcontar:~> cer-g@Telcontar:~> rm .gnupg/trustdb.gpg cer-g@Telcontar:~> gpg --recv-keys B533181C6D8D47D5 gpg: key B533181C6D8D47D5: 27 signatures not checked due to missing keys gpg: key B533181C6D8D47D5: "Carlos E. R. (cer) <robin.listas@telefonica.net>" not changed gpg: Total number processed: 1 gpg: unchanged: 1 cer-g@Telcontar:~> It works fine here. But I use a slightly different command. -- Cheers / Saludos, Carlos E. R. (from 15.0 x86_64 at Telcontar)