Opened 8 years ago

Closed 8 years ago

#2758 closed enhancement (implemented)

Proposal for modular transport spec

Reported by: arma Owned by: tomb
Priority: High Milestone: Deliverable-Mar2011
Component: Obfuscation/Pluggable transport Version:
Severity: Keywords:
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


We're working on a pair of transport proxies for Tor that will make it harder to fingerprint by traffic content. We should generalize the way that Tor launches these proxies, and the way that we describe them in bridge address lines, so other people can make new proxies down the road and Tor will be able to handle them automatically.

Child Tickets

Change History (7)

comment:1 Changed 8 years ago by arma

Status: newneeds_review

Nickm added the rest of the first draft of the proposal last week:

Now it needs review.

Also, we should compare the trajectories for the http headers design (#2759), the obfsproxy design (#2760), and the triangle boy design (#2468) to make sure they are compatible with this spec.

comment:2 Changed 8 years ago by arma

Priority: normalmajor

comment:3 Changed 8 years ago by nickm

I'm going to actually give the thing a final readability-and-consistency edit today.

My main worry is that it is needlessly complex in some way. But I think I've outlined a way in the "implementation plan" section to explain how to build the minimal bits first and see how much the complicated bits are needed.

comment:4 Changed 8 years ago by arma

Component: Tor ClientPluggable transport

comment:5 Changed 8 years ago by arma

comment:6 Changed 8 years ago by tomb

Owner: set to tomb
Status: needs_reviewaccepted

I will review this proposal

comment:7 Changed 8 years ago by arma

Resolution: implemented
Status: acceptedclosed

This first go at the proposal is in. I'm going to close this trac entry.

(Closing of the trac entry is orthogonal to whether further people review it.)

Note: See TracTickets for help on using tickets.