<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">On 17 Jun 2025, at 14:41, Walt Mankowski <waltman@pobox.com> wrote:<br><div><blockquote type="cite"><div><div><div><br></div><div>When I changed the command to</div><div><br></div><div>gpg --keyserver<span class="qt-Apple-converted-space"> </span><a href="hkp://keyserver.ubuntu.com">hkp://keyserver.ubuntu.com</a>::11371<span class="qt-Apple-converted-space"> </span>--recv-keys 77D4D81DC47D68FA9E9E6A7C5DF19E2B67A7B584</div><div><br></div><div>then it retrieved the key as expected. I added the port to gpg.conf and now everything is fine.</div></div></div></blockquote><div><br></div><div>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)?</div><br><blockquote type="cite"><div><div><div>I did notice that /etc/services on macOS has two entries for hkp:</div><div><br></div><div>hkp 11371/udp # OpenPGP HTTP Keyserver</div><div>hkp 11371/tcp # OpenPGP HTTP Keyserver</div><div><br></div><div>I tried commenting out the udp version and restarting dirmngr, but that had no effect.</div></div></div></blockquote><br></div><div>No, I wouldn’t expect it to. /etc/services is mainly informational these days, most applications hard code their port numbers.</div><div><br></div><div>A</div><div><br></div></body></html>