summaryrefslogtreecommitdiff
path: root/doc/todo/tor.mdwn
diff options
context:
space:
mode:
authorGravatar Joey Hess <joeyh@joeyh.name>2016-12-09 13:38:50 -0400
committerGravatar Joey Hess <joeyh@joeyh.name>2016-12-09 13:38:50 -0400
commit94e91f857e9ae3522c31c3d2268475aeae45fdb3 (patch)
tree4e1f00e6c3f62067242ca8bc29c320ed94de8916 /doc/todo/tor.mdwn
parent6aac10c5215e822b2252897b777b41b97abbfb33 (diff)
update
Diffstat (limited to 'doc/todo/tor.mdwn')
-rw-r--r--doc/todo/tor.mdwn6
1 files changed, 2 insertions, 4 deletions
diff --git a/doc/todo/tor.mdwn b/doc/todo/tor.mdwn
index 11d441dab..0980fbaf5 100644
--- a/doc/todo/tor.mdwn
+++ b/doc/todo/tor.mdwn
@@ -4,16 +4,14 @@ Mostly working!
Current todo list:
-* Current use of hGetLine to read protocol messages allows memory DOS by
- sending a very long line. May also have line ending problems across OS's.
- Switch to instead reading a packed data structure that starts with its
- length, and refuse to read messages > 32k.
* When a transfer can't be done because another transfer of the same
object is already in progress, the message about this is output by the
remotedaemon --debug, but not forwarded to the peer, which shows
"Connection reset by peer"
* Think about locking some more. What happens if the connection to the peer
is dropped while we think we're locking content there from being dropped?
+* Make remotedaemon connect to tor peers, notice when their repos have
+ changed, and pull, like it does for ssh peers.
Eventually: