[or-cvs] take some items off the todo

[Roger Dingledine]

Update of /home2/or/cvsroot/tor/doc
In directory moria.mit.edu:/home2/arma/work/onion/cvs/tor/doc

Modified Files:
	TODO 
Log Message:
take some items off the todo


Index: TODO
===================================================================
RCS file: /home2/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.297
retrieving revision 1.298
diff -u -d -r1.297 -r1.298
--- TODO	1 Apr 2005 07:04:40 -0000	1.297
+++ TODO	4 Apr 2005 04:09:34 -0000	1.298
@@ -152,14 +152,13 @@
     - 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 @@
      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 @@
     - 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?