TODO 13 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314
  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. For 0.0.9:
  13. o Solve the MSVC nuisance where __FILE__ contains the full path.
  14. People are getting confused about why their errors are coming from
  15. C:\Documents and Settings\Nick Mathewson\My Documents\src\tor .
  16. N&R. bring tor-spec up to date
  17. N&R. make loglevels info,debug less noisy
  18. N . OS X package (and bundle?)
  19. N . Working RPMs
  20. N - Get win32 servers working, or find out why it isn't happening now.
  21. - Why can't win32 find a cpuworker?
  22. ************************ For Post 0.0.9 *****************************
  23. Tier one:
  24. o Move to our new version system.
  25. - Changes for forward compatibility
  26. - If a version is later than the last in its series, but a version
  27. in the next series is recommended, that doesn't mean it's bad.
  28. - Bugfixes
  29. - fix dfc/weasel's intro point bug
  30. - when we haven't explicitly sent a socks reject, sending one in
  31. connection_about_to_close_connection() fails because we never give it
  32. a chance to flush. right answer is to do the socks reply manually in
  33. each appropriate case, and then about-to-close-connection can simply
  34. warn us if we forgot one.
  35. - Documentation
  36. - Convert man pages to pod, or whatever's right. Alternatively, find
  37. a man2html that actually works.
  38. - Macintosh HOWTO page.
  39. - Evangelism
  40. - Get more nodes running on 80 and 443.
  41. - Get epic, aclu, etc running nodes.
  42. - Dirservers and server descs: small, backward-compatible changes
  43. - support hostnames as well as IPs for authdirservers.
  44. - If we have a trusted directory on port 80, stop falling back to
  45. forbidden ports when fascistfirewall blocks all good dirservers.
  46. - GPSLocation optional config string.
  47. - SOCKS enhancements
  48. - niels's "did it fail because conn refused or timeout or what"
  49. relay end feature.
  50. - Windows
  51. N - Make millisecond accuracy work on win32
  52. - Switch to WSA*Event code as a better poll replacement. Or maybe just
  53. do libevent?
  54. - Code cleanup
  55. - Make more configuration variables into CSVs.
  56. - Make configure.in handle cross-compilation
  57. - Have NULL_REP_IS_ZERO_BYTES default to 1.
  58. - Make with-ssl-dir disable search for ssl.
  59. - Support
  60. - Bug tracker.
  61. - Exit hostname support
  62. - cache .foo.exit names better, or differently, or not.
  63. - IPv6 support
  64. - teach connection_ap_handshake_socks_reply() about ipv6 and friends
  65. so connection_ap_handshake_socks_resolved() doesn't also need
  66. to know about them.
  67. - Packaging
  68. - Figure out how to make the rpm not strip the binaries it makes.
  69. Tier two:
  70. - Efficiency/speed improvements.
  71. - Handle pools of waiting circuits better.
  72. - Limit number of circuits that we preemptively generate based on past
  73. behavior; use same limits in circuit_expire_old_circuits().
  74. - Write limiting; configurable token buckets.
  75. - Switch to libevent? Evaluate it first.
  76. - Make it harder to circumvent bandwidth caps: look at number of bytes
  77. sent across sockets, not number sent inside TLS stream.
  78. - QOI
  79. - Let more config options (e.g. ORPort) change dynamically.
  80. - Dirservers and server descs: small, backward-compatible changes
  81. - make advertised_server_mode() ORs fetch dirs more often.
  82. - Implement If-Modified-Since for directories.
  83. - Big, incompatible re-architecting and decentralization of directory
  84. system.
  85. - Only the top of a directory needs to be signed.
  86. - Windows
  87. N - Clean up NT service code; make it work
  88. - Get a controller to launch tor and keep it on the system tray.
  89. - Win32 installer plus privoxy, sockscap/freecap, etc.
  90. - Controller enhancements.
  91. - controller should have 'getinfo' command to query about rephist,
  92. about rendezvous status, etc.
  93. N - Handle rendezvousing with unverified nodes.
  94. - Specify: Stick rendezvous point's key in INTRODUCE cell.
  95. Bob should _always_ use key from INTRODUCE cell.
  96. - Implement.
  97. N - IPv6 support (For exit addresses)
  98. - Spec issue: if a resolve returns an IP4 and an IP6 address,
  99. which to use?
  100. - Add to exit policy code
  101. - Make tor_gethostbyname into tor_getaddrinfo
  102. - Make everything that uses uint32_t as an IP address change to use
  103. a generalize address struct.
  104. - Change relay cell types to accept new addresses.
  105. - Add flag to serverdescs to tell whether IPv6 is supported.
  106. - When should servers
  107. - Security fixes
  108. - christian grothoff's attack of infinite-length circuit.
  109. the solution is to have a separate 'extend-data' cell type
  110. which is used for the first N data cells, and only
  111. extend-data cells can be extend requests.
  112. - Make sure logged information is 'safe'.
  113. - Code cleanup
  114. . rename/rearrange functions for what file they're in
  115. - fix router_get_by_* functions so they can get ourselves too,
  116. and audit everything to make sure rend and intro points are
  117. just as likely to be us as not.
  118. - Bugfixes
  119. - hidserv offerers shouldn't need to define a SocksPort
  120. * figure out what breaks for this, and do it.
  121. - should retry exitpolicy end streams even if the end cell didn't
  122. resolve the address for you
  123. - tor should be able to have a pool of outgoing IP addresses
  124. that it is able to rotate through. (maybe)
  125. Packaging, docs, etc:
  126. - Exit node caching: tie into squid or other caching web proxy.
  127. Deferred until needed:
  128. - Do something to prevent spurious EXTEND cells from making middleman
  129. nodes connect all over. Rate-limit failed connections, perhaps?
  130. - Limit to 2 dir, 2 OR, N SOCKS connections per IP.
  131. - Handle full buffers without totally borking
  132. * do this eventually, no rush.
  133. - Rate-limit OR and directory connections overall and per-IP and
  134. maybe per subnet.
  135. - DoS protection: TLS puzzles, public key ops, bandwidth exhaustion.
  136. - Have clients and dirservers preserve reputation info over
  137. reboots.
  138. - round detected bandwidth up to nearest 10KB?
  139. - client software not upload descriptor until:
  140. - you've been running for an hour
  141. - it's sufficiently satisfied with its bandwidth
  142. - it decides it is reachable
  143. - start counting again if your IP ever changes.
  144. - never regenerate identity keys, for now.
  145. - you can set a bit for not-being-an-OR.
  146. * no need to do this yet. few people define their ORPort.
  147. - authdirserver lists you as running iff:
  148. - he can connect to you
  149. - he has successfully extended to you
  150. - you have sufficient mean-time-between-failures
  151. * keep doing nothing for now.
  152. - Include HTTP status messages in logging (see parse_http_response).
  153. Blue sky or deferred indefinitely:
  154. - Support egd or other non-OS-integrated strong entropy sources
  155. - password protection for on-disk identity key
  156. - Possible to get autoconf to easily install things into ~/.tor?
  157. - server descriptor declares min log level, clients avoid servers
  158. that are too loggy.
  159. - put expiry date on onion-key, so people don't keep trying
  160. old ones that they could know are expired?
  161. - Add a notion of nickname->Pubkey binding that's not 'verification'
  162. - Conn key rotation.
  163. - Need a relay teardown cell, separate from one-way ends.
  164. Big tasks that would demonstrate progress:
  165. - Facility to automatically choose long-term helper nodes; perhaps
  166. on by default for hidden services.
  167. - patch privoxy and socks protocol to pass strings to the browser.
  168. - patch tsocks with our current patches + gethostbyname, getpeername, etc.
  169. - make freecap (or whichever) do what we want.
  170. - scrubbing proxies for protocols other than http.
  171. - Find an smtp proxy?
  172. . Get socks4a support into Mozilla
  173. N - Reverse DNS: specify and implement.
  174. - figure out enclaves, e.g. so we know what to recommend that people
  175. do, and so running a tor server on your website is helpful.
  176. - Do enclaves for same IP only.
  177. - Resolve first, then if IP is an OR, extend to him first.
  178. - implement a trivial fun gui to demonstrate our control interface.
  179. ************************ Roadmap for 2004-2005 **********************
  180. Hard problems that need to be solved:
  181. - Separating node discovery from routing.
  182. - Arranging membership management for independence.
  183. Sybil defenses without having a human bottleneck.
  184. How to gather random sample of nodes.
  185. How to handle nodelist recommendations.
  186. Consider incremental switches: a p2p tor with only 50 users has
  187. different anonymity properties than one with 10k users, and should
  188. be treated differently.
  189. - Measuring performance of other nodes. Measuring whether they're up.
  190. - Choosing exit node by meta-data, e.g. country.
  191. - Incentives to relay; incentives to exit.
  192. - Allowing dissidents to relay through Tor clients.
  193. - How to intercept, or not need to intercept, dns queries locally.
  194. - Improved anonymity:
  195. - Experiment with mid-latency systems. How do they impact usability,
  196. how do they impact safety?
  197. - Understand how powerful fingerprinting attacks are, and experiment
  198. with ways to foil them (long-range padding?).
  199. - Come up with practical approximations to picking entry and exit in
  200. different routing zones.
  201. - Find ideal churn rate for helper nodes; how safe is it?
  202. - What info squeaks by Privoxy? Are other scrubbers better?
  203. - Attacking freenet-gnunet/timing-delay-randomness-arguments.
  204. - Is abandoning the circuit the only option when an extend fails, or
  205. can we do something without impacting anonymity too much?
  206. - Is exiting from the middle of the circuit always a bad idea?
  207. Sample Publicity Landmarks:
  208. - we have N servers / N users
  209. - we have servers at epic and aclu and foo
  210. - hidden services are robust and fast
  211. - a more decentralized design
  212. - tor win32 installer works
  213. - win32 tray icon for end-users
  214. - tor server works on win32
  215. - win32 service for servers
  216. - mac installer works
  217. ***************************Future tasks:****************************
  218. Rendezvous and hidden services:
  219. make it fast:
  220. - preemptively build and start rendezvous circs.
  221. - preemptively build n-1 hops of intro circs?
  222. - cannibalize general circs?
  223. make it reliable:
  224. - standby/hotswap/redundant services.
  225. - store stuff to disk? dirservers forget service descriptors when
  226. they restart; nodes offering hidden services forget their chosen
  227. intro points when they restart.
  228. make it robust:
  229. - auth mechanisms to let midpoint and bob selectively choose
  230. connection requests.
  231. make it scalable:
  232. - robust decentralized storage for hidden service descriptors.
  233. make it accessible:
  234. - web proxy gateways to let normal people browse hidden services.
  235. Tor scalability:
  236. Relax clique assumptions.
  237. Redesign how directories are handled.
  238. - Resolve directory agreement somehow.
  239. Find and remove bottlenecks
  240. - Address linear searches on e.g. circuit and connection lists.
  241. Reputation/memory system, so dirservers can measure people,
  242. and so other people can verify their measurements.
  243. - Need to measure via relay, so it's not distinguishable.
  244. Let dissidents get to Tor servers via Tor users. ("Backbone model")
  245. Make it more correct:
  246. Handle half-open connections: right now we don't support all TCP
  247. streams, at least according to the protocol. But we handle all that
  248. we've seen in the wild.
  249. Support IPv6.
  250. Efficiency/speed/robustness:
  251. Congestion control. Is our current design sufficient once we have heavy
  252. use? Need to measure and tweak, or maybe overhaul.
  253. Allow small cells and large cells on the same network?
  254. Cell buffering and resending. This will allow us to handle broken
  255. circuits as long as the endpoints don't break, plus will allow
  256. connection (tls session key) rotation.
  257. Implement Morphmix, so we can compare its behavior, complexity, etc.
  258. Use cpuworker for more heavy lifting.
  259. - Signing (and verifying) hidserv descriptors
  260. - Signing (and verifying) intro/rend requests
  261. - Signing (and verifying) router descriptors
  262. - Signing (and verifying) directories
  263. - Doing TLS handshake (this is very hard to separate out, though)
  264. Buffer size pool: allocate a maximum size for all buffers, not
  265. a maximum size for each buffer. So we don't have to give up as
  266. quickly (and kill the thickpipe!) when there's congestion.
  267. Other transport. HTTP, udp, rdp, airhook, etc. May have to do our own
  268. link crypto, unless we can bully openssl into it.