Am Sat, 2 Aug 2014 15:54:00 +0000 (UTC)
schrieb Kill Your TV <killyourtv@???>:
> On Sat, 2 Aug 2014 14:15:48 +0000 (UTC)
> intrigeri <intrigeri@???> wrote:
>
> > Oh, I forgot: it would be wonderful if addressing #7416 ("Have GnuPG
> > use the Tor SOCKS port directly") could be sneaked in as step 0.
> > It's a two-lines change, and I'd love it if I could do steps 3 and
> > 4 only once for #7512 and #7416. Would save me quite some time and
> > watt*hour's.
>
>
> FWIW, I didn't include that because at least in Debian unstable I
> cannot get it to work and I definitely have a "new enough" curl. Maybe
> it will work in Tails, but I've not tried it yet.
On Tails 1.1 it works when you replace the http-proxy from the default
config with socks5-hostname://127.0.0.1:9050/
>
> * Hostname was NOT found in DNS cache
> * Trying 127.0.0.1...
> * Hostname was NOT found in DNS cache
> * Can't complete SOCKS5 connection to 0.0.0.0:0. (1)
> * Closing connection 0
> gpgkeys: HTTP search error 7: Can't complete SOCKS5 connection to
> 0.0.0.0:0. (1)
>
>
> From what I understand
> --keyserver-options http-proxy=socks5-hostname://127.0.0.1:9050
> should be all that's needed to use Tor if Tor is accessible on port
> 9050, but it fails with both socks:// and socks5-hostname:// and Tor
> is definitely accessible:
>
> $ echo 'GET /' |nc 127.0.0.1 9050
> HTTP/1.0 501 Tor is not an HTTP Proxy
> Content-Type: text/html; charset=iso-8859-1
> <html>
> <head>
> <title>Tor is not an HTTP Proxy</title>
> [...]
>
> I'm attaching the full output of the gpg session(s) since my client is
> wrapping the lines, which makes the output harder to read. Maybe I'm
> just doing something wrong.
>
>
