TODO 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286
  1. $Id$
  2. Legend:
  3. SPEC!! - Not specified
  4. SPEC - Spec not finalized
  5. N - nick claims
  6. R - arma claims
  7. P - phobos claims
  8. - Not done
  9. * Top priority
  10. . Partially done
  11. o Done
  12. D Deferred
  13. X Abandoned
  14. Non-Coding, Soon:
  15. N - Mark up spec; note unclear points about servers
  16. N - Mention controller libs someplace.
  17. D FAQ entry: why gnutls is bad/not good for tor
  18. P - flesh out the rest of the section 6 of the faq
  19. R . more pictures from ren. he wants to describe the tor handshake
  20. R - make a page with the hidden service diagrams.
  21. NR- write a spec appendix for 'being nice with tor'
  22. - tor-in-the-media page
  23. - Remove need for HACKING file.
  24. Website:
  25. - and remove home and make the "Tor" picture be the link to home.
  26. - put the logo on the website, in source form, so people can put it on
  27. stickers directly, etc.
  28. for 0.1.1.x-final:
  29. N - building on freebsd 6.0: (with multiple openssl installations)
  30. . <nickm> "Let's try to find a way to make it run and make the version
  31. match, but if not, let's just make it run."
  32. - <arma> should we detect if we have a --with-ssl-dir and try the -R
  33. by default, if it works?
  34. - support dir 503s better
  35. o clients don't log as loudly when they receive them
  36. - they don't count toward the 3-strikes rule
  37. - should there be some threshold of 503's after which we give up?
  38. - think about how to split "router is down" from "dirport shouldn't
  39. be tried for a while"?
  40. - authorities should *never* 503 a cache, but *should* 503 clients
  41. when they feel like it.
  42. - update dir-spec with what we decided for each of these
  43. o find N dirservers.
  44. o Make it no longer default for v2 dirservers to support v1.
  45. o non-versioning dirservers don't need to set recommended*versions.
  46. o non-naming dirservers don't need to have an approved-routers file.
  47. o What are criteria to be a dirserver? Write a policy.
  48. - are there other options that we haven't documented so far?
  49. . look at the proposed os x uninstaller:
  50. http://archives.seul.org/or/talk/Jan-2006/msg00038.html
  51. - Interim things:
  52. - provide no-cache no-index headers from the dirport?
  53. o remove down/useless descriptors from v1 directory?
  54. - exitlist should avoid outputting the same IP address twice.
  55. Deferred from 0.1.1.x:
  56. - We need a way for the authorities to declare that nodes are
  57. in a family. Needs design.
  58. R - streamline how we define a guard node as 'up'. document it
  59. somewhere.
  60. - Make "setconf" and "hup" behavior cleaner for LINELIST config
  61. options (e.g. Log). Bug 238.
  62. N - commit edmanm's win32 makefile to tor cvs contrib
  63. R - look into "uncounting" bytes spent on local connections. so
  64. we can bandwidthrate but still have fast downloads.
  65. R - Christian Grothoff's attack of infinite-length circuit.
  66. the solution is to have a separate 'extend-data' cell type
  67. which is used for the first N data cells, and only
  68. extend-data cells can be extend requests.
  69. - Specify, including thought about
  70. - Implement
  71. R - When we connect to a Tor server, it sends back a cell listing
  72. the IP it believes it is using. Use this to block dvorak's attack.
  73. Also, this is a fine time to say what time you think it is.
  74. - Verify that a new cell type is okay with deployed codebase
  75. - Specify
  76. - Implement
  77. R - failed rend desc fetches sometimes don't get retried.
  78. N - Display the reasons in 'destroy' and 'truncated' cells under some
  79. circumstances?
  80. - If the server is spewing complaints about raising your ulimit -n,
  81. we should add a note about this to the server descriptor so other
  82. people can notice too.
  83. - We need a getrlimit equivalent on Windows so we can reserve some
  84. file descriptors for saving files, etc. Otherwise we'll trigger
  85. asserts when we're out of file descriptors and crash.
  86. X <weasel> it would be nice to support a unix socket for the control thing.
  87. The main motivation behind this was that we could let unix permissions
  88. take care of the authentication step: everybody who can connect to the
  89. socket is authenticated. However, the linux unix(7) manual page suggests
  90. that requiring read/write permissions on the socket in order to use it
  91. is Linux specific, and that many BSD-derived systems ignore the permissions
  92. on the socket file. Portable programs should not rely on this feature for
  93. security, therefore the motivation for this feature is gone.
  94. - the tor client can do the "automatic proxy config url" thing?
  95. R - clients prefer to avoid exit nodes for non-exit path positions.
  96. - Automatically determine what ports are reachable and start using
  97. those, if circuits aren't working and it's a pattern we recognize
  98. ("port 443 worked once and port 9001 keeps not working").
  99. N - Should router info have a pointer to routerstatus?
  100. - We should at least do something about the duplicated fields.
  101. N . Additional controller features
  102. - change circuit status events to give more details, like purpose,
  103. whether they're internal, when they become dirty, when they become
  104. too dirty for further circuits, etc.
  105. R - What do we want here, exactly?
  106. N - Specify and implement it.
  107. - Change stream status events analogously.
  108. R - What do we want here, exactly?
  109. N - Specify and implement it.
  110. - Make other events "better".
  111. - Change stream status events analogously.
  112. R - What do we want here, exactly?
  113. N - Specify and implement it.
  114. - Make other events "better" analogously
  115. R - What do we want here, exactly?
  116. N - Specify and implement it.
  117. . Expose more information via getinfo:
  118. - import and export rendezvous descriptors
  119. - Review all static fields for additional candidates
  120. - Allow EXTENDCIRCUIT to unknown server.
  121. - We need some way to adjust server status, and to tell tor not to
  122. download directories/network-status, and a way to force a download.
  123. - It would be nice to request address lookups from the controller
  124. without using SOCKS.
  125. - Make everything work with hidden services
  126. X switch accountingmax to count total in+out, not either in or
  127. out. it's easy to move in this direction (not risky), but hard to
  128. back out if we decide we prefer it the way it already is. hm.
  129. - cpu fixes:
  130. - see if we should make use of truncate to retry
  131. R - kill dns workers more slowly
  132. . Directory changes
  133. . Some back-out mechanism for auto-approval
  134. - a way of rolling back approvals to before a timestamp
  135. - Consider minion-like fingerprint file/log combination.
  136. - config option to publish what ports you listen on, beyond
  137. ORPort/DirPort. It should support ranges and bit prefixes (?) too.
  138. - Parse this.
  139. - Relay this in networkstatus.
  140. - Non-directories don't need to keep descriptors in memory.
  141. o Make descriptor-fetching happen via an indirection function.
  142. - Remember file and offset.
  143. - Keep a journal FD for appending router descriptors.
  144. - packaging and ui stuff:
  145. . multiple sample torrc files
  146. - uninstallers
  147. . for os x
  148. . figure out how to make nt service stuff work?
  149. . Document it.
  150. o Add version number to directory.
  151. N - Vet all pending installer patches
  152. - Win32 installer plus privoxy, sockscap/freecap, etc.
  153. - Vet win32 systray helper code
  154. - document:
  155. o torcp needs more attention in the tor-doc-win32.
  156. - recommend gaim.
  157. - unrecommend IE because of ftp:// bug.
  158. - torrc.complete.in needs attention?
  159. - Bind to random port when making outgoing connections to Tor servers,
  160. to reduce remote sniping attacks.
  161. - Have new people be in limbo and need to demonstrate usefulness
  162. before we approve them.
  163. - Clients should estimate their skew as median of skew from servers
  164. over last N seconds.
  165. - Security
  166. - Alices avoid duplicate class C nodes.
  167. - Analyze how bad the partitioning is or isn't.
  168. . Update the hidden service stuff for the new dir approach.
  169. - switch to an ascii format, maybe sexpr?
  170. - authdirservers publish blobs of them.
  171. - other authdirservers fetch these blobs.
  172. - hidserv people have the option of not uploading their blobs.
  173. - you can insert a blob via the controller.
  174. - and there's some amount of backwards compatibility.
  175. - teach clients, intro points, and hidservs about auth mechanisms.
  176. - come up with a few more auth mechanisms.
  177. - auth mechanisms to let hidden service midpoint and responder filter
  178. connection requests.
  179. . Come up with a coherent strategy for bandwidth buckets and TLS. (The
  180. logic for reading from TLS sockets is likely to overrun the bandwidth
  181. buckets under heavy load. (Really, the logic was never right in the
  182. first place.) Also, we should audit all users of get_pending_bytes().)
  183. - Make it harder to circumvent bandwidth caps: look at number of bytes
  184. sent across sockets, not number sent inside TLS stream.
  185. - Make router_is_general_exit() a bit smarter once we're sure what it's for.
  186. - rewrite how libevent does select() on win32 so it's not so very slow.
  187. - Write limiting; separate token bucket for write
  188. - Audit everything to make sure rend and intro points are just as likely to
  189. be us as not.
  190. - Do something to prevent spurious EXTEND cells from making middleman
  191. nodes connect all over. Rate-limit failed connections, perhaps?
  192. Major items for 0.1.2.x:
  193. - Directory guards
  194. R - Server usability
  195. N - Better hidden service performance
  196. - Improve controller
  197. - Asynchronous DNS
  198. - Better estimates in the directory of whether servers have good uptime
  199. (high expected time to failure) or good guard qualities (high
  200. fractional uptime).
  201. - memory usage on dir servers.
  202. copy less!
  203. N - oprofile including kernel time.
  204. Topics to think about during 0.1.2.x development:
  205. - Figure out non-clique.
  206. - Figure out partial network knowledge.
  207. - Figure out incentives.
  208. Future version:
  209. - Limit to 2 dir, 2 OR, N SOCKS connections per IP.
  210. - Handle full buffers without totally borking
  211. - Rate-limit OR and directory connections overall and per-IP and
  212. maybe per subnet.
  213. - Hold-open-until-flushed now works by accident; it should work by
  214. design.
  215. - DoS protection: TLS puzzles, public key ops, bandwidth exhaustion.
  216. - Specify?
  217. - tor-resolve script should use socks5 to get better error messages.
  218. - Track uptime as %-of-time-up, as well as time-since-last-down.
  219. - hidserv offerers shouldn't need to define a SocksPort
  220. * figure out what breaks for this, and do it.
  221. - Relax clique assumptions.
  222. X start handling server descriptors without a socksport?
  223. - tor should be able to have a pool of outgoing IP addresses
  224. that it is able to rotate through. (maybe)
  225. - let each hidden service (or other thing) specify its own
  226. OutboundBindAddress?
  227. Blue-sky:
  228. - Patch privoxy and socks protocol to pass strings to the browser.
  229. - Standby/hotswap/redundant hidden services.
  230. - Robust decentralized storage for hidden service descriptors.
  231. - The "China problem"
  232. - Allow small cells and large cells on the same network?
  233. - Cell buffering and resending. This will allow us to handle broken
  234. circuits as long as the endpoints don't break, plus will allow
  235. connection (tls session key) rotation.
  236. - Implement Morphmix, so we can compare its behavior, complexity, etc.
  237. - Other transport. HTTP, udp, rdp, airhook, etc. May have to do our own
  238. link crypto, unless we can bully openssl into it.
  239. - Need a relay teardown cell, separate from one-way ends.
  240. (Pending a user who needs this)
  241. - Handle half-open connections: right now we don't support all TCP
  242. streams, at least according to the protocol. But we handle all that
  243. we've seen in the wild.
  244. (Pending a user who needs this)