4 SPEC - Spec not finalized
23 =======================================================================
28 W - Take the results from instrumenting directory downloads on Tor
29 clients, and analyze/simulate some alternate approaches. Finish
30 proposal for how to improve things, iterate based on feedback,
31 convince us that the anonymity tradeoffs and/or scalability
32 tradeoffs are acceptable.
35 KS - Design hidden service improvements, evaluate them and consider
36 security properties: write some proposals, get feedback, revise
38 ? - nlnet 'user safety contest'. submit torbrowser, others?
42 o Vidalia learns when Tor thinks it should be updated
43 R - Tor status events should suggest a new version to switch to
44 I - Figure out a good PKI, document the design, assess security issues:
46 - Vidalia fetches the new one via Tor when possible, but fetches
47 it without Tor "when necessary", whatever that means.
48 - Give an interface for notifying the user, and letting her
49 decide to fetch and decide to swap out the old Tor for the new.
50 - Do the same for Polipo
51 - and for Vidalia itself
54 NSE - Write first draft of research study for Paul's research problem.
55 This should be at least vaguely related to what was discussed in
56 the end-of-May deliverable.
59 KS - Finish implementation of hidden service improvements: have a set
60 of patches that you think work.
61 W - Finish implementation of directory overhead changes: have a set
62 of patches that you think work.
65 KS - Finish testing, debugging, unit testing, etc the hidden service
66 changes. Have it in the development version and in use.
67 W - Finish testing, debugging, unit testing, etc the directory overhead
68 changes. Have it in the development version and in use.
70 =======================================================================
72 Other things Roger would be excited to see:
75 - Finish buffer stuff in libevent; start using it in Tor.
76 - Tors start believing the contents of NETINFO cells.
77 . Work with Steven and Roger to decide which parts of Paul's project
79 - respond to Steven's red-team TLS testing (a.k.a, look at a packet
83 - Fit Vidalia in 640x480 again.
84 - When user changes the language in Vidalia, have it change right then.
85 - Vidalia should display/edit PlaintextPorts events/config.
86 . Vidalia's GUI should let you specify an http proxy that it launches
87 for you. Maybe in the general config window next to which Tor it
89 - Vidalia should avoid stomping on your custom exit policy lines
90 just because you click on 'save' for a totally different config thing.
91 - How much space do we save in TBB by stripping symbols from Vidalia
92 first? Good idea or crazy idea?
95 - gmail auto responder so you send us an email and we send you a Tor
96 binary. Probably needs a proposal first.
97 - weather.torproject.org should go live.
98 o Learn from Steven how to build/maintain the Tor Browser Bundle.
99 - Keep advocating new Tor servers and working with orgs like Mozilla
100 to let them like Tor.
101 - Start converting critical wiki pages into real Tor wml pages. E.g.,
102 https://wiki.torproject.org/noreply/TheOnionRouter/VerifyingSignatures
103 - Find out what happened to the buildbot and get it back up:
104 http://tor-buildbot.freehaven.net:8010/
105 - Learn about locking memory pages that have sensitive content. Get
108 - Vidalia html help files
109 - should we i18nize polipo's error messages too?
110 - Some of our translated wml files are very old -- so old that they
111 are harmful to leave in place. We need some sort of way to notice
112 this and disable them.
115 - Figure out (or give up on) how to run Tor Browser and ordinary
116 Firefox side-by-side.
117 - Enumerate and analyze traces left when running from USB
118 - Write a list of research items Tor would like to see done, for the
119 volunteer page. Pick a few you'd like to work on yourself.
120 - Move proposal 131 or equivalent forward.
121 - Keep bugging us about exploits on the .exit notation.
122 - If relays have 100KB/s but set relaybandwidthrate to 10KB/s, do your
123 interference attacks still work?
124 - Mike's question #3 on https://www.torproject.org/volunteer#Research
125 - Worthwhile shipping TBB with some local html help files that come
127 - Decide whether TBB should use Torbutton's "lock" feature.
128 http://archives.seul.org/or/cvs/Jun-2008/msg00186.html
131 - Which bundles include Torbutton? Change the docs/tor-doc-foo pages
132 so they admit that Torbutton is in them too. Change the download
134 - The OS X bundle screenshots are from forever ago -- they don't
135 include Torbutton, they still say it's tor.eff.org, etc.
136 - Should we still be telling you how to use Safari on OS X for Tor,
137 given all the holes that Torbutton-dev solves on Firefox?
140 o Make a hidden services explanation page with the hidden service
141 diagrams. See img/THS-[1-6].png. These need some text to go along
142 with them though, so people can follow what's going on.
143 - We should consider a single config option TorPrivateNetwork that
144 turns on all the config options for running a private test tor
145 network. having to keep updating all the tools, and the docs,
149 - Figure out how to make Vidalia and Tor play nicely on Debian, make
150 the necessary modifications, and make some Vidalia debs that pass
153 - Get oftc to switch to Tor dns bulk exitlist. Or tell us why it's
155 - Take non-Running entries out of the networkstatus consensus.
156 - Move proposal 134 forward.
157 - putting port predictions in state file
158 - if tor hasn't been used in a while it stops fetching consensus
159 documents. Retain that state over restarts.
162 - Finish tor-doc-bridge.wml
163 . Fix FAQ entry on setting up private Tor network
164 - Review Karsten's hidden service diagrams
165 - Roger should visit Internews DC sometime.
166 - Did we actually apply Steven's dkimproxy patch?
167 - Brainstorm about safe but effective ways for vidalia to
168 auto-update its user's bridges via Tor in the background.
171 - Roger wants to get an email every time there's a blog change,
172 e.g. a comment. That way spam doesn't go undetected for weeks.
173 - Or, maybe just disable linking from blog comments entirely?
175 =======================================================================
177 Bugs/issues for Tor 0.2.0.x:
178 . we should have an off-by-default way for relays to dump geoip data to
179 a file in their data directory, for measurement purposes.
180 o Basic implementation
181 N - Include probability-of-selection
182 R d let bridges set relaybandwidthrate as low as 5kb
183 R - bridge communities
186 - man page entries for Alternate*Authority config options
188 Documentation for Tor 0.2.0.x:
190 . 111: Prioritize local traffic over relayed.
191 R - Merge into tor-spec.txt.
192 - 113: mark as closed close.
193 o document the "3/4 and 7/8" business in the clients fetching consensus
195 R - then document the bridge user download timeline.
196 - HOWTO for DNSPort. See tup's wiki page.
197 . Document transport and natdport in a good HOWTO.
198 - Quietly document NT Service options: revise (or create) FAQ entry
200 =======================================================================
203 R d bug: if we launch using bridges, and then stop using bridges, we
204 still have our bridges in our entryguards section, and may use them.
205 R d add an event to report geoip summaries to vidalia for bridge relays,
206 so vidalia can say "recent activity (1-8 users) from sa".
207 R - investigate: it looks like if the bridge authority is unreachable,
208 we're not falling back on querying bridges directly?
209 R - if "no running bridges known", an application request should make
210 us retry all our bridges.
211 R - get matt to make vidalia do a getinfo status/bootstrap-phase to
212 get caught up after it connects.
213 R d Setting DirPort when acting as bridge will give false Warnings
217 o 110: avoid infinite-length circuits
218 R d 128: families of private bridges
219 - 134: handle authority fragmentation.
221 - Proposals to write:
222 R d Do we want to maintain our own set of entryguards that we use as
223 next hop after the bridge?
224 X Add an 'exit-address' line in the descriptor for servers that exit
225 from something that isn't their published address.
226 [I think tordnsel solved this. -RD]
227 - Proposal to supersede 117 by adding IPv6 support for exits and entries.
228 - Internal code support for ipv6:
229 o Clone ipv6 functions (inet_ntop, inet_pton) where they don't exist.
230 - Most address variables need to become tor_addr_t
231 - Teach resolving code how to handle ipv6.
232 - Teach exit policies about ipv6 (consider ipv4/ipv6 interaction!)
233 - 118: Listen on and advertise multiple ports:
234 - Tor should be able to have a pool of outgoing IP addresses that it is
235 able to rotate through. (maybe. Possible overlap with proposal 118.)
236 - config option to publish what ports you listen on, beyond
237 ORPort/DirPort. It should support ranges and bit prefixes (?) too.
238 (This is very similar to proposal 118.)
239 - Fix voting to handle bug 608 case when multiple servers get
241 d Possibly: revise link protocol to allow big circuit IDs,
242 variable-length cells, proposal-110 stuff, and versioned CREATES?
243 o Eliminate use of v2 networkstatus documents in v3 authority
245 N . Draft proposal for GeoIP aggregation (see external constraints *)
246 o Separate Guard flags for "pick this as a new guard" and "keep this
247 as an existing guard". First investigate if we want this.
248 . Figure out how to make good use of the fallback consensus file. Right
249 now many of the addresses in the fallback consensus will be stale,
250 so it will take dozens of minutes to bootstrap from it. This is a
251 bad first Tor experience. But if we check the fallback consensus
252 file *after* we fail to connect to any authorities, then it may
253 still be valuable as a blocking-resistance step.
254 o Write the proposal.
255 - Patch our tor.spec rpm package so it knows where to put the fallback
257 d Something for bug 469, to limit connections per IP.
258 . Put bandwidth weights in the networkstatus? So clients get weight
259 their choices even before they have the descriptors; and so
260 authorities can put in more accurate numbers in the future.
261 d Fetch an updated geoip file from the directory authorities.
263 - Tiny designs to write:
264 . Better estimate of clock skew; has anonymity implications. Clients
265 should estimate their skew as median of skew from servers over last
266 N seconds, but for servers this is not so easy, since a server does
267 not choose who it connects to.
268 - Do TLS connection rotation more often than "once a week" in the
270 (One reason not to do it more often is because the old TLS conn
271 probably has a circuit on it, and we don't really want to build up
272 dozens of TCP connections to all the other extra-stable relays.)
273 - If a relay publishes a new descriptor with a significantly lower
274 uptime or with a new IP address, then we should consider its current
275 "running" interval to have ended even if it hadn't yet failed its
276 third reachability test. the interval ended when the new descriptor
277 appeared, and a new interval began then too.
280 - Optimize cell pool allocation.
281 d Support (or just always use) jemalloc (if it helps)
283 - Look into pulling serverdescs off buffers as they arrive.
285 - Use if-modified-since to download consensuses
286 - Handle multi-core cpus better
287 - Use information from NETINFO cells
288 - Don't extend a circuit over a noncanonical connection with
290 - Learn our outgoing IP address from netinfo cells?
291 - Learn skew from netinfo cells?
293 - Better unit test coverage
294 - Refactor unit tests into multiple files
295 - Verify that write limits to linked connections work.
296 - Use more mid-level and high-level libevent APIs
301 - Get IOCP patch into libevent *
303 - Security improvements
304 - make is-consensus-fresh-enough check way tighter.
305 - If we haven't tried downloading a consensus for ages since we're tired,
306 try getting a new one before we use old descriptors for a circuit.
309 - Feature removals and deprecations:
310 - Get rid of the v1 directory stuff (making, serving, and caching)
311 - First verify that the caches won't flip out?
312 - If they will, just stop the caches from caching for now
313 - perhaps replace it with a "this is a tor server" stock webpage.
314 - The v2dir flag isn't used for anything anymore, right? If so, dump it.
315 - Even clients run rep_hist_load_mtbf_data(). Does this waste memory?
317 - Unless we start using ftime functions, dump them.
318 - can we deprecate 'getinfo network-status'?
319 - can we deprecate the FastFirstHopPK config option?
320 - Can we deprecate controllers that don't use both features?
322 Nice to have for 0.2.1.x:
324 - steven's plan for replacing check.torproject.org with a built-in
325 answer by tor itself.
328 P - Make documentation realize that location of system configuration file
329 will depend on location of system defaults, and isn't always /etc/torrc.
331 - Small controller features
332 - A status event for when tor decides to stop fetching directory info
333 if the client hasn't clicked recently: then make the onion change too.
334 - Add a status event when new consensus arrives
337 P - Figure out why dll's compiled in mingw don't work right in WinXP.
338 P - create a "make win32-bundle" for vidalia-privoxy-tor-torbutton bundle
341 - Refactor the HTTP logic so the functions aren't so large.
342 - Refactor buf_read and buf_write to have sensible ways to return
343 error codes after partial writes
344 - Router_choose_random_node() has a big pile of args. make it "flags".
345 - Streamline how we pick entry nodes: Make choose_random_entry() have
346 less magic and less control logic.
347 - Don't call time(NULL) so much; instead have a static time_t field
348 that gets updated only a handful of times per second.
349 - Move all status info out of routerinfo into local_routerstatus. Make
350 "who can change what" in local_routerstatus explicit. Make
351 local_routerstatus (or equivalent) subsume all places to go for "what
353 - deprecate router_digest_is_trusted_dir() in favor of
354 router_get_trusteddirserver_by_digest()
356 - Make Tor able to chroot itself
357 o allow it to load an entire config file from control interface
359 - log rotation (and FD passing) via control interface
360 - chroot yourself, including inhibit trying to read config file
361 and reopen logs, unless they are under datadir.
364 - Base relative control socket paths (and other stuff in torrc) on datadir.
365 - Tor logs the libevent version on startup, for debugging purposes.
366 This is great. But it does this before configuring the logs, so
367 it only goes to stdout and is then lost.
368 - Make TrackHostExits expire TrackHostExitsExpire seconds after their
369 *last* use, not their *first* use.
370 - enforce a lower limit on MaxCircuitDirtiness and CircuitBuildTimeout.
371 - Make 'safelogging' extend to info-level logs too.
372 - don't do dns hijacking tests if we're reject *:* exit policy?
373 (deferred until 0.1.1.x is less common)
374 - More consistent error checking in router_parse_entry_from_string().
375 I can say "banana" as my bandwidthcapacity, and it won't even squeak.
377 - Interface for letting SOAT modify flags that authorities assign.
378 (How to keep the authority from clobbering them afterwards?
380 Later, unless people want to implement them now:
381 - Actually use SSL_shutdown to close our TLS connections.
382 - Include "v" line in networkstatus getinfo values.
383 [Nick: bridge authorities output a networkstatus that is missing
384 version numbers. This is inconvenient if we want to make sure
385 bridgedb gives out bridges with certain characteristics. -RD]
386 [Okay. Is this a separate item, or is it the same issue as the lack of
387 a "v" line in response to the controller GETINFO command? -NM]
388 - Let tor dir mirrors proxy connections to the tor download site, so
389 if you know a bridge you can fetch the tor software.
390 - when somebody uses the controlport as an http proxy, give them
391 a "tor isn't an http proxy" error too like we do for the socks port.
392 - MAYBE kill stalled circuits rather than stalled connections. This is
393 possible thanks to cell queues, but we need to consider the anonymity
395 - Make resolves no longer use edge_connection_t unless they are actually
396 _on_ a socks connection: have edge_connection_t and (say)
397 dns_request_t both extend an edge_stream_t, and have p_streams and
398 n_streams both be linked lists of edge_stream_t.
399 - Generate torrc.{complete|sample}.in, tor.1.in, the HTML manual, and the
400 online config documentation from a single source.
401 - It would be potentially helpful to respond to https requests on
402 the OR port by acting like an HTTPS server.
403 - Make the timestamp granularity on logs configurable, with default
404 of "1 second". This might make some kinds of after-the-fact attack harder.
406 Can anybody remember why we wanted to do this and/or what it means?
407 - config option __ControllerLimit that hangs up if there are a limit
408 of controller connections already.
409 [This was mwenge's idea. The idea is that a Tor controller can
410 "fill" Tor's controller slot quota, so jerks can't do cross-protocol
411 attacks like the http form attack. -RD]
413 . Ask all directory questions to bridge via BEGIN_DIR.
414 - use the bridges for dir fetches even when our dirport is open.
415 - drop 'authority' queries if they're to our own identity key; accept
417 - give extend_info_t a router_purpose again
421 If somebody wants to do this in some version, they should:
422 - Create packages for Nokia 800, requested by Chris Soghoian
423 - More work on AvoidDiskWrites
424 - Make DNSPort support TCP DNS.
427 * * * * Roger, please sort these: * * * *
429 - bridge communities with local bridge authorities:
430 - clients who have a password configured decide to ask their bridge
431 authority for a networkstatus
432 - be able to have bridges that aren't in your torrc. save them in
434 - Consider if we can solve: the Tor client doesn't know what flags
435 its bridge has (since it only gets the descriptor), so it can't
436 make decisions based on Fast or Stable.
437 - Some mechanism for specifying that we want to stop using a cached
440 =======================================================================
445 - Our current approach to block attempts to use Tor as a single-hop proxy
446 is pretty lame; we should get a better one.
447 - Allow small cells and large cells on the same network?
448 - Cell buffering and resending. This will allow us to handle broken
449 circuits as long as the endpoints don't break, plus will allow
450 connection (tls session key) rotation.
451 - Implement Morphmix, so we can compare its behavior, complexity,
452 etc. But see paper breaking morphmix.
453 - Other transport. HTTP, udp, rdp, airhook, etc. May have to do our own
454 link crypto, unless we can bully DTLS into it.
455 - Need a relay teardown cell, separate from one-way ends.
456 (Pending a user who needs this)
457 - Handle half-open connections: right now we don't support all TCP
458 streams, at least according to the protocol. But we handle all that
459 we've seen in the wild.
460 (Pending a user who needs this)
464 - handle connect-dir streams that don't have a chosen_exit_name set.
465 - Have a "Faster" status flag that means it. Fast2, Fast4, Fast8?
466 - Add an option (related to AvoidDiskWrites) to disable directory
467 caching. (Is this actually a good idea??)
468 X Add d64 and fp64 along-side d and fp so people can paste status
469 entries into a url. since + is a valid base64 char, only allow one
470 at a time. Consider adding to controller as well.
471 [abandoned for lack of demand]
472 - Some back-out mechanism for auto-approval on authorities
473 - a way of rolling back approvals to before a timestamp
474 - Consider minion-like fingerprint file/log combination.
475 X Have new people be in limbo and need to demonstrate usefulness
476 before we approve them.
479 d Standby/hotswap/redundant hidden services: needs a proposal.
480 - you can insert a hidserv descriptor via the controller.
481 - auth mechanisms to let hidden service midpoint and responder filter
482 connection requests: proposal 121.
483 - Let each hidden service (or other thing) specify its own
487 - If the server is spewing complaints about raising your ulimit -n,
488 we should add a note about this to the server descriptor so other
489 people can notice too.
490 - When we hit a funny error from a dir request (eg 403 forbidden),
491 but tor is working and happy otherwise, and we haven't seen many
492 such errors recently, then don't warn about it.
495 - Implement missing status events and accompanying getinfos
497 - BAD_DIR_RESPONSE (Unexpected directory response; maybe we're behind
499 - BAD_PROXY (Bad http or https proxy)
500 - UNRECOGNIZED_ROUTER (a nickname we asked for is unavailable)
501 - Status events related to hibernation
502 - something about failing to parse our address?
503 from resolve_my_address() in config.c
504 - sketchy OS, sketchy threading
505 - too many onions queued: threading problems or slow CPU?
506 - Implement missing status event fields:
507 - TIMEOUT on CHECKING_REACHABILITY
508 - GETINFO status/client, status/server, status/general: There should be
509 some way to learn which status events are currently "in effect."
510 We should specify which these are, what format they appear in, and so
512 - More information in events:
513 - Include bandwidth breakdown by conn->type in BW events.
514 - Change circuit status events to give more details, like purpose,
515 whether they're internal, when they become dirty, when they become
516 too dirty for further circuits, etc.
517 - Change stream status events analogously.
518 - Expose more information via getinfo:
519 - import and export rendezvous descriptors
520 - Review all static fields for additional candidates
521 - Allow EXTENDCIRCUIT to unknown server.
522 - We need some way to adjust server status, and to tell tor not to
523 download directories/network-status, and a way to force a download.
524 - Make everything work with hidden services
526 - Performance/resources
527 - per-conn write buckets
528 - separate config options for read vs write limiting
529 (It's hard to support read > write, since we need better
530 congestion control to avoid overfull buffers there. So,
531 defer the whole thing.)
532 - Rate limit exit connections to a given destination -- this helps
533 us play nice with websites when Tor users want to crawl them; it
534 also introduces DoS opportunities.
535 - Consider truncating rather than destroying failed circuits,
536 in order to save the effort of restarting. There are security
537 issues here that need thinking, though.
538 - Handle full buffers without totally borking
539 - Rate-limit OR and directory connections overall and per-IP and
543 - Hold-open-until-flushed now works by accident; it should work by
545 - Display the reasons in 'destroy' and 'truncated' cells under
547 - Make router_is_general_exit() a bit smarter once we're sure what
549 - Automatically determine what ports are reachable and start using
550 those, if circuits aren't working and it's a pattern we
551 recognize ("port 443 worked once and port 9001 keeps not
555 - some better fix for bug #516?
558 - Servers might check certs for known-good ssl websites, and if
559 they come back self-signed, declare themselves to be
560 non-exits. Similar to how we test for broken/evil dns now.
561 - Authorities should try using exits for http to connect to some
562 URLS (specified in a configuration file, so as not to make the
563 List Of Things Not To Censor completely obvious) and ask them
564 for results. Exits that don't give good answers should have
565 the BadExit flag set.
566 - Alternatively, authorities should be able to import opinions
567 from Snakes on a Tor.
568 - Bind to random port when making outgoing connections to Tor servers,
569 to reduce remote sniping attacks.
570 - Audit everything to make sure rend and intro points are just as
571 likely to be us as not.
572 - Do something to prevent spurious EXTEND cells from making
573 middleman nodes connect all over. Rate-limit failed
574 connections, perhaps?
575 - DoS protection: TLS puzzles, public key ops, bandwidth exhaustion.
578 - Now that we're avoiding exits when picking non-exit positions,
579 we need to consider how to pick nodes for internal circuits. If
580 we avoid exits for all positions, we skew the load balancing. If
581 we accept exits for all positions, we leak whether it's an
582 internal circuit at every step. If we accept exits only at the
583 last hop, we reintroduce Lasse's attacks from the Oakland paper.
585 - Windows server usability
586 - Solve the ENOBUFS problem.
587 - make tor's use of openssl operate on buffers rather than sockets,
588 so we can make use of libevent's buffer paradigm once it has one.
589 - make tor's use of libevent tolerate either the socket or the
590 buffer paradigm; includes unifying the functions in connect.c.
591 - We need a getrlimit equivalent on Windows so we can reserve some
592 file descriptors for saving files, etc. Otherwise we'll trigger
593 asserts when we're out of file descriptors and crash.
596 - a way to generate the website diagrams from source, so we can
597 translate them as utf-8 text rather than with gimp. (svg? or
599 . Flesh out options_description array in src/or/config.c
600 . multiple sample torrc files
601 - Refactor tor man page to divide generally useful options from
603 - Add a doxygen style checker to make check-spaces so nick doesn't drift
604 too far from arma's undocumented styleguide. Also, document that
605 styleguide in HACKING. (See r9634 for example.)
606 - exactly one space at beginning and at end of comments, except i
607 guess when there's line-length pressure.
608 - if we refer to a function name, put a () after it.
609 - only write <b>foo</b> when foo is an argument to this function.
610 - doxygen comments must always end in some form of punctuation.
611 - capitalize the first sentence in the doxygen comment, except
613 - avoid spelling errors and incorrect comments. ;)
616 - The Debian package now uses --verify-config when (re)starting,
617 to distinguish configuration errors from other errors. Perhaps
618 the RPM and other startup scripts should too?
619 - add a "default.action" file to the tor/vidalia bundle so we can
620 fix the https thing in the default configuration:
621 http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#PrivoxyWeirdSSLPort
624 =======================================================================
626 Documentation, non-version-specific.
628 - Mark up spec; note unclear points about servers
629 NR - write a spec appendix for 'being nice with tor'
630 - Specify the keys and key rotation schedules and stuff
631 . Finish path-spec.txt
632 - Mention controller libs someplace.
633 - Remove need for HACKING file.
634 - document http://wiki.noreply.org/noreply/TheOnionRouter/TransparentProxy on freebsd and osx
635 P - figure out why x86_64 won't build rpms from tor.spec
636 P - figure out rpm spec files for bundles of vidalia-tor-polipo
637 P - figure out polipo install scripts for bundles of vidalia-tor-polipo on osx, win32
638 - figure out selinux policy for tor
639 P - change packaging system to more automated and specific for each
640 platform, suggested by Paul Wouter
641 P - Setup repos for redhat and suse rpms & start signing the rpms the
642 way package management apps prefer
645 J . tor-in-the-media page
646 P - Figure out licenses for website material.
647 (Phobos reccomends the Open Publication License with Option A at
648 http://opencontent.org/openpub/)
649 P - put the logo on the website, in source form, so people can put it on
650 stickers directly, etc.
651 P - put the source image for the stickers on the website, so people can
653 P - figure out a license for the logos and docs we publish (trademark
655 (Phobos reccomends the Open Publication License with Option A at
656 http://opencontent.org/openpub/)
657 P - ask Jan/Jens to be the translation coordinator? add to volunteer page.
658 I - add a page for localizing all tor's components.
659 - It would be neat if we had a single place that described _all_ the
660 tor-related tools you can use, and what they give you, and how well they
661 work. Right now, we don't give a lot of guidance wrt
662 torbutton/foxproxy/privoxy/polipo in any consistent place.
663 P - create a 'blog badge' for tor fans to link to and feature on their
664 blogs. A sample is at http://interloper.org/tmp/tor/tor-button.png
665 - More prominently, we should have a recommended apps list.
666 - recommend pidgin (gaim is renamed)
667 - unrecommend IE because of ftp:// bug.
668 - Addenda to tor-design
669 - we should add a preamble to tor-design saying it's out of date.
670 - we should add an appendix or errata on what's changed.
673 - make a mailing list with the mirror operators
674 o make an automated tool to check /project/trace/ at mirrors to
675 learn which ones are lagging behind.
676 - auto (or manually) cull the mirrors that are broken; and
677 contact their operator?
678 - a set of instructions for mirror operators to make their apaches
679 serve our charsets correctly, and bonus points for language
681 - figure out how to load-balance the downloads across mirrors?
682 - ponder how to get users to learn that they should google for
683 "tor mirrors" if the main site is blocked.
684 - find a mirror volunteer to coordinate all of this