On 17 Jun 2025, at 14:41, Walt Mankowski <[email protected]> wrote: > > When I changed the command to > > gpg --keyserver hkp://keyserver.ubuntu.com::11371 --recv-keys > 77D4D81DC47D68FA9E9E6A7C5DF19E2B67A7B584 > > then it retrieved the key as expected. I added the port to gpg.conf and now > everything is fine.
Aha, that’s interesting. keyserver.ubuntu.com does also serve keys on the default HTTP port, so I’m not sure why the explicit port number would help. Out of curiosity, what happens if you change it to hkps://keyserver.ubuntu.com ? (with the “s” and without the port)? > I did notice that /etc/services on macOS has two entries for hkp: > > hkp 11371/udp # OpenPGP HTTP Keyserver > hkp 11371/tcp # OpenPGP HTTP Keyserver > > I tried commenting out the udp version and restarting dirmngr, but that had > no effect. No, I wouldn’t expect it to. /etc/services is mainly informational these days, most applications hard code their port numbers. A
signature.asc
Description: Message signed with OpenPGP
_______________________________________________ Gnupg-users mailing list [email protected] https://lists.gnupg.org/mailman/listinfo/gnupg-users
