Socks5 and socks5t got changed and broke compatibility with privoxy
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.