using --keyserver but still getting gpg: no keyserver known (use option --keyserver)

[Dr. Peter Voigt]

On Mon, 18 Sep 2017 12:13:20 -0400
Lee <ler762 at gmail.com> wrote:

> Try it without the port number
> $ gpg --keyserver hkp://pgp.mit.edu --search-keys
> torbrowser at torproject.org gpg: searching for
> "torbrowser at torproject.org" from hkp server pgp.mit.edu (1)     Tor
> Browser Developers (unknown) <torbrowser at torproject.org> 4096 bit RSA
> key 0x669ECC703A7C585A, created: 2017-08-18, expires: 2020-08-24
> (2)     Tor Browser Developers <torbrowser at torproject.org>
>           4096 bit RSA key 0xB9294788BE63AEFC, created: 2017-08-18,
> expires: 2017-08-25 (expired)
> (3)     Tor Browser Developers (signing key)
> <torbrowser at torproject.org> 4096 bit RSA key 0x4E2C6E8793298290,
> created: 2014-12-15, expires: 2020-08-24
> Keys 1-3 of 3 for "torbrowser at torproject.org".  Enter number(s),
> N)ext, or Q)uit > q
 

Hhm, it's working on my machine both with "hkp://" and with port number:

# gpg --keyserver hkp://pgp.mit.edu:11371 --search-keys torbrowser at torproject.org
gpg: data source: http://pgp.mit.edu:11371
(1)	Tor Browser Developers (unknown) <torbrowser at torproject.org>
	  4096 bit RSA key 669ECC703A7C585A, created: 2017-08-18, expires: 2020-08-24
(2)	Tor Browser Developers <torbrowser at torproject.org>
	  4096 bit RSA key B9294788BE63AEFC, created: 2017-08-18, expires: 2017-08-25 (expired)
(3)	Tor Browser Developers (signing key) <torbrowser at torproject.org>
	  4096 bit RSA key 4E2C6E8793298290, created: 2014-12-15, expires: 2020-08-24
Keys 1-3 of 3 for "torbrowser at torproject.org".  Enter number(s), N)ext, or Q)uit > 

My GnuPG version is 2.1.18.

Under Debian Stretch I have solved similar keyserver related issues
with the option "standard-resolver" in ~/.gnupg/dirmngr.conf. I hope it
helps.

Peter


-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20170918/2ebf97e5/attachment-0001.sig>