socks5-proxy

ein socks5-proxy ist ein simpler traffic-weiterleiter - tor stellt einen auf localhost bereit, und so werden normale anwendungen durch das tor-netzwerk geschleust.

socks5 is a bare-bones proxy protocol: an application connects to the proxy and says "forward this connection there", and the proxy relays raw tcp traffic without understanding it. no protocol-specific tricks, no headers rewritten - just plumbing.

the tor daemon speaks socks5, listening by default on 127.0.0.1:9050. that is the mechanism behind "route app x through tor": point the application's proxy setting at that address and its connections enter the tor network. the tor browser bundles its own tor instance on a different port and handles this internally.

two classic footguns deserve warnings. first, dns: an application that resolves hostnames through your normal resolver despite proxied traffic has leaked every site you visit before any proxy helps - configure remote dns resolution (socks5h behavior) or stick to apps that handle it. second, a random commercial "anonymous socks5" bought from a panel gives you a shift of ip address and zero anonymity - the operator sees everything and can sell logs.

rule of thumb: localhost socks5 pointing at tor is a building block; remote paid socks5 is a liability. if an app needs tor and lacks proxy support, torsocks-style wrappers force the issue.