Add a French page
Mfr authored 15 years ago
|
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>
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 & 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) -->
|
|
Add a French page
Mfr authored 15 years ago
|
117) </p><p>
118) Some users may prefer a toolbar button instead of a statusbar panel. Such a button is included, and one adds it to the toolbar by right-clicking on the desired toolbar, selecting "Customize...", and then dragging the Torbutton icon onto the toolbar. There is an option in the preferences to hide the statusbar panel (Tools->Extensions, select Torbutton, and click on Preferences).
119) </p>
120) <p>
121) Newer Firefoxes have the ability to send DNS resolves through the socks proxy, and Torbutton will make use of this feature if it is available in your version of Firefox.
122) </p>
123)
124) <a id="FAQ"></a><h2>FAQ</h2>
125)
126) <strong>I can't click on links or hit reload after I toggle Tor! Why?</strong>
127) <p>
128)
129) Due to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=409737">Firefox
130) Bug 409737</a>, pages can still open popups and perform Javascript redirects
131) and history access after Tor has been toggled. These popups and redirects can
132) be blocked, but unfortunately they are indistinguishable from normal user
133) interactions with the page (such as clicking on links, opening them in new
134) tabs/windows, or using the history buttons), and so those are blocked as a
135) side effect. Once that Firefox bug is fixed, this degree of isolation will
136) become optional (for people who do not want to accidentally click on links and
137) give away information via referrers). A workaround is to right click on the
138) link, and open it in a new tab or window. The tab or window won't load
139) automatically, but you can hit enter in the URL bar, and it will begin
140) loading. Hitting enter in the URL bar will also reload the page without
141) clicking the reload button.
142)
143) </p>
144)
145) <strong>My browser is in some weird state where nothing works right!</strong>
146) <p>
147)
148) Try to disable Tor by clicking on the button, and then open a new window. If
149) that doesn't fix the issue, go to the preferences page and hit 'Restore
150) Defaults'. This should reset the extension and Firefox to a known good
151) configuration. If you can manage to reproduce whatever issue gets your
152) Firefox wedged, please file details at <a
153) href="https://bugs.torproject.org/flyspray/index.php?tasks=all&project=5">the
154) bug tracker</a>.
155)
156) </p>
157)
158) <strong>When I toggle Tor, my sites that use javascript stop working. Why?</strong>
159) <p>
160) Javascript can do things like wait until you have disabled Tor before trying
161) to contact its source site, thus revealing your IP address. As such, Torbutton
162) must disable Javascript, Meta-Refresh tags, and certain CSS behavior when Tor
163) state changes from the state that was used to load a given page. These features
164) are re-enabled when Torbutton goes back into the state that was used to load
165) the page, but in some cases (particularly with Javascript and CSS) it is
166) sometimes not possible to fully recover from the resulting errors, and the
167) page is broken. Unfortunately, the only thing you can do (and still remain
168) safe from having your IP address leak) is to reload the page when you toggle
169) Tor, or just ensure you do all your work in a page before switching tor state.
170) </p>
171)
172)
173) <strong>When I use Tor, Firefox is no longer filling in logins/search boxes
174) for me. Why?</strong>
175) <p>
176) Currently, this is tied to the "<b>Block history writes during Tor</b>"
177) setting. If you have enabled that setting, all formfill functionality (both
178) saving and reading) is disabled. If this bothers you, you can uncheck that
179) option, but both history and forms will be saved. To prevent history
180) disclosure attacks via Non-Tor usage, it is recommended you disable Non-Tor
181) history reads if you allow history writing during Tor.
182) </p>
183)
184)
185) <strong>Which Firefox extensions should I avoid using?</strong>
186) <p>
187)
188) This is a tough one. There are thousands of Firefox extensions: making a
189) complete list of ones that are bad for anonymity is near impossible. However,
190) here are a few examples that should get you started as to what sorts of
191) behavior are dangerous.
192)
193) <ol>
194) <li>StumbleUpon, et al</li>
195) These extensions will send all sorts of information about the websites you
196) visit to the stumbleupon servers, and correlate this information with a
197) unique identifier. This is obviously terrible for your anonymity.
198) More generally, any sort of extension that requires registration, or even
199) extensions that provide information about websites you visit should be
200) suspect.
201)
202) <li>FoxyProxy</li>
203)
204) While FoxyProxy is a nice idea in theory, in practice it is impossible to
205) configure securely for Tor usage without Torbutton. Like all vanilla third
206) party proxy plugins, the main risks are <a
207) href="http://www.metasploit.com/research/projects/decloak/">plugin leakage</a>
208) and <a href="http://ha.ckers.org/weird/CSS-history.cgi">history
209) disclosure</a>, followed closely by cookie theft by exit nodes and tracking by
210) adservers (see the <a href="design/index.html#adversary">Torbutton Adversary
211) Model</a> for more information). However, even with Torbutton installed in
212) tandem and always enabled, it is still very difficult (though not impossible)
213) to configure FoxyProxy securely. Since FoxyProxy's 'Patterns' mode only
214) applies to specific urls, and not to an entire tab, setting FoxyProxy to only
215) send specific sites through Tor will still allow adservers to still learn your
216) real IP. Worse, if those sites use offsite logging services such as Google
217) Analytics, you may still end up in their logs with your real IP. Malicious
218) exit nodes can also cooperate with sites to inject images into pages that
219) bypass your filters. Setting FoxyProxy to only send certain URLs via Non-Tor
220) is much more viable, but be very careful with the filters you allow. For
221) example, something as simple as allowing *google* to go via Non-Tor will still
222) cause you to end up in all the logs of all websites that use Google Analytics!
223) See <a href="http://foxyproxy.mozdev.org/faq.html#privacy-01">this
224) question</a> on the FoxyProxy FAQ for more information.
225)
226) <li>NoScript</li>
227) Torbutton currently mitigates all known anonymity issues with Javascript.
228) While it may be tempting to get better security by disabling Javascript for
229) certain sites, you are far better off with an all-or-nothing approach.
230) NoScript is exceedingly complicated, and has many subtleties that can surprise
231) even advanced users. For example, addons.mozilla.org verifies extension
232) integrity via Javascript over https, but downloads them in the clear. Not
233) adding it to your whitelist effectively
234) means you are pulling down unverified extensions. Worse still, using NoScript
235) can actually disable protections that Torbutton itself provides via
236) Javascript, yet still allow malicious exit nodes to compromise your
237) anonymity via the default whitelist (which they can spoof to inject any script they want).
238)
239) </ol>
240)
241) </p>
242)
243) <strong>Which Firefox extensions do you recommend?</strong>
244) <p>
245) <ol>
246) <li><a href="https://addons.mozilla.org/firefox/addon/953">RefControl</a></li>
247) Mentioned above, this extension allows more fine-grained referrer spoofing
248) than Torbutton currently provides. It should break less sites than Torbutton's
249) referrer spoofing option.
250) <li><a href="https://addons.mozilla.org/firefox/addon/1474">SafeCache</a></li>
251) If you use Tor excessively, and rarely disable it, you probably want to
252) install this extension to minimize the ability of sites to store long term
253) identifiers in your cache. This extension applies same origin policy to the
254) cache, so that elements are retrieved from the cache only if they are fetched
255) from a document in the same origin domain as the cached element.
256) </ol>
257)
258) </p>
259)
260) <strong>Are there any other issues I should be concerned about?</strong>
261) <p>
262)
263) There is currently one known unfixed security issue with Torbutton: it is
264) possible to unmask the javascript hooks that wrap the Date object to conceal
265) your timezone in Firefox 2, and the timezone masking code does not work at all
266) on Firefox 3. We are working with the Firefox team to fix one of <a
267) href="https://bugzilla.mozilla.org/show_bug.cgi?id=392274">Bug 399274</a> or
268) <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=419598">Bug 419598</a>
269) to address this. In the meantime, it is possible to set the <b>TZ</b>
270) environment variable to <b>UTC</b> to cause the browser to use UTC as your
271) timezone. Under Linux, you can add an <b>export TZ=UTC</b> to the
272) /usr/bin/firefox script, or edit your system bashrc to do the same. Under
273) Windows, you can set either a <a
274) href="http://support.microsoft.com/kb/310519">User or System Environment
275) Variable</a> for TZ via My Computer's properties. In MacOS, the situation is
276) <a
277) href="http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html#//apple_ref/doc/uid/20002093-BCIJIJBH">a
278) lot more complicated</a>, unfortunately.
279)
280) </p>
281)
282) <p>
283)
284) In addition, RSS readers such as Firefox Livemarks can perform
285) periodic fetches. Due to <a
286) href="https://bugzilla.mozilla.org/show_bug.cgi?id=436250">Firefox Bug
287) 436250</a>, there is no way to disable Livemark fetches during Tor. This can
288) be a problem if you have a lot of custom Livemark urls that can give away
289) information about your identity.
290)
291) </p>
292)
|
Add a French page