[or-cvs] Mark a few bugs as done or as nonstarters

[nickm@xxxxxxxx (Nick Mathewson)]

Update of /home/or/cvsroot/tor/doc
In directory moria:/tmp/cvs-serv27131/doc

Modified Files:
	TODO 
Log Message:
Mark a few bugs as done or as nonstarters

Index: TODO
===================================================================
RCS file: /home/or/cvsroot/tor/doc/TODO,v
retrieving revision 1.329
retrieving revision 1.330
diff -u -d -r1.329 -r1.330
--- TODO	29 Jun 2005 21:51:30 -0000	1.329
+++ TODO	30 Jun 2005 07:19:20 -0000	1.330
@@ -104,8 +104,9 @@
         o Look for v1 descriptor if available, else look for v0 descriptor.
         o Use new INTRODUCE protocol if allowed.
     . Verify that new code works.
-  - it looks like tor_assert writes to stderr. what happens if
-    stderr was closed and is now something else? uh.
+  X It looks like tor_assert writes to stderr. This isn't a problem, because
+    start_daemon doesn't close fd 2; it uses dup2 to replace it with
+    a file open to /dev/null.
   - christian grothoff's attack of infinite-length circuit.
     the solution is to have a separate 'extend-data' cell type
     which is used for the first N data cells, and only
@@ -118,8 +119,8 @@
     (AGL had a patch; consider applying it.)
   - recommended-versions for client / server ?
   - warn if listening for SOCKS on public IP.
-  - Forward-compatibility: add "needclientversion" option or "opt critical"
-    prefix.
+  o Forward-compatibility: add "needclientversion" option or "opt critical"
+    prefix?  No, just make unknown keywords less critical.
   - cpu fixes:
     - see if we should make use of truncate to retry
     o hardware accelerator support (configure engines.)