summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2008-03-04 07:46:44 +0000
committerRoger Dingledine <arma@torproject.org>2008-03-04 07:46:44 +0000
commit7dca2292900f18c8ad0cd55f67d4ba843caedb0e (patch)
treed6b7855226eb9968b858abd928f88e86b8b1465c
parenteffdec39740836a413d47c67e7ffad0b9c556287 (diff)
downloadtor-7dca2292900f18c8ad0cd55f67d4ba843caedb0e.tar.gz
tor-7dca2292900f18c8ad0cd55f67d4ba843caedb0e.zip
and move another item up two months, but try to make it easier to
be sure to finish svn:r13848
-rw-r--r--doc/TODO10
1 files changed, 6 insertions, 4 deletions
diff --git a/doc/TODO b/doc/TODO
index 9a4d879f45..10b288a955 100644
--- a/doc/TODO
+++ b/doc/TODO
@@ -59,6 +59,10 @@ N - Investigate and start resolving (or declare unresolvable) the ram
o better buffer approaches in Tor
- better buffer approaches in openssl
- shipping Tor with its own integrated allocator.
+N - Write a draft research proposal for how to safely collect and
+ aggregate some GeoIP data from non-bridge entry nodes, or conclude
+ that we don't know how to do it safely while still being useful
+ and explain why.
- Mid May
S - More TorBrowser work
@@ -88,10 +92,8 @@ NR - Include "stable" bridge and "port 443" bridge and "adequately
box!^W^W^Woutput batch.
N - Detect proxies and treat them as the same address
- More back-end work:
-N - Write a research proposal for how to safely collect and aggregate
- some GeoIP data from non-bridge entry nodes. Deploy that if we
- think it's safe enough, or produce a clear roadmap to getting it
- safe if we don't think it's ready yet.
+N - If we decided above that we know how to collect geoip data for
+ non bridge relays, deploy that plan.
N - Additional TLS-camouflage work (spoofing FF cipher suite, etc.)
- spoof the cipher suites
- spoof the extensions list