Commit 01718369 authored by Roger Dingledine's avatar Roger Dingledine
Browse files

take some items off the todo


svn:r4005
parent f1edeebf
Loading
Loading
Loading
Loading
+5 −7
Changes for doc/TODO: 5 added lines, 7 removed lines.
Original line number Diff line number Diff line
@@ -152,14 +152,13 @@ N . Make logs go into platform default locations.
    - Windows. (?)

 Correctness
   - Mark bugs for 010 or post 010 in bugtracker.
   - Bugfixes
R    - when we haven't explicitly sent a socks reject, sending one in
   o Bugfixes
     o when we haven't explicitly sent a socks reject, sending one in
       connection_about_to_close_connection() fails because we never give it
       a chance to flush. right answer is to do the socks reply manually in
       each appropriate case, and then about-to-close-connection can simply
       warn us if we forgot one. [Tag this 010 in flyspray.]
R    - should retry exitpolicy end streams even if the end cell didn't
     o should retry exitpolicy end streams even if the end cell didn't
       resolve the address for you
   o Figure out when to reset addressmaps (on hup, on reconfig, etc)
   - how do ulimits work on win32, anyway?  (We should handle WSAENOBUFS as
@@ -178,7 +177,6 @@ R o client software not upload descriptor until:
     o start counting again if your IP ever changes.
     o never regenerate identity keys, for now.
     o you can set a bit for not-being-an-OR.
       * no need to do this yet. few people define their ORPort.

 Arguable
N - tor-resolve script should use socks5 to get better error messages.
@@ -204,8 +202,8 @@ N - Code cleanup
    - Write limiting; configurable token buckets.
    - Make it harder to circumvent bandwidth caps: look at number of bytes
      sent across sockets, not number sent inside TLS stream.
  - Hidden service improvements
    - Investigate hidden service performance/reliability
  o Hidden service improvements
    o Investigate hidden service performance/reliability
  - Add private:* alias in exit policies to make it easier to ban all the
    fiddly little 192.168.foo addresses.
  - controller should have an event to learn about new addressmappings?