summaryrefslogtreecommitdiff
path: root/doc/TODO.future
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2010-07-06 18:10:53 -0400
committerNick Mathewson <nickm@torproject.org>2010-07-06 18:10:53 -0400
commitf72c6f91deed6b076fd730d049c3bddbbb3eb329 (patch)
tree40774a32eddf909b135001a962f90e55d50d61fd /doc/TODO.future
parenta9edb0b4f67825a11647c8faefa613d704be44ae (diff)
downloadtor-f72c6f91deed6b076fd730d049c3bddbbb3eb329.tar.gz
tor-f72c6f91deed6b076fd730d049c3bddbbb3eb329.zip
Remove TODO items that are either done or moved to the tracker
Diffstat (limited to 'doc/TODO.future')
-rw-r--r--doc/TODO.future7
1 files changed, 0 insertions, 7 deletions
diff --git a/doc/TODO.future b/doc/TODO.future
index 4220799574..85e07aa921 100644
--- a/doc/TODO.future
+++ b/doc/TODO.future
@@ -22,7 +22,6 @@ K - Karsten claims
=======================================================================
Later, unless people want to implement them now:
- - tor as a socks proxy should accept (and ignore) password auth
- Actually use SSL_shutdown to close our TLS connections.
- Include "v" line in networkstatus getinfo values.
[Nick: bridge authorities output a networkstatus that is missing
@@ -30,10 +29,6 @@ Later, unless people want to implement them now:
bridgedb gives out bridges with certain characteristics. -RD]
[Okay. Is this a separate item, or is it the same issue as the lack of
a "v" line in response to the controller GETINFO command? -NM]
- - Let tor dir mirrors proxy connections to the tor download site, so
- if you know a bridge you can fetch the tor software.
- - when somebody uses the controlport as an http proxy, give them
- a "tor isn't an http proxy" error too like we do for the socks port.
- MAYBE kill stalled circuits rather than stalled connections. This is
possible thanks to cell queues, but we need to consider the anonymity
implications.
@@ -45,8 +40,6 @@ Later, unless people want to implement them now:
online config documentation from a single source.
- It would be potentially helpful to respond to https requests on
the OR port by acting like an HTTPS server.
- - Make the timestamp granularity on logs configurable, with default
- of "1 second". This might make some kinds of after-the-fact attack harder.
- We should get smarter about handling address resolve failures, or
addresses that resolve to local IPs. It would be neat to retry