Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-13T05:30:59Zhttps://gitlab.torproject.org/legacy/trac/-/issues/13430Can't set custom http-proxy on GnuPG-settings, lost after restart2020-06-13T05:30:59ZTracCan't set custom http-proxy on GnuPG-settings, lost after restartI'm using Polipo as an HTTP-proxy over Tor, which is listening on port 8123.
If I'm searching the keyserver for keys with Enigmail, it does not work, because the default setting is "http-proxy=http://127.0.0.1:8118".
If I'm changing this...I'm using Polipo as an HTTP-proxy over Tor, which is listening on port 8123.
If I'm searching the keyserver for keys with Enigmail, it does not work, because the default setting is "http-proxy=http://127.0.0.1:8118".
If I'm changing this setting to "http-proxy=http://127.0.0.1:8123", it works, but is reset after the restart of Icedove.
Please add the opportunity on the settings-menu to permanently set GnuPG-HTTP-proxy.
TorBirdy-Version: 0.1.2
Best regards,
Jarrod
**Trac**:
**Username**: jarrod.ewingJacob AppelbaumJacob Appelbaumhttps://gitlab.torproject.org/legacy/trac/-/issues/6060add http proxy support to Tor2020-06-13T14:20:18Zproperadd http proxy support to TorMany applications, such as wget, apt-get, gpg, etc. do not speak socks, are unlikely to speak socks anytime soon, but support http.
Privoxy or polipo are of no help. They provides only one http port, with the one big drawback: all http ...Many applications, such as wget, apt-get, gpg, etc. do not speak socks, are unlikely to speak socks anytime soon, but support http.
Privoxy or polipo are of no help. They provides only one http port, with the one big drawback: all http connections will be presses through the same SocksPort (identity correlation).
torsocks is of no big help either. I think it has been designed, when identity correlation wasn't a big topic. By default torsocks uses /etc/torsocks.conf and also presses all applications started with usewithtor <app> into the same SocksPort (identity correlation again). To me it also looks like torsocks is practically unmaintained, there is a critical bug open, [IPv6 can leak real IP](https://code.google.com/p/torsocks/issues/detail?id=37), no progress for a very long time.
As a solution I propose a HttpPort directive for torrc. And stream isolate the same way, Tor stream isolates SocksPort. (Different HttpPorts get isolated, also isolate by http username or http password etc.)
I don't know how much effort it were to add a http proxy. You have already some very basic http support "Tor is not a http proxy". Can you translate the http proxy request and internally redirect it to your existing socks code?
,,
Imho "#2846 Patch GPG to support SOCKS proxies" does not make sense. Why patch individual applications, when you can support all of them by adding http proxy support to Tor... Another Related Ticket: #1667.Tor: unspecifiedRoger DingledineRoger Dingledine