Added 6 pages with images.
Matt Pagan authored 10 years ago
|
en-US/bridges.page 1)
en-US/bridges.page 2) <page xmlns="http://projectmallard.org/1.0/"
en-US/bridges.page 3) type="topic"
en-US/bridges.page 4) id="bridges">
en-US/bridges.page 5)
en-US/bridges.page 6) <info>
en-US/bridges.page 7) <desc>What bridges are and how to use them.</desc>
en-US/bridges.page 8) <link type="guide" xref="index" />
en-US/bridges.page 9) </info>
en-US/bridges.page 10)
en-US/bridges.page 11) <title>Bridges</title>
en-US/bridges.page 12)
en-US/bridges.page 13) <p>
en-US/bridges.page 14) Bridges are quiet gateways into the Tor Network. Like Tor relays, they are run
en-US/bridges.page 15) by volunteers. Unlike relays, they are not listed publicly. Using bridges
en-US/bridges.page 16) disguise the fact that one is using Tor.
en-US/bridges.page 17) </p>
en-US/bridges.page 18)
en-US/bridges.page 19) <p>
en-US/bridges.page 20) Currently there are five bridge types, or transports, available. More are
en-US/bridges.page 21) being developed.
en-US/bridges.page 22) </p>
en-US/bridges.page 23) <table frame='all' rules='all'>
en-US/bridges.page 24) <tr>
en-US/bridges.page 25) <td>
en-US/bridges.page 26) <p>
en-US/bridges.page 27) ORPort
en-US/bridges.page 28) </p>
en-US/bridges.page 29) </td>
en-US/bridges.page 30) <td>
en-US/bridges.page 31) <p>
en-US/bridges.page 32) Requesting 'bridges' without specifying the bridge type, will return
en-US/bridges.page 33) ORPort bridges, also called Vanilla bridges. ORPort bridges are NOT
en-US/bridges.page 34) reliable for circumventing censorship or national firewalls. ORPort
en-US/bridges.page 35) bridges can be useful as trusted entry points into the Tor network.
en-US/bridges.page 36) </p>
en-US/bridges.page 37) </td>
en-US/bridges.page 38) </tr>
en-US/bridges.page 39) <tr>
en-US/bridges.page 40) <td>
en-US/bridges.page 41) <p>
en-US/bridges.page 42) obfs2
en-US/bridges.page 43) </p>
en-US/bridges.page 44) </td>
en-US/bridges.page 45) <td>
en-US/bridges.page 46) <p>
en-US/bridges.page 47) Censors have learned how to identify obfs2 bridges. This transport
en-US/bridges.page 48) is being deprecated.
en-US/bridges.page 49) </p>
en-US/bridges.page 50) </td>
en-US/bridges.page 51) </tr>
en-US/bridges.page 52) <tr>
en-US/bridges.page 53) <td>
en-US/bridges.page 54) <p>
en-US/bridges.page 55) obfs3
en-US/bridges.page 56) </p>
en-US/bridges.page 57) </td>
en-US/bridges.page 58) <td>
en-US/bridges.page 59) <p>
en-US/bridges.page 60) Obfsproxy disguises Tor traffic as random noise. obfs3 bridges work
en-US/bridges.page 61) almost everywhere. A few obfs3 bridges have been blocked.
en-US/bridges.page 62) </p>
en-US/bridges.page 63) </td>
en-US/bridges.page 64) </tr>
en-US/bridges.page 65) <tr>
en-US/bridges.page 66) <td>
en-US/bridges.page 67) <p>
en-US/bridges.page 68) Scramblesuit
en-US/bridges.page 69) </p>
en-US/bridges.page 70) </td>
en-US/bridges.page 71) <td>
en-US/bridges.page 72) <p>
en-US/bridges.page 73) Scramblesuit is an additional tool for the obfsproxy transport.
en-US/bridges.page 74) Scramblesuit bridges are designed to be hard to identify and hard to
en-US/bridges.page 75) block.
en-US/bridges.page 76) </p>
en-US/bridges.page 77) </td>
en-US/bridges.page 78) </tr>
en-US/bridges.page 79) <tr>
en-US/bridges.page 80) <td>
en-US/bridges.page 81) <p>
en-US/bridges.page 82) FTE
en-US/bridges.page 83) </p>
en-US/bridges.page 84) </td>
en-US/bridges.page 85) <td>
en-US/bridges.page 86) <p>
en-US/bridges.page 87) Format-Transforming Encryption disguises Tor traffic as web (HTTP)
en-US/bridges.page 88) traffic or other types of internet traffic. FTE bridges are
en-US/bridges.page 89) effective, but in limited supply.
en-US/bridges.page 90) </p>
en-US/bridges.page 91) </td>
en-US/bridges.page 92) </tr>
en-US/bridges.page 93) </table>
en-US/bridges.page 94)
en-US/bridges.page 95) <p>
en-US/bridges.page 96) (Note that flashproxy is a Pluggable Transport, but does not rely on bridges.)
en-US/bridges.page 97) </p>
en-US/bridges.page 98)
en-US/bridges.page 99) <p>
en-US/bridges.page 100) There are four ways to get a bridge.
en-US/bridges.page 101) </p>
en-US/bridges.page 102)
en-US/bridges.page 103) <steps>
en-US/bridges.page 104) <item>
en-US/bridges.page 105) <p>
en-US/bridges.page 106) Visit <link href='https://bridges.torproject.org/'>https://bridges.torproject.org/</link> and follow the instructions.
en-US/bridges.page 107) </p>
en-US/bridges.page 108) </item>
en-US/bridges.page 109) <item>
en-US/bridges.page 110) <p>
en-US/bridges.page 111) Email bridges@bridges.torproject.org from a gmail or yahoo
en-US/bridges.page 112) email address. Put <cmd>get bridges</cmd> in the body for ORPort bridges
en-US/bridges.page 113) or <cmd>transport=obfs3</cmd> for obfs3 bridges.
en-US/bridges.page 114) </p>
en-US/bridges.page 115) </item>
en-US/bridges.page 116) <item>
en-US/bridges.page 117) <p>
en-US/bridges.page 118) Politely ask a human at help@rt.torproject.org if you cannot access
en-US/bridges.page 119) either of the first two methods.
en-US/bridges.page 120) </p>
en-US/bridges.page 121) </item>
en-US/bridges.page 122) <item>
en-US/bridges.page 123) <p>
en-US/bridges.page 124) Install and configure a Tor instance to be bridge
en-US/bridges.page 125) for yourself. The computer acting as a bridge must have uncensored internet
en-US/bridges.page 126) access to the Tor network. A full installation guide can be found at
en-US/bridges.page 127) <link href='https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en'>https://www.torproject.org/projects/obfsproxy-debian-instructions.html.en</link>
en-US/bridges.page 128) </p>
en-US/bridges.page 129) </item>
en-US/bridges.page 130) </steps>
en-US/bridges.page 131)
en-US/bridges.page 132) <p>
en-US/bridges.page 133) Enter the bridge information you get from any of the above steps in
en-US/bridges.page 134) Tor-launcher.
en-US/bridges.page 135) </p>
en-US/bridges.page 136)
en-US/bridges.page 137) <p>
en-US/bridges.page 138) Choose yes when asked if your Internet Service Provider blocks connections to
en-US/bridges.page 139) the Tor network. Select 'Use custom bridges' and enter each bridge identifier
en-US/bridges.page 140) on its own line.
en-US/bridges.page 141) </p>
en-US/bridges.page 142)
|