deleted file mode 100644

@@ -1,150 +0,0 @@

-## 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">

-

-    <!-- PUT CONTENT AFTER THIS TAG -->

-

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

-

-    <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a>

-

-    <p>

-    <img width="7%" height="7%" style="float: left;" src="$(IMGROOT)/icon-Obfsproxy.jpg">

-    <b> Hey! </b>

-    If you are <b>not</b> using Debian or Ubuntu, you better look

-    <a href="<page projects/obfsproxy-instructions>">at this other guide</a>

-    which sets up Obfsproxy from source.

-    </p>

-    <br><br>

-

-

-    <p>

-      This is a <b>Debian/Ubuntu</b> guide for installing the Python

-      version of obfsproxy. If you are still using the C version, we

-      recommend you to upgrade to the Python version!

-    </p>

-

-    <h3>Step 0: Install a recent version of Tor (>= 0.2.4.1)</h3>

-    <br>

-

-    <p>

-    Add the <a href="<page docs/debian>#ubuntu">official Tor

-    APT repository</a> and run the specified commands to install <code>tor</code>

-    and <code>deb.torproject.org-keyring</code>. You need <em>Tor 0.2.4.x</em> because

-    it knows how to automatically report your obfsproxy address to <a

-    href="https://bridges.torproject.org/?transport=obfs3">BridgeDB</a>.

-    </p>

-

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

-    <br>

-

-    <p>

-    Since you installed the Tor APT repository, installing obfsproxy is now a matter of running a command:

-    </p>

-

-    <pre style="margin: 1.5em 0 1.5em 2em">

-\# apt-get install obfsproxy

-    </pre>

-

-    <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 auto

-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 obfs3 exec /usr/bin/obfsproxy managed

-    </pre>

-

-    <p>

-    Don't forget to uncomment and 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 until 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 — both on the ORPort and

-    the obfsproxy ports. The ORPort is whatever you defined in step two

-    above. To find your obfsproxy ports, 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 'obfs3' at '0.0.0.0:42000

-    </pre>

-

-    <p>

-    The last number in each line, in this case <i>26821</i> and

-    <i>42000</i>, is the TCP port number that you need to forward

-    through your firewall. (The ports are randomly chosen the first

-    time Tor starts, but Tor will cache and reuse the same number in

-    future runs.) If you want to change the number, use Tor

-    0.2.4.7-alpha or later, and set something similar to

-    "ServerTransportListenAddr obfs3 0.0.0.0:26821" in your torrc.

-    </p>

-

-  </div>

-  <!-- END MAINCOL -->

-  <div id = "sidecol">

-#include "side.wmi"

-#include "info.wmi"

-  </div>

-  <!-- END SIDECOL -->

-</div>

-<!-- END CONTENT -->

-#include <foot.wmi>

-

@@ -65,7 +65,7 @@

     <pre style="margin: 1.5em 0 1.5em 2em">

 SocksPort 0

-ORPort 443 # or some other port if you already run a webserver/skype

+ORPort auto

 BridgeRelay 1

 Exitpolicy reject *:*

@@ -42,7 +42,7 @@

     APT repository</a> and run the specified commands to install <code>tor</code>

     and <code>deb.torproject.org-keyring</code>. You need <em>Tor 0.2.4.x</em> because

     it knows how to automatically report your obfsproxy address to <a

-    href="https://bridges.torproject.org/?transport=obfs2">BridgeDB</a>.

+    href="https://bridges.torproject.org/?transport=obfs3">BridgeDB</a>.

     </p>

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

@@ -124,7 +124,6 @@ Nov 05 16:40:48.000 [notice] Bootstrapped 100%: Done.

     </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

 Oct 05 20:00:41.000 [notice] Registered server transport 'obfs3' at '0.0.0.0:42000

     </pre>

@@ -135,7 +134,7 @@ Oct 05 20:00:41.000 [notice] Registered server transport 'obfs3' at '0.0.0.0:420

     time Tor starts, but Tor will cache and reuse the same number in

     future runs.) If you want to change the number, use Tor

     0.2.4.7-alpha or later, and set something similar to

-    "ServerTransportListenAddr obfs2 0.0.0.0:26821" in your torrc.

+    "ServerTransportListenAddr obfs3 0.0.0.0:26821" in your torrc.

     </p>

   </div>

@@ -74,7 +74,7 @@ Exitpolicy reject *:*

 \## CHANGEME_2 -> provide some email address so we can contact you if there's a problem

 \#ContactInfo CHANGEME_2

-ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed

+ServerTransportPlugin obfs3 exec /usr/bin/obfsproxy managed

     </pre>

     <p>

@@ -22,7 +22,7 @@

     <img width="7%" height="7%" style="float: left;" src="$(IMGROOT)/icon-Obfsproxy.jpg">

     <b> Hey! </b>

     If you are <b>not</b> using Debian or Ubuntu, you better look

-    <a href="../projects/obfsproxy-instructions.html.en">at this other guide</a>

+    <a href="<page projects/obfsproxy-instructions>">at this other guide</a>

     which sets up Obfsproxy from source.

     </p>

     <br><br>

@@ -34,11 +34,11 @@

       recommend you to upgrade to the Python version!

     </p>

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

+    <h3>Step 0: Install a recent version of Tor (>= 0.2.4.1)</h3>

     <br>

     <p>

-    Add the <a href="<page docs/debian>#development">development Tor

+    Add the <a href="<page docs/debian>#ubuntu">official Tor

     APT repository</a> and run the specified commands to install <code>tor</code>

     and <code>deb.torproject.org-keyring</code>. You need <em>Tor 0.2.4.x</em> because

     it knows how to automatically report your obfsproxy address to <a

@@ -30,7 +30,7 @@

     <p>

       This is a <b>Debian/Ubuntu</b> guide for installing the Python

-      version of obfsproxy. If you still have the C version, we

+      version of obfsproxy. If you are still using the C version, we

       recommend you to upgrade to the Python version!

     </p>

@@ -46,6 +46,11 @@

     </p>

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

+    <br>

+

+    <p>

+    Since you installed the Tor APT repository, installing obfsproxy is now a matter of running a command:

+    </p>

     <pre style="margin: 1.5em 0 1.5em 2em">

 \# apt-get install obfsproxy

@@ -19,7 +19,19 @@

     <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a>

     <p>

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

+    <img width="7%" height="7%" style="float: left;" src="$(IMGROOT)/icon-Obfsproxy.jpg">

+    <b> Hey! </b>

+    If you are <b>not</b> using Debian or Ubuntu, you better look

+    <a href="../projects/obfsproxy-instructions.html.en">at this other guide</a>

+    which sets up Obfsproxy from source.

+    </p>

+    <br><br>

+

+

+    <p>

+      This is a <b>Debian/Ubuntu</b> guide for installing the Python

+      version of obfsproxy. If you still have the C version, we

+      recommend you to upgrade to the Python version!

     </p>

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

@@ -27,27 +39,18 @@

     <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 because

+    APT repository</a> and run the specified commands to install <code>tor</code>

+    and <code>deb.torproject.org-keyring</code>. You need <em>Tor 0.2.4.x</em> 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>

@@ -66,7 +69,7 @@ Exitpolicy reject *:*

 \## 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

+ServerTransportPlugin obfs2,obfs3 exec /usr/bin/obfsproxy managed

     </pre>

     <p>

@@ -82,7 +85,7 @@ ServerTransportPlugin obfs2 exec /usr/bin/obfsproxy --managed

     </p>

     <pre style="margin: 1.5em 0 1.5em 2em">

-service tor restart

+\# service tor restart

     </pre>

     <p>

@@ -110,22 +113,24 @@ Nov 05 16:40:48.000 [notice] Bootstrapped 100%: Done.

     <p>

     If you're behind a NAT/firewall, you'll need to make your bridge

     reachable from the outside world — 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

+    the obfsproxy ports. The ORPort is whatever you defined in step two

+    above. To find your obfsproxy ports, 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

+Oct 05 20:00:41.000 [notice] Registered server transport 'obfs3' at '0.0.0.0:42000

     </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.) If you want to change the number, use

-    Tor 0.2.4.7-alpha or later, and set "ServerTransportListenAddr obfs2

-    0.0.0.0:26821" in your torrc.

+    The last number in each line, in this case <i>26821</i> and

+    <i>42000</i>, is the TCP port number that you need to forward

+    through your firewall. (The ports are randomly chosen the first

+    time Tor starts, but Tor will cache and reuse the same number in

+    future runs.) If you want to change the number, use Tor

+    0.2.4.7-alpha or later, and set something similar to

+    "ServerTransportListenAddr obfs2 0.0.0.0:26821" in your torrc.

     </p>

   </div>

@@ -123,9 +123,9 @@ Oct 05 20:00:41.000 [notice] Registered server transport 'obfs2' at '0.0.0.0:268

     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.) If you want to change the number,

-    stop Tor, edit /var/lib/tor/state to change the number in the

-    "TransportProxy obfs2" line, and then restart Tor.

+    same number in future runs.) If you want to change the number, use

+    Tor 0.2.4.7-alpha or later, and set "ServerTransportListenAddr obfs2

+    0.0.0.0:26821" in your torrc.

     </p>

   </div>

@@ -28,7 +28,7 @@

     <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

+    and deb.torproject.org-keyring. You need Tor 0.2.4.x because

     it knows how to automatically report your obfsproxy address to <a

     href="https://bridges.torproject.org/?transport=obfs2">BridgeDB</a>.

     </p>

@@ -62,7 +62,7 @@ BridgeRelay 1

 Exitpolicy reject *:*

 \## CHANGEME_1 -> provide a nickname for your bridge, can be anything you like

-Nickname CHANGEME_1

+\#Nickname CHANGEME_1

 \## CHANGEME_2 -> provide some email address so we can contact you if there's a problem

 \#ContactInfo CHANGEME_2

@@ -70,7 +70,7 @@ ServerTransportPlugin obfs2 exec /usr/bin/obfsproxy --managed

     </pre>

     <p>

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

+    Don't forget to uncomment and edit the <i>CHANGEME</i> fields!

     </p>

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

@@ -100,7 +100,7 @@ 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

+    If Tor is earlier in the bootstrapping phase, wait until it gets to

     100%.

     </p>

@@ -123,7 +123,9 @@ Oct 05 20:00:41.000 [notice] Registered server transport 'obfs2' at '0.0.0.0:268

     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.)

+    same number in future runs.) If you want to change the number,

+    stop Tor, edit /var/lib/tor/state to change the number in the

+    "TransportProxy obfs2" line, and then restart Tor.

     </p>

   </div>

@@ -41,9 +41,10 @@

     </pre>

     <p>

-    Obfsproxy requires libevent2. If your distribution (e.g. Debian

-    squeeze) doesn't include it, you can get it from the <a

-    href="http://packages.debian.org/search?keywords=libevent-2.0-5">backports</a>

+    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>

@@ -2,7 +2,7 @@

 # Revision: $Revision$

 # Translation-Priority: 4-optional

-#include "head.wmi" TITLE="obfsproxy: Installation instructions" CHARSET="UTF-8"

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

 <div id="content" class="clearfix">

   <div id="breadcrumbs">

@@ -14,65 +14,55 @@

     <!-- PUT CONTENT AFTER THIS TAG -->

-    <h1 id="instructions">Obfsproxy Bridge Instructions on Debian/Ubuntu</h1>

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

     <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a>

     <p>

-    This guide will help you setup an obfuscated bridge on a Debian/Ubuntu system.

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

     </p>

-    <h3>Step 0: Add Tor repositories to APT</h3>

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

     <br>

     <p>

-    You need

-    to <a href="https://www.torproject.org/docs/debian#development">install

-    the experimental official Tor Project APT repositories</a>,

-    because a fresh version of Tor (0.2.4.x) is required (Older

-    versions of Tor don't report their bridge addresses to BridgeDB).

+    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 Tor and obfsproxy</h3>

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

     <br>

-    <p>

-    Now install tor and obfsproxy:

-    </p>

-

     <pre style="margin: 1.5em 0 1.5em 2em">

-\# apt-get update

-\# apt-get install obfsproxy tor

+\# apt-get install obfsproxy

     </pre>

     <p>

-      Note that obfsproxy requires

-    libevent2 and your distribution (e.g. Debian stable) might not

-    have it in its repos.  You can

-    <a href="https://trac.torproject.org/projects/tor/ticket/5009#comment:9">try

-    our experimental backport libevent2 debs</a>,

-    or <a href="https://trac.torproject.org/projects/tor/ticket/5009#comment:17">build

-    libevent2 from source</a>.

+    Obfsproxy requires libevent2. If your distribution (e.g. Debian

+    squeeze) doesn't include it, you can get it from the <a

+    href="http://packages.debian.org/search?keywords=libevent-2.0-5">backports</a>

+    repository.

     </p>

-    <h3>Step 2: Set up Tor</h3>

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

     <br>

     <p>

-    You will need an appropriate

-    Tor <a href="<page docs/faq>#torrc">configuration file</a>

-    (usually at <i>/etc/tor/torrc</i>):

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

     </p>

     <pre style="margin: 1.5em 0 1.5em 2em">

 SocksPort 0

-ORPort auto

+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.

+\## CHANGEME_1 -> provide a nickname for your bridge, can be anything you like

 Nickname CHANGEME_1

-\## CHANGEME_2 -> If you want others to be able to contact you uncomment this line and put your GPG fingerprint for example.

+\## 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

@@ -82,11 +72,12 @@ ServerTransportPlugin obfs2 exec /usr/bin/obfsproxy --managed

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

     </p>

-    <h3>Step 3: Launch Tor and verify that it works</h3>

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

     <br>

     <p>

-    Restart Tor for the the new configuration file to be in effect:

+    Restart Tor to use the new configuration file.

+    (Preface with sudo if needed.)

     </p>

     <pre style="margin: 1.5em 0 1.5em 2em">

@@ -112,10 +103,16 @@ Nov 05 16:40:48.000 [notice] Bootstrapped 100%: Done.

     100%.

     </p>

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

+    <br>

+

     <p>

-    Now you need to find the address on which obfsproxy is

-    listening. To do this, check your Tor logs for a line similar to

-    this one:

+    If you're behind a NAT/firewall, you'll need to make your bridge

+    reachable from the outside world — 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

@@ -123,17 +120,9 @@ Oct 05 20:00:41.000 [notice] Registered server transport 'obfs2' at '0.0.0.0:268

     <p>

     The last number, in this case <i>26821</i>, is the TCP port number

-    that your clients should point their obfsproxy to. So for example,

-    if your public IP is 1.2.3.4, your clients should put <i>Bridge

-    obfs2 1.2.3.4:26821</i> in their configuration file.

-    </pre>

-    </p>

-

-    <p>

-    <img width="7%" height="7%" style="float: left;" src="$(IMGROOT)/icon-Obfsproxy.jpg">

-    <b>Don't forget!</b> If you are behind a NAT, you should <b>port

-    forward</b> the port that obfsproxy is listening on. In the

-    example above you would have to forward port <i>26821</i>.

+    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>

new file mode 100644

@@ -0,0 +1,149 @@

+## translation metadata

+# Revision: $Revision$

+# Translation-Priority: 4-optional

+

+#include "head.wmi" TITLE="obfsproxy: Installation instructions" 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">

+

+    <!-- PUT CONTENT AFTER THIS TAG -->

+

+    <h1 id="instructions">Obfsproxy Bridge Instructions on Debian/Ubuntu</h1>

+

+    <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a>

+

+    <p>

+    This guide will help you setup an obfuscated bridge on a Debian/Ubuntu system.

+    </p>

+

+    <h3>Step 0: Add Tor repositories to APT</h3>

+    <br>

+

+    <p>

+    You need

+    to <a href="https://www.torproject.org/docs/debian#development">install

+    the experimental official Tor Project APT repositories</a>,

+    because a fresh version of Tor (0.2.4.x) is required (Older

+    versions of Tor don't report their bridge addresses to BridgeDB).

+    </p>

+

+    <h3>Step 1: Install Tor and obfsproxy</h3>

+    <br>

+

+    <p>

+    Now install tor and obfsproxy:

+    </p>

+

+    <pre style="margin: 1.5em 0 1.5em 2em">

+\# apt-get update

+\# apt-get install obfsproxy tor

+    </pre>

+

+    <p>

+      Note that obfsproxy requires

+    libevent2 and your distribution (e.g. Debian stable) might not

+    have it in its repos.  You can

+    <a href="https://trac.torproject.org/projects/tor/ticket/5009#comment:9">try

+    our experimental backport libevent2 debs</a>,

+    or <a href="https://trac.torproject.org/projects/tor/ticket/5009#comment:17">build

+    libevent2 from source</a>.

+    </p>

+

+    <h3>Step 2: Set up Tor</h3>

+    <br>

+

+    <p>

+    You will need an appropriate

+    Tor <a href="<page docs/faq>#torrc">configuration file</a>

+    (usually at <i>/etc/tor/torrc</i>):

+    </p>

+

+    <pre style="margin: 1.5em 0 1.5em 2em">

+SocksPort 0

+ORPort auto

+BridgeRelay 1

+Exitpolicy reject *:*

+

+\## CHANGEME_1 -> provide a nickname for your bridge, can be anything you like.

+Nickname CHANGEME_1

+\## CHANGEME_2 -> If you want others to be able to contact you uncomment this line and put your GPG fingerprint for example.

+\#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 works</h3>

+    <br>

+

+    <p>

+    Restart Tor for the the new configuration file to be in effect:

+    </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>

+

+    <p>

+    Now you need to find the address on which obfsproxy is

+    listening. To do this, check your Tor logs for a line similar to

+    this one:

+

+    <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 your clients should point their obfsproxy to. So for example,

+    if your public IP is 1.2.3.4, your clients should put <i>Bridge

+    obfs2 1.2.3.4:26821</i> in their configuration file.

+    </pre>

+    </p>

+

+    <p>

+    <img width="7%" height="7%" style="float: left;" src="$(IMGROOT)/icon-Obfsproxy.jpg">

+    <b>Don't forget!</b> If you are behind a NAT, you should <b>port

+    forward</b> the port that obfsproxy is listening on. In the

+    example above you would have to forward port <i>26821</i>.

+    </p>

+

+  </div>

+  <!-- END MAINCOL -->

+  <div id = "sidecol">

+#include "side.wmi"

+#include "info.wmi"

+  </div>

+  <!-- END SIDECOL -->

+</div>

+<!-- END CONTENT -->

+#include <foot.wmi>

+