tor-webwml.git

1) ## translation metadata

2) # Based-On-Revision: 16108

3) # Last-Translator: mfr(ät]misericordia.be
4) 
5) #include "head.wmi" TITLE="Torbutton - Basculez rapidement sur le réseau Tor avec Firefox" CHARSET="UTF-8"
6) 
7) <div class="main-column">
8) 
9) <!-- PUT CONTENT AFTER THIS TAG -->
10) 
11) <link rel="search" type="application/opensearchdescription+xml" title="Google Canada" href="search/google-ca.xml">
12) <link rel="search" type="application/opensearchdescription+xml" title="Google UK" href="search/google-uk.xml">
13) <link rel="search" type="application/opensearchdescription+xml" title="Google USA" href="search/google-us.xml">

14) <script type="text/javascript">

15) 
16) function addSearchProvider(prov) {
17) 
18) try {
19) window.external.AddSearchProvider(prov);
20) }
21) 
22) catch (e) {
23) alert("Search plugins require Firefox 2");
24) return;
25) }
26) }
27) 
28) function addEngine(name,ext,cat,pid)
29) {
30)   if ((typeof window.sidebar == "object") && (typeof window.sidebar.addSearchEngine == "function")) {
31)     window.sidebar.addSearchEngine(
32)       "http://mycroft.mozdev.org/install.php/" + pid + "/" + name + ".src",
33)       "http://mycroft.mozdev.org/install.php/" + pid + "/" + name + "."+ ext, name, cat );
34)   } else {
35)     alert("You will need a browser which supports Sherlock to install this plugin.");
36)   }
37) }
38) 
39) function addOpenSearch(name,ext,cat,pid,meth)
40) {
41)   if ((typeof window.external == "object") && ((typeof window.external.AddSearchProvider == "unknown") || (typeof window.external.AddSearchProvider == "function"))) {
42)     if ((typeof window.external.AddSearchProvider == "unknown") && meth == "p") {
43)       alert("This plugin uses POST which is not currently supported by Internet Explorer's implementation of OpenSearch.");
44)     } else {
45)       window.external.AddSearchProvider(
46)         "http://mycroft.mozdev.org/installos.php/" + pid + "/" + name + ".xml");
47)     }
48)   } else {
49)     alert("You will need a browser which supports OpenSearch to install this plugin.");
50)   }
51) }
52) 
53) function addOpenSearch2(name,ext,cat,pid,meth)
54) {
55)   if ((typeof window.external == "object") && ((typeof window.external.AddSearchProvider == "unknown") || (typeof window.external.AddSearchProvider == "function"))) {
56)     if ((typeof window.external.AddSearchProvider == "unknown") && meth == "p") {
57)       alert("This plugin uses POST which is not currently supported by Internet Explorer's implementation of OpenSearch.");
58)     } else {
59)       window.external.AddSearchProvider(
60)         "http://torbutton.torproject.org/dev/search/" + name + ".xml");
61)     }
62)   } else {
63)     alert("You will need a browser which supports OpenSearch to install this plugin.");
64)   }
65) }
66) 
67) function install (aEvent)
68) {
69)   var params = {
70)     "Torbutton": { URL: aEvent.target.href,
71)              Hash: aEvent.target.getAttribute("hash"),
72)              toString: function () { return this.URL; }
73)     }
74)   };
75)   InstallTrigger.install(params);
76) 
77)   return false;
78) }
79) 
80) 
81) </script>
82) 
83) <h2>Torbutton</h2>
84) <hr>
85) 
86) <strong>Version Actuelle:</strong><version-torbutton><br/>
87) <br/>
88) <strong>Auteurs:</strong> Scott Squires &amp; Mike Perry<br>
89) <strong>Courriel:</strong> squires at freehaven dot net, mikeperry (o) fscked/org<br/>
90) <br/>
91) <strong>Installation:</strong> 
92) <a href="http://www.torproject.org/torbutton/torbutton-current.xpi"
93)   hash="<version-hash-torbutton>"
94)   onclick="return install(event);">Local (Javascript verified)</a><br/>
95) <strong>Versions antérieures:</strong> <a href="releases/">Local</a><br/>
96) <strong>Documentation de Développement:</strong> <a href="design/">Torbutton Design Document</a> et <a href="design/MozillaBrownBag.pdf">Slides (Not actively updated)</a><br/>
97) <strong>Extras:</strong> 
98) 
99) Complément de recherche Google pour
100) 
101) <a href="/jsreq.html" title="Ref: 14938 (googleCA)"
102)  onClick="addOpenSearch('GoogleCanada','ico','General','14937','g');return false">Google CA</a>, et 
103) 
104) <a href="/jsreq.html" title="Ref: 14938 (googleCA)"
105)  onClick="addOpenSearch('googleuk_web','png','General','14445','g');return false">Google UK</a>.
106) <br/>
107) <!--
108) <strong>Install:</strong> <a href="torbutton-1.0.4.xpi">torbutton-1.0.4.xpi</a><br/>
109) -->

110) <strong>Source:</strong> Vous pouvez <a href="https://svn.torproject.org/svn/torbutton/trunk/">parcourir le référenciel</a> ou simplement dezipper le xpi.

111) <br/>

112) <strong>Rapports de Bogues:</strong> <a href="https://bugs.torproject.org/flyspray/index.php?tasks=all&amp;project=5">Torproject flyspray</a><br/>

113) <strong>Documents:</strong> <b>[</b> <a href="#FAQ">FAQ</a> <b>|</b> <a href="https://svn.torproject.org/svn/torbutton/trunk/src/CHANGELOG">changelog</a> <b>|</b> <a href="https://svn.torproject.org/svn/torbutton/trunk/src/LICENCE">licence</a> <b>|</b> <a href="https://svn.torproject.org/svn/torbutton/trunk/src/CREDITS">crédits</a> <b>]</b><br/>

114) <h2>Présentation</h2>
115) <p>

116) Torbutton est un moyen en 1-click pour les utilisateurs de Firefox d'activer
117)  ou de désactiver l'utilisation de <a href="<page index>">Tor</a> dans le 
118) 	navigateur. Il ajoute un panneau à la barre d'état qui dit "Tor Enabled" 
119) 	(en vert) or "Tor Désactivé" (en rouge). L'utilisateur peut cliquer sur le
120)  panneau pour changer de statut. Si l'utilisateur (ou une autre extension)
121)  modifie les paramètres de proxy, le changement est automatiquement pris en
122)  compte dans la barre d'état.
123) 	</p>
124) <p>
125) Certains utilisateurs peuvent préfèrer un bouton dans la barre d'outils au 
126) lieu d'un panneau d'état. Ce bouton est inclus, et l'on ajoute à la barre
127)  d'outils en cliquant avec le bouton droit sur la barre d'outils souhaitée, 
128) 	en sélectionnant "Personnaliser ...", puis en faisant glisser l'icône 
129) 	Torbutton sur la barre d'outils. Il y a une option dans les préférences 
130) 	pour cacher le panneau d'état (Outils-&gt; Modules complémentaires, 
131) 	sélectionnez Torbutton, et cliquez sur Préférences).
132) 	</p>

133) <p>

134) Les nouveaux Firefoxs ont la capacité d'envoyer les requêtes DNS à travers le proxy SOCKS, et Torbutton fera usage de cette fonctionnalité si elle est disponible dans votre version de Firefox.

135) </p>
136) 
137) <a id="FAQ"></a><h2>FAQ</h2>
138) 
139) <strong>I can't click on links or hit reload after I toggle Tor! Why?</strong>
140) <p>
141) 
142) Due to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=409737">Firefox
143) Bug 409737</a>, pages can still open popups and perform Javascript redirects
144) and history access after Tor has been toggled. These popups and redirects can
145) be blocked, but unfortunately they are indistinguishable from normal user
146) interactions with the page (such as clicking on links, opening them in new
147) tabs/windows, or using the history buttons), and so those are blocked as a
148) side effect. Once that Firefox bug is fixed, this degree of isolation will
149) become optional (for people who do not want to accidentally click on links and
150) give away information via referrers). A workaround is to right click on the
151) link, and open it in a new tab or window. The tab or window won't load
152) automatically, but you can hit enter in the URL bar, and it will begin
153) loading. Hitting enter in the URL bar will also reload the page without
154) clicking the reload button.
155) 
156) </p>
157) 
158) <strong>My browser is in some weird state where nothing works right!</strong>
159) <p>
160) 
161) Try to disable Tor by clicking on the button, and then open a new window. If
162) that doesn't fix the issue, go to the preferences page and hit 'Restore
163) Defaults'. This should reset the extension and Firefox to a known good
164) configuration.  If you can manage to reproduce whatever issue gets your
165) Firefox wedged, please file details at <a

166) href="https://bugs.torproject.org/flyspray/index.php?tasks=all&project=5">the

167) bug tracker</a>.
168) 
169) </p>
170) 
171) <strong>When I toggle Tor, my sites that use javascript stop working. Why?</strong>
172) <p>
173) Javascript can do things like wait until you have disabled Tor before trying
174) to contact its source site, thus revealing your IP address. As such, Torbutton
175) must disable Javascript, Meta-Refresh tags, and certain CSS behavior when Tor
176) state changes from the state that was used to load a given page. These features 
177) are re-enabled when Torbutton goes back into the state that was used to load
178) the page, but in some cases (particularly with Javascript and CSS) it is
179) sometimes not possible to fully recover from the resulting errors, and the
180) page is broken. Unfortunately, the only thing you can do (and still remain
181) safe from having your IP address leak) is to reload the page when you toggle
182) Tor, or just ensure you do all your work in a page before switching tor state.
183) </p>
184) 
185) 
186) <strong>When I use Tor, Firefox is no longer filling in logins/search boxes
187) for me. Why?</strong>
188) <p>
189) Currently, this is tied to the "<b>Block history writes during Tor</b>"
190) setting. If you have enabled that setting, all formfill functionality (both
191) saving and reading) is disabled. If this bothers you, you can uncheck that
192) option, but both history and forms will be saved. To prevent history
193) disclosure attacks via Non-Tor usage, it is recommended you disable Non-Tor
194) history reads if you allow history writing during Tor.
195) </p>
196) 
197) 
198) <strong>Which Firefox extensions should I avoid using?</strong>
199) <p>
200) This is a tough one. There are thousands of Firefox extensions: making a
201) complete list of ones that are bad for anonymity is near impossible. However,
202) here are a few examples that should get you started as to what sorts of
203) behavior are dangerous.
204) 
205) <ol>
206)  <li>StumbleUpon, et al</li>
207)  These extensions will send all sorts of information about the websites you
208)  visit to the stumbleupon servers, and correlate this information with a
209)  unique identifier. This is obviously terrible for your anonymity.
210)  More generally, any sort of extension that requires registration, or even
211)  extensions that provide information about websites you visit should be
212)  suspect.
213) 
214)  <li>FoxyProxy</li>
215) 
216) While FoxyProxy is a nice idea in theory, in practice it is impossible to
217) configure securely for Tor usage without Torbutton. Like all vanilla third
218) party proxy plugins, the main risks are <a
219) href="http://www.metasploit.com/research/projects/decloak/">plugin leakage</a>
220) and <a href="http://ha.ckers.org/weird/CSS-history.cgi">history
221) disclosure</a>, followed closely by cookie theft by exit nodes and tracking by
222) adservers (see the <a href="design/index.html#adversary">Torbutton Adversary
223) Model</a> for more information). However, even with Torbutton installed in
224) tandem and always enabled, it is still very difficult (though not impossible)
225) to configure FoxyProxy securely. Since FoxyProxy's 'Patterns' mode only
226) applies to specific urls, and not to an entire tab, setting FoxyProxy to only
227) send specific sites through Tor will still allow adservers to still learn your
228) real IP. Worse, if those sites use offsite logging services such as Google
229) Analytics, you may still end up in their logs with your real IP. Malicious
230) exit nodes can also cooperate with sites to inject images into pages that
231) bypass your filters. Setting FoxyProxy to only send certain URLs via Non-Tor
232) is much more viable, but be very careful with the filters you allow. For
233) example, something as simple as allowing *google* to go via Non-Tor will still
234) cause you to end up in all the logs of all websites that use Google Analytics!
235) See <a href="http://foxyproxy.mozdev.org/faq.html#privacy-01">this
236) question</a> on the FoxyProxy FAQ for more information.
237) 
238)  <li>NoScript</li>
239)  Torbutton currently mitigates all known anonymity issues with Javascript.
240)  While it may be tempting to get better security by disabling Javascript for
241)  certain sites, you are far better off with an all-or-nothing approach.
242)  NoScript is exceedingly complicated, and has many subtleties that can surprise
243)  even advanced users. For example, addons.mozilla.org verifies extension
244)  integrity via Javascript over https, but downloads them in the clear. Not 
245)  adding it to your whitelist effectively
246)  means you are pulling down unverified extensions. Worse still, using NoScript
247)  can actually disable protections that Torbutton itself provides via
248)  Javascript, yet still allow malicious exit nodes to compromise your
249)  anonymity via the default whitelist (which they can spoof to inject any script  they want). 
250) </ol>
251) </p>
252) 
253) <strong>Which Firefox extensions do you recommend?</strong>
254) <p>
255) <ol>
256)  <li><a href="https://addons.mozilla.org/firefox/addon/953">RefControl</a></li>
257)  Mentioned above, this extension allows more fine-grained referrer spoofing
258) than Torbutton currently provides. It should break less sites than Torbutton's
259) referrer spoofing option.
260)  <li><a href="https://addons.mozilla.org/firefox/addon/1474">SafeCache</a></li>
261)  If you use Tor excessively, and rarely disable it, you probably want to
262) install this extension to minimize the ability of sites to store long term
263) identifiers in your cache. This extension applies same origin policy to the
264) cache, so that elements are retrieved from the cache only if they are fetched
265) from a document in the same origin domain as the cached element. 
266) </ol>
267) 
268) </p>
269) 
270) <strong>Are there any other issues I should be concerned about?</strong>
271) <p>
272) 
273) There is currently one known unfixed security issue with Torbutton: it is
274) possible to unmask the javascript hooks that wrap the Date object to conceal
275) your timezone in Firefox 2, and the timezone masking code does not work at all
276) on Firefox 3. We are working with the Firefox team to fix one of <a
277) href="https://bugzilla.mozilla.org/show_bug.cgi?id=392274">Bug 399274</a> or
278) <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=419598">Bug 419598</a>
279) to address this. In the meantime, it is possible to set the <b>TZ</b>
280) environment variable to <b>UTC</b> to cause the browser to use UTC as your
281) timezone. Under Linux, you can add an <b>export TZ=UTC</b> to the
282) /usr/bin/firefox script, or edit your system bashrc to do the same. Under
283) Windows, you can set either a <a
284) href="http://support.microsoft.com/kb/310519">User or System Environment
285) Variable</a> for TZ via My Computer's properties. In MacOS, the situation is
286) <a
287) href="http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html#//apple_ref/doc/uid/20002093-BCIJIJBH">a
288) lot more complicated</a>, unfortunately.
289) 
290) </p>
291) 
292) <p>
293) 
294) In addition, RSS readers such as Firefox Livemarks can perform
295) periodic fetches. Due to <a
296) href="https://bugzilla.mozilla.org/show_bug.cgi?id=436250">Firefox Bug
297) 436250</a>, there is no way to disable Livemark fetches during Tor. This can
298) be a problem if you have a lot of custom Livemark urls that can give away
299) information about your identity.
300) 
301) </p>
302) 

303) <h2>Description des Options</h2>