I've encountered this bug again under Precise. What confuses the issue greatly is that it's environment-dependent in an unknown way. In many posts the recommended way to deal with a missing public key is this:
gpg --keyserver pgpkeys.mit.edu --recv-key A8AA1FAA3F055C03 with the key shown here replaced by the troublesome one. For many people it works -- for me it does not. Apparently it doesn't work if you're calling gpg from behind a proxy server -- but I'm not. There's also an issue about gpg using the nonstandard port 11371 rather than port 80, but when I opened the port explicitly the problem did not go away. I've seen this behavior on two different machines, although the HTTP code has been different -- either 6 or 7. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/736533 Title: gpg gives bogus, misleading error message To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/736533/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
