Continuing the discussion from Persistent Tor Entry Guard Relays can make you trackable Across Different Physical Locations:
That statement comes from the following page:
I see, that statement needs some refinement.
- “We are not aware of any http(s) or socks4(a)/5 proxies that offer an encrypted connection between itself and the user.” - Strictly speaking this is true. And this matters if http(s) or socks4(a)/5 runs on remote locations.
- There are however local clients that suggest using http(s) or socks4(a)/5 as local interface. Such clients include Tor, i2p, JonDo, others and perhaps also some of the ones you pointed out.
- Not sure we should call those still “proxy”? That term is over used. Can we somehow distinguish simple remote http(s) or socks4(a)/5 proxies and those using that as local interface only and then use custom encrypted transports?