projects/en/obfsproxy-debian-instructions.wml (44af79ab5) - tor-webwml.git

obfsproxy-debian-instructions.wml

## translation metadata
# Revision: $Revision$
# Translation-Priority: 4-optional

#include "head.wmi" TITLE="obfsproxy: Setting up an Obfsproxy Bridge on Debian/Ubuntu" CHARSET="UTF-8"

<div id="content" class="clearfix">
  <div id="breadcrumbs">
    <a href="<page index>">Home &raquo; </a>
    <a href="<page projects/projects>">Projects &raquo; </a>
    <a href="<page projects/obfsproxy>">obfsproxy</a>
  </div>
  <div id="maincol">

<h1 id="instructions">Setting up an Obfsproxy Bridge on Debian/Ubuntu</h1>

<p>
    This guide will help you set up an obfuscated bridge on a Debian/Ubuntu system.
    </p>

<h3>Step 0: Move to the development version of Tor</h3>
    <br>

<p>
    Add the <a href="<page docs/debian>#development">development Tor
    APT repository</a> and run the specified commands to install tor
    and deb.torproject.org-keyring. You need Tor 0.2.4.x Tor because
    it knows how to automatically report your obfsproxy address to <a
    href="https://bridges.torproject.org/?transport=obfs2">BridgeDB</a>.
    </p>

<h3>Step 1: Install obfsproxy</h3>
    <br>

<pre style="margin: 1.5em 0 1.5em 2em">
\# apt-get install obfsproxy
    </pre>

<p>
    Obfsproxy requires libevent2. If your distribution
    (e.g. Debian squeeze) doesn't include it,
    you can get the libevent-2.0 package from the <a
    href="http://backports-master.debian.org/Instructions/">backports</a>
    repository.
    </p>

<h3>Step 2: Configure Tor</h3>
    <br>

<p>
    Edit your <i>/etc/tor/torrc</i> to add:
    </p>

<pre style="margin: 1.5em 0 1.5em 2em">
SocksPort 0
ORPort 443 # or some other port if you already run a webserver/skype
BridgeRelay 1
Exitpolicy reject *:*

\## 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 obfs2 exec /usr/bin/obfsproxy --managed
    </pre>

<p>
    Don't forget to edit the <i>CHANGEME</i> fields!
    </p>

<h3>Step 3: Launch Tor and verify that it bootstraps</h3>
    <br>

<p>
    Restart Tor to use the new configuration file.
    (Preface with sudo if needed.)
    </p>

<pre style="margin: 1.5em 0 1.5em 2em">
service tor restart
    </pre>

<p>
    Now check <i>/var/log/tor/log</i> and you should see something
    like this:
    </p>

<pre style="margin: 1.5em 0 1.5em 2em">
Nov 05 16:40:45.000 [notice] We now have enough directory information to build circuits.
Nov 05 16:40:45.000 [notice] Bootstrapped 80%: Connecting to the Tor network.
Nov 05 16:40:46.000 [notice] Bootstrapped 85%: Finishing handshake with first hop.
Nov 05 16:40:46.000 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Nov 05 16:40:48.000 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Nov 05 16:40:48.000 [notice] Bootstrapped 100%: Done.
    </pre>

<p>
    If Tor is earlier in the bootstrapping phase, wait till it gets to
    100%.
    </p>

<h3>Step 4: Set up port forwarding if needed</h3>
    <br>

<p>
    If you're behind a NAT/firewall, you'll need to make your bridge
    reachable from the outside world &mdash; both on the ORPort and
    the obfsproxy port. The ORPort is whatever you defined in step two
    above. To find your obfsproxy port, check your Tor logs for a line
    similar to this one:
    </p>

<pre style="margin: 1.5em 0 1.5em 2em">
Oct 05 20:00:41.000 [notice] Registered server transport 'obfs2' at '0.0.0.0:26821
    </pre>

<p>
    The last number, in this case <i>26821</i>, is the TCP port number
    that you need to forward through your firewall. (This port is randomly
    chosen the first time Tor starts, but Tor will cache and reuse the
    same number in future runs.)
    </p>

</div>
  
  <div id = "sidecol">
#include "side.wmi"
#include "info.wmi"
  </div>
  
</div>

#include <foot.wmi>

tor-webwml.git

fix backports directions per dcf's suggestion