[tor-dev] Sponsor F: update; next meeting [in *two weeks*]

Ximin Luo infinity0 at gmx.com
Mon Oct 14 20:14:25 UTC 2013

On 01/10/13 03:13, Tom Lowenthal wrote:
> Combine obfuscation (obfsproxy) with address-diversity (flashproxy) [#11]
> -------------------------------------------------------------------
> **[On Track: Minimal]** The work of integrating obfsproxy with
> flashproxy is done. George will include this in the next released
> version of the pluggable transports browser bundle. George will also
> write a report on this work. Ximin and David will help. By Halloween,
> the report will be complete and the bundles will either be released or
> well on their way through testing. This likely represents some
> combination of minimal or intended outcomes for this deliverable.

We have deployed and tested working instances of the combined obfs3/flashproxy transport. This includes all components - the client, server, facilitator and browser proxy - and they are all backwards compatible with the old components that only support the plain (non-obfs3) websocket protocol. Soon (this week) the code will be merged. There are a few other issues to iron out before a production-quality release. We may be able to do it by Halloween, but I'd prefer not to rush through them just to make that date (if that is fine for the sponsor). I'm more certain it will be production-quality sometime mid-November.

I haven't considered PTBB packaging and I'm not sure about the work needed, but if George does this in parallel with me making the code production-quality, the timings should line up as expected.

Specific remaining tasks:

- merge #9349, #6810, #9974
- push #7167 to an official tpo repo
- do #9976, and #7167#comment:42 might require an obfsproxy fix

Other less-vital things which improve robustness/quality:

- connection reliability under churn: #9964, #5426, #8285
- flexibility of ecosystem: #9942, #9949, #9965
- various other code-quality issues, all on trac, see [1]

We've also made progress on the long-term goal of general PT composition, mentioned in the the intended/ideal outcomes, as #9744:

- solid and complete ideas in place
- start of precise design specs
- can now see a full path to eventual implementation

[1] Full list of tickets; though about half are not relevant to this deliverable.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 897 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20131014/bf1186ca/attachment.sig>

More information about the tor-dev mailing list