I am having some problems updating my pacman keyring. I am doing
# pacman-key --refresh-keys
and I get
gpg: refreshing 70 keys from hkp://pgp.mit.edu:11371
gpg: requesting key 74AE1420 from hkp server pgp.mit.edu
gpg: requesting key FFF979E7 from hkp server pgp.mit.edu
gpgkeys: key 4B41ACF2C61A3ED1E6FE10DFA68FBA9374AE1420 not found on keyserver
gpgkeys: key AB19265E5D7D20687D303246BA1DFB64FFF979E7 not found on keyserver
gpgkeys: key 27FFC4769E19F096D41D9265A04F9397CDFD6BB0 not found on keyserver
pg: no valid OpenPGP data found.
gpg: Total number processed: 0
==> ERROR: A specified local key could not be updated from a keyserver.
I have tried changing the keyserver in /etc/pacman.d/gnupg/gpg.conf to either
but neither work.
My machine is behind my university's flaky/restrictive proxy and firewall and I am guessing that is the problem. Any ideas how to proceed?
gpg honors the http_proxy environment variable. Does setting that help?
E.g. http_proxy=http://myproxy.tld:1234 pacman-key --refresh
...or is this a case of all the traffic being transparently proxied? If it's a transparent proxy, there isn't much you can do except maybe reroute requests through an http proxy outside of the network (and on a different port).
Last edited by falconindy (2013-04-26 17:39:05)
The proxy is a good suggestion, but doesn't solve the problem. Further, I think it also requires https_proxy and ftp_proxy to be set since I have another computer on a different network for which pacman-key works and if I unset any of the three it fails.
What ports do keyservers tend to work on? Is there a keyserver that works over port 80 or some other port that is likely to be open on a very restrictive firewall?
There is an alternative HTTP:80 keyserver on the above link, along with other helpful information.