TODO 27 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576
  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. S - Steven claims
  9. M - Matt claims
  10. J - Jeff claims
  11. - Not done
  12. * Top priority
  13. . Partially done
  14. o Done
  15. d Deferrable
  16. D Deferred
  17. X Abandoned
  18. For Tor 0.2.0.13-alpha:
  19. - Put a consensus in place of the empty fallback-consensus file in
  20. src/config and see what breaks.
  21. - let bridges set relaybandwidthrate as low as 5kb
  22. - config option FetchDirInfoEagerly so the dnsel can fetch dir
  23. info like a mirror without needing to be a tor server.
  24. - nick has to pick a name for it
  25. Features blocking 0.2.0.x:
  26. - mirror tor downloads on (via) tor dir caches
  27. R . spec
  28. d deploy
  29. - geoip caching and publishing for bridges
  30. R . spec
  31. ? - deploy
  32. d let Vidalia use the geoip data too rather than doing its own
  33. anonymized queries
  34. - bridge address disbursal strategies
  35. o get the cached-descriptors* to bridges@moria
  36. - parse out bridge addresses from cached-descriptors*
  37. (or parse them out before Tonga sends them)
  38. (or get Tonga's Tor to write them out better in the first place)
  39. N * answer by IP/timestamp
  40. - run a little web server on moria?
  41. N d answer by answering email to bridges@torproject
  42. - keep track of which addresses have been answered already
  43. R d some sort of reachability testing on bridges
  44. R - bridge communities
  45. - spec
  46. - deploy
  47. - interface for letting soat modify flags that authorities assign
  48. R . spec
  49. - deploy
  50. - add an AuthDirBadexit torrc option if we decide we want one.
  51. S * tor usb windows image (vidalia, polipo, tor, firefox)
  52. S/M - vidalia can launch firefox
  53. - build a community version of firefox
  54. - pick our favorite extensions
  55. Things we'd like to do in 0.2.0.x:
  56. - See also Flyspray tasks.
  57. - See also all items marked XXXX020 and DOCDOC in the code
  58. - https://www.torproject.org/eff/legal-faq.html#License doesn't mention
  59. licenses for other components of the bundles.
  60. - Before the feature freeze: (Nick)
  61. D 118 if feasible and obvious
  62. D Maintain a skew estimate and use ftime consistently.
  63. - 105+TLS, if possible.
  64. . TLS backend work
  65. - New list of ciphers for clients
  66. o Servers detect new ciphers, and only send ID cert when they
  67. get an older cipher list, and only request client cert when
  68. they get an older cipher list.
  69. - Clients only send certificates when asked for them.
  70. o Servers disable callback once negotiation is finished, so
  71. that renegotiation happens according to the old rules.
  72. o Clients initiate renegotiation immediately on completing
  73. a v2 connection.
  74. o Servers detect renegotiation, and if there is now a client
  75. cert, they adust the client ID.
  76. o Detect.
  77. o Adjust.
  78. - New revised handshake: post-TLS:
  79. - start by sending VERSIONS cells
  80. - once we have a version, send a netinfo and become open
  81. - Ban most cell types on a non-OPEN connection.
  82. - NETINFO fallout
  83. - Don't extend a circuit over a noncanonical connection with
  84. mismatched address.
  85. - Learn our outgoing IP address from netinfo cells?
  86. o Protocol revision.
  87. o Earliest stages of 110 (infinite-length) in v2 protocol:
  88. add support for RELAY_EARLY.
  89. - get more v3 authorities before 0.2.0.x comes out.
  90. - brainstorm about who those should be
  91. - Bugs.
  92. - Bug reports Roger has heard along the way that don't have enough
  93. details/attention to solve them yet.
  94. - arma noticed that when his network went away and he tried
  95. a new guard node and the connect() syscall failed to it,
  96. the guard wasn't being marked as down. 0.2.0.x.
  97. - after being without network for 12 hours, arma's tor decided
  98. it couldn't fetch any network statuses, and never tried again
  99. even when the network came back and arma clicked on things.
  100. also 0.2.0.
  101. - we need a config option to turn off proposal 109 behavior, else
  102. running a private tor network on your own computer is very hard.
  103. . man page entry for HidServDirectoryV2 and
  104. MinUptimeHidServDirectoryV2.
  105. d Tor logs the libevent version on startup, for debugging purposes.
  106. This is great. But it does this before configuring the logs, so
  107. it only goes to stdout and is then lost.
  108. d we should do another bandwidth test every 12 hours or something
  109. if we're showing less than 50KB and our bandwidthrate says we can
  110. do more than that. I think some servers are forgetting the results
  111. of their first test, and then never seeing use.
  112. - Proposals:
  113. o 101: Voting on the Tor Directory System (plus 103)
  114. D Use if-modified-since on consensus download
  115. - Controller support
  116. - GETINFO to get consensus
  117. - Event when new consensus arrives
  118. - 105: Version negotiation for the Tor protocol
  119. . 111: Prioritize local traffic over relayed.
  120. - Merge into tor-spec.txt.
  121. - Refactoring:
  122. . Make cells get buffered on circuit, not on the or_conn.
  123. . Switch to pool-allocation for cells?
  124. - Benchmark pool-allocation vs straightforward malloc.
  125. - Adjust memory allocation logic in pools to favor a little less
  126. slack memory.
  127. . Remove socketpair-based bridges conns, and the word "bridge". (Use
  128. shared (or connected) buffers for communication, rather than sockets.)
  129. . Implement
  130. - Handle rate-limiting on directory writes to linked directory
  131. connections in a more sensible manner.
  132. - Find more ways to test this.
  133. D Do TLS connection rotation more often than "once a week" in the
  134. extra-stable case.
  135. D Streamline how we pick entry nodes: Make choose_random_entry() have
  136. less magic and less control logic.
  137. - Refactor networkstatus generation:
  138. - Include "v" line in getinfo values.
  139. - Bridges:
  140. . Bridges users (rudimentary version)
  141. o Ability to specify bridges manually
  142. o Config option 'UseBridges' that bridge users can turn on.
  143. o uses bridges as first hop rather than entry guards.
  144. o if you don't have any routerinfos for your bridges, or you don't
  145. like the ones you have, ask a new bridge for its server/authority.
  146. . Ask all directory questions to bridge via BEGIN_DIR.
  147. - use the bridges for dir fetches even when our dirport is open.
  148. R - drop 'authority' queries if they're to our own identity key; accept
  149. them otherwise.
  150. X Design/implement the "local-status" or something like it, from the
  151. "Descriptor purposes: how to tell them apart" section of
  152. http://archives.seul.org/or/dev/May-2007/msg00008.html
  153. o timeout and retry schedules for fetching bridge descriptors
  154. - give extend_info_t a router_purpose again
  155. o react faster to download networkstatuses after the first bridge
  156. descriptor arrives
  157. o be more robust to bridges being marked as down and leaving us
  158. stranded without any known "running" bridges.
  159. - Bridges operators (rudimentary version)
  160. o Ability to act as dir cache without a dir port.
  161. o Bridges publish to bridge authorities
  162. o Fix BEGIN_DIR so that you connect to bridge of which you only
  163. know IP (and optionally fingerprint), and then use BEGIN_DIR to learn
  164. more about it.
  165. R - look at server_mode() and decide if it always applies to bridges too.
  166. - Bridges
  167. o Clients can ask bridge authorities for updates on known bridges.
  168. - Misc
  169. * Make BEGIN_DIR mandatory for asking questions of bridge authorities?
  170. (but only for bridge descriptors. not for ordinary cache stuff.)
  171. - Features (other than bridges):
  172. - Audit how much RAM we're using for buffers and cell pools; try to
  173. trim down a lot.
  174. - Base relative control socket paths on datadir.
  175. - Make TrackHostExits expire TrackHostExitsExpire seconds after their
  176. *last* use, not their *first* use.
  177. - Limit to 2 dir, 2 OR, N SOCKS connections per IP.
  178. - Or maybe close connections from same IP when we get a lot from one.
  179. - Or maybe block IPs that connect too many times at once.
  180. - Testing
  181. N - Hack up a client that gives out weird/no certificates, so we can
  182. test to make sure that this doesn't cause servers to crash.
  183. - Deprecations:
  184. - can we deprecate 'getinfo network-status'?
  185. - can we deprecate the FastFirstHopPK config option?
  186. - Documentation
  187. - HOWTO for DNSPort.
  188. - Quietly document NT Service options
  189. - More prominently, we should have a recommended apps list.
  190. - recommend pidgin (gaim is renamed)
  191. - unrecommend IE because of ftp:// bug.
  192. - we should add a preamble to tor-design saying it's out of date.
  193. . Document transport and natdport in a good HOWTO.
  194. - Publicize torel. (What else?
  195. . Finish path-spec.txt
  196. P - Packaging:
  197. P - Plan a switch to polipo. Perhaps we'll offer two http proxies in
  198. the future.
  199. P - Make documentation realize that location of system configuration file
  200. will depend on location of system defaults, and isn't always /etc/torrc.
  201. P - Figure out why dll's compiled in mingw don't work right in WinXP.
  202. - Create packages for Nokia 800, requested by Chris Soghoian
  203. P - Consider creating special Tor-Polipo-Vidalia test packages,
  204. requested by Dmitri Vitalev
  205. o Get Vidalia supporting protocolinfo and using auth by default.
  206. P - create a "make win32-bundle" for vidalia-privoxy-tor-torbutton bundle
  207. P - Flyspray 487, create a universal binary privoxy for inclusion in
  208. packages.
  209. Planned for 0.2.1.x:
  210. - we try to build 4 test circuits to break them over different
  211. servers. but sometimes our entry node is the same for multiple
  212. test circuits. this defeats the point.
  213. - enforce a lower limit on MaxCircuitDirtiness and CircuitBuildTimeout.
  214. - configurable timestamp granularity. defaults to 'seconds'.
  215. - consider making 'safelogging' extend to info-level logs too.
  216. - we should consider a single config option TorPrivateNetwork that
  217. turns on all the config options for running a private test tor
  218. network. having to keep updating all the tools, and the docs,
  219. just isn't working.
  220. - consider whether a single Guard flag lets us distinguish between
  221. "was good enough to be a guard when we picked it" and "is still
  222. adequate to be used as a guard even after we've picked it". We should
  223. write a real proposal for this.
  224. - switch out privoxy in the bundles and replace it with polipo.
  225. - make the new tls handshake blocking-resistant.
  226. - figure out some way to collect feedback about what countries are using
  227. bridges, in a way that doesn't screw anonymity too much.
  228. - let tor dir mirrors proxy connections to the tor download site, so
  229. if you know a bridge you can fetch the tor software.
  230. - more strategies for distributing bridge addresses in a way that
  231. doesn't rely on knowing somebody who runs a bridge for you.
  232. - A way to adjust router status flags from the controller. (How do we
  233. prevent the authority from clobbering them soon afterward?)
  234. - Bridge authorities should do reachability testing but only on the
  235. purpose==bridge descriptors they have.
  236. - Clients should estimate their skew as median of skew from servers
  237. over last N seconds.
  238. - Investigate RAM use in Tor servers.
  239. - Start on the WSAENOBUFS solution.
  240. - Start on Windows auto-update for Tor
  241. Deferred from 0.2.0.x:
  242. - Proposals
  243. - 113: Simplifying directory authority administration
  244. - 110: prevent infinite-length circuits (phase one)
  245. - 118: Listen on and advertise multiple ports:
  246. - Tor should be able to have a pool of outgoing IP addresses that it is
  247. able to rotate through. (maybe. Possible overlap with proposal 118.)
  248. - config option to publish what ports you listen on, beyond
  249. ORPort/DirPort. It should support ranges and bit prefixes (?) too.
  250. (This is very similar to proposal 118.)
  251. - 117: IPv6 Exits
  252. - Internal code support for ipv6:
  253. o Clone ipv6 functions (inet_ntop, inet_pton) where they don't exist.
  254. - Most address variables need to become tor_addr_t
  255. - Teach resolving code how to handle ipv6.
  256. - Teach exit policies about ipv6 (consider ipv4/ipv6 interaction!)
  257. - Features
  258. - Let controller set router flags for authority to transmit, and for
  259. client to use.
  260. - add an 'exit-address' line in the descriptor for servers that exit
  261. from something that isn't their published address.
  262. - More work on AvoidDiskWrites?
  263. - Features
  264. - Make a TCP DNSPort
  265. - Protocol work
  266. - MAYBE kill stalled circuits rather than stalled connections. This is
  267. possible thanks to cell queues, but we need to consider the anonymity
  268. implications.
  269. - Implement TLS shutdown properly when possible.
  270. - Bugs
  271. - If the client's clock is too far in the past, it will drop (or just not
  272. try to get) descriptors, so it'll never build circuits.
  273. - Refactoring
  274. - Make resolves no longer use edge_connection_t unless they are actually
  275. _on_ a socks connection: have edge_connection_t and (say)
  276. dns_request_t both extend an edge_stream_t, and have p_streams and
  277. n_streams both be linked lists of edge_stream_t.
  278. - Generate torrc.{complete|sample}.in, tor.1.in, the HTML manual, and the
  279. online config documentation from a single source.
  280. - Move all status info out of routerinfo into local_routerstatus. Make
  281. "who can change what" in local_routerstatus explicit. Make
  282. local_routerstatus (or equivalent) subsume all places to go for "what
  283. router is this?"
  284. - Blocking/scanning-resistance
  285. - It would be potentially helpful to respond to https requests on
  286. the OR port by acting like an HTTPS server.
  287. - Do we want to maintain our own set of entryguards that we use as
  288. next hop after the bridge? Open research question; let's say no
  289. for 0.2.0 unless we learn otherwise.
  290. - Some mechanism for specifying that we want to stop using a cached
  291. bridge.
  292. - Build:
  293. - Detect correct version of libraries from autoconf script.
  294. Future versions:
  295. - See also Flyspray tasks.
  296. - See also all OPEN/ACCEPTED proposals.
  297. - See also all items marked XXXX and FFFF in the code.
  298. - Protocol:
  299. - Our current approach to block attempts to use Tor as a single-hop proxy
  300. is pretty lame; we should get a better one.
  301. - Allow small cells and large cells on the same network?
  302. - Cell buffering and resending. This will allow us to handle broken
  303. circuits as long as the endpoints don't break, plus will allow
  304. connection (tls session key) rotation.
  305. - Implement Morphmix, so we can compare its behavior, complexity,
  306. etc. But see paper breaking morphmix.
  307. - Other transport. HTTP, udp, rdp, airhook, etc. May have to do our own
  308. link crypto, unless we can bully DTLS into it.
  309. - Need a relay teardown cell, separate from one-way ends.
  310. (Pending a user who needs this)
  311. - Handle half-open connections: right now we don't support all TCP
  312. streams, at least according to the protocol. But we handle all that
  313. we've seen in the wild.
  314. (Pending a user who needs this)
  315. - Directory system
  316. - BEGIN_DIR items
  317. X turn the received socks addr:port into a digest for setting .exit
  318. - handle connect-dir streams that don't have a chosen_exit_name set.
  319. - Have a "Faster" status flag that means it. Fast2, Fast4, Fast8?
  320. - Add an option (related to AvoidDiskWrites) to disable directory
  321. caching. (Is this actually a good idea??)
  322. - Add d64 and fp64 along-side d and fp so people can paste status
  323. entries into a url. since + is a valid base64 char, only allow one
  324. at a time. Consider adding to controller as well.
  325. - Some back-out mechanism for auto-approval on authorities
  326. - a way of rolling back approvals to before a timestamp
  327. - Consider minion-like fingerprint file/log combination.
  328. - Have new people be in limbo and need to demonstrate usefulness
  329. before we approve them.
  330. - Hidden services:
  331. - Standby/hotswap/redundant hidden services.
  332. . Update the hidden service stuff for the new dir approach. (Much
  333. of this will be superseded by 114.)
  334. - switch to an ascii format, maybe sexpr?
  335. - authdirservers publish blobs of them.
  336. - other authdirservers fetch these blobs.
  337. - hidserv people have the option of not uploading their blobs.
  338. - you can insert a blob via the controller.
  339. - and there's some amount of backwards compatibility.
  340. - teach clients, intro points, and hidservs about auth mechanisms.
  341. - come up with a few more auth mechanisms.
  342. - auth mechanisms to let hidden service midpoint and responder filter
  343. connection requests.
  344. - Let each hidden service (or other thing) specify its own
  345. OutboundBindAddress?
  346. - Hidserv offerers shouldn't need to define a SocksPort
  347. - Server operation
  348. X When we notice a 'Rejected: There is already a named server with
  349. this nickname' message... or maybe instead when we see in the
  350. networkstatuses that somebody else is Named with the name we
  351. want: warn the user, send a STATUS_SERVER message, and fall back
  352. to unnamed.
  353. - If the server is spewing complaints about raising your ulimit -n,
  354. we should add a note about this to the server descriptor so other
  355. people can notice too.
  356. - When we hit a funny error from a dir request (eg 403 forbidden),
  357. but tor is working and happy otherwise, and we haven't seen many
  358. such errors recently, then don't warn about it.
  359. - Controller
  360. - Implement missing status events and accompanying getinfos
  361. - DIR_REACHABLE
  362. - BAD_DIR_RESPONSE (Unexpected directory response; maybe we're behind
  363. a firewall.)
  364. - BAD_PROXY (Bad http or https proxy)
  365. - UNRECOGNIZED_ROUTER (a nickname we asked for is unavailable)
  366. - Status events related to hibernation
  367. - something about failing to parse our address?
  368. from resolve_my_address() in config.c
  369. - sketchy OS, sketchy threading
  370. - too many onions queued: threading problems or slow CPU?
  371. - Implement missing status event fields:
  372. - TIMEOUT on CHECKING_REACHABILITY
  373. - GETINFO status/client, status/server, status/general: There should be
  374. some way to learn which status events are currently "in effect."
  375. We should specify which these are, what format they appear in, and so
  376. on.
  377. - More information in events:
  378. - Include bandwidth breakdown by conn->type in BW events.
  379. - Change circuit status events to give more details, like purpose,
  380. whether they're internal, when they become dirty, when they become
  381. too dirty for further circuits, etc.
  382. - Change stream status events analogously.
  383. - Expose more information via getinfo:
  384. - import and export rendezvous descriptors
  385. - Review all static fields for additional candidates
  386. - Allow EXTENDCIRCUIT to unknown server.
  387. - We need some way to adjust server status, and to tell tor not to
  388. download directories/network-status, and a way to force a download.
  389. - Make everything work with hidden services
  390. - Performance/resources
  391. - per-conn write buckets
  392. - separate config options for read vs write limiting
  393. (It's hard to support read > write, since we need better
  394. congestion control to avoid overfull buffers there. So,
  395. defer the whole thing.)
  396. - Look into pulling serverdescs off buffers as they arrive.
  397. - Rate limit exit connections to a given destination -- this helps
  398. us play nice with websites when Tor users want to crawl them; it
  399. also introduces DoS opportunities.
  400. - Consider truncating rather than destroying failed circuits,
  401. in order to save the effort of restarting. There are security
  402. issues here that need thinking, though.
  403. - Handle full buffers without totally borking
  404. - Rate-limit OR and directory connections overall and per-IP and
  405. maybe per subnet.
  406. - Misc
  407. - Hold-open-until-flushed now works by accident; it should work by
  408. design.
  409. - Display the reasons in 'destroy' and 'truncated' cells under
  410. some circumstances?
  411. - Make router_is_general_exit() a bit smarter once we're sure what
  412. it's for.
  413. - Automatically determine what ports are reachable and start using
  414. those, if circuits aren't working and it's a pattern we
  415. recognize ("port 443 worked once and port 9001 keeps not
  416. working").
  417. - Security
  418. - some better fix for bug #516?
  419. - don't do dns hijacking tests if we're reject *:* exit policy?
  420. (deferred until 0.1.1.x is less common)
  421. - Directory guards
  422. - Mini-SoaT:
  423. - Servers might check certs for known-good ssl websites, and if
  424. they come back self-signed, declare themselves to be
  425. non-exits. Similar to how we test for broken/evil dns now.
  426. - Authorities should try using exits for http to connect to some
  427. URLS (specified in a configuration file, so as not to make the
  428. List Of Things Not To Censor completely obvious) and ask them
  429. for results. Exits that don't give good answers should have
  430. the BadExit flag set.
  431. - Alternatively, authorities should be able to import opinions
  432. from Snakes on a Tor.
  433. - More consistent error checking in router_parse_entry_from_string().
  434. I can say "banana" as my bandwidthcapacity, and it won't even squeak.
  435. - Bind to random port when making outgoing connections to Tor servers,
  436. to reduce remote sniping attacks.
  437. - Audit everything to make sure rend and intro points are just as
  438. likely to be us as not.
  439. - Do something to prevent spurious EXTEND cells from making
  440. middleman nodes connect all over. Rate-limit failed
  441. connections, perhaps?
  442. - DoS protection: TLS puzzles, public key ops, bandwidth exhaustion.
  443. - Needs thinking
  444. - Now that we're avoiding exits when picking non-exit positions,
  445. we need to consider how to pick nodes for internal circuits. If
  446. we avoid exits for all positions, we skew the load balancing. If
  447. we accept exits for all positions, we leak whether it's an
  448. internal circuit at every step. If we accept exits only at the
  449. last hop, we reintroduce Lasse's attacks from the Oakland paper.
  450. - Windows server usability
  451. - Solve the ENOBUFS problem.
  452. - make tor's use of openssl operate on buffers rather than sockets,
  453. so we can make use of libevent's buffer paradigm once it has one.
  454. - make tor's use of libevent tolerate either the socket or the
  455. buffer paradigm; includes unifying the functions in connect.c.
  456. - We need a getrlimit equivalent on Windows so we can reserve some
  457. file descriptors for saving files, etc. Otherwise we'll trigger
  458. asserts when we're out of file descriptors and crash.
  459. - Merge code from Urz into libevent
  460. - Make Tor use evbuffers.
  461. - Documentation
  462. - a way to generate the website diagrams from source, so we can
  463. translate them as utf-8 text rather than with gimp. (svg? or
  464. imagemagick?)
  465. . Flesh out options_description array in src/or/config.c
  466. . multiple sample torrc files
  467. . figure out how to make nt service stuff work?
  468. . Document it.
  469. - Refactor tor man page to divide generally useful options from
  470. less useful ones?
  471. - Add a doxygen style checker to make check-spaces so nick doesn't drift
  472. too far from arma's undocumented styleguide. Also, document that
  473. styleguide in HACKING. (See r9634 for example.)
  474. - exactly one space at beginning and at end of comments, except i
  475. guess when there's line-length pressure.
  476. - if we refer to a function name, put a () after it.
  477. - only write <b>foo</b> when foo is an argument to this function.
  478. - doxygen comments must always end in some form of punctuation.
  479. - capitalize the first sentence in the doxygen comment, except
  480. when you shouldn't.
  481. - avoid spelling errors and incorrect comments. ;)
  482. - Packaging
  483. - The Debian package now uses --verify-config when (re)starting,
  484. to distinguish configuration errors from other errors. Perhaps
  485. the RPM and other startup scripts should too?
  486. - add a "default.action" file to the tor/vidalia bundle so we can
  487. fix the https thing in the default configuration:
  488. http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#PrivoxyWeirdSSLPort
  489. - Related tools
  490. - Patch privoxy and socks protocol to pass strings to the browser.
  491. Documentation, non-version-specific.
  492. - Specs
  493. - Mark up spec; note unclear points about servers
  494. NR - write a spec appendix for 'being nice with tor'
  495. - Specify the keys and key rotation schedules and stuff
  496. - Mention controller libs someplace.
  497. - Remove need for HACKING file.
  498. - document http://wiki.noreply.org/noreply/TheOnionRouter/TransparentProxy on freebsd and osx
  499. P - figure out why x86_64 won't build rpms from tor.spec
  500. P - figure out spec files for bundles of vidalia-tor-polipo
  501. P - figure out polipo install scripts for bundles of vidalia-tor-polipo on osx, win32
  502. - figure out selinux policy for tor
  503. P - change packaging system to more automated and specific for each
  504. platform, suggested by Paul Wouter
  505. P - Setup repos for redhat and suse rpms & start signing the rpms the
  506. way package management apps prefer
  507. Website:
  508. J - tor-in-the-media page
  509. P - Figure out licenses for website material.
  510. (Phobos reccomends the Open Publication License at
  511. http://opencontent.org/openpub/)
  512. P - put the logo on the website, in source form, so people can put it on
  513. stickers directly, etc.
  514. P - put the source image for the stickers on the website, so people can
  515. print their own
  516. P - figure out a license for the logos and docs we publish (trademark
  517. figures into this)
  518. (Phobos reccomends the Open Publication License at
  519. http://opencontent.org/openpub/)
  520. R - make a page with the hidden service diagrams.
  521. P - ask Jan/Jens to be the translation coordinator? add to volunteer page.
  522. - add a page for localizing all tor's components.
  523. - It would be neat if we had a single place that described _all_ the
  524. tor-related tools you can use, and what they give you, and how well they
  525. work. Right now, we don't give a lot of guidance wrt
  526. torbutton/foxproxy/privoxy/polipo in any consistent place.
  527. P - create a 'blog badge' for tor fans to link to and feature on their
  528. blogs. A sample can be found at http://interloper.org/tmp/tor/tor-button.png
  529. - Tor mirrors
  530. - make a mailing list with the mirror operators
  531. - make an automated tool to check /project/trace/ at mirrors to
  532. learn which ones are lagging behind.
  533. - auto (or manually) cull the mirrors that are broken; and
  534. contact their operator?
  535. - a set of instructions for mirror operators to make their apaches
  536. serve our charsets correctly, and bonus points for language
  537. negotiation.
  538. - figure out how to load-balance the downloads across mirrors?
  539. - ponder how to get users to learn that they should google for
  540. "tor mirrors" if the main site is blocked.
  541. - find a mirror volunteer to coordinate all of this