[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
FEATURE IDEA: Hidden Directory Authorities
- To: or-dev@xxxxxxxx, or-dev@xxxxxxxxxxxxx
- Subject: FEATURE IDEA: Hidden Directory Authorities
- From: "Kyle Williams" <kyle.kwilliams@xxxxxxxxx>
- Date: Mon, 19 Nov 2007 00:29:53 -0800
- Delivered-to: archiver@xxxxxxxx
- Delivered-to: or-dev-outgoing@xxxxxxxx
- Delivered-to: or-dev@xxxxxxxx
- Delivery-date: Mon, 19 Nov 2007 03:30:03 -0500
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; bh=F6f2zbPXbgOe+fpFMeQVPueYZOq0HrLjcb83wLqo8k4=; b=s9jX3I4m9q4eLqQLE2JfZ8IqXOJDmJhCGucBSONsf7uJwSGO0ihtEf6TJoGNm1RpUWPR/5ihcOA8DW5ogXZ+aS9BqwXs7/YqxecW4WqwquyKWBN44GaH6BarpHNgZ0Ihg6eG2uPHe9YoEV2ziEq4TcL58mmq5nq3oi7YKnR9mV0=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=hMguiIIK6xMshy3QrUPOfIKyBMfKbuGcxidw/MdcWH2XaiUWSJfr4c0RzhZDyoGo1TCSdSmQp7b++DwJIsrBCo8sSg6dc/E600AfCVA/JZDmkrz+lJeLppwIlCjb9Px2Pbcy+1ZuI1f94zxX9IqBMwkchMIAqL7F0mwK7eMOeco=
- Reply-to: or-dev@xxxxxxxxxxxxx
- Sender: owner-or-dev@xxxxxxxxxxxxx
Any suggestions, questions, or comments are encouraged.
I know that Tor has the PrivateDir option, which uses an Onion Router
to make the request to the DA to retrieve updated cached-* documents.
However, this option will not
function without a pre-cached copy of the cached-routers documents
because it wouldn't know of an Onion Routers to tunnel the request
through.
Basically you need a pre-cached copy of cached-routers for PrivateDir
to work, right?
(Please correct me if I am wrong here.)
So the questions that entered my mind were:
* Could Directory Authorities use an .onion address instead of an IP
address if a pre-cached copy of cached-routers was distributed with
the initial download of Tor?
* Would this make the Directory Authorities more resistant to digital
& physical attack?
* Are "guard" nodes[2] the same as "valet" nodes[1]?
The wording of "guard" nodes [2] sounds very similar to the concept of
"valet" nodes [1], but I'm not quite sure if these are the same. Are
they?
Since the DAs would be the most logical place for an attacker to DoS
or attack, I was thinking that it would make sense if the DAs couldn't
be found physically or by IP.
To start a network, I was think of using 3 DAs with 8 nodes. The
nodes would act as rendezvous points, introduction points, valet/guard
points, entry, middle, and exit nodes.
If the DAs .onion information and 8 startup nodes information was
pre-cached when Tor is download, would that be enough to keep the DA's
hidden?
Now the big question. What type of attacks would this be prone to?
After reading [2], it became clear that someone could attack
Introduction Points to reveal the true location of the hidden service.
But the 'valet' (or 'guard'?) node design model would significantly
help reduce the probability of this attack being successful. So, if
the DA's are acting as a hidden service, in theory, Introduction and
Valet Points wouldn't be able to distinguish regular hidden services
from the DA's hidden service.
I know that by hiding the DA's, every downloaded package of Tor would
have to contain an up-to-date copy of the cached-routers. Could a
"cached-onions" file be introduced into the design to make it clear
which are Onion Routers and which are Hidden Services?
This idea was something that been going through my mind the last few
weeks. What do you think?
Paul, if you're reading this, I would really like to hear what you
think about this.
Any feedback from anyone is appreciated.
Best Regards,
Kyle
-------------------------------------------------------------------------------------
References:
[1] Making Anonymous Communications
( http://www.onion-router.net/Publications/Briefing-2004.pdf )
[2] Locating Hidden Servers
( http://www.onion-router.net/Publications/locating-hidden-servers.pdf )