So now the question is how to configure Chrome to use SOCKS instead of whatever it currently uses. But Tor is not an HTTP proxy, it's a SOCKS proxy. This means Chrome is using the wrong protocol to talk to Tor, most likely (like the error says) Chrome is talking like it would to an HTTP proxy. ![]() It means the port is right because Tor is receiving data from Chrome, but Tor tries to interpret it as SOCKS data and is unable to recognize it (67 is not an existing version of SOCKS). Another option might be to tunnel an entire (virtual) machine's traffic through Tor (like Tails OS does I think) but that is out of scope here. The safe method is the Tor Browser Bundle, you can not expect Chrome to keep you anonymous just like this. ![]() Warning: The Tor Project advises against configuring systems manually like this.
0 Comments
Leave a Reply. |