What steps will reproduce the problem?
1. Proxy server configured and working correctly for torrent metadata between
daemon & client
2. Reverse DNS lookups (for the Hostname field of the Peers tab) are resolved
on the client (via my PC's internet connection) without being tunneled through
the proxy server
3. DNS queries leak peer information and reveal bittorrent behavior
What is the expected output? What do you see instead?
Expected: DNS queries are resolved from the remote endpoint of the proxy server
Reality: DNS queries are resolved from the client (my PC) without going through
the proxy connection
What version of the products are you using?
OS: Windows 7
Transmission: 2.80-2 (build XXXX)
Remote: 3.24 (build 3)
Please provide any additional information below. Feel free to
attach screenshots or sample code which demonstrates the issue being
described.
The DNS queries reveal peer identities to corporate network monitors, ISPs,
authoritarian governments, etc. DNS query swarms are also indicative of
bittorrent usage. Additionally, it would be computationally possible to
identify the likely torrent of the connected swarm via a peer list. Only a few
governments would have the juice to do that, but we now know who they are at
this point. If impossible to tunnel the traffic through the proxy server,
please offer an option to disable reverse dns lookup (hostname resolution).
Original issue reported on code.google.com by ericsoll...@gmail.com on 6 Jul 2013 at 4:05
Original issue reported on code.google.com by
ericsoll...@gmail.comon 6 Jul 2013 at 4:05