On Mon, 18 Sep 2017 23:37, d...@fifthhorseman.net said:
> modern versions of gpg should default to the hkps pool, and shouldn't
> need any explicit configuration.
Right, and it is also more future proof to use the keyserver option in
dirmngr.conf instead of gpg.conf. But as you say, no configura
On Mon 2017-09-18 13:50:00 +, Patrick Schleizer wrote:
> gpg --keyserver hkp://pgp.mit.edu:11371 --search-keys m...@e-mail.com
>
> gpg --keyserver=hkp://pgp.mit.edu:11371 --search-keys m...@e-mail.com
>
> gpg: no keyserver known (use option --keyserver)
> gpg: keyserver search failed: No keyser
On Mon, 18 Sep 2017 12:13:20 -0400
Lee wrote:
> Try it without the port number
> $ gpg --keyserver hkp://pgp.mit.edu --search-keys
> torbrow...@torproject.org gpg: searching for
> "torbrow...@torproject.org" from hkp server pgp.mit.edu (1) Tor
> Browser Developers (unknown) 4096 bit RSA
> ke
On 9/18/17, Patrick Schleizer wrote:
> gpg --keyserver hkp://pgp.mit.edu:11371 --search-keys m...@e-mail.com
>
> gpg --keyserver=hkp://pgp.mit.edu:11371 --search-keys m...@e-mail.com
>
> gpg: no keyserver known (use option --keyserver)
> gpg: keyserver search failed: No keyserver available
>
> Wha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
September 18, 2017 11:43 AM, "Patrick Schleizer"
wrote:
> gpg --keyserver hkp://pgp.mit.edu:11371 --search-keys m...@e-mail.com
>
> gpg --keyserver=hkp://pgp.mit.edu:11371 --search-keys m...@e-mail.com
>
> gpg: no keyserver known (use option --key
gpg --keyserver hkp://pgp.mit.edu:11371 --search-keys m...@e-mail.com
gpg --keyserver=hkp://pgp.mit.edu:11371 --search-keys m...@e-mail.com
gpg: no keyserver known (use option --keyserver)
gpg: keyserver search failed: No keyserver available
What am I doing wrong?
__
