tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

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

10) Sometimes it's not possible to directly reach the Tor Project website. 
11) We're currently

12) working on ways to help users find, download, and install a current version of
13) Tor without already having Tor. We know that these suggestions are imperfect,

14) but we hope that users will be able to find Tor indirectly if our website is

15) blocked. If you're reading this from a search engine's cache, directly from our
16) website, or by some other method, we hope these suggestions are helpful.

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

19) </p>
20) 
21) <h2>Fetching Tor with Tor: Using your web browser</h2>
22) <hr />
23) <p>

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

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

28) Please take care to <a

29) href="http://wiki.noreply.org/noreply/TheOnionRouter/VerifyingSignatures">verify
30) the signature</a> of any downloaded package when possible.

31) </p>
32) 
33) <h2>With a little help from our friends: Using Mirrors</h2>
34) <hr />
35) <p>

36) A Tor mirror is a site that contains an exact copy of our main site.
37) People who cannot reach the Tor website are encouraged to visit our <a
38) href="<page mirrors>">mirrors</a> to download copies of our source code as well

39) as binary builds for their desired platforms. You may want to use

40) a search engine to find mirrors if our mirror page is blocked or seemingly

41) unresponsive. It is very important to <a

42) href="http://wiki.noreply.org/noreply/TheOnionRouter/VerifyingSignatures">verify

43) the cryptographic signatures</a> of our software when using any mirror. We
44) cannot ensure the safety or security of any package hosted on remote mirrors

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

47) </p>
48) 
49) <h2>Fetching Tor via email: gettor</h2>
50) <hr />
51) <p>

52) It is possible to get a copy of Tor by sending an email to a special email
53) address: '<tt>gettor AT torproject.org</tt>'. This email system is a gateway
54) that allows anyone who can send email to get a copy of Tor. Currently, we only
55) support mail systems that we know
56) don't mind large email attachments. Gmail and Yahoo! mail are two such mail
57) services that are known to work. This is useful for users who can send email
58) but have no other direct method of downloading Tor. A user only needs to tell
59) us their Operating System (Windows XP? Mac OS X? Linux?). An email with the
60) requested package will be sent shortly.

61) </p>
62) 
63) <h2>Fetching Tor via IRC: gettor</h2>
64) <hr />
65) <p>
66) It is possible to fetch the source code, binaries and other files related to 
67) Tor by using the XDCC IRC file transfer protocol. It is best to attempt this 
68) only if you connect to the IRC server using SSL. Currently <tt>gettor</tt> 

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

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

101) '/msg gettor xdcc send #1'
102) '/msg gettor xdcc send #2'

103) </pre>
104) </tt>
105) <br>
106) After these commands are sent, the <tt>gettor</tt> user will respond. It will 
107) send each file as a XDCC file transfer. Depending on the IRC client in use, you may have
108) to manually accept the file, please consult the manual for your software or 
109) <a href="<page contact>">contact us for help</a>.<br>
110) <br>
111) It is
112) very important to <a
113) href="http://wiki.noreply.org/noreply/TheOnionRouter/VerifyingSignatures">verify
114) the cryptographic signatures</a> of our software when using DCC file transfers
115) just as with any type of mirroring. Someone could easily impersonate the IRC 
116) user and send trojaned software. Always validate the cryptographic signature
117) of any package before attempting to do an installation of the software.

118) </p>
119) 

120)   </div><!-- #main -->
121)