Update the finding-tor page to include possible IRC DCC bots that may be lurking on an irc network. This should help people who are unable to visit our main website but are still able to connect to IRC. We'll need many of these bots to be effective.
Jacob Appelbaum commited on 2008-06-29 11:38:52
Zeige 1 geänderte Dateien mit 57 Einfügungen und 0 Löschungen.
- en/finding-tor.wml 889c03ebd..4530c73b5
| ... | ... |
@@ -58,6 +58,63 @@ services that are known to work. This is useful for users who can send email |
| 58 | 58 |
but have no other direct method of downloading Tor. A user only needs to tell |
| 59 | 59 |
us their Operating System (Windows XP? Mac OS X? Linux?). An email with the |
| 60 | 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 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. |
|
| 61 | 118 |
</p> |
| 62 | 119 |
|
| 63 | 120 |
</div><!-- #main --> |
| 64 | 121 |