Roger Dingledine commited on 2013-03-24 22:56:14
Zeige 1 geänderte Dateien mit 10 Einfügungen und 7 Löschungen.
... | ... |
@@ -20,6 +20,9 @@ |
20 | 20 |
</div> |
21 | 21 |
<!-- END SIDEBAR --> |
22 | 22 |
|
23 |
+ <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a> |
|
24 |
+ </p> |
|
25 |
+ |
|
23 | 26 |
<p> |
24 | 27 |
obfsproxy is a tool that attempts to circumvent censorship, by |
25 | 28 |
transforming the Tor traffic between the client and the |
... | ... |
@@ -27,14 +30,14 @@ |
27 | 30 |
client and the bridge, will see innocent-looking transformed |
28 | 31 |
traffic instead of the actual Tor traffic. |
29 | 32 |
|
30 |
- <img src="$(IMGROOT)/obfsproxy_diagram.png" alt="obfsproxy diagram"></a> |
|
31 |
- </p> |
|
32 |
- |
|
33 | 33 |
<p> |
34 |
- obfsproxy supports multiple protocols, called <a href="<page docs/pluggable-transports>">pluggable |
|
35 |
- transports</a>, which specify how the traffic is transformed. For |
|
36 |
- example, there might be a HTTP transport which transforms Tor |
|
37 |
- traffic to look like regular HTTP traffic. |
|
34 |
+ obfsproxy supports multiple protocols, called <a href="<page |
|
35 |
+ docs/pluggable-transports>">pluggable transports</a>, which |
|
36 |
+ specify how the traffic is transformed. For example, there might |
|
37 |
+ be a HTTP transport which transforms Tor traffic to look like |
|
38 |
+ regular HTTP traffic. See the <a href="<page |
|
39 |
+ docs/pluggable-transports>">pluggable transports page</a> for more |
|
40 |
+ information. |
|
38 | 41 |
</p> |
39 | 42 |
|
40 | 43 |
<p> |
41 | 44 |