[tor-commits] r25338: {} add asn's first draft of obfsproxy webpage. i tweaked it som (website/trunk/projects/en)
Roger Dingledine
arma at torproject.org
Tue Jan 24 02:42:28 UTC 2012
Author: arma
Date: 2012-01-24 02:42:28 +0000 (Tue, 24 Jan 2012)
New Revision: 25338
Added:
website/trunk/projects/en/obfsproxy-instructions.wml
website/trunk/projects/en/obfsproxy.wml
Log:
add asn's first draft of obfsproxy webpage. i tweaked it some already.
Added: website/trunk/projects/en/obfsproxy-instructions.wml
===================================================================
--- website/trunk/projects/en/obfsproxy-instructions.wml (rev 0)
+++ website/trunk/projects/en/obfsproxy-instructions.wml 2012-01-24 02:42:28 UTC (rev 25338)
@@ -0,0 +1,154 @@
+## 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 » </a>
+ <a href="<page projects/projects>">Projects » </a>
+ <a href="<page projects/obfsproxy>">obfsproxy</a>
+ </div>
+ <div id="maincol">
+
+ <!-- PUT CONTENT AFTER THIS TAG -->
+
+ <h1 id="instructions">Instructions</h1>
+
+ <h3>Step One: Install necessary dependencies</h3>
+ <br>
+
+ <p>
+ You will need a C compiler (<em>gcc</em>), the <em>Autotools</em>
+ build system, the <em>git</em> revision control system,
+ <em>libevent-2</em> and the development headers of
+ <em>OpenSSL</em>.
+ </p>
+
+ <p>
+ In a Linux system using the APT package manager you could do: <br>
+ <tt># apt-get install autotools gcc git libevent-2.0-5 libevent-openssl-2.0-5 libssl-dev</tt>
+ </p>
+
+ <h3>Step Two: Install obfsproxy</h3>
+ <br>
+
+ <p>
+ Clone obfsproxy from its git repository:<br>
+ <tt>$ git clone git://git.torproject.org/obfsproxy.git</tt> <br>
+
+ The above command should create and populate a directory named
+ 'obfsproxy' in your current directory. </p>
+
+ <p>
+ Compile obfsproxy: <br>
+ <tt>$ cd obfsproxy</tt> <br>
+ <tt>$ ./autogen.sh && ./configure && make</tt> <br>
+ </p>
+
+ <p>
+ And then <strong>as root</strong> install obfsproxy in your system: <br>
+ <tt># make install</tt>
+ </p>
+
+ <h3>Step Three: Install tor</h3>
+ <br>
+
+ <p>
+ To follow this guide, you will need the current git master.
+
+ </p>
+
+ <p>
+ <img align="left"
+ style="margin-top:5px;margin-left:-10px;margin-right:5px"
+ src="$(IMGROOT)/warning.png"> <strong>If you want to set up a Tor
+ bridge with obfsproxy, click <a class="anchor"
+ href="#bridge_instructions">here</a> for bridge instructions,
+ otherwise continue to <a class="anchor"
+ href="#client_instructions">step four.</a></strong>
+ </p>
+
+ <h3 id="client_instructions">Step Four (client): Configure tor</h3>
+ <br>
+
+ <p>
+ Set up your tor configuration file:<br><br>
+ <img src="$(IMGROOT)/obfs-torrc_client.png" alt="client torrc"></a>
+ </p>
+
+ <h3>Step Five (client): Launch tor</h3>
+ <br>
+
+ <p>
+ Launch tor using the configuration file you made in the previous
+ step. You can do this by using your favorite init script, or by
+ pointing the tor binary to the torrc:
+ </p>
+
+ <img src="$(IMGROOT)/obfs-spawn_tor_client.png" alt="spawn tor" height="101" width="882">
+
+ <p> <br>
+ <img src="$(IMGROOT)/sidenav-arrow.png">
+ <strong>Congratulations!</strong> Your traffic should now be
+ obfuscated by obfsproxy. You are done! You can now start using Tor.
+ </p>
+
+ <br> <br> <br> <br>
+
+ <hr>
+
+ <br> <br> <br> <br>
+
+ <h3 id="bridge_instructions">Step Four (bridge): Configure tor</h3>
+ <br>
+
+ <p>
+ Set up your tor configuration file:<br><br>
+ <img src="$(IMGROOT)/obfs-torrc_bridge.png" alt="bridge torrc"></a>
+ </p>
+
+ <h3>Step Five (bridge): Launch tor</h3>
+ <br>
+
+ <p>
+ Launch tor using the configuration file you made in the previous
+ step. You can do this by using your favorite init script, or by
+ pointing the tor binary to the torrc:
+ <p>
+
+ <p>
+ <img src="$(IMGROOT)/obfs-spawn_tor_bridge.png" alt="spawn tor" height="101" width="882"></a>
+ </p>
+
+ <h3>Step Six (bridge): Find the TCP ports opened by obfsproxy</h3>
+ <br>
+
+ <p>
+ Look in your log file for a line similar to this one: <br>
+ <img src="$(IMGROOT)/obfs-log_checking.png" alt="bridge torrc" width="437" height="14"></a>
+ <br>
+ The last number, in this case <em>34545</em>, is the TCP port
+ number that your clients should point their obfsproxy to.
+ </p>
+
+ <p>
+ <img src="$(IMGROOT)/sidenav-arrow.png">
+ <strong>Congratulations!</strong> Tell your clients to point their
+ obfsproxy to your IP and to port <em>34545</em>.
+ </p>
+
+ <br>
+
+ </div>
+ <!-- END MAINCOL -->
+ <div id = "sidecol">
+#include "side.wmi"
+#include "info.wmi"
+ </div>
+ <!-- END SIDECOL -->
+</div>
+<!-- END CONTENT -->
+#include <foot.wmi>
+
Added: website/trunk/projects/en/obfsproxy.wml
===================================================================
--- website/trunk/projects/en/obfsproxy.wml (rev 0)
+++ website/trunk/projects/en/obfsproxy.wml 2012-01-24 02:42:28 UTC (rev 25338)
@@ -0,0 +1,69 @@
+## translation metadata
+# Revision: $Revision$
+# Translation-Priority: 4-optional
+
+#include "head.wmi" TITLE="Tor Project: obfsproxy" CHARSET="UTF-8"
+<div id="content" class="clearfix">
+ <div id="breadcrumbs">
+ <a href="<page index>">Home » </a>
+ <a href="<page projects/projects>">Projects » </a>
+ <a href="<page projects/obfsproxy>">obfsproxy » </a>
+ </div>
+ <div id="maincol">
+ <!-- PUT CONTENT AFTER THIS TAG -->
+
+ <h2>obfsproxy</h2>
+ <div class="underline"></div>
+
+ <!-- BEGIN SIDEBAR -->
+ <div class="sidebar-left">
+ </div>
+ <!-- END SIDEBAR -->
+
+ <p>
+ obfsproxy is a tool that attempts to circumvent censorship, by
+ transforming the Tor traffic between the client and the
+ bridge. This way, censors, who usually monitor traffic between the
+ client and the bridge, will see innocent-looking transformed
+ traffic instead of the actual Tor traffic.
+
+ <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="client torrc"></a>
+ </p>
+
+ <p>
+ obfsproxy supports multiple protocols, called pluggable
+ transports, which specify how the traffic is transformed. For
+ example, there might be a HTTP transport which transforms Tor
+ traffic to look like regular HTTP traffic.
+ </p>
+
+ <p>
+ Even though obfsproxy is a separate application, completely
+ independent from tor, it speaks to tor using an <a
+ href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable-transport.txt">internal
+ protocol</a> in an attempt minimize necessary end-user
+ configuration.
+ </p>
+
+ <h2><a class="anchor" href="<page projects/obfsproxy-instructions>#instructions">Installation Instructions</a></h2>
+
+ <h2><a href="https://gitweb.torproject.org/obfsproxy.git">Download</a></h2>
+
+ <p>
+ Please open a <a
+ href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Pluggable+transport&order=priority&col=id&col=summary&col=status&col=type&col=priority&col=milestone&col=component">ticket</a>
+ on our bug tracker for any bugs you find or features you would
+ like to see added in future releases.
+ </p>
+
+ </div>
+ <!-- END MAINCOL -->
+ <div id = "sidecol">
+#include "side.wmi"
+#include "info.wmi"
+ </div>
+ <!-- END SIDECOL -->
+</div>
+<!-- END CONTENT -->
+#include <foot.wmi>
+
More information about the tor-commits
mailing list