Prepare a Pluggable Transports Bundle
This ticket is about preparing a Pluggable Transports Tor Bundle (PTTB, for now)that end users can download and run effortlessly.
Some thoughts on how the PTTB should look like:
Bridge-side
I imagine that a bridge-side PTTB will need a tor version that supports managed proxies, and contains the fix for #4725 (moved) and #4865 (moved).
I suppose that PTTB will contain an obfsproxy binary in its root directory, and then inside the premade torrc there will be a line that references and launches it with obfs2, like this:
ServerTransportPlugin obfs2 exec ../../obfsproxy --managed
Ideally then, Vidalia will pick up the log line (or even better we should export this information using the control protocol) that says in which port obfsproxy is listening, and display it to the bridge operator so that he can give it to his/her users. The log line currently looks like this:
Registered server transport 'obfs2' at '0.0.0.0:42666'
Client-side
A client-side PTTB simply needs a tor version that supports managed proxies (over 0.2.3.10).
obfsproxy will again be placed in the root directory of PTTB (or somewhere around there), and the premade torrc should reference it with a ClientTransportPlugin line, like this:
ClientTransportPlugin obfs2 exec ../../obfsproxy --managed
Then, Vidalia should have some sort of graphical way of adding obfs2'ed bridges that end-users will do. Such bridge lines in torrc usually look like this:
Bridge obfs2 192.0.2.1:42666
BTW, I don't really know how TBB works internally, so my thoughts above might not be realistic.