[tor-bugs] #13665 [Website]: Update the obfsbridge setup instructions on the website

[Tor Bug Tracker & Wiki]

#13665: Update the obfsbridge setup instructions on the website
-------------------------+-----------------------
     Reporter:  asn      |      Owner:  Sebastian
         Type:  task     |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Website  |    Version:
   Resolution:           |   Keywords:
Actual Points:           |  Parent ID:
       Points:           |
-------------------------+-----------------------

Comment (by asn):

 Replying to [comment:2 yawning]:
 > Sure, this is a good idea.
 >
 > I'm not sure about how the Debian specific parts of this works, is "apt-
 get install obfs4proxy" sufficient (I know that both Debian's and our repo
 have the package)?
 >

 Hm, I think you will probably want to use Tor's debian repository, since
 looking at:
 https://packages.debian.org/search?keywords=obfs4proxy
 it seems that there is no obfs4proxy package for Debian stable.

 We also need to revisit this page:
 https://www.torproject.org/projects/obfsproxy-instructions.html.en
 for non-Debian instructions for obfs4proxy.

 And also this page:
 https://www.torproject.org/docs/pluggable-transports.html.en
 to add a "How to setup an obfsbridge" section that links to our
 instructions.

 > Basic obfs4 deployment would be something like:
 > {{{
 > SocksPort 0
 > ORPort 443 # or some other port if you already run a webserver/skype
 > BridgeRelay 1
 > Exitpolicy reject *:*
 > ExtORPort auto
 >
 > ## CHANGEME_1 -> provide a nickname for your bridge, can be anything you
 like
 > #Nickname CHANGEME_1
 > ## CHANGEME_2 -> provide some email address so we can contact you if
 there's a problem
 > #ContactInfo CHANGEME_2
 >
 > ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy
 > }}}
 >
 > (Optionally) For people that want to run both obfs3 and obfs4, the last
 line should read as:
 > {{{
 > ServerTransportPlugin obfs3,obfs4 exec /usr/bin/obfs4proxy
 > }}}
 >
 > I assume to avoid user confusion we should just entirely replace
 obfsproxy with obfs4proxy in our instructions till otherwise needed (NB:
 obfs4proxy packages only exist for i386/amd64 and ARM).
 >

 I think that makes sense. Since obfs4proxy supports obfs3 and obfs4 we
 should be fine.

 > Would this also be the place to document how to use `capabilities(7)`
 and `ServerTransportListenAddr` to run the obfs4 bridge on reserved ports
 (eg: 443)?
 >

 Hm, maybe. But in a different section.
 Or maybe put that in the wiki and link to the wiki?
 Up to you.

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