[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
(FWD) Re: Whitedust article
[Forwarding because our good friend Mixminion isn't on the
list either. Tor is already tackling the below problems, though
we're not currently aiming to defeat a China-level adversary:
----- Forwarded message from owner-or-talk@xxxxxxxxxxxxx -----
Subject: Re: Whitedust article
Date: Tue, 13 Dec 2005 07:06:17 +0100 (CET)
This is a Type III anonymous message, sent to you by the Mixminion
server at mercurio.mixmaster.it. If you do not want to receive
anonymous messages, please contact mercurio-admin@xxxxxxxxxxxx
-----BEGIN TYPE III ANONYMOUS MESSAGE-----
In <439E4FFA.5040600@xxxxxxxxx> Void Beast <daemonik.dragon@xxxxxxxxx> wrote:
>-----BEGIN PGP SIGNED MESSAGE-----
>Ok, so we should place rules of some kind...
>So who should police these rules and how should they be impemented?
>Many people have different configurations so the rules may be different for
>So we should perhaps rely on ourselves to impose our own rules? But then,
>will that cause outsiders to look upon tor as unregulated and therefore
>This is interesting so far... Who else has an idea?
Network admins DO have legit concerns about people abusing both Tor and their
systems, however as I understand it from the Tor website, Tor's primary goal
is functional anonymity that can protect people in harsh circumstances. One
good example is that people are using things like Tor and Freenet to get
information through the Bamboo Firewall of China. In order to remain effective,
Tor must remain able to function in spite of people attempting to shut it down
or block it.
I think my ideas are reletively simple concepts:
1 Encourage more node operators to become directory servers.
(this one's a no-brainer)
2 Add (unless it's already there) an ability to have Tor use an
'accessible' port like 80 or 443 to contact directory servers instead of
the default port that people trying to stop Tor will likely be watching.
3 Implement decentralized directory functions. Take a page from Freenet
and let the client attempt to get directory info from any node it is able
to contact. Even if each node can only tell about the ones that it has
contacted, it shouldn't take long for Tor to build enough directory info
to allow it to route to a full directory server through the network.
combined with the use of a separatly downloadable file similar to the freenet
seednode.ref, a current copy of which would be included in the installer
along with directons for getting a fresh one from a Tor website if it's
-----END TYPE III ANONYMOUS MESSAGE-----
----- End forwarded message -----