Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2020-06-15T23:26:12Zhttps://gitlab.torproject.org/legacy/trac/-/issues/16073Unable to use Tor Browser with SOCKS5 proxy2020-06-15T23:26:12ZcypherpunksUnable to use Tor Browser with SOCKS5 proxySince 4.5.0 I am not able to use Tor Browser with non-tor SOCKS proxy (with local SSH tunnel) for usual, not-anonymous use for clearnet. I think it is due to new isolation stuff when browser sends additional data as login+pass.
extensio...Since 4.5.0 I am not able to use Tor Browser with non-tor SOCKS proxy (with local SSH tunnel) for usual, not-anonymous use for clearnet. I think it is due to new isolation stuff when browser sends additional data as login+pass.
extensions.torbutton.isolate_content -> false doesn`t help
I know it is not trivial, but I want more security even with non-anonymous use.
Maybe related:
https://trac.torproject.org/projects/tor/ticket/16055https://gitlab.torproject.org/legacy/trac/-/issues/29236After updating tor to 8.0.5, socks5 started to not work2020-06-13T16:10:05ZTracAfter updating tor to 8.0.5, socks5 started to not workI usually use socks5 in Adium messenger, but when i updated tor to new version Adium start to give the error - Error: Connection failed
In tor logs i found those -
1/30/19, 20:16:31.821 [WARN] Fetching socks handshake failed. Closing.
...I usually use socks5 in Adium messenger, but when i updated tor to new version Adium start to give the error - Error: Connection failed
In tor logs i found those -
1/30/19, 20:16:31.821 [WARN] Fetching socks handshake failed. Closing.
1/30/19, 20:16:31.821 [WARN] socks5: parsing failed - invalid user/pass authentication message.
1/30/19, 20:16:31.821 [WARN] Fetching socks handshake failed. Closing.
1/30/19, 20:16:37.680 [WARN] socks5: parsing failed - invalid user/pass authentication message.
1/30/19, 20:16:37.680 [WARN] Fetching socks handshake failed. Closing.
1/30/19, 20:16:37.680 [WARN] socks5: parsing failed - invalid user/pass authentication message.
I never had this before, all have worked perfectly. Immediately after the update, everything stopped working. I tried all, i installed tor/messenger and updated os, but nothing helped.
Help!
**Trac**:
**Username**: bugiguimanDavid Gouletdgoulet@torproject.orgDavid Gouletdgoulet@torproject.orghttps://gitlab.torproject.org/legacy/trac/-/issues/15014Socks5 and socks5t got changed and broke compatibility with privoxy2017-06-09T15:52:48ZTracSocks5 and socks5t got changed and broke compatibility with privoxyI updated tor on the 15 relays I run privately and the 5 my employers network hosts, for employees to use as clients; I started receiving an error in privoxy for unencrypted sites when I tried to browse:
* 2015-02-23 16:02:09.636 0000...I updated tor on the 15 relays I run privately and the 5 my employers network hosts, for employees to use as clients; I started receiving an error in privoxy for unencrypted sites when I tried to browse:
* 2015-02-23 16:02:09.636 0000260c Error: Invalid server headers. Applying the MS IIS5 hack didn't help.
and in torbrowser:
* "...does not look like http"
I was pulling my hair out restoring backup configs for privoxy, tor, and tor browser itself to find that something had been changed in tor 0.2.5.10 with the socks5 protocols that now breaks functionality for privoxy. I have used other programs on socks5 fine since the change, which is why I thought it was privoxy, which it "is".
However, when you decide to change something in tor where another service is developed and deployed in unison with tor, like privoxy, please put an option to specify in torrc to use the old protocol until privoxy, or whatever project, can get up to speed :) I Have always known privoxy and tor to be promoted together, people suggesting privoxy when they suggest tor. I mean, socks5t was developed specifically for privoxy, right?
Now, I'd say over HALF of the people using the tor network to browse (because of the popularity with privoxy) are having the same error, not realizing they need to change privoxy config to use socks4 or socks4a until privoxy updates or you add an option to revert compatibility.
I don't know if privoxy is in tor browser bundle or not but I assume not, since tor browser gets configured with the only proxy being socks, by default. I assume torbirdy? is responsible for this.
**Trac**:
**Username**: johnakabeanTor: unspecified