[tor-bugs] #12903 [Pluggable transport]: Integrate obfs4proxy into the TBB bundle.

[Tor Bug Tracker & Wiki]

#12903: Integrate obfs4proxy into the TBB bundle.
-------------------------------------+------------------------
     Reporter:  yawning              |      Owner:  yawning
         Type:  task                 |     Status:  new
     Priority:  normal               |  Milestone:
    Component:  Pluggable transport  |    Version:
   Resolution:                       |   Keywords:  obfs4, tbb
Actual Points:                       |  Parent ID:  #12130
       Points:                       |
-------------------------------------+------------------------

Comment (by yawning):

 Ok, per discussion in IRC and #12130 2 bridges may be enough for now for
 the branch to get merged.

 Current issues:
  * I'm not sure if I want to be in the default TBB bridge business, but
 it's easy to remove my bridge as long as it's before we deploy this right?
  * As noted by dcf, obfs4proxy currently uses SOCKS4a.  I changed the
 default obfs2/obfs3 providers from obfsproxy (python) to obfs4proxy for
 testing purposes, so that may need to be reverted if people use those with
 IPv6 (alternatively, my #12535 goptlib branch should be good to go, but
 won't get merged till it sees field testing in a TBB alpha).  Using
 obfs4proxy where possible would be better because it implements the
 PT_PROXY stuff without py2exe brain damage.

 gk I assume you're going to squash the branch if/when you merge it?
 Having a billion wip commits probably is neither useful nor interesting
 (apart from documenting my struggles with gitian for posterity).  I could
 make a squashed branch as well.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12903#comment:11>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online