summaryrefslogtreecommitdiff
path: root/doc/TODO.021
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2008-12-27 07:28:47 +0000
committerRoger Dingledine <arma@torproject.org>2008-12-27 07:28:47 +0000
commit43c22c5b7970ed441b2b4a22395ffd2e87b00c58 (patch)
treeb329d4fe430c825a7df3c33433dcd880df080273 /doc/TODO.021
parent5519e633ec4c48c5e547554ff750db1aab835cc7 (diff)
downloadtor-43c22c5b7970ed441b2b4a22395ffd2e87b00c58.tar.gz
tor-43c22c5b7970ed441b2b4a22395ffd2e87b00c58.zip
minor todo updates
svn:r17797
Diffstat (limited to 'doc/TODO.021')
-rw-r--r--doc/TODO.02114
1 files changed, 8 insertions, 6 deletions
diff --git a/doc/TODO.021 b/doc/TODO.021
index 77d494718b..b86940727a 100644
--- a/doc/TODO.021
+++ b/doc/TODO.021
@@ -105,10 +105,6 @@ Bugs/issues for Tor 0.2.0.x:
o Basic implementation
N - Include probability-of-selection
R d let bridges set relaybandwidthrate as low as 5kb
-R - bridge communities
- . spec
- . deploy
- - man page entries for Alternate*Authority config options
Documentation for Tor 0.2.0.x:
o Proposals:
@@ -305,6 +301,8 @@ P - create a "make win32-bundle" for vidalia-privoxy-tor-torbutton bundle
- can we deprecate 'getinfo network-status'?
- Dump most uint32_t addr functions.
+ - do the part of the "abandon .exit" proposal that involves isolating
+ circuits which have used a .exit stream from those that haven't
Defer:
- Proposals
@@ -318,12 +316,15 @@ Defer:
- Proposals to write.
d Something for bug 469, to limit connections per IP.
-R d Do we want to maintain our own set of entryguards that we use as
+ d Do we want to maintain our own set of entryguards that we use as
next hop after the bridge?
d Possibly: revise link protocol to allow big circuit IDs,
variable-length cells, proposal-110 stuff, and versioned CREATES?
d Fetch an updated geoip file from the directory authorities.
-
+R - bridge communities (revive proposal 128)
+ . spec
+ . deploy
+ - man page entries for Alternate*Authority config options
- Tiny designs to write
- Better estimate of clock skew; has anonymity implications. Clients
@@ -384,3 +385,4 @@ R d Do we want to maintain our own set of entryguards that we use as
d Interface for letting SOAT modify flags that authorities assign.
(How to keep the authority from clobbering them afterwards?
+