TODO 4.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117
  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. - 3des for now
  14. - aes when we everybody has openssl 0.9.7
  15. . Topics / circuits
  16. o Implement topics
  17. - Rotate circuits after N minutes?
  18. - Circuits should expire when circuit->expire triggers
  19. NICK . Handle half-open connections
  20. NICK . On the fly compression of each stream
  21. o Clean up the event loop (optimize and sanitize)
  22. - Exit policies
  23. - Path selection algorithms
  24. - Let user request certain nodes
  25. - And disallow certain nodes
  26. - Choose path by jurisdiction, etc?
  27. D Implement our own memory management, at least for common structs
  28. . Appropriate logging
  29. - Come up with convention for what log level means what
  30. - Make code follow convention
  31. . Terminology
  32. o Circuits, topics, cells stay named that
  33. - 'Connection' gets divided, or renamed, or something?
  34. . DNS farm
  35. o Distribute queries onto the farm, get answers
  36. o Preemptively grow a new worker before he's needed
  37. - Prune workers when too many are idle
  38. o Keep track of which connections are in dns_wait
  39. o Need to cache positives/negatives on the tor side
  40. o Keep track of which queries have been asked
  41. . Better error handling when
  42. . An address doesn't resolve
  43. - We have max workers running
  44. - Consider taking the master out of the loop?
  45. . Directory servers
  46. - Automated reputation management
  47. ARMA - Include key in source; sign directories
  48. ARMA - Have directories list recommended-versions
  49. - Quit if running the wrong version
  50. - Command-line option to override quit
  51. . Add more information to directory server entries
  52. - Exit policies
  53. - jurisdiction? others?
  54. SPEC!! - Figure out how to do threshold directory servers
  55. . Scrubbing proxies
  56. - Find an smtp proxy?
  57. - Find an ftp proxy? Figure out how that would work?
  58. - Wait until there are packet redirectors for Linux
  59. . Get socks4a support into Mozilla
  60. . Get tor to act like a socks server
  61. o socks4, socks4a
  62. - socks5
  63. SPEC!! - Handle socks commands other than connect, eg, bind?
  64. - Develop rendezvous points
  65. D Implement reply onions
  66. D Deploy and manage open source development site.
  67. . Documentation
  68. . Discussion of socks, tsocks, etc
  69. - On-the-network protocol
  70. - Onions
  71. - Cells
  72. . Better comments for functions!
  73. - Tests
  74. - Testing harness/infrastructure
  75. - Unit tests
  76. - System tests (how?)
  77. - Performance tests, so we know when we've improved
  78. . webload infrastructure (Bruce)
  79. . httperf infrastructure (easy to set up)
  80. . oprofile (installed in RH 8.0)
  81. D Deploy a widespread network
  82. . Router twins
  83. o Choose twin if primary is down, when laying circuit
  84. - Load balancing between twins
  85. - Keep track of load over links/nodes, to
  86. know who's hosed
  87. NICK - Daemonize and package
  88. o Teach it to fork and background
  89. - Red Hat spec file
  90. - Debian spec file equivalent
  91. . Autoconf
  92. . Which .h files are we actually using? Port to:
  93. o Linux
  94. o BSD
  95. . Solaris
  96. . Windows
  97. NICK . OS X
  98. . Move away from openssl
  99. o Abstract out crypto calls
  100. D Look at ndss, others? Just include code?
  101. . transition addr to sin_addr (huh?)
  102. . Clean up the number of places that get to look at prkey
  103. SPEC!! - Non-clique topologies, clearer bandwidth management
  104. . Look at OR handshake in more detail
  105. o Spec it
  106. - Merge OR and OP handshakes?
  107. - Periodic link key rotation. Spec?
  108. - More flexibility in node addressing
  109. - Support IPv6 rather than just 4
  110. - Handle multihomed servers