Mfr commited on 2008-07-31 09:09:46
Zeige 4 geänderte Dateien mit 30 Einfügungen und 444 Löschungen.
... | ... |
@@ -1,5 +1,5 @@ |
1 | 1 |
## translation metadata |
2 |
-# Based-On-Revision: 15123 |
|
2 |
+# Based-On-Revision: 16280 |
|
3 | 3 |
# Last-Translator: mfr(ät]misericordia.be, fredzupy@gmail.com |
4 | 4 |
|
5 | 5 |
|
... | ... |
@@ -231,7 +231,7 @@ Parcourez le <b>dépôt SVN</b> : (il n'est pas garanti qu'il fonctionne ni mê |
231 | 231 |
<li><a href="<svnsandbox>">Bac à sable SVN (sandbox) régulièrement mis à jour</a></li> |
232 | 232 |
<li><a href="https://svn.torproject.org/svn/tor/trunk">Parcourir le répertoire du dépôt SVN directement</a></li> |
233 | 233 |
<li><a href="http://cvs.seul.org/viewcvs/viewcvs.cgi/?root=Tor">Voir le CVS</a></li> |
234 |
- <li>accès anonyme à <a href="http://subversion.tigris.org/">subversion :</a> |
|
234 |
+ <li><a href="http://subversion.tigris.org/">Subversion :</a> |
|
235 | 235 |
<ul> |
236 | 236 |
<li>Créez un répertoire vide et placez-vous dans ce répertoire.</li> |
237 | 237 |
<li><kbd>svn checkout https://tor-svn.freehaven.net/svn/tor/trunk tor</kbd></li> |
... | ... |
@@ -1,5 +1,5 @@ |
1 | 1 |
## translation metadata |
2 |
-# Based-On-Revision: 15961 |
|
2 |
+# Based-On-Revision: 16278 |
|
3 | 3 |
# Last-Translator: mfr(ä]misericordia.be, eightone_18 @yahoo.co.uk |
4 | 4 |
|
5 | 5 |
#include "head.wmi" CHARSET="UTF-8" TITLE="Tor : Télécharger pour Linux/Unix" |
... | ... |
@@ -49,8 +49,7 @@ href="<package-rpm4-stable-sig>">sig</a>) |
49 | 49 |
</td> |
50 | 50 |
<td> |
51 | 51 |
<a href="<package-rpm4-alpha>"><version-rpm4-alpha> RPM</a> (<a |
52 |
-href="<package-rpm4-alpha-sig>">sig</a>)<br /> |
|
53 |
-<a href="<package-rpm4-021>"><version-rpm4-021> RPM</a> (<a href="<package-rpm4-021-sig>">sig</a>) |
|
52 |
+href="<package-rpm4-alpha-sig>">sig</a>) |
|
54 | 53 |
</td> |
55 | 54 |
<td> |
56 | 55 |
<a href="<page docs/tor-doc-unix>">instructions Linux/BSD/Unix</a> |
... | ... |
@@ -65,8 +64,7 @@ href="<package-srpm4-stable-sig>">sig</a>) |
65 | 64 |
</td> |
66 | 65 |
<td> |
67 | 66 |
<a href="<package-srpm4-alpha>"><version-rpm4-alpha> SRPM</a> (<a |
68 |
-href="<package-srpm4-alpha-sig>">sig</a>)<br /> |
|
69 |
- <a href="<package-srpm4-021>"><version-rpm4-021> SRPM</a> (<a href="<package-srpm4-021-sig>">sig</a>) |
|
67 |
+href="<package-srpm4-alpha-sig>">sig</a>) |
|
70 | 68 |
</td> |
71 | 69 |
<td> |
72 | 70 |
<a href="<page docs/tor-doc-unix>">Linux/BSD/Unix instructions</a> |
... | ... |
@@ -80,8 +78,7 @@ href="<package-rpm5-stable-sig>">sig</a>) |
80 | 78 |
</td> |
81 | 79 |
<td> |
82 | 80 |
<a href="<package-rpm5-alpha>"><version-rpm5-alpha> RPM</a> (<a |
83 |
-href="<package-rpm5-alpha-sig>">sig</a>)<br /> |
|
84 |
- <a href="<package-rpm5-021>"><version-rpm5-021> RPM</a> (<a href="<package-rpm5-021-sig>">sig</a>) |
|
81 |
+href="<package-rpm5-alpha-sig>">sig</a>) |
|
85 | 82 |
</td> |
86 | 83 |
<td> |
87 | 84 |
<a href="<page docs/tor-doc-unix>">Instructions Linux/BSD/Unix</a> |
... | ... |
@@ -97,8 +94,7 @@ href="<package-srpm5-stable-sig>">sig</a>) |
97 | 94 |
<td> |
98 | 95 |
|
99 | 96 |
<a href="<package-srpm5-alpha>"><version-rpm5-alpha> SRPM</a> (<a |
100 |
-href="<package-srpm5-alpha-sig>">sig</a>)<br /> |
|
101 |
- <a href="<package-srpm5-021>"><version-rpm5-021> SRPM</a> (<a href="<package-srpm5-021-sig>">sig</a>) |
|
97 |
+href="<package-srpm5-alpha-sig>">sig</a>) |
|
102 | 98 |
</td> |
103 | 99 |
<td> |
104 | 100 |
<a href="<page docs/tor-doc-unix>">Instructions Linux/BSD/Unix</a> |
... | ... |
@@ -112,8 +108,7 @@ href="<package-srpm5-alpha-sig>">sig</a>)<br /> |
112 | 108 |
</td> |
113 | 109 |
<td> |
114 | 110 |
<a href="<package-rpmfc-alpha>"><version-rpmfc-alpha> RPM</a> (<a |
115 |
-href="<package-rpmfc-alpha-sig>">sig</a>)<br /> |
|
116 |
- <a href="<package-rpmfc-021>"><version-rpmfc-021> RPM</a> (<a href="<package-rpmfc-021-sig>">sig</a>) |
|
111 |
+href="<package-rpmfc-alpha-sig>">sig</a>) |
|
117 | 112 |
</td> |
118 | 113 |
<td> |
119 | 114 |
<a href="<page docs/tor-doc-unix>">Instructions Linux/BSD/Unix</a> |
... | ... |
@@ -127,8 +122,7 @@ href="<package-rpmfc-alpha-sig>">sig</a>)<br /> |
127 | 122 |
</td> |
128 | 123 |
<td> |
129 | 124 |
<a href="<package-srpmfc-alpha>"><version-rpmfc-alpha> SRPM</a> (<a |
130 |
-href="<package-srpmfc-alpha-sig>">sig</a>)<br /> |
|
131 |
- <a href="<package-srpmfc-021>"><version-rpmfc-021> SRPM</a> (<a href="<package-srpmfc-021-sig>">sig</a>) |
|
125 |
+href="<package-srpmfc-alpha-sig>">sig</a>) |
|
132 | 126 |
</td> |
133 | 127 |
<td> |
134 | 128 |
<a href="<page docs/tor-doc-unix>">Instructions Linux/BSD/Unix</a> |
... | ... |
@@ -143,8 +137,7 @@ href="<package-rpmsuse-stable-sig>">sig</a>) |
143 | 137 |
</td> |
144 | 138 |
<td> |
145 | 139 |
<a href="<package-rpmsuse-alpha>"><version-rpmsuse-alpha> RPM</a> (<a |
146 |
-href="<package-rpmsuse-alpha-sig>">sig</a>)<br /> |
|
147 |
- <a href="<package-rpmsuse-021>"><version-rpmsuse-021> RPM</a> (<a href="<package-rpmsuse-021-sig>">sig</a>) |
|
140 |
+href="<package-rpmsuse-alpha-sig>">sig</a>) |
|
148 | 141 |
</td> |
149 | 142 |
<td> |
150 | 143 |
<a href="<page docs/tor-doc-unix>">instructions Linux/BSD/Unix</a> |
... | ... |
@@ -159,8 +152,7 @@ href="<package-srpmsuse-stable-sig>">sig</a>) |
159 | 152 |
</td> |
160 | 153 |
<td> |
161 | 154 |
<a href="<package-srpmsuse-alpha>"><version-rpmsuse-alpha> SRPM</a> (<a |
162 |
- href="<package-srpmsuse-alpha-sig>">sig</a>)<br /> |
|
163 |
- <a href="<package-srpmsuse-021>"><version-rpmsuse-021> SRPM</a> (<a href="<package-srpmsuse-021-sig>">sig</a>) |
|
155 |
+ href="<package-srpmsuse-alpha-sig>">sig</a>) |
|
164 | 156 |
</td> |
165 | 157 |
<td> |
166 | 158 |
<a href="<page docs/tor-doc-unix>">instructions Linux/BSD/Unix</a> |
... | ... |
@@ -1,5 +1,5 @@ |
1 | 1 |
## translation metadata |
2 |
-# Based-On-Revision: 15961 |
|
2 |
+# Based-On-Revision: 16278 |
|
3 | 3 |
# Last-Translator: mfr(ät] misericordia.be, fredzupy@gmail.com |
4 | 4 |
|
5 | 5 |
#include "head.wmi" CHARSET="UTF-8" TITLE="Tor : Télécharger" |
... | ... |
@@ -30,8 +30,7 @@ Windows<br/> |
30 | 30 |
href="<package-win32-bundle-stable-sig>">sig</a>) |
31 | 31 |
</td> |
32 | 32 |
<td> |
33 |
- <a href="<package-win32-bundle-alpha>"><version-win32-bundle-alpha></a> (<a href="<package-win32-bundle-alpha-sig>">sig</a> ) <br /> |
|
34 |
- <a href="<package-win32-bundle-021>"><version-win32-bundle-021></a> (<a href="<package-win32-bundle-021-sig>">sig</a>) |
|
33 |
+ <a href="<package-win32-bundle-alpha>"><version-win32-bundle-alpha></a> (<a href="<package-win32-bundle-alpha-sig>">sig</a> ) |
|
35 | 34 |
</td> |
36 | 35 |
<td> |
37 | 36 |
<a href="<page docs/tor-doc-windows>">Installation & guide de configuration</a> |
... | ... |
@@ -47,8 +46,7 @@ Mac<br /> |
47 | 46 |
</td> |
48 | 47 |
<td> |
49 | 48 |
<a href="<package-osx-bundle-alpha>"><version-osx-bundle-alpha></a> (<a |
50 |
-href="<package-osx-bundle-alpha-sig>">sig</a>)<br /> |
|
51 |
- <a href="<package-osx-bundle-021>"><version-osx-bundle-021></a> (<a href="<package-osx-bundle-021-sig>">sig</a>) |
|
49 |
+href="<package-osx-bundle-alpha-sig>">sig</a>) |
|
52 | 50 |
</td> |
53 | 51 |
<td> |
54 | 52 |
<a href="<page docs/tor-doc-osx>">Installation & guide de configuration</a> |
... | ... |
@@ -63,8 +61,7 @@ Mac<br /> |
63 | 61 |
<a href="<package-oldosx-bundle-stable>"><version-oldosx-bundle-stable></a> (<a href="<package-oldosx-bundle-stable-sig>">sig</a>) |
64 | 62 |
</td> |
65 | 63 |
<td> |
66 |
- <a href="<package-oldosx-alpha>"><version-oldosx-alpha></a> (<a href="<package-oldosx-alpha-sig>">sig</a>)<br /> |
|
67 |
- <a href="<package-oldosx-bundle-021>"><version-oldosx-bundle-021></a> (<a href="<package-oldosx-bundle-021-sig>">sig</a>) |
|
64 |
+ <a href="<package-oldosx-alpha>"><version-oldosx-alpha></a> (<a href="<package-oldosx-alpha-sig>">sig</a>) |
|
68 | 65 |
</td> |
69 | 66 |
<td> |
70 | 67 |
<a href="<page docs/tor-doc-osx>">Installation & guide de configuration</a> |
... | ... |
@@ -242,8 +239,7 @@ href="<package-win32-stable-sig>">sig</a>) |
242 | 239 |
</td> |
243 | 240 |
<td> |
244 | 241 |
<a href="<package-win32-alpha>"><version-win32-alpha></a> (<a |
245 |
-href="<package-win32-alpha-sig>">sig</a>) <br /> |
|
246 |
-<a href="<package-win32-021>"><version-win32-021></a> (<a href="<package-win32-021-sig>">sig</a>) |
|
242 |
+href="<package-win32-alpha-sig>">sig</a>) |
|
247 | 243 |
</td> |
248 | 244 |
<td> |
249 | 245 |
<a href="<page docs/tor-doc-windows>">Installation & guide de configuration</a> |
... | ... |
@@ -261,8 +257,7 @@ href="<package-osx-stable-sig>">sig</a>) |
261 | 257 |
</td> |
262 | 258 |
<td> |
263 | 259 |
<a href="<package-osx-alpha>"><version-osx-alpha></a> (<a |
264 |
- href="<package-osx-alpha-sig>">sig</a>)<br /> |
|
265 |
- <a href="<package-osx-021>"><version-osx-021></a> (<a href="<package-osx-021-sig>">sig</a>) |
|
260 |
+ href="<package-osx-alpha-sig>">sig</a>) |
|
266 | 261 |
</td> |
267 | 262 |
<td> |
268 | 263 |
<a href="<page docs/tor-doc-osx>">Installation & guide de configuration</a> |
... | ... |
@@ -279,8 +274,7 @@ Mac (Contient Tor, Torbutton, et Privoxy)<br /> |
279 | 274 |
href="<package-oldosx-stable-sig>">sig</a>) |
280 | 275 |
</td> |
281 | 276 |
<td> |
282 |
-<a href="<package-oldosx-alpha>"><version-oldosx-alpha></a> (<a href="<package-oldosx-alpha-sig>">sig</a>)<br /> |
|
283 |
- <a href="<package-oldosx-021>"><version-oldosx-021></a> (<a href="<package-oldosx-021-sig>">sig</a>) |
|
277 |
+<a href="<package-oldosx-alpha>"><version-oldosx-alpha></a> (<a href="<package-oldosx-alpha-sig>">sig</a>) |
|
284 | 278 |
</td> |
285 | 279 |
<td> |
286 | 280 |
<a href="<page docs/tor-doc-osx>">Installation & guide de configuration</a> |
... | ... |
@@ -1,5 +1,5 @@ |
1 | 1 |
## translation metadata |
2 |
-# Based-On-Revision: 16239 |
|
2 |
+# Based-On-Revision: 16271 |
|
3 | 3 |
# Last-Translator: mfr(ät]misericordia.be |
4 | 4 |
|
5 | 5 |
#include "head.wmi" TITLE="Torbutton - Basculez rapidement sur le réseau Tor avec Firefox" CHARSET="UTF-8" |
... | ... |
@@ -81,12 +81,11 @@ function install (aEvent) |
81 | 81 |
</script> |
82 | 82 |
|
83 | 83 |
<h2>Torbutton</h2> |
84 |
-<hr> |
|
84 |
+<hr /> |
|
85 | 85 |
|
86 | 86 |
<strong>Version Actuelle:</strong><version-torbutton><br/> |
87 | 87 |
<br/> |
88 | 88 |
<strong>Auteurs:</strong> Scott Squires & Mike Perry<br/> |
89 |
-<strong>Courriel:</strong> squires at freehaven dot net, mikeperry (o) fscked/org<br/> |
|
90 | 89 |
<br/> |
91 | 90 |
<strong>Installation:</strong> |
92 | 91 |
<a href="http://www.torproject.org/torbutton/torbutton-current.xpi" |
... | ... |
@@ -104,14 +103,12 @@ Complément de recherche Google pour |
104 | 103 |
<a href="/jsreq.html" title="Ref: 14938 (googleCA)" |
105 | 104 |
onClick="addOpenSearch('googleuk_web','png','General','14445','g');return false">Google UK</a>. |
106 | 105 |
<br/> |
107 |
-<!-- |
|
108 |
-<strong>Install:</strong> <a href="torbutton-1.0.4.xpi">torbutton-1.0.4.xpi</a><br/> |
|
109 |
---> |
|
110 | 106 |
<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 | 107 |
<br/> |
112 | 108 |
<strong>Rapports de Bogues:</strong> <a href="https://bugs.torproject.org/flyspray/index.php?tasks=all&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> |
|
109 |
+<strong>Documents:</strong> <b>[</b> <a href="<page torbutton/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/> |
|
110 |
+ |
|
111 |
+<br/> |
|
115 | 112 |
<p> |
116 | 113 |
Torbutton est un moyen en 1-click pour les utilisateurs de Firefox d'activer |
117 | 114 |
ou de désactiver l'utilisation de <a href="<page index>">Tor</a> dans le |
... | ... |
@@ -122,7 +119,13 @@ Torbutton est un moyen en 1-click pour les utilisateurs de Firefox d'activer |
122 | 119 |
compte dans la barre d'état. |
123 | 120 |
</p> |
124 | 121 |
<p> |
125 |
-Certains utilisateurs peuvent préfèrer un bouton dans la barre d'outils au |
|
122 |
+Afin de préserver votre sécurité, Torbutton désactive différents types de contenu dynamique. Vous |
|
123 |
+pouvez en apprendre plus dans la <a href="<page torbutton/faq>">FAQ Torbutton</a>, |
|
124 |
+ou consultez la liste détaillée des <a href="<page torbutton/options>">options Torbutton |
|
125 |
+</a>. |
|
126 |
+</p> |
|
127 |
+<p> |
|
128 |
+Certains utilisateurs préfèrent avoir un bouton dans la barre d'outils au |
|
126 | 129 |
lieu d'un panneau d'état. Ce bouton est inclus, et l'on ajoute à la barre |
127 | 130 |
d'outils en cliquant avec le bouton droit sur la barre d'outils souhaitée, |
128 | 131 |
en sélectionnant "Personnaliser ...", puis en faisant glisser l'icône |
... | ... |
@@ -130,410 +133,7 @@ lieu d'un panneau d'état. Ce bouton est inclus, et l'on ajoute à la barre |
130 | 133 |
pour cacher le panneau d'état (Outils-> Modules complémentaires, |
131 | 134 |
sélectionnez Torbutton, et cliquez sur Préférences). |
132 | 135 |
</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 |
- |
|
141 |
-<p> |
|
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 |
-</p> |
|
156 |
- |
|
157 |
-<strong>My browser is in some weird state where nothing works right!</strong> |
|
158 |
- |
|
159 |
-<p> |
|
160 |
-Try to disable Tor by clicking on the button, and then open a new window. If |
|
161 |
-that doesn't fix the issue, go to the preferences page and hit 'Restore |
|
162 |
-Defaults'. This should reset the extension and Firefox to a known good |
|
163 |
-configuration. If you can manage to reproduce whatever issue gets your |
|
164 |
-Firefox wedged, please file details at <a |
|
165 |
-href="https://bugs.torproject.org/flyspray/index.php?tasks=all&project=5">the |
|
166 |
-bug tracker</a>. |
|
167 |
-</p> |
|
168 |
- |
|
169 |
-<strong>When I toggle Tor, my sites that use javascript stop working. Why?</strong> |
|
170 |
- |
|
171 |
-<p> |
|
172 |
-Javascript can do things like wait until you have disabled Tor before trying |
|
173 |
-to contact its source site, thus revealing your IP address. As such, Torbutton |
|
174 |
-must disable Javascript, Meta-Refresh tags, and certain CSS behavior when Tor |
|
175 |
-state changes from the state that was used to load a given page. These features |
|
176 |
-are re-enabled when Torbutton goes back into the state that was used to load |
|
177 |
-the page, but in some cases (particularly with Javascript and CSS) it is |
|
178 |
-sometimes not possible to fully recover from the resulting errors, and the |
|
179 |
-page is broken. Unfortunately, the only thing you can do (and still remain |
|
180 |
-safe from having your IP address leak) is to reload the page when you toggle |
|
181 |
-Tor, or just ensure you do all your work in a page before switching tor state. |
|
182 |
-</p> |
|
183 |
- |
|
184 |
- |
|
185 |
-<strong>When I use Tor, Firefox is no longer filling in logins/search boxes |
|
186 |
-for me. Why?</strong> |
|
187 |
- |
|
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 |
- |
|
200 |
-<p> |
|
201 |
-This is a tough one. There are thousands of Firefox extensions: making a |
|
202 |
-complete list of ones that are bad for anonymity is near impossible. However, |
|
203 |
-here are a few examples that should get you started as to what sorts of |
|
204 |
-behavior are dangerous. |
|
205 |
-</p> |
|
206 |
- |
|
207 |
-<ol> |
|
208 |
- <li>StumbleUpon, et al</li> |
|
209 |
- These extensions will send all sorts of information about the websites you |
|
210 |
- visit to the stumbleupon servers, and correlate this information with a |
|
211 |
- unique identifier. This is obviously terrible for your anonymity. |
|
212 |
- More generally, any sort of extension that requires registration, or even |
|
213 |
- extensions that provide information about websites you visit should be |
|
214 |
- suspect. |
|
215 |
- |
|
216 |
- <li>FoxyProxy</li> |
|
217 |
- |
|
218 |
-While FoxyProxy is a nice idea in theory, in practice it is impossible to |
|
219 |
-configure securely for Tor usage without Torbutton. Like all vanilla third |
|
220 |
-party proxy plugins, the main risks are <a |
|
221 |
-href="http://www.metasploit.com/research/projects/decloak/">plugin leakage</a> |
|
222 |
-and <a href="http://ha.ckers.org/weird/CSS-history.cgi">history |
|
223 |
-disclosure</a>, followed closely by cookie theft by exit nodes and tracking by |
|
224 |
-adservers (see the <a href="design/index.html#adversary">Torbutton Adversary |
|
225 |
-Model</a> for more information). However, even with Torbutton installed in |
|
226 |
-tandem and always enabled, it is still very difficult (though not impossible) |
|
227 |
-to configure FoxyProxy securely. Since FoxyProxy's 'Patterns' mode only |
|
228 |
-applies to specific urls, and not to an entire tab, setting FoxyProxy to only |
|
229 |
-send specific sites through Tor will still allow adservers to still learn your |
|
230 |
-real IP. Worse, if those sites use offsite logging services such as Google |
|
231 |
-Analytics, you may still end up in their logs with your real IP. Malicious |
|
232 |
-exit nodes can also cooperate with sites to inject images into pages that |
|
233 |
-bypass your filters. Setting FoxyProxy to only send certain URLs via Non-Tor |
|
234 |
-is much more viable, but be very careful with the filters you allow. For |
|
235 |
-example, something as simple as allowing *google* to go via Non-Tor will still |
|
236 |
-cause you to end up in all the logs of all websites that use Google Analytics! |
|
237 |
-See <a href="http://foxyproxy.mozdev.org/faq.html#privacy-01">this |
|
238 |
-question</a> on the FoxyProxy FAQ for more information. |
|
239 |
- |
|
240 |
- <li>NoScript</li> |
|
241 |
- Torbutton currently mitigates all known anonymity issues with Javascript. |
|
242 |
- While it may be tempting to get better security by disabling Javascript for |
|
243 |
- certain sites, you are far better off with an all-or-nothing approach. |
|
244 |
- NoScript is exceedingly complicated, and has many subtleties that can surprise |
|
245 |
- even advanced users. For example, addons.mozilla.org verifies extension |
|
246 |
- integrity via Javascript over https, but downloads them in the clear. Not |
|
247 |
- adding it to your whitelist effectively |
|
248 |
- means you are pulling down unverified extensions. Worse still, using NoScript |
|
249 |
- can actually disable protections that Torbutton itself provides via |
|
250 |
- Javascript, yet still allow malicious exit nodes to compromise your |
|
251 |
- anonymity via the default whitelist (which they can spoof to inject any script they want). |
|
252 |
-</ol> |
|
253 |
- |
|
254 |
- |
|
255 |
-<strong>Which Firefox extensions do you recommend?</strong> |
|
256 |
-<p> |
|
257 |
-<ol> |
|
258 |
- <li><a href="https://addons.mozilla.org/firefox/addon/953">RefControl</a></li> |
|
259 |
- Mentioned above, this extension allows more fine-grained referrer spoofing |
|
260 |
-than Torbutton currently provides. It should break less sites than Torbutton's |
|
261 |
-referrer spoofing option. |
|
262 |
- <li><a href="https://addons.mozilla.org/firefox/addon/1474">SafeCache</a></li> |
|
263 |
- If you use Tor excessively, and rarely disable it, you probably want to |
|
264 |
-install this extension to minimize the ability of sites to store long term |
|
265 |
-identifiers in your cache. This extension applies same origin policy to the |
|
266 |
-cache, so that elements are retrieved from the cache only if they are fetched |
|
267 |
-from a document in the same origin domain as the cached element. |
|
268 |
-</ol> |
|
269 |
-</p> |
|
270 |
- |
|
271 |
-<strong>Are there any other issues I should be concerned about?</strong> |
|
272 |
-<p> |
|
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 |
-</p> |
|
290 |
- |
|
291 |
-<p> |
|
292 |
-In addition, RSS readers such as Firefox Livemarks can perform |
|
293 |
-periodic fetches. Due to <a |
|
294 |
-href="https://bugzilla.mozilla.org/show_bug.cgi?id=436250">Firefox Bug |
|
295 |
-436250</a>, there is no way to disable Livemark fetches during Tor. This can |
|
296 |
-be a problem if you have a lot of custom Livemark urls that can give away |
|
297 |
-information about your identity. |
|
298 |
-</p> |
|
299 |
- |
|
300 |
-<h2>Description des Options</h2> |
|
301 |
- |
|
302 |
-<p>The development branch of Torbutton adds several new security features to |
|
303 |
-protect your anonymity from all the major threats the author is aware of. The |
|
304 |
-defaults should be fine for most people, but in case you are the tweaker type, |
|
305 |
-or if you prefer to try to outsource some options to more flexible extensions, |
|
306 |
-here is the complete list. (In an ideal world, these descriptions should all be |
|
307 |
-tooltips in the extension itself, but Firefox bugs <a |
|
308 |
-href="https://bugzilla.mozilla.org/show_bug.cgi?id=45375">45375</a> and <a |
|
309 |
-href="https://bugzilla.mozilla.org/show_bug.cgi?id=218223">218223</a> currently |
|
310 |
-prevent this).</p> |
|
311 |
- |
|
312 |
-<ul> |
|
313 |
- <li>Disable plugins on Tor Usage (crucial)</li> |
|
314 |
- |
|
315 |
- This option is key to Tor security. Plugins perform their own networking |
|
316 |
-independent of the browser, and many plugins only partially obey even their own |
|
317 |
-proxy settings. |
|
318 |
- |
|
319 |
- <li>Isolate Dynamic Content to Tor State (crucial)</li> |
|
320 |
- |
|
321 |
- Another crucial option, this setting causes the plugin to disable Javascript |
|
322 |
- on tabs that are loaded during a Tor state different than the current one, |
|
323 |
- to prevent delayed fetches of injected URLs that contain unique identifiers, |
|
324 |
- and to prevent meta-refresh tags from revealing your IP when you turn off |
|
325 |
- Tor. It also prevents all fetches from tabs loaded with an opposite Tor |
|
326 |
- state. This serves to block non-Javascript dynamic content such as CSS |
|
327 |
- popups from revealing your IP address if you disable Tor. |
|
328 |
- |
|
329 |
- <li>Hook Dangerous Javascript (crucial)</li> |
|
330 |
- |
|
331 |
-This setting enables the Javascript hooking code. Javascript is injected into |
|
332 |
-pages to hook the Date object to mask your timezone, and to hook the navigator |
|
333 |
-object to mask OS and user agent properties not handled by the standard |
|
334 |
-Firefox user agent override settings. |
|
335 |
- |
|
336 |
- <li>Resize window dimensions to multiples of 50px on toggle (recommended)</li> |
|
337 |
- |
|
338 |
-To cut down on the amount of state available to fingerprint users uniquely, |
|
339 |
-this pref causes windows to be resized to a multiple of 50 pixels on each |
|
340 |
-side when Tor is enabled and pages are loaded. |
|
341 |
- |
|
342 |
- <li>Disable Updates During Tor (recommended)</li> |
|
343 |
- |
|
344 |
-Under Firefox 2, many extension authors did not update their extensions from |
|
345 |
-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 |
|
346 |
-existing extensions. Since Firefox 3 now enforces encrypted and/or |
|
347 |
-authenticated updates, this setting is no longer as important as it once |
|
348 |
-was (though updates do leak information about which extensions you have, it is |
|
349 |
-fairly infrequent). |
|
350 |
- |
|
351 |
- <li>Disable Search Suggestions during Tor (optional)</li> |
|
352 |
- |
|
353 |
-This optional setting governs if you get Google search suggestions during Tor |
|
354 |
-usage. Since no cookie is transmitted during search suggestions, this is a |
|
355 |
-relatively benign behavior. |
|
356 |
- |
|
357 |
- <li>Block Tor/Non-Tor access to network from file:// urls (recommended)</li> |
|
358 |
- |
|
359 |
-These settings prevent local html documents from transmitting local files to |
|
360 |
-arbitrary websites <a href="http://www.gnucitizen.org/blog/content-disposition-hacking/">under Firefox 2</a>. Since exit nodes can insert headers that |
|
361 |
-force the browser to save arbitrary pages locally (and also inject script into |
|
362 |
-arbitrary html files you save to disk via Tor), it is probably a good idea to |
|
363 |
-leave this setting on. |
|
364 |
- |
|
365 |
- <li>Close all Non-Tor/Tor windows and tabs on toggle (optional)</li> |
|
366 |
- |
|
367 |
-These two settings allow you to obtain a greater degree of assurance that |
|
368 |
-after you toggle out of Tor, the pages are really gone and can't perform any |
|
369 |
-extra network activity. Currently, there is no known way that pages can still |
|
370 |
-perform activity after toggle, but these options exist as a backup measure |
|
371 |
-just in case a flaw is discovered. They can also serve as a handy 'Boss |
|
372 |
-Button' feature for clearing all Tor browsing off your screen in a hurry. |
|
373 |
- |
|
374 |
- <li>Isolate access to history navigation to Tor state (crucial)</li> |
|
375 |
- |
|
376 |
-This setting prevents both Javascript and accidental user clicks from causing |
|
377 |
-the session history to load pages that were fetched in a different Tor state |
|
378 |
-than the current one. Since this can be used to correlate Tor and Non-Tor |
|
379 |
-activity and thus determine your IP address, it is marked as a crucial |
|
380 |
-setting. |
|
381 |
- |
|
382 |
- <li>Block History Reads during Tor (crucial)</li> |
|
383 |
- |
|
384 |
- Based on code contributed by <a href="http://www.collinjackson.com/">Collin |
|
385 |
- Jackson</a>, when enabled and Tor is enabled, this setting prevents the |
|
386 |
-rendering engine from knowing if certain links were visited. This mechanism |
|
387 |
-defeats all document-based history disclosure attacks, including CSS-only |
|
388 |
-attacks. |
|
389 |
- |
|
390 |
- <li>Block History Reads during Non-Tor (recommended)</li> |
|
391 |
- |
|
392 |
- This setting accomplishes the same but for your Non-Tor activity. |
|
393 |
- |
|
394 |
- <li>Block History Writes during Tor (recommended)</li> |
|
395 |
- |
|
396 |
- This setting prevents the rendering engine from recording visited URLs, and |
|
397 |
-also disables download manager history. Note that if you allow writing of Tor history, |
|
398 |
-it is recommended that you disable non-Tor history reads, since malicious |
|
399 |
-websites you visit without Tor can query your history for .onion sites and |
|
400 |
-other history recorded during Tor usage (such as Google queries). |
|
401 |
- |
|
402 |
- <li>Block History Writes during Non-Tor (optional)</li> |
|
403 |
- |
|
404 |
-This setting also disables recording any history information during Non-Tor |
|
405 |
-usage. |
|
406 |
- |
|
407 |
-<li>Clear History During Tor Toggle (optional)</li> |
|
408 |
- |
|
409 |
- This is an alternate setting to use instead of (or in addition to) blocking |
|
410 |
-history reads or writes. |
|
411 |
- |
|
412 |
- <li>Block Password+Form saving during Tor/Non-Tor</li> |
|
413 |
- |
|
414 |
- These options govern if the browser writes your passwords and search |
|
415 |
- submissions to disk for the given state. |
|
416 |
- |
|
417 |
- <li>Block Tor disk cache and clear all cache on Tor Toggle</li> |
|
418 |
- |
|
419 |
- Since the browser cache can be leveraged to store unique identifiers, cache |
|
420 |
-must not persist across Tor sessions. This option keeps the memory cache active |
|
421 |
-during Tor usage for performance, but blocks disk access for caching. |
|
422 |
- |
|
423 |
- <li>Block disk and memory cache during Tor</li> |
|
424 |
- |
|
425 |
- This setting entirely blocks the cache during Tor, but preserves it for |
|
426 |
-Non-Tor usage. |
|
427 |
- |
|
428 |
- <li>Clear Cookies on Tor Toggle</li> |
|
429 |
- |
|
430 |
- Fully clears all cookies on Tor toggle. |
|
431 |
- |
|
432 |
- <li>Store Non-Tor cookies in a protected jar</li> |
|
433 |
- |
|
434 |
- This option stores your persistent Non-Tor cookies in a special cookie jar |
|
435 |
- file, in case you wish to preserve some cookies. Based on code contributed |
|
436 |
- by <a href="http://www.collinjackson.com/">Collin Jackson</a>. It is |
|
437 |
- compatible with third party extensions that you use to manage your Non-Tor |
|
438 |
- cookies. Your Tor cookies will be cleared on toggle, of course. |
|
439 |
- |
|
440 |
- <li>Store both Non-Tor and Tor cookies in a protected jar (dangerous)</li> |
|
441 |
- |
|
442 |
- This option stores your persistent Tor and Non-Tor cookies |
|
443 |
- separate cookie jar files. Note that it is a bad idea to keep Tor |
|
444 |
- cookies around for any length of time, as they can be retrieved by exit |
|
445 |
- nodes that inject spoofed forms into plaintext pages you fetch. |
|
446 |
- |
|
447 |
- <li>Manage My Own Cookies (dangerous)</li> |
|
448 |
- |
|
449 |
- This setting allows you to manage your own cookies with an alternate |
|
450 |
-extension, such as <a href="https://addons.mozilla.org/firefox/addon/82">CookieCuller</a>. Note that this is particularly dangerous, |
|
451 |
-since malicious exit nodes can spoof document elements that appear to be from |
|
452 |
-sites you have preserved cookies for (and can then do things like fetch your |
|
453 |
-entire gmail inbox, even if you were not using gmail or visiting any google |
|
454 |
-pages at the time!). |
|
455 |
- |
|
456 |
- <li>Do not write Tor/Non-Tor cookies to disk</li> |
|
457 |
- |
|
458 |
- These settings prevent Firefox from writing any cookies to disk during the |
|
459 |
- corresponding Tor state. If cookie jars are enabled, those jars will |
|
460 |
- exist in memory only, and will be cleared when Firefox exits. |
|
461 |
- |
|
462 |
- <li>Disable DOM Storage during Tor usage (crucial)</li> |
|
463 |
- |
|
464 |
- Firefox has recently added the ability to store additional state and |
|
465 |
- identifiers in persistent tables, called <a |
|
466 |
- href="http://developer.mozilla.org/docs/DOM:Storage">DOM Storage</a>. |
|
467 |
- Obviously this can compromise your anonymity if stored content can be |
|
468 |
- fetched across Tor-state. |
|
469 |
- |
|
470 |
- <li>Clear HTTP auth sessions (recommended)</li> |
|
471 |
- |
|
472 |
- 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. |
|
473 |
- |
|
474 |
- <li>Clear cookies on Tor/Non-Tor shutdown</li> |
|
475 |
- |
|
476 |
- These settings install a shutdown handler to clear cookies on Tor |
|
477 |
-and/or Non-Tor browser shutdown. It is independent of your Clear Private Data |
|
478 |
-settings, and does in fact clear the corresponding cookie jars. |
|
479 |
- |
|
480 |
- <li>Prevent session store from saving Tor-loaded tabs (recommended)</li> |
|
481 |
- |
|
482 |
- This option augments the session store to prevent it from writing out |
|
483 |
- Tor-loaded tabs to disk. Unfortunately, this also disables your ability to |
|
484 |
- undo closed tabs. The reason why this setting is recommended is because |
|
485 |
- after a session crash, your browser will be in an undefined Tor state, and |
|
486 |
- can potentially load a bunch of Tor tabs without Tor. The following option |
|
487 |
- is another alternative to protect against this. |
|
488 |
- |
|
489 |
- <li>On normal startup, set state to: Tor, Non-Tor, Shutdown State</li> |
|
490 |
- |
|
491 |
- This setting allows you to choose which Tor state you want the browser to |
|
492 |
- start in normally: Tor, Non-Tor, or whatever state the browser shut down in. |
|
493 |
- |
|
494 |
- <li>On crash recovery or session restored startup, restore via: Tor, Non-Tor</li> |
|
495 |
- |
|
496 |
- When Firefox crashes, the Tor state upon restart usually is completely |
|
497 |
- random, and depending on your choice for the above option, may load |
|
498 |
- a bunch of tabs in the wrong state. This setting allows you to choose |
|
499 |
- which state the crashed session should always be restored in to. |
|
500 |
- |
|
501 |
- <li>Prevent session store from saving Non-Tor/Tor-loaded tabs</li> |
|
502 |
- |
|
503 |
- These two settings allow you to control what the Firefox Session Store |
|
504 |
- writes to disk. Since the session store state is used to automatically |
|
505 |
- load websites after a crash or upgrade, it is advisable not to allow |
|
506 |
- Tor tabs to be written to disk, or they may get loaded in Non-Tor |
|
507 |
- after a crash (or the reverse, depending upon the crash recovery setting, |
|
508 |
- of course). |
|
509 |
- |
|
510 |
- <li>Set user agent during Tor usage (crucial)</li> |
|
511 |
- |
|
512 |
- User agent masking is done with the idea of making all Tor users appear |
|
513 |
-uniform. A recent Firefox 2.0.0.4 Windows build was chosen to mimic for this |
|
514 |
-string and supporting navigator.* properties, and this version will remain the |
|
515 |
-same for all TorButton versions until such time as specific incompatibility |
|
516 |
-issues are demonstrated. Uniformity of this value is obviously very important |
|
517 |
-to anonymity. Note that for this option to have full effectiveness, the user |
|
518 |
-must also allow Hook Dangerous Javascript ensure that the navigator.* |
|
519 |
-properties are reset correctly. The browser does not set some of them via the |
|
520 |
-exposed user agent override preferences. |
|
521 |
- |
|
522 |
- <li>Spoof US English Browser</li> |
|
523 |
- |
|
524 |
-This option causes Firefox to send http headers as if it were an English |
|
525 |
-browser. Useful for internationalized users. |
|
526 |
- |
|
527 |
- <li>Don't send referrer during Tor Usage</li> |
|
528 | 136 |
|
529 |
-This option disables the referrer header, preventing sites from determining |
|
530 |
-where you came from to visit them. This can break some sites, however. <a |
|
531 |
-href="http://www.digg.com">Digg</a> in particular seemed to be broken by this. |
|
532 |
-A more streamlined, less intrusive version of this option should be available |
|
533 |
-eventually. In the meantime, <a |
|
534 |
-href="https://addons.mozilla.org/firefox/addon/953">RefControl</a> can |
|
535 |
-provide this functionality via a default option of <b>Forge</b>. |
|
536 |
-</ul> |
|
537 | 137 |
|
538 | 138 |
</div><!-- #main --> |
539 | 139 |
|
540 | 140 |