Skip to Content.
Sympa Menu

discuss - Re: [opennic-discuss] TOR and OpenNIC

discuss AT lists.opennicproject.org

Subject: Discuss mailing list

List archive

Re: [opennic-discuss] TOR and OpenNIC


Chronological Thread 
  • From: The Doctor <drwho AT virtadpt.net>
  • To: discuss AT lists.opennicproject.org
  • Subject: Re: [opennic-discuss] TOR and OpenNIC
  • Date: Wed, 19 Sep 2012 15:01:05 -0400
  • Openpgp: id=807B17C1
  • Organization: Virtual Adept Networks, Unlimited

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 09/18/2012 07:27 PM, Peter Green wrote:

> What I would prefer is that the application/s that route through
> the TOR network would route my D.N.S. requests to the servers in
> my resolve.conf and return the results for my browser (or other
> app) to access the correct I.P. again through the TOR network.

The problem there is the following scenario:

0) Your workstation queries a DNS listed in your /etc/resolv.conf
file. Let's say you're trying to access i-love-hamsters.ing.
1) Traffic leaves your workstation in the clear, hits your ISP's
infrastructure, and DNS resolution proceeds apace.
2).0 Your ISPs is recording your traffic due to mandatory data
retention laws and notes that you are attempting to resolve
i-love-hamsters.ing.
2).1 Your ISP also records the fact that there is Tor traffic coming
from the IP address they assigned you.
2).2 These two facts are correlated, and they now know you're using
Tor to access i-love-hamsters.ing. You're branched.
2).3 They hand over their records to a LEO, and you're now a person of
interest because you're visiting a website with a potentially
embarrassing domain name. Oops.

> It seems there's two basic problems. 1)TOR insisting on using the

As I understand it, this is by design. By requiring the exit nodes to
perform DNS resolution on behalf of clients, the user's local ISP is
no longer in a position to know what you're resolving (i.e., browsing,
participating in). All of the DNS resolution requests match all of
the traffic traversing the exit node, but there is no way of knowing
who initiated the traffic or where they are.

> exit nodes resolvers and 2)local apps not working in a secure way,

That actually comes from the developers not adding SOCKS 5 support
correctly (or only implementing SOCKS 4a support).

- --
The Doctor [412/724/301/703] [ZS]
Developer, Project Byzantium: http://project-byzantium.org/

PGP: 0x807B17C1 / 7960 1CDC 85C9 0B63 8D9F DD89 3BD8 FF2B 807B 17C1
WWW: https://drwho.virtadpt.net/

"So light your candles, and may SERVER protect us all." --Sean Kennedy VI

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAlBaFnEACgkQO9j/K4B7F8EElwCcC5s3cUnj/kajv6WNShEJYE+9
I94AnjFBXTXtdV3pS2eZ7BegU2EUURKP
=oznd
-----END PGP SIGNATURE-----



Archive powered by MHonArc 2.6.19.

Top of Page