Sebastian Hahn commited on 2010-02-14 19:51:10
Zeige 1 geänderte Dateien mit 0 Einfügungen und 59 Löschungen.
... | ... |
@@ -74,65 +74,6 @@ which is an email feature that lets us verify that the address in the |
74 | 74 |
mail service that is known to work. If we get an email |
75 | 75 |
from a service that doesn't use DKIM, we'll send a short explanation |
76 | 76 |
and then ignore the email address for the next day or so. |
77 |
-</p> |
|
78 |
- |
|
79 |
-<a id="IRC"></a> |
|
80 |
-<h2><a class="anchor" href="#IRC">Fetching Tor via IRC: gettor</a></h2> |
|
81 |
-<hr /> |
|
82 |
- |
|
83 |
-<p> |
|
84 |
-It is possible to fetch the source code, binaries and other files related to |
|
85 |
-Tor by using the XDCC IRC file transfer protocol. It is best to attempt this |
|
86 |
-only if you connect to the IRC server using SSL. Currently <tt>gettor</tt> |
|
87 |
-is known to spend time on Freenode, 2600, Indymedia and OFTC. |
|
88 |
-<br/><br/> |
|
89 |
-If you're currently able to connect to one of those IRC networks, look for a |
|
90 |
-user named '<tt>gettor</tt>' that is connected from the host |
|
91 |
-'<tt>check.torproject.org</tt>'. Send the user a private message like so: |
|
92 |
-<br/> |
|
93 |
-<br/> |
|
94 |
-'<tt>/msg gettor xdcc list</tt>' |
|
95 |
-<br/> |
|
96 |
-<br/> |
|
97 |
-The <tt>gettor</tt> user should respond with a list of files |
|
98 |
-available for download. If there is no response, something has gone wrong. Some |
|
99 |
-IRC networks require that you are registered before you can send private |
|
100 |
-queries to other users (this is often to reduce spam). You may need to register |
|
101 |
-with the NickServ before you can talk to the <tt>'gettor'</tt> user. |
|
102 |
-<br/> |
|
103 |
-An example response returned by <tt>gettor</tt> is presented below:<br/> |
|
104 |
-<pre> |
|
105 |
--gettor- ** 14 packs ** 20 of 20 slots open, Record: 6397.1KB/s |
|
106 |
--gettor- ** Bandwidth Usage ** Current: 0.0KB/s, Record: 10.3KB/s |
|
107 |
--gettor- ** To request a file, type "/msg gettor xdcc send #x" ** |
|
108 |
--gettor- ** To request details, type "/msg gettor xdcc info #x" ** |
|
109 |
--gettor- #1 1x [1.2M] tor-0.1.2.19.tar.gz |
|
110 |
--gettor- #2 0x [ <1K] tor-0.1.2.19.tar.gz.asc |
|
111 |
-</pre> |
|
112 |
-<br/> |
|
113 |
-To fetch the Tor source code and signature file, a user would simply need to |
|
114 |
-send the following commands: <br/> |
|
115 |
-<pre> |
|
116 |
-'/msg gettor xdcc send #1' |
|
117 |
-'/msg gettor xdcc send #2' |
|
118 |
-</pre> |
|
119 |
-<br/> |
|
120 |
-</p> |
|
121 |
- |
|
122 |
-<p> |
|
123 |
-After these commands are sent, the <tt>gettor</tt> user will respond. It will |
|
124 |
-send each file as a XDCC file transfer. Depending on the IRC client in use, you may have |
|
125 |
-to manually accept the file, please consult the manual for your software or |
|
126 |
-<a href="<page contact>">contact us for help</a>.</p> |
|
127 |
- |
|
128 |
-<p> |
|
129 |
-It is |
|
130 |
-very important to <a |
|
131 |
-href="<page verifying-signatures>">verify |
|
132 |
-the cryptographic signatures</a> of our software when using DCC file transfers |
|
133 |
-just as with any type of mirroring. Someone could easily impersonate the IRC |
|
134 |
-user and send trojaned software. Always validate the cryptographic signature |
|
135 |
-of any package before attempting to do an installation of the software. |
|
136 | 77 |
</p> |
137 | 78 |
|
138 | 79 |
</div><!-- #main --> |
139 | 80 |