aboutsummaryrefslogtreecommitdiff
path: root/doc/TODO.future
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2009-01-06 03:57:06 +0000
committerRoger Dingledine <arma@torproject.org>2009-01-06 03:57:06 +0000
commit55665f25e58981022667115e8fc9778e54cf0ea3 (patch)
tree7d731cc29b9f6057c08837baba90382ac6cfffd3 /doc/TODO.future
parentf772fc0c36578e61e01f8d54c95415554d5ef892 (diff)
downloadtor-55665f25e58981022667115e8fc9778e54cf0ea3.tar.gz
tor-55665f25e58981022667115e8fc9778e54cf0ea3.zip
the new alpha release is coming out this week sometime. too many
bugs fixed to keep waiting. i still need to track down bug 709 first though, since i am increasingly thinking it's a real bug. svn:r17944
Diffstat (limited to 'doc/TODO.future')
-rw-r--r--doc/TODO.future2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/TODO.future b/doc/TODO.future
index 8b5decd0d0..77c9a3c4b1 100644
--- a/doc/TODO.future
+++ b/doc/TODO.future
@@ -49,7 +49,7 @@ 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
+ - We should get smarter about handling 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