tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 1-high

4) 
5) #include "head.wmi" TITLE="Tor: Finding Tor"
6) <div class="main-column">
7) 
8) <h1>Tor: Finding Tor</h1>
9) <hr />
10) <p>

11) Sometimes it's not possible to directly reach the Tor Project website. Here
12) are some ways that you can find and download a current version of
13) Tor if our website is blocked in your area. If you're reading this from
14) a search engine's cache, directly from our

15) website, or by some other method, we hope these suggestions are helpful.

16) Additionally, if you have ideas for how to improve these instructions, please
17) <a href="<page contact>">contact us</a> and let us know.

18) </p>
19) 

20) <a id="WithTor"></a>
21) <h2><a class="anchor" href="#WithTor">Fetching Tor with Tor: Using your
22) web browser</a></h2>

23) <hr />
24) <p>

25) If you're already running Tor, you should be able to download a new Tor

26) securely with your current Tor. You should do this for your friends who don't
27) already have Tor. You can do this from our <a href="<page download>">download
28) page</a> or from a download page on one of the many Tor <a href="<page mirrors>">mirrors</a>.

29) Please take care to <a

30) href="<page verifying-signatures>">verify

31) the signature</a> of any downloaded package when possible.

32) </p>
33) 

34) <a id="Mirrors"></a>
35) <h2><a class="anchor" href="#Mirrors">With a little help from our friends:
36) Using Mirrors</a></h2>

37) <hr />
38) <p>

39) A Tor mirror is a website that contains an exact copy of our main site.
40) We have <a
41) href="<page mirrors>">several dozen mirrors</a> currently, and you
42) can find the list by searching for "Tor mirrors" on your favorite
43) search engine.
44) </p>
45) 
46) <p>
47) It is very important to <a

48) href="<page verifying-signatures>">verify

49) the cryptographic signatures</a> on the Tor software when using any mirror. We

50) cannot ensure the safety or security of any package hosted on remote mirrors

51) without a signature. It's probably safe, but a cautious user should check
52) signatures when possible.

53) </p>
54) 

55) <a id="Mail"></a>
56) <h2><a class="anchor" href="#Mail">Fetching Tor via Gmail: gettor</a></h2>

57) <hr />
58) <p>

59) It is possible to get a copy of Tor by sending an email to a special email
60) address: '<tt>gettor AT torproject.org</tt>'. Now anyone who can send
61) email can get a copy of Tor. A user only needs to send us a request with
62) 'help' in the body of the email, and instructions will be sent as a reply.

63) </p>
64) 
65) <p>
66) To avoid spamming people accidentally, we only answer emails that are sent
67) from email services that support <a href="http://www.dkim.org/">DKIM</a>,

68) which is an email feature that lets us verify that the address in the

69) "From" line is actually the one who sent the mail. Gmail is an example of a
70) mail service that is known to work. If we get an email

71) from a service that doesn't use DKIM, we'll send a short explanation
72) and then ignore the email address for the next day or so.

73) </p>
74) 

75) <a id="IRC"></a>
76) <h2><a class="anchor" href="#IRC">Fetching Tor via IRC: gettor</a></h2>

77) <hr />
78) <p>
79) It is possible to fetch the source code, binaries and other files related to 
80) Tor by using the XDCC IRC file transfer protocol. It is best to attempt this 
81) only if you connect to the IRC server using SSL. Currently <tt>gettor</tt> 

82) is known to spend time on Freenode, 2600, Indymedia and OFTC.

83) <br><br>
84) If you're currently able to connect to one of those IRC networks, look for a 
85) user named '<tt>gettor</tt>' that is connected from the host 
86) '<tt>check.torproject.org</tt>'. Send the user a private message like so:
87) <br>
88) <br>
89) '<tt>/msg gettor xdcc list</tt>'
90) <br>
91) <br>
92) The <tt>gettor</tt> user should respond with a list of files
93) available for download. If there is no response, something has gone wrong. Some
94) IRC networks require that you are registered before you can send private
95) queries to other users (this is often to reduce spam). You may need to register
96) with the NickServ before you can talk to the <tt>'gettor'</tt> user.
97) <br>
98) An example response returned by <tt>gettor</tt> is presented below:<br>
99) <pre>
100) -gettor- ** 14 packs **  20 of 20 slots open, Record: 6397.1KB/s
101) -gettor- ** Bandwidth Usage ** Current: 0.0KB/s, Record: 10.3KB/s
102) -gettor- ** To request a file, type "/msg gettor xdcc send #x" **
103) -gettor- ** To request details, type "/msg gettor xdcc info #x" **
104) -gettor- #1  1x [1.2M] tor-0.1.2.19.tar.gz
105) -gettor- #2  0x [ <1K] tor-0.1.2.19.tar.gz.asc
106) </pre>
107) <br>
108) To fetch the Tor source code and signature file, a user would simply need to
109) send the following commands: <br>
110) <pre>

111) '/msg gettor xdcc send #1'
112) '/msg gettor xdcc send #2'

113) </pre>
114) <br>

115) <p>

116) After these commands are sent, the <tt>gettor</tt> user will respond. It will 
117) send each file as a XDCC file transfer. Depending on the IRC client in use, you may have
118) to manually accept the file, please consult the manual for your software or 

119) <a href="<page contact>">contact us for help</a>.</p>
120) <p>

121) It is
122) very important to <a

123) href="<page verifying-signatures>">verify

124) the cryptographic signatures</a> of our software when using DCC file transfers
125) just as with any type of mirroring. Someone could easily impersonate the IRC 
126) user and send trojaned software. Always validate the cryptographic signature
127) of any package before attempting to do an installation of the software.

128) </p>
129) 

130)   </div><!-- #main -->
131)