aboutsummaryrefslogtreecommitdiff
path: root/doc/TODO.future
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2009-01-05 20:52:14 +0000
committerNick Mathewson <nickm@torproject.org>2009-01-05 20:52:14 +0000
commitf772fc0c36578e61e01f8d54c95415554d5ef892 (patch)
tree6e49e10e1ec83e3e9b2e860839857706bfd2a51c /doc/TODO.future
parente3388230c4c02c3fd83e38a87785ae815851578c (diff)
downloadtor-f772fc0c36578e61e01f8d54c95415554d5ef892.tar
tor-f772fc0c36578e61e01f8d54c95415554d5ef892.tar.gz
apply a variant of rovv's bug 872 patch, and document that we want a better solution for 0.2.2.x.
svn:r17924
Diffstat (limited to 'doc/TODO.future')
-rw-r--r--doc/TODO.future7
1 files changed, 7 insertions, 0 deletions
diff --git a/doc/TODO.future b/doc/TODO.future
index eaebde594..8b5decd0d 100644
--- a/doc/TODO.future
+++ b/doc/TODO.future
@@ -49,6 +49,13 @@ Later, unless people want to implement them now:
- 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 handkling address resolve failures, or
+ addresses that resolve to local IPs. It would be neat to retry
+ them, since right now we just close the stream. But we need to
+ make sure we don't retry them on the same exit as before. But if
+ we mark the circuit, then any user who types "localhost" will
+ cycle through circuits till they run out of retries. See bug 872.
+
Can anybody remember why we wanted to do this and/or what it means?
- config option __ControllerLimit that hangs up if there are a limit
of controller connections already.