tor-tb-manual.git

en-US/bridges.page  1) <page xmlns="http://projectmallard.org/1.0/"
en-US/bridges.page  2)   type="topic"
en-US/bridges.page  3)   id="bridges">
en-US/bridges.page  4) 
en-US/bridges.page  5) <info>

C/bridges.page      6)   <desc>Learn what bridges are and how to get them</desc>
C/bridges.page      7)   <link type="topic" xref="circumvention" />

en-US/bridges.page  8) </info>
en-US/bridges.page  9) 
en-US/bridges.page 10) <title>Bridges</title>
en-US/bridges.page 11) 
en-US/bridges.page 12) <p>

C/bridges.page     13)  Most <link xref='transports'>Pluggable Transports</link>, such as obfs3
C/bridges.page     14)  and obfs4, rely on the use of “bridge” relays. Like ordinary Tor relays, bridges
C/bridges.page     15)  are run by volunteers; unlike ordinary relays, however, they are not listed
C/bridges.page     16)  publicly, so an adversary cannot identify them easily. Using bridges in
C/bridges.page     17)  combination with pluggable transports helps to disguise the fact that you
C/bridges.page     18)  are using Tor.

en-US/bridges.page 19) </p>
en-US/bridges.page 20) 
en-US/bridges.page 21) <p>

C/bridges.page     22) Other pluggable transports, like meek, use different

C/bridges.page     23) anti-censorship techniques that do not rely on bridges. You do not need
C/bridges.page     24) to obtain bridge addresses in order to use these transports.

en-US/bridges.page 25) </p>
en-US/bridges.page 26) 

C/bridges.page     27) <section id="getting-bridges">
C/bridges.page     28)  <title>Getting bridge addresses</title>
C/bridges.page     29)  <p>
C/bridges.page     30)  Because bridge addresses are not public, you will need to request them

C/bridges.page     31)  yourself. You have two options:

C/bridges.page     32)  </p>

en-US/bridges.page 33) 

C/bridges.page     34) <list>

en-US/bridges.page 35)   <item>
en-US/bridges.page 36)     <p>

C/bridges.page     37)     Visit <link href='https://bridges.torproject.org/'>https://bridges.torproject.org/</link>
C/bridges.page     38)     and follow the instructions, or

en-US/bridges.page 39)     </p>
en-US/bridges.page 40)   </item>
en-US/bridges.page 41)   <item>
en-US/bridges.page 42)     <p>

C/bridges.page     43)     Email bridges@torproject.org from a Gmail, Yahoo, or Riseup email
C/bridges.page     44)     address, or

en-US/bridges.page 45)     </p>
en-US/bridges.page 46)   </item>

C/bridges.page     47) </list>
C/bridges.page     48) </section>

en-US/bridges.page 49) 

C/bridges.page     50) <section id="entering-bridges">
C/bridges.page     51)  <title>Entering bridge addresses</title>
C/bridges.page     52)  <p>
C/bridges.page     53)  Once you have obtained some bridge addresses, you will need to enter them
C/bridges.page     54)  into Tor Launcher.
C/bridges.page     55)  </p>

en-US/bridges.page 56) 

C/bridges.page     57)  <p>
C/bridges.page     58)  Choose “yes” when asked if your Internet Service Provider blocks connections to 
C/bridges.page     59)  the Tor network. Select “Use custom bridges” and enter each bridge address
C/bridges.page     60)  on a separate line.
C/bridges.page     61)  </p>

en-US/bridges.page 62) 

C/bridges.page     63)  <media type="image" width="600" src="media/tor-launcher-custom-bridges.png" />

en-US/bridges.page 64) 

C/bridges.page     65)  <p>
C/bridges.page     66)  Click “Connect”. Using bridges may slow down the connection compared to
C/bridges.page     67)  using ordinary Tor relays. If the connection fails, the bridges you
C/bridges.page     68)  received may be down. Please use one of the above methods to obtain
C/bridges.page     69)  more bridge addresses, and try again.
C/bridges.page     70)  </p>
C/bridges.page     71) </section>