## 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 -->
<img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a>
</p>
<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.
<p>
obfsproxy supports multiple protocols, called <a href="<page
docs/pluggable-transports>">pluggable transports</a>, 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. See the <a href="<page
docs/pluggable-transports>">pluggable transports page</a> for more
information.
</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> to minimize necessary end-user configuration.
</p>
<p>
Please open a <a