TODO 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363
  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. . <nickm> "Let's try to find a way to make it run and make the version
  15. match, but if not, let's just make it run."
  16. - <arma> "should we detect if we have a --with-ssl-dir and try the -R
  17. by default, if it works?"
  18. Items for 0.1.2.x, real soon now:
  19. - When we've been idle a long time, we stop fetching server
  20. descriptors. When we then get a socks request, we build circuits
  21. immediately using whatever descriptors we have, rather than waiting
  22. until we've fetched correct ones.
  23. - If the client's clock is too far in the past, it will drop (or
  24. just not try to get) descriptors, so it'll never build circuits.
  25. - when we start, remove any entryguards that are listed in excludenodes.
  26. . start calling dev releases 0.1.2.1-alpha-dev, not -cvs. Do we need
  27. to change the code in any way for this? Appears to be "no".
  28. - Remember the last time we saw one of our entry guards labelled with
  29. the GUARD flag. If it's been too long, it is not suitable for use.
  30. If it's been really too long, remove it from the list.
  31. . Figure out avoiding duplicate /24 lines
  32. o automatically add /16 servers to family
  33. - do it in an efficient way. keep a list of something somewhere?
  34. - make the "16" part configurable, so people who run their own
  35. tor network can set it to 32.
  36. N - Clients stop dumping old descriptors if the network-statuses
  37. claim they're still valid.
  38. . If we fail to connect via an exit enclave, (warn and) try again
  39. without demanding that exit node.
  40. - And recognize when extending to the enclave node is failing,
  41. so we can abandon then too.
  42. - We need a separate list of "hidserv authorities" if we want to
  43. retire moria1 from the main list.
  44. Items for 0.1.2.x, later on:
  45. o re-enable blossom functionality: let tor servers decide if they
  46. will use local search when resolving, or not.
  47. - enumerate events of important things that occur in tor, so vidalia can
  48. react.
  49. - We should ship with a list of stable dir mirrors -- they're not
  50. trusted like the authorities, but they'll provide more robustness
  51. and diversity for bootstrapping clients.
  52. - Servers are easy to setup and run: being a relay is about as easy as
  53. being a client.
  54. - Reduce resource load
  55. - look into "uncounting" bytes spent on local connections. so
  56. we can bandwidthrate but still have fast downloads.
  57. - Write limiting; separate token bucket for write
  58. o dir answers include a your-ip-address-is header, so we can
  59. break our dependency on dyndns.
  60. - Come up with good 'nicknames' automatically, or make no-nickname
  61. routers workable.
  62. - tolerate clock skew on bridge relays.
  63. - a way to export server descriptors to controllers, and/or to
  64. non-standard dir authorities.
  65. - a way to pick entries based wholly on extend_info equivalent;
  66. a way to export extend_info equivalent.
  67. - option to dl directory info via tor
  68. - is the __AllDirActionsPrivate config option sufficient?
  69. D Count TLS bandwidth more accurately
  70. - Write-limit directory responses (need to research)
  71. N . Improve memory usage on tight-memory machines.
  72. . Directory-related fixes.
  73. . Mmap cache files where possible.
  74. o Mmap cached-routers file; when building it, go oldest-to-newest.
  75. - More unit tests and asserts for cached-routers file: ensure digest
  76. for the right router. Verify dl by digest, fp, etc.
  77. o Make sure cached-routers values and offsets are correct in the
  78. presence of windows FS insanity.
  79. D Save and mmap v1 directories, and networkstatus docs; store them
  80. zipped, not uncompressed.
  81. D Switch cached_router_t to use mmap.
  82. D What to do about reference counts on windows?
  83. (On Unix, this is easy: unlink works fine. (Right?) On
  84. Windows, I have doubts. Do we need to keep multiple files?)
  85. D What do we do about the fact that people can't read zlib-
  86. compressed files manually?
  87. - Look into pulling serverdescs off buffers as they arrive.
  88. - "bandwidth classes", for incoming vs initiated-here conns.
  89. o Asynchronous DNS
  90. o And test it
  91. . Make it work on windows.
  92. o Implement
  93. . Enable
  94. - Test
  95. X Make the Nameservers option documented, and make it work right on
  96. reload.
  97. o Fail when we have no configured nameservers!
  98. o Make it the default on platforms where it works.
  99. - Document SearchDomains, ResolvConf options
  100. o Make resolv.conf (or local equivalent) get checked on reload,
  101. settable while running, etc.
  102. - Add ipv6 support; make API closer to getaddrinfo(). (i.e., allow a
  103. single AAAA/A query, return cname as well)
  104. - Teach it to be able to listen for A and PTR requests to be processed.
  105. Interface should be set_request_listener(sock, cb); [ cb(request) ]
  106. send_reply(request, answer);.
  107. - Refactor exit side of resolve: do we need a connection_t?
  108. - Refactor entry side of resolve: do we need a connection_t?
  109. - Directory guards
  110. - Make reverse DNS work.
  111. - Specify
  112. X Implement with dnsworkers
  113. (There's no point doing this, since we will throw away dnsworkers once
  114. eventdns is confirmed to work everywhere.)
  115. o Implement in eventdns
  116. - Connect to resolve cells, server-side.
  117. - Add client-side interface
  118. - Performance improvements
  119. - Better estimates in the directory of whether servers have good uptime
  120. (high expected time to failure) or good guard qualities (high
  121. fractional uptime).
  122. - AKA Track uptime as %-of-time-up, as well as time-since-last-down.
  123. - Clients should prefer to avoid exit nodes for non-exit path positions.
  124. (bug 200)
  125. - Have a "Faster" status flag that means it. Fast2, Fast4, Fast8?
  126. - A more efficient dir protocol.
  127. - Later, servers will stop generating new descriptors simply
  128. because 18 hours have passed.
  129. - Authorities should fetch the network-statuses amongst each
  130. other, consensus them, and advertise a communal network-status.
  131. This is not so much for safety/complexity as it is to reduce
  132. bandwidth requirements for Alice.
  133. - How does this interact with our goal of being able to choose
  134. your own dir authorities? I guess we're now assuming that all
  135. dir authorities know all the other authorities in their "group"?
  136. - Should we also look into a "delta since last network-status
  137. checkpoint" scheme, to reduce overhead further?
  138. D Extend the "r" line in network-status to give a set of buckets (say,
  139. comma-separated) for that router.
  140. - Buckets are deterministic based on IP address.
  141. - Then clients can choose a bucket (or set of buckets) to
  142. download and use.
  143. - Critical but minor bugs, backport candidates.
  144. - Failed rend desc fetches sometimes don't get retried. True/false?
  145. - non-v1 authorities should not accept rend descs.
  146. - support dir 503s better
  147. o clients don't log as loudly when they receive them
  148. - they don't count toward the 3-strikes rule
  149. - should there be some threshold of 503's after which we give up?
  150. - think about how to split "router is down" from "dirport shouldn't
  151. be tried for a while"?
  152. - authorities should *never* 503 a cache, but *should* 503 clients
  153. when they feel like it.
  154. - update dir-spec with what we decided for each of these
  155. - provide no-cache no-index headers from the dirport?
  156. - Windows server usability
  157. - Solve the ENOBUFS problem.
  158. - make tor's use of openssl operate on buffers rather than sockets,
  159. so we can make use of libevent's buffer paradigm once it has one.
  160. - make tor's use of libevent tolerate either the socket or the
  161. buffer paradigm; includes unifying the functions in connect.c.
  162. - We need a getrlimit equivalent on Windows so we can reserve some
  163. file descriptors for saving files, etc. Otherwise we'll trigger
  164. asserts when we're out of file descriptors and crash.
  165. M - rewrite how libevent does select() on win32 so it's not so very slow.
  166. - Add overlapped IO
  167. N - When we connect to a Tor server, it sends back a cell listing
  168. the IP it believes it is using. Use this to block dvorak's attack.
  169. Also, this is a fine time to say what time you think it is.
  170. o Verify that a new cell type is okay with deployed codebase
  171. . Specify HELLO cells
  172. . Figure out v0 compatibility.
  173. - Implement
  174. N - Exitlist should avoid outputting the same IP address twice.
  175. N - Write path-spec.txt
  176. - Packaging
  177. - Tell people about OSX Uninstaller
  178. - Quietly document NT Service options
  179. - Docs
  180. - More prominently, we should have a recommended apps list.
  181. - recommend gaim.
  182. - unrecommend IE because of ftp:// bug.
  183. - torrc.complete.in needs attention?
  184. Topics to think about during 0.1.2.x development:
  185. * Figure out incentives.
  186. - (How can we make this tolerant of a bad v0?)
  187. * Figure out non-clique.
  188. * Figure out China.
  189. - Figure out partial network knowledge.
  190. - Figure out hidden services.
  191. Minor items for 0.1.2.x as time permits.
  192. - If we try to publish as a nickname that's already claimed, should
  193. we append a number (or increment the number) and try again? This
  194. way people who read their logs can fix it as before, but people
  195. who don't read their logs will still offer Tor servers.
  196. - Tor should bind its ports before dropping privs, so users don't
  197. have to do the ipchains dance.
  198. o Make --verify-config return a useful error code.
  199. - Rate limit exit connections to a given destination -- this helps
  200. us play nice with websites when Tor users want to crawl them; it
  201. also introduces DoS opportunities.
  202. - The bw_accounting file should get merged into the state file.
  203. - Streamline how we define a guard node as 'up'.
  204. - Better installers and build processes.
  205. - Commit edmanm's win32 makefile to tor contrib, or write a new one.
  206. - Christian Grothoff's attack of infinite-length circuit.
  207. the solution is to have a separate 'extend-data' cell type
  208. which is used for the first N data cells, and only
  209. extend-data cells can be extend requests.
  210. - Specify, including thought about anonymity implications.
  211. - Display the reasons in 'destroy' and 'truncated' cells under some
  212. circumstances?
  213. - We need a way for the authorities to declare that nodes are
  214. in a family. Also, it kinda sucks that family declarations use O(N^2)
  215. space in the descriptors.
  216. - If the server is spewing complaints about raising your ulimit -n,
  217. we should add a note about this to the server descriptor so other
  218. people can notice too.
  219. - cpu fixes:
  220. - see if we should make use of truncate to retry
  221. - kill dns workers more slowly
  222. . Directory changes
  223. . Some back-out mechanism for auto-approval
  224. - a way of rolling back approvals to before a timestamp
  225. - Consider minion-like fingerprint file/log combination.
  226. - packaging and ui stuff:
  227. . multiple sample torrc files
  228. . figure out how to make nt service stuff work?
  229. . Document it.
  230. - Vet all pending installer patches
  231. - Win32 installer plus privoxy, sockscap/freecap, etc.
  232. - Vet win32 systray helper code
  233. - Improve controller
  234. - change circuit status events to give more details, like purpose,
  235. whether they're internal, when they become dirty, when they become
  236. too dirty for further circuits, etc.
  237. - What do we want here, exactly?
  238. - Specify and implement it.
  239. - Change stream status events analogously.
  240. - What do we want here, exactly?
  241. - Specify and implement it.
  242. - Make other events "better".
  243. - Change stream status events analogously.
  244. - What do we want here, exactly?
  245. - Specify and implement it.
  246. - Make other events "better" analogously
  247. - What do we want here, exactly?
  248. - Specify and implement it.
  249. . Expose more information via getinfo:
  250. - import and export rendezvous descriptors
  251. - Review all static fields for additional candidates
  252. - Allow EXTENDCIRCUIT to unknown server.
  253. - We need some way to adjust server status, and to tell tor not to
  254. download directories/network-status, and a way to force a download.
  255. - It would be nice to request address lookups from the controller
  256. without using SOCKS.
  257. - Make everything work with hidden services
  258. - Directory system improvements
  259. - config option to publish what ports you listen on, beyond
  260. ORPort/DirPort. It should support ranges and bit prefixes (?) too.
  261. - Parse this.
  262. - Relay this in networkstatus.
  263. Future version:
  264. - Tor should have a "DNS port" so we don't need to ship with (and
  265. write) a clean portable dns proxy.
  266. . Update the hidden service stuff for the new dir approach.
  267. - switch to an ascii format, maybe sexpr?
  268. - authdirservers publish blobs of them.
  269. - other authdirservers fetch these blobs.
  270. - hidserv people have the option of not uploading their blobs.
  271. - you can insert a blob via the controller.
  272. - and there's some amount of backwards compatibility.
  273. - teach clients, intro points, and hidservs about auth mechanisms.
  274. - come up with a few more auth mechanisms.
  275. - auth mechanisms to let hidden service midpoint and responder filter
  276. connection requests.
  277. - Bind to random port when making outgoing connections to Tor servers,
  278. to reduce remote sniping attacks.
  279. - Have new people be in limbo and need to demonstrate usefulness
  280. before we approve them.
  281. - Clients should estimate their skew as median of skew from servers
  282. over last N seconds.
  283. - Make router_is_general_exit() a bit smarter once we're sure what it's for.
  284. - Audit everything to make sure rend and intro points are just as likely to
  285. be us as not.
  286. - Do something to prevent spurious EXTEND cells from making middleman
  287. nodes connect all over. Rate-limit failed connections, perhaps?
  288. - Automatically determine what ports are reachable and start using
  289. those, if circuits aren't working and it's a pattern we recognize
  290. ("port 443 worked once and port 9001 keeps not working").
  291. - Limit to 2 dir, 2 OR, N SOCKS connections per IP.
  292. - Handle full buffers without totally borking
  293. - Rate-limit OR and directory connections overall and per-IP and
  294. maybe per subnet.
  295. - Hold-open-until-flushed now works by accident; it should work by
  296. design.
  297. - DoS protection: TLS puzzles, public key ops, bandwidth exhaustion.
  298. - Specify?
  299. - tor-resolve script should use socks5 to get better error messages.
  300. - hidserv offerers shouldn't need to define a SocksPort
  301. * figure out what breaks for this, and do it.
  302. - tor should be able to have a pool of outgoing IP addresses
  303. that it is able to rotate through. (maybe)
  304. - let each hidden service (or other thing) specify its own
  305. OutboundBindAddress?
  306. - Have a mode that doesn't write to disk much, so we can run Tor on
  307. flash memory (e.g. Linksys routers).
  308. Blue-sky:
  309. - Patch privoxy and socks protocol to pass strings to the browser.
  310. - Standby/hotswap/redundant hidden services.
  311. - Robust decentralized storage for hidden service descriptors.
  312. - The "China problem"
  313. - Allow small cells and large cells on the same network?
  314. - Cell buffering and resending. This will allow us to handle broken
  315. circuits as long as the endpoints don't break, plus will allow
  316. connection (tls session key) rotation.
  317. - Implement Morphmix, so we can compare its behavior, complexity, etc.
  318. - Other transport. HTTP, udp, rdp, airhook, etc. May have to do our own
  319. link crypto, unless we can bully openssl into it.
  320. - Need a relay teardown cell, separate from one-way ends.
  321. (Pending a user who needs this)
  322. - Handle half-open connections: right now we don't support all TCP
  323. streams, at least according to the protocol. But we handle all that
  324. we've seen in the wild.
  325. (Pending a user who needs this)
  326. Non-Coding:
  327. - Mark up spec; note unclear points about servers
  328. - Mention controller libs someplace.
  329. . more pictures from ren. he wants to describe the tor handshake
  330. NR- write a spec appendix for 'being nice with tor'
  331. - tor-in-the-media page
  332. - Remove need for HACKING file.
  333. - Figure out licenses for website material.
  334. Website:
  335. - and remove home and make the "Tor" picture be the link to home.
  336. - put the logo on the website, in source form, so people can put it on
  337. stickers directly, etc.
  338. R - make a page with the hidden service diagrams.
  339. - ask Jan to be the translation coordinator? add to volunteer page.