Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#5059 closed task (implemented)

Organize an obfsproxy/PTTB test run

Reported by: asn Owned by: asn
Priority: Medium Milestone:
Component: Circumvention/Pluggable transport Version:
Severity: Keywords:
Cc: arma, karsten, ln5, mo, marlowe Actual Points:
Parent ID: #5038 Points:
Reviewer: Sponsor:


karsten and arma were considering an obfsproxy testrun, where a
client-PTTB (#4927) would be deployed, configured with hardcoded
obfs2'ed bridges.

This should get us some bug reports on obfsproxy, some usability
comments from end-users, and help us figure out #5038 and other
performance-related questions.

The initial plan was to setup an obfsproxy in moria, but I believe
it's a better idea to setup obfsproxy in less sensitive boxes [0].

This is a ticket to coordinate this effort.

#5047 is also important, to gather statistics and see approximately
how many users used pluggable transports during the testing period.

We should also decide how many bridges to hardcode. Do we actually
need more than one? I know that gamambel, marlowe and ln5 are
interested in setting up obfsproxy. Still, I think that the original
idea of a single bridge is better, so that we can get better answers
for #5038. If too many users use the bundle, we can then add more
bridges. So, who gets to setup the PTTB obfsproxy?

There are probably easier ways of compromising computers than
exploiting obfsproxy security bugs, but I will be feeling better if
obfsproxy-beta is not touching a directory authority.

Child Tickets

Change History (3)

comment:1 Changed 9 years ago by asn

Parent ID: #5038

comment:2 Changed 9 years ago by rransom

Resolution: implemented
Status: newclosed

We're having a test run now! (Too bad we didn't get to organize it.)

comment:3 Changed 9 years ago by nickm

After the "test run" is done, we should do a quick pass over "pluggable transports need XYZ" tickets and "obfsproxy needs XYZ" tickets, to see which of them turned out to actually be not so crucial as expected.

Note: See TracTickets for help on using tickets.