git.schokokeks.org
Repositories
Help
Report an Issue
tor-webwml.git
Code
Commits
Branches
Tags
Suche
Strukturansicht:
33dabf51f
Branches
Tags
bridges
docs-debian
jobs
master
press-clips
tor-webwml.git
en
finding-tor.wml
The pages en/download-unix.wml, en/download.wml and en/finding-tor.wml linked to the wiki for verifying signatures. I've corrected the links to point to <page verifying-signatures> instead.
Oliver Knapp
commited
33dabf51f
at 2009-02-12 15:36:35
finding-tor.wml
Blame
History
Raw
## translation metadata # Revision: $Revision$ #include "head.wmi" TITLE="Tor: Finding Tor" <div class="main-column"> <h1>Tor: Finding Tor</h1> <hr /> <p> Sometimes it's not possible to directly reach the Tor Project website. Here are some ways that you can find and download a current version of Tor if our website is blocked in your area. If you're reading this from a search engine's cache, directly from our website, or by some other method, we hope these suggestions are helpful. Additionally, if you have ideas for how to improve these instructions, please <a href="<page contact>">contact us</a> and let us know. </p> <a id="WithTor"></a> <h2><a class="anchor" href="#WithTor">Fetching Tor with Tor: Using your web browser</a></h2> <hr /> <p> If you're already running Tor, you should be able to download a new Tor securely with your current Tor. You should do this for your friends who don't already have Tor. You can do this from our <a href="<page download>">download page</a> or from a download page on one of the many Tor <a href="<page mirrors>">mirrors</a>. Please take care to <a href="<page verifying-signatures>">verify the signature</a> of any downloaded package when possible. </p> <a id="Mirrors"></a> <h2><a class="anchor" href="#Mirrors">With a little help from our friends: Using Mirrors</a></h2> <hr /> <p> A Tor mirror is a website that contains an exact copy of our main site. We have <a href="<page mirrors>">several dozen mirrors</a> currently, and you can find the list by searching for "Tor mirrors" on your favorite search engine. </p> <p> It is very important to <a href="<page verifying-signatures>">verify the cryptographic signatures</a> on the Tor software when using any mirror. We cannot ensure the safety or security of any package hosted on remote mirrors without a signature. It's probably safe, but a cautious user should check signatures when possible. </p> <a id="Mail"></a> <h2><a class="anchor" href="#Mail">Fetching Tor via Gmail: gettor</a></h2> <hr /> <p> It is possible to get a copy of Tor by sending an email to a special email address: '<tt>gettor AT torproject.org</tt>'. Now anyone who can send email can get a copy of Tor. A user only needs to send us a request with 'help' in the body of the email, and instructions will be sent as a reply. </p> <p> To avoid spamming people accidentally, we only answer emails that are sent from email services that support <a href="http://www.dkim.org/">DKIM</a>, which is an email feature that lets us verify that the address in the "From" line is actually the one who sent the mail. Gmail is an example of a mail service that is known to work. If we get an email from a service that doesn't use DKIM, we'll send a short explanation and then ignore the email address for the next day or so. </p> <a id="IRC"></a> <h2><a class="anchor" href="#IRC">Fetching Tor via IRC: gettor</a></h2> <hr /> <p> It is possible to fetch the source code, binaries and other files related to Tor by using the XDCC IRC file transfer protocol. It is best to attempt this only if you connect to the IRC server using SSL. Currently <tt>gettor</tt> is known to spend time on Freenode, 2600, Indymedia and OFTC. <br><br> If you're currently able to connect to one of those IRC networks, look for a user named '<tt>gettor</tt>' that is connected from the host '<tt>check.torproject.org</tt>'. Send the user a private message like so: <br> <br> '<tt>/msg gettor xdcc list</tt>' <br> <br> The <tt>gettor</tt> user should respond with a list of files available for download. If there is no response, something has gone wrong. Some IRC networks require that you are registered before you can send private queries to other users (this is often to reduce spam). You may need to register with the NickServ before you can talk to the <tt>'gettor'</tt> user. <br> An example response returned by <tt>gettor</tt> is presented below:<br> <pre> -gettor- ** 14 packs ** 20 of 20 slots open, Record: 6397.1KB/s -gettor- ** Bandwidth Usage ** Current: 0.0KB/s, Record: 10.3KB/s -gettor- ** To request a file, type "/msg gettor xdcc send #x" ** -gettor- ** To request details, type "/msg gettor xdcc info #x" ** -gettor- #1 1x [1.2M] tor-0.1.2.19.tar.gz -gettor- #2 0x [ <1K] tor-0.1.2.19.tar.gz.asc </pre> <br> To fetch the Tor source code and signature file, a user would simply need to send the following commands: <br> <pre> '/msg gettor xdcc send #1' '/msg gettor xdcc send #2' </pre> <br> <p> After these commands are sent, the <tt>gettor</tt> user will respond. It will send each file as a XDCC file transfer. Depending on the IRC client in use, you may have to manually accept the file, please consult the manual for your software or <a href="<page contact>">contact us for help</a>.</p> <p> It is very important to <a href="<page verifying-signatures>">verify the cryptographic signatures</a> of our software when using DCC file transfers just as with any type of mirroring. Someone could easily impersonate the IRC user and send trojaned software. Always validate the cryptographic signature of any package before attempting to do an installation of the software. </p> </div><!-- #main --> #include <foot.wmi>