TODO 6.6 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150
  1. Legend:
  2. SPEC!! - Not specified
  3. SPEC - Spec not finalized
  4. NICK - nick claims
  5. ARMA - arma claims
  6. - Not done
  7. * Top priority
  8. . Partially done
  9. o Done
  10. D Deferred
  11. X Abandoned
  12. . Use a stronger cipher
  13. o 3des for now
  14. - aes when we everybody has openssl 0.9.7
  15. . Topics / circuits
  16. o Implement topics
  17. o Rotate circuits after N minutes?
  18. X Circuits should expire when circuit->expire triggers
  19. NICK . Handle half-open connections
  20. - Figure out what causes connections to close, standardize
  21. when we mark a connection vs when we tear it down
  22. o Look at what ssl does to keep from mutating data streams
  23. X On the fly compression of each stream
  24. o Clean up the event loop (optimize and sanitize)
  25. ARMA o Remove that awful concept of 'roles'
  26. ARMA . Exit policies
  27. o Spec how to write the exit policies
  28. - Path selection algorithms
  29. - Let user request certain nodes
  30. - And disallow certain nodes
  31. D Choose path by jurisdiction, etc?
  32. - Rewrite how the AP works
  33. SPEC!! D Non-clique topologies
  34. D Implement our own memory management, at least for common structs
  35. . Appropriate logging
  36. - Come up with convention for what log level means what
  37. - Make code follow convention
  38. o Terminology
  39. o Circuits, topics, cells stay named that
  40. o 'Connection' gets divided, or renamed, or something?
  41. . DNS farm
  42. o Distribute queries onto the farm, get answers
  43. o Preemptively grow a new worker before he's needed
  44. - Prune workers when too many are idle
  45. - DNS cache
  46. - Clear DNS cache over time
  47. - Honor DNS TTL info
  48. - Have strategy when all workers are busy
  49. o Keep track of which connections are in dns_wait
  50. o Need to cache positives/negatives on the tor side
  51. o Keep track of which queries have been asked
  52. . Better error handling when
  53. . An address doesn't resolve
  54. - We have max workers running
  55. - Consider taking the master out of the loop?
  56. . Directory servers
  57. D Automated reputation management
  58. . Include key in source; sign directories
  59. o Signed directory backend
  60. o Document
  61. ARMA - Integrate
  62. - Add versions to code
  63. NICK . Have directories list recommended-versions
  64. o Include (unused) line in directories
  65. o Check for presence of line.
  66. - Quit if running the wrong version
  67. - Command-line option to override quit
  68. . Add more information to directory server entries
  69. o Exit policies
  70. D jurisdiction? others?
  71. SPEC!! D Figure out how to do threshold directory servers
  72. . Scrubbing proxies
  73. - Find an smtp proxy?
  74. - Check the old smtp proxy code
  75. o Find an ftp proxy? wget --passive
  76. D Wait until there are packet redirectors for Linux
  77. . Get socks4a support into Mozilla
  78. . Get tor to act like a socks server
  79. o socks4, socks4a
  80. - socks5
  81. SPEC!! - Handle socks commands other than connect, eg, bind?
  82. - Develop rendezvous points
  83. D Implement reply onions
  84. D Deploy and manage open source development site.
  85. . Documentation
  86. o Discussion of socks, tsocks, etc
  87. o On-the-network protocol
  88. o Onions
  89. o Cells
  90. . Better comments for functions!
  91. - Tests
  92. o Testing harness/infrastructure
  93. NICK . Unit tests
  94. D System tests (how?)
  95. - Performance tests, so we know when we've improved
  96. . webload infrastructure (Bruce)
  97. . httperf infrastructure (easy to set up)
  98. . oprofile (installed in RH 8.0)
  99. D Deploy a widespread network
  100. . Router twins
  101. o Choose twin if primary is down, when laying circuit
  102. D Load balancing between twins
  103. - Keep track of load over links/nodes, to
  104. know who's hosed
  105. NICK - Daemonize and package
  106. o Teach it to fork and background
  107. - Red Hat spec file
  108. - Debian spec file equivalent
  109. . Autoconf
  110. . Which .h files are we actually using? Port to:
  111. o Linux
  112. o BSD
  113. . Solaris
  114. . Windows
  115. NICK . OS X
  116. - openssl randomness
  117. - inet_ntoa, stdint.h
  118. - Make a script to set up a local network on your machine
  119. D Move away from openssl
  120. o Abstract out crypto calls
  121. D Look at nss, others? Just include code?
  122. . transition addr to sin_addr (huh?)
  123. . Clean up the number of places that get to look at prkey
  124. . Clearer bandwidth management
  125. - Total rate limiting
  126. . Look at OR handshake in more detail
  127. o Spec it
  128. o Merge OR and OP handshakes
  129. - rearrange connection_or so it doesn't suck so much to read
  130. D Periodic link key rotation. Spec?
  131. - More flexibility in node addressing
  132. D Support IPv6 rather than just 4
  133. - Handle multihomed servers (config variable to set IP)
  134. . Move from onions to ephemeral DH
  135. o incremental path building
  136. o transition circuit-level sendmes to hop-level sendmes
  137. - implement truncate, truncated
  138. o move from 192byte DH to 128byte DH, so it isn't so damn slow
  139. - exiting from not-last hop
  140. - OP logic to decide to extend/truncate a path
  141. - make sure exiting from the not-last hop works
  142. - logic to find last *open* hop, not last hop, in cpath
  143. - choose exit nodes by exit policies
  144. o wrap malloc with something that explodes when it fails