tor-webwml.git

1) ## translation metadata
2) # Revision: $Revision$
3) # Translation-Priority: 3-low
4) 

5) #include "head.wmi" TITLE="Torbutton Options" CHARSET="UTF-8"

6) 
7) <div class="main-column">
8) 
9) <!-- PUT CONTENT AFTER THIS TAG -->
10) 
11) <h2>Torbutton Options</h2>
12) <hr />
13) 

14) <p>Torbutton 1.2.0 adds several new security features to protect your
15) anonymity from all the major threats we know about. The defaults should be
16) fine (and safest!) for most people, but in case you are the tweaker type,

17) or if you prefer to try to outsource some options to more flexible extensions,
18) here is the complete list. (In an ideal world, these descriptions should all be
19) tooltips in the extension itself, but Firefox bugs <a
20) href="https://bugzilla.mozilla.org/show_bug.cgi?id=45375">45375</a> and <a
21) href="https://bugzilla.mozilla.org/show_bug.cgi?id=218223">218223</a> currently

22) prevent this.)</p>

23) 
24) <ul>

25)  <li>Disable plugins on Tor Usage (crucial)<p> 

26) 
27)   This option is key to Tor security. Plugins perform their own networking
28) independent of the browser, and many plugins only partially obey even their own
29) proxy settings.

30) </p></li>

31)   <li>Isolate Dynamic Content to Tor State (crucial)<p> 

32) 
33)   Another crucial option, this setting causes the plugin to disable Javascript
34)   on tabs that are loaded during a Tor state different than the current one,
35)   to prevent delayed fetches of injected URLs that contain unique identifiers,
36)   and to prevent meta-refresh tags from revealing your IP when you turn off
37)   Tor. It also prevents all fetches from tabs loaded with an opposite Tor
38)   state. This serves to block non-Javascript dynamic content such as CSS
39)   popups from revealing your IP address if you disable Tor.

40) </p></li>

41)   <li>Hook Dangerous Javascript (crucial)<p> 

42) 
43) This setting enables the Javascript hooking code. Javascript is injected into
44) pages to hook the Date object to mask your timezone, and to hook the navigator
45) object to mask OS and user agent properties not handled by the standard
46) Firefox user agent override settings.

47) </p></li>

48)   <li>Resize window dimensions to multiples of 50px on toggle (recommended)<p> 

49) 
50) To cut down on the amount of state available to fingerprint users uniquely, 
51) this pref causes windows to be resized to a multiple of 50 pixels on each
52) side when Tor is enabled and pages are loaded.

53) </p></li>

54)   <li>Disable Updates During Tor (recommended)<p> 

55) 
56) Under Firefox 2, many extension authors did not update their extensions from 
57) SSL-enabled websites. It is possible for malicious Tor nodes to hijack these extensions and replace them with malicious ones, or add malicious code to 
58) existing extensions. Since Firefox 3 now enforces encrypted and/or
59) authenticated updates, this setting is no longer as important as it once
60) was (though updates do leak information about which extensions you have, it is
61) fairly infrequent).

62) </p></li>

63)   <li>Disable Search Suggestions during Tor (optional)<p> 

64) 
65) This optional setting governs if you get Google search suggestions during Tor
66) usage. Since no cookie is transmitted during search suggestions, this is a
67) relatively benign behavior.

68) </p></li>
69)   <li>Block Livemarks updates during Tor usage (recommended)<p> 
70) 
71) This setting causes Torbutton to disable your <a
72) href="http://www.mozilla.com/firefox/livebookmarks.html">Live bookmark</a>
73) updates. Since most people use Live bookmarks for RSS feeds from their blog,
74) their friends' blogs, the wikipedia page they edit, and other such things,
75) these updates probably should not happen over Tor. This feature takes effect
76) in Firefox 3.5 and above only.
77) 

78) </p></li>

79)   <li>Block Tor/Non-Tor access to network from file:// urls (recommended)<p> 

80) 
81) These settings prevent local html documents from transmitting local files to
82) arbitrary websites <a href="http://www.gnucitizen.org/blog/content-disposition-hacking/">under Firefox 2</a>. Since exit nodes can insert headers that
83) force the browser to save arbitrary pages locally (and also inject script into
84) arbitrary html files you save to disk via Tor), it is probably a good idea to
85) leave this setting on.

86) </p></li>

87)   <li>Close all Non-Tor/Tor windows and tabs on toggle (optional)<p> 

88) 
89) These two settings allow you to obtain a greater degree of assurance that
90) after you toggle out of Tor, the pages are really gone and can't perform any
91) extra network activity. Currently, there is no known way that pages can still
92) perform activity after toggle, but these options exist as a backup measure
93) just in case a flaw is discovered. They can also serve as a handy 'Boss
94) Button' feature for clearing all Tor browsing off your screen in a hurry.

95) </p></li>

96)   <li>Isolate access to history navigation to Tor state (crucial)<p> 

97) 
98) This setting prevents both Javascript and accidental user clicks from causing
99) the session history to load pages that were fetched in a different Tor state
100) than the current one. Since this can be used to correlate Tor and Non-Tor
101) activity and thus determine your IP address, it is marked as a crucial 
102) setting.

103) </p></li>

104)   <li>Block History Reads during Tor (crucial)<p> 

105) 
106)   Based on code contributed by <a href="http://www.collinjackson.com/">Collin
107)   Jackson</a>, when enabled and Tor is enabled, this setting prevents the
108) rendering engine from knowing if certain links were visited.  This mechanism
109) defeats all document-based history disclosure attacks, including CSS-only
110) attacks.

111) </p></li>

112)   <li>Block History Reads during Non-Tor (recommended)<p> 

113) 
114)   This setting accomplishes the same but for your Non-Tor activity.

115) </p></li>

116)   <li>Block History Writes during Tor (recommended)<p> 

117) 
118)   This setting prevents the rendering engine from recording visited URLs, and
119) also disables download manager history. Note that if you allow writing of Tor history,
120) it is recommended that you disable non-Tor history reads, since malicious
121) websites you visit without Tor can query your history for .onion sites and
122) other history recorded during Tor usage (such as Google queries).

123) </p></li>

124)   <li>Block History Writes during Non-Tor (optional)<p> 

125) 
126) This setting also disables recording any history information during Non-Tor
127) usage.

128) </p></li>

129) <li>Clear History During Tor Toggle (optional)<p> 

130) 
131)   This is an alternate setting to use instead of (or in addition to) blocking
132) history reads or writes.

133) </p></li>

134)   <li>Block Password+Form saving during Tor/Non-Tor<p> 

135) 
136)   These options govern if the browser writes your passwords and search
137)   submissions to disk for the given state.

138) </p></li>

139)   <li>Block Tor disk cache and clear all cache on Tor Toggle<p> 

140) 
141)   Since the browser cache can be leveraged to store unique identifiers, cache
142) must not persist across Tor sessions. This option keeps the memory cache active
143) during Tor usage for performance, but blocks disk access for caching.

144) </p></li>

145)   <li>Block disk and memory cache during Tor<p> 

146) 
147)   This setting entirely blocks the cache during Tor, but preserves it for
148) Non-Tor usage.

149) </p></li>

150)   <li>Clear Cookies on Tor Toggle<p> 

151) 
152)   Fully clears all cookies on Tor toggle.

153) </p></li>

154)   <li>Store Non-Tor cookies in a protected jar<p> 

155) 
156)   This option stores your persistent Non-Tor cookies in a special cookie jar
157)   file, in case you wish to preserve some cookies. Based on code contributed
158)   by <a href="http://www.collinjackson.com/">Collin Jackson</a>. It is
159)   compatible with third party extensions that you use to manage your Non-Tor
160)   cookies. Your Tor cookies will be cleared on toggle, of course.

161) </p></li>

162)   <li>Store both Non-Tor and Tor cookies in a protected jar (dangerous)<p> 

163) 
164)   This option stores your persistent Tor and Non-Tor cookies 
165)   separate cookie jar files. Note that it is a bad idea to keep Tor
166)   cookies around for any length of time, as they can be retrieved by exit
167)   nodes that inject spoofed forms into plaintext pages you fetch.

168) </p></li>

169)   <li>Manage My Own Cookies (dangerous)<p> 

170) 
171)   This setting allows you to manage your own cookies with an alternate
172) extension, such as <a href="https://addons.mozilla.org/firefox/addon/82">CookieCuller</a>. Note that this is particularly dangerous,
173) since malicious exit nodes can spoof document elements that appear to be from
174) sites you have preserved cookies for (and can then do things like fetch your
175) entire gmail inbox, even if you were not using gmail or visiting any google
176) pages at the time!).

177) </p></li>

178)   <li>Do not write Tor/Non-Tor cookies to disk<p> 

179) 
180)   These settings prevent Firefox from writing any cookies to disk during the
181)   corresponding Tor state. If cookie jars are enabled, those jars will
182)   exist in memory only, and will be cleared when Firefox exits.

183) </p></li>

184)   <li>Disable DOM Storage during Tor usage (crucial)<p> 

185) 
186)   Firefox has recently added the ability to store additional state and
187)   identifiers in persistent tables, called <a
188)   href="http://developer.mozilla.org/docs/DOM:Storage">DOM Storage</a>.
189)   Obviously this can compromise your anonymity if stored content can be
190)   fetched across Tor-state.

191) </p></li>

192)   <li>Clear HTTP auth sessions (recommended)<p> 

193) 
194)   HTTP authentication credentials can be probed by exit nodes and used to both confirm that you visit a certain site that uses HTTP auth, and also impersonate you on this site. 

195) </p></li>

196)   <li>Clear cookies on Tor/Non-Tor shutdown<p> 

197) 
198)   These settings install a shutdown handler to clear cookies on Tor
199) and/or Non-Tor browser shutdown. It is independent of your Clear Private Data
200) settings, and does in fact clear the corresponding cookie jars.

201) </p></li>

202)   <li>Prevent session store from saving Tor-loaded tabs (recommended)<p> 

203) 
204)   This option augments the session store to prevent it from writing out
205)   Tor-loaded tabs to disk. Unfortunately, this also disables your ability to 
206)   undo closed tabs. The reason why this setting is recommended is because
207)   after a session crash, your browser will be in an undefined Tor state, and
208)   can potentially load a bunch of Tor tabs without Tor. The following option
209)   is another alternative to protect against this.

210) </p></li>

211)   <li>On normal startup, set state to: Tor, Non-Tor, Shutdown State<p> 

212) 
213)   This setting allows you to choose which Tor state you want the browser to
214)   start in normally: Tor, Non-Tor, or whatever state the browser shut down in.

215) </p></li>

216)   <li>On crash recovery or session restored startup, restore via: Tor, Non-Tor<p> 

217) 
218)   When Firefox crashes, the Tor state upon restart usually is completely
219)   random, and depending on your choice for the above option, may load 
220)   a bunch of tabs in the wrong state. This setting allows you to choose
221)   which state the crashed session should always be restored in to.

222) </p></li>

223)   <li>Prevent session store from saving Non-Tor/Tor-loaded tabs<p> 

224) 
225)   These two settings allow you to control what the Firefox Session Store
226)   writes to disk. Since the session store state is used to automatically
227)   load websites after a crash or upgrade, it is advisable not to allow
228)   Tor tabs to be written to disk, or they may get loaded in Non-Tor
229)   after a crash (or the reverse, depending upon the crash recovery setting, 
230)   of course).

231) </p></li>

232)   <li>Set user agent during Tor usage (crucial)<p> 

233) 
234)   User agent masking is done with the idea of making all Tor users appear
235) uniform. A recent Firefox 2.0.0.4 Windows build was chosen to mimic for this
236) string and supporting navigator.* properties, and this version will remain the
237) same for all TorButton versions until such time as specific incompatibility
238) issues are demonstrated. Uniformity of this value is obviously very important
239) to anonymity. Note that for this option to have full effectiveness, the user
240) must also allow Hook Dangerous Javascript ensure that the navigator.*
241) properties are reset correctly.  The browser does not set some of them via the
242) exposed user agent override preferences.

243) </p></li>

244)   <li>Spoof US English Browser<p> 

245) 
246) This option causes Firefox to send http headers as if it were an English
247) browser. Useful for internationalized users.

248) </p></li>

249)   <li>Don't send referrer during Tor Usage<p> 

250) 
251) This option disables the referrer header, preventing sites from determining
252) where you came from to visit them. This can break some sites, however. <a
253) href="http://www.digg.com">Digg</a> in particular seemed to be broken by this.
254) A more streamlined, less intrusive version of this option should be available
255) eventually. In the meantime, <a
256) href="https://addons.mozilla.org/firefox/addon/953">RefControl</a> can
257) provide this functionality via a default option of <b>Forge</b>.

258) </p></li>