wiki:org/sponsors/SponsorF/November2011

Version 12 (modified by karsten, 6 years ago) (diff)

Update status of November deliverables.

Deliverable List for Sponsor F, November 1, 2011

Note that November 1, 2011 is the date when we need a status update which of the deliverables are done or what's missing to complete them. But not all deliverables on this page are due November 1, 2011:

  • Some deliverables should be finished much earlier, because we already promised them for May or June.
  • Some deliverables are due November 1.
  • Some deliverables are due November 30, but we should have a very good intuition whether we'll finish them on time by November 1.

Which due date belongs to which deliverable is written below.

Analysis

  • Comparison of datagram Tor designs
    • Not done: We need to compare existing UDP designs (#1855), figure out what we want to do and why it's the right thing to do. This may require bringing researchers together and discussing their approaches, which in turn requires coordination on Tor side. Due date was May 1. [sjmurdoch]
  • Why else is Tor slow?
    • Not done: We should write a draft as a follow-up to performance.pdf. Due date is November 1. [arma]
  • Analysis for increasing the set of guards
    • Partially done: We wrote a blog post containing the research questions. Next step is to find a grad student to start answering them. Due date is November 1. [arma]
  • Security tradeoffs from using a SOCKS proxy vs. a bridge
    • Not done: We should write a blog post about these possible tradeoffs (#2764, #3292). Due date was June 1. [arma]
  • Preventing relays from enumerating bridges
    • Not done: We need to assess options for preventing relays from enumerating bridges. We should analyze security of bridge users using guard-flagged relays for their middle hop, or of bridges forcing an entry guard as an extra hop. Due date is November 30. [arma]
  • FC paper proposing adaptive bridge address distribution
    • Not done: We should write a summary of the paper, point out why it's so exciting, but then list open research questions. Due date is November 30. [arma]
  • Bridge descriptor retrieval and storage
    • Not done: Write a patch for Tonga to include daily statistics about bridge server descriptor downloads in its extra-info descriptors. These statistics should include total requests per day and number of unique bridges of which server descriptors were requested. Due date is November 30. [Sebastian]
    • Not done: Write a blog post comparing different bridge usage requirements from only using bridges by IP address to updating descriptors from Tonga. Due date is November 30. [Sebastian]
    • Not done: Write a proposal to store information about bridges in a client's state file. Optionally, write a proposal to retrieve descriptors from Tonga. Due date is November 30. [Sebastian]
  • Analysis of passive bridge reachability data
    • Not done: We already promised to make progress on this for sponsor E for September 15. Due date for sponsor F is November 30. [karsten]
  • Bridge churn analysis
    • Not done: We could do an analysis similar to the Guard/Stable flag analysis for relays, but for stable bridges (#2794, #2911). Due date is November 30. [karsten]
  • Censorship detector
    • Not done: George Danezis wrote a censorship detector that analyzes daily user numbers and detects unusual up- or downturns (#2718). Needs fine-tuning. Due date is November 30. [karsten]

Tor Client

  • Tor 0.2.2.x stable release
    • Done: We have a stable release (#3032). Due date was June 1. [nickm and arma]
  • Eliminate TLS renegotiation
    • Not done: We should get rid of TLS renegotiation to make Tor traffic stand out less. In theory, this is due November 30, but we should finish it much earlier. [nickm]
  • Alternate crypto ops backward-compatibly
    • Status unknown. Due date is November 30. [nickm]

Tor Relay

  • Microdescriptor roll-out for client-side
    • Done: We also promised to make progress on this for sponsor D for August 31 (#1748). Due date for sponsor F was May 1. [nickm]
  • Libevent2 working for Windows bundles
    • Not done: We also promised to make progress on this for sponsor D for August 31 (#2007). Due date for sponsor F was June 1. [nickm]
  • UPnP working without Vidalia
    • Done: We already promised to make progress on this for sponsor D for August 31. Due date for sponsor F is November 30. [sjmurdoch]
    • Ongoing: We may have to fork the UPnP library as the release management practice is rather poor. [sjmurdoch]
  • PMP for port forwarding in Tor or Vidalia
    • Not done: Need to investigate PMP libraries. See tor-fw-helper, incl. #1983. The work on UPnP in Tor will solve part of making PMP in Tor, too. Due date is November 30. [sjmurdoch]
    • Ongoing: We may have to fork the NAT PMP library as the release management practice is rather poor. [sjmurdoch]

Tor Bridge

  • Bridges on IPv6
    • Not done: We need to review and merge Fuzzel's patch or start from scratch. Due date is November 30. [nickm]

Tor bundles/installation

  • Bridge-by-default bundles
    • Done: See "Unstable Bridge-by-Default Vidalia Bundle" on the download page. [erinn]

Pluggable transport

  • Support camouflaged transport
    • Done: We need a proposal for a modular transport spec. Due date was March 15. (#2758) [nickm]
    • Done: We need proof-of-concept transport plugins (for team use; not required for use by user in country): http headers (#2759) and superencryption (#2760). Due date was June 1. [nickm]
    • Not done: Implement all of the tor-side parts of Proposal 180 in order to make proxies easy to configure. Due date is November 30. [nickm with asn]
    • Not done: We should prepare a bundle that includes obfsproxy and get actual users using it. Due date is November 30. [nickm]

Torflow

  • Bandwidth authority improvements
    • Not done: Better tracking for measurement feedback (#1976). Due date is November 1. [mikeperry]
    • Not done: Upgrade the bwscanners to the new SQLALchemy release (#2391). Due date was June 30. [mikeperry]
    • Not done: Help aagbsn understand system and write a bwscanner spec (#2861). Due date was June 30. [mikeperry]
    • Not done: Set up a 5th scanner (#1778). Due date was June 30. [mikeperry]

BridgeDB

  • BridgeDB spec
    • Done: We have a BridgeDB spec draft (#1606). Due date is November 30. [karsten]

Torbutton

  • Firefox Mobile release of Torbutton
    • Not done: Unsure what's required here (#1506). Due date was June 1. [mikeperry]
  • Stable release of Torbutton (#3071)
    • Done: Torbutton 1.4.0 is out. Due date was June 30. [mikeperry]
  • Chrome
    • Ongoing: Continue to keep in touch with Chrome folks (#1770, #1816, #1925, #2956, #3072). "Due date" was June 30. [mikeperry]
  • Fork Firefox 4 for Tor Browser Bundle
    • Status unknown. Due date is November 30. [mikeperry]
  • CSS Font fixes
    • Not done: #2872. Due date is November 30. [mikeperry]
  • CSS media query/resolution fixes
    • Not done: #2875. Due date is November 30. [mikeperry]

Tor Cloud

  • Experiments with change-my-IP interface
    • Not done: We need to perform experiments on cloud images, e.g., using the change-my-IP interface (#3606). Does it work? What does it cost? Are there other interesting issues? Due date was June 1. [Runa]