Opened 5 years ago

Closed 5 years ago

#14919 closed defect (fixed)

Update the obfs4proxy tag, and use it as the ScrambleSuit PT provider.

Reported by: yawning Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Keywords: TorBrowserTeam201502R, GeorgKoppen201502R
Cc: gk Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


obfs4proxy-0.0.4 is out now.

This means:

  • The old go.crypto stuff in the build can be removed.
  • obfs4proxy can/should be used as the ClientTransportPlugin for scramblesuit.

Ideally I'd like to see this in the next Tor Browser alpha so the code gets more testing, and I will attach a branch that does all of these things. Note that while obfsproxy is no longer referenced from any of the PT torrcs, it is still needed as a run time dependency for FTE.

Child Tickets

Change History (4)

comment:1 Changed 5 years ago by yawning

Status: newneeds_review

That branch should do the right thing. It's split into two commits, one for "use latest obfs4proxy, remove old library", and one for "use obfs4proxy for scramblesuit".

comment:2 Changed 5 years ago by gk

Keywords: GeorgKoppen201502R added

comment:3 Changed 5 years ago by gk

Status: needs_reviewneeds_revision

Using Scramblesuit does not work anymore (the "XXX" were done by myself):

Feb 18 09:40:28.000 [warn] We were supposed to connect to bridge 'XXX.XXX.XXX.XXX:XXX' using pluggable transport 'scramblesuit', but we can't find a pluggable transport proxy supporting 'scramblesuit'. This can happen if you haven't provided a ClientTransportPlugin line, or if your pluggable transport proxy stopped running.
Feb 18 09:40:28.000 [warn] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Can't connect to bridge; PT_MISSING; count 1; recommendation warn)

A build without your patches is still working fine.

comment:4 Changed 5 years ago by gk

Resolution: fixed
Status: needs_revisionclosed

This was a bug in my build environment, sorry. Merged in commit c268ca1dab6a1dbcd106da29c47390c9d834b420.

Note: See TracTickets for help on using tickets.