You are not logged in.
If you install wireshark then run
gpg -v --search-keys --keyserver hkps://hkps.pool.sks-keyservers.net BBBEBDBB24C6F355
What output does wireshark record I see 2 DNS queries one for _pgpkey-https._tcp.hkps.pool.sks-keyservers.net with a no such name response
followed by the second for hkps.pool.sks-keyservers.net which has a standard query response with a listof IP addresses.
Then a TLS1.2 session to one of the IPs just returned.
Offline
so, i tried this on a different network, that has a different isp, and it worked. i think that comcast blocks the ports needed in order to connect to the keyservers.
Offline
Seems unlikely to be blocking hkps as that uses port 443 which is the same port https uses which would block all encrypted web traffic.
More likely a more targeted block against gpg servers, the wireshark output might contain some clues as to what in particular is being blocked.
In the various keyservers you tried did that include hkp://p80.pool.sks-keyservers.net:80 ?
edit:
grammar , instead of or
Last edited by loqs (2018-03-13 23:14:42)
Offline