Phase One: Ramp up.
September 15, 2010 - March 15, 2011.
Currently a mix of brainstorming and deliverables. Needs tickets for each task and sub-task to track progress. Master ticket is (#2277).
- Create, collate, produce educational materials about Internet censorship and using Tor for circumvention. (Karen, partner) (#2272)
- Training materials and sessions for train the trainers. Pull from the educational materials. (Karen, partner, Andrew, Jacob) (#2273)
- Full translation of all materials, software documentation, and interfaces into target languages. (Runa, Andrew) (#2274) and (#2275)
- Recruiting bridges and relays:
- Hardware Tor router and access point (Jacob, partner) 1. 20 test relays/bridges (get 20 technical people to run these devices for prototyping and feedback) (#2269) 1. openwrt-based image (#2270) 1. updates (automated via hudson?) (#2278) 1. find the hardware we like and figure out flash image (#2271) 1. thinking down the line: mba class - social business opportunity; we've done the base OS/image, you figure out the logistics, sales, marketing, and support problems 1. vendor support: buffalo, fon, linksys help? (#2276)
- Anonymizing LiveCD/LiveUSB with Tor (Jacob, partner) 1. pidgin, otr, claws, firefox w/torbutton, gpg, transparent proxy, vlc, encrypted homedir 1. support: ubuntu org supported, LTS edition? xubuntu for minimal hardware requirement? talk to ubuntu org 1. distribution: cd dist/shipping, download iso, packages/scripts in official ubuntu repos, WUBI
- Cloud computing images: Amazon, Rackspace, other? (Runa, partner) 1. dyc.edu ramdisk based? 1. ubuntu server on amazon cloud image (#3033) 1. rackspace? identify other cloud providers?
- Map out IPv6 challenges and possible solutions to making Tor compatible. (#2538) (Nick, Roger, Sebastian)
- Communications 1. branding/video explaining what a bridge/relay/exit relay means and why you should care 1. risks of a relay in some sort of wording to explain that unless you are an exit, everything is encrypted and anonymous 1. being a non-exit relay is less risky than reading a pdf or playing a flash game/video 1. figure out how to garner support for exit relays, counter chilling effects, sort out individuals who are likely to want to run exit relays
- Develop and iterate a propagation strategy. How to get content, software, and materials into the hands of those who need them? How to anonymously measure success? (Andrew, partner)
1. ip space allocation:
- map changing ip addresses to tor relays/bridges others run
- better use your unallocated ip space before ARIN takes it away
- anycast tor bridges?
- instrument tor to figure out metrics from ip addresses
- ipv6/v4 tunnels from ipv6 ranges to tor relays/bridges
- Tracking of Bridge reachability. Investigate five directions: (Nick, Roger, Karsten)
- passive scanning from bridge self-reporting. How good can we get at recognizing that a bridge has become blocked by looking at the stats it reports? (Karsten)
- active scanning from within various countries. Nick points out that we should throw in some decoy addresses too. (Andrew, Kaner)
- client self-reporting? In theory the client could use its other bridges to tell us that a given bridge isn't working anymore.
- DNS reflector idea (Roger)
- Bridge tests its reachability to baidu (and/or some other consensus-specified destination) and publishes that reachability test in its extrainfo descriptor. (#1851, #2576)
- Increasing the total number of bridges and relays. (Steven, Erinn, partner)
- bridge by default bundles. setup vidalia.conf to work as a bridge by default. if it works, great. if not, no sweat.
- relays by default bundles. setup vidalia.conf to work as a non-exit relay by default. if it works, great. if not, no sweat.
- spread bundles into various communities (partner)
- think about better user feedback to users who successfully run a bridge/relay. 1. list countries of users who have used your bridge (nickm, vidalia) 1. update vidalia interface to reflect this information and if zero users, explain possibilites
- Real time information on internet censorship (Jacob, Johnathan, partner)
- Guidance on ‘how best to address censorship’ manual (Andrew, partner)
- how to interpret the source data collected and reported from number 8?
- how do users use this data to change their actions?