tor-webwml.git

1) ## translation metadata

2) # Revision: $Revision$

3) # Translation-Priority: 3-low
4) 

5) #include "head.wmi" TITLE="Tor Project: GetTor email autoresponder" CHARSET="UTF-8" ANNOUNCE_RSS="yes"

6) <div id="content" class="clearfix">
7) 	<div id="breadcrumbs">
8)     <a href="<page index>">Home &raquo; </a>
9)     <a href="<page projects/projects>">Projects &raquo; </a>

10)     <a href="<page projects/gettor>">GetTor &raquo; </a>

11)   </div>
12) 	<div id="maincol"> 
13) 

14)     <h1>GetTor e-mail autoresponder</h1>

15) <p>GetTor is a program for serving Tor and related files over SMTP. Users
16) interact with GetTor by sending it email.</p>
17) 

18) <h2>Finding GetTor</h2>

19) 
20) <p>It is assumed that a user has a method of finding a valid GetTor
21) email robot.  Currently the best known GetTor email is gettor @
22) torproject.org. This should be the most current stable GetTor robot as
23) it is operated by the Tor Project.</p>
24) 
25) 

26) <h2>Requirements for using GetTor</h2>

27) 
28) <p>Users communicate with the GetTor robot by sending messages via email.
29) The messages are currently English keywords. The user must use an email
30) provider that signs their email with DKIM. A user will be alerted if
31) their email provider is unsupported.</p>
32) 

33) <h2>Using GetTor</h2>

34) 
35) <p>Currently, users have a limited set of options. It is best to send an
36) email with a message body (the subject line can be blank) that consists
37) of only the word 'help' to receive instructions. This will send the most
38) current set of choices. An example reply to a request for help
39) follows:</p>
40) 

41) <pre>

42)   Hello, This is the "gettor" robot.
43) 
44)    I am sorry, but your request was not understood. Please select one
45)    of the following package names:
46) 
47)        panther-bundle
48)        source-bundle
49)        windows-bundle
50)        tiger-bundle
51)        tor-browser-bundle
52)        tor-im-browser-bundle
53) 
54)    Please send me another email. It only needs a single package name
55)    anywhere in the body of your email.

56) </pre>

57) <br>

58) 
59) <p>For example, it is possible to fetch the most current Windows bundle. A
60) user may send a request with only the word 'windows-bundle' in the body of the
61) email. An example reply would look something like the following:</p>
62) 

63) <pre>

64)    Hello! This is the "gettor" robot.
65) 
66)    Here's your requested software as a zip file. Please unzip the
67)    package and verify the signature.
68) 
69)    Hint: If your computer has GnuPG installed, use the gpg
70)    commandline tool as follows after unpacking the zip file:
71) 

72)       gpg --verify <packagename>.asc <packagename>

73) 
74)    The output should look somewhat like this:
75) 

76)       gpg: Good signature from "Roger Dingledine <arma@mit.edu>"

77) 
78)    If you're not familiar with commandline tools, try looking for
79)    a graphical user interface for GnuPG on this website:
80) 
81)       http://www.gnupg.org/related_software/frontends.html
82) 
83)    Have fun.

84) </pre>

85) <br>

86) 
87) <p>The email should also include an attachment with the name
88) 'windows-bundle.z' that can be downloaded by the user. The user must now
89) unpack the zip file and if they wish, they may verify that the file is
90) from the Tor Project.</p>
91) 
92) <h2>Unpacking and verifying the requested files</h2>
93) 
94) <p>A user should have software for decompressing .zip files. It will
95) contain at least two files, the requested bundle and its digital
96) signature. Before a user installs the bundle, they should verify the
97) signature.</p>
98) 
99) <p>Users should follow the most current instructions for <a href="<page

100) docs/verifying-signatures>">signature verification</a>.</p>