You are not logged in.
It is important to understand how resolv.conf and systemd-resolved interact to properly configure the DNS that will be used, some explanations are provided in systemd-resolved.
(emphasis mine)
If gnupg does not work with a symlink to stub-resolv.conf and systemd-networkd running correctly then it is really a bug somewhere. If gpg can't deal with itbeing a symlink, then try to copy the file.
Last edited by progandy (2021-01-01 17:05:54)
| alias CUTF='LANG=en_XX.UTF-8@POSIX ' |
Offline
It does work with a the stub resolv.conf and systemd-networkd, the person in question just didn't configure their system correctly.
Online
Well, thank you for all the indirect help
It turns out that I originally had empty `/etc/resolve.conf`, but I should've done this:
ln -sf /run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
I just did, rebooted and then run:
gpg --verbose --keyserver hkp://keys.gnupg.net --recv EC94D18F7F05997E
and it works just fine.
I should've followed more carefully instructions on https://wiki.archlinux.org/index.php/Systemd-resolved page.
Offline
Thanks everyone and especially #28!
Dude ... I've been using systemd-resolved for (what it feels like) years and never noticed I did it wrongly ...
Last edited by resi (2021-02-05 22:45:39)
Offline