Remove NoScript from conflicting addons list and add it and others to recommended list.
Mike Perry

Mike Perry commited on 2009-05-16 03:05:29
Zeige 1 geänderte Dateien mit 87 Einfügungen und 34 Löschungen.

... ...
@@ -78,6 +78,14 @@ cookies</a>. It is possible to use a LiveCD or VMWare-based solution such as
78 78
 <a href="http://anonymityanywhere.com/incognito/">Incognito</a> that creates a
79 79
 secure, transparent proxy to protect you from proxy bypass, however issues
80 80
 with local IP address discovery and Flash cookies potentially remain.
81
+</p>
82
+<p>
83
+
84
+If you are not concerned about being tracked by these sites (and others that
85
+try to unmask you by pretending to be them), and are unconcerned about your
86
+local censors noticing you visit them, you can enable plugins by going into the
87
+Torbtuton Preferences-&gt;Security Settings-&gt;Dynamic Content tab and
88
+unchecking "Disable plugins during Tor usage" box.
81 89
 
82 90
 </p>
83 91
 
... ...
@@ -89,20 +97,20 @@ annoying. Can't I just use the old version?</a></strong>
89 97
 
90 98
 <b>No.</b> Use of the old version, or any other vanilla proxy changer
91 99
 (including FoxyProxy -- see below) without Torbutton is actively discouraged.
92
-Seriously. Using a vanilla proxy switcher by itself is so insecure that you
93
-are not only just wasting your time, you are also actually endangering
94
-yourself. Simply do not use Tor and you will have the same (and in some cases,
95
-better) security.  For more information on the types of attacks you are
96
-exposed to with a "homegrown" solution, please see <a
100
+Seriously. Using a vanilla proxy switcher by itself is so insecure that you are
101
+not only just wasting your time, you are also actually endangering yourself.
102
+<b>Simply do not use Tor</b> and you will have the same (and in some cases,
103
+better) security.  For more information on the types of attacks you are exposed
104
+to with a "homegrown" solution, please see <a
97 105
 href="https://www.torproject.org/torbutton/design/#adversary">The Torbutton
98
-Adversary Model</a>, in particular the 
99
-<a href="https://www.torproject.org/torbutton/design/#attacks">Adversary
106
+Adversary Model</a>, in particular the <a
107
+href="https://www.torproject.org/torbutton/design/#attacks">Adversary
100 108
 Capabilities - Attacks</a> subsection. If there are any specific Torbutton
101 109
 behaviors that you do not like, please file a bug on <a
102 110
 href="https://bugs.torproject.org/flyspray/index.php?tasks=all&amp;project=5">the
103
-bug tracker.</a> Most of Torbutton's security features can also be disabled
104
-via its preferences, if you think you have your own protection for those
105
-specific cases.
111
+bug tracker.</a> Most of Torbutton's security features can also be disabled via
112
+its preferences, if you think you have your own protection for those specific
113
+cases.
106 114
 
107 115
 </p>
108 116
 
... ...
@@ -192,37 +200,15 @@ cooperate with sites to inject images into pages that bypass your filters.
192 200
 Setting FoxyProxy to only send certain URLs via Non-Tor is much more secure in
193 201
 this regard, but be very careful with the filters you allow. For example, 
194 202
 something as simple as allowing *google* to go via Non-Tor will still cause you to end up
195
-in all the logs of all websites that use Google Analytics!  See <a
196
-href="http://foxyproxy.mozdev.org/faq.html#privacy-01">this question</a> on
203
+in all the logs of all websites that use Google Analytics!  See 
204
+<a href="http://foxyproxy.mozdev.org/faq.html#privacy-01">this question</a> on
197 205
 the FoxyProxy FAQ for more information.
198 206
  </p></li>
199
- <li>NoScript
200
- <p>
201
- Torbutton currently mitigates all known anonymity issues with Javascript.
202
- While it may be tempting to get better security by disabling Javascript for
203
- certain sites, you are far better off with an all-or-nothing approach.
204
- NoScript is exceedingly complicated, and has many subtleties that can surprise
205
- even advanced users. For example, addons.mozilla.org verifies extension
206
- integrity via Javascript over https, but downloads them in the clear. Not 
207
- adding it to your whitelist effectively
208
- means you are pulling down unverified extensions. Worse still, using NoScript
209
- can actually disable protections that Torbutton itself provides via
210
- Javascript, yet still allow malicious exit nodes to compromise your
211
- anonymity via the default whitelist (which they can spoof to inject any script  they want). 
212
-</p></li>
213 207
 </ol>
214 208
 
215 209
 <a id="recommendedextensions"></a>
216 210
 <strong><a class="anchor" href="#recommendedextensions">Which Firefox extensions do you recommend?</a></strong>
217 211
 <ol>
218
- <li><a href="https://crypto.stanford.edu/forcehttps/">ForceHTTPS</a>
219
-	<p>
220
-Many sites on the Internet are <a
221
-href="http://www.defcon.org/html/defcon-16/dc-16-speakers.html#Perry">sloppy
222
-about their use of HTTPS</a> and secure
223
-cookies. This addon can help you ensure that you always use HTTPS for sites
224
-that support it, and reduces the chances of your cookies being stolen for
225
-sites that do not secure them.</p></li>
226 212
  <li><a href="https://addons.mozilla.org/firefox/addon/953">RefControl</a>
227 213
 	<p>
228 214
 Mentioned above, this extension allows more fine-grained referrer spoofing
... ...
@@ -236,6 +223,73 @@ identifiers in your cache. This extension applies same origin policy to the
236 223
 cache, so that elements are retrieved from the cache only if they are fetched
237 224
 from a document in the same origin domain as the cached element. 
238 225
 </p></li>
226
+ </li>
227
+
228
+ <li><a href="https://addons.mozilla.org/en-US/firefox/addon/6623">Better
229
+Privacy</a>
230
+ <p>
231
+
232
+Better Privacy is an excellent extension that protects you from cookies used
233
+by Flash applications, which often persist forever and are not clearable via
234
+normal Firefox "Private Data" clearing. Flash and all other plugins are
235
+disabled by Torbutton by default, but if you are interested in privacy, you
236
+may want this extension to allow you to inspect and automatically clear your
237
+Flash cookies for your Non-Tor usage.
238
+
239
+ </p>
240
+ </li>
241
+ <li><a href="https://addons.mozilla.org/firefox/addon/1865">AdBlock Plus</a>
242
+ <p>
243
+
244
+AdBlock Plus is an excellent addon for removing annoying, privacy-invading,
245
+and <a
246
+href="http://www.wired.com/techbiz/media/news/2007/11/doubleclick">malware-distributing</a>
247
+advertisements from the web. It provides 
248
+<a href="http://adblockplus.org/en/subscriptions">subscriptions</a> that are
249
+continually updated to catch the latest efforts of ad networks to circumvent
250
+these filters. I recommend the EasyPrivacy+EasyList combination filter
251
+subscription in the Miscellaneous section of the subscriptions page.
252
+
253
+ </p>
254
+ <li><a href="https://addons.mozilla.org/firefox/addon/82">Cookie Culler</a>
255
+ <p>
256
+
257
+Cookie Culler is a handy extension to give quick access to the cookie manager
258
+in Firefox. It also provides the ability to protect certain cookies from
259
+deletion, but unfortunately, this behavior does not integrate well with Torbutton. Kory Kirk is working on addressing this for this Google Summer of Code project for 2009.
260
+
261
+ </p>
262
+ </li>
263
+
264
+ <li><a href="https://addons.mozilla.org/en-US/firefox/addon/722">NoScript</a>
265
+ <p>
266
+ Torbutton currently mitigates all known anonymity issues with Javascript.
267
+ However, if you are concerned about Javascript exploits against your browser
268
+ or against websites you are logged in to, you may want to use NoScript. It
269
+ provides the ability to allow Javascript only for particular websites 
270
+ and also provides mechanisms to force HTTPS urls for sites with 
271
+<a href="http://fscked.org/category/tags/insecurecookies">insecure
272
+ cookies</a>.<br>
273
+
274
+ It can be difficult to configure such that the majority sites will work
275
+ properly though. In particular, you want to make sure you do not remove the Javascript whitelist for
276
+ addons.mozilla.org, as extensions are downloaded via http and verified by
277
+ javascript from the https page.
278
+
279
+ </p></li>
280
+ <li><a href="https://addons.mozilla.org/en-US/firefox/addon/9727/">Request
281
+Policy</a>
282
+ <p>
283
+
284
+Request Policy is similar to NoScript in that it requires that you configure
285
+which sites are allowed to load content from other domains. It can be very
286
+difficult for novice users to configure properly, but it does provide a good
287
+deal of protection against ads, injected content, and cross-site request
288
+forgery attacks.
289
+
290
+ </p>
291
+ </li>
292
+
239 293
 </ol>
240 294
 
241 295
 <a id="securityissues"></a>
242 296