[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[or-cvs] r8631: a new research problem our weight_for_exit algorithm has int (tor/trunk/doc)
- To: or-cvs@xxxxxxxxxxxxx
- Subject: [or-cvs] r8631: a new research problem our weight_for_exit algorithm has int (tor/trunk/doc)
- From: arma@xxxxxxxx
- Date: Sat, 7 Oct 2006 02:30:49 -0400 (EDT)
- Delivered-to: archiver@seul.org
- Delivered-to: or-cvs-outgoing@seul.org
- Delivered-to: or-cvs@seul.org
- Delivery-date: Sat, 07 Oct 2006 02:30:56 -0400
- Reply-to: or-talk@xxxxxxxxxxxxx
- Sender: owner-or-cvs@xxxxxxxxxxxxx
Author: arma
Date: 2006-10-07 02:30:48 -0400 (Sat, 07 Oct 2006)
New Revision: 8631
Modified:
tor/trunk/doc/TODO
Log:
a new research problem our weight_for_exit algorithm has introduced.
Modified: tor/trunk/doc/TODO
===================================================================
--- tor/trunk/doc/TODO 2006-10-07 06:28:50 UTC (rev 8630)
+++ tor/trunk/doc/TODO 2006-10-07 06:30:48 UTC (rev 8631)
@@ -76,6 +76,12 @@
P - Figure out why openssl 0.9.8c "make test" fails at sha256t test.
Items for 0.1.2.x:
+ - Now that we're avoiding exits when picking non-exit positions,
+ we need to consider how to pick nodes for internal circuits. If
+ we avoid exits for all positions, we skew the load balancig. If
+ we accept exits for all positions, we leak whether it's an internal
+ circuit at every step. If we accept exits only at the last hop, we
+ reintroduce Lasse's attacks from the Oakland paper.
o re-enable blossom functionality: let tor servers decide if they
will use local search when resolving, or not.
o Document it.