tor-webwml.git

first cut of the new, shiny tor website as wml.
Andrew Lewman

Andrew Lewman commited on 2010-07-09 03:55:22
Zeige 489 geänderte Dateien mit 48432 Einfügungen und 0 Löschungen.

Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,59 @@
1 
+# Directions for building the website:
2 
+#
3 
+# FIXME: this is incorrect, because maint-0.2.1 and master merged
4 
+# 1. Clone the Tor git repository, switch to branch maint-0.2.1, and
5 
+# make TORSVNSTABLE point to it:
6 
+#
7 
+# 	git clone git://git.torproject.org/tor/ tor-stable
8 
+# 	cd tor-stable && git checkout maint-0.2.1
9 
+#
10 
+# 2. Clone the Tor git repository again and make TORGIT point to it:
11 
+#
12 
+# 	git clone git://git.torproject.org/tor/ tor
13 
+#
14 
+# 3. Edit include/versions.wmi or others if you like
15 
+# 4. Update STABLETAG and DEVTAG below if there is a new git tag
16 
+# 5. make
17 
+# 6. ./publish
18 
+
19 
+# FIXME: these are the same
20 
+#TORSVNSTABLE = tor/stable
21 
+TORSVNSTABLE = tor-stable
22 
+TORGIT = tor/.git
23 
+STABLETAG = tor-0.2.1.26
24 
+DEVTAG = tor-0.2.2.13-alpha
25 
+
26 
+WMLBASE = .
27 
+SUBDIRS =docs eff projects press about download download getinvolved donate
28 
+
29 
+include $(WMLBASE)/Makefile.common
30 
+all: $(SUBDIRS)
31 
+
32 
+docs:
33 
+	$(MAKE) -C "$@" WMLBASE=..
34 
+eff:
35 
+	$(MAKE) -C "$@" WMLBASE=..
36 
+projects:
37 
+	$(MAKE) -C "$@" WMLBASE=..
38 
+press:
39 
+	$(MAKE) -C "$@" WMLBASE=..
40 
+about:
41 
+	$(MAKE) -C "$@" WMLBASE=..
42 
+download:
43 
+	$(MAKE) -C "$@" WMLBASE=..
44 
+getinvolved:
45 
+	$(MAKE) -C "$@" WMLBASE=..
46 
+donate:
47 
+	$(MAKE) -C "$@" WMLBASE=..
48 
+mirrors:
49 
+	./update-mirrors.pl
50 
+translations:
51 
+	./po2wml.sh
52 
+qrcode:
53 
+	qrencode -o img/android/orbot-qr-code-latest.png \
54 
+    "http://www.torproject.org/dist/android/alpha-orbot-latest.apk"
55 
+
56 
+# XXX: this also depends on all subs' wmlfiles.  How to fix?
57 
+translation-status.html.en: $(LANGS) $(WMIFILES) $(WMLFILES)
58 
+
59 
+.PHONY: docs eff projects press about download download getinvolved donate
Makefile.common
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,244 @@
1 
+# Directions for adding a new language:
2 
+# 1. Add the two-letter code to LANGS below.
3 
+# 2. Add a new "%.html.es: es/%.wml en/%.wml" clause below.
4 
+# 3. Add a new ".deps/%.html.es.d: es/%.wml .deps/.stamp" clause below.
5 
+# 4. mkdir a new two-letter directory. Make sure there's a foot.wmi
6 
+#    and navigation.wmi.
7 
+# 5. Edit include/perl-globals.wmi, add to @LANGUAGES and %LANGUAGES.
8 
+#    You might find useful %LANGUAGES strings at the bottom of
9 
+#    http://debian.org/
10 
+# 6. Add a new images/es.png flag image.
11 
+
12 
+WMLOPT  = \
13 
+          -I $(WMLBASE)/include \
14 
+          -D DOCROOT=$(WMLBASE) \
15 
+          -D IMGROOT=$(WMLBASE)/images \
16 
+          -D TORSVNSTABLE=$(TORSVNSTABLE) \
17 
+          -D TORGIT=$(TORGIT)\
18 
+          -D DEVTAG=$(DEVTAG) \
19 
+          -D STABLETAG=$(STABLETAG)
20 
+
21 
+LANGS=ar bms de en es et fa it fi fr ja ko nl no pl pt ru se tr zh-cn
22 
+#LANGS=en
23 
+
24 
+WMLFILES=$(wildcard $(patsubst %, %/*.wml, $(LANGS)))
25 
+WMIFILES=$(wildcard $(patsubst %, %/*.wmi, $(LANGS)) $(WMLBASE)/include/*.wmi )
26 
+
27 
+HTMLFILES = $(shell perl -le 's,  (.*)/(.*).wml  ,        $$2.html.$$1    ,x, print $$_ for @ARGV' $(WMLFILES))
28 
+DEPFILES  = $(shell perl -le 's,  (.*)/(.*).wml  ,  .deps/$$2.html.$$1.d  ,x, print $$_ for @ARGV' $(WMLFILES))
29 
+
30 
+
31 
+all: $(HTMLFILES)
32 
+
33 
+%.html.en: en/%.wml
34 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
35 
+
36 
+%.html.ar: ar/%.wml en/%.wml
37 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
38 
+
39 
+%.html.bms: bms/%.wml en/%.wml
40 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
41 
+
42 
+%.html.es: es/%.wml en/%.wml
43 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
44 
+
45 
+%.html.et: et/%.wml en/%.wml
46 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
47 
+
48 
+%.html.de: de/%.wml en/%.wml
49 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
50 
+
51 
+%.html.fa: fa/%.wml en/%.wml
52 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
53 
+
54 
+%.html.it: it/%.wml en/%.wml
55 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
56 
+
57 
+%.html.fi: fi/%.wml en/%.wml
58 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
59 
+
60 
+%.html.fr: fr/%.wml en/%.wml
61 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
62 
+
63 
+%.html.ja: ja/%.wml en/%.wml
64 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
65 
+
66 
+%.html.ko: ko/%.wml en/%.wml
67 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
68 
+
69 
+%.html.nl: nl/%.wml en/%.wml
70 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
71 
+
72 
+%.html.no: no/%.wml en/%.wml
73 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
74 
+
75 
+%.html.pl: pl/%.wml en/%.wml
76 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
77 
+
78 
+%.html.pt: pt/%.wml en/%.wml
79 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
80 
+
81 
+%.html.ru: ru/%.wml en/%.wml
82 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
83 
+
84 
+%.html.se: se/%.wml en/%.wml
85 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
86 
+
87 
+%.html.tr: tr/%.wml en/%.wml
88 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
89 
+
90 
+%.html.zh-cn: zh-cn/%.wml en/%.wml
91 
+	lang=`dirname $<` && wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $@
92 
+
93 
+.deps/%.html.en.d: en/%.wml .deps/.stamp
94 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
95 
+	lang=`dirname $<` && \
96 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
97 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
98 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
99 
+	rm -f $$tmpfile
100 
+.deps/%.html.ar.d: es/%.wml .deps/.stamp
101 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
102 
+	lang=`dirname $<` && \
103 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
104 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
105 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
106 
+	rm -f $$tmpfile
107 
+.deps/%.html.bms.d: bms/%.wml .deps/.stamp
108 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
109 
+	lang=`dirname $<` && \
110 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
111 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
112 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
113 
+	rm -f $$tmpfile
114 
+.deps/%.html.es.d: es/%.wml .deps/.stamp
115 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
116 
+	lang=`dirname $<` && \
117 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
118 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
119 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
120 
+	rm -f $$tmpfile
121 
+.deps/%.html.et.d: et/%.wml .deps/.stamp
122 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
123 
+	lang=`dirname $<` && \
124 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
125 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
126 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
127 
+	rm -f $$tmpfile
128 
+.deps/%.html.de.d: de/%.wml .deps/.stamp
129 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
130 
+	lang=`dirname $<` && \
131 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
132 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
133 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
134 
+	rm -f $$tmpfile
135 
+.deps/%.html.it.d: it/%.wml .deps/.stamp
136 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
137 
+	lang=`dirname $<` && \
138 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
139 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
140 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
141 
+	rm -f $$tmpfile
142 
+.deps/%.html.fa.d: fa/%.wml .deps/.stamp
143 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
144 
+	lang=`dirname $<` && \
145 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
146 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
147 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
148 
+	rm -f $$tmpfile
149 
+.deps/%.html.fi.d: fi/%.wml .deps/.stamp
150 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
151 
+	lang=`dirname $<` && \
152 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
153 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
154 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
155 
+	rm -f $$tmpfile
156 
+.deps/%.html.fr.d: fr/%.wml .deps/.stamp
157 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
158 
+	lang=`dirname $<` && \
159 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
160 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
161 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
162 
+	rm -f $$tmpfile
163 
+.deps/%.html.ja.d: ja/%.wml .deps/.stamp
164 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
165 
+	lang=`dirname $<` && \
166 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
167 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
168 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
169 
+	rm -f $$tmpfile
170 
+.deps/%.html.ko.d: ko/%.wml .deps/.stamp
171 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
172 
+	lang=`dirname $<` && \
173 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
174 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
175 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
176 
+	rm -f $$tmpfile
177 
+.deps/%.html.nl.d: nl/%.wml .deps/.stamp
178 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
179 
+	lang=`dirname $<` && \
180 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
181 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
182 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
183 
+	rm -f $$tmpfile
184 
+.deps/%.html.no.d: no/%.wml .deps/.stamp
185 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
186 
+	lang=`dirname $<` && \
187 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
188 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
189 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
190 
+	rm -f $$tmpfile
191 
+.deps/%.html.pl.d: pl/%.wml .deps/.stamp
192 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
193 
+	lang=`dirname $<` && \
194 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
195 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
196 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
197 
+	rm -f $$tmpfile
198 
+.deps/%.html.pt.d: pt/%.wml .deps/.stamp
199 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
200 
+	lang=`dirname $<` && \
201 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
202 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
203 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
204 
+	rm -f $$tmpfile
205 
+.deps/%.html.ru.d: ru/%.wml .deps/.stamp
206 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
207 
+	lang=`dirname $<` && \
208 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
209 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
210 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
211 
+	rm -f $$tmpfile
212 
+.deps/%.html.se.d: se/%.wml .deps/.stamp
213 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
214 
+	lang=`dirname $<` && \
215 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
216 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
217 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
218 
+	rm -f $$tmpfile
219 
+.deps/%.html.tr.d: tr/%.wml .deps/.stamp
220 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
221 
+	lang=`dirname $<` && \
222 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
223 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
224 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
225 
+	rm -f $$tmpfile
226 
+.deps/%.html.zh-cn.d: zh-cn/%.wml .deps/.stamp
227 
+	tmpfile=`mktemp -t tmp.XXXXXXX` \
228 
+	lang=`dirname $<` && \
229 
+	OUT=`echo $@ | sed -e 's,\.deps/\(.*\)\.d$$,\1,'` && \
230 
+	wml $(WMLOPT) -I $$lang -I $(WMLBASE)/$$lang -D LANG=$$lang $< -o $$OUT --depend | tee $$tmpfile > $@ && \
231 
+	sed -e s',\(^[^ ]*\):,.deps/\1.d:,' < $$tmpfile >> $@ && \
232 
+	rm -f $$tmpfile
233 
+.deps/.stamp:
234 
+	[ -d .deps ] || mkdir .deps
235 
+	touch "$@"
236 
+
237 
+dep: $(DEPFILES)
238 
+clean:
239 
+	rm -f $(HTMLFILES) $(DEPFILES)
240 
+	for sub in $(SUBDIRS); do \
241 
+		$(MAKE) -C "$$sub" WMLBASE=../$(WMLBASE) clean; \
242 
+	done
243 
+
244 
+include $(DEPFILES)
about/._.DS_Store
Zeige Datei @ 2a9aaa802
about/.deps/.stamp
Zeige Datei @ 2a9aaa802
about/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1 @@
1 
+include $(WMLBASE)/Makefile.common
about/en/about.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,28 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Tor Overview" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About</a>
10 
+  </div>
11 
+  <div id="maincol">
12 
+    <h1>Tor Overview</h1>
13 
+    <p>Tor is a network of virtual tunnels that allows people and groups to improve their privacy and security on the Internet. It also enables software developers to create new communication tools with built-in privacy features. Tor provides the foundation for a range of applications that allow organizations and individuals to share information over public networks without compromising their privacy.</p>
14 
+    <p>Individuals use Tor to keep websites from tracking them and their family members, or to connect to news sites, instant messaging services, and the like when these are blocked by their local Internet providers. Tor's <a href="#">hidden services</a> let users publish web sites and other services without needing to reveal the location of the site. Individuals also use Tor for socially sensitive communication: chat rooms and web forums for rape and abuse survivors, or people with illnesses.</p>
15 
+    <p>Journalists use Tor to communicate more safely with whistleblowers and dissidents. Non-governmental organizations (NGOs) use Tor to allow their workers to connect to their home website while they're in a foreign country, without notifying everybody nearby that they're working with that organization.</p>
16 
+    <p>Groups such as Indymedia recommend Tor for safeguarding their members' online privacy and security. Activist groups like the <a href="http://www.eff.org/">Electronic Frontier Foundation</a> (EFF) recommend Tor as a mechanism for maintaining civil liberties online. Corporations use Tor as a safe way to conduct competitive analysis, and to protect sensitive procurement patterns from eavesdroppers. They also use it to replace traditional VPNs, which reveal the exact amount and timing of communication. Which locations have employees working late? Which locations have employees consulting job-hunting websites? Which research divisions are communicating with the company's patent lawyers?</p>
17 
+    <p>A branch of the U.S. Navy uses Tor for open source intelligence gathering, and one of its teams used Tor while deployed in the Middle East recently. Law enforcement uses Tor for visiting or surveilling web sites without leaving government IP addresses in their web logs, and for security during sting operations.</p>
18 
+    <p>The <a href="<page about/corepeople>">variety of people</a> who use Tor is actually part of <a href="<page about/overview>">what makes it so secure</a>. Tor hides you among the other users on the network, so the more populous and diverse the user base for Tor is, the more your anonymity will be protected.</p>
19 
+  </div>
20 
+  <!-- END MAINCOL -->
21 
+  <div id = "sidecol">
22 
+#include "side.wmi"
23 
+#include "info.wmi"
24 
+  </div>
25 
+  <!-- END SIDECOL -->
26 
+</div>
27 
+<!-- END CONTENT -->
28 
+#include <foot.wmi>
about/en/board.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,75 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Board of Directors" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/board>">Board of Directors</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+  	<h1>Board of Directors</h1>
14 
+    <table>
15 
+    	<tr>
16 
+        <td class="beige">
17 
+          <div class="name">Board Member Name</div>
18 
+          <div class="caps">Board Member Title</div>
19 
+          <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
20 
+        </td>
21 
+        <td>
22 
+          <div class="name">Board Member Name</div>
23 
+          <div class="caps">Board Member Title</div>
24 
+          <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
25 
+        </td>
26 
+      </tr>
27 
+      <tr>
28 
+        <td>
29 
+          <div class="name">Board Member Name</div>
30 
+          <div class="caps">Board Member Title</div>
31 
+          <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
32 
+        </td>
33 
+        <td class="beige">
34 
+          <div class="name">Board Member Name</div>
35 
+          <div class="caps">Board Member Title</div>
36 
+          <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
37 
+        </td>
38 
+      </tr>
39 
+      <tr>
40 
+        <td class="beige">
41 
+          <div class="name">Board Member Name</div>
42 
+          <div class="caps">Board Member Title</div>
43 
+          <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
44 
+        </td>
45 
+        <td>
46 
+          <div class="name">Board Member Name</div>
47 
+          <div class="caps">Board Member Title</div>
48 
+          <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
49 
+        </td>
50 
+      </tr>
51 
+      <tr>
52 
+        <td>
53 
+          <div class="name">Board Member Name</div>
54 
+          <div class="caps">Board Member Title</div>
55 
+          <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
56 
+        </td>
57 
+        <td class="beige">
58 
+          <div class="name">Board Member Name</div>
59 
+          <div class="caps">Board Member Title</div>
60 
+          <p>Board Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
61 
+        </td>
62 
+      </tr>
63 
+    </table>
64 
+    <!-- END TABLE -->
65 
+  </div>
66 
+  <!-- END MAINCOL -->
67 
+  <div id = "sidecol">
68 
+#include "side.wmi"
69 
+#include "info.wmi"
70 
+  </div>
71 
+  <!-- END SIDECOL -->
72 
+</div>
73 
+<!-- END CONTENT -->
74 
+#include <foot.wmi>
75 
+
about/en/contact.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,39 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22359 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Contact" CHARSET="UTF-8"
6 
+
7 
+<div id="content" class="clearfix">
8 
+	<div id="breadcrumbs">
9 
+    <a href="<page home>">Home &raquo; </a>
10 
+    <a href="<page about/about>">About &raquo; </a>
11 
+    <a href="<page about/contact>">Contact</a>
12 
+  </div>
13 
+  <div id="maincol">
14 
+    <h2>Tor: Contact</h2>
15 
+
16 
+    <p>First, if you have a problem or question about using Tor, go look at the <a href="<page docs/documentation>#Support">Support section</a> for how to proceed. The Tor developers spend most of their time developing Tor, and there are no people devoted to user support, so try to help yourself before <a href="<page docs/faq>#SupportMail">politely trying to find a volunteer</a>.</p>
17 
+
18 
+    <p>If you really do need to reach us, here are some approaches. All of these addresses are @torproject.org. Note that in practice most of them go to the same small group of people, so please be patient and <a href="http://www.catb.org/~esr/faqs/smart-questions.html">helpful</a>, and please make sure to write your mail in English.</p>
19 
+
20 
+    <ul>
21 
+      <li><tt>tor-assistants</tt> is the catch-all address for everything. If you'd like to ask a more directed question, please see the descriptions below.</li>
22 
+      <li><tt>tor-ops</tt> gets to the people who manage the directory authorities. Use this if you run a Tor relay and have a question or problem with your relay.</li>
23 
+      <li><tt>tor-webmaster</tt> can fix typos on the website, change wrong statements or directions on the website, and add new sections and paragraphs that you send us. You might want to make a draft of your new sections on <a href="https://trac.torproject.org/projects/tor/wiki">the Tor wiki</a> first.</li>
24 
+      <li><tt>tor-volunteer</tt> wants to hear about your documents, patches, testing, experiences with supporting applications, and so forth inspired by our <a href="<page getinvolved/volunteer>">volunteer page</a> (or other problems you've fixed or documented about using Tor). There's no need to mail us before you start working on something -- like all volunteer Internet projects, we hear from a lot of excited people who vanish soon after, so we are most interested in hearing about actual progress.</li>
25 
+      <li><tt>tor-translation</tt> can put new <a href="<page getinvolved/translation>">website translations</a> into place, and help answer questions about existing and new translations.</li>
26 
+      <li><tt>tordnsel</tt> is the alias for the people responsible for the tordns exitlist.</li>
27 
+      <li><tt>donations</tt> is for questions and comments about <a href="<page donate/donate>">getting money to the developers</a>. More donations means <a href="<page docs/faq>#Funding">more Tor</a>. We're happy to help think about creative ways for you to contribute.</li>
28 
+      <li><tt>execdir</tt> is for press/media, questions and comments about Tor the non-profit corporation: trademark questions, affiliation and coordination, major gifts, contract inquiries, licensing and certification, etc.</li>
29 
+    </ul>
30 
+  </div>
31 
+  <!-- END MAINCOL -->
32 
+  <div id = "sidecol">
33 
+#include "side.wmi"
34 
+#include "info.wmi"
35 
+  </div>
36 
+  <!-- END SIDECOL -->
37 
+</div>
38 
+<!-- END CONTENT -->
39 
+#include <foot.wmi>
about/en/contributors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,74 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+#include "head.wmi" TITLE="Tor Project: Past Contributors" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+<div id="content" class="clearfix">
6 
+	<div id="breadcrumbs">
7 
+    <a href="<page home>">Home &raquo; </a>
8 
+    <a href="<page about/about>">About &raquo; </a>
9 
+    <a href="<page about/contributors>">Past Contributors</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+  	<h1>Past Contributors</h1>
13 
+    <table>
14 
+    	<tr>
15 
+        <td class="beige">
16 
+          <div class="name">Contributor Name</div>
17 
+          <div class="caps">Contributor Title</div>
18 
+          <p>Contributor is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
19 
+        </td>
20 
+        <td>
21 
+          <div class="name">Contributor Name</div>
22 
+          <div class="caps">Contributor Title</div>
23 
+          <p>Contributor is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
24 
+        </td>
25 
+      </tr>
26 
+      <tr>
27 
+        <td>
28 
+          <div class="name">Contributor Name</div>
29 
+          <div class="caps">Contributor Title</div>
30 
+          <p>Contributor is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
31 
+        </td>
32 
+        <td class="beige">
33 
+          <div class="name">Contributor Name</div>
34 
+          <div class="caps">Contributor Title</div>
35 
+          <p>Contributor is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
36 
+        </td>
37 
+      </tr>
38 
+      <tr>
39 
+        <td class="beige">
40 
+          <div class="name">Contributor Name</div>
41 
+          <div class="caps">Contributor Title</div>
42 
+          <p>Contributor is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
43 
+        </td>
44 
+        <td>
45 
+          <div class="name">Contributor Name</div>
46 
+          <div class="caps">Contributor Title</div>
47 
+          <p>Contributor is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
48 
+        </td>
49 
+      </tr>
50 
+      <tr>
51 
+        <td>
52 
+          <div class="name">Contributor Name</div>
53 
+          <div class="caps">Contributor Title</div>
54 
+          <p>Contributor is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
55 
+        </td>
56 
+        <td class="beige">
57 
+          <div class="name">Contributor Name</div>
58 
+          <div class="caps">Contributor Title</div>
59 
+          <p>Contributor is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
60 
+        </td>
61 
+      </tr>
62 
+    </table>
63 
+    <!-- END TABLE -->
64 
+  </div>
65 
+  <!-- END MAINCOL -->
66 
+
67 
+  <div id = "sidecol">
68 
+#include "side.wmi"
69 
+#include "info.wmi"
70 
+  </div>
71 
+  <!-- END SIDECOL -->
72 
+</div>
73 
+<!-- END CONTENT -->
74 
+#include <foot.wmi>
about/en/corepeople.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,74 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+#include "head.wmi" TITLE="Tor Project: Core People" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+<div id="content" class="clearfix">
6 
+	<div id="breadcrumbs">
7 
+    <a href="<page home>">Home &raquo; </a>
8 
+    <a href="<page about/about>">About &raquo; </a>
9 
+    <a href="<page about/corepeople>">Tor People</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+  	<h1>Core Tor People</h1>
13 
+    <table>
14 
+    	<tr>
15 
+        <td class="beige">
16 
+          <div class="name">Staff Member Name</div>
17 
+          <div class="caps">Staff Member Title</div>
18 
+          <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
19 
+        </td>
20 
+        <td>
21 
+          <div class="name">Staff Member Name</div>
22 
+          <div class="caps">Staff Member Title</div>
23 
+          <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
24 
+        </td>
25 
+      </tr>
26 
+      <tr>
27 
+        <td>
28 
+          <div class="name">Staff Member Name</div>
29 
+          <div class="caps">Staff Member Title</div>
30 
+          <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
31 
+        </td>
32 
+        <td class="beige">
33 
+          <div class="name">Staff Member Name</div>
34 
+          <div class="caps">Staff Member Title</div>
35 
+          <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
36 
+        </td>
37 
+      </tr>
38 
+      <tr>
39 
+        <td class="beige">
40 
+          <div class="name">Staff Member Name</div>
41 
+          <div class="caps">Staff Member Title</div>
42 
+          <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
43 
+        </td>
44 
+        <td>
45 
+          <div class="name">Staff Member Name</div>
46 
+          <div class="caps">Staff Member Title</div>
47 
+          <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
48 
+        </td>
49 
+      </tr>
50 
+      <tr>
51 
+        <td>
52 
+          <div class="name">Staff Member Name</div>
53 
+          <div class="caps">Staff Member Title</div>
54 
+          <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
55 
+        </td>
56 
+        <td class="beige">
57 
+          <div class="name">Staff Member Name</div>
58 
+          <div class="caps">Staff Member Title</div>
59 
+          <p>Staff Member is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
60 
+        </td>
61 
+      </tr>
62 
+    </table>
63 
+    <!-- END TABLE -->
64 
+
65 
+  </div>
66 
+  <!-- END MAINCOL -->
67 
+  <div id = "sidecol">
68 
+#include "side.wmi"
69 
+#include "info.wmi"
70 
+  </div>
71 
+  <!-- END SIDECOL -->
72 
+</div>
73 
+<!-- END CONTENT -->
74 
+#include <foot.wmi>
about/en/future.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,47 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Future of Tor" CHARSET="UTF-8" <p>
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/future>">The Future of Tor</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>The future of Tor</a></h1>
14 
+
15 
+    <p>
16 
+    Providing a usable anonymizing network on the Internet today is an
17 
+    ongoing challenge. We want software that meets users' needs. We also
18 
+    want to keep the network up and running in a way that handles as many
19 
+    users as possible. Security and usability don't have to be at odds:
20 
+    As Tor's usability increases, it will attract more users, which will
21 
+    increase the possible sources and destinations of each communication,
22 
+    thus increasing security for everyone.
23 
+    We're making progress, but we need your help.  Please consider
24 
+    <a href="<page docs/tor-doc-relay>">running a relay</a>
25 
+    or <a href="<page getinvolved/volunteer>">volunteering</a> as a
26 
+    <a href="<page docs/documentation>#Developers">developer</a>.
27 
+    </p>
28 
+
29 
+    <p>
30 
+    Ongoing trends in law, policy, and technology threaten anonymity as never
31 
+    before, undermining our ability to speak and read freely online. These
32 
+    trends also undermine national security and critical infrastructure by
33 
+    making communication among individuals, organizations, corporations,
34 
+    and governments more vulnerable to analysis. Each new user and relay
35 
+    provides additional diversity, enhancing Tor's ability to put control
36 
+    over your security and privacy back into your hands.
37 
+    </p>
38 
+  </div>
39 
+  <!-- END MAINCOL -->
40 
+  <div id = "sidecol">
41 
+#include "side.wmi"
42 
+#include "info.wmi"
43 
+  </div>
44 
+  <!-- END SIDECOL -->
45 
+</div>
46 
+<!-- END CONTENT -->
47 
+#include <foot.wmi>
about/en/gsoc.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,210 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22179 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor: Google Summer of Code 2010" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/gsoc>">Google Summer of Code 2010</a>
10 
+  </div>
11 
+  <div id="maincol">
12 
+    <h2>Tor: Google Summer of Code 2010</h2>
13 
+    <hr />
14 
+
15 
+    <p>
16 
+    In the last three years, The Tor Project in collaboration with <a
17 
+    href="https://www.eff.org/">The Electronic Frontier Foundation</a>
18 
+    successfully took part in
19 
+    <a href="http://code.google.com/soc/2007/eff/about.html">Google Summer of Code
20 
+    2007</a>, <a href="http://code.google.com/soc/2008/eff/about.html">2008</a>,
21 
+    and <a href="http://socghop.appspot.com/gsoc/org/home/google/gsoc2009/eff">2009</a>.
22 
+    In total we had 17 students as full-time developers for the summers of 2007 to
23 
+    2009. Now we've been accepted to <a
24 
+    href="https://socghop.appspot.com/gsoc/org/show/google/gsoc2010/tor">Google
25 
+    Summer of Code 2010</a>!
26 
+    </p>
27 
+
28 
+    <p>
29 
+    The <a
30 
+    href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/timeline">deadline</a>
31 
+    for your <a
32 
+    href="http://socghop.appspot.com/document/show/gsoc_program/google/gsoc2010/faqs#student_apply">application</a>
33 
+    is <b>April 9, 2010</b> at 19:00 UTC.
34 
+    </p>
35 
+
36 
+    <p>
37 
+    You must be self-motivated and able to work independently. We have
38 
+    a thriving community of interested developers on the IRC channel and
39 
+    mailing lists, and we're eager to work with you, brainstorm about design,
40 
+    and so on, but you need to be able to manage your own time, and you
41 
+    need to already be somewhat familiar with how free software development on the
42 
+    Internet works.
43 
+    </p>
44 
+
45 
+    <p>
46 
+    Working on Tor is rewarding because:
47 
+    </p>
48 
+
49 
+    <ul>
50 
+    <li>You can work your own hours in your own locations. As long as you
51 
+    get the job done, we don't care about the process.</li>
52 
+    <li>We only write free (open source) software. The tools you make won't
53 
+    be locked down or rot on a shelf.</li>
54 
+    <li>You will work with a world-class team of anonymity experts and
55 
+    developers on what is already the largest and most active strong anonymity
56 
+    network ever.</li>
57 
+    <li>The work you do could contribute to academic publications &mdash;
58 
+    Tor development raises many open questions and interesting problems
59 
+    in the field of <a href="http://freehaven.net/anonbib/">anonymity
60 
+    systems</a>.</li>
61 
+    </ul>
62 
+
63 
+    <a id="GettingInvolved"></a>
64 
+    <h2><a class="anchor" href="#GettingInvolved">How To Get Involved</a></h2>
65 
+
66 
+    <p>
67 
+    The best way to get involved is to come listen on IRC (both "#tor" and
68 
+    "#tor-dev"), read our docs and other webpages, try out the various tools
69 
+    that are related to the projects that interest you, and ask questions
70 
+    as they come to you: <a href="<page docs/documentation>#UpToSpeed">Getting
71 
+    up to speed</a>.
72 
+    </p>
73 
+
74 
+    <p>
75 
+    In addition to getting some more development work
76 
+    done on Tor and related applications, Google and Tor are most interested
77 
+    in getting students involved in Tor development in a way that keeps them
78 
+    involved after the summer too. That means we will give priority to students
79 
+    who have demonstrated continued interest and responsiveness. We will require
80 
+    students to write public status report updates for our community, either by
81 
+    blogging or sending mail to our mailing list. We want to ensure that the
82 
+    community and the student can both benefit from each other.
83 
+    </p>
84 
+
85 
+    <p>
86 
+    When it comes time for us to choose projects, our impression of how well
87 
+    you'll fit into our community &mdash; and how good you are at taking
88 
+    the initiative to do things &mdash; will be at least as important as
89 
+    the actual project you'll be working on.
90 
+    </p>
91 
+
92 
+    <a id="Ideas"></a>
93 
+    <h2><a class="anchor" href="#Ideas">Ideas List</a></h2>
94 
+
95 
+    <p>
96 
+    This year, we have two ideas lists: one for projects to
97 
+    <a href="<page getinvolved/volunteer>#Projects">help develop Tor</a>,
98 
+    and one for <a href="https://www.eff.org/gsoc2010">EFF's projects</a>.
99 
+    </p>
100 
+
101 
+    <p>
102 
+    The best kind of ideas are A) ones that we know we need done real soon
103 
+    now (you can get a sense of urgency from the priority on the wishlist,
104 
+    and from talking to the potential mentors), and B) ones where it's
105 
+    clear what needs to be done, at least for the first few steps. Lots of
106 
+    students try to bite off open-ended research topics; but if you're going
107 
+    to be spending the first half of your summer figuring out what exactly
108 
+    you should code, and there's a chance that the conclusion will be "oh,
109 
+    that isn't actually a good idea to build", then your proposal will make
110 
+    us very nervous. Try to figure out how much you can actually fit in a
111 
+    summer, break the work down into manageable pieces, and most importantly,
112 
+    figure out how to make sure your incremental milestones are actually
113 
+    useful &mdash; if you don't finish everything in your plan, we want to
114 
+    know that you'll still have produced something useful.
115 
+    </p>
116 
+
117 
+    <a id="Template"></a>
118 
+    <h2><a class="anchor" href="#Template">Application Template</a></h2>
119 
+
120 
+    <p>
121 
+    Please use the following template for your application, to make sure you
122 
+    provide enough information for us to evaluate you and your proposal.
123 
+    </p>
124 
+
125 
+    <ol>
126 
+
127 
+    <li>What project would you like to work on? Use our ideas lists as a starting
128 
+    point or make up your own idea. Your proposal should include high-level
129 
+    descriptions of what you're going to do, with more details about the
130 
+    parts you expect to be tricky. Your proposal should also try to break
131 
+    down the project into tasks of a fairly fine granularity, and convince
132 
+    us you have a plan for finishing it.</li>
133 
+
134 
+    <li>Point us to a code sample: something good and clean to demonstrate
135 
+    that you know what you're doing, ideally from an existing project.</li>
136 
+
137 
+    <li>Why do you want to work with The Tor Project / EFF in
138 
+    particular?</li>
139 
+
140 
+    <li>Tell us about your experiences in free software development
141 
+    environments. We especially want to hear examples of how you have
142 
+    collaborated with others rather than just working on a project by
143 
+    yourself.</li>
144 
+
145 
+    <li>Will you be working full-time on the project for the summer, or will
146 
+    you have other commitments too (a second job, classes, etc)? If you won't
147 
+    be available full-time, please explain, and list timing if you know them
148 
+    for other major deadlines (e.g. exams). Having other activities isn't
149 
+    a deal-breaker, but we don't want to be surprised.</li>
150 
+
151 
+    <li>Will your project need more work and/or maintenance after the summer
152 
+    ends? What are the chances you will stick around and help out with that
153 
+    and other related projects?</li>
154 
+
155 
+    <li>What is your ideal approach to keeping everybody informed of your
156 
+    progress, problems, and questions over the course of the project? Said
157 
+    another way, how much of a "manager" will you need your mentor to be?</li>
158 
+
159 
+    <li>What school are you attending? What year are you, and what's your
160 
+    major/degree/focus? If you're part of a research group, which one?</li>
161 
+
162 
+    <li>How can we contact you to ask you further questions? Google doesn't
163 
+    share your contact details with us automatically, so you should include
164 
+    that in your application. In addition, what's your IRC nickname?
165 
+    Interacting with us on IRC will help us get to know you, and help you
166 
+    get to know our community.</li>
167 
+
168 
+    <li>Is there anything else we should know that will make us like your
169 
+    project more?</li>
170 
+
171 
+    </ol>
172 
+
173 
+    <p>
174 
+    We have picked out 10+ mentors for this year &mdash; most of the
175 
+    people on the <a href="<page about/people>#Core">core Tor development team</a>
176 
+    plus a few people from <a href="http://www.eff.org/about/staff">EFF's staff</a>
177 
+    &mdash; so we should be able to accommodate a wide variety of projects,
178 
+    ranging from work on Tor itself to work on supporting or peripheral
179 
+    projects. We can figure out which mentor is appropriate while we're
180 
+    discussing the project you have in mind. We plan to assign a primary
181 
+    mentor to each student, along with one or two assistant mentors to help
182 
+    answer questions and help you integrate with the broader Tor community.
183 
+    </p>
184 
+
185 
+    <p>
186 
+    If you're interested, you can either contact the <a href="<page
187 
+    about/contact>">tor-assistants list</a> with a brief summary of your proposal
188 
+    and we'll give you feedback, or just jump right in and post your ideas
189 
+    and goals to the <a href="<page docs/documentation>#MailingLists">or-talk
190 
+    mailing list</a>. Make sure to be responsive during the application
191 
+    selection period; if we like your application but you never answer our
192 
+    mails asking for more information, that's not a good sign.
193 
+    </p>
194 
+
195 
+    <p>
196 
+    The more applications we get, the more likely Google is to give us good
197 
+    students. So if you haven't filled up your summer plans yet, please
198 
+    consider spending some time working with us to make Tor better!
199 
+    </p>
200 
+  </div>
201 
+  <!-- END MAINCOL -->
202 
+  <div id = "sidecol">
203 
+#include "side.wmi"
204 
+#include "info.wmi"
205 
+  </div>
206 
+  <!-- END SIDECOL -->
207 
+</div>
208 
+<!-- END CONTENT -->
209 
+#include <foot.wmi>
210 
+
about/en/overview.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,261 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22308 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Overview" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/about>">Overview</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a name="overview"></a>
14 
+    <h2><a class="anchor" href="#overview">Tor: Overview</a></h2>
15 
+    <!-- BEGIN SIDEBAR -->
16 
+    <div class="sidebar-left">
17 
+      <h3>Topics</h3>
18 
+      <ul>
19 
+        <li><a href="<page about/overview>#overview">Overview</a></li>
20 
+        <li><a href="<page about/overview>#whyweneedtor">Why we need Tor</a></li>
21 
+        <li><a href="<page about/overview>#thesolution">The Solution</a></li>
22 
+        <li><a href="<page about/overview>#hiddenservices">Hidden services</a></li>
23 
+        <li><a href="<page about/overview>#stayinganonymous">Staying anonymous</a></li>
24 
+        <li><a href="<page about/overview>#thefutureoftor">The future of Tor</a></li>
25 
+      </ul>
26 
+    </div>
27 
+    <!-- END SIDEBAR -->
28 
+
29 
+    <hr />
30 
+
31 
+    <p>
32 
+    Tor is a network of virtual tunnels that allows people and groups to
33 
+    improve their privacy and security on the Internet.  It also enables
34 
+    software developers to create new communication tools
35 
+    with built-in privacy features.  Tor provides the foundation for
36 
+    a range of applications that allow organizations and individuals
37 
+    to share information over public networks without compromising their
38 
+    privacy.
39 
+    </p>
40 
+
41 
+    <p>
42 
+    Individuals use Tor to keep websites from tracking them and their family
43 
+    members, or to connect to news sites, instant messaging services, or the
44 
+    like when these are blocked by their local Internet providers.  Tor's <a
45 
+    href="<page docs/hidden-services>">hidden services</a>
46 
+    let users publish web sites and other services without needing to reveal
47 
+    the location of the site. Individuals also use Tor for socially sensitive
48 
+    communication: chat rooms and web forums for rape and abuse survivors,
49 
+    or people with illnesses.
50 
+    </p>
51 
+
52 
+    <p>
53 
+    Journalists use Tor to communicate more safely with whistleblowers and
54 
+    dissidents. Non-governmental organizations (NGOs) use Tor to allow their
55 
+    workers to connect to their home website while they're in a foreign
56 
+    country, without notifying everybody nearby that they're working with
57 
+    that organization.
58 
+    </p>
59 
+
60 
+    <p>
61 
+    Groups such as Indymedia recommend Tor for safeguarding their members'
62 
+    online privacy and security. Activist groups like the Electronic Frontier
63 
+    Foundation (EFF) recommend Tor as a mechanism for
64 
+    maintaining civil liberties online. Corporations use Tor as a safe way
65 
+    to conduct competitive analysis, and to protect sensitive procurement
66 
+    patterns from eavesdroppers. They also use it to replace traditional
67 
+    VPNs, which reveal the exact amount and timing of communication. Which
68 
+    locations have employees working late? Which locations have employees
69 
+    consulting job-hunting websites? Which research divisions are communicating
70 
+    with the company's patent lawyers?
71 
+    </p>
72 
+
73 
+    <p>
74 
+    A branch of the U.S. Navy uses Tor for open source intelligence
75 
+    gathering, and one of its teams used Tor while deployed in the Middle
76 
+    East recently. Law enforcement uses Tor for visiting or surveilling
77 
+    web sites without leaving government IP addresses in their web logs,
78 
+    and for security during sting operations.
79 
+    </p>
80 
+
81 
+    <p>
82 
+    The variety of people who use Tor is actually <a
83 
+    href="http://freehaven.net/doc/fc03/econymics.pdf">part of what makes
84 
+    it so secure</a>.  Tor hides you among <a href="<page about/torusers>">the
85 
+    other users on the network</a>,
86 
+    so the more populous and diverse the user base for Tor is, the more your
87 
+    anonymity will be protected.
88 
+    </p>
89 
+
90 
+    <a name="whyweneedtor"></a>
91 
+    <h3><a class="anchor" href="#whyweneedtor">Why we need Tor</a></h3>
92 
+
93 
+    <p>
94 
+    Using Tor protects you against a common form of Internet surveillance
95 
+    known as "traffic analysis."  Traffic analysis can be used to infer
96 
+    who is talking to whom over a public network.  Knowing the source
97 
+    and destination of your Internet traffic allows others to track your
98 
+    behavior and interests.  This can impact your checkbook if, for example,
99 
+    an e-commerce site uses price discrimination based on your country or
100 
+    institution of origin.  It can even threaten your job and physical safety
101 
+    by revealing who and where you are. For example, if you're travelling
102 
+    abroad and you connect to your employer's computers to check or send mail,
103 
+    you can inadvertently reveal your national origin and professional
104 
+    affiliation to anyone observing the network, even if the connection
105 
+    is encrypted.
106 
+    </p>
107 
+
108 
+    <p>
109 
+    How does traffic analysis work?  Internet data packets have two parts:
110 
+    a data payload and a header used for routing.  The data payload is
111 
+    whatever is being sent, whether that's an email message, a web page, or an
112 
+    audio file.  Even if you encrypt the data payload of your communications,
113 
+    traffic analysis still reveals a great deal about what you're doing and,
114 
+    possibly, what you're saying.  That's because it focuses on the header,
115 
+    which discloses source, destination, size, timing, and so on.
116 
+    </p>
117 
+
118 
+    <p>
119 
+    A basic problem for the privacy minded is that the recipient of your
120 
+    communications can see that you sent it by looking at headers.  So can
121 
+    authorized intermediaries like Internet service providers, and sometimes
122 
+    unauthorized intermediaries as well.  A very simple form of traffic
123 
+    analysis might involve sitting somewhere between sender and recipient on
124 
+    the network, looking at headers.
125 
+    </p>
126 
+
127 
+    <p>
128 
+    But there are also more powerful kinds of traffic analysis.  Some
129 
+    attackers spy on multiple parts of the Internet and use sophisticated
130 
+    statistical techniques to track the communications patterns of many
131 
+    different organizations and individuals.  Encryption does not help against
132 
+    these attackers, since it only hides the content of Internet traffic, not
133 
+    the headers.
134 
+    </p>
135 
+
136 
+    <a name="thesolution"></a>
137 
+    <h3><a class="anchor" href="#thesolution">The solution: a distributed, anonymous network</a></h3>
138 
+
139 
+    <p>
140 
+    Tor helps to reduce the risks of both simple and sophisticated traffic
141 
+    analysis by distributing your transactions over several places on the
142 
+    Internet, so no single point can link you to your destination.  The idea
143 
+    is similar to using a twisty, hard-to-follow route in order to throw off
144 
+    somebody who is tailing you &mdash; and then periodically erasing your
145 
+    footprints.  Instead of taking a direct route from source to
146 
+    destination, data packets on the Tor network take a random pathway
147 
+    through several relays that cover your tracks so no observer at any
148 
+    single point can tell where the data came from or where it's going.
149 
+    </p>
150 
+
151 
+    <p><img alt="Tor circuit step one" src="$(IMGROOT)/htw1.png" /></p>
152 
+
153 
+    <p>
154 
+    To create a private network pathway with Tor, the user's software or
155 
+    client incrementally builds a circuit of encrypted connections through
156 
+    relays on the network.  The circuit is extended one hop at a time, and
157 
+    each relay along the way knows only which relay gave it data and which
158 
+    relay it is giving data to.  No individual relay ever knows the
159 
+    complete path that a data packet has taken.  The client negotiates a
160 
+    separate set of encryption keys for each hop along the circuit to ensure
161 
+    that each hop can't trace these connections as they pass through.
162 
+    </p>
163 
+
164 
+    <p><img alt="Tor circuit step two" src="$(IMGROOT)/htw2.png" /></p>
165 
+
166 
+    <p>
167 
+    Once a circuit has been established, many kinds of data can be exchanged
168 
+    and several different sorts of software applications can be deployed
169 
+    over the Tor network.  Because each relay sees no more than one hop in
170 
+    the circuit, neither an eavesdropper nor a compromised relay can use
171 
+    traffic analysis to link the connection's source and destination.  Tor
172 
+    only works for TCP streams and can be used by any application with SOCKS
173 
+    support.
174 
+    </p>
175 
+
176 
+    <p>
177 
+    For efficiency, the Tor software uses the same circuit for connections
178 
+    that happen within the same ten minutes or so.  Later requests are given a
179 
+    new circuit, to keep people from linking your earlier actions to the new
180 
+    ones.
181 
+    </p>
182 
+
183 
+    <p><img alt="Tor circuit step three" src="$(IMGROOT)/htw3.png" /></p>
184 
+
185 
+
186 
+    <a name="hiddenservices"></a>
187 
+    <h3><a class="anchor" href="#hiddenservices">Hidden services</a></h3>
188 
+
189 
+    <p>
190 
+    Tor also makes it possible for users to hide their locations while
191 
+    offering various kinds of services, such as web publishing or an instant
192 
+    messaging server.  Using Tor "rendezvous points," other Tor users can
193 
+    connect to these hidden services, each without knowing the other's
194 
+    network identity.  This hidden service functionality could allow Tor
195 
+    users to set up a website where people publish material without worrying
196 
+    about censorship.  Nobody would be able to determine who was offering
197 
+    the site, and nobody who offered the site would know who was posting to it.
198 
+    Learn more about <a href="<page docs/tor-hidden-service>">configuring
199 
+    hidden services</a> and how the <a href="<page docs/hidden-services>">hidden
200 
+    service protocol</a> works.
201 
+    </p>
202 
+
203 
+    <a name="stayinganonymous"></a>
204 
+    <h3><a class="anchor" href="#stayinganonymous">Staying anonymous</a></h3>
205 
+
206 
+    <p>
207 
+    Tor can't solve all anonymity problems.  It focuses only on
208 
+    protecting the transport of data.  You need to use protocol-specific
209 
+    support software if you don't want the sites you visit to see your
210 
+    identifying information. For example, you can use web proxies such as
211 
+    Privoxy while web browsing to block cookies and withhold information
212 
+    about your browser type.
213 
+    </p>
214 
+
215 
+    <p>
216 
+    Also, to protect your anonymity, be smart.  Don't provide your name
217 
+    or other revealing information in web forms.  Be aware that, like all
218 
+    anonymizing networks that are fast enough for web browsing, Tor does not
219 
+    provide protection against end-to-end timing attacks: If your attacker
220 
+    can watch the traffic coming out of your computer, and also the traffic
221 
+    arriving at your chosen destination, he can use statistical analysis to
222 
+    discover that they are part of the same circuit.
223 
+    </p>
224 
+
225 
+    <a name="thefutureoftor"></a>
226 
+    <h3><a class="anchor" href="#thefutureoftor">The future of Tor</a></h3>
227 
+
228 
+    <p>
229 
+    Providing a usable anonymizing network on the Internet today is an
230 
+    ongoing challenge. We want software that meets users' needs. We also
231 
+    want to keep the network up and running in a way that handles as many
232 
+    users as possible. Security and usability don't have to be at odds:
233 
+    As Tor's usability increases, it will attract more users, which will
234 
+    increase the possible sources and destinations of each communication,
235 
+    thus increasing security for everyone.
236 
+    We're making progress, but we need your help.  Please consider
237 
+    <a href="<page docs/tor-doc-relay>">running a relay</a>
238 
+    or <a href="<page getinvolved/volunteer>">volunteering</a> as a
239 
+    <a href="<page docs/documentation>#Developers">developer</a>.
240 
+    </p>
241 
+
242 
+    <p>
243 
+    Ongoing trends in law, policy, and technology threaten anonymity as never
244 
+    before, undermining our ability to speak and read freely online. These
245 
+    trends also undermine national security and critical infrastructure by
246 
+    making communication among individuals, organizations, corporations,
247 
+    and governments more vulnerable to analysis. Each new user and relay
248 
+    provides additional diversity, enhancing Tor's ability to put control
249 
+    over your security and privacy back into your hands.
250 
+    </p>
251 
+
252 
+  </div>
253 
+  <!-- END MAINCOL -->
254 
+  <div id = "sidecol">
255 
+#include "side.wmi"
256 
+#include "info.wmi"
257 
+  </div>
258 
+  <!-- END SIDECOL -->
259 
+</div>
260 
+<!-- END CONTENT -->
261 
+#include <foot.wmi>
about/en/people.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,357 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22448 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: People" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/board>">Board of Directors</a>
11 
+  </div>
12 
+  <div class="maincol">
13 
+    <h2>Tor: People</h2>
14 
+
15 
+    #<!-- BEGIN SIDEBAR -->
16 
+    #<div class="sidebar-left">
17 
+    #<h3>Sections</h3>
18 
+    #<ul>
19 
+    #<li><a href="<page about/corepeople>#Core">Core Tor People</a></li>
20 
+    #<li><a href="<page about/people>#Board">Board of Directors</a></li>
21 
+    #<li><a href="<page about/people>#GSoC">Summer Students</a></li>
22 
+    #<li><a href="<page about/people>#Translators">Translators</a></li>
23 
+    #<li><a href="<page about/people>#Volunteers">Volunteers</a></li>
24 
+    #<li><a href="<page about/people>#Past">Past Contributors</a></li>
25 
+    #</ul>
26 
+    #</div>
27 
+    #<!-- END SIDEBAR -->
28 
+
29 
+    <p>The Tor Project is a 501(c)(3) non-profit based in
30 
+    the United States. The official address of the organization is:
31 
+    </p>
32 
+
33 
+    <address>
34 
+    The Tor Project<br />
35 
+    969 Main Street, Suite 206<br />
36 
+    Walpole, MA 02081 USA<br /><br />
37 
+    </address>
38 
+
39 
+    <p>The organization consists of many volunteers and a few employees.
40 
+    Please don't contact us individually about Tor topics &mdash; if you
41 
+    have a problem or question, please look through the <a href="<page
42 
+    about/contact>">contact page</a> for appropriate addresses.</p>
43 
+
44 
+    <div class="underline"></div>
45 
+    <a id="Core"></a>
46 
+    <h3><a class="anchor" href="#Core">Core Tor people:</a></h3>
47 
+
48 
+    <dl>
49 
+    <dt>Carolyn Anhalt (Community and Translation
50 
+    Coordinator)</dt><dd>Responsible for growing Tor's community
51 
+    moderators and translators.</dd>
52 
+
53 
+    <dt>Jacob Appelbaum (Developer and Advocate)</dt><dd>Runs
54 
+    the <a href="https://check.torproject.org/">Tor DNSEL</a> <a
55 
+    href="http://exitlist.torproject.org/">site</a>, and also the in-progress
56 
+    Tor weather site.</dd>
57 
+
58 
+    <dt>Erinn Clark (Packaging and Build Automation)</dt><dd>Erinn is tackling
59 
+    the growing needs for easy to install and configure packages on a variety
60 
+    of operating systems.  Also working on automating the build system and
61 
+    producing nightly builds for all operating systems we support.</dd>
62 
+
63 
+    <dt>Christopher Davis</dt><dd>Worked during Google Summer of Code 2009
64 
+    on porting Polipo to Windows and on helping with the libevent bufferevent
65 
+    code. Now he's the Polipo maintainer.</dd>
66 
+
67 
+    <dt>Roger Dingledine (Project Leader; Director)</dt><dd>Original
68 
+    developer of Tor; now plays pretty much all the roles to keep everything
69 
+    on track.</dd>
70 
+
71 
+    <dt>Matt Edman (Developer)</dt><dd>Lead developer for <a href="<page
72 
+    projects/vidalia>">Vidalia</a>, a cross-platform Tor GUI included in the
73 
+    Windows and OS X bundles.</dd>
74 
+
75 
+    <dt>Nathan Freitas</dt><dd>The driving force behind Tor on the Android
76 
+    platform in the form of <a href="<page docs/android>">Orbot</a>.</dd>
77 
+
78 
+    <dt>Christian Fromme (Developer)</dt><dd>Christian works on all things
79 
+    python for Tor.  He enhanced and maintains a slew of codebases for us,
80 
+    such as the get-tor email auto-responder, check.torproject.org, bridge
81 
+    db, tor weather, tor controller, tor flow, etc.</dd>
82 
+
83 
+    <dt>Melissa Gilroy (CFO and Internal Audit)</dt><dd>With a strong
84 
+    background in non-profit accounting and auditing, Melissa is in charge of
85 
+    Tor's finances, audit compliance, and keeping Tor's financial operations
86 
+    moving along.</dd>
87 
+
88 
+    <dt>Sebastian Hahn</dt><dd> Worked during the 2008 Google Summer of
89 
+    Code on a networking application to automatically carry out tests for
90 
+    Tor and during the 2009 Google Summer of Code on expanding Thandy to
91 
+    include BitTorrent support. Generally helps out a lot.</dd>
92 
+
93 
+    <dt>Damian Johnson</dt><dd>Builds a command-line application for monitoring
94 
+    Tor relays, providing real-time status information such as the current
95 
+    configuration, bandwidth usage, message log, etc. (<a
96 
+    href="https://svn.torproject.org/svn/arm/trunk/README">code</a>).</dd>
97 
+
98 
+    <dt>Andrew Lewman (Executive Director; Director; <a href="<page
99 
+    press/press>">press contact</a>)</dt><dd>Manages the business operations
100 
+    of The Tor Project, Inc.  Plays roles of finance, advocacy, project
101 
+    management, and general support.  General package hacker for Windows,
102 
+    OS X, and various linux distributions.</dd>
103 
+
104 
+    <dt>Karsten Loesing (Developer)</dt><dd>
105 
+    Worked during the 2007 Google Summer of Code on <a
106 
+    href="<gitblob>doc/spec/proposals/114-distributed-storage.txt">distributing
107 
+    and securing the publishing and fetching of hidden
108 
+    service descriptors</a>. Currently working on <a href="<page
109 
+    projects/hidserv>">making hidden services faster and more reliable</a>,
110 
+    and on <a href="http://metrics.torproject.org/">metrics</a>.</dd>
111 
+
112 
+    <dt>Nick Mathewson (Chief architect; Director)</dt><dd>One of the
113 
+    three original designers of Tor; does a lot of the ongoing design work.
114 
+    One of the two main developers, along with Roger.</dd>
115 
+
116 
+    <dt>Steven Murdoch (Researcher and Developer)</dt><dd>Researcher at
117 
+    the University of Cambridge, currently funded by The Tor Project to
118 
+    improve the security, performance, and usability of Tor. Creator of the
119 
+    <a href="<page projects/torbrowser>">Tor Browser Bundle</a>.</dd>
120 
+
121 
+    <dt>Peter Palfrader</dt><dd>Manages the Debian packages, runs one of
122 
+    the directory authorities, runs the website and the wiki, and generally
123 
+    helps out a lot.</dd>
124 
+
125 
+    <dt>Mike Perry (Developer)</dt><dd>Author of <a
126 
+    href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>,
127 
+    a Tor controller that builds paths through the Tor network and measures
128 
+    various properties and behaviors, and new author of <a href="<page
129 
+    projects/torbutton>">Torbutton</a>.</dd>
130 
+
131 
+    <dt>Karen Reilly (Development Director)</dt><dd>Responsible for
132 
+    fundraising, advocacy, and general marketing and outreach programs
133 
+    for Tor.</dd>
134 
+
135 
+    <dt>Runa A. Sandvik</dt><dd>Maintains the <a
136 
+    href="https://translation.torproject.org/">Tor Translation
137 
+    Portal</a>, and works on automatically converting our website wml
138 
+    files to po files (and back) so that they can be handled by <a
139 
+    href="http://translate.sourceforge.net/wiki/pootle/index">Pootle</a>.</dd>
140 
+
141 
+    <dt>Paul Syverson</dt><dd>Inventor of <a
142 
+    href="http://www.onion-router.net/">Onion Routing</a>, original designer
143 
+    of Tor along with Roger and Nick, and project leader for original design,
144 
+    development, and deployment of Tor. Currently helps out with research
145 
+    and design.</dd>
146 
+    </dl>
147 
+
148 
+    <div class="underline"></div>
149 
+    <a id="Board"></a>
150 
+    <h3><a class="anchor" href="#Board">The Tor Project Board of
151 
+    Directors:</a></h3>
152 
+
153 
+    <dl>
154 
+    <dt>Meredith Hoban Dunn (Director)</dt><dd>Our audit committee chair. Her
155 
+    role is to help us make sure we're able to pass our upcoming corporate
156 
+    audits correctly, watch for internal fraud, tell us when we're doing
157 
+    things in a non-standard way, and so on.</dd>
158 
+
159 
+    <dt>Ian Goldberg (Director)</dt><dd>Cryptographer,
160 
+    privacy expert, and professor; one of the designers of <a
161 
+    href="http://www.cypherpunks.ca/otr/">Off-the-Record Messaging</a>.</dd>
162 
+
163 
+    <dt>Xianghui (Isaac) Mao (Director)</dt><dd>Chinese blogging
164 
+    and privacy activist.  His current activities can be found at <a
165 
+    href="http://isaacmao.com/">his website</a>.</dd>
166 
+
167 
+    <dt>Frank Rieger (Director)</dt><dd>CTO of <a
168 
+    href="http://www.gsmk.de/">GSMK Cryptophone</a>.</dd>
169 
+
170 
+    <dt>Wendy Seltzer (Director)</dt><dd>Lawyer,
171 
+    cyberlaw professor, and founder of <a
172 
+    href="http://chillingeffects.org/">ChillingEffects.org</a>.</dd>
173 
+
174 
+    <dt>Along with Roger, Nick, and Andrew listed above as Directors.</dt>
175 
+    </dl>
176 
+
177 
+    <div class="underline"></div>
178 
+    <a id="GSoC"></a>
179 
+    <h3><a class="anchor" href="#GSoC">Google Summer of Code 2010 students:</a></h3>
180 
+
181 
+    <dl>
182 
+    <dt>Kevin Berry</dt><dd>Working on a database schema to support better
183 
+    node churn metrics and on a more dynamic metrics website. Mentored by
184 
+    Karsten Loesing.</dd>
185 
+    <dt>Harry Bock</dt><dd>Working on TorBEL, a Tor bulk exit list tracker and
186 
+    service designed to replace TorDNSEL. TorBEL is written in Python using
187 
+    the torflow API. Mentored by Sebastian Hahn.</dd>
188 
+    <dt>Kory Kirk</dt><dd>Worked during Google Summer of Code 2009 on
189 
+    extending Torbutton. Now he's working on implementing hidden services
190 
+    for our java Tor client. Mentored by Bruce Leidl.</dd>
191 
+    <dt>John Schanck</dt><dd>Works on improving the automated detection of
192 
+    misconfigured or malicious exit nodes. Mentored by Mike Perry.</dd>
193 
+    </dl>
194 
+
195 
+    <div class="underline"></div>
196 
+    <a id="Translators"></a>
197 
+    <h3><a class="anchor" href="#Translators">Core translators:</a></h3>
198 
+
199 
+    <dl>
200 
+    <dt>Bogdan Drozdowski</dt><dd><a
201 
+    href="https://www.torproject.org/index.html.pl">Polish</a>.</dd>
202 
+    <dt>Tiago Faria</dt><dd>Portuguese.</dd>
203 
+    <dt>fredzupy</dt><dd><a
204 
+    href="https://www.torproject.org/index.html.fr">French</a>.</dd>
205 
+    <dt>Ruben Garcia, plus further pages by <a
206 
+    href="http://www.greentranslations.com/">Green Crescent</a></dt><dd><a
207 
+    href="https://www.torproject.org/index.html.es">Spanish</a>.</dd>
208 
+    <dt>Jens Kubieziel and Oliver Knapp</dt><dd><a
209 
+    href="https://www.torproject.org/index.html.de">German</a>.</dd>
210 
+    <dt>Pei Hanru and bridgefish</dt><dd><a
211 
+    href="https://www.torproject.org/index.html.zh-cn">Simplified Chinese</a>.</dd>
212 
+    <dt>Jan Reister</dt><dd><a
213 
+    href="https://www.torproject.org/index.html.it">Italian</a>.</dd>
214 
+    <dt>Masaki Taniguchi</dt><dd><a
215 
+    href="https://www.torproject.org/index.html.ja">Japanese</a>.</dd>
216 
+    <dt>Jan Woning</dt><dd><a
217 
+    href="https://www.torproject.org/index.html.nl">Dutch</a>.</dd>
218 
+    <dt>ygrek</dt><dd><a
219 
+    href="https://www.torproject.org/index.html.ru">Russian</a>.</dd>
220 
+    </dl>
221 
+
222 
+    <div class="underline"></div>
223 
+    <a id="Volunteers"></a>
224 
+    <h3><a class="anchor" href="#Volunteers">More volunteers:</a></h3>
225 
+
226 
+    <dl>
227 
+    <dt>Anonym</dt><dd>Maintainer of the Incognito LiveCD.</dd>
228 
+    <dt>Kevin Bankston</dt><dd>EFF lawyer who helped write the <a
229 
+    href="<page eff/tor-legal-faq>">Tor Legal FAQ</a> and
230 
+    tirelessly answers the phone when somebody in the world has a legal
231 
+    question about Tor.</dd>
232 
+    <dt>Marco Bonetti</dt><dd>Focusing on MobileTor for the iPhone.</dd>
233 
+    <dt>Kasimir Gabert</dt><dd>Maintains the <a
234 
+    href="https://torstatus.kgprog.com/">TorStatus</a> statistics pages.</dd>
235 
+    <dt>Robert Hogan</dt><dd>Developer for the <a
236 
+    href="http://tork.sf.net/">TorK</a> Tor controller.</dd>
237 
+    <dt>Fabian Keil</dt><dd>One of the core Privoxy developers, and also a
238 
+    Tor fan. He's the reason Tor and Privoxy still work well together.</dd>
239 
+    <dt>Bruce Leidl</dt><dd>Working on a Tor client in Java.</dd>
240 
+    <dt>Julius Mittenzwei</dt><dd>A lawyer with the CCC in
241 
+    Germany. Coordinates the German Tor community with respect to legal
242 
+    questions and concerns.</dd>
243 
+    <dt>Shava Nerad</dt><dd>Our former Development Director. She still works
244 
+    on PR and community relations.</dd>
245 
+    <dt>Linus Nordberg</dt><dd>Enjoys measuring the Tor network and helps
246 
+    with outreach in the Nordic countries.</dd>
247 
+    <dt>Lasse &Oslash;verlier</dt><dd>Writes research papers on Tor: attacks,
248 
+    defenses, and resource management, especially for hidden services.</dd>
249 
+    <dt>Martin Peck</dt><dd>Working on a VM-based transparent
250 
+    proxying approach for Tor clients on Windows.</dd>
251 
+    <dt>rovv (a pseudonym -- he's managed to stay anonymous even from
252 
+    us!)</dt><dd>The most dedicated bug reporter we've ever heard from. He
253 
+    must read Tor source code every day over breakfast.</dd>
254 
+    <dt>tup (another pseudonym)</dt><dd>Periodically adds new features for
255 
+    making Tor easier to use as a <a
256 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TransparentProxy">transparent
257 
+    proxy</a>. Also maintains the <a
258 
+    href="http://p56soo2ibjkx23xo.onion/">TorDNSEL code</a>.</dd>
259 
+    <dt>Kyle Williams</dt><dd>Developer for
260 
+    JanusVM, a VMWare-based
261 
+    transparent Tor proxy that makes Tor easier to set up and use.</dd>
262 
+    <dt>Ethan Zuckerman</dt><dd>A blogger who has written some
263 
+    <a href="http://www.ethanzuckerman.com/blog/?p=1019">interesting</a>
264 
+    <a href="http://advocacy.globalvoicesonline.org/tools/guide/">tutorials</a>
265 
+    for how, when, and whether to use Tor. He also teaches activists around
266 
+    the world about Tor and related tools.</dd>
267 
+    <dt>All our relay operators, people who write <a
268 
+    href="http://freehaven.net/anonbib/">research papers</a> about Tor,
269 
+    people who teach others about Tor, etc.</dt>
270 
+    </dl>
271 
+
272 
+    <div class="underline"></div>
273 
+    <a id="Past"></a>
274 
+    <h3><a class="anchor" href="#Past">Past thanks to:</a></h3>
275 
+
276 
+    <dl>
277 
+    <dt>John Bashinski</dt><dd> Contributed the initial rpm spec file.</dd>
278 
+    <dt>Domenik Bork</dt><dd> Worked on
279 
+    Configuration of Hidden Services with User Authorization in Vidalia (<a
280 
+    href="http://trac.vidalia-project.net/browser/vidalia/branches/hidden-services">svn</a>) as part of Google Summer of Code 2008.</dd>
281 
+    <dt>Benedikt Boss</dt><dd>Worked during the 2007 Google Summer of Code on <a
282 
+    href="https://svn.torproject.org/svn/topf/trunk/README">TOPF</a>,
283 
+    a fuzzer for Tor; mentored by Roger.</dd>
284 
+    <dt>Ren Bucholz</dt><dd>Our fine logo and images.</dd>
285 
+    <dt>Fallon Chen</dt><dd> Worked on
286 
+    Improving Tor Path Selection (<a
287 
+    href="https://svn.torproject.org/cgi-bin/viewcvs.cgi/torflow/branches/gsoc2008/">svn</a>)
288 
+    and <a
289 
+    href="<gitblob>doc/spec/proposals/151-path-selection-improvements.txt">proposal
290 
+    151</a> as part of Google Summer of Code 2008.</dd>
291 
+    <dt>Bram Cohen</dt><dd>Helped design our congestion control mechanisms,
292 
+    in Tor's early days.</dd>
293 
+    <dt>Pat Double</dt><dd>Creator of the Incognito LiveCD.</dd>
294 
+    <dt>Geoff Goodell</dt><dd>Started the <a
295 
+    href="https://svn.torproject.org/svn/blossom/trunk/">Blossom project</a>
296 
+    which uses Tor as its overlay network; also helped motivate Tor's control
297 
+    interface to be as flexible as it is.</dd>
298 
+    <dt>Aleksei Gorny</dt><dd> Working on
299 
+    Tor exit scanner improvements (<a
300 
+    href="https://svn.torproject.org/cgi-bin/viewcvs.cgi/torflow/branches/gsoc2008/">svn</a>), originally started as part of Google Summer of Code 2008.</dd>
301 
+    <dt>Christian Grothoff</dt><dd> Contributed better daemonizing behavior.</dd>
302 
+    <dt>Steven Hazel</dt><dd> Made 'make install' do the right thing.</dd>
303 
+    <dt>Justin Hipple</dt><dd>The other developer for Vidalia.</dd>
304 
+    <dt>Jason Holt</dt><dd> Contributed patches to the instructions and the man
305 
+    page.</dd>
306 
+    <dt>Christian King</dt><dd> Worked during the 2007 Google Summer of Code
307 
+    on making Tor relays stable on
308 
+    Windows, by developing a <a
309 
+    href="https://svn.torproject.org/svn/libevent-urz/trunk/README">buffer
310 
+    implementation for libevent</a>; mentored by Nick.</dd>
311 
+    <dt>Joe Kowalski</dt><dd>Original author and provider of the torstatus
312 
+    script formerly run on nighteffect.</dd>
313 
+    <dt>Adam Langley</dt><dd>Our fine eventdns code.</dd>
314 
+    <dt>Rebecca MacKinnon</dt><dd>Former Director of Tor.  Co-Founder of <a
315 
+    href="http://www.globalvoicesonline.org/">Global Voices Online</a>.</dd>
316 
+    <dt>Chris Palmer</dt><dd>Our liaison and tech guy with EFF while EFF
317 
+    was funding us. Also helped advocate and write end-user docs.</dd>
318 
+    <dt>Matej Pfajfar</dt><dd>Author of the original onion routing code that
319 
+    Tor is based on, so we didn't have to start from scratch.</dd>
320 
+    <dt>Johannes Renner</dt><dd> Worked during the 2007 Google Summer of
321 
+    Code on modifying <a
322 
+    href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>
323 
+    to measure various properties of the Tor network; mentored by Mike
324 
+    Perry.</dd>
325 
+    <dt>Scott Squires</dt><dd>The original developer of <a
326 
+    href="<page projects/torbutton>">Torbutton</a>.</dd>
327 
+    <dt>Aaron Turner</dt><dd> Contributed the first version of the tor.sh
328 
+    initscripts shell script.</dd>
329 
+    <dt>Stephen Tyree</dt><dd> Worked during Google Summer of Code 2009 to
330 
+    develop a plugin API for <a href="<page projects/vidalia>">Vidalia</a>
331 
+    and create a plugin to allow HerdictWeb integration, a project aiming
332 
+    at identifying website inaccessibility using user submissions.</dd>
333 
+    <dt>Camilo Viecco</dt><dd> Worked on
334 
+    Providing Blossom functionality to Vidalia (<a
335 
+    href="http://trac.vidalia-project.net/browser/vidalia/branches/exit-country">svn</a>) as part of Google Summer of Code 2008.</dd>
336 
+    <dt>Fred von Lohmann</dt><dd>Fred served on our Board of Directors
337 
+    from 2006 through 2009.   His complete bio can be found at the <a
338 
+    href="http://www.eff.org/about/staff/?f=fred_von_lohmann.html">EFF
339 
+    Staff Site</a>.</dd>
340 
+    <dt>Christian Wilms</dt><dd> Worked on
341 
+    Performance Enhancing Measures for Tor Hidden Services (<a
342 
+    href="https://svn.torproject.org/cgi-bin/viewcvs.cgi/tor/branches/hidserv-perf/">svn</a>) as part of Google Summer of Code 2008.</dd>
343 
+    <dt>Jillian C. York</dt><dd><a href="http://jilliancyork.com/">Jillian
344 
+    C. York</a> is a writer, blogger, and activist based in
345 
+    Boston.  She blogs on the uses of Tor and anonymity at <a
346 
+    href="http://www.knightpulse.org/blog/tor">KnightPulse</a>.</dd>
347 
+    </dl>
348 
+  </div>
349 
+  <!-- END MAINCOL -->
350 
+  <div id = "sidecol">
351 
+#include "side.wmi"
352 
+#include "info.wmi"
353 
+  </div>
354 
+  <!-- END SIDECOL -->
355 
+</div>
356 
+<!-- END CONTENT -->
357 
+#include <foot.wmi>
about/en/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,63 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'about/about',
21 
+       'txt'  => 'Tor Overview',
22 
+       'subelements' => [
23 
+          {'url'  => 'about/why',
24 
+           'txt'  => 'Why We Need Tor',
25 
+          },
26 
+          {'url'  => 'about/staying',
27 
+           'txt'  => 'Staying Anonymous',
28 
+          },
29 
+          {'url'  => 'about/future',
30 
+           'txt'  => 'Future of Tor',
31 
+          }]
32 
+      },
33 
+      {'url'  => 'about/torusers',
34 
+       'txt'  => 'Users of Tor',
35 
+      },
36 
+
37 
+      {'url'  => 'about/corepeople',
38 
+       'txt'  => 'Tor People',
39 
+       'subelements' => [
40 
+          {'url'  => 'about/board',
41 
+           'txt'  => 'Board of Directors',
42 
+          },
43 
+          {'url'  => 'about/translators',
44 
+           'txt'  => 'Translators',
45 
+          },
46 
+          {'url'  => 'about/volunteers',
47 
+           'txt'  => 'Volunteers',
48 
+          },
49 
+          {'url'  => 'about/contributors',
50 
+           'txt'  => 'Past Contributors',
51 
+          }]
52 
+      },
53 
+      {'url'  => 'about/sponsors',
54 
+       'txt'  => 'Sponsors',
55 
+      },
56 
+      {'url'  => 'projects/clientside',
57 
+       'txt'  => 'Projects',
58 
+      },
59 
+      {'url'  => 'docs/faq',
60 
+       'txt'  => 'FAQ',
61 
+      },
62 
+  ];
63 
+:>
about/en/sponsors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,82 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22225 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Sponsors" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/sponsors>">Sponsors</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor: Sponsors</h1>
14 
+    <p>
15 
+    The Tor Project's <a href="<page about/torusers>">diversity of users</a> means we
16 
+    have a diversity of funding sources too &mdash; and we're eager to diversify
17 
+    even further! Our sponsorships are divided into levels based on total funding received:
18 
+    </p>
19 
+
20 
+    <h3><i>Magnoliophyta</i> (over $1 million)</h3>
21 
+    	<ul>
22 
+    		<li>You?</li>
23 
+    	</ul>
24 
+
25 
+    <h3><i>Liliopsida</i> (up to $750k)</h3>
26 
+    	<ul>
27 
+    		<li>An anonymous North American NGO (2008-2010)</li>
28 
+    	</ul>
29 
+
30 
+    <h3><i>Asparagales</i> (up to $500k)</h3>
31 
+    	<ul>
32 
+    		<li><a href="http://www.ibb.gov/">International Broadcasting Bureau</a> (2006-2010)</li>
33 
+    		<li>An anonymous European NGO (2006-2008)</li>
34 
+    	</ul>
35 
+
36 
+    <h3><i>Alliaceae</i> (up to $200k)</h3>
37 
+    	<ul>
38 
+    		<li>You?</li>
39 
+    	</ul>
40 
+
41 
+    <h3><i>Allium</i> (up to $100k)</h3>
42 
+    	<ul>
43 
+    		<li><a href="http://www.nlnet.nl/">NLnet Foundation</a> (2008-2009)</li>
44 
+    		<li><a href="http://chacs.nrl.navy.mil/">Naval Research Laboratory</a> (2006-2010)</li>
45 
+    		<li>An anonymous North American ISP (2009-2010)</li>
46 
+    	</ul>
47 
+
48 
+    <h3><i>Allium cepa</i> (up to $50k)</h3>
49 
+    	<ul>
50 
+    		<li><a href="<page donate/donate>">More than 500 personal donations from individuals like you</a> (2006-2010)</li>
51 
+    		<li><a href="http://code.google.com/opensource/">Google</a> (2008-2009)</li>
52 
+    		<li><a href="http://code.google.com/soc/">Google Summer of Code</a> (2007-2009)</li>
53 
+    		<li><a href="http://www.hrw.org/">Human Rights Watch</a> (2007)</li>
54 
+    		<li><a href="http://www.torfox.org/">Torfox</a> (2009)</li>
55 
+        <li><a href="http://www.shinjiru.com/">Shinjiru Technology</a> (2009-2010)</li>
56 
+      </ul>
57 
+
58 
+    <h3>Past sponsors</h3>
59 
+    <p>We greatly appreciate the support provided by our past sponsors in keeping the pre-501(c)(3) Tor Project progressing through our ambitious goals:</p>
60 
+    	<ul>
61 
+    		<li><a href="https://www.eff.org/">Electronic Frontier Foundation</a> (2004-2005)</li>
62 
+    		<li><a href="http://chacs.nrl.navy.mil/">DARPA and ONR via Naval Research Laboratory</a> (2001-2006)</li>
63 
+    		<li><a href="http://www.cyber-ta.org/">Cyber-TA project</a> (2006-2008)</li>
64 
+    		<li>Bell Security Solutions Inc (2006)</li>
65 
+    		<li><a href="http://www.omidyar.net/">Omidyar Network Enzyme Grant</a> (2006)</li>
66 
+    		<li><a href="http://seclab.cs.rice.edu/lab/2005/08/01/seclab-awarded-grant-to-study-security-of-p2p/">NSF via Rice University</a> (2006-2007)</li>
67 
+    	</ul>
68 
+    <p>Thank you to all the people and groups who have made Tor possible so
69 
+    far, and thank you especially to the individual volunteers who have made
70 
+    non-financial contributions: coding, testing, documenting, educating,
71 
+    researching, and running the relays that make up the Tor network.
72 
+    </p>
73 
+  </div>
74 
+  <!-- END MAINCOL -->
75 
+  <div id = "sidecol">
76 
+#include "side.wmi"
77 
+#include "info.wmi"
78 
+  </div>
79 
+  <!-- END SIDECOL -->
80 
+</div>
81 
+<!-- END CONTENT -->
82 
+#include <foot.wmi>
about/en/staying.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,42 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Staying Anonymous" CHARSET="UTF-8" <p>
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/staying>">Staying Anonymous</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Staying anonymous</h1>
14 
+
15 
+    <p>
16 
+    Tor can't solve all anonymity problems.  It focuses only on
17 
+    protecting the transport of data.  You need to use protocol-specific
18 
+    support software if you don't want the sites you visit to see your
19 
+    identifying information. For example, you can use web proxies such as
20 
+    Privoxy while web browsing to block cookies and withhold information
21 
+    about your browser type.
22 
+    </p>
23 
+
24 
+    <p>
25 
+    Also, to protect your anonymity, be smart.  Don't provide your name
26 
+    or other revealing information in web forms.  Be aware that, like all
27 
+    anonymizing networks that are fast enough for web browsing, Tor does not
28 
+    provide protection against end-to-end timing attacks: If your attacker
29 
+    can watch the traffic coming out of your computer, and also the traffic
30 
+    arriving at your chosen destination, he can use statistical analysis to
31 
+    discover that they are part of the same circuit.
32 
+    </p>
33 
+  </div>
34 
+  <!-- END MAINCOL -->
35 
+  <div id = "sidecol">
36 
+#include "side.wmi"
37 
+#include "info.wmi"
38 
+  </div>
39 
+  <!-- END SIDECOL -->
40 
+</div>
41 
+<!-- END CONTENT -->
42 
+#include <foot.wmi>
about/en/torusers.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,343 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22261 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Who uses Tor?" CHARSET="UTF-8"
6 
+
7 
+<div id="content" class="clearfix">
8 
+  <div id="breadcrumbs">
9 
+    <a href="<page home>">Home &raquo; </a>
10 
+    <a href="<page about/about>">About &raquo; </a>
11 
+    <a href="<page about/torusers>">Who Uses Tor</a>
12 
+  </div>
13 
+  <div id="maincol">
14 
+
15 
+    <h1>Inception</h1>
16 
+
17 
+    #<!-- BEGIN SIDEBAR -->
18 
+    #<div class="sidebar-left">
19 
+    #<h3>Who uses Tor?</h3>
20 
+    #<ul>
21 
+    #<li><a href="<page about/torusers>#normalusers">Normal people use Tor</a></li>
22 
+    #<li><a href="<page about/torusers>#military">Militaries use Tor</a></li>
23 
+    #<li><a href="<page about/torusers>#journalist">Journalists and their audience use Tor</a></li>
24 
+    #<li><a href="<page about/torusers>#lawenforcement">Law enforcement officers use Tor</a></li>
25 
+    #<li><a href="<page about/torusers>#activists">Activists &amp; Whistleblowers use Tor</a></li>
26 
+    #<li><a href="<page about/torusers>#spotlight">High &amp; low profile people use Tor</a></li>
27 
+    #<li><a href="<page about/torusers>#executives">Business executives use Tor</a></li>
28 
+    #<li><a href="<page about/torusers>#bloggers">Bloggers use Tor</a></li>
29 
+    #<li><a href="<page about/torusers>#itprofessionals">IT Professionals use Tor</a></li>
30 
+    #</ul>
31 
+    #</div>
32 
+    #<!-- END SIDEBAR -->
33 
+
34 
+    <hr />
35 
+    <p>
36 
+    Tor was originally designed, implemented, and deployed as a third-generation
37 
+    <a href="http://www.onion-router.net/">onion routing project of the Naval Research Laboratory</a>.
38 
+    It was originally developed with the U.S. Navy in mind, for the primary purpose of protecting government communications.
39 
+    Today, it is used every day for a wide variety of purposes by the military, journalists, law enforcement officers, activists, and many others. Here are some of the specific uses we've seen or recommend.
40 
+    </p>
41 
+
42 
+    <a name="normalusers"></a>
43 
+    <h2><a class="anchor" href="#normalusers">Normal people use Tor</a></h2>
44 
+    <hr />
45 
+    <ul>
46 
+    <li><strong>They protect their privacy from unscrupulous marketers and identity thieves.</strong>
47 
+    Internet Service Providers (ISPs) <a href="http://seekingalpha.com/article/29449-compete-ceo-isps-sell-clickstreams-for-5-a-month">
48 
+    sell your Internet browsing records</a> to marketers or anyone else
49 
+    willing to pay for it. ISPs typically say that
50 
+    they anonymize the data by not providing personally identifiable information, but
51 
+    <a href="http://www.wired.com/politics/security/news/2006/08/71579?currentPage=all">this
52 
+    has proven incorrect</a>.  A full record of every site you visit, the text of every search you perform, and potentially
53 
+    userid and even password information can still be part of this data.  In addition to your ISP, the websites (<a href="http://www.google.com/privacy_faq.html">and search engines</a>) you visit have their own logs, containing the same or more information.
54 
+    </li>
55 
+    <li><strong> They protect their communications from irresponsible corporations.</strong>
56 
+    All over the Internet, Tor is being recommended to people newly concerned about their privacy in the face of increasing breaches and betrayals of
57 
+    private data. From <a href="http://www.securityfocus.com/news/11048">lost backup tapes</a>, to
58 
+    <a href="http://www.nytimes.com/2006/08/09/technology/09aol.html?ex=1312776000&amp;en=f6f61949c6da4d38&amp;ei=5090">giving away the data to researchers</a>,
59 
+    your data is often not well protected by those you are supposed to trust to keep it safe.
60 
+    </li>
61 
+    <li><strong>They protect their children online.</strong>
62 
+    You've told your kids they shouldn't share personally identifying information online, but they may be sharing their location simply
63 
+    by not concealing their IP address. Increasingly, IP addresses can be <a href="http://whatismyipaddress.com/">literally mapped to a city or even street location</a>, and can <a href="http://whatsmyip.org/more/">reveal other information</a> about how you are connecting to the Internet.
64 
+    In the United States, the government is pushing to make this mapping increasingly precise.
65 
+    </li>
66 
+    <li><strong>They research sensitive topics.</strong>
67 
+    There's a wealth of information available online. But perhaps in your country, access to information on AIDS, birth control,
68 
+    <a href="http://www.cbsnews.com/stories/2002/12/03/tech/main531567.shtml">Tibetan culture</a>,
69 
+    or world religions is behind a national firewall.
70 
+    </li>
71 
+    </ul>
72 
+
73 
+    <a name="military"></a>
74 
+    <h2><a class="anchor" href="#military">Militaries use Tor</a></h2>
75 
+    <hr />
76 
+    <ul>
77 
+
78 
+    <li>
79 
+    <strong>Field Agents:</strong>
80 
+    It is not difficult for insurgents to monitor Internet traffic and
81 
+    discover all the hotels and other locations from which people are
82 
+    connecting to known military servers.
83 
+    Military field agents deployed away from home use Tor to
84 
+    mask the sites they are visiting, protecting military interests and
85 
+    operations, as well as protecting themselves from physical harm.
86 
+    </li>
87 
+
88 
+    <li><strong>Hidden services:</strong>
89 
+    When the Internet was designed by DARPA, its primary purpose was to be able to facilitate distributed, robust communications in case of
90 
+    local strikes.  However, some functions must be centralized, such as command and control sites.  It's the nature of the Internet protocols to
91 
+    reveal the geographic location of any server that is reachable online.  Tor's hidden services capacity allows military command and
92 
+    control to be physically secure from discovery and takedown.
93 
+    </li>
94 
+    <li><strong>Intelligence gathering:</strong>
95 
+    Military personnel need to use electronic resources run and monitored by insurgents. They do not want the webserver logs on an insurgent website
96 
+    to record a military address, thereby revealing the surveillance.
97 
+    </li>
98 
+    </ul>
99 
+
100 
+    <a name="journalist"></a>
101 
+    <h2><a class="anchor" href="#journalist">Journalists and their audience use Tor</a></h2>
102 
+    <hr />
103 
+    <ul>
104 
+    <li><strong><a href="http://www.rsf.org/">Reporters without Borders</a></strong>
105 
+    tracks Internet prisoners of conscience and jailed or harmed journalists all over the world. They advise
106 
+    journalists, sources, bloggers, and dissidents to use Tor to ensure their privacy and safety.
107 
+    </li>
108 
+    <li><strong>The US <a href="http://www.ibb.gov/">International Broadcasting Bureau</a></strong>
109 
+    (Voice of America/Radio Free Europe/Radio Free Asia) supports Tor development to help Internet users in countries without
110 
+    safe access to free media.  Tor preserves the ability of persons behind national firewalls or under
111 
+    the surveillance of repressive regimes to obtain a global perspective on controversial topics including democracy,
112 
+    economics and religion.
113 
+    </li>
114 
+    <li><strong>Citizen journalists in China</strong> use Tor to write about
115 
+    local events to encourage social change and political reform.
116 
+    </li>
117 
+    <li><strong>Citizens and journalists in <a
118 
+    href="http://www.rsf.org/rubrique.php3?id_rubrique=554">Internet black
119 
+    holes</a></strong> use Tor to research state propaganda and opposing
120 
+    viewpoints, to file stories with non-State controlled media, and to
121 
+    avoid risking the personal consequences of intellectual curiosity.
122 
+    </li>
123 
+    </ul>
124 
+
125 
+    <a name="lawenforcement"></a>
126 
+    <h2><a class="anchor" href="#lawenforcement">Law enforcement officers use Tor</a></h2>
127 
+    <hr />
128 
+    <ul>
129 
+    <li><strong>Online surveillance:</strong>
130 
+    Tor allows officials to surf questionable web sites and services
131 
+    without leaving tell-tale tracks.  If the system administrator of an
132 
+    illegal gambling site, for example, were to see multiple connections from
133 
+    government or law enforcement IP addresses in usage logs, investigations
134 
+    may be hampered.
135 
+    </li>
136 
+    <li><strong>Sting operations:</strong>
137 
+    Similarly, anonymity allows law officers to engage in online
138 
+    &ldquo;undercover &rdquo; operations.  Regardless of how good an
139 
+    undercover officer's &ldquo;street cred&rdquo; may be, if the
140 
+    communications include IP ranges from police addresses, the cover is blown.
141 
+    </li>
142 
+    <li><strong>Truly anonymous tip lines:</strong>
143 
+    While online anonymous tip lines are popular, without anonymity
144 
+    software, they are far less useful.  Sophisticated sources understand that
145 
+    although a name or email address is not attached to information, server
146 
+    logs can identify them very quickly.  As a result, tip line web sites that
147 
+    do not encourage anonymity are limiting the sources of their tips.
148 
+    </li>
149 
+    </ul>
150 
+
151 
+    <a name="activists"></a>
152 
+    <h2><a class="anchor" href="#activists">Activists &amp; Whistleblowers use Tor</a></h2>
153 
+    <hr />
154 
+    <ul>
155 
+    <li><strong>Human rights activists use Tor to anonymously report abuses from
156 
+    danger zones.</strong>  Internationally, labor rights workers use Tor and other
157 
+    forms of online and offline anonymity to organize workers in accordance
158 
+    with the Universal Declaration of Human Rights. Even though they are within
159 
+    the law, it does not mean they are safe. Tor provides the ability to
160 
+    avoid persecution while still raising a voice.
161 
+    </li>
162 
+    <li>When groups such as the <strong>Friends Service Committee and environmental
163 
+    groups are increasingly <a href="http://www.afsc.org/news/2005/government-spying.htm">falling under surveillance</a>
164 
+    in the United States</strong> under laws meant to protect against terrorism, many peaceful agents of
165 
+    change rely on Tor for basic privacy during legitimate activities.
166 
+    </li>
167 
+    <li><strong><a href="http://hrw.org/doc/?t=internet">Human Rights Watch</a></strong>
168 
+    recommends Tor in their report, &ldquo;
169 
+    <a href="http://www.hrw.org/reports/2006/china0806/">Race to the Bottom: Corporate
170 
+    Complicity in Chinese Internet Censorship</a>.&rdquo; The study
171 
+    co-author interviewed Roger Dingledine, Tor project leader,
172 
+    on Tor use.  They cover Tor in the section on how to breach the <a
173 
+    href="http://www.hrw.org/reports/2006/china0806/3.htm#_Toc142395820">&ldquo;Great
174 
+    Firewall of China,&rdquo;</a> and recommend that human rights workers throughout
175 
+    the globe use Tor for &ldquo;secure browsing and communications.&rdquo;
176 
+    </li>
177 
+    <li> Tor has consulted with and volunteered help to <strong>Amnesty International's
178 
+    recent <a href="http://irrepressible.info/">corporate responsibility campaign</a></strong>.
179 
+    See also their <a href="http://irrepressible.info/static/pdf/FOE-in-china-2006-lores.pdf">full
180 
+    report</a> on China Internet issues.
181 
+    </li>
182 
+    <li><a href="http://www.globalvoicesonline.org">Global Voices</a>
183 
+    recommends Tor, especially for <strong>anonymous blogging</strong>,
184 
+    throughout their <a href="http://advocacy.globalvoicesonline.org/projects/guide/">
185 
+    web site.</a>
186 
+    </li>
187 
+    <li>In the US, the Supreme Court recently stripped legal protections from
188 
+    government whistleblowers.  But whistleblowers working for governmental
189 
+    transparency or corporate accountability can use Tor to seek justice
190 
+    without personal repercussions.
191 
+    </li>
192 
+    <li>A contact of ours who works with a public health nonprofit in
193 
+    Africa reports that his nonprofit <strong>must budget 10% to cover various sorts of corruption</strong>,
194 
+    mostly bribes and such.  When that percentage rises steeply, not only can they not afford the money, but they can
195 
+    not afford to complain &mdash; this is the point at which open objection can
196 
+    become dangerous.  So his nonprofit has been working to
197 
+    <strong>use Tor to safely whistleblow on government corruption</strong> in order to continue their work.
198 
+    </li>
199 
+    <li>At a recent conference, a Tor staffer ran into a woman who came from
200 
+    a &ldquo;company town&rdquo; in the eastern United States. She was attempting to blog anonymously to rally
201 
+    local residents to <strong>urge reform in the company</strong> that dominated the town's
202 
+    economic and government affairs. She is fully cognizant that the kind of
203 
+    organizing she was doing <strong>could lead to harm or &ldquo;fatal
204 
+    accidents.&rdquo;</strong>
205 
+    </li>
206 
+    <li>In east Asia, some labor organizers use anonymity to <strong>reveal information
207 
+    regarding sweatshops</strong> that produce goods for western countries and to
208 
+    organize local labor.
209 
+    </li>
210 
+    <li>
211 
+    Tor can help activists avoid government or corporate censorship that hinders organization.
212 
+    In one such case, a
213 
+    <a href="http://www.cbc.ca/canada/story/2005/07/24/telus-sites050724.html">Canadian ISP blocked access to a union website used by their own employees</a>
214 
+    to help organize a strike.
215 
+    </li>
216 
+    </ul>
217 
+
218 
+    <a name="spotlight"></a>
219 
+    <h2><a class="anchor" href="#spotlight">High &amp; low profile people use Tor</a></h2>
220 
+    <hr />
221 
+    <ul>
222 
+    <li>Does being in the public spotlight shut you off from having a private
223 
+    life, forever, online?  A rural lawyer in a New England state keeps
224 
+    an anonymous blog because, with the diverse clientele at his prestigious
225 
+    law firm, <strong>his political beliefs are bound to offend someone</strong>.  Yet, he
226 
+    doesn't want to remain silent on issues he cares about.  Tor helps him
227 
+    feel secure that he can express his opinion without consequences to his
228 
+    public role.
229 
+    </li>
230 
+    <li>People living in poverty often don't participate fully in civil society
231 
+    -- not out of ignorance or apathy, but out of fear.  If something you
232 
+    write were to get back to your boss, would you lose your job?  If your
233 
+    social worker read about your opinion of the system, would she treat
234 
+    you differently?  Anonymity gives a voice to the voiceless.
235 
+    To support this, <strong>Tor currently has an open Americorps/VISTA position</strong> pending.  This
236 
+    government grant will cover a full time stipend for a volunteer to create
237 
+    curricula to <strong>show low-income populations how to use anonymity online for
238 
+    safer civic engagement</strong>.  Although it's often said that the poor do not use
239 
+    online access for civic engagement, failing to act in their self-interests,
240 
+    it is our hypothesis (based on personal conversations and anecdotal
241 
+    information) that it is precisely the &ldquo;permanent record &rdquo;
242 
+    left online that keeps many of the poor from speaking out on the Internet.
243 
+    We hope to show people how to engage more safely online, and then at
244 
+    the end of the year, evaluate how online and offline civic engagement has
245 
+    changed, and how the population sees this continuing into the future.
246 
+    </li>
247 
+    </ul>
248 
+
249 
+    <a name="executives"></a>
250 
+    <h2><a class="anchor" href="#executives">Business executives use Tor</a></h2>
251 
+    <hr />
252 
+    <ul>
253 
+    <li><strong>Security breach information clearinghouses:</strong>
254 
+    Say a financial institution participates in a security clearinghouse
255 
+    of information on Internet attacks.  Such a repository requires members
256 
+    to report breaches to a central group, who correlates attacks to detect
257 
+    coordinated patterns and send out alerts.  But if a specific bank in St. Louis is breached, they don't want an attacker watching the incoming
258 
+    traffic to such a repository to be able to track where information is
259 
+    coming from.  Even though every packet were encrypted, the IP
260 
+    address would betray the location of a compromised system.  Tor allows
261 
+    such repositories of sensitive information to resist compromises.
262 
+    </li>
263 
+    <li><strong>Seeing your competition as your market does:</strong>
264 
+    If you try to check out a competitor's pricing, you may find no
265 
+    information or misleading information on their web site.  This is because
266 
+    their web server may be keyed to detect connections from competitors,
267 
+    and block or spread disinformation to your staff.  Tor allows a business
268 
+    to view their sector as the general public would view it.
269 
+    </li>
270 
+    <li><strong>Keeping strategies confidential:</strong>
271 
+    An investment bank, for example, might not want industry snoopers to be
272 
+    able to track what web sites their analysts are watching.  The strategic
273 
+    importance of traffic patterns, and the vulnerability of the surveillance
274 
+    of such data, is starting to be more widely recognized in several areas
275 
+    of the business world.
276 
+    </li>
277 
+    <li><strong>Accountability:</strong>
278 
+    In an age when irresponsible and unreported corporate activity has
279 
+    undermined multi-billion dollar businesses, an executive exercising true
280 
+    stewardship wants the whole staff to feel free to disclose internal
281 
+    malfeasance.  Tor facilitates internal accountability before it turns
282 
+    into whistleblowing.
283 
+    </li>
284 
+    </ul>
285 
+
286 
+    <a name="bloggers"></a>
287 
+    <h2><a class="anchor" href="#bloggers">Bloggers use Tor</a></h2>
288 
+    <hr />
289 
+    <ul>
290 
+    <li>Frequently we hear about bloggers who are
291 
+    <a href="http://online.wsj.com/public/article/SB112541909221726743-Kl4kLxv0wSbjqrkXg_DieY3c8lg_20050930.html">sued</a> or
292 
+    <a href="http://www.usatoday.com/money/workplace/2005-06-14-worker-blogs-usat_x.htm">fired</a>
293 
+    for saying perfectly legal things online, in their blog.</li>
294 
+    <li>We recommend the <a href="http://www.eff.org/issues/bloggers/legal">EFF Legal Guide for Bloggers</a>.</li>
295 
+    <li>Global Voices maintains a <a href="http://advocacy.globalvoicesonline.org/projects/guide/">guide to anonymous blogging with Wordpress and Tor</a>.</li>
296 
+    </ul>
297 
+
298 
+    <a name="itprofessionals"></a>
299 
+    <h2><a class="anchor" href="#itprofessionals">IT Professionals use Tor</a></h2>
300 
+    <hr />
301 
+    <ul>
302 
+    <li>To verify IP based firewall rules: A firewall may have some policies that only allow certain IP addresses or ranges. Tor can be used to verify those configurations by using an IP number outside of the company's alloted IP block.</li>
303 
+    <li>To bypass their own security systems for sensitive professional activities: For instance, a company may have a strict policy regarding the material employees can view on the internet. A log review reveals a possible violation. Tor can be used to verify the information without an exception being put into corporate security systems.</li>
304 
+    <li>To connect back to deployed services: A network engineer can use Tor to remotely connect back to services, without the need for an external machine and user account, as part of operational testing.</li>
305 
+    <li>To access internet resources: Acceptable use policy for IT Staff and normal employees is usually different. Tor can allow unfettered access to the internet while leaving standard security policies in place.</li>
306 
+    <li>To work around ISP network outages: Sometimes when an ISP is having routing or DNS problems, Tor can make internet resources available, when the actual ISP is malfunctioning. This can be invaluable is crisis situations. </li>
307 
+    </ul>
308 
+
309 
+    <p>
310 
+    Please do send us your success stories. They are very important because
311 
+    Tor provides anonymity. While it is thrilling to speculate about <a
312 
+    href="<page docs/faq-abuse>">undesired effects of Tor</a>, when it succeeds, nobody notices.  This is
313 
+    great for users, but not so good for us, since publishing success
314 
+    stories about how people or organizations are staying anonymous could be
315 
+    counterproductive.  For example, we talked to an FBI officer who
316 
+    explained that he uses Tor every day for his work &mdash; but he quickly followed up with a request not to provide
317 
+    details or mention his name.</p>
318 
+
319 
+    <p> Like any technology, from pencils to cellphones, anonymity can be used for both good and bad.  You have probably seen some of the vigorous
320 
+    debate (<a href="http://www.wired.com/politics/security/commentary/securitymatters/2006/01/70000">pro</a>,
321 
+    <a href="http://www.edge.org/q2006/q06_4.html#kelly">con</a>, and <a
322 
+    href="http://web.mit.edu/gtmarx/www/anon.html">academic</a>) over anonymity. The Tor project is based on the belief that anonymity is not
323 
+    just a good idea some of the time - it is a requirement for a free and functioning society.  The <a href="http://www.eff.org/issues/anonymity">EFF maintains a good overview</a> of how anonymity was crucial to the founding of the United States.  Anonymity is recognized by US courts as a fundamental and important right. In fact, governments mandate anonymity in many cases themselves:
324 
+    <a href="https://www.crimeline.co.za/default.asp">police tip lines</a>,
325 
+    <a href="http://www.texasbar.com/Content/ContentGroups/Public_Information1/Legal_Resources_Consumer_Information/Family_Law1/Adoption_Options.htm#sect2">adoption services</a>,
326 
+    <a href="http://writ.news.findlaw.com/aronson/20020827.html">police officer identities</a>,
327 
+    and so forth. It would be impossible to rehash the entire anonymity debate here - it is too large an issue with too many nuances, and there
328 
+    are plenty of other places where this information can be found. We do have a <a href="<page docs/faq-abuse>">Tor abuse</a> page describing some of
329 
+    the possible abuse cases for Tor, but suffice it to say that if you want to abuse the system, you'll either find it mostly closed for your
330 
+    purposes (e.g. the majority of Tor relays do not support SMTP in order to prevent anonymous email spamming), or if you're one of the
331 
+    <a href="http://www.schneier.com/blog/archives/2005/12/computer_crime_1.html">Four Horsemen of the Information Apocalypse</a>,
332 
+    you have better options than Tor. While not dismissing the potential abuses of Tor,
333 
+    this page shows a few of the many important ways anonymity is used online today.</p>
334 
+  </div>
335 
+  <!-- END MAINCOL -->
336 
+  <div id = "sidecol">
337 
+#include "side.wmi"
338 
+#include "info.wmi"
339 
+  </div>
340 
+  <!-- END SIDECOL -->
341 
+</div>
342 
+<!-- END CONTENT -->
343 
+#include <foot.wmi>
about/en/translators.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,74 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Translators" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/volunteers>">Translators</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+  	<h1>Translators</h1>
14 
+    <table>
15 
+    	<tr>
16 
+        <td class="beige">
17 
+          <div class="name">Translator Name</div>
18 
+          <div class="caps">Translator Title</div>
19 
+          <p>Translator is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
20 
+        </td>
21 
+        <td>
22 
+          <div class="name">Translator Name</div>
23 
+          <div class="caps">Translator Title</div>
24 
+          <p>Translator is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
25 
+        </td>
26 
+      </tr>
27 
+      <tr>
28 
+        <td>
29 
+          <div class="name">Translator Name</div>
30 
+          <div class="caps">Translator Title</div>
31 
+          <p>Translator is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
32 
+        </td>
33 
+        <td class="beige">
34 
+          <div class="name">Translator Name</div>
35 
+          <div class="caps">Translator Title</div>
36 
+          <p>Translator is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
37 
+        </td>
38 
+      </tr>
39 
+      <tr>
40 
+        <td class="beige">
41 
+          <div class="name">Translator Name</div>
42 
+          <div class="caps">Translator Title</div>
43 
+          <p>Translator is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
44 
+        </td>
45 
+        <td>
46 
+          <div class="name">Translator Name</div>
47 
+          <div class="caps">Translator Title</div>
48 
+          <p>Translator is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
49 
+        </td>
50 
+      </tr>
51 
+      <tr>
52 
+        <td>
53 
+          <div class="name">Translator Name</div>
54 
+          <div class="caps">Translator Title</div>
55 
+          <p>Translator is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
56 
+        </td>
57 
+        <td class="beige">
58 
+          <div class="name">Translator Name</div>
59 
+          <div class="caps">Translator Title</div>
60 
+          <p>Translator is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
61 
+        </td>
62 
+      </tr>
63 
+    </table>
64 
+    <!-- END TABLE -->
65 
+  </div>
66 
+  <!-- END MAINCOL -->
67 
+  <div id = "sidecol">
68 
+#include "side.wmi"
69 
+#include "info.wmi"
70 
+  </div>
71 
+  <!-- END SIDECOL -->
72 
+</div>
73 
+<!-- END CONTENT -->
74 
+#include <foot.wmi>
about/en/volunteers.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,74 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+#include "head.wmi" TITLE="Tor Project: Volunteers" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/volunteers>">Volunteers</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+  	<h1>Volunteers</h1>
14 
+    <table>
15 
+    	<tr>
16 
+        <td class="beige">
17 
+          <div class="name">Volunteer Name</div>
18 
+          <div class="caps">Volunteer Title</div>
19 
+          <p>Volunteer is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
20 
+        </td>
21 
+        <td>
22 
+          <div class="name">Volunteer Name</div>
23 
+          <div class="caps">Volunteer Title</div>
24 
+          <p>Volunteer is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
25 
+        </td>
26 
+      </tr>
27 
+      <tr>
28 
+        <td>
29 
+          <div class="name">Volunteer Name</div>
30 
+          <div class="caps">Volunteer Title</div>
31 
+          <p>Volunteer is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
32 
+        </td>
33 
+        <td class="beige">
34 
+          <div class="name">Volunteer Name</div>
35 
+          <div class="caps">Volunteer Title</div>
36 
+          <p>Volunteer is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
37 
+        </td>
38 
+      </tr>
39 
+      <tr>
40 
+        <td class="beige">
41 
+          <div class="name">Volunteer Name</div>
42 
+          <div class="caps">Volunteer Title</div>
43 
+          <p>Volunteer is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
44 
+        </td>
45 
+        <td>
46 
+          <div class="name">Volunteer Name</div>
47 
+          <div class="caps">Volunteer Title</div>
48 
+          <p>Volunteer is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
49 
+        </td>
50 
+      </tr>
51 
+      <tr>
52 
+        <td>
53 
+          <div class="name">Volunteer Name</div>
54 
+          <div class="caps">Volunteer Title</div>
55 
+          <p>Volunteer is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
56 
+        </td>
57 
+        <td class="beige">
58 
+          <div class="name">Volunteer Name</div>
59 
+          <div class="caps">Volunteer Title</div>
60 
+          <p>Volunteer is tackling the growing needs for easy to configure packages on many operating systems. She’s also automating the build system and producing nightly builds for all operating systems we support.</p>
61 
+        </td>
62 
+      </tr>
63 
+    </table>
64 
+    <!-- END TABLE -->
65 
+  </div>
66 
+  <!-- END MAINCOL -->
67 
+  <div id = "sidecol">
68 
+#include "side.wmi"
69 
+#include "info.wmi"
70 
+  </div>
71 
+  <!-- END SIDECOL -->
72 
+</div>
73 
+<!-- END CONTENT -->
74 
+#include <foot.wmi>
about/en/why.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,66 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Why We Need Tor" CHARSET="UTF-8" <p>
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page about/about>">About &raquo; </a>
10 
+    <a href="<page about/why>">Why We Need Tor</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Why We Need Tor</h1>
14 
+
15 
+    <p>
16 
+    Using Tor protects you against a common form of Internet surveillance
17 
+    known as "traffic analysis."  Traffic analysis can be used to infer
18 
+    who is talking to whom over a public network.  Knowing the source
19 
+    and destination of your Internet traffic allows others to track your
20 
+    behavior and interests.  This can impact your checkbook if, for example,
21 
+    an e-commerce site uses price discrimination based on your country or
22 
+    institution of origin.  It can even threaten your job and physical safety
23 
+    by revealing who and where you are. For example, if you're travelling
24 
+    abroad and you connect to your employer's computers to check or send mail,
25 
+    you can inadvertently reveal your national origin and professional
26 
+    affiliation to anyone observing the network, even if the connection
27 
+    is encrypted.
28 
+    </p>
29 
+
30 
+    <p>
31 
+    How does traffic analysis work?  Internet data packets have two parts:
32 
+    a data payload and a header used for routing.  The data payload is
33 
+    whatever is being sent, whether that's an email message, a web page, or an
34 
+    audio file.  Even if you encrypt the data payload of your communications,
35 
+    traffic analysis still reveals a great deal about what you're doing and,
36 
+    possibly, what you're saying.  That's because it focuses on the header,
37 
+    which discloses source, destination, size, timing, and so on.
38 
+    </p>
39 
+
40 
+    <p>
41 
+    A basic problem for the privacy minded is that the recipient of your
42 
+    communications can see that you sent it by looking at headers.  So can
43 
+    authorized intermediaries like Internet service providers, and sometimes
44 
+    unauthorized intermediaries as well.  A very simple form of traffic
45 
+    analysis might involve sitting somewhere between sender and recipient on
46 
+    the network, looking at headers.
47 
+    </p>
48 
+
49 
+    <p>
50 
+    But there are also more powerful kinds of traffic analysis.  Some
51 
+    attackers spy on multiple parts of the Internet and use sophisticated
52 
+    statistical techniques to track the communications patterns of many
53 
+    different organizations and individuals.  Encryption does not help against
54 
+    these attackers, since it only hides the content of Internet traffic, not
55 
+    the headers.
56 
+    </p>
57 
+  </div>
58 
+  <!-- END MAINCOL -->
59 
+  <div id = "sidecol">
60 
+#include "side.wmi"
61 
+#include "info.wmi"
62 
+  </div>
63 
+  <!-- END SIDECOL -->
64 
+</div>
65 
+<!-- END CONTENT -->
66 
+#include <foot.wmi>
ar/foot.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,109 @@
1 
+#!/usr/bin/env wml
2 
+    <div id="footer">
3 
+    	<div class="onion"><img src="$(IMGROOT)/onion.jpg" alt="Tor" /></div>
4 
+      <div class="about">
5 
+      	<p>"Tor" and the "Onion Logo" are registered trademarks of <a href="#">The Tor Project, Inc.</a> Content on this site is licensed under a <a href="#">Creative Commons Attribution 3.0 United States License</a>, unless otherwise noted.</p>
6 
+        <p> Last modified: Thu Mar 4 07:48:04 2010
7 
+        # This will grab the date from svn info but formatting is tedious
8 
+        #<:{
9 
+        #  my $svninfo = `svn info`;
10 
+        #  if ($svninfo =~ m/Last Changed Date: (\d{4}-\d{2}-\d{2})\s(\d{2}:\d{2}:\d{2})\s(.*)\s\((.*)\)/) {
11 
+        #    my $modifydate = "$4 $2";
12 
+        #    # remove commas from date
13 
+        #    $modifydate =~ s/,//;
14 
+        #    print 'Last modified: '.$modifydate."\n";
15 
+        #  }
16 
+        #}:>
17 
+        <br />
18 
+        <:{
19 
+          my $compiledate = `date`;
20 
+          print 'Last compiled: '.$compiledate."\n";
21 
+        }:>
22 
+        </p>
23 
+      </div>
24 
+      <!-- END ABOUT -->
25 
+			<div class="newsletter">
26 
+				<form action="">
27 
+        	<input class="textfield" type="text" name="email" value="Sign up for our newsletter! Enter email." />
28 
+          <input class="signup" type="submit" name="submit" value="Sign Up" />
29 
+        </form>
30 
+      </div>
31 
+			<!-- END NEWSLETTER -->
32 
+      <div class="col first">
33 
+      	<h4>About Tor</h4>
34 
+        <ul>
35 
+          <li><a href="<page about/about>">What Tor Does</a></li>
36 
+          <li><a href="<page about/torusers>">Users of Tor</a></li>
37 
+          <li><a href="<page about/corepeople>">Core Tor People</a></li>
38 
+          <li><a href="<page about/sponsors>">Sponsors</a></li>
39 
+          <li><a href="<page about/contact>">Contact Us</a></li>
40 
+        </ul>
41 
+      </div>
42 
+      <!-- END COL -->
43 
+      <div class="col">
44 
+      	<h4>Get Involved</h4>
45 
+        <ul>
46 
+          <li><a href="<page donate/donate>">Donate</a></li>
47 
+          <li><a href="<page getinvolved/getinvolved>">Mailing List</a></li>
48 
+          <li><a href="#">Relays</a></li>
49 
+          <li><a href="<page docs/running-a-mirror>">Mirrors</a></li>
50 
+          <li><a href="<page docs/hidden-services>">Hidden Services</a></li>
51 
+          <li><a href="<page getinvolved/translation>">Translations</a></li>
52 
+          <li><a href="<page getinvolved/open-positions>">Careers</a></li>
53 
+        </ul>
54 
+      </div>
55 
+      <!-- END COL -->
56 
+      <div class="col">
57 
+      	<h4>Documentation</h4>
58 
+        <ul>
59 
+          <li><a href="<page docs/tor-manual>">Manuals</a></li>
60 
+          <li><a href="<page docs/documentation>">Installation Guides</a></li>
61 
+          <li><a href="<page docs/glossary>">Glossary</a></li>
62 
+          <li><a href="http://wiki.torproject.org">Tor Wiki</a></li>
63 
+          <li><a href="<page docs/faq>">FAQ</a></li>
64 
+        </ul>
65 
+      </div>
66 
+      <!-- END COL -->
67 
+      <div class="col wider">
68 
+      	<h4>Languages</h4>
69 
+        # this is a cgi trampoline to bounce us to the right page
70 
+        # alternately, if the client supports javascript we can redirect that way
71 
+        # noscript does not block onclick but clients may have disabled javascript completely
72 
+        #
73 
+        # for this to work we need to know the relative path from the document root
74 
+        # to the current directory that wml is in.
75 
+				<form action="$(DOCROOT)/cgi-bin/languageswitch.cgi">
76 
+          <select name="Language" id="lang">
77 
+          <:{
78 
+            #import "perl-globals.wmi";
79 
+            use Cwd;
80 
+            use Cwd 'abs_path';
81 
+            use File::Spec;
82 
+            my $urlbase = File::Spec->abs2rel(getcwd(),abs_path("$(DOCROOT)"));
83 
+            my $LANGUAGES;
84 
+            my $page = $WML_SRC_FILENAME;
85 
+            opendir(DIR, getcwd()) or die $!;
86 
+            # take a look and see what language support we have
87 
+            while (my $file = readdir(DIR)) {
88 
+                if (-d $file) {
89 
+                    if (-e "$file/$page") {
90 
+                        my $url = $urlbase.'/'.$WML_SRC_BASENAME.'.html.'.$file;
91 
+                        my $url2js = $WML_SRC_BASENAME.'.html.'.$file;
92 
+                        print '<option value="'.$url.'" onclick="window.location=\''.$url2js.'\'">'.$LANGUAGES{$file}.'</option>'."\n" unless not defined $LANGUAGES{$file};
93 
+                    }
94 
+                }
95 
+            }
96 
+            closedir(DIR);
97 
+          }:>
98 
+          </select>
99 
+          <input class="go" type="submit" name="submit" value="Go" />
100 
+        </form>
101 
+        <p>Questions on this? Visit <a href="http://www.debian.org/intro/cn#howtoset">how to set the default document language</a>.</p>
102 
+      </div>
103 
+    </div>
104 
+    <!-- END FOOTER -->
105 
+
106 
+  </div>
107 
+  <!-- END WRAP -->
108 
+</body>
109 
+</html>
bms/navigation.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,39 @@
1 
+#!/usr/bin/wml
2 
+
3 
+## translation metadata
4 
+# Revision: $Revision: 22069 $
5 
+# Translation-Priority: 1-high
6 
+
7 
+#<:
8 
+#   my @navigation = (
9 
+#       'index'         , 'Home',
10 
+#       'overview'      , 'Overview',
11 
+#       'easy-download'     , 'Download',
12 
+#       'documentation'     , 'Docs',
13 
+#       'volunteer'     , 'Volunteer',
14 
+#       'people'        , 'People',
15 
+#       'https://blog.torproject.org/', 'Blog',
16 
+#       'donate'        , 'Donate!',
17 
+#        'http://printfection.com/torprojectstore', 'Store',
18 
+#   );
19 
+#:>
20 
+
21 
+# order-of-appearance matters
22 
+<:
23 
+  # path          tag
24 
+    my @navigation = (
25 
+        'home'                        , 'Home',
26 
+        'about/about'                 , 'About Tor',
27 
+        'docs/documentation'          , 'Documentation',
28 
+        'projects/projects'           , 'Projects',
29 
+        'press/press'                 , 'Press',
30 
+        'https://blog.torproject.org' , 'Blog',
31 
+        'http://store.torproject.org' , 'Store',
32 
+    );
33 
+    my @calltoaction = (
34 
+        'download/download'                , 'Download',
35 
+        'donate/donate'               , 'Donate',
36 
+        'getinvolved/getinvolved'          , 'Get Involved',
37 
+    );
38 
+
39 
+:>
bms/overview.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,292 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22308 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor: Overview" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<a name="overview"></a>
14 
+<h2><a class="anchor" href="#overview">Tor :  ျခံဳငံုသံုးသပ္ခ်က္</a></h2>
15 
+
16 
+<!-- BEGIN SIDEBAR -->
17 
+<div class="sidebar-left">
18 
+<h3>အေၾကာင္းအရာမ်ား</h3>
19 
+<ul>
20 
+<li><a href="<page overview>#overview">ျခံဳငံုသံုးသပ္ခ်က္</a></li>
21 
+<li><a href="<page overview>#whyweneedtor">ကၽြႏု္ပ္တို႕ Tor ကို
22 
+ဘာေၾကာင့္လိုသလဲ</a></li>
23 
+<li><a href="<page overview>#thesolution">ေျဖရွင္းမႈ</a></li>
24 
+<li><a href="<page overview>#hiddenservices">ကြယ္ဝွယ္ထားေသာ ဝန္ေဆာင္မႈမ်ား</a></li>
25 
+<li><a href="<page overview>#stayinganonymous">အမည္ဝွက္ ေနထုိင္မႈ</a></li>
26 
+<li><a href="<page overview>#thefutureoftor">Tor ၏ အနာဂါတ္</a></li>
27 
+</ul>
28 
+</div>
29 
+
30 
+
31 
+<!-- END SIDEBAR -->
32 
+<hr />
33 
+
34 
+<p>
35 
+Tor သည္ လိုဏ္ေခါင္းေယာင္ကြန္ယက္တစ္ခုျဖစ္ျပီး လူအမ်ားႏွင့္ အုပ္စုမ်ားကုိ
36 
+၎တို႕၏ ကိုယ္ေရးအခ်က္အလက္သီးသန္႕တည္ရွိမႈႏွင့္ လံုျခံဳေရးမ်ား တုိးျမင့္ေစရန္
37 
+လမ္းဖြင့္ေပးပါသည္။ ေဆာ့ဝဲတီထြင္ထုတ္လုပ္သူမ်ားကိုလည္း အသင့္ထည့္သြင္းျပီး
38 
+ကုိယ္ေရးအခ်က္အလက္ လကၡဏာမ်ားပါဝင္ေသာ ဆက္သြယ္ေရး ကိရိယာေဆာ့ဝဲမ်ား အသစ္
39 
+ဖန္တီးရန္ ကူညီေပးပါသည္။ Tor သည္ အဖဲြ႕အစည္းမ်ားႏွင့္ တစ္ဦးခ်င္းစီအတြက္
40 
+၎တုိ႕၏ ကုိယ္ေရးအခ်က္အလက္မ်ားကို မထိခုိက္ေစဘဲ အမ်ားသံုးကြန္ယက္တြင္
41 
+သတင္းအခ်က္အလက္မ်ားကို မွ်ေဝႏုိင္ေသာ အသံုးခ်ပရုိဂရမ္မ်ားအတြက္ အေျခခံအျဖစ္
42 
+ေဆာင္ရြက္ေပးပါသည္။
43 
+</p>
44 
+
45 
+<p>
46 
+Individuals use Tor to keep websites from tracking them and their family
47 
+members, or to connect to news sites, instant messaging services, or the
48 
+like when these are blocked by their local Internet providers.  Tor's <a
49 
+href="<page hidden-services>">hidden services</a> let users publish web
50 
+sites and other services without needing to reveal the location of the
51 
+site. Individuals also use Tor for socially sensitive communication: chat
52 
+rooms and web forums for rape and abuse survivors, or people with illnesses.
53 
+</p>
54 
+
55 
+<p>
56 
+ဂ်ာနယ္လစ္မ်ားသည္ Tor ကို မေကာင္းမႈျပဳသူမ်ားကို ဖြင့္ခ်သူမ်ားႏွင့္
57 
+အစိုးရႏွင့္ သေဘာကဲြလဲြသူမ်ားကို ပိုမိုလံုျခံဳစြာ ဆက္သြယ္ရန္ အသံုးျပဳၾကပါသည္။
58 
+အစိုးရမဟုတ္ေသာ အဖဲြ႕အစည္းမ်ား (NGOs) မ်ားအေနျဖင့္ Tor ကုိ ၎တို႕၏
59 
+အလုပ္သမားမ်ားသည္ အတူအလုပ္လုပ္ေနေသာ အဖဲြ႕အစည္းအနီးရွိ အျခားသူမ်ား မသိရွိေစဘဲ
60 
+၎တို႕၏ မူလဝက္ဆိုက္မ်ားကို ဆက္သြယ္ႏုိင္ေစရန္ အသံုးျပဳၾကပါသည္။
61 
+</p>
62 
+
63 
+<p>
64 
+Indymedia ကဲ့သုိ႕ အုပ္စုမ်ားသည္ ၎တို႕၏ အသင္းဝင္မ်ား၏ ကုိယ္ေရးအခ်က္အလက္ႏွင့္
65 
+လံုျခံဳမႈမ်ားကုိ လံုျခံဳစြာ ထိန္းသိမ္းႏုိင္ရန္ Tor ကို
66 
+အၾကံျပဳေထာက္ခံၾကပါသည္။ Electronic Frontier Foundation (EFF) ကဲ့သို႕
67 
+လႈပ္ရွားသူ အုပ္စုမ်ားသည္ Tor ကို ျမိဳ႕ျပအြန္လိုင္းလြပ္လပ္မႈကို ထိန္းသိမ္းရန္
68 
+ယႏၱရားအျဖစ္ အၾကံျပဳေထာက္ခံပါသည္။ ေကာ္ပိုေရးရွင္းမ်ားသည္ Tor ကုိ အမ်ားႏွင့္
69 
+ယွဥ္ျပိဳင္ရေသာ စိစစ္ေလ့လာခ်က္မ်ား လုပ္ကိုင္ရန္ လံုျခံဳေသာ နည္းလမ္းအျဖစ္ႏွင့္
70 
+အျခားသူ၏သီးသန္႕စကားကုိ တိတ္တဆိတ္နားေထာင္သူမ်ားမွ အထိခိုက္မခံေသာ
71 
+ဝယ္ယူမႈပံုစံမ်ားကုိ ကာကြယ္ရန္ အသံုးျပဳၾကပါသည္။ ၎တို႕သည္ ပမာဏအတိအက်ႏွင့္
72 
+ဆက္သြယ္မႈျပဳခ်ိန္ကို သိရွိႏုိင္ေသာ အသံုးျပဳေနက် VPN မ်ားကို
73 
+အစားထုိးရန္အတြက္လည္း အသံုးျပဳၾကပါသည္။ မည္သည့္ေနရာတြင္ ဝန္ထမ္းမ်ား
74 
+ေနာက္က်ပါသလဲ ? မည္သည့္ေနရာတြင္ ဝန္ထမ္းမ်ား အလုပ္ရွာသည့္ ဝက္ဆုိက္မ်ားႏွင့္
75 
+တုိင္ပင္ေနပါသလဲ ? မည္သည့္ သုေတသနဌာနသည္ ကုမၸဏီ၏ မူပိုင္ခြင့္ ဥပေဒသမားႏွင့္
76 
+ဆက္သြယ္ေနပါသလဲ ?
77 
+</p>
78 
+
79 
+<p>
80 
+U.S ေရတပ္၏ ဌာနခဲြတစ္ခုသည္ Tor ကုိ ပြင့္လင္းေသာ အသိဉာဏ္စုေဆာင္းမႈအျဖစ္
81 
+အသံုးျပဳျပီး ၎တို႕၏ အဖဲြ႕တစ္ခုသည္ အေရွ႕အလယ္ပိုင္းတြင္ မၾကာေသးမီက Tor ကုိ
82 
+ထိေရာက္စြာ အသံုးခ်ခဲ့ပါသည္။ ဥပေဒအာဏာပိုင္မ်ားသည္ Tor ကုိ ၎တို႕၏ web
83 
+မွတ္တမ္းမ်ားတြင္ အစိုးရအိုင္ပီကုိ မထားခဲ့ဘဲႏွင့္ web site မ်ားကုိ
84 
+လည္ပတ္ေသာအခါ သို႕မဟုတ္ ေစာင့္ၾကပ္ၾကည့္ရႈေသာအခါႏွင့္ နစ္နာမႈရွိေသာ
85 
+လုပ္ေဆာင္မႈမ်ား ျပဳလုပ္ေနစဥ္အတြင္း လံုျခံဳေရးအတြက္ အသံုးျပဳၾကပါသည္။
86 
+</p>
87 
+
88 
+<p>
89 
+Tor ကို အသံုးျပဳသည့္ မ်ိဳးစံုေသာ လူအမ်ားသည္ အမွန္တကယ္မွာ <a
90 
+href="http://freehaven.net/doc/fc03/econymics.pdf">လံုျခံဳမႈရွိေစရန္
91 
+ျပဳလုပ္ေသာ အစိတ္အပိုင္းပင္ ျဖစ္ပါသည္။</a> Tor သည္ သင့္ကို <a href="<page
92 
+torusers>">ကြန္ယက္အတြင္းရွိ အျခားသူမ်ားမွ</a> ကြယ္ဝွက္ထားပါသည္။ ထုိ႕ေၾကာင့္
93 
+Tor ကို အေျခခံေသာ အသံုးျပဳသူ ပိုမိုသိပ္သည္းမ်ားျပား၍ ပိုမို ကဲြျပားျခားနားေလ
94 
+သင္၏ အမည္ဝွက္မႈမွာ ပိုမိုအကာအကြယ္ရေလ ျဖစ္ပါသည္။
95 
+</p>
96 
+
97 
+<a name="whyweneedtor"></a>
98 
+<h3><a class="anchor" href="#whyweneedtor">ကၽြႏု္ပ္တို႕ Tor ကို
99 
+ဘာေၾကာင့္လိုသလဲ</a></h3>
100 
+
101 
+<p>
102 
+Tor ကို အသံုးျပဳျခင္းျဖင့္ “သတင္းပို႕လႊတ္မႈ စိတ္ျဖာခ်က္မ်ား” ဟု သိရွိၾကေသာ
103 
+အင္တာနက္ေစာင့္ၾကပ္ၾကည့္ရႈမႈမ်ားမွ သင့္ကုိ အကာအကြယ္ေပးပါသည္။ သတင္းပို႕လႊတ္မႈ
104 
+စိတ္ျဖာခ်က္မ်ားဆုိသည္မွာ အမ်ားသံုးကြန္ယက္တြင္ မည္သူက မည္သူ႕ကို
105 
+ေျပာေနသနည္းဆိုသည္ကုိ ဆိုလိုပါသည္။  သင့္အင္တာနက္ပို႕လႊတ္မႈမွ
106 
+မူလအရင္းအျမစ္ႏွင့္ ဦးတည္ရာကုိ သိရွိျခင္းသည္ သင့္ အမူအက်င့္ႏွင့္
107 
+စိတ္ဝင္စားမႈမ်ားကုိ ေျခရာခံခြင့္ေပးျခင္းပင္ျဖစ္ပါသည္။ အကယ္၍ အီလက္ထရြန္းနစ္
108 
+စီးပြားကူးသန္းမႈ ဆုိက္တစ္ခုသည္ သင့္တုိင္းျပည္ သို႕မဟုတ္ မူလေဒသ၏
109 
+အဖဲြ႕အစည္းေပၚမူတည္၍ ေစ်းႏႈန္းခဲြျခားမႈ ရွိသည္ဆိုပါက ဤအခ်က္သည္ သင့္
110 
+ခ်က္လက္မွတ္စာအုပ္ကုိ ထိခိုက္ႏုိင္ပါသည္။ သင္မည္သူျဖစ္သည္ႏွင့္ မည္သည့္ေနရာမွ
111 
+ျဖစ္သည္ကို သိရွိျခင္းျဖင့္ သင့္အလုပ္အကုိင္ႏွင့္ ခႏၶာကိုယ္လံုျခံဳမႈကိုပင္
112 
+ထိခိုက္ႏုိင္ပါသည္။ ဥပမာအားျဖင့္ သင္ ျပည္ပခရီးသြားေနစဥ္အတြင္း သင့္ အလုပ္ရွင္၏
113 
+ကြန္ပ်ဴတာသို႕ ဆက္သြယ္ကာ အီးေမးလ္စစ္ျခင္း သို႕မဟုတ္ ပို႕ျခင္းမ်ား
114 
+ျပဳလုပ္မည္ဆိုပါက ကြန္ယက္ကုိ စူးစမ္းရွာေဖြေနသူ တစ္စံုတစ္ေယာက္သည္ သင့္
115 
+မူလႏုိင္ငံႏွင့္ အသက္ေမြးဝမ္းေက်ာင္းမႈအဖဲြ႕အစည္းကုိ
116 
+ဆက္သြယ္မႈစကားဝွက္ျပဳလုပ္ထားေသာ္လည္း မေတာ္တဆ သိရွိသြားေစႏုိင္ပါသည္။
117 
+</p>
118 
+
119 
+<p>
120 
+သတင္းပို႕လႊတ္မႈ စိတ္ျဖာခ်က္မ်ားဆိုသည္မွာ အဘယ္နည္း ? အင္တာနက္ အခ်က္အလက္
121 
+အထုပ္ငယ္မ်ားသည္ အစိတ္အပိုင္း ႏွစ္ခုရွိပါသည္ : အခ်က္အလက္ဝန္ခ်ိန္ႏွင့္
122 
+လမ္းေၾကာင္းရွာေဖြမႈအတြက္ ေခါင္းစည္းတို႕ျဖစ္ပါသည္။ အခ်က္အလက္ဝန္ခ်ိန္သည္
123 
+ပို႕လႊတ္မည့္ မည္သည့္အရာမဆိုျဖစ္သည္။ အီးေမးလ္အခ်က္အလက္၊ web စာမ်က္ႏွာ၊
124 
+အသံဖိုင္တစ္ခု စသည္တုိ႕ ျဖစ္ခ်င္ရာ ျဖစ္ေပမည္။ သင့္ဆက္သြယ္ေရး၏
125 
+အခ်က္အလက္ဝန္ခ်ိန္ကို စကားဝွက္ျပဳလုပ္ထားေသာ္လည္း ပို႕လႊတ္မႈ စိတ္ျဖာျခင္းမွ
126 
+သင္ဘာလုပ္ေနသည္ဆုိသည္ႏွင့္ သင္ဘာေျပာေနသည္ကို မ်ားစြာ သိရွိႏိုင္ပါသည္။
127 
+ထို႕ေၾကာင့္ မူလအရင္းအျမစ္၊ ဦးတည္ရာ၊ ပမာဏ၊ အခ်ိန္ကုိက္မႈ စသည္ျဖင့္
128 
+ပူးတြဲပါဝင္ေသာ ေေခါင္းစည္းပိုင္းတြင္ အာရံုစိုက္ရျခင္းျဖစ္ပါသည္။
129 
+</p>
130 
+
131 
+<p>
132 
+ကုိယ္ေရးအခ်က္အလက္ကို ဂရုျပဳရျခင္း၏ အေျခခံ ျပႆနာမွာ သင့္ဆက္သြယ္မႈ၏ လက္ခံသူမွာ
133 
+ေခါင္းစည္းပိုင္းကို ၾကည့္ရႈျခင္းျဖင့္ သင္ပို႕လႊတ္သည္ကို
134 
+သိရွိႏုိင္ျခင္းျဖစ္သည္။ ထို႕ေၾကာင့္
135 
+အင္တာနက္ဝန္ေဆာင္မႈေပးသူကဲ့သို႕ေသာသူမ်ားကို ခ်က္ခ်င္း
136 
+ခြင့္ျပဳမိန္႕ေပးႏုိင္သည္။ သို႕မဟုတ္ ခ်က္ခ်င္း ခြင့္ျပဳမိန္႕မေပးျခင္းလည္း
137 
+ျပဳႏုိင္သည္။ အလြန္ရိုးရွင္းေသာ ပို႕လႊတ္မႈစိတ္ျဖာခ်က္မွာ ကြန္ယက္ေပၚမွ
138 
+ပို႕လႊတ္သူႏွင့္ လက္ခံသူအၾကား တစ္ေနရာတြင္ ေနထိုင္ျပီး ေခါင္းစည္းပိုင္းကို
139 
+ၾကည့္ရႈေနျခင္း ျဖစ္သည္။
140 
+</p>
141 
+
142 
+<p>
143 
+သို႕ေသာ္ ပိုမိုအားေကာင္းေသာ ပို႕လႊတ္မႈစိတ္ျဖာခ်က္အမ်ိဳးအစားမ်ားလည္း
144 
+ရွိပါသည္။ အခ်ိဳ႕ တုိက္ခိုက္သူမ်ားသည္ အင္တာနက္မွ အစိတ္အပိုင္းမ်ိဳးစံုကို
145 
+သူလွ်ိဳျပဳလုပ္ကာ ေခတ္မီဆန္းျပားရႈပ္ေထြးေသာ အခ်က္အလက္ခဲြျခမ္းမႈ
146 
+နည္းပညာမ်ားျဖင့္ ကဲြျပားျခားနားေသာ အဖဲြ႕အစည္းမ်ားႏွင့္ တစ္ဦးခ်င္းစီ၏
147 
+ဆက္သြယ္မႈ ပံုစံမ်ားကို ေျခရာခံႏုိင္ပါသည္။ စကားဝွက္ျပဳလုပ္ျခင္းသည္
148 
+အင္တာနက္ပို႕လႊတ္မႈကိုသာ ကြယ္ဝွက္ေပးျပီး ေခါင္းစည္းပိုင္းကို
149 
+မကာကြယ္ေပးေသာေၾကာင့္ ၎တုိက္ခိုက္သူမ်ားကုိ ကာကြယ္ရန္ မတတ္ႏုိင္ပါ။
150 
+</p>
151 
+
152 
+<a name="thesolution"></a>
153 
+<h3><a class="anchor" href="#thesolution">ေျဖရွင္းမႈ : ျဖန္႕က်က္ထားေသာ၊ အမည္ဝွက္
154 
+ကြန္ယက္ တစ္ခု</a></h3>
155 
+
156 
+<p>
157 
+Tor သည္ သင့္ပို႕လႊတ္လက္ခံမႈမ်ားကို အင္တာနက္၏ ေနရာမ်ားစြာသို႕
158 
+ျဖန္႕ေဝေပးျခင္း၊ တစ္ေနရာတည္းမွသာသင့္ဦးတည္ရာသို႕
159 
+သင္ႏွင့္ခ်ိတ္ဆက္ေပးျခင္းတို႕ျဖင့္ ရုိးရွင္းေသာ ပို႕လႊတ္မႈစိတ္ျဖာခ်က္ႏွင့္
160 
+ဆန္းျပားရႈပ္ေထြးေသာ ပို႕လႊတ္မႈစိတ္ျဖာခ်က္ ႏွစ္ခုလံုး၏ အႏၱရာယ္ကုိ
161 
+ေလ်ာ့ခ်ေပးပါသည္။ ၾကံစည္ထားမႈမွာ ေနာက္မွ လိုက္လာသူကုိ ေေလတုိက္သကဲ့သို႕၊
162 
+ေနာက္ေယာင္ခံရန္ ခက္ခဲေသာ လမ္းေၾကာင္းျဖင့္ အေဝးသို႕
163 
+လြင့္ထြက္သြားေစျခင္းျဖစ္ျပီး အခါအားေလ်ာ္စြာ သင့္ ေျခရာမ်ားကုိ
164 
+ဖ်က္ဆီးျခင္းျဖစ္ပါသည္။ မူလအရင္းအျမစ္မွ ဦးတည္ရာသို႕
165 
+တိုက္ရုိက္လမ္းေၾကာင္းဆက္သြယ္ျခင္းအစား Tor ကြန္ယက္တြင္
166 
+အခ်က္အလက္အထုပ္ငယ္မ်ားကုိ ထပ္ဆင့္လႊင့္သူအမ်ားအျပားကို ျဖတ္သန္း၍ က်ဘန္း
167 
+ယူေဆာင္ေစျခင္းျဖင့္ မည္သည့္စူးစမ္းရွာေဖြသူကုိမွ် မည္သည့္ေနရာတြင္မွ်
168 
+အခ်က္အလက္မ်ား မည္သည့္ေနရာက လာ၍ မည္သည့္ေနရာကို သြားမည္ကုိ ေျခရာခံမႈ
169 
+မျပဳလုပ္ႏုိင္ေတာ့ပါ။
170 
+</p>
171 
+
172 
+<p><img alt="Tor circuit step one" src="$(IMGROOT)/htw1.png" /></p>
173 
+
174 
+<p>
175 
+Tor ျဖင့္ သီးသန္႕ ကြန္ယက္လမ္းေၾကာင္းတစ္ခု ဖန္တီးမည္ဆုိပါက အသံုးျပဳသူ၏ ေဆာ့ဝဲ
176 
+သို႕မဟုတ္ client သည္ ကြန္ယက္ေပၚမွ ထပ္ဆင့္လႊင့္သူမ်ားကုိ ျဖတ္သန္း၍
177 
+စကားဝွက္ျပဳလုပ္ထားေသာ ပတ္လမ္းေၾကာင္းတစ္ခုကို တစစ တိုးခ်ဲ႕တည္ေဆာက္သြားပါသည္။
178 
+ပတ္လမ္းသည္ တစ္ၾကိမ္ခုန္ကူးလွ်င္ တစ္ၾကိမ္ တုိးသြားပါသည္။ ျပီးလွ်င္
179 
+လမ္းတစ္ေလွ်ာက္ရွိ ထပ္ဆင့္လႊင့္သူတိုင္းသည္ မည္သည့္ ထပ္ဆင့္လႊင့္သူမွ
180 
+အခ်က္အလက္ေပးသည္ႏွင့္ မည္သည့္ ထပ္ဆင့္လႊင့္သူကို အခ်က္အလက္ေပးရမည္ဆိုသည္ကုိသာ
181 
+သိပါသည္။ မည္သည့္ တစ္ဦးခ်င္း ထပ္ဆင့္လႊင့္သူမွ အခ်က္အလက္အထုပ္ငယ္သြားေရာက္ေသာ
182 
+လမ္းေၾကာင္းအျပည့္အစံုကို မသိရွိႏုိင္ပါ။ client သည္
183 
+အခ်က္အလက္ျဖတ္သန္းသြားလာေသာ ဆက္သြယ္မႈလမ္းေၾကာင္းကုိ ေျခရာမခံႏိုင္ေစရန္
184 
+လမ္းေၾကာင္းတစ္ေလွ်ာက္တြင္ တစ္ခါခုန္ကူးမႈတုိင္းအတြက္ သီးျခား
185 
+စကားဝွက္ေသာ့မ်ားကို ေဆြးေႏြးညိႇႏိႈင္းရယူပါသည္။
186 
+</p>
187 
+
188 
+<p><img alt="Tor circuit step two" src="$(IMGROOT)/htw2.png" /></p>
189 
+
190 
+<p>
191 
+ပတ္လမ္းေၾကာင္း တစ္ခု တည္ေဆာက္ျပီးသည္ႏွင့္ Tor ကြန္ယက္ကုိ ျဖတ္သန္း၍
192 
+အခ်က္အလက္မ်ိဳးစံု ကူးသန္းလဲလွယ္ႏိုင္ျပီး ေဆာ့ဝဲအသံုးခ်ပရိုဂရမ္မ်ိဳးစံုကို
193 
+အသံုးခ်ႏုိင္ပါသည္။ အဘယ္ေၾကာင့္ဆုိေသာ္ ထပ္ဆင့္လႊင့္သူတိုင္းသည္
194 
+ၾကားျဖတ္ခုိးယူနားေထာင္သူျဖစ္ေစ သို႕မဟုတ္ အေပးအယူညႇိႏိႈင္းထားေသာ
195 
+ထပ္ဆင့္လႊင့္သူျဖစ္ေစ ပတ္လမ္းထဲတြင္ တစ္ခါခုန္ကူးမႈထက္ပို၍
196 
+မျမင္ႏုိင္ေသာေၾကာင့္ ျဖစ္ပါသည္။ Tor သည္ TCP စီးဆင္းမႈအတြက္သာ အလုပ္လုပ္ျပီး
197 
+SOCKS အေထာက္အကူျပဳေသာ မည္သည့္ အသံုးခ်ပရိုဂရမ္မဆို အသံုးျပဳႏုိင္ပါသည္။
198 
+</p>
199 
+
200 
+<p>
201 
+ထိေရာက္စြာအက်ိဳးရွိေစရန္ Tor ေဆာ့ဝဲသည္ တူညီေသာ ၁၀ မိနစ္အတြင္း သို႕မဟုတ္
202 
+ထုိကဲ့သို႕ေသာ အခ်ိန္အတြင္းတြင္ ျဖစ္ေပၚေသာ ဆက္သြယ္မႈကုိ တူညီေသာ ပတ္လမ္းအျဖစ္
203 
+အသံုးျပဳပါသည္။ ေနာက္ပိုင္း ေတာင္းဆုိမႈမ်ားကုိ လူအမ်ားအေစာပိုင္း
204 
+လုပ္ေဆာင္မႈမွ အသစ္တစ္ခုသို႕ ခ်ိတ္ဆက္ႏုိင္ေစရန္ ပတ္လမ္းေၾကာင္း အသစ္တစ္ခု
205 
+ေပးပါသည္။
206 
+</p>
207 
+
208 
+<p><img alt="Tor circuit step three" src="$(IMGROOT)/htw3.png" /></p>
209 
+
210 
+
211 
+<a name="hiddenservices"></a>
212 
+<h3><a class="anchor" href="#hiddenservices">ကြယ္ဝွယ္ထားေသာ ဝန္ေဆာင္မႈမ်ား</a></h3>
213 
+
214 
+<p>
215 
+Tor သည္ ဝက္ထုတ္လႊင့္မႈမ်ား သို႕မဟုတ္ အခ်က္အလက္ ခ်က္ခ်င္းပို႕ႏုိင္သည့္
216 
+ဆာဗာမ်ားကဲ့သို႕ေသာ မ်ိဳးစံုသည့္ ဝန္ေဆာင္မႈမ်ားကို
217 
+အသံုးျပဳေနစဥ္အတြင္းတြင္လည္း ၎တုိ႕၏ တည္ေနရာကို ဝွက္ထားရန္ အသံုးျပဳႏုိင္ပါသည္။
218 
+Tor “ဆံုရပ္ ေနရာ” ကုိ အသံုးျပဳျခင္းျဖင့္ အျခား Tor အသံုးျပဳသူမ်ားသည္
219 
+တစ္ဦးစီ၏ အျခား ကြန္ယက္ အမွတ္အသားကို မသိရွိဘဲ ဤကြယ္ဝွက္ထားေသာ
220 
+ဝန္ေဆာင္မႈမ်ားကို ဆက္သြယ္ႏုိင္ပါသည္။ ဤ ကြယ္ဝွက္ထားေသာ ဝန္ေဆာင္မႈသည္
221 
+ဆင္ဆာတည္းျဖတ္မႈကို စိုးရိမ္စရာမလုိဘဲ ဝက္ဆုိက္တည္ေထာင္ျခင္းမ်ားကုိ
222 
+လုပ္ေဆာင္ႏိုင္ပါသည္။ မည္သူမွ် ဆိုက္ကို တင္ဆက္သည္ကို မဆံုးျဖတ္ႏုိင္ပါ။
223 
+ဆုိက္ကို တင္ဆက္သူ မည္သူမွ် မည္သူက ေရးသားေပးပို႕ေနသည္ကုိ မသိရွိႏုိင္ပါ။ <a
224 
+href="<page docs/tor-hidden-service>">ကြယ္ဝွက္ထားေသာ ဝန္ေဆာင္မႈမ်ား
225 
+ျပင္ဆင္သတ္မွတ္ျခင္း</a> ႏွင့္ <a href="<page
226 
+hidden-services>">ကြယ္ဝွက္ထားေသာ ဝန္ေဆာင္မႈ ဘာသာစကား</a> ကုိ ဆက္လက္ေလ့လာပါ။
227 
+</p>
228 
+
229 
+<a name="stayinganonymous"></a>
230 
+<h3><a class="anchor" href="#stayinganonymous">အမည္ဝွက္ ေနထုိင္မႈ</a></h3>
231 
+
232 
+<p>
233 
+Tor သည္ အမည္ဝွက္ျပႆနာအားလံုးကုိ မေျဖရွင္းႏုိင္ပါ။ ၎မွ
234 
+အခ်က္အလက္ပို႕ေဆာင္မႈကို ကာကြယ္ေပးျခင္းကိုသာ အေလးထားပါသည္။
235 
+သင့္ကုိယ္ပုိင္အမွတ္အသား သတင္းအခ်က္အလက္မ်ားကို သင္လည္ပတ္ေသာ ဝက္ဆိုက္မ်ားမွ
236 
+မျမင္ေတြ႕ေစလုိလွ်င္ သတ္မွတ္ ဘာသာစကား အေထာက္အကူျပဳ ေဆာ့ဝဲမ်ားကုိ အသံုးျပဳရန္
237 
+လိုအပ္ပါသည္။ ဥပမာအားျဖင့္ သင္ web ၾကည့္ရႈေနစဥ္အတြင္း သင့္ browser
238 
+အမ်ိဳးအစားႏွင့္ ပတ္သတ္ေသာ အခ်က္အလက္မ်ားႏွင့္ cookies မ်ားကို မျပသလိုလွ်င္
239 
+Privoxy ကဲ့သို႕ေသာ web proxies မ်ားကုိ အသံုးျပဳႏုိင္ပါသည္။
240 
+</p>
241 
+
242 
+<p>
243 
+သင့္ အမည္ဝွက္မႈကုိ ကာကြယ္ရန္ လိမၼာပါးနပ္ရပါမည္။ Web ပံုစံစာရြက္မ်ားတြင္
244 
+သင့္နာမည္ သို႕မဟုတ္ အျခား သတင္းအခ်က္အလက္မ်ားကို မေဖာ္ျပပါႏွင့္။ အျခား
245 
+အမည္ဝွက္ကြန္ယက္အားလံုးကဲ့သို႕ပင္ ဝက္ၾကည့္ရႈျခင္းအတြက္ လံုေလာက္ေသာ
246 
+ျမန္ဆန္ေသာ္လည္း Tor သည္ အဆံုးမွအဆံုးသို႕ တုိက္ခုိက္ျခင္းကုိ ကာကြယ္မႈ
247 
+မျပဳႏိုင္ျခင္း၊ သင့္ကုိ တုိက္ခိုက္သူသည္ သင့္ကြန္ပ်ဴတာမွ ထြက္လာေသာ
248 
+ပို႕လႊတ္မႈမ်ားကို ေစာင့္ၾကည့္ႏုိင္ျခင္း၊ သင္ေရြးခ်ယ္ထားေသာ ဦးတည္ရာသို႕
249 
+ေရာက္ရွိလာေသာ ပို႕လႊတ္မႈမ်ားကို ေစာင့္ၾကည့္ႏုိင္ျခင္း၊
250 
+စာရင္းအင္းစိတ္ျဖာမႈကုိ အသံုးျပဳ၍ သူတို႕သည္ တူညီေသာ ပတ္လမ္းအတြင္းမွ
251 
+အစိတ္အပိုင္းျဖစ္သည္ကုိ ရွာေဖြႏိုင္ျခင္းတို႕ကို သတိျပဳပါ။
252 
+</p>
253 
+
254 
+<a name="thefutureoftor"></a>
255 
+<h3><a class="anchor" href="#thefutureoftor">Tor ၏ အနာဂါတ္</a></h3>
256 
+
257 
+<p>
258 
+ယေန႕ အင္တာနက္တြင္ အသံုးဝင္ေသာ အမည္ဝွက္ကြန္ယက္ကုိ ေဖာ္ေဆာင္ျခင္းသည္
259 
+ဆက္လက္လုပ္ေဆာင္ရဦးမည့္ စိန္ေခၚမႈ တစ္ခု ျဖစ္ပါသည္။ အသံုးျပဳသူမ်ား၏
260 
+လိုအပ္ခ်က္ႏွင့္ ကိုက္ညီမည့္ ေဆာ့ဝဲမ်ားကုိ ကၽြႏု္ပ္တို႕ လိုလားပါသည္။
261 
+အသံုးျပဳသူမ်ားႏိုင္သမွ် မ်ားမ်ားကုိ ကုိင္တြယ္ႏုိင္မည့္နည္းလမ္းႏွင့္
262 
+ကြန္ယက္ကုိ ၾကီးထြားႏိုင္သမွ် ၾကီးထြားေအာင္ ထိန္းသိမ္းရန္လည္း လိုလားပါသည္။
263 
+Tor ၏ အသံုးဝင္မႈ တုိးတက္လာသည္ႏွင့္ ပိုမိုမ်ားျပားေသာ အသံုးျပဳသူမ်ားကို
264 
+ဆဲြေဆာင္လာႏုိင္ျခင္းျဖင့္ ဆက္သြယ္မႈတုိင္း၏ မူလအရင္းအျမစ္ႏွင့္ ဦးတည္ရာမ်ား
265 
+ပိုမိုမ်ားျပားလာႏုိင္ျခင္း၊ ထုိ႕ေၾကာင့္ လူတုိင္းအတြက္ လံုျခံဳမႈ
266 
+ျမင့္တက္လာျခင္းတို႕ေၾကာင့္ လံုျခံဳေရးႏွင့္ အသံုးဝင္မႈသည္
267 
+ပိုလွ်ံေနသည္မရွိေစရပါ။ ကၽြႏု္ပ္တို႕ တုိးတက္ေစရန္ ျပဳလုပ္ေနေသာ္လည္း
268 
+သင့္အကူအညီကုိ လိုအပ္ပါသည္။ ေက်းဇူးျပဳ၍ <a href="<page
269 
+docs/tor-doc-relay>">ထပ္ဆင့္လႊင့္မႈ ျပဳလုပ္ျခင္း</a> သို႕မဟုတ္ <a
270 
+href="<page documentation>#Developers">ထုတ္လုပ္ဖန္တီးသူ အျဖစ္</a> <a
271 
+href="<page volunteer>">ေစတနာ့ဝန္ထမ္းလုပ္ျခင္း</a> တုိ႕ကုိ
272 
+စဥ္းစားေပးေစလုိပါသည္။
273 
+</p>
274 
+
275 
+<p>
276 
+ဥပေဒ၊ မူဝါဒ ႏွင့္ နည္းပညာ တို႕၏ လားရာ တုိးတက္မႈမ်ားမွ အမည္ဝွက္မႈကုိ
277 
+မၾကံဳဘူးေသးေသာ ျခိမ္းေျခာက္မႈမ်ားေၾကာင့္ ကၽြႏု္ပ္တို႕၏ အြန္လိုင္းတြင္
278 
+လြတ္လပ္စြာ ေျပာဆိုႏိုင္ျခင္း၊ ဖတ္ရႈႏုိင္ျခင္းမ်ားကို  ေလ်ာ့ပါးေစပါသည္။ ၎
279 
+လားရာမ်ားသည္ တစ္ဦးခ်င္းစီအတြင္း၊ အဖဲြ႕အစည္းမ်ားအတြင္း၊
280 
+ေကာ္ပိုေရးရွင္းမ်ားအတြင္းႏွင့္ အစိုးရမ်ားအတြင္း အားနည္းခ်က္မ်ားကုိ
281 
+စိတ္ျဖာႏုိင္ရန္ ပိုမိုဆက္သြယ္မႈမ်ား ျပဳလုပ္ျခင္းျဖင့္
282 
+အမ်ိဳးသားလံုျခံဳေရးႏွင့္ အဓိက အေျခခံအေဆာက္အဦမ်ားကုိ ေအာက္ေျခမွ
283 
+လိႈက္စားခ်ိနဲ႕ေစပါသည္။ အသံုးျပဳသူအသစ္တုိင္းႏွင့္ ထပ္ဆင့္လႊင့္သူတုိင္းသည္
284 
+အပိုေဆာင္း ထိန္းသိမ္းေစာင့္ေရွာက္မႈမ်ား၊ Tor ၏ စြမ္းေဆာင္ႏုိင္မႈမ်ားကုိ
285 
+တုိးခ်ဲ႕၍ သင့္လံုျခံဳမႈႏွင့္ တစ္ကုိယ္ေရတည္ရွိမႈမ်ားကုိ သင့္လက္ထဲသို႕
286 
+ျပန္လည္ေရာက္ရွိေအာင္ လုပ္ေဆာင္ေပးၾကပါသည္။
287 
+</p>
288 
+
289 
+  </div>
290 
+
291 
+
292 
+#include <foot.wmi>
cgi-bin/languageswitch.cgi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,7 @@
1 
+#!/usr/bin/env perl
2 
+
3 
+# This CGI tries to do as little as possible. A URL is passed from the languages
4 
+# dropdown form generated in /include/foot.wmi and the client is redirected to that page
5 
+use CGI qw(:standard);
6 
+my $lang = param('Language');
7 
+print "Status: 302 Moved\nLocation: /$lang\n\n";
css/._ie6.css
Zeige Datei @ 2a9aaa802
css/._ie7-and-down.css
Zeige Datei @ 2a9aaa802
css/._layout.css
Zeige Datei @ 2a9aaa802
css/._master.css
Zeige Datei @ 2a9aaa802
css/._reset.css
Zeige Datei @ 2a9aaa802
css/._typography.css
Zeige Datei @ 2a9aaa802
css/ie6.css
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,40 @@
1 
+@charset "UTF-8";
2 
+/* IE6 Only*/
3 
+
4 
+html * {
5 
+padding: 0;
6 
+margin: 0;
7 
+border: 0;
8 
+}
9 
+
10 
+#maincol-left, #maincol { width: 690px; }
11 
+#sidecol-right, #sidecol { width: 210px; }
12 
+#home #maincol { width: 600px; }
13 
+#home #sidecol { width: 290px; }
14 
+
15 
+#calltoaction {
16 
+	margin: 0;
17 
+}
18 
+
19 
+#banner ul li { list-style: url(../images/white-bullet.gif) outside; }
20 
+
21 
+#sidenav ul li {
22 
+		display: inline-block;
23 
+	}
24 
+
25 
+.img-shadow .custom-infoblock { width: 412px; }
26 
+
27 
+#footer .newsletter input.textfield { border: 1px solid #ddd; }
28 
+
29 
+#home-our-projects {
30 
+  margin-top: 25px;
31 
+}
32 
+
33 
+#download a .download-tor {
34 
+  background: url(../images/button-download-arrow.gif) right center no-repeat;
35 
+}
36 
+
37 
+#download a:link,
38 
+#download a:visited {
39 
+  background: url(../images/button-download.gif) left top no-repeat;
40 
+}
css/ie7-and-down.css
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,54 @@
1 
+@charset "UTF-8";
2 
+/* IE7 and Lower */
3 
+
4 
+
5 
+#nav { margin: 0; }
6 
+#nav ul li a:link,
7 
+#nav ul li a:visited {
8 
+	display: block;
9 
+	height: 50px;
10 
+}
11 
+
12 
+h1.headline { padding: 5px 0 10px; }
13 
+p.desc { margin: -10px 0 10px; }
14 
+
15 
+#download a:link,
16 
+#download a:visited {
17 
+	margin: -14px 0 0;
18 
+}
19 
+
20 
+	#sidenav ul li ul {
21 
+		display: inline-block;
22 
+	}
23 
+
24 
+	#sidenav ul li.active,
25 
+	#sidenav ul li.active-longtitle {
26 
+		background: none;
27 
+		width: 100%;
28 
+		border-bottom: 1px solid #ddd;
29 
+	}
30 
+
31 
+.donate-btn {
32 
+	width: 102px;
33 
+	font-size: 0;
34 
+	color: #fff;
35 
+	text-align: right;
36 
+}
37 
+
38 
+.focus .continue { padding-bottom: 20px; }
39 
+
40 
+table h2 { margin-bottom: -4px; padding-bottom: 0;}
41 
+
42 
+/*#footer .signup {
43 
+	width: 82px;
44 
+	font-size: 0;
45 
+	color: #fff;
46 
+	text-align: right;
47 
+}
48 
+
49 
+#footer .go {
50 
+	width: 20px;
51 
+	font-size: 0;
52 
+	color: #fff;
53 
+	text-align: right;
54 
+}*/
0 55 
\ No newline at end of file
css/layout.css
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,579 @@
1 
+@charset "UTF-8";
2 
+/* Layout */
3 
+
4 
+/* UNIVERSAL ------------*/
5 
+
6 
+body {
7 
+	background: #fff;
8 
+}
9 
+
10 
+#wrap {
11 
+	width: 960px;
12 
+	margin: 0 auto;
13 
+}
14 
+
15 
+.left { float: left; }
16 
+.right { float: right; }
17 
+.twenty { width: 20%; }
18 
+.thirty { width: 30%; }
19 
+.forty { width: 40%; }
20 
+.fifty { width: 50%; }
21 
+.sixty { width: 60%; }
22 
+.hundred { width: 100%; }
23 
+
24 
+.nopad { padding: 0; }
25 
+.toppad { padding-top: 10px; }
26 
+.toptwenty { margin-top: 20px; }
27 
+.topforty { margin-top: 40px; }
28 
+
29 
+
30 
+/* HEADER ------------*/
31 
+
32 
+#header {
33 
+	width: 960px;
34 
+	height: 97px;
35 
+	margin-bottom: 23px;
36 
+	position: relative;
37 
+}
38 
+
39 
+  h1#logo {
40 
+    margin: 0;
41 
+    float: left;
42 
+  }
43 
+
44 
+	h1#logo a,
45 
+	h1#logo a:visited {
46 
+		background: url(../images/tor-logo.jpg) left top no-repeat;
47 
+		text-indent: -9999px;
48 
+		overflow: hidden;
49 
+		width: 150px;
50 
+		height: 97px;
51 
+		display: block;
52 
+	}
53 
+
54 
+	#nav {
55 
+	  float: right;
56 
+	}
57 
+
58 
+		#nav ul {
59 
+			height: 50px;
60 
+			float: right;
61 
+			margin-bottom: 0;
62 
+		}
63 
+
64 
+			#nav ul li {
65 
+				float: left;
66 
+				display: inline;
67 
+				width: auto;
68 
+			}
69 
+
70 
+	#calltoaction {
71 
+		height: 30px;
72 
+		float: right;
73 
+		margin-top: 10px;
74 
+	}
75 
+
76 
+    #calltoaction ul {
77 
+      padding: 0;
78 
+      margin: 0;
79 
+      height: 30px;
80 
+      list-style: none;
81 
+      float: right;
82 
+    }
83 
+
84 
+      #calltoaction ul li {
85 
+        list-style: none;
86 
+        display: inline;
87 
+        float: left;
88 
+        width: auto;
89 
+        margin-left: 10px;
90 
+      }
91 
+
92 
+      #calltoaction ul li a:link,
93 
+      #calltoaction ul li a:visited{
94 
+        background: #96c35a;
95 
+        border-top: 1px solid #6ab334;
96 
+        border-left: 1px solid #6ab334;
97 
+        border-bottom: 1px solid #5a952b;
98 
+        border-right: 1px solid #5a952b;
99 
+        padding: 8px 8px 0px;
100 
+        color: #222c14;
101 
+        font-weight: bold;
102 
+        text-decoration: none;
103 
+        font-size: 1.167em;
104 
+        line-height: 1.167em;
105 
+        height: 22px;
106 
+        float: left;
107 
+      }
108 
+
109 
+      #calltoaction ul li a:hover,
110 
+      #calltoaction ul li a.active { background: #6ab334; }
111 
+
112 
+
113 
+/* BANNER ------------*/
114 
+
115 
+		#banner {
116 
+			background: url(../images/bg-banner.jpg) left top no-repeat;
117 
+			height: 200px;
118 
+			width: 600px;
119 
+			padding: 23px 15px;
120 
+			margin-bottom: 15px;
121 
+		}
122 
+
123 
+		#download a:link,
124 
+		#download a:visited {
125 
+			margin: -17px 0 0;
126 
+			background: url(../images/button-download.png) left top no-repeat;
127 
+			width: 257px;
128 
+			height: 79px;
129 
+			float: left;
130 
+			padding: 35px 0 0 80px;
131 
+			text-decoration: none;
132 
+		}
133 
+
134 
+		#download a .download-tor {
135 
+			background: url(../images/button-download-arrow.png) right center no-repeat;
136 
+			font-family: "Arial Narrow", Arial, sans-serif;
137 
+			color: #fff;
138 
+			font-size: 2.167em;
139 
+			letter-spacing: 1px;
140 
+			padding-right: 25px;
141 
+		}
142 
+		#download a .version {
143 
+			color: #bda5cc;
144 
+			font-size: 1.167em;
145 
+			line-height: 1.167em;
146 
+		}
147 
+		#download a .info {
148 
+			color: #bda5cc;
149 
+			font-size: 0.833em;
150 
+			line-height: 0.833em;
151 
+		}
152 
+
153 
+		#download a:hover {
154 
+			background-position: 0 -114px;
155 
+		}
156 
+		#download a:hover .version,
157 
+		#download a:hover .info { color: #f1c6a1; }
158 
+
159 
+			#banner ul {
160 
+				background: #387520 url(../images/banner-gradient.jpg) left top repeat-x;
161 
+				border: 1px solid #366b32;
162 
+				width: 180px;
163 
+				float: right;
164 
+				margin: 0 15px 0 0;
165 
+				padding: 10px 10px 10px 30px;
166 
+			}
167 
+
168 
+			#banner ul li {
169 
+				list-style: url(../images/white-bullet.png) outside;
170 
+				padding: 5px 0;
171 
+			}
172 
+
173 
+/* CONTENT ------------*/
174 
+
175 
+#content {
176 
+	width: 960px;
177 
+}
178 
+
179 
+	#content img { max-width: 250px; }
180 
+
181 
+	#breadcrumbs { padding: 0 0 10px 5px; }
182 
+
183 
+	#home #maincol {
184 
+		float: left;
185 
+		width: 620px;
186 
+		margin-right: 20px;
187 
+	}
188 
+
189 
+	#maincol {
190 
+		float: right;
191 
+		width: 710px;
192 
+		margin-bottom: 20px;
193 
+	}
194 
+
195 
+	#maincol-left {
196 
+		float: left;
197 
+		width: 710px;
198 
+		margin-bottom: 20px;
199 
+	}
200 
+
201 
+		.subcol {
202 
+			width: 280px;
203 
+			float: left;
204 
+			margin: 0 0 25px;
205 
+		}
206 
+
207 
+			#content .first {
208 
+				margin-right: 20px;
209 
+			}
210 
+
211 
+/* SIDEBAR ------------*/
212 
+
213 
+#home #sidecol {
214 
+	float: right;
215 
+	width: 300px;
216 
+}
217 
+
218 
+#sidecol {
219 
+	float: left;
220 
+	width: 230px;
221 
+	margin-right: 20px;
222 
+}
223 
+
224 
+#sidecol-right {
225 
+	float: right;
226 
+	width: 230px;
227 
+	margin-left: 20px;
228 
+}
229 
+
230 
+	#torusers { margin: 0 0 27px; }
231 
+		.user {
232 
+			margin: 0 0 12px;
233 
+			height: auto;
234 
+		}
235 
+		.user img, .project-icon {
236 
+			border: 1px solid #cac8a7;
237 
+			float: left;
238 
+			margin: 3px 10px 0 0;
239 
+		}
240 
+		.user p { margin: 0; }
241 
+
242 
+/* IMGSHADOW ------------*/
243 
+
244 
+.img-shadow {
245 
+	float:left;
246 
+	background: url(../images/shadowAlpha.png) no-repeat bottom right !important;
247 
+	background: url(../images/shadow.gif) no-repeat bottom right;
248 
+	margin: 10px 0 10px 10px !important;
249 
+	margin: 10px 0 10px 5px;
250 
+}
251 
+
252 
+	.img-shadow .infoblock,
253 
+	.img-shadow .important-infoblock,
254 
+	.img-shadow .custom-infoblock,
255 
+	.img-shadow #sidenav,
256 
+	.img-shadow .sidenav-sub {
257 
+		display: block;
258 
+		position: relative;
259 
+		margin: -6px 6px 6px -6px;
260 
+		background-color: #fff;
261 
+		border: 1px solid #ddd;
262 
+	}
263 
+	.img-shadow .important-infoblock {
264 
+		background-color: #f7f8f0;
265 
+		border: 1px solid #eeefe8;
266 
+	}
267 
+
268 
+	.img-shadow .infoblock,
269 
+	.img-shadow .important-infoblock {
270 
+		padding: 15px;
271 
+		width: 188px;
272 
+	}
273 
+
274 
+	.img-shadow .custom-infoblock {
275 
+		padding: 15px;
276 
+		height: 120px;
277 
+		width: 426px;
278 
+	}
279 
+
280 
+	.img-shadow .infoblock p,
281 
+	.img-shadow .important-infoblock p,
282 
+	.img-shadow .custom-infoblock p {
283 
+		margin: 0;
284 
+	}
285 
+
286 
+
287 
+/* SIDENAV ------------*/
288 
+
289 
+/*Note: #sidenav-sub is used on the downloads page as a tertiary navigation*/
290 
+
291 
+.img-shadow #sidenav,
292 
+.img-shadow .sidenav-sub {
293 
+	padding: 10px 0 0;
294 
+	width: 218px;
295 
+}
296 
+
297 
+	#sidenav ul li,
298 
+	.sidenav-sub ul li { border-bottom: 1px solid #ddd; }
299 
+
300 
+	#sidenav ul li.dropdown a:link,
301 
+	#sidenav ul li.dropdown a:visited { background: url(../images/sidenav-arrow.gif) left center no-repeat; }
302 
+	#sidenav ul li.dropdown a.active { background: url(../images/sidenav-arrow-active.gif) left center no-repeat; }
303 
+
304 
+	.sidenav-sub ul li.dropdown a:link,
305 
+	.sidenav-sub ul li.dropdown a:visited {
306 
+		background: url(../images/sidenav-arrow.gif) left top no-repeat;
307 
+		margin-top: 12px;
308 
+	}
309 
+
310 
+	#sidenav ul li a:link,
311 
+	#sidenav ul li a:visited {
312 
+		display: block;
313 
+		height: auto;
314 
+		padding: 8px 15px 8px 26px;
315 
+	}
316 
+
317 
+	#sidenav ul li ul li a:link,
318 
+	#sidenav ul li ul li a:visited {
319 
+		padding-left: 37px;
320 
+	}
321 
+
322 
+	.sidenav-sub ul li a:link,
323 
+	.sidenav-sub ul li a:visited {
324 
+		display: block;
325 
+		padding: 0 15px 10px 26px;
326 
+		line-height: 16px;
327 
+	}
328 
+
329 
+	#sidenav ul li.active {
330 
+		background: url(../images/sidenav-active.png) left center no-repeat;
331 
+		width: 230px;
332 
+		border: 0;
333 
+	}
334 
+
335 
+  #sidenav ul li ul li ul li a:link,
336 
+	#sidenav ul li ul li ul li a:visited {
337 
+		padding-left: 48px;
338 
+	}
339 
+
340 
+/* TABLE ------------*/
341 
+
342 
+table { width: 100%; }
343 
+
344 
+td { padding: 12px; }
345 
+
346 
+table td img,
347 
+table tr img {
348 
+	border: 1px solid #cac8a7;
349 
+	float: left;
350 
+	margin-right: 10px;
351 
+}
352 
+
353 
+.icon {
354 
+	float: left;
355 
+	width: auto;
356 
+	margin-right: 15px;
357 
+	padding: 10px 0;
358 
+	border: 0;
359 
+}
360 
+
361 
+.calendar {
362 
+	background: url(../images/icon-calendar.jpg) left top no-repeat;
363 
+	float: left;
364 
+	margin-right: 10px;
365 
+	width: 45px;
366 
+	height: 54px;
367 
+	text-align: center;
368 
+	padding: 4px 0;
369 
+}
370 
+
371 
+.fauxhead {
372 
+	background: url(../images/table-arrow.jpg) right top no-repeat;
373 
+	width: 100%;
374 
+	height: 11px;
375 
+}
376 
+
377 
+.beige { background: #f5f5df; }
378 
+
379 
+.meta {
380 
+	float: right;
381 
+	width: auto;
382 
+}
383 
+
384 
+/* DL TABLE ------------*/
385 
+
386 
+td.intro { padding: 0 0 10px; }
387 
+
388 
+.windows,
389 
+.mac,
390 
+.linux,
391 
+.android { padding: 5px 0 5px 20px; }
392 
+
393 
+.windows { background: url(../images/icon-windows.gif) left center no-repeat; }
394 
+.mac { background: url(../images/icon-mac.gif) left center no-repeat; }
395 
+.linux { background: url(../images/icon-linux.gif) left center no-repeat; }
396 
+.android { background: url(../images/icon-android.gif) left center no-repeat; }
397 
+
398 
+
399 
+/* MISC ------------*/
400 
+
401 
+.title {
402 
+	background: url(../images/table-title-arrow.jpg) right top no-repeat;
403 
+	padding: 10px 25px 0 10px;
404 
+	height: 33px;
405 
+	float: left;
406 
+}
407 
+
408 
+	.title a:link,
409 
+	.title a:visited {
410 
+		background: url(../images/table-title.jpg) left top no-repeat;
411 
+		height: 33px;
412 
+		display: block;
413 
+	}
414 
+
415 
+.paypal {
416 
+	float: left;
417 
+	width: auto;
418 
+	min-height: 159px;
419 
+	max-width: 365px;
420 
+}
421 
+	.paypal span { padding-right: 20px; }
422 
+
423 
+.warning {
424 
+	background: #ebd4a9 url(../images/warning.jpg) left center no-repeat;;
425 
+	border: 1px solid #deba78;
426 
+	padding: 10px 15px;
427 
+}
428 
+	.warning p { padding-left: 40px; }
429 
+
430 
+.focus {
431 
+	background: #f4f2c7;
432 
+	border: 1px solid #ebd4a9;
433 
+	padding: 10px 15px;
434 
+}
435 
+
436 
+	.focus .icon {
437 
+		float: left;
438 
+		width: auto;
439 
+		margin-right: 10px;
440 
+	}
441 
+
442 
+.featured-project { width: 313px; }
443 
+
444 
+/* FORM ------------*/
445 
+
446 
+input, select {
447 
+	margin: 0 3px 10px 0;
448 
+}
449 
+
450 
+input.textfield {
451 
+	padding: 0 10px;
452 
+	vertical-align: top;
453 
+}
454 
+
455 
+.donate-btn {
456 
+	background: url(../images/button-donate.jpg) left top no-repeat;
457 
+	height: 26px;
458 
+	width: 92px;
459 
+	text-indent: -9999px;
460 
+	overflow: hidden;
461 
+	border: 0;
462 
+	vertical-align: top;
463 
+	margin-top: 5px;
464 
+}
465 
+	.donate-btn:hover {
466 
+		background-position: 0 -26px;
467 
+		cursor: pointer;
468 
+	}
469 
+
470 
+.signup {
471 
+	background: #96c35a;
472 
+	border-top: 1px solid #6ab334;
473 
+	border-left: 1px solid #6ab334;
474 
+	border-bottom: 1px solid #5a952b;
475 
+	border-right: 1px solid #5a952b;
476 
+	height: 31px;
477 
+	padding: 0 5px;
478 
+	vertical-align: top;
479 
+	color: #222c14;
480 
+	font-weight: bold;
481 
+	font-size: 1em;
482 
+	line-height: 1em;
483 
+}
484 
+	.signup:hover { background: #6ab334; }
485 
+
486 
+select#lang {
487 
+	float: left;
488 
+	width: 160px;
489 
+	margin-right: 3px;
490 
+}
491 
+.go {
492 
+	background: #96c35a;
493 
+	border-top: 1px solid #6ab334;
494 
+	border-left: 1px solid #6ab334;
495 
+	border-bottom: 1px solid #5a952b;
496 
+	border-right: 1px solid #5a952b;
497 
+	padding: 0 5px;
498 
+	vertical-align: top;
499 
+	color: #222c14;
500 
+	font-weight: bold;
501 
+	font-size: 1em;
502 
+	line-height: 1em;
503 
+	height: 18px;
504 
+}
505 
+	.go:hover { background: #6ab334; }
506 
+
507 
+
508 
+/* FOOTER ------------*/
509 
+
510 
+#footer {
511 
+	width: 960px;
512 
+	height: 200px;
513 
+	border-top: 1px solid #ddd;
514 
+	padding: 20px 0;
515 
+	margin: 20px 0 0;
516 
+}
517 
+
518 
+	.onion {
519 
+		float: left;
520 
+		width: 78px;
521 
+		padding-right: 20px;
522 
+		height: 100%;
523 
+	}
524 
+
525 
+	#footer .about {
526 
+		width: 180px;
527 
+		padding-right: 30px;
528 
+		border-right: 1px solid #ddd;
529 
+		float: left;
530 
+	}
531 
+
532 
+	#footer .newsletter {
533 
+		padding: 0 0 15px 30px;
534 
+		width: auto;
535 
+		margin-left: 308px;
536 
+	}
537 
+
538 
+		#footer input.textfield {
539 
+			width: 220px;
540 
+			height: 26px;
541 
+		}
542 
+
543 
+		#footer input {
544 
+			margin: 0;
545 
+		}
546 
+
547 
+	#footer .col {
548 
+		float: left;
549 
+		width: 100px;
550 
+		margin-left: 20px;
551 
+	}
552 
+
553 
+		#footer .first { margin-left: 30px; }
554 
+		#footer .wider { width: 201px; }
555 
+
556 
+/*
557 
+** Markup free clearing
558 
+** Details: http://www.positioniseverything.net/easyclearing.html
559 
+*/
560 
+.clearfix:after {
561 
+  content: ".";
562 
+  display: block;
563 
+  height: 0;
564 
+  clear: both;
565 
+  visibility: hidden;
566 
+}
567 
+
568 
+.clearfix {
569 
+  display: inline-block;
570 
+}
571 
+
572 
+/* Hides from IE-mac \*/
573 
+* html .clearfix {
574 
+  height: 1%;
575 
+}
576 
+.clearfix {
577 
+  display: block;
578 
+}
579 
+/* End hide from IE-mac */
0 580 
\ No newline at end of file
css/master.css
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,14 @@
1 
+@charset "UTF-8";
2 
+/* --------------------------------------------------------------
3 
+
4 
+	Company Name: The Tor Project
5 
+	Company URI: http://www.torproject.org
6 
+	Author: New Eon Media.
7 
+	Author URI: http://www.neweonmedia.com
8 
+	Date: May 2010
9 
+
10 
+-------------------------------------------------------------- */
11 
+
12 
+@import "reset.css";
13 
+@import "layout.css";
14 
+@import "typography.css";
0 15 
\ No newline at end of file
css/reset.css
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,49 @@
1 
+@charset "UTF-8";
2 
+/* Eric Meyer's Reset Reloaded */
3 
+
4 
+html, body, div, span, applet, object, iframe,
5 
+h1, h2, h3, h4, h5, h6, p, blockquote, pre,
6 
+a, abbr, acronym, address, big, cite, code,
7 
+del, dfn, em, font, img, ins, kbd, q, s, samp,
8 
+small, strike, strong, sub, sup, tt, var,
9 
+dl, dt, dd, ol, ul, li,
10 
+fieldset, form, label, legend,
11 
+table, caption, tbody, tfoot, thead, tr, th, td {
12 
+        margin: 0;
13 
+        padding: 0;
14 
+        border: 0;
15 
+        outline: 0;
16 
+        font-weight: inherit;
17 
+        font-style: inherit;
18 
+        font-size: 100%;
19 
+        font-family: inherit;
20 
+        vertical-align: baseline;
21 
+}
22 
+/* remember to define focus styles! */
23 
+:focus {
24 
+        outline: 0;
25 
+}
26 
+body {
27 
+        line-height: 1;
28 
+        color: black;
29 
+        background: white;
30 
+}
31 
+ol, ul {
32 
+        list-style: none;
33 
+}
34 
+/* tables still need 'cellspacing="0"' in the markup */
35 
+table {
36 
+        border-collapse: separate;
37 
+        border-spacing: 0;
38 
+}
39 
+caption, th, td {
40 
+        text-align: left;
41 
+        font-weight: normal;
42 
+}
43 
+blockquote:before, blockquote:after,
44 
+q:before, q:after {
45 
+        content: "";
46 
+}
47 
+blockquote, q {
48 
+        quotes: "" "";
49 
+}
css/typography.css
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,320 @@
1 
+@charset "UTF-8";
2 
+/* Typography */
3 
+
4 
+
5 
+/* UNIVERSAL ------------*/
6 
+
7 
+body {
8 
+	font-family: Helvetica, "Helvetica Neue", Arial, sans-serif;
9 
+	font-size: 9pt;
10 
+	color: #1a1a1a;
11 
+}
12 
+
13 
+h1, h2, h3, h4 {
14 
+	font-family: Georgia, "Times New Roman", Times, serif;
15 
+	font-weight: bold;
16 
+	color: #23300e;
17 
+}
18 
+
19 
+h1 a:link,
20 
+h1 a:visited,
21 
+h2 a:link,
22 
+h2 a:visited,
23 
+h3 a:link,
24 
+h3 a:visited,
25 
+h4 a:link,
26 
+h4 a:visited { text-decoration: none; }
27 
+
28 
+
29 
+h1 {
30 
+	font-size: 2em;
31 
+	line-height: 28px;
32 
+	margin-bottom: 10px;
33 
+}
34 
+
35 
+h2 {
36 
+	font-size: 1.5em;
37 
+	line-height: 28px;
38 
+	margin-bottom: 10px;
39 
+}
40 
+	.subcol h2 { margin: 0; }
41 
+	#sidenav h2,
42 
+	.sidenav-sub h2 { padding: 10px 0 0 10px; }
43 
+	h2.bulb {
44 
+		background: url(../images/lightbulb.jpg) left top no-repeat;
45 
+		padding: 0 0 0 25px;
46 
+	}
47 
+
48 
+h3 {
49 
+	font-family: Helvetica, "Helvetica Neue", Arial, sans-serif;
50 
+	font-size: 1.167em;
51 
+	line-height: 20px;
52 
+	color: #0d1304;
53 
+}
54 
+
55 
+h4 {
56 
+	font-family: Helvetica, "Helvetica Neue", Arial, sans-serif;
57 
+	line-height: 20px;
58 
+	font-size: 1em;
59 
+}
60 
+	.focus h4 { margin-bottom: 5px; }
61 
+
62 
+p, blockquote, ol, ul {
63 
+	font-size: 1em;
64 
+	line-height: 20px;
65 
+	margin-bottom: 18px;
66 
+}
67 
+
68 
+a:link, a:visited { color: #4e6a20; }
69 
+a:hover { color: #a07320; }
70 
+
71 
+strong { font-weight: bold; }
72 
+em { font-style: italic; }
73 
+
74 
+blockquote {
75 
+	color: #454545;
76 
+	font-style: italic;
77 
+	padding: 0 20px;
78 
+}
79 
+
80 
+ol, ul {
81 
+	padding-left: 40px;
82 
+}
83 
+ol { list-style: outside lower-alpha; }
84 
+ul { list-style: outside square; }
85 
+
86 
+.small { font-size: 0.833em; }
87 
+
88 
+.caps {
89 
+	font-size: 1em;
90 
+	text-transform: uppercase;
91 
+	margin: 2px 0 5px;
92 
+}
93 
+
94 
+/* NAVIGATION ------------*/
95 
+
96 
+#nav ul { font-size: 1.167em; }
97 
+
98 
+  #nav ul li { list-style: none; }
99 
+
100 
+  #nav ul li a:link,
101 
+  #nav ul li a:visited {
102 
+    color: #23300e;
103 
+    text-decoration: none;
104 
+    padding: 10px 20px 0;
105 
+    height: 40px;
106 
+    float: left;
107 
+  }
108 
+  #nav ul li a:hover,
109 
+  #nav ul li a.active { background: url(../images/bg-nav-hover.jpg) left top repeat-x;}
110 
+  #nav ul li a.active { font-weight: bold; }
111 
+
112 
+#breadcrumbs a:link,
113 
+#breadcrumbs a:visited,
114 
+.meta {
115 
+	text-transform: uppercase;
116 
+	font-size: 0.833em;
117 
+	text-decoration: none;
118 
+}
119 
+
120 
+.meta a:link,
121 
+.meta a:visited { text-decoration: none; }
122 
+
123 
+
124 
+/* BANNER ------------*/
125 
+
126 
+h1.headline {
127 
+	color: #fff;
128 
+	font-size: 3.5em;
129 
+	line-height: 28px;
130 
+	font-weight: normal;
131 
+	text-shadow: 1px 1px 2px #23300e;
132 
+	float: left;
133 
+	width: 360px;
134 
+	margin-bottom: 12px;
135 
+}
136 
+
137 
+p.desc {
138 
+	font-size: 1.417em;
139 
+	line-height: 20px;
140 
+	color: #fff;
141 
+	text-shadow: 1px 1px 2px #23300e;
142 
+	width: 360px;
143 
+	float: left;
144 
+}
145 
+
146 
+#banner ul {
147 
+	color: #fff;
148 
+	text-shadow: 1px 1px 2px #366b32;
149 
+	line-height: 16px;
150 
+	font-size: 1.167em;
151 
+}
152 
+
153 
+#banner .incorrect a:link,
154 
+#banner .incorrect a:visited {
155 
+	color: #fff;
156 
+	font-size: 0.833em;
157 
+	text-align: right;
158 
+	width: 315px;
159 
+	float: left;
160 
+	padding-right: 45px;
161 
+	line-height: 0;
162 
+	margin: -3px 0 0;
163 
+}
164 
+
165 
+/* SIDENAV ------------*/
166 
+
167 
+#sidenav ul {
168 
+	margin-bottom: 0;
169 
+	padding-left: 0;
170 
+	list-style: none;
171 
+}
172 
+
173 
+#sidenav ul li ul li { font-size: 0.917em; }
174 
+
175 
+#sidenav ul li a:link,
176 
+#sidenav ul li a:visited {
177 
+	text-decoration: none;
178 
+	color: #23300e;
179 
+	line-height: 18px;
180 
+}
181 
+
182 
+#sidenav ul li a.active,
183 
+#sidenav ul li.active,
184 
+#sidenav ul li a:hover { font-weight: bold; }
185 
+
186 
+.sidenav-sub ul {
187 
+	padding-left: 0;
188 
+	list-style: none;
189 
+	margin-bottom: 0;
190 
+}
191 
+
192 
+.sidenav-sub ul li a:link,
193 
+.sidenav-sub ul li a:visited {
194 
+	text-decoration: none;
195 
+		line-height: 16px;
196 
+}
197 
+
198 
+/* TABLE ------------*/
199 
+
200 
+table h2,
201 
+#home-our-projects h2,
202 
+#home-announcements h2 {
203 
+	background: url(../images/table-head.jpg) left top repeat-x;
204 
+	color: #f6f6ed;
205 
+	padding-left: 10px;
206 
+	margin: 0;
207 
+}
208 
+table h3 { font-size: 1.167em; }
209 
+table p {
210 
+	margin: 0;
211 
+}
212 
+
213 
+table .name {
214 
+	font-size: 1.5em;
215 
+	font-weight: bold;
216 
+	color: #23300e;
217 
+}
218 
+
219 
+.calendar .month { color: #fff; }
220 
+.calendar .day {
221 
+	font-weight: bold;
222 
+	color: #4d4d4d;
223 
+	font-size: 1.429em;
224 
+	line-height: 32px;
225 
+}
226 
+
227 
+/* DL TABLE ------------*/
228 
+
229 
+.column-title {
230 
+	font-weight: bold;
231 
+	color: #23300e;
232 
+}
233 
+
234 
+/* MISC ------------*/
235 
+
236 
+.continue a:link,
237 
+.continue a:visited {
238 
+	float: right;
239 
+	font-weight: bold;
240 
+	text-decoration: none;
241 
+}
242 
+
243 
+.paypal {
244 
+	font-size: 1.167em;
245 
+	color: #666;
246 
+}
247 
+
248 
+.warning p {
249 
+	color: #3a3a3a;
250 
+	margin-bottom: 0;
251 
+	line-height: 20px;
252 
+}
253 
+
254 
+.focus .name {
255 
+	font-size: 1.5em;
256 
+	font-weight: bold;
257 
+	color: #4e6a20;
258 
+}
259 
+.focus p { margin: 0; }
260 
+
261 
+.title {
262 
+	font-size: 1.167em;
263 
+	font-weight: bold;
264 
+	color: #f6f6ed;
265 
+}
266 
+
267 
+	.title a:link,
268 
+	.title a:visited {
269 
+		font-weight: bold;
270 
+		color: #f6f6ed;
271 
+	}
272 
+	.title a:hover { color: #f6f6ed; }
273 
+
274 
+.or {
275 
+	color: #c0e07a;
276 
+	font-size: 3em;
277 
+	padding: 30px 20px;
278 
+	font-weight: bold;
279 
+}
280 
+
281 
+.fakeol {
282 
+	font-family: Georgia, "Times New Roman", Times, serif;
283 
+	font-size: 3em;
284 
+	color: #e4c07e;
285 
+	vertical-align: text-top;
286 
+	float: left;
287 
+	width: 40px;
288 
+}
289 
+
290 
+.instructions {
291 
+	margin-bottom: 18px;
292 
+	float: left;
293 
+	width: 620px;
294 
+	line-height: 18px;
295 
+}
296 
+
297 
+.current-relay,
298 
+.target-relay {
299 
+	font-family: Georgia, "Times New Roman", Times, serif;
300 
+	font-size: 2.5em;
301 
+}
302 
+.current-relay { color: #695279; }
303 
+.target-relay { color: #4e6a20; }
304 
+
305 
+
306 
+/* FOOTER ------------*/
307 
+
308 
+#footer p,
309 
+#footer ul {
310 
+	font-size: 0.833em;
311 
+}
312 
+#footer ul {
313 
+	padding-left: 0;
314 
+	list-style: none;
315 
+}
316 
+
317 
+#footer ul li {
318 
+	line-height: 18px;
319 
+}
320 
+
de/sponsors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,90 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22225 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Sponsors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Sponsoren</h2>
14 
+<div class="underline"></div>
15 
+<p>
16 
+Die <a href="<page torusers>">verschiedenen Benutzergruppen</a> des Tor
17 
+Projektes führen dazu, dass wir ebenfalls ganz unterschiedliche
18 
+Einnahmequellen haben, und es ist uns wichtig, diese weiter zu
19 
+diversifizieren! Unsere Sponsoren können nach der Höhe des erhaltenen Geldes
20 
+unterteilt werden:
21 
+</p>
22 
+
23 
+<h3><i>Magnoliophyta</i> (über eine Million Dollar)</h3>
24 
+	<ul>
25 
+		<li>Sie?</li>
26 
+	</ul>
27 
+
28 
+<h3><i>Liliopsida</i> (bis zu 750'000 Dollar)</h3>
29 
+	<ul>
30 
+		<li>Eine anonyme amerikanische Nichtregierungsorganisation (2008-2010)</li>
31 
+	</ul>
32 
+
33 
+<h3><i>Asparagales</i> (bis zu 500'000 Dollar)</h3>
34 
+	<ul>
35 
+		<li><a href="http://www.ibb.gov/">International Broadcasting Bureau</a>
36 
+(2006-2010)</li>
37 
+		<li>Eine anonyme europäische Nichtregierungsorganisation (2006-2008)</li>
38 
+	</ul>
39 
+
40 
+<h3><i>Alliaceae</i> (bis zu 200'000 Dollar)</h3>
41 
+	<ul>
42 
+		<li>Sie?</li>
43 
+	</ul>
44 
+
45 
+<h3><i>Allium</i> (bis zu 100'000 Dollar)</h3>
46 
+	<ul>
47 
+		<li><a href="http://www.nlnet.nl/">NLnet Foundation</a> (2008-2009)</li>
48 
+		<li><a href="http://chacs.nrl.navy.mil/">Naval Research Laboratory</a>
49 
+(2006-2010)</li>
50 
+		<li>Ein anonymer amerikanische Internet Service Provider (2009-2010)</li>
51 
+	</ul>
52 
+
53 
+<h3><i>Allium cepa</i> (bis zu 50'000)</h3>
54 
+	<ul>
55 
+		<li><a href="<page donate>">Mehr als 500 persönliche Spenden von Einzelpersonen
56 
+wie Sie</a> (2006-2010)</li>
57 
+		<li><a href="http://code.google.com/opensource/">Google</a> (2008-2009)</li>
58 
+		<li><a href="http://code.google.com/soc/">Google Summer of Code</a> (2007-2009)</li>
59 
+		<li><a href="http://www.hrw.org/">Human Rights Watch</a> (2007)</li>
60 
+		<li><a href="http://www.torfox.org/">Torfox</a> (2009)</li>
61 
+    <li><a href="http://www.shinjiru.com/">Shinjiru Technology</a> (2009-2010)</li>
62 
+  </ul>
63 
+
64 
+<h3>Bisherige Sponsoren</h3>
65 
+<p>We greatly appreciate the support provided by our past sponsors in keeping
66 
+the pre-501(c)(3) Tor Project progressing through our ambitious goals:</p>
67 
+	<ul>
68 
+		<li><a href="https://www.eff.org/">Electronic Frontier Foundation</a>
69 
+(2004-2005)</li>
70 
+		<li><a href="http://chacs.nrl.navy.mil/">DARPA and ONR via Naval Research
71 
+Laboratory</a> (2001-2006)</li>
72 
+		<li><a href="http://www.cyber-ta.org/">Cyber-TA Projekt</a> (2006-2008)</li>
73 
+		<li>Bell Security Solutions Inc (2006)</li>
74 
+		<li><a href="http://www.omidyar.net/">Omidyar Network Enzyme Grant</a> (2006)</li>
75 
+		<li><a
76 
+href="http://seclab.cs.rice.edu/lab/2005/08/01/seclab-awarded-grant-to-study-security-of-p2p/">NSF
77 
+via Rice Universität</a> (2006-2007)</li>
78 
+	</ul>
79 
+<p>Grosser Dank geht an alle Personen und Gruppen, die Tor bisher ermöglicht
80 
+haben. Ganz besonders bedanken möchten wir uns bei den einzelnen
81 
+Freiwilligen, welche nicht-monetäre Unterstützung geleistet haben:
82 
+Programmieren, Testen, Dokumentieren, Ausbildung, Forschung und Betreiben
83 
+der Tor Knoten aus denen dieses Netzwerk besteht.
84 
+</p>
85 
+
86 
+</div>
87 
+
88 
+
89 
+
90 
+#include <foot.wmi>
docs/.deps/.stamp
Zeige Datei @ 2a9aaa802
docs/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,5 @@
1 
+include $(WMLBASE)/Makefile.common
2 
+TORSVNSTABLE = $(WMLBASE)/tor-stable
3 
+TORGIT = $(WMLBASE)/tor/.git
4 
+STABLETAG = tor-0.2.1.26
5 
+DEVTAG = tor-0.2.2.13-alpha
docs/ar/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/bms/debian.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,176 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22268 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian>">Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <h2><a class="anchor" href="#debian">ေရြးခ်ယ္ခ်က္ (၁) : Debian Lenny ရွိ Tor ၊
15 
+    Debian sid ၊ Debian testing</a></h2>
16 
+    <br />
17 
+
18 
+    <p>
19 
+    If you're using Debian stable (lenny), unstable (sid), or testing (squeeze),
20 
+    just run<br /> <tt>apt-get install tor tor-geoipdb</tt> as root.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    Tor ၏ ေနာက္ဆံုးေပၚ versions မ်ားကိုအျမဲေပးႏိုင္သည္ဟုအာမမခံႏိုင္ေသာ္လည္း၊
25 
+    အေရးၾကီးေသာ လံုျခံဳေရးႏွင့္သတ္ဆိုင္သည့္ ျပင္ဆင္မွဳမ်ားကိုရရွိမည္ျဖစ္ပါသည္။
26 
+    ေနာက္ဆံုး ေပၚ Tor version ကိုအျမဲတေစသံုးလိုပါက၊ ေအာက္မွ ေရြးခ်ယ္ခ်က္ (၂)
27 
+    ကိုၾကည့္ပါ။
28 
+    </p>
29 
+
30 
+    <p>
31 
+    Tor အလုပ္လုပ္ေနပါျပီ။ "Tor on Linux/Unix" ထည့္သြင္းျခင္း၏ <a href="<page
32 
+    docs/tor-doc-unix>#polipo">အဆင့္(၂)</a> သို႔ထပ္သြားပါရန္။
33 
+    </p>
34 
+
35 
+    <hr /> <a id="ubuntu"></a> <a id="packages မ်ား"></a>
36 
+    <h2><a class="anchor" href="#ubuntu">ေရြးခ်ယ္ခ်က္ (၂) : Tor on Ubuntu or
37 
+    Debian</a></h2>
38 
+    <br />
39 
+
40 
+    <p>
41 
+    <b>Ubuntu's universe တြင္ ဤ package မ်ားကိုမသံုးပါႏွင့္။</b> ၄င္းတို႔သည္
42 
+    ျပင္ဆင္မွဳမ်ားမရွိဘဲ out of date ျဖစ္ေနပါသည္။ ထို႔ေၾကာင့္ ၄င္းကိုသံုးလွ်င္
43 
+    software တည္ျငိမ္မွဳမရွိျပီး လံုျခံေရးဆိုင္ရာ ျပင္ဆင္မွဳမ်ားကိုလည္း
44 
+    ျပဳလုပ္၍မရႏိုင္ပါ။
45 
+    </p>
46 
+
47 
+    <p>
48 
+    You'll need to set up our package repository before you can fetch
49 
+    Tor. First, you need to figure out the name of your distribution. If you're
50 
+    using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty", 8.10 is
51 
+    "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's "etch",
52 
+    and Debian Lenny is "lenny". Then add this line to your
53 
+    <tt>/etc/apt/sources.list</tt> file:<br />
54 
+    <pre>
55 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
56 
+    </pre>
57 
+    where you put the codename of your distribution (i.e. etch, lenny, sid,
58 
+    karmic, jaunty, intrepid, hardy or whatever it is) in place of
59 
+    &lt;DISTRIBUTION&gt;.
60 
+    </p>
61 
+
62 
+    <p>
63 
+    Then add the gpg key used to sign the packages by running the following
64 
+    commands at your command prompt:
65 
+    <pre>
66 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
67 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
68 
+    </pre>
69 
+    Now refresh your sources and install Tor by running the following commands
70 
+    at your command prompt:
71 
+    <pre>
72 
+    apt-get update
73 
+    apt-get install tor tor-geoipdb
74 
+    </pre>
75 
+    </p>
76 
+
77 
+    <p>
78 
+    Tor အလုပ္လုပ္ေနပါျပီ။ "Tor on Linux/Unix" ထည့္သြင္းျခင္း၏ <a href="<page
79 
+    docs/tor-doc-unix>#polipo">အဆင့္(၂)</a> သို႔ထပ္သြားပါရန္။
80 
+    </p>
81 
+
82 
+    <p style="font-size: small">
83 
+    The DNS name <code>deb.torproject.org</code> is actually a set of
84 
+    independent servers in a DNS round robin configuration.  If you for some
85 
+    reason cannot access it you might try to use the name of one of its part
86 
+    instead.  Try <code>deb-master.torproject.org</code>,
87 
+    <code>mirror.netcologne.de</code> or <code>tor.mirror.youam.de</code>.
88 
+    </p>
89 
+
90 
+    <hr /> <a id="development"></a>
91 
+    <h2><a class="anchor" href="#development">ေရြးခ်ယ္မွဳ ၃: Tor ၏ development
92 
+    branch ကို Debian or Ubuntu တြင္အသံုးျပဳျခင္း</a></h2>
93 
+    <br />
94 
+
95 
+    <p>Tor ၏ <a href="<page download/download>#packagediff">development branch</a>
96 
+    ကိုအစားထိုးသံုးလိုပါက ( Feature ႏွင့္ Bug မ်ားပိုမ်ားႏိုင္ပါသည္),
97 
+    <tt>/etc/apt/sources.list</tt> file:<br /> တြင္ line
98 
+    အသစ္မ်ားျဖင့္ထပ္မံအသံုးျပဳရပါလိမ့္မည္။
99 
+    <pre>
100 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
101 
+    deb     http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
102 
+    </pre>
103 
+    where you again substitute the name of your distro (etch, lenny, sid,
104 
+    karmic, jaunty, intrepid, hardy) in place of &lt;DISTRIBUTION&gt;.
105 
+    </p>
106 
+
107 
+    <p>
108 
+    Then run the following commands at your command prompt:
109 
+    <pre>
110 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
111 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
112 
+    apt-get update
113 
+    </pre>
114 
+    </p>
115 
+
116 
+    <p>
117 
+    Tor အလုပ္လုပ္ေနပါျပီ။ "Tor on Linux/Unix" ထည့္သြင္းျခင္း၏ <a href="<page
118 
+    docs/tor-doc-unix>#polipo">အဆင့္(၂)</a> သို႔ထပ္သြားပါရန္။
119 
+    </p>
120 
+
121 
+    <hr /> <a id="source"></a>
122 
+    <h2><a class="anchor" href="#source">source မွတည္ေဆာက္ျခင္း</a></h2>
123 
+    <br />
124 
+
125 
+    <p>
126 
+    ကိုယ္ပိုင္ debs မ်ားကိုတည္ေဆာက္လိုပါက သင့္ေလွ်ာ္ေသာ <tt>deb-src</tt>
127 
+    ကို<tt>sources.list</tt> တြင္ထည့္သြင္းရပါမည္။
128 
+    <pre>
129 
+    # For the stable version.
130 
+    # For the unstable version.
131 
+
132 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
133 
+
134 
+
135 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
136 
+    deb-src http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
137 
+    </pre>
138 
+    Tor: တည္ေဆာက္ရန္ ကိုယ္ပိုင္ debs ႏွင့္ packages မ်ားကိုလည္း
139 
+    ထည့္သြင္းအသံုးျပဳရန္ လိုအပ္ပါလိမ့္မည္။
140 
+    <pre>
141 
+    apt-get install build-essential fakeroot devscripts
142 
+    apt-get build-dep tor
143 
+    </pre>
144 
+    Tor ကို ~/debian-packages: မ်ားတြင္ တည္ေဆာက္ႏိုင္ပါသည္။
145 
+    <pre>
146 
+    mkdir ~/debian-packages; cd ~/debian-packages
147 
+    apt-get source tor
148 
+    cd tor-*
149 
+    debuild -rfakeroot -uc -us
150 
+    cd ..
151 
+    </pre>
152 
+    Package အသစ္ကိုထည့္သြင္းအသံုးျပဳႏိုင္ပါျပီ။
153 
+    <pre>
154 
+    sudo dpkg -i tor_*.deb
155 
+    </pre>
156 
+    </p>
157 
+
158 
+    <p>
159 
+    Tor အလုပ္လုပ္ေနပါျပီ။ "Tor on Linux/Unix" ထည့္သြင္းျခင္း၏ <a href="<page
160 
+    docs/tor-doc-unix>#polipo">အဆင့္(၂)</a> သို႔ထပ္သြားပါရန္။
161 
+    </p>
162 
+
163 
+    <hr />
164 
+
165 
+    <p>ဤစာရြက္စာတမ္းႏွင့္ပတ္သတ္၍ အၾကံေပးလိုပါက ကၽြႏု္ပ္တို႔ကို <a href="<page
166 
+    about/contact>">ဆက္သြယ္လိုက္ပါ</a>. ေက်းဇူးတင္ပါတယ္။</p>
167 
+  </div>
168 
+  <!-- END MAINCOL -->
169 
+  <div id = "sidecol">
170 
+#include "side.wmi"
171 
+#include "info.wmi"
172 
+  </div>
173 
+  <!-- END SIDECOL -->
174 
+</div>
175 
+<!-- END CONTENT -->
176 
+#include <foot.wmi>
docs/bms/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/bms/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,225 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Mac OS X တြင္ <a href="<page index>">Tor</a> သံုးစဲြသူအျဖစ္ လုပ္ေဆာင္ျခင္း</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>ဤညႊန္ၾကားခ်က္တို႕မွာ Mac OS X အေပၚတြင္ Tor သံုးစဲြသူအျဖစ္ ထည့္သြင္းရန္
18 
+    လုပ္ေဆာင္ျခင္းအတြက္  ညႊန္ၾကားခ်က္မ်ား ျဖစ္သည္။ သင္သည္ အျခားအေပၚတြင္
19 
+    သတင္းအခ်က္အလက္ သြားလာမႈမ်ားကို ထပ္ဆင့္လႊင့္ျခင္းျဖင့္ ကြန္ယက္ကုိ
20 
+    ၾကီးထြားေအာင္(ေက်းဇူးျပဳ၍ လုပ္ေဆာင္ပါ) ျပဳလုပ္မည္ဆိုပါက၊ ေက်းဇူးျပဳ၍<a
21 
+    href="<page docs/tor-doc-relay>">ထပ္ဆင့္လႊင့္မႈ ျပင္ဆင္သတ္မွတ္ျခင္း</a>
22 
+    လမ္းညႊန္ကို ဖတ္႐ႈပါ။</b>
23 
+    </p>
24 
+
25 
+    <hr />
26 
+    <a id="installing"></a>
27 
+    <h2><a class="anchor" href="#installing">အဆင့္ တစ္: Download လုပ္၍ Tor ကုိ
28 
+    ထည့္သြင္းပါ</a></h2>
29 
+    <br />
30 
+
31 
+    <p>
32 
+    The install for Macintosh OS X bundles <a href="<page index>">Tor</a>, <a
33 
+    href="<page projects/vidalia>">Vidalia</a> (a graphical interface for Tor), <a
34 
+    href="<page projects/torbutton>">Torbutton</a>, and <a
35 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (a web
36 
+    proxy)  into one package, with the four applications pre-configured to work
37 
+    together.  Download either the <a
38 
+    href="../<package-osx-bundle-stable>">stable</a> or the <a
39 
+    href="../<package-osx-bundle-alpha>">experimental</a> version of the OS X
40 
+    bundle for Intel, or look for more options on the <a href="<page
41 
+    download/download>">download page</a>.
42 
+    </p>
43 
+
44 
+    <p>dmg ကုိ ေဒါင္းလုဒ္လုပ္၍ ျပီးသည္ႏွင့္ ကလစ္ႏွစ္ခ်က္ႏိွပ္၍ စတင္ပါ။ Finder တြင္
45 
+    ယခု Vidala Bundle ကုိ ဖြင့္ရန္ေနရာကို သြားပါ။ Vidalia onion icon ကုိ
46 
+    ရုိးရွင္းစြာ drag ဆဲြယူ၍ Applications folder ထဲသို႕ ဆဲြခ်ျခင္းျဖင့္
47 
+    ထည့္သြင္းမႈကုိ လြယ္ကူစြာ ျပဳလုပ္ႏုိင္ပါသည္။ ေရြးခ်ယ္စရာရွိသည္မွာ "install
48 
+    torbutton" script ကုိ ကလစ္ႏွစ္ခ်က္ႏွိပ္၍ torbutton ကုိ Firefox သို႕
49 
+    ထည့္သြင္းႏုိင္ပါသည္။ Torbutton ကုိ Mozilla Add-ons တြင္ "torbutton" ဟု
50 
+    ရွာေဖြျခင္းျဖင့္လည္း ရရွိႏုိင္ပါသည္။</p>
51 
+
52 
+    <p>ထည့္သြင္းျခင္း ျပီးဆံုးပါက Vidalia icon ကုိ Applications folder မွ
53 
+    ေရြးခ်ယ္ျခင္းျဖင့္ စတင္ႏုိင္ပါသည္။ အနီေရာင္ X ပံုစံျပေနေသာ မွိန္ေနသည့္
54 
+    ၾကက္သြန္ပံုစံသည္ လက္ရွိတြင္ Tor အလုပ္လုပ္မေနေၾကာင္း ျပသပါသည္။ screen
55 
+    ၏အေပၚဘက္တြင္ ရွိေသာ "Tor" menu မွ Start ကုိ ေရြးခ်ယ္ျခင္းျဖင့္ Tor ကုိ
56 
+    စတင္ႏုိင္ပါသည္။
57 
+    </p>
58 
+
59 
+    <p>Tor အလုပ္လုပ္ေဆာင္ေနခ်ိန္တြင္ Vidalia ၏ အုိင္ကြန္သည္ ေအာက္ေဖာ္ျပပါအတုိင္း
60 
+    ရွိေနပါမည္။
61 
+    </p>
62 
+
63 
+    <p><img alt="vidalia running tor"
64 
+    src="../img/screenshot-osx-vidalia.png"
65 
+    border="1"/></p>
66 
+
67 
+    <p>Polipo သည္ Tor အစုအေဝး၏ ထည့္သြင္းမႈတြင္ အစိတ္အပိုင္းတစ္ခုအျဖစ္
68 
+    ထည့္သြင္းေပးပါသည္။ ၎ကို ထည့္သြင္းျပီးသည့္အခါ ကြန္ပ်ဴတာ ျပန္လည္စတင္သည္ႏွင့္
69 
+    အလိုအေလ်ာက္ စတင္ပါလိမ့္မည္။ Polipo ကုိ Tor &mdash အသံုးျပဳရန္အတြက္
70 
+    ျပင္ဆင္သတ္မွတ္ရန္ မလိုအပ္ပါ။ Tor အတြက္ ျပင္ဆင္သတ္မွတ္ျခင္းမ်ားကုိ
71 
+    ထည့္သြင္းမႈ အစုအေဝးတြင္ အစိတ္အပိုင္းတစ္ခုအျဖစ္ ထည့္သြင္းျပီးသား
72 
+    ျဖစ္ေသာေၾကာင့္ ျဖစ္ပါသည္။
73 
+    </p>
74 
+
75 
+    <hr />
76 
+    <a id="using"></a>
77 
+    <h2><a class="anchor" href="#using">အဆင့္ ႏွစ္ : သင့္အသံုးခ် ေဆာ့ဝဲမ်ားကို Tor
78 
+    အသံုးျပဳရန္ ျပင္ဆင္ပါ</a></h2>
79 
+    <br />
80 
+
81 
+    <p>Tor ႏွင့္ Polipo တို႕ကုိ ထည့္သြင္းျပီးပါက သင့္အသံုးခ်ေဆာ့ဝဲမ်ားကုိ
82 
+    အသံုးျပဳႏုိင္ရန္ ျပင္ဆင္ရပါမည္။ ပထမအဆင့္မွာ Web ၾကည့္ရႈျခင္းအတြက္
83 
+    ျပင္ဆင္ျခင္း ျဖစ္ပါသည္။</p>
84 
+
85 
+    <p>သင့္အတြက္ အေကာင္းဆံုး လံုျခံဳမႈရႏုိင္ရန္ Tor ပါဝင္ေသာ Firefox ႏွင့္
86 
+    Torbutton တို႕ကုိ အသံုးျပဳသင့္ပါသည္။ Torbutton မွာ ထည့္သြင္းျပီး ျဖစ္ပါသည္။
87 
+    အနီေရာင္ "Tor Disabled" ေျပာင္းလဲမႈ ခလုပ္ကုိ ႏွိပ္၍ Tor ကို ဖြင့္ပါ။
88 
+    ျပီးလွ်င္ ေအာက္ပါတုိ႕ကုိ သတ္မွတ္ပါ : </p>
89 
+
90 
+    <p><img alt="Torbutton plugin for Firefox"
91 
+    src="../img/screenshot-torbutton.png"
92 
+    border="1"/></p>
93 
+
94 
+    <p>
95 
+    အျခား ကြန္ပ်ဴတာတြင္ Firefox ကုိ အသံုးျပဳမည္ဟု အစီအစဥ္ရွိပါက <a
96 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">မတူညီေသာ
97 
+    ကြန္ပ်ဴတာတြင္ Tor လုပ္ေဆာင္ျခင္းအတြက္ ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> ကုိ
98 
+    ၾကည့္ရႈပါ။
99 
+    </p>
100 
+
101 
+    <p>HTTP proxies ကုိ ေထာက္ပံ့ေသာ အျခား အသံုးခ်ေဆာ့ဝဲမ်ားကုိ Tor
102 
+    လုပ္ေဆာင္ႏိုင္ရန္ Polipo ကုိသာ ညႊန္ျပေပးပါ(၎မွာ localhost port 8118
103 
+    ျဖစ္ပါသည္။) SOCKS ကုိ တုိက္ရုိက္ အသံုးျပဳရန္(သတင္းခ်က္ခ်င္းပို႕ျခင္းမ်ား၊
104 
+    Jabber, IRC စသည္ျဖင့္) Tor(localhost port 9050) သို႕
105 
+    တုိက္ရုိက္ညႊန္ျပႏုိင္ပါသည္။ သို႕ေသာ္ <a
106 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">ဤ
107 
+    ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> ကုိ ဘာေၾကာင့္ အႏၱရာယ္ရွိႏုိင္ေၾကာင္း
108 
+    သိရွိႏိုင္ရန္ ၾကည့္ရႈပါ။ SOCKS ႏွင့္ HTTP ပါ ေထာက္ပံ့မႈမရွိေသာ
109 
+    အသံုးခ်ေဆာ့ဝဲမ်ားအတြက္ <a
110 
+    href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a> သို႕မဟုတ္
111 
+    <a href="http://www.dest-unreach.org/socat/">socat</a>တြင္ ၾကည့္ပါ။</p>
112 
+
113 
+    <p>အျခားအသံုးခ်ေဆာ့ဝဲမ်ားကုိ Tor လုပ္ေဆာင္ႏုိင္ရန္ မည္သို႕လုပ္ေဆာင္ရမည္ကုိ <a
114 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">မည္သို႕
115 
+    Tor လုပ္ေဆာင္ႏုိင္ေစမည္လဲ</a> တြင္ၾကည့္ရႈပါ။
116 
+    </p>
117 
+
118 
+    <hr />
119 
+    <a id="verify"></a>
120 
+    <h2><a class="anchor" href="#verify">အဆင့္ သံုး : အလုပ္လုပ္ေၾကာင္း
121 
+    ေသခ်ာပါေစ။</a></h2>
122 
+    <br />
123 
+
124 
+    <p>
125 
+    ေနာက္တစ္ဆင့္တြင္ သင့္ browser တြင္ Tor ႏွင့္ သံုးစဲြၾကည့္ရႈ၍ သင့္ IP
126 
+    လိပ္စာသည္ အမည္ဝွက္မႈ လုပ္ေဆာင္ထားေၾကာင္း ေသခ်ာပါေစ။ <a
127 
+    href="https://check.torproject.org/">Tor စစ္ေဆးၾကည့္ရႈသူ</a> ကုိ ကလစ္ႏွိပ္၍
128 
+    သင္ Tor အသံုးျပဳေနျခင္း ဟုတ္ မဟုတ္ စစ္ေဆးပါ။ (ဤ site အလုပ္မလုပ္ပါက၊ <a
129 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">ဤ
130 
+    ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> တြင္ သင့္ Tor ကုိ မည္သို႕စမ္းသပ္ရမည္ဆိုသည့္
131 
+    အၾကံျပဳခ်က္မ်ားကုိ ၾကည့္ရႈပါ။)
132 
+    </p>
133 
+
134 
+    <p>သင့္တြင္ သင့္ကြန္ပ်ဴတာကို ကုိယ္တုိင္ဆက္သြယ္ရန္ ကန္႕သတ္ထားေသာ တစ္ကုိယ္ေရသံုး
135 
+    Firewall ရွိပါက သင့္ စက္တြင္းမွ အသံုးခ်ေဆာ့ဝဲမ်ားကုိ စက္တြင္းမွ port 8118
136 
+    ႏွင့္ port 9050 တို႕သို႕ ဆက္သြယ္ႏုိင္ေၾကာင္း ေသခ်ာပါေစ။ သင့္ Firewall မွ
137 
+    အျပင္သို႕ ဆက္သြယ္မႈမ်ားကုိ ပိတ္ဆို႕ထားပါက အေပါက္တစ္ခုျပဳလုပ္၍ TCP ports
138 
+    မ်ားျဖစ္ေသာ 80 ႏွင့္ 443 တုိ႕ကုိ ဆက္သြယ္ႏုိင္ေစရန္ ျပဳလုပ္ပါ။ ျပီးလွ်င္ <a
139 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">ဤ
140 
+    ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> ကို ၾကည့္ရႈပါ။
141 
+    </p>
142 
+
143 
+    <p>ဤသည္တို႕ႏွင့္ အလုပ္မလုပ္ေသးလွ်င္ <a
144 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">ဤ
145 
+    ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> ကုိ အရိပ္အျမြက္သိရွိႏုိင္ရန္ ၾကည့္ရႈပါ။</p>
146 
+
147 
+    <p>
148 
+    အလုပ္လုပ္သည္ႏွင့္ <a href="<page download/download>#Warning">Tor မွ မည္သည္တို႕ကုိ
149 
+    လုပ္ေဆာင္ႏုိင္၍ မည္သည္တို႕ကုိ မလုပ္ေဆာင္ႏိုင္ပါ</a> တို႕ကို ဆက္လက္ ေလ့လာပါ။
150 
+    </p>
151 
+
152 
+    <hr />
153 
+    <a id="server"></a> <a id="relay"></a>
154 
+    <h2><a class="anchor" href="#relay">အဆင့္ ေလး : ထပ္ဆင့္လႊင့္သူအျဖစ္
155 
+    ျပင္ဆင္သတ္မွတ္ပါ။</a></h2>
156 
+    <br />
157 
+
158 
+    <p>Tor ကြန္ယက္သည္ ေစတနာ့ဝန္ထမ္းမ်ား၏ လိုင္းအက်ယ္လွဴဒါန္းမႈကို မီွခိုရပါသည္။
159 
+    ထပ္ဆင့္လႊင့္သူ ပိုမုိမ်ားျပားေလ Tor ကြန္ယက္ပိုမိုျမန္ဆန္ေလ ျဖစ္ပါသည္။
160 
+    သင့္တြင္ လမ္းတိုင္းအတြက္ အနည္းဆံုး 20 kilobytes/s ရွိလွ်င္ သင့္ Tor ကုိ
161 
+    ထပ္ဆင့္လႊင့္သူအျဖစ္ ျပင္ဆင္သတ္မွတ္၍ ကူညီေပးပါ။ ကၽြႏု္ပ္တို႕တြင္ Tor
162 
+    ထပ္ဆင့္လႊင့္သူမ်ားကို လြယ္ကူေစရန္ႏွင့္ သက္သာအဆင္ေျပေစရန္
163 
+    လိုင္းအက်ယ္ႏႈန္းကန္႕သတ္ျခင္း၊ အလဲြသံုးမႈ ေစာဒကမ်ားမွ လြတ္ကင္းရန္
164 
+    အထြက္မူဝါဒမ်ား၊ ေျပာင္းလဲေနေသာ IP လိပ္စာမ်ားစသည္ျဖင့္ စီစဥ္ထားရွိပါသည္။</p>
165 
+
166 
+    <p>အင္တာနက္ေပၚတြင္ ထပ္ဆင့္လႊင့္သူမ်ား ေနရာအႏွံ႕ထားရွိျခင္းသည္ Tor
167 
+    အသံုးျပဳသူမ်ားကို ပိုမိုလံုျခံဳေစပါသည္။ အေဝးရွိ site မ်ားမွ သင့္ကြန္ပ်ဴတာမွ
168 
+    ဆက္သြယ္မႈ စတင္သည္ သို႕မဟုတ္ အျခားသူတို႕မွ ထပ္ဆင့္လႊင့္သည္တုိ႕ကုိ
169 
+    မသိရွိႏိုင္သျဖင့္ <a
170 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">သင္ကုိယ္တုိင္
171 
+    ပိုမိုေကာင္းမြန္ေသာ အမည္ဝွက္မႈကို ရရွိႏိုင္ပါသည္။</a></p>
172 
+
173 
+    <p><a href="<page docs/tor-doc-relay>">ထပ္ဆင့္လႊင့္သူအျဖစ္
174 
+    ျပင္ဆင္သတ္မွတ္ျခင္း</a> လမ္းညႊန္တြင္ ပိုမို ဖတ္ရႈပါ။</p>
175 
+
176 
+    <hr />
177 
+    <a id="uninstall"></a>
178 
+    <h2><a class="anchor" href="#uninstall">Tor ႏွင့္ Privoxy ကုိ ဘယ္လို
179 
+    ဖယ္ထုတ္မလဲ</a></h2>
180 
+    <br />
181 
+
182 
+    <p>ေဆာ့ဝဲ အစုအေဝး သင့္ကြန္ပ်ဴတာမွ ဖယ္ရွားရန္ နည္းလမ္းႏွစ္ခု ရွိပါသည္။ Finder
183 
+    ကုိ အသံုးျပဳ၍ သို႕မဟုတ္ command သုိ႕မဟုတ္ Terminal-based ဖယ္ရွားမႈကုိ
184 
+    အသံုးျပဳ၍ ဖယ္ရွားႏုိင္ပါသည္။ OSX မွ Tor ကုိ ဖယ္ရွားလိုလွ်င္ ေအာက္ပါအတုိင္း
185 
+    ျပဳလုပ္ပါ :</p>
186 
+
187 
+    <p>သင့္ အသံုးခ် ေဆာ့ဝဲ၏ ပေရာ့စီ သတ္မွတ္ခ်က္မ်ားကုိ မူလ တန္ဖုိးမ်ားသို႕
188 
+    ေျပာင္းလဲပါ။ Tor ကုိ အသံုးျပဳျခင္းမွ ရပ္တန္႕လိုျခင္းသာ ျဖစ္လွ်င္ ဤေနရာတြင္
189 
+    ရပ္တန္႕ႏုိင္ပါျပီ။</p>
190 
+
191 
+    <p>Tor ကုိ လံုးဝအျပည့္အစံု ဖယ္ရွားလိုျပီး သင့္တြင္ ထိန္းခ်ဳပ္သူအဆင့္ account
192 
+    ရွိလွ်င္ ေအာက္ပါအတုိင္း ေဆာင္ရြက္ပါ :</p>
193 
+
194 
+    <ol>
195 
+    <li>Finder ကုိ ဖြင့္၍ Applications ကုိ ကလစ္ႏိွပ္ပါ။</li>
196 
+    <li>/Applications/Vidalia ကုိ Trash သို႕ ဆဲြထည့္လုိက္ပါ။</li>
197 
+    <li>/Library/Torbutton ကုိ သင့္စနစ္မွ ဖယ္ရွားပါ။</li>
198 
+    <li>သင့္ home directory တြင္ Library သုိ႕သြား၍ Vidalia directory ကုိ ဖယ္ရွားပါ။</li>
199 
+    </ol>
200 
+
201 
+    <p>Tor, Vidalia ႏွင့္ Polipo တို႕ သင့္စနစ္မွ လံုးဝဖယ္ရွားျပီး ျဖစ္ပါသည္။</p>
202 
+
203 
+    <p>command line သို႕မဟုတ္ Terminal ႏွင့္ သင္ အကၽြမ္းတဝင္ရွိပါက ေအာက္ပါအတုိင္း
204 
+    ကုိယ္တုိင္ ဖယ္ရွားႏိုင္ပါသည္။</p>
205 
+    <ul>
206 
+    <li>/Applications/Vidalia.app/</li>
207 
+    <li>/Library/Torbutton/</li>
208 
+    <li>~/Library/Vidalia</li>
209 
+    <li>~/.tor</li>
210 
+    </ul>
211 
+
212 
+    <hr />
213 
+
214 
+    <p>သင့္တြင္ ဤစာရြက္စာတမ္း ပိုမုိေကာင္းမြန္ေစႏုိင္ေသာ အၾကံဳျပဳခ်က္မ်ား ရွိပါက <a
215 
+    href="<page about/contact>"> ကၽြႏု္ပ္တို႕ကုိ ေပးပို႕ပါ။</a> ေက်းဇူးတင္ပါသည္ !</p>
216 
+  </div>
217 
+  <!-- END MAINCOL -->
218 
+  <div id = "sidecol">
219 
+#include "side.wmi"
220 
+#include "info.wmi"
221 
+  </div>
222 
+  <!-- END SIDECOL -->
223 
+</div>
224 
+<!-- END CONTENT -->
225 
+#include <foot.wmi>
docs/bms/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,200 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Microsoft Windows တြင္ <a href="<page index>">Tor</a> သံုးစဲြသူအျဖစ္
14 
+    လုပ္ေဆာင္ျခင္း</h1>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>ဤညႊန္ၾကားခ်က္တို႕မွာ Windows (2000, XP, Vista, 7, and Server Editions)
19 
+    တို႕အေပၚတြင္ Tor သံုးစဲြသူအျဖစ္ ထည့္သြင္းရန္ လုပ္ေဆာင္ျခင္းအတြက္
20 
+    ညႊန္ၾကားခ်က္မ်ား ျဖစ္သည္။ သင္သည္ အျခားအေပၚတြင္ သတင္းအခ်က္အလက္
21 
+    သြားလာမႈမ်ားကို ထပ္ဆင့္လႊင့္ျခင္းျဖင့္ ကြန္ယက္ကုိ ၾကီးထြားေအာင္(ေက်းဇူးျပဳ၍
22 
+    လုပ္ေဆာင္ပါ) ျပဳလုပ္မည္ဆိုပါက၊ ေက်းဇူးျပဳ၍<a href="<page
23 
+    docs/tor-doc-relay>">ထပ္ဆင့္လႊင့္မႈ ျပင္ဆင္သတ္မွတ္ျခင္း</a> လမ္းညႊန္ကို
24 
+    ဖတ္႐ႈပါ။</b>
25 
+    </p>
26 
+
27 
+    <p>Freedom House has produced a video on how to install Tor.  You can view it
28 
+    at <a
29 
+    href="http://media.torproject.org/video/2009-install-and-use-tor.ogv">How to
30 
+    install Tor on Windows</a>.  Know of a better video, or one translated into
31 
+    your language? Let us know!</p>
32 
+
33 
+    <div class="center">
34 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor.ogv" autobuffer="true" controls="controls"></video></p>
35 
+    </div>
36 
+
37 
+    <hr /> <a id="installing"></a>
38 
+    <h2><a class="anchor" href="#installing">အဆင့္ တစ္: Download လုပ္၍ Tor ကုိ
39 
+    ထည့္သြင္းပါ</a></h2>
40 
+    <br />
41 
+
42 
+    <p>
43 
+    Microsoft Windows စုစည္းမႈတြင္ <a href="<page index>">Tor</a>, <a
44 
+    href="<page projects/vidalia>">Vidalia </a>(Tor အတြက္ GUI တစ္ခု)၊ <a
45 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> (Mozilla
46 
+    Firefox အတြက္ plugin တစ္ခု) ႏွင့္ <a
47 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (Web proxy
48 
+    တစ္ခု) တို႕ကုိ အတူတကြ အလုပ္လုပ္ႏိုင္ရန္ ၾကိဳတင္ျပင္ဆင္ထားေသာ
49 
+    စုစည္းမႈတစ္ခုထဲတြင္ ထည့္သြင္းထားပါသည္။ Windows ၏ <a
50 
+    href="../<package-win32-bundle-stable>">တည္ျငိမ္ေသာ</a> သို႕မဟုတ္ <a
51 
+    href="../<package-win32-bundle-alpha>">စမ္းသပ္ဆဲျဖစ္ေသာ</a>မူကုိ Download
52 
+    လုပ္ပါ။ သို႕မဟုတ္ <a href="<page download/download>">download
53 
+    စာမ်က္ႏွာ</a>တြင္ပိုမိုေရြးခ်ယ္ရန္ ၾကည့္ရႈပါ။
54 
+    </p>
55 
+
56 
+    <img alt="tor installer splash page"
57 
+    src="../img/screenshot-win32-installer-splash.png" />
58 
+
59 
+    <p>သင့္ထံတြင္ ယခင္ ထည့္သြင္းျပီး ျဖစ္ေသာ Tor၊ Vidalia သို႕မဟုတ္ Polipo တို႕
60 
+    ရွိပါက ေအာက္တြင္ျပထားေသာ ေနရာတြင္ သင္ ထည့္သြင္းရန္မလိုေသာ
61 
+    အစိတ္အပိုင္းမ်ားကို မေရြးခ်ယ္ဘဲ ေနႏိုင္ပါသည္။
62 
+    </p>
63 
+
64 
+    <img alt="select components to install"
65 
+    src="../img/screenshot-win32-installer-components.png" />
66 
+
67 
+    <p>ထည့္သြင္းမႈ ျပီးစီးပါက သင္ေရြးခ်ယ္ထားေသာ အစိတ္အပိုင္းမ်ားသည္ အလိုအေလ်ာက္
68 
+    စတင္ပါလိမ့္မည္။
69 
+    </p>
70 
+
71 
+    <p>Tor သည္ ပံုမွန္အားျဖင့္ သံုးစဲြသူ အျဖစ္ ျပင္ဆင္သတ္မွတ္ထားပါသည္။ ၎သည္
72 
+    ျပင္ဆင္သတ္မွတ္မႈ ဖုိင္ ပါဝင္ျပီး ျဖစ္၍ အမ်ားစုေသာသူတို႕အတြက္ ခ်ိန္ညွိမႈမ်ား
73 
+    ျပဳလုပ္ရန္ မလိုအပ္ပါ။ Tor ကို ယခု ထည့္သြင္းျပီးပါျပီ။
74 
+    </p>
75 
+
76 
+    <hr /> <a id="using"></a>
77 
+    <h2><a class="anchor" href="#using">အဆင့္ ႏွစ္: သင့္အသံုခ်ေဆာ့ဝဲမ်ားကုိ Tor
78 
+    အသံုးျပဳရန္ ျပင္ဆင္ပါ</a></h2>
79 
+    <br />
80 
+
81 
+    <p>Tor ႏွင့္ Polipo တို႕ကုိ ထည့္သြင္းျပီးပါက သင့္အသံုးခ်ေဆာ့ဝဲမ်ားကုိ
82 
+    အသံုးျပဳႏုိင္ရန္ ျပင္ဆင္ရပါမည္။ ပထမအဆင့္မွာ Web ၾကည့္ရႈျခင္းအတြက္
83 
+    ျပင္ဆင္ျခင္း ျဖစ္ပါသည္။</p>
84 
+
85 
+    <p>သင့္အတြက္ အေကာင္းဆံုး လံုျခံဳမႈရႏုိင္ရန္ Tor ပါဝင္ေသာ Firefox ႏွင့္
86 
+    Torbutton တို႕ကုိ အသံုးျပဳသင့္ပါသည္။ စုစည္းမႈက ထည့္သြင္းေပးသည္မွာ သင့္အတြက္
87 
+    <a href="https://addons.mozilla.org/firefox/2275/">Torbutton
88 
+    plugin</a>ျဖစ္ပါသည္။ သင့္ Firefox ကုိ ျပန္လည္စတင္ပါ။ ျပီးလွ်င္
89 
+    ေအာက္ပါတို႕ကုိ သတ္မွတ္ပါ :
90 
+    </p>
91 
+
92 
+    <img alt="Torbutton plugin for Firefox"
93 
+    src="../img/screenshot-torbutton.png" border="1"/> <br />
94 
+
95 
+    <p>
96 
+    အျခား ကြန္ပ်ဴတာတြင္ Firefox ကုိ အသံုးျပဳမည္ဟု အစီအစဥ္ရွိပါက <a
97 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">မတူညီေသာ
98 
+    ကြန္ပ်ဴတာတြင္ Tor လုပ္ေဆာင္ျခင္းအတြက္ ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> ကုိ
99 
+    ၾကည့္ရႈပါ။
100 
+    </p>
101 
+
102 
+    <p>HTTP proxies ကုိ ေထာက္ပံ့ေသာ အျခား အသံုးခ်ေဆာ့ဝဲမ်ားကုိ Tor
103 
+    လုပ္ေဆာင္ႏိုင္ရန္ Polipo ကုိသာ ညႊန္ျပေပးပါ(၎မွာ localhost port 8118
104 
+    ျဖစ္ပါသည္။) SOCKS ကုိ တုိက္ရုိက္ အသံုးျပဳရန္(သတင္းခ်က္ခ်င္းပို႕ျခင္းမ်ား၊
105 
+    Jabber, IRC စသည္ျဖင့္) Tor(localhost port 9050) သို႕
106 
+    တုိက္ရုိက္ညႊန္ျပႏုိင္ပါသည္။ သို႕ေသာ္ <a
107 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">ဤ
108 
+    ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> ကုိ ဘာေၾကာင့္ အႏၱရာယ္ရွိႏုိင္ေၾကာင္း
109 
+    သိရွိႏိုင္ရန္ ၾကည့္ရႈပါ။ SOCKS ႏွင့္ HTTP ပါ ေထာက္ပံ့မႈမရွိေသာ
110 
+    အသံုးခ်ေဆာ့ဝဲမ်ားအတြက္ SocksCap သို႕မဟုတ္ <a
111 
+    href="http://www.freecap.ru/eng/">FreeCap</a> တြင္ ၾကည့္ပါ။ (FreeCap သည္
112 
+    အခမဲ့ေဆာ့ဝဲျဖစ္၍ ကုမၸဏီပုိင္တစ္ခုျဖစ္ပါသည္။)</p>
113 
+
114 
+    <p>အျခားအသံုးခ်ေဆာ့ဝဲမ်ားကုိ Tor လုပ္ေဆာင္ႏုိင္ရန္ မည္သို႕လုပ္ေဆာင္ရမည္ကုိ <a
115 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">မည္သို႕
116 
+    Tor လုပ္ေဆာင္ႏုိင္ေစမည္လဲ</a> တြင္ၾကည့္ရႈပါ။
117 
+    </p>
118 
+
119 
+    <hr /> <a id="verify"></a>
120 
+    <h2><a class="anchor" href="#verify">အဆင့္ သံုး : အလုပ္လုပ္ေၾကာင္း
121 
+    ေသခ်ာပါေစ။</a></h2>
122 
+    <br />
123 
+
124 
+    <p>
125 
+    Vidalia လုပ္ေဆာင္ေနမႈ ရွိ မရိွ စစ္ေဆးပါ။ Vidalia သည္ ေသးငယ္ေသာ အစိမ္းေရာင္
126 
+    ၾကက္သြန္နီေလးကို Tor လုပ္ေဆာင္ေနေၾကာင္းျပသရန္ အသံုးျပဳပါသည္။ သို႕မဟုတ္
127 
+    အနီေရာင္ "X"အမွတ္အသားႏွင့္ ညိဳမည္းေနေသာ ၾကက္သြန္နီေလးကုိ Tor အလုပ္မလုပ္ေသာ
128 
+    အခါ ျပသပါသည္။ System Tray ရွိ Vidalia ရုပ္ပံုေပၚတြင္ ညာဘက္ကလစ္ႏွိပ္၍ Tor ကုိ
129 
+    စတင္ျခင္း သို႕မဟုတ္ ရပ္တန္႕ျခင္း ျပဳလုပ္ႏုိင္ပါသည္။ သို႕မဟုတ္ ေအာက္တြင္
130 
+    ျပသထားသကဲ့သို႕ "စတင္ရန္" သို႕မဟုတ္ "ရပ္တန္႕ရန္" တုိ႕ကုိ Menu မွ
131 
+    ေရြးခ်ယ္ႏုိင္ပါသည္ :
132 
+    </p>
133 
+
134 
+    <img alt="Vidalia Tray Icon" src="../img/screenshot-win32-vidalia.png"/>
135 
+
136 
+    <p>
137 
+    ေနာက္တစ္ဆင့္တြင္ သင့္ browser တြင္ Tor ႏွင့္ သံုးစဲြၾကည့္ရႈ၍ သင့္ IP
138 
+    လိပ္စာသည္ အမည္ဝွက္မႈ လုပ္ေဆာင္ထားေၾကာင္း ေသခ်ာပါေစ။ <a
139 
+    href="https://check.torproject.org/">Tor စစ္ေဆးၾကည့္ရႈသူ</a> ကုိ ကလစ္ႏွိပ္၍
140 
+    သင္ Tor အသံုးျပဳေနျခင္း ဟုတ္ မဟုတ္ စစ္ေဆးပါ။ (ဤ site အလုပ္မလုပ္ပါက၊ <a
141 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">ဤ
142 
+    ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> တြင္ သင့္ Tor ကုိ မည္သို႕စမ္းသပ္ရမည္ဆိုသည့္
143 
+    အၾကံျပဳခ်က္မ်ားကုိ ၾကည့္ရႈပါ။)
144 
+    </p>
145 
+
146 
+    <p>သင့္တြင္ သင့္ကြန္ပ်ဴတာကို ကုိယ္တုိင္ဆက္သြယ္ရန္ ကန္႕သတ္ထားေသာ တစ္ကုိယ္ေရသံုး
147 
+    Firewall ရွိပါက သင့္ စက္တြင္းမွ အသံုးခ်ေဆာ့ဝဲမ်ားကုိ စက္တြင္းမွ port 8118
148 
+    ႏွင့္ port 9050 တို႕သို႕ ဆက္သြယ္ႏုိင္ေၾကာင္း ေသခ်ာပါေစ။ သင့္ Firewall မွ
149 
+    အျပင္သို႕ ဆက္သြယ္မႈမ်ားကုိ ပိတ္ဆို႕ထားပါက အေပါက္တစ္ခုျပဳလုပ္၍ TCP ports
150 
+    မ်ားျဖစ္ေသာ 80 ႏွင့္ 443 တုိ႕ကုိ ဆက္သြယ္ႏုိင္ေစရန္ ျပဳလုပ္ပါ။ ျပီးလွ်င္ <a
151 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">ဤ
152 
+    ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> ကို ၾကည့္ရႈပါ။
153 
+    </p>
154 
+
155 
+    <p>ဤသည္တို႕ႏွင့္ အလုပ္မလုပ္ေသးလွ်င္ <a
156 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">ဤ
157 
+    ေမးေလ့ရွိေသာ ေမးခြန္းမ်ား</a> ကုိ အရိပ္အျမြက္သိရွိႏုိင္ရန္ ၾကည့္ရႈပါ။</p>
158 
+
159 
+    <p>
160 
+    အလုပ္လုပ္သည္ႏွင့္ <a href="<page download/download>#Warning">Tor မွ မည္သည္တို႕ကုိ
161 
+    လုပ္ေဆာင္ႏုိင္၍ မည္သည္တို႕ကုိ မလုပ္ေဆာင္ႏိုင္ပါ</a> တို႕ကို ဆက္လက္ ေလ့လာပါ။
162 
+    </p>
163 
+
164 
+    <hr /> <a id="server"></a> <a id="relay"></a>
165 
+    <h2><a class="anchor" href="#relay">အဆင့္ ေလး : ထပ္ဆင့္လႊင့္သူအျဖစ္
166 
+    ျပင္ဆင္သတ္မွတ္ပါ။</a></h2>
167 
+    <br />
168 
+
169 
+    <p>Tor ကြန္ယက္သည္ ေစတနာ့ဝန္ထမ္းမ်ား၏ လိုင္းအက်ယ္လွဴဒါန္းမႈကို မီွခိုရပါသည္။
170 
+    ထပ္ဆင့္လႊင့္သူ ပိုမုိမ်ားျပားေလ Tor ကြန္ယက္ပိုမိုျမန္ဆန္ေလ ျဖစ္ပါသည္။
171 
+    သင့္တြင္ လမ္းတိုင္းအတြက္ အနည္းဆံုး 20 kilobytes/s ရွိလွ်င္ သင့္ Tor ကုိ
172 
+    ထပ္ဆင့္လႊင့္သူအျဖစ္ ျပင္ဆင္သတ္မွတ္၍ ကူညီေပးပါ။ ကၽြႏု္ပ္တို႕တြင္ Tor
173 
+    ထပ္ဆင့္လႊင့္သူမ်ားကို လြယ္ကူေစရန္ႏွင့္ သက္သာအဆင္ေျပေစရန္
174 
+    လိုင္းအက်ယ္ႏႈန္းကန္႕သတ္ျခင္း၊ အလဲြသံုးမႈ ေစာဒကမ်ားမွ လြတ္ကင္းရန္
175 
+    အထြက္မူဝါဒမ်ား၊ ေျပာင္းလဲေနေသာ IP လိပ္စာမ်ားစသည္ျဖင့္ စီစဥ္ထားရွိပါသည္။</p>
176 
+
177 
+    <p>အင္တာနက္ေပၚတြင္ ထပ္ဆင့္လႊင့္သူမ်ား ေနရာအႏွံ႕ထားရွိျခင္းသည္ Tor
178 
+    အသံုးျပဳသူမ်ားကို ပိုမိုလံုျခံဳေစပါသည္။ အေဝးရွိ site မ်ားမွ သင့္ကြန္ပ်ဴတာမွ
179 
+    ဆက္သြယ္မႈ စတင္သည္ သို႕မဟုတ္ အျခားသူတို႕မွ ထပ္ဆင့္လႊင့္သည္တုိ႕ကုိ
180 
+    မသိရွိႏိုင္သျဖင့္ <a
181 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">သင္ကုိယ္တုိင္
182 
+    ပိုမိုေကာင္းမြန္ေသာ အမည္ဝွက္မႈကို ရရွိႏိုင္ပါသည္။</a></p>
183 
+
184 
+    <p><a href="<page docs/tor-doc-relay>">ထပ္ဆင့္လႊင့္သူအျဖစ္
185 
+    ျပင္ဆင္သတ္မွတ္ျခင္း</a> လမ္းညႊန္တြင္ ပိုမို ဖတ္ရႈပါ။</p>
186 
+
187 
+    <hr />
188 
+
189 
+    <p>သင့္တြင္ ဤစာရြက္စာတမ္း ပိုမုိေကာင္းမြန္ေစႏုိင္ေသာ အၾကံဳျပဳခ်က္မ်ား ရွိပါက <a
190 
+    href="<page about/contact>"> ကၽြႏု္ပ္တို႕ကုိ ေပးပို႕ပါ။</a> ေက်းဇူးတင္ပါသည္ !</p>
191 
+  </div>
192 
+  <!-- END MAINCOL -->
193 
+  <div id = "sidecol">
194 
+#include "side.wmi"
195 
+#include "info.wmi"
196 
+  </div>
197 
+  <!-- END SIDECOL -->
198 
+</div>
199 
+<!-- END CONTENT -->
200 
+#include <foot.wmi>
docs/de/debian.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,168 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22268 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian>">Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <h2><a class="anchor" href="#debian">Möglichkeit eins: Tor unter Debian Lenny,
15 
+    Debian Sid oder Debian Testing</a></h2>
16 
+    <br />
17 
+
18 
+    <p> Wenn du Debian stable (Lenny), unstable (Sid) oder Testing (squeeze)
19 
+    benutzt, musst du nur folgendes ausführen:<br />
20 
+    <tt>apt-get install tor tor-geoipdb</tt> </p>
21 
+
22 
+    <p> Beachte bitte, dass dir das nicht immer die letzte stabile Torversion
23 
+    liefert, aber du erhälst alle sicherheitsrelevanten Fehlerbehebungen. Um
24 
+    sicherzustellen, dass du immer die neueste Version einsetzt, schau dir die
25 
+    Option Zwei weiter unten an. </p>
26 
+
27 
+    <p> Jetzt ist Tor installiert und läuft. Mache weiter bei <a href="<page
28 
+    docs/tor-doc-unix>#polipo">Schritt Zwei</a> der "Tor unter Linux/Unix"
29 
+    Anleitung. </p>
30 
+
31 
+    <hr />
32 
+
33 
+    <a id="ubuntu"></a>
34 
+    <a id="packages"></a>
35 
+    <h2><a class="anchor" href="#ubuntu">Option Zwei: Tor unter Ubuntu oder
36 
+    Debian</a></h2>
37 
+    <br />
38 
+
39 
+    <p> <b>Nimm nicht die Pakete im Ubuntu universe!</b> Diese werden nicht
40 
+    gepflegt und sind veraltet. Das bedeutet, dass dir wichtige Sicherheits- und
41 
+    Stabilitätspatche fehlen! </p>
42 
+
43 
+    <p> Du musst als erstes unser Paket-Repository einrichten, bevor du Tor
44 
+    installieren kannst. Als erstes musst du dafür den Namen deiner Distribution
45 
+    kennen. Wenn du Ubuntu 9.04 einsetzt, ist er "jaunty". Ubuntu 8.10 heißt
46 
+    "intrepid" und Ubuntu 8.04 ist "hardy". Wenn du Debian Etch hast, ist es
47 
+    "etch", Debian Lenny ist "lenny". Danach füge die folgende Zeile in deine <tt>
48 
+    /etc/apt/sources.list</tt> Datei ein:<br />
49 
+
50 
+    <pre>
51 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
52 
+    </pre>
53 
+    Verwende den Namen deiner Distribution (etch, lenny, sid, jaunty, intrepid,
54 
+    hardy) statt &lt;DISTRIBUTION&gt;.
55 
+    </p>
56 
+
57 
+    <p>
58 
+    Danach führe folgendes Kommando aus:
59 
+    <pre>
60 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
61 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
62 
+    apt-get update
63 
+    apt-get install tor tor-geoipdb
64 
+    </pre>
65 
+    </p>
66 
+
67 
+    <p> Jetzt ist Tor installiert und läuft. Mache weiter bei <a href="<page
68 
+    docs/tor-doc-unix>#polipo">Schritt Zwei</a> der "Tor unter Linux/Unix"
69 
+    Anleitung. </p>
70 
+
71 
+    <p style="font-size: small"> Der DNS-Eintrag von <code>
72 
+    deb.torproject.org</code> ist in Wirklichkeit eine Menge von unabhängigen
73 
+    Servern mit DNS Round Robin Konfiguration. Sollte ein Zugriff nicht möglich
74 
+    sein, kannst du auch versuchen einen der Server direkt zu erreichen. Die
75 
+    Adressen lauten:
76 
+    <code>deb-master.torproject.org</code>,
77 
+    <code>mirror.netcologne.de</code> oder
78 
+    <code>tor.mirror.youam.de</code>.
79 
+    </p>
80 
+
81 
+    <hr />
82 
+
83 
+    <a id="development"></a> <h2><a class="anchor" href="#development">Option
84 
+    Drei: Benutze die aktuellste Entwicklerversion unter Debian oder Ubuntu</a>
85 
+    </h2> <br />
86 
+
87 
+    <p>Wenn du den <a href="<page download/download>#packagediff">Entwicklerzweig</a> von
88 
+    Tor benutzen willst (mehr Features, aber vielleicht auch mehr Bugs), musst du
89 
+    folgende Zeilen in deine <tt>/etc/apt/sources.list</tt> Datei einfügen:<br />
90 
+    <pre>
91 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
92 
+    deb     http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
93 
+    </pre>
94 
+    Verwende den Namen deiner Distribution (etch, lenny, sid, jaunty, intrepid,
95 
+    hardy) statt &lt;DISTRIBUTION&gt;.
96 
+    </p>
97 
+
98 
+    <p>
99 
+    Danach führe folgende Kommandos aus:
100 
+    <pre>
101 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
102 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
103 
+    apt-get update
104 
+    apt-get install tor tor-geoipdb
105 
+    </pre>
106 
+    </p>
107 
+
108 
+
109 
+    <p> Jetzt ist Tor installiert und läuft. Mache weiter bei <a href="<page
110 
+    docs/tor-doc-unix>#polipo">Schritt Zwei</a> der "Tor unter Linux/Unix"
111 
+    Anleitung. </p>
112 
+
113 
+
114 
+    <hr />
115 
+
116 
+    <a id="source"></a>
117 
+    <h2><a class="anchor" href="#source">Direkt aus den Quellen kompilieren:</a></h2>
118 
+    <br />
119 
+
120 
+    <p> Wenn du deine eigenen Pakete direkt aus den Quellen erstellen möchtest,
121 
+    musst du als erstes einen entsprechende <tt>deb-src</tt> Zeile in deine <tt>
122 
+    sources.list</tt> einfügen.
123 
+    <pre>
124 
+    # Für die "stable"-Version
125 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
126 
+
127 
+    # Für die "unstable"-Version
128 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
129 
+    deb-src http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
130 
+    </pre>
131 
+    Ausserdem musst du noch folgende essentzielle Pakete installieren, damit du
132 
+    die Tor-Quellen kompilieren kannst:
133 
+    <pre>
134 
+    apt-get install build-essential fakeroot devscripts
135 
+    apt-get build-dep tor
136 
+    </pre>
137 
+    Danach kannst du Tor in ~/debian-packages erzeugen:
138 
+    <pre>
139 
+    mkdir ~/debian-packages; cd ~/debian-packages
140 
+    apt-get source tor
141 
+    cd tor-*
142 
+    debuild -rfakeroot -uc -us
143 
+    cd ..
144 
+    </pre>
145 
+    Jetzt kannst du das neue Paket installieren:
146 
+    <pre>
147 
+    sudo dpkg -i tor_*.deb
148 
+    </pre>
149 
+    </p>
150 
+
151 
+    <p> Jetzt ist Tor installiert und läuft. Mache weiter bei <a href="<page
152 
+    docs/tor-doc-unix>#polipo">Schritt Zwei</a> der "Tor unter Linux/Unix"
153 
+    Anleitung. </p>
154 
+
155 
+    <hr />
156 
+
157 
+    <p>Wenn du Vorschläge hast, wie wir diese Datei verbessern können, <a
158 
+    href="<page about/contact>">schick sie uns bitte</a>. Danke!</p>
159 
+  </div>
160 
+  <!-- END MAINCOL -->
161 
+  <div id = "sidecol">
162 
+#include "side.wmi"
163 
+#include "info.wmi"
164 
+  </div>
165 
+  <!-- END SIDECOL -->
166 
+</div>
167 
+<!-- END CONTENT -->
168 
+#include <foot.wmi>
docs/de/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/de/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,189 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor auf Mac OS X als Client betreiben</h1>
14 
+
15 
+    <p>
16 
+    <b>Diese Anweisungen betreffen den Betrieb von Tor als Client auf Mac
17 
+      OS X. Wenn du für andere Netzwerkverkehr weiterleiten willst, um das
18 
+      Tor-Netzwerk wachsen zu lassen, lies bitte die Anleitung zur <a
19 
+      href="<page docs/tor-doc-relay>">Konfiguration eines Servers</a>.</b>
20 
+    </p>
21 
+
22 
+    <hr />
23 
+    <a id="installing"></a>
24 
+    <h2><a class="anchor" href="#installing">Schritt Eins: Lade Tor
25 
+      herunter und installiere das Programm</a></h2>
26 
+
27 
+    <p>Die Installationsdatei für  Mac OS X fasst <a href="<page
28 
+      index>">Tor</a>, <a
29 
+      href="<page projects/vidalia>">Vidalia</a> (eine grafische
30 
+      Oberfläche für Tor), <a href="<page projects/torbutton>">Torbutton</a> und <a
31 
+      href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (ein Proxy)
32 
+      in ein Paket zusammen. Alle Anwendungen sind vorkonfiguriert und
33 
+      sollten direkt nach der Installation laufen. Lade entweder die <a
34 
+      href="../<package-osx-bundle-stable>">stabile</a> oder die <a
35 
+      href="../<package-osx-bundle-alpha>">experimentelle</a> Version
36 
+      herunter. Andere Optionen findest du auf der <a href="<page
37 
+      download/download>">Downloadseite</a> beschrieben.
38 
+    </p>
39 
+
40 
+    <p>Nachdem du die dmg-Datei runtergeladen hast, klicke doppelt darauf, damit
41 
+    sie eingebunden wird. Danach sollte sich der Finder mit dem Vidalia-Bundle
42 
+    öffnen. Die Installation ist ganz einfach, ziehe einfach die Datei in deinem
43 
+    Anwendungsordner. Optional kannst du noch das "install torbutton" Skript
44 
+    ausführen. Es installiert dir Torbutton in den Firefox, ansonsten bekommst du
45 
+    Torbutton auch über das Mozilla Erweiterungsportal wenn du nach "torbutton"
46 
+    suchst.</p>
47 
+
48 
+    <p>Wenn du mit dem Installieren beendet ist, kannst du Vidalia
49 
+      starten, indem du das Icon vom Ordner Applications auswählst. Eine
50 
+      dunkle Zwiebel mit einem roten X heißt, dass Tor derzeit
51 
+      abgeschalten ist. Wenn du Start (aus dem Menu Tor ganz oben)
52 
+      anklickst, wird Tor gestartet.
53 
+    </p>
54 
+
55 
+    <p>Sobald Tor aktiv ist, ändert sich das Icon folgendermaßen:
56 
+    </p>
57 
+
58 
+    <p><img alt="vidalia running tor"
59 
+      src="../img/screenshot-osx-vidalia.png" border="1" /></p>
60 
+
61 
+    <p>Polipo ist als Teil des Tor-Paketes mit installiert worden. Das
62 
+      Programm startet automatisch, wenn du den Computer anschaltest. Du
63 
+      musst Polipo nicht konfigurieren. Das wurde bereits während der
64 
+      Installation erledigt.
65 
+    </p>
66 
+
67 
+    <hr />
68 
+    <a id="using"></a>
69 
+    <h2><a class="anchor" href="#using">Schritt Zwei: Konfiguration der Anwendungen</a></h2>
70 
+
71 
+    <p>Nachdem Tor und Privoxy installiert sind, musst du deine
72 
+    Anwendungen so anpassen, dass diese Tor nutzen. Wir fangen mit dem
73 
+    Browser an.</p>
74 
+
75 
+    <p>Du solltest für die beste Sicherheit Tor mit Firefox und Torbutton benutzen.
76 
+    Torbutton ist für dich installiert worden. Klicke auf den roten Knopf <q>Tor
77 
+    Disabled</q>, um Tor zu aktivieren und du bist fertig: </p>
78 
+
79 
+    <p><img alt="Torbutton plugin for Firefox"
80 
+    src="../img/screenshot-torbutton.png" border="1" /></p>
81 
+
82 
+    <p>
83 
+    Wenn Firefox auf einem anderen Rechner als Tor laufen
84 
+    soll, schaue dir den <a
85 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">Eintrag
86 
+    in der FAQ dazu</a> an.</p>
87 
+
88 
+    <p>Wir man andere Anwendungen torifiziert, ist in einem
89 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
90 
+    HOWTO</a> beschrieben.
91 
+    </p>
92 
+
93 
+    <hr />
94 
+    <a id="verify"></a>
95 
+    <h2><a class="anchor" href="#verify">Schritt Drei: Stelle sicher, dass
96 
+    alles funktioniert</a></h2>
97 
+
98 
+    <p>Du solltest deinen Browser mit Tor benutzen und sicherstellen, dass
99 
+    deine IP-Adresse anonymisiert wird. Klicke auf den
100 
+    <a href="https://check.torproject.org/">Tor-Detektor</a> und sieh
101 
+    nach, ob du Tor nutzt oder nicht.
102 
+    (Wenn die Seite nicht erreichbar ist, du noch andere <a
103 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">Vorschläge,
104 
+    wie du es testen kannst.</a>)
105 
+    </p>
106 
+
107 
+    <p>Solltest du eine Personal Firewall nutzen, die die Verbindungen des
108 
+    Rechners einschränkt, stelle sicher, dass du dich mit dem lokalen Port
109 
+    8118 und 9050 verbinden kannst. Wenn deine Firewall ausgehende
110 
+    Verbindungen blockiert, stelle sicher, dass zumindest Verbindungen zu
111 
+    den Ports 80 und 443 zugelassen werden und schaue dir den <a
112 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">Eintrag
113 
+    in der FAQ</a> an.
114 
+    </p>
115 
+
116 
+    <p>Falls es immer noch nicht funktioniert, beschreibt ein <a
117 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">weiterer
118 
+    FAQ-Eintrag, woran es liegen kann</a>.</p>
119 
+
120 
+    <p>Wenn es denn geht, lerne mehr darüber,
121 
+    <a href="<page download/download>#Warning">was Tor bietet und was nicht</a>.
122 
+    </p>
123 
+
124 
+    <hr />
125 
+    <a id="server"></a>
126 
+    <a id="relay"></a>
127 
+    <h2><a class="anchor" href="#relay">Schritt Vier: Betreibe einen Server</a></h2>
128 
+
129 
+    <p>Das Tor-Netzwerk vertraut auf Freiwillige, die Verkehr
130 
+    weiterleiten. Je mehr Leute dies tun, desto schneller wird das Netz
131 
+    werden. Falls du mindestens 20 kilobytes/s in jede Richtung hast, hilf
132 
+    bitte mit einem Server aus. Es gibt viele Einstellungen, die es
133 
+    vereinfachen, einen Tor-Server zu betreiben. Das schliesst die
134 
+    Limitierung der Bandbreite, ExitPolicys und Unterstützung für
135 
+    dynamische IP-Adressen mit ein.</p>
136 
+
137 
+    <p>Tor-Servern in unterschiedlichsten Orten im Netz macht Tor
138 
+    sicher. Außerdem bietet das auch dir <a
139 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">stärkere
140 
+    Anonymität</a>, denn eine entfernte Seite kann nicht erkennen, ob die
141 
+    Verbindung von dir oder dem Tor-Server kam.</p>
142 
+
143 
+    <p>Lies mehr bei der <a href="<page docs/tor-doc-relay>">Anleitung für
144 
+    einen Tor-Server</a>.</p>
145 
+
146 
+    <hr />
147 
+    <a id="uninstall"></a>
148 
+    <h2><a class="anchor" href="#uninstall">Wie du Tor and Privoxy deinstallierst</a></h2>
149 
+
150 
+    <p>Es gibt zwei Wege das Tor-Bundle zu deinstallieren. Entweder per Finder
151 
+    oder mittels einem Terminal-basiertem Deinstallationsprogramm. Wenn du Tor
152 
+    unter OSX deinstallieren willst, hier steht wie es geht:</p>
153 
+
154 
+    <p>Ändere die Einstellungen in allen Anwendungen so, dass Tor nicht
155 
+       mehr benutzt wird. Dies reicht, um Tor nicht mehr aktiv zu nutzen.</p>
156 
+
157 
+    <p>Wenn du Tor komplett entfernen willst und dein Zugang die nötigen
158 
+    Adminrechte hat, verfahre folgendermaßen:</p>
159 
+    <ol>
160 
+    <li> Öffne den Finder und klick auf Anwendungen"</li>
161 
+    <li> Ziehe /Anwendungen/Vidalia in den Mülleimer</li>
162 
+    <li> Entferne /Bibliotheken/Torbutton von deinem System</li>
163 
+    <li> Entferne das Vidalia Verzeichniss aus deinem Benutzerordner</li>
164 
+    </ol>
165 
+
166 
+    <p>Tor, Vidalia und Polipo sind jetzt komplett von deinem System entfernt.</p>
167 
+
168 
+    <p>Wenn du dich mit der Kommandozeile auskennst, kannst du auch folgendes manuell entfernen:</p>
169 
+    <ul>
170 
+    <li>/Applications/Vidalia.app/</li>
171 
+    <li>/Library/Vidalia/</li>
172 
+    <li>/Library/Torbutton/</li>
173 
+    <li>~/.tor</li>
174 
+    </ul>
175 
+
176 
+    <hr />
177 
+
178 
+    <p>Hast du Verbesserungen für das Dokument? Dann sende diese bitte an <a
179 
+    href="<page about/contact>">uns</a>. Danke!</p>
180 
+  </div>
181 
+  <!-- END MAINCOL -->
182 
+  <div id = "sidecol">
183 
+#include "side.wmi"
184 
+#include "info.wmi"
185 
+  </div>
186 
+  <!-- END SIDECOL -->
187 
+</div>
188 
+<!-- END CONTENT -->
189 
+#include <foot.wmi>
docs/de/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,262 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor-Server konfigurieren</h1>
14 
+
15 
+    <!-- BEGIN SIDEBAR -->
16 
+    <div class="sidebar-left">
17 
+    <h3>Schritte zur Einrichtung</h3>
18 
+    <ol>
19 
+    <li><a href="<page docs/tor-doc-relay>#install">Herunterladen &amp; Installieren</a></li>
20 
+    <li><a href="<page docs/tor-doc-relay>#setup">Konfigurieren</a></li>
21 
+    <li><a href="<page docs/tor-doc-relay>#check">Überprüfen &amp; Bestätigen</a></li>
22 
+    <li><a href="<page docs/tor-doc-relay>#after">Letze Schritte</a></li>
23 
+    </ol>
24 
+    </div>
25 
+    <!-- END SIDEBAR -->
26 
+
27 
+    <hr />
28 
+
29 
+    <p>Das Tor-Netzwerk beruht auf Freiwilligen, die Bandbreite zur Verfügung
30 
+    stellen. Je mehr Leute einen Tor-Server betreiben, desto schneller wird das
31 
+    Netzwerk. Wenn du wenigstens 20&nbsp;kB/s in eine Richtung hast, bitte hilf
32 
+    uns und konfiguriere Tor auch als Server. Wir haben vieles, was den Betrieb
33 
+    eines Servers einfach und bequem macht. Dazu gehören u.a. <a href="<page docs/faq> #RelayFlexible">
34 
+    Bandbreitenlimitierung, flexible Exitpolicies und
35 
+    Unterstützung für dynamische IP-Adressen.</a></p>
36 
+
37 
+    <p>Du kannst einen Server auf so <a
38 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerOS">
39 
+    ziemlich jedem Betriebssystem</a> installieren, am Besten funktioniert Tor
40 
+    aber unter Linux, FreeBSD 5.x+, OS X Tiger oder neuer und Windows Server 2003
41 
+    oder neuer.</p>
42 
+
43 
+    <hr />
44 
+    <a id="zero"></a>
45 
+    <a id="install"></a>
46 
+    <h2><a class="anchor" href="#install">Schritt Eins: Tor herunterladen und installieren</a></h2>
47 
+
48 
+    <p>Vergewissere dich bevor du beginnst, dass Tor installiert ist und
49 
+    läuft.</p>
50 
+
51 
+    <p>Hol dir die aktuelle Installationsdatei für dein Betriebssystem von unserer
52 
+    <a href="<page download/easy-download>">Downloadseite</a>.</p>
53 
+
54 
+    <p>Wenn du willst, kannst du Tor auch erst eine Weile als Client
55 
+    verwenden, um sicher zu gehen, dass es auch richtig funktioniert.</p>
56 
+
57 
+    <hr />
58 
+    <a id="setup"></a>
59 
+    <h2><a class="anchor" href="#setup">Schritt Zwei: Richte Tor als Server ein</a></h2>
60 
+
61 
+    <ol>
62 
+
63 
+    <li>Stelle sicher, dass die Uhrzeit korrekt eingestellt ist. Falls es möglich
64 
+    ist, synchronisiere sie mit einem <a href="http://en.wikipedia.org/wiki/Network_Time_Protocol">öffentlichen
65 
+    Zeitserver im Internet</a>.</li>
66 
+
67 
+      <li><strong>Windows / OS X Configuration</strong>:
68 
+      <ol>
69 
+
70 
+     <ul><strong>Einfache Einrichtung</strong>:
71 
+     <li>Rechtsklicke auf das Vidalia Icon in deiner Taskleiste, wähle <tt>Einstellungen</tt>.</li>
72 
+      	 <li>Klicke auf Beteiligung</li>
73 
+    <li>Klicke auf <tt>Netzwerkverkehr für andere Tor-Nutzer weiterleiten</tt>,
74 
+    wenn du ein öffentliches Relay betreiben möchtest (empfohlen) oder auf "Hilf
75 
+    zensierten Nutzern" wenn du eine <a href="<page docs/faq>#RelayOrBridge">Bridge</a>
76 
+    betreiben willst um Nutzern aus Zensurländern zu helfen</li>
77 
+    <li>Gib einen Namen für deinen Server an. (Optional, kannst du Kontaktdaten
78 
+    angeben, damit wir dich bei Probleme verständigen können)</li>
79 
+      	 <li>Wähle <tt>Versuche automatisch die Port-Weiterleitung zu konfigurieren</tt> und klicke
80 
+      	 auf den <tt>Test</tt> Button, um zu sehen, ob es geht. Wenn es geht, toll!
81 
+      	 Wenn nicht, schau dir Schritt 3 weiter unten an.</li>
82 
+    <li>Wähle den <tt>Bandbreitenbegrenzung</tt> Karteireiter. Such dir aus, wie
83 
+    viel Bandbreite du für andere Nutzer bereitstellen willst.</li>
84 
+
85 
+    <li>Klicke den <tt>Exit-Regeln</tt> Karteireiter und deaktiviere alle Dienste
86 
+    die <a href="<page docs/faq>#ExitPolicies">NICHT von deinem Relay erreicht werden
87 
+    sollen</a>. Wenn du kein Exit sein möchtest, wähle alle ab.</li>
88 
+
89 
+    <li>Klicke den <tt>Ok</tt> Knopf. Schau dir Schritt Drei weiter unten an,
90 
+    damit du weißt wie du die Funktion testen kannst.</li> </ol> <br/> <strong>
91 
+    Unix / Linux Einrichtung</strong>: <ul> <li>Editiere den unteren Teil deiner
92 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">
93 
+    torrc Datei</a>. Wenn du ein öffentliches Relay sein möchtest (empfohlen)
94 
+    musst du einen ORPort wählen und einen Blick auf <a href="<page docs/faq> #ExitPolicies">die ExitPolicies</a> werfen; wenn du <a href="<page docs/faq> #RelayOrBridge">eine Bridge </a>für Nutzer aus Zensurländern sein willst,
95 
+    <a href="<page docs/bridges>#RunningABridge">nimm diese Zeilen</a>. </li>
96 
+
97 
+      </ul></li>
98 
+
99 
+    <li>Wenn du eine Firewall verwendest, öffne einen Port, damit eingehende
100 
+    Verbindungen, die von dir konfigurierten Ports erreichen können (<var>
101 
+    ORPort</var> plus <var>DirPort</var>, falls gesetzt). Wenn du ein DSL-Modem
102 
+    oder eine andere Firewall hast, kann dir <a href="http://portforward.com/">
103 
+    portforward.com</a> helfen. Stelle sicher, dass alle abgehenden Verbindungen
104 
+    von der Firewall zugelassen werden, damit die anderen Torserver erreicht
105 
+    werden können.</li>
106 
+
107 
+
108 
+
109 
+    <li>Starte deinen Server neu: Wenn es Warnungen gibt, solltest du sie erst
110 
+    beheben.</li>
111 
+
112 
+    <li>Trage dich in die Mailingliste <a
113 
+    href="http://archives.seul.org/or/announce/">or-announce</a> ein. Sie wird
114 
+    dich über neue stabile Pakete auf dem laufenden halten. Du möchtest dich
115 
+    eventuell auch bei <a href="<page docs/documentation>#MailingLists">den anderen
116 
+    Tor-Mailinglisten</a> einschreiben. Diese Listen informieren auch über neue
117 
+    Entwicklerversionen.</li>
118 
+
119 
+    </ol>
120 
+
121 
+    <hr />
122 
+    <a id="check"></a>
123 
+    <h2><a class="anchor" href="#check">Schritt Drei: Sicher gehen, dass es funktioniert</a></h2>
124 
+
125 
+    <p>Sobald sich dein Server zum Netzwerk verbinden kann, wird er versuchen
126 
+    herauszufinden, ob die Ports, die du konfiguriert hast, von außen erreichbar
127 
+    sind. Normalerweise geht das sehr schnell, kann aber bis zu 20&nbsp;Minuten
128 
+    dauern. Halte nach Logeinträgen wie <samp>self-testing indicates your ORPort
129 
+    is reachable from the outside. Excellent</samp> Ausschau. Wenn du diese
130 
+    Nachricht nicht siehst, bedeutet dies, dass dein Server von außen nicht
131 
+    erreichbar ist. Stelle sicher, dass die Angaben zu IP-Adresse und Port richtig
132 
+    sind.</p>
133 
+
134 
+    <p>Wenn er erreichbar ist, wird er einen &quot;Serverdescriptor&quot; in die
135 
+    Verzeichnisse laden. Dadurch wissen andere Clients, welche Adresse, Ports,
136 
+    Schlüssel etc. dein Server verwendet. Du kannst <a
137 
+    href="http://moria.seul.org:9032/tor/status/authority">den Netzwerkstatus
138 
+    manuell laden</a> und ihn nach deinem Nickname durchsuchen. So kannst du sicher
139 
+    gehen, dass er existiert. Dies dauert meist einige Sekunden.</p>
140 
+
141 
+    <hr />
142 
+    <a id="after"></a>
143 
+    <h2><a class="anchor" href="#after">Schritt Vier: Wenn es funktioniert</a></h2>
144 
+
145 
+    <p>Wir empfehlen folgende Schritte zusätzlich auszuführen:</p>
146 
+
147 
+    <p>In <a
148 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/operationalsecurity">diesem
149 
+    Dokument</a> gibt es Anweisungen, wie du die Sicherheit des Servers
150 
+    erhöhen kannst.</p>
151 
+
152 
+    <p>Entscheide dich, welche Exitpolicy du willst. Standardmäßig
153 
+    gewährt dein Server den Zugriff auf viele bekannte Dienste. Einige
154 
+    (z.B. Port 25) werden jedoch eingeschränkt, aufgrund von vorhandenem
155 
+    Missbrauchpotential. Vielleicht möchtest du eine restriktivere oder
156 
+    weniger restriktive Exitpolicy wählen. Editiere dazu deine
157 
+    <var>torrc</var> entsprechend. Lies die FAQ über <a href="<page
158 
+    docs/faq-abuse>#typicalabuses">Probleme, die bei der Verwendung der
159 
+    standardmäßigen Exitpolicy auftreten können</a>. Wenn du eine
160 
+    liberale Exitpolicy wählst, stelle auch sicher, dass dein ISP damit
161 
+    leben kann. Falls es Ressourcen gibt, die dein Computer nicht
162 
+    erreichen kann, lehne diese bitte explizit in deiner Exitpolicy ab
163 
+    &mdash; sonst werden Tornutzer auch hiervon betroffen sein.</p>
164 
+
165 
+    <p>Du solltest dir Gedanken über die Limitierung der Bandbreite
166 
+    machen. Modem, DSL und andere Nutzer, die asymmetrische Verbindungen
167 
+    haben (z.b. höhere Downloadbandbreite) sollten den Durchsatz auf die kleinere
168 
+    Bandbreite limitieren, um so Blockaden zu vermeiden. Dieser <a
169 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">FAQ-Eintrag</a>
170 
+    enthält weitere Details.</p>
171 
+
172 
+    <ol start="8"> <li>Mache ein Backup vom privaten Schlüssel deines
173 
+    Torservers (gespeichert in <var>keys/secret_id_key</var> in deinem
174 
+    Datenverzeichnis). Dies ist die &bdquo;Identität&ldquo; deines
175 
+    Servers. Halte sie geheim, damit niemand deinen Server abhören
176 
+    kann. Das ist die kritische Datei, um deinen Server <a
177 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeServer">zu
178 
+    verschieben oder wiederherzustellen</a>, wenn etwas schief geht.</li>
179 
+
180 
+    <li>Wenn du die Nameserver für deine Domain kontrollierst, überlege
181 
+    dir, ob du nicht deinen Hostnamen auf <samp>anonymous</samp> oder
182 
+    <samp>proxy</samp> oder <samp>tor-proxy</samp> setzt. Wenn die Leute
183 
+    die Adresse in ihren Logdateien sehen, wissen sie schneller, was los
184 
+    ist.</li>
185 
+
186 
+    <li>Wenn dein Server nicht als Webserver fungiert, erwäge
187 
+    doch deinen ORport auf 443 und deinen DirPort auf 80 zu ändern.
188 
+    Viele Tor-Benutzer stecken hinter Firewalls fest, welche sie nur
189 
+    surfen lassen. Diese Änderungen würden auch den
190 
+    Benutzern Zugang zu deinem Tor-Server ermöglichen. Auf einem
191 
+    Win32-Server kann einfach der ORPort und DirPort direkt in der
192 
+    <var>torrc</var>
193 
+    geändert und Tor neu gestartet werden.  Auf OS X oder Unixservern
194 
+    kann man nicht direkt diese Ports verwenden (weil Tor dort nicht
195 
+    als root läuft).  Deshalb muss man da irgendeine Form von
196 
+    <a
197 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">Portweiterleitung</a>
198 
+    einrichten, damit Verbindungen zum Tor-Server gemacht werden können.
199 
+    Falls du die Ports 80 und 443 schon benutzt, aber trotzdem helfen willst, öffne
200 
+    Port 22, 110, und 143.</li>
201 
+
202 
+    <li>Falls dein Tor-Server noch andere Dienste auf der selben Adresse
203 
+    anbietet &mdash; wie z.B. einen Webserver &mdash; vergewissere dich,
204 
+    dass Verbindungen zum Webserver auch vom localhost zugelassen werden.
205 
+    Diese Verbindungen müssen klappen, da Torclients erkennen, dass dein
206 
+    Torserver der <a
207 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">sicherste
208 
+    Weg ist, deinen Webserver zu erreichen</a>. Daher bauen sie immer
209 
+    Verbindungen, die bei deinem Server aufhören. Wenn du diese
210 
+    Verbindungen nicht erlauben willst, dann musst die sie direkt in
211 
+    deiner Exitpolicy verbieten.</li>
212 
+
213 
+    <li>(nur Unix). Lege einen neuen Nutzer an, welcher das Programm
214 
+    ausführt. Wenn du das OS X, deb oder rpm installiert hast, so
215 
+    wurde dies bereits erledigt. Ansonsten kannst du dies per Hand
216 
+    erledigen. (Der Tor-Server muss nicht als root laufen, es ist also
217 
+    eine gute Idee das auch nicht zu tun. Ausführen als 'tor'
218 
+    Benutzer erübrigt Probleme mit inetd und anderen Diensten, welche
219 
+    auf Nutzernamen prüfen. wenn du ein paranoider Zeitgenosse bist
220 
+    kannst du <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">Tor
221 
+    in einer chroot-Jail ausführen</a>.)</li>
222 
+
223 
+    <li>(nur Unix). Vermutlich limitiert dein Betriebssystem die Anzahl offener
224 
+    Dateien pro Prozess auf 1024 (oder noch weniger). Wenn du vorhast, einen
225 
+    schnellen Exitknoten zu betreiben, wird das vermutlich nicht reichen. Unter
226 
+    Linux solltest du eine Zeile wie <var>toruser hard nofile 8192</var> zu deiner
227 
+    <var>/etc/security/limits.conf</var>
228 
+    hinzufügen (<var>toruser</var> ist hier der Benutzer, unter dem der Prozess läuft).
229 
+    Anschließend musst du Tor neu starten.</li>
230 
+
231 
+    <li>Wenn du Tor über ein Paket oder ein Installationsprogramm installiert
232 
+    hast, wird er vermutlich automatisch beim Booten gestartet. Wenn du
233 
+    jedoch aus dem Quellcode installiert hast, findest du vielleicht die
234 
+    Initscripte in <var>contrib/tor.sh</var> oder <var>contrib/torctl</var>
235 
+    hilfreich.</li>
236 
+
237 
+    </ol>
238 
+
239 
+    <p>Bei Änderungen kann <a
240 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Restarting">in
241 
+    den meisten Fällen die Konfigurationsdatei neu geladen werden, ohne Tor neu
242 
+    starten zu müssen</a>. Stelle sicher, dass die Option <samp>ContactInfo</samp>
243 
+    gesetzt ist, so dass wir dich bei Problemen kontaktieren können. Falls du
244 
+    Probleme oder Fragen hast, schaue auf die <a href="<page
245 
+    docs/documentation>#Support">Support</a>-Seite oder <a href="<page
246 
+    about/contact>">kontaktiere uns</a> auf der tor-ops-Mailingliste. Wir danken dir, dass
247 
+    du das Netzwerk wachsen lässt!</p>
248 
+
249 
+    <hr />
250 
+
251 
+    <p>Wenn du Vorschläge zur Verbesserung dieses Dokuments hast, <a href="<page
252 
+    about/contact>">schicke sie uns bitte</a>. Danke!</p>
253 
+  </div>
254 
+  <!-- END MAINCOL -->
255 
+  <div id = "sidecol">
256 
+#include "side.wmi"
257 
+#include "info.wmi"
258 
+  </div>
259 
+  <!-- END SIDECOL -->
260 
+</div>
261 
+<!-- END CONTENT -->
262 
+#include <foot.wmi>
docs/de/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,173 @@
1 
+    <h1>Tor-Client auf Linux/BSD/Unix betreiben</h1>
2 
+
3 
+    <p>
4 
+    <b>Das sind die Anweisungen, um ein Clientprogramm zu betreiben. Wenn du für
5 
+    andere Verkehr weiterleiten möchtest und helfen willst, das Netzwerk auszubauen,
6 
+    dann lies bitte die Anleitung zur <a
7 
+    href="<page docs/tor-doc-relay>">Konfiguration eines Servers</a>.</b>
8 
+    </p>
9 
+
10 
+    <hr />
11 
+    <a id="installing"></a>
12 
+    <h2><a class="anchor" href="#installing">Schritt Eins: Lade Tor herunter und
13 
+    installiere es</a></h2>
14 
+
15 
+    <p>Die letzte Version von Tor kannst du auf der <a href="<page download/download>">
16 
+    Download-Seite</a> finden. Wir haben Pakete für Debian, Red Hat, Gentoo, *BSD
17 
+    etc. Wenn du Ubuntu benutzt, nimm auf keinen Fall die standard Pakete! Nimm
18 
+    stattdessen <a href="<page docs/debian>#ubuntu">unser Deb-Repository</a>. </p>
19 
+
20 
+    <p>Falls du das Programm aus dem Quellcode bauen willst, installiere zuerst <a
21 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a> und stelle sicher,
22 
+    dass du auch OpenSSL und zlib hast (inklusive der Entwicklerpakete). Führe dann
23 
+    aus:<br />
24 
+    <kbd>tar xzf tor-<version-stable>.tar.gz; cd tor-<version-stable><br />
25 
+    ./configure &amp;&amp; make</kbd><br />
26 
+    Du kannst nun Tor mit dem Befehl <kbd>src/or/tor</kbd> ausführen oder mit <kbd>make
27 
+    install</kbd> installieren, um es nach /usr/local/ zu installieren. Danach
28 
+    brauchst du nur noch <kbd>tor</kbd> auszuführen.
29 
+    </p>
30 
+
31 
+    <p>Tor ist standardmäßig als Client eingerichtet. Es benutzt eine eingebaute
32 
+    Konfigurationsdatei und meist benötigt man nichts zu ändern. Tor ist nun
33 
+    installiert.
34 
+    </p>
35 
+
36 
+    <hr />
37 
+    <a id="privoxy"></a>
38 
+    <a id="polipo"></a>
39 
+    <h2><a class="anchor" href="#polipo">Schritt Zwei: Installiere Polipo zum Surfen</a></h2>
40 
+    <br />
41 
+
42 
+    <p>Nachdem du Tor installiert hast, musst du deine Anwendungen richtig einstellen.
43 
+    </p>
44 
+
45 
+    <p> Der erste Schritt ist es, deinen Browser einzurichten. Dafür solltest du
46 
+    <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> aus
47 
+    deinem Lieblingsrepository installieren. Polipo ist ein Webproxy mit Cache,
48 
+    der auch HTTP Pipelining kann und daher sehr gut für die Latenzen des
49 
+    Tornetzwerks geeignet ist. Stelle sicher, dass du mindestens Polipo 1.0.4
50 
+    einsetzt, frühere Versionen haben keinen SOCKS Support den man für Tor
51 
+    braucht. </p>
52 
+
53 
+    <p> Wenn Polipo installiert ist, <b>musst du Polipo noch für Tor
54 
+    einrichten!</b> Nimm einfach unsere <a
55 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/polipo.conf">
56 
+    Polipo Konfiguration für Tor</a> und kopiere sie an die Stelle deiner
57 
+    aktuellen Konfiguration (meistens in /etc/polipo/config oder ~/.polipo).
58 
+    Danach musst du Polipo noch neustarten.</p>
59 
+
60 
+    <p>Wenn du lieber Privoxy verwendest, nimm diese <a
61 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">
62 
+    Beispielkonfiguration für Privoxy</a>. Aber da beide Einstellungsdateien den
63 
+    Port 8118 nutzen, solltest du nicht beide Programme gleichzeitig laufen
64 
+    lassen.</p>
65 
+
66 
+    <hr />
67 
+    <a id="using"></a>
68 
+    <h2><a class="anchor" href="#using">Schritt Drei: Konfiguriere deine Anwendungen </a></h2>
69 
+
70 
+    <p>Nachdem Tor und Polipo installiert sind, musst du die Anwendungen ebenfalls
71 
+    einrichten. Der erste Schritt ist Webbrowsing.</p>
72 
+
73 
+    <p>Du solltest Tor mit Firefox und Torbutton benutzen. Installiere einfach die
74 
+    Erweiterung <a href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> und
75 
+    starte den Firefox neu.
76 
+    </p>
77 
+
78 
+    <p><img alt="Torbutton plugin for Firefox" src="../img/screenshot-torbutton.png"
79 
+    border="1" /></p>
80 
+
81 
+    <p>Falls du Firefox auf einem anderen Computer als Tor betreiben willst, schaue
82 
+    dir den <a
83 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">Eintrag
84 
+    in der FAQ</a> an.
85 
+    </p>
86 
+
87 
+    <p>Um andere Anwendungen, die HTTP-Proxys unterstützen, konfiguriere sie,
88 
+    Polipo zu nutzen (localhost port 8118). Zur direkten Verwendung von SOCKS (für
89 
+    Instant Messaging, Jabber, IRC etc) kannst du die Anwendung direkt mit Tor
90 
+    anwenden (localhost port 9050). Ein <a
91 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">FAQ-Eintrag</a>
92 
+    sagt dir, warum das unter Umständen gefährlich ist. Anwendungen, die weder HTTP
93 
+    noch SOCKS sprechen, können mit <a
94 
+    href="http://tsocks.sourceforge.net/">tsocks</a> oder <a
95 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>
96 
+    benutzt werden.
97 
+    </p>
98 
+
99 
+    <p>Das
100 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
101 
+    HOWTO</a> beschreibt, wie man verschiedene Programme zusammen mit Tor benutzen
102 
+    kann.
103 
+    </p>
104 
+
105 
+    <hr />
106 
+    <a id="verify"></a>
107 
+    <h2><a class="anchor" href="#verify">Schritt Vier: Stelle sicher, dass alles
108 
+    funktioniert</a></h2>
109 
+
110 
+    <p>Versuche nun deinen Browser mit Tor zu nutzen und stelle sicher, dass deine
111 
+    IP-Adresse anonymisiert wird. Klicke auf den
112 
+    <a href="https://check.torproject.org/">Tor-Detektor</a> und schaue nach, ob er
113 
+    der Meinung ist, ob du Tor nutzt.
114 
+    #<a href="http://ipchicken.com/">this site</a>
115 
+    #to see what IP address it thinks you're using.
116 
+    (Für den Fall das die Seite nicht erreichbar ist, gibt der <a
117 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">FAQ-Eintrag
118 
+    weitere Wege, wie du Tor testen kannst</a>.)
119 
+    </p>
120 
+
121 
+    <p>Solltest du eine Personal Firewall einsetzen, die die Fähigkeiten deines
122 
+    Computers einschränkt (schließt auch SELinux auf Fedora Core 4 ein), stelle
123 
+    sicher, dass lokale Anwendungen zu Privoxy (Port 8118) und zu Tor (Port 9050)
124 
+    verbinden können. Wenn deine Firewall ausgehende Verbindungen verbietet,
125 
+    ändere dies, so dass mindestens Port 80 und 443 erlaubt sind und schaue dir
126 
+    danach diesen <a
127 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">FAQ-Eintrag</a>
128 
+    an. Wenn dein SELinux nicht erlaubt, Tor oder Polipo korrekt zu betreiben, lege
129 
+    eine Datei namens booleans.local im Verzeichnis /etc/selinux/targeted an.
130 
+    Editiere die Datei und füge die Zeile "allow_ypbind=1" hinzu. Danach musst du
131 
+    deinen Rechner neu starten.
132 
+    </p>
133 
+
134 
+    <p>Falls es immer noch nichtgeht, schaue dir diesen <a
135 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">FAQ-Eintrag</a>
136 
+    an.</p>
137 
+
138 
+    <hr />
139 
+    <a id="server"></a>
140 
+    <a id="relay"></a>
141 
+    <h2><a class="anchor" href="#relay">Schritt Fünf: Richte es als Server ein</a></h2>
142 
+
143 
+    <p>Das Tor-Netzwerk vertraut auf Freiwillige, die Bandbreite spenden. Je mehr
144 
+    Menschen Server betreiben, desto schneller wird das Netzwerk werden. Wenn du
145 
+    mindestens 20 Kilobytes/s in jede Richtung hast, dann hilf dem Tor-Netzwerk
146 
+    bitte aus. Wir haben einige Eigenschaften, die es einfach machen, Tor-Server zu
147 
+    betreiben. Das schließt die Limitierung der Bandbreite, ExitPolicys und
148 
+    Unterstützung für dynamische IP-Adressen mit ein.
149 
+    </p>
150 
+
151 
+    <p>Tor-Server an unterschiedlichen Plätzen in der Welt zu haben, macht die
152 
+    Tor-Benutzer sicherer. Außerdem bekommst du selbst <a
153 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">eine
154 
+    stärkere Anonymität</a>. Denn entfernte Seiten können nicht wissen, ob die
155 
+    Verbindungen von dir oder von anderen kommen.</p>
156 
+
157 
+    <p>Lies mehr in der <a href="<page docs/tor-doc-relay>">Anleitung zur
158 
+    Konfiguration eines Servers</a>.</p>
159 
+
160 
+    <hr />
161 
+
162 
+    <p>Falls du Verbesserungsvorschläge für dieses Dokuments hast, dann <a
163 
+    href="<page about/contact>">sende sie bitte an uns</a>. Danke!</p>
164 
+  </div>
165 
+  <!-- END MAINCOL -->
166 
+  <div id = "sidecol">
167 
+#include "side.wmi"
168 
+#include "info.wmi"
169 
+  </div>
170 
+  <!-- END SIDECOL -->
171 
+</div>
172 
+<!-- END CONTENT -->
173 
+#include <foot.wmi>
docs/de/tor-doc-web.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,70 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Configuring your browser to use Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-web>">Configure Your Browser</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Richte deinen Browser zur Nutzung von Tor ein</h1>
14 
+
15 
+    <p>Wenn du Firefoxb benutzt (was wir empfehlen), brauchst du diese Seite
16 
+      nicht. Installiere einfach die Erweiterung <a
17 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton</a>, starte
18 
+      Firefox neu und du bist fertig.
19 
+    </p>
20 
+
21 
+    <p><img alt="Torbutton plugin for Firefox"
22 
+      src="../img/screenshot-torbutton.png" border="1" /></p>
23 
+
24 
+    <p>Ansonsten musst du die Proxyeinstellungen deines Browsers selbst
25 
+      einstellen.</p>
26 
+      <dl>
27 
+        <dt>Mozilla und Firefox unter Windows</dt>
28 
+        <dd>Extras - Einstellungen - Allgemein -
29 
+      Verbindungseinstellungen</dd>
30 
+
31 
+      <dt>Firefox unter Mac OS X</dt>
32 
+      <dd>Firefox - Preferences - General - Connection Settings</dd>
33 
+
34 
+      <dt>Firefox unter Linux</dt>
35 
+      <dd>Optionen - Einstellungen - Erweitert- Proxys</dd>
36 
+
37 
+      <dt>Opera</dt>
38 
+      <dd>Extras - Einstellungen... - Erweitert - Netzwerk -
39 
+    Proxyserver...</dd>
40 
+
41 
+    <dt>Internet Explorer</dt> <dd>Wir können den Einsatz des IE nicht empfehlen,
42 
+    aber für die Leute die sich etwas Anonymität einbilden möchten:<br/> Extras -
43 
+    Internetoptionen - Verbindungen - LAN-Einstellungen - Proxyserver -
44 
+    Erweitert</dd> </dl>
45 
+
46 
+    <p><img alt="Proxyeinstellungen im Firefox"
47 
+      src="../img/screenshot-win32-firefox-proxies.jpg" /></p>
48 
+
49 
+    <p>Du solltest die Angaben zu Host ("localhost") und zum Port ("8118")
50 
+      in allen Feldern eintragen. (Auch wenn Privoxy diese Protokolle
51 
+      nicht unterstützt, <a
52 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">solltest
53 
+      du die eintragen</a>.) Weiterhin solltest du auch das Feld mit dem
54 
+      SOCKS-Proxy ausfüllen ("localhost", "9050" und socks5), um
55 
+      Protokolle außer den ersten vier abzudecken. Danach klicke auf "OK".</p>
56 
+
57 
+    <hr />
58 
+
59 
+    <p>Wenn du Verbesserungen für das Dokument hast, <a
60 
+    href="<page about/contact>">sende diese bitte an uns</a>. Danke!</p>
61 
+  </div>
62 
+  <!-- END MAINCOL -->
63 
+  <div id = "sidecol">
64 
+#include "side.wmi"
65 
+#include "info.wmi"
66 
+  </div>
67 
+  <!-- END SIDECOL -->
68 
+</div>
69 
+<!-- END CONTENT -->
70 
+#include <foot.wmi>
docs/de/tor-doc-win32.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,7 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 13195
3 
+# Status: obsolete
4 
+
5 
+#include "head.wmi" TITLE="Redirecting" REDIRECT="docs/tor-doc-windows"
6 
+
7 
+#include <foot.wmi>
docs/de/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,181 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor unter Microsoft Windows benutzen</h1>
14 
+
15 
+    <p><b>Bitte beachte, das diese Anleitung die Installation für
16 
+    Microsoft Windows (98, 98SE, NT4, 2000, XP, Vista, Server)
17 
+    beschreibt. Wenn du Netzverkehr für andere Benutzer weiterleiten und
18 
+    beim Ausbau des Tor-Netzwerks mithelfen willst (Du bist herzlich
19 
+    eingeladen!), lies die <a href="<page docs/tor-doc-relay>"> Anleitung
20 
+    zum Einrichten eines Servers</a>.</b> </p>
21 
+
22 
+    <hr />
23 
+    <a id="installing"></a>
24 
+    <h2><a class="anchor" href="#installing">Schritt Eins: Download und Installation von Tor</a></h2>
25 
+
26 
+    <p>Das Installationspaket für MS Windows enthält <a href="<page
27 
+      index>">Tor</a>, <a
28 
+      href="<page projects/vidalia>">Vidalia</a> (eine
29 
+      Benutzeroberfläche für Tor), und <a
30 
+      href="http://www.privoxy.org/">Privoxy</a> (ein lokaler Proxy zum
31 
+      Filtern von Webseiten). Die drei Programme sind für die gemeinsame
32 
+      Arbeit vorkonfiguriert. Bitte lade entweder das <a
33 
+      href="../<package-win32-bundle-stable>">stabile</a> oder das <a
34 
+      href="../<package-win32-bundle-alpha>">Entwicklerpaket</a> von der
35 
+      <a href="<page download/download>">Download-Seite</a> herunter.</p>
36 
+
37 
+    <p><img alt="tor installer splash page"
38 
+      src="../img/screenshot-win32-installer-splash.png" height="386"
39 
+      width="503" /></p>
40 
+
41 
+    <p>Wenn Tor, Vidalia oder Privoxy bereits zuvor installiert wurden,
42 
+      kannst du mit dem unten dargestellten Dialog wählen, welche
43 
+      Komponenten aus dem kombinierten Softwarepaket nicht installiert
44 
+      werden sollen.</p>
45 
+
46 
+    <p><img alt="select components to install"
47 
+      src="../img/screenshot-win32-installer-components.png" height="386"
48 
+      width="503" /></p>
49 
+
50 
+    <p>Nach der erfolgreichen Installation werden alle ausgewählten
51 
+      Programme automatisch gestartet.</p>
52 
+
53 
+    <!--
54 
+    <p>
55 
+    Voreingestellt ist die Installation von Tor als Dienst (client).
56 
+    Die Vorgaben sind in einer eingebaute Konfigurations-Datei abgelegt.
57 
+    Die meisten Anwender werden keine Änderungen an den Vorgaben vornehmen müssen.
58 
+    Tor ist jetzt installiert.
59 
+    </p>
60 
+    -->
61 
+
62 
+    <hr />
63 
+    <a id="using"></a>
64 
+    <h2><a class="anchor" href="#using">Schritt Zwei: Programme einrichten</a></h2>
65 
+
66 
+    <p>Nach der Installation von Tor und Privoxy müssen die Programme
67 
+    eingestellt werden. Zuerst wird der Web-Browser angepasst.</p>
68 
+
69 
+    <p>Du solltest Tor mit Firefox und der Erweiterung TorButton für bestmögliche
70 
+    Sicherheit benutzen. Das Paket installiert Vidalia den <a
71 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> für
72 
+    dich. Starte Firefox neu und du bist fertig:
73 
+    </p>
74 
+
75 
+    <p>
76 
+    <img alt="Torbutton plugin for Firefox"
77 
+    src="../img/screenshot-torbutton.png" border="1" height="78"
78 
+    width="161" /></p>
79 
+
80 
+    <p>Wenn du vorhast, Firefox auf einem anderen Computer zu
81 
+    benutzen als auf dem, wo Tor installiert ist, lies den Eintrag in
82 
+    der <a
83 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">FAQ
84 
+    zum Betrieb von Tor auf einem anderen Computer</a>.</p>
85 
+
86 
+    <p>Andere Programme, die HTTP-Proxys unterstützen, können Tor nutzen,
87 
+    wenn Privoxy als HTTP-Proxy eingerichtet ist (einfach "localhost" und
88 
+    "port 8118" eingeben). Bei Programmen, die SOCKS direkt nutzen
89 
+    (z.B. Instant-Messaging, Jabber, IRC usw.), trage Tor als Proxy ein
90 
+    ("localhost" und "port 9050"). Beachte aber diesen <a
91 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">Eintrag
92 
+    in der FAQ</a>. Er erklärt, warum dies die Anonymität gefährdet. Bei
93 
+    Programmen, die weder SOCKS- noch HTTP-Proxys nutzen, könnte SocksCap
94 
+    oder <a href="http://www.freecap.ru/eng/">FreeCap</a> helfen.
95 
+    (FreeCap ist freie Software; SocksCap ist kommerziell.)</p>
96 
+
97 
+    <p>Weitere Informationen findest du im
98 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
99 
+    HOWTO</a>.
100 
+    </p>
101 
+
102 
+    <hr />
103 
+    <a id="verify"></a>
104 
+    <h2><a class="anchor" href="#verify">Schritt Drei: Prüfe, ob alles funktioniert</a></h2>
105 
+
106 
+    <p>
107 
+    Prüfe, ob Privoxy und Vidalia in der Task-Leiste aktiv sind. Das Icon
108 
+    von Privoxy ist ein blauer oder grüner Kreis mit einem "P"
109 
+    darin. Vidalia zeigt eine kleine grüne Zwiebel, wenn Tor aktiv ist
110 
+    oder eine dunkle Zwiebel mit einem roten Kreuz, wenn Tor inaktiv
111 
+    ist. Du kannst Tor starten oder anhalten, wenn du das Vidalia-Icon in
112 
+    der Taskleiste mit der rechten Maustaste anklickst und "Start" oder
113 
+    "Stopp" aus dem Menü (unten) auswählst.
114 
+    </p>
115 
+
116 
+    <p>
117 
+    <img alt="Vidalia Tray Icon" src="../img/screenshot-win32-vidalia.png"
118 
+    height="215" width="161" /></p>
119 
+
120 
+    <p>
121 
+    Dann solltest du prüfen, ob der Browser Tor benutzt und die IP-Adresse
122 
+    anonymisiert. Klicke auf <a
123 
+    href="http://check.torproject.org/">Tordetektor</a>
124 
+    und schaue, ob du Tor nutzt.
125 
+    (Wenn die Seite nicht erreichbar ist, findest du <a
126 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">in
127 
+    diesem FAQ-Eintrag</a> weitere Vorschläge, Tor zu testen.)
128 
+    </p>
129 
+
130 
+    <p>Wenn deine Personal Firewall auch Verbindungen des Computers mit
131 
+    den eigenen Programmen blockiert, erlaube Verbindungen mit "localhost"
132 
+    auf Port 8118 und Port 9050. Wenn die Personal Firewall ausgehende
133 
+    Verbindungen blockiert, erlaube Verbindungen auf den TCP-Ports 80 und
134 
+    443 und lese diesen <a
135 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">Eintrag
136 
+    in der FAQ</a>.</p>
137 
+
138 
+    <p>Wenn es immer noch nicht funktioniert, lies die <a
139 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">weiteren
140 
+    Hinweise in der FAQ</a>.</p>
141 
+
142 
+    <p>Sobald es funktioniert, schaue dir an, <a href="<page
143 
+    download/download>#Warning">was Tor bietet und was nicht</a>.</p>
144 
+
145 
+    <hr />
146 
+    <a id="server"></a>
147 
+    <h2><a class="anchor" href="#server">Schritt Vier: Tor als Server einrichten</a></h2>
148 
+
149 
+    <p>
150 
+    Das Tor-Netzwerk ist auf Freiwillige angewiesen, die Bandbreite spenden.
151 
+    Je mehr Menschen einen Tor-Server betreiben, desto schneller wird das
152 
+    Tor-Netzwerk. Wenn du über mindestens 20 KBytes/s verfügst, hilf bitte
153 
+    dem Tor-Netzwerk, indem du auch einen Tor-Server einrichtest. Server
154 
+    haben viele Eigenschaften, die ihren Betrieb einfach und bequem
155 
+    machen. Dazu gehöret die Begrenzung der Bandbreite, ExitPolicys, die
156 
+    das Risiko von Mißbrauch eingrenzen und Unterstützung von dynamischen
157 
+    IP-Adressen.</p>
158 
+
159 
+    <p>Viele Server an unterschiedlichen Stellen im Internet machen die
160 
+    Tor-Benutzer sicher. Du erhälst selbst eine <a
161 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerAnonymity">stärkere
162 
+    Anonymität</a>, weil fremde Webseiten nicht feststellen können, ob
163 
+    eine Verbindung von deinem Computer ausgeht oder ob sie für andere
164 
+    weitergeleitet wird.</p>
165 
+
166 
+    <p>Lies mehr in unserer Anleitung, wie man einen <a href="<page
167 
+    docs/tor-doc-relay>">Tor-Server konfiguriert</a>.</p>
168 
+
169 
+    <hr />
170 
+    <p> Sende Verbesserungsvorschläge für dieses Dokument bitte an
171 
+    <a href="<page about/contact>">uns</a>. Vielen Dank!</p>
172 
+  </div>
173 
+  <!-- END MAINCOL -->
174 
+  <div id = "sidecol">
175 
+#include "side.wmi"
176 
+#include "info.wmi"
177 
+  </div>
178 
+  <!-- END SIDECOL -->
179 
+</div>
180 
+<!-- END CONTENT -->
181 
+#include <foot.wmi>
docs/de/tor-hidden-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,264 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22314 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Versteckte Dienste bei Tor einrichten</h1>
14 
+    <hr />
15 
+
16 
+    <p>Mit Tor ist es möglich, versteckte Dienste, so genannte Hidden Services,
17 
+    anzubieten. Dies funktioniert sowohl mit einem Tor-Knoten, als auch mit einem
18 
+    Client. Damit kann man zum Beispiel einen Webserver, einen Mailserver oder
19 
+    einen SSH-Server anbieten, ohne die Identität preiszugeben. Es ist sogar
20 
+    möglich, solch einen Dienst hinter einer Firewall zu betreiben. </p>
21 
+
22 
+    <p>Wenn du bereits Tor installiert hast, kannst du unseren versteckten Dienst
23 
+    live unter <a href="http://duskgytldkxiuqc6.onion/">duskgytldkxiuqc6.onion</a>
24 
+    oder den versteckten Dienst von Wikileaks unter <a
25 
+    href="http://gaddbiwdftapglkq.onion/">gaddbiwdftapglkq.onion</a> erleben. </p>
26 
+
27 
+    <p>In diesem HowTo erfährst du, wie du eine eigene, versteckte Webseite
28 
+    betreiben kannst. Für technische Details, wie das Protokoll für die
29 
+    versteckten Dienste funktioniert, schau dir unsere <a href="<page
30 
+    docs/hidden-services>">hidden service protocol</a> Seite an.</p>
31 
+
32 
+    <hr />
33 
+    <a id="zero"></a>
34 
+    <h2><a class="anchor" href="#zero">Schritt Null: Bekomme Tor und Privoxy zum
35 
+    Laufen</a></h2>
36 
+    <br />
37 
+
38 
+    <p>Bevor es losgeht, überprüfe folgendes:</p>
39 
+    <ol>
40 
+    <li>Tor ist installiert und läuft.</li>
41 
+    <li>Privoxy oder Polipo installiert und läuft.</li>
42 
+    <li>Privoxy oder Polipo ist richtig eingerichtet und benutzt Tor und</li>
43 
+    <li>alles funktioniert so wie es soll.</li>
44 
+    </ol>
45 
+
46 
+    <p>Windows Nutzer sollten dem <a href="<page docs/tor-doc-windows>">Windows
47 
+    HowTo</a>, OS X Nutzer dem <a href="<page docs/tor-doc-osx>">OS X HowTo</a>,
48 
+    und Linux/BSD/Unix Nutzer dem <a href="<page docs/tor-doc-unix>">Unix HowTo</a>
49 
+     folgen.</p>
50 
+
51 
+    <p>Wenn du alles eingerichtet hast, versuche nochmal den oben erwähnten
52 
+    versteckten Dienst unter <a href="http://duskgytldkxiuqc6.onion/">
53 
+    duskgytldkxiuqc6.onion</a> oder den versteckten Dienst von Wikileaks unter <a
54 
+    href="http://gaddbiwdftapglkq.onion/">gaddbiwdftapglkq.onion</a> zu erreichen.
55 
+    Normalerweise dauert es zwischen 10&mdash;60 Sekunden, bis die Seite geladen
56 
+    ist (oder bis sich herausstellt, dass sie gerade unerreichbar ist). Wenn es
57 
+    gleich zu Beginn fehlschlägt und dein Browser eine Meldung bringt wie
58 
+    "www.duskgytldkxiuqc6.onion could not be found, please check the name and try
59 
+    again" scheinst du Tor und Privoxy nicht richtig konfiguriert zu haben. Zum
60 
+    dem Problem gibt es einen <a
61 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">
62 
+    Eintrag in der FAQ</a>, der dir vielleicht weiterhelfen kann. </p>
63 
+
64 
+    <hr />
65 
+    <a id="one"></a>
66 
+    <h2><a class="anchor" href="#one">Schritt Eins: Installiere einen lokalen
67 
+    Webserver</a></h2>
68 
+    <br />
69 
+
70 
+    <p>Als Erstes musst du einen lokalen Webserver einrichten. Das kann durchaus
71 
+    kompliziert sein, daher können wir nur ganz grundlegende Hilfestellung geben.
72 
+    Solltest du Probleme haben, frage einen Freund um Hilfe. Wir empfehlen die
73 
+    Installation eines neuen, separaten Webservers für den versteckten Dienst,
74 
+    weil du einen bereits installierten möglicherweise bereits für eine andere
75 
+    Seite benutzt oder mal benutzen möchtest. </p>
76 
+
77 
+    <p>Wenn du Unix oder OS X benutzt und dich mit der Kommandozeile auskennst,
78 
+    ist der beste Weg, wenn du dir <a href="http://www.acme.com/software/thttpd/">
79 
+    thttpd</a> installierst. Hol dir einfach den neuesten Tarball und entpacke
80 
+    ihn. Mittels <kbd>./configure &amp;&amp; make</kbd> wird der Server
81 
+    installiert. Danach musst du noch <kbd>mkdir hidserv; cd hidserv</kbd>
82 
+    eingeben und danach mittels <kbd>../thttpd -p 5222 -h localhost</kbd> den
83 
+    Server starten. Du landest wieder auf der Kommandozeile, hast aber jetzt einen
84 
+    Webserver auf Port 5222 laufen. Du kannst Dateien, die er ausliefern soll,
85 
+    einfach in das hidserv Verzeichnis legen. </p>
86 
+
87 
+    <p>Wenn du unter Windows arbeitest, wählst du am Besten <a
88 
+    href="http://savant.sourceforge.net/">Savant</a> oder <a
89 
+    href="http://httpd.apache.org/">Apache</a>. Versichere dich aber, dass der
90 
+    Server nur an localhost gebunden ist. Ausserdem solltest du wissen, auf
91 
+    welchem Port der Server lauscht, diese Information brauchst du gleich. </p>
92 
+
93 
+    <p>(Das Binden an localhost stellt sicher, dass der Server nur über Tor
94 
+    ansprechbar ist. Ansonsten könnte man vielleicht auf diese Weise den Betreiber
95 
+    des versteckten Dienstes enttarnen.) </p>
96 
+
97 
+    <p>Wenn du den Server eingerichtet hast, solltest du dich davon überzeugen,
98 
+    dass er funktioniert: starte deinen Browser und besuche <a
99 
+    href="http://localhost:5222/">http://localhost:5222/</a>. 5222 ist der Port, an
100 
+    dem dein Webserver lauscht. Wenn das geht, versuche eine Datei, in das
101 
+    Verzeichnis zu legen und schaue, ob sie im Browser auftaucht, wenn du die
102 
+    Ansicht aktualisierst. </p>
103 
+
104 
+    <hr />
105 
+    <a id="two"></a>
106 
+    <h2><a class="anchor" href="#two">Schritt Zwei:
107 
+    Einrichtung des versteckten Dienstes</a></h2>
108 
+    <br />
109 
+
110 
+    <p>Als nächsten Schritt musst du deinen versteckten Dienst einrichten, damit
111 
+    er auf deinen Webserver zeigt. </p>
112 
+
113 
+    <p>Erstens: Öffne deine torrc in einem Text-Editor. (Unter <a
114 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc
115 
+    FAQ Eintrag</a> steht, was das bedeutet.) Etwa in der Mitte der Datei steht
116 
+    die folgende Zeile:</p>
117 
+
118 
+    <pre><p> \############### This section is just for location-hidden services ###</p>
119 
+    </pre>
120 
+
121 
+    <p> Dieser Abschnitt besteht aus Zeilengruppen. Jede steht für einen
122 
+    versteckten Dienst. Zu Beginn sind alle auskommentiert (haben also ein # als
123 
+    erstes Zeichen), versteckte Dienste sind also nicht aktiv. Jede Zeilengruppe
124 
+    besteht aus einer <var>HiddenServiceDir</var>-Zeile und einer oder mehreren
125 
+    <var>HiddenServicePort</var>-Zeilen:</p>
126 
+    <ul>
127 
+    <li><var>HiddenServiceDir</var>
128 
+    ist ein Verzeichnis, in dem Tor Informationen über den Hidden Service
129 
+    speichert. Genauer gesagt: Tor wird hier eine Datei namens <var>hostname</var>
130 
+    erstellen, in der die URL des versteckte Dienste steht. Du musst keine
131 
+    Dateien in das Verzeichnis legen.</li>
132 
+    <li><var>HiddenServicePort</var> lässt
133 
+    dich einen virtuellen Port (das ist der Port, mit dem Nutzer auf deinen
134 
+    versteckten Dienst zugreifen können) und eine IP-Adresse sowie Port (an welche
135 
+    die Anfragen dann weitergeleitet werden) festlegen. </li>
136 
+    </ul>
137 
+
138 
+    <p>Damit unser Beispiel-Webserver funktioniert, musst du die folgenden Zeilen
139 
+    in deine torrc hinzufügen: </p>
140 
+
141 
+    <pre><p>HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/<br />
142 
+    HiddenServicePort 80 127.0.0.1:5222</p></pre>
143 
+
144 
+    <p>Du solltest die Variable <var>HiddenServiceDir</var> so wählen, dass der
145 
+    Nutzer der
146 
+    Tor laufen lässt, darauf Lese- und Schreibzugriff besitzt. Die Zeile oben
147 
+    sollten auch für das OS X Paket funktionieren. Unter Unix, müsste
148 
+    "/home/username/hidserv/" gehen (natürlich musst du "username" mit deinem
149 
+    eigenen Benutzernamen ersetzen). Unter Windows sollte folgendes funktionieren
150 
+    (natürlich auch mit dem richtigen Benutzernamen):</p>
151 
+    <pre>HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\\
152 
+    HiddenServicePort 80 127.0.0.1:5222 </pre>
153 
+
154 
+    <p>Jetzt musst du deine veränderte torrc speichern und Tor neustarten. </p>
155 
+
156 
+    <p>Wenn Tor startet, ist das schon mal super. Wenn nicht, ist etwas schief
157 
+    gegangen. Als erstes solltest du in deinen Logfiles nach Hinweisen suchen. Tor
158 
+    wird Warnungen oder sogar Fehler ausgeben. Damit solltest du in der Lage sein,
159 
+    das Problem einzugrenzen. Typischerweise hast du Tippfehler in deiner torrc
160 
+    oder fehlende Schreib- und Leserechte in den angegebenen Verzeichnissen.
161 
+    (Unter <a
162 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">Der
163 
+    Logfile FAQ Eintrag</a> findest du weitere Hilfe, wenn du Probleme hast die
164 
+    Logs zu finden oder zu aktivieren. </p>
165 
+
166 
+    <p>Wenn Tor startet wird es automatisch das Verzeichnis in
167 
+    <var>HiddenServiceDir</var>, falls nötig, anlegen und darin 2 Dateien
168 
+    ablegen.</p>
169 
+
170 
+    <dl>
171 
+    <dt><var>private_key</var></dt>
172 
+    <dd>Als Erstes wird Tor ein neues
173 
+    Schlüsselpaar mit öffentlichem und privatem Schlüssel für deinen versteckten
174 
+    Dienst erzeugen. Dieses Paar wird in die Datei namens "private_key"
175 
+    geschrieben. Diese Datei darfst du unter keinen Umständen weitergeben,
176 
+    ansonsten könnten andere deine Identität annehmen.</dd>
177 
+    <dt><var>hostname</var></dt>
178 
+    <dd>Die andere Datei die Tor erstellt nennt sich "hostname". Dabei
179 
+    handelt es sich um eine kurze Zusammenfassung deines öffentlichen Schlüssels.
180 
+    Diese Zusammenfassung sieht etwa folgendermaßen aus: <tt>
181 
+    duskgytldkxiuqc6.onion</tt>. Dabei handelt es sich gleichzeitig auch um die
182 
+    Adresse deines versteckte Dienste, die du an andere Menschen weitergeben oder
183 
+    z.B. im Internet veröffentlichen kannst.</dd>
184 
+    </dl>
185 
+
186 
+    <p>Wenn Tor unter einem anderen Benutzeraccount läuft, musst du möglicherweise
187 
+    die Rechte des Hauptnutzers (root, Administrator) haben, damit du die Dateien
188 
+    anschauen kannst.</p>
189 
+
190 
+    <p>Nach einem Neustart ist Tor erstmal damit beschäftigt, sogenannte
191 
+    Introduction Points auszuwählen und einen <em>hidden service descriptor</em>
192 
+    zu erzeugen. Dabei handelt es sich um eine unterschriebene Liste von
193 
+    Introduction Points mit dem vollständigen öffentlichen Schlüssel des
194 
+    versteckten Dienstes. Diese Beschreibung veröffentlicht dein Client dann
195 
+    anonym auf den Verzeichnisservern, wo andere Leute, die deinen versteckten
196 
+    Dienst besuchen wollen, ihn dann ebenfalls anonym abrufen. </p>
197 
+
198 
+    <p>Jetzt kannst du es versuchen: Kopiere den Inhalt der hostname-Datei in
199 
+    deinen Webbrowser. Wenn es klappt, solltest du die vorher eingerichtete
200 
+    HTML-Seite bekommen. Wenn es nicht geht, schau in deinen
201 
+    Logs nach Hinweisen und versuche diesen nachzugehen, bis es klappt. </p>
202 
+
203 
+    <hr />
204 
+    <a id="three"></a>
205 
+    <h2><a class="anchor" href="#three">Schritt Drei:
206 
+    Tipps für Fortgeschrittene</a></h2>
207 
+    <br />
208 
+
209 
+    <p>Wenn du vor hast deinen versteckten Dienst über längere Zeit anzubieten,
210 
+    solltest du den privaten Schlüssel des Dienstes, also die
211 
+    <var>private_key</var> Datei redundant sichern. </p>
212 
+
213 
+    <p>Wir haben weiter oben bewusst nicht den Webserver Apache empfohlen, weil er
214 
+    a) vielleicht
215 
+    schon für andere Webseiten auf dem Rechner eingesetzt wird und er b) sehr groß
216 
+    und kompliziert ist und an vielen Stellen deine wirkliche IP verraten könnte
217 
+    (z.B. auf 404 Seiten). Für Leute, die etwas mehr Funktionalität brauchen,
218 
+    könnte Apache aber genau das Richtige sein. Wir bräuchten daher eine
219 
+    Checkliste, wie man seinen Apache absichert, wenn du ihn für versteckte
220 
+    Dienste nutzen willst. Es wäre toll, wenn die uns jemand erstellen könnte.
221 
+    Savant hat möglicherweise ähnliche Probleme. </p>
222 
+
223 
+    <p>Wenn du mehrere virtuelle Adressen an einen einzelnen versteckten Dienst
224 
+    weiterleiten willst, musst du einfach mehr <var>HiddenServicePort</var>-Zeilen
225 
+    einfügen. Wenn du mehrere versteckte Dienste mit dem gleichen Tor-Client
226 
+    anbieten möchtest, must du einfach eine weitere
227 
+    <var>HiddenServiceDir</var>-Zeile einfügen. Alle danach folgenden
228 
+    <var>HiddenServicePort</var>-Zeilen
229 
+    beziehen sich dann auf diese <var>HiddenServiceDir</var>-Zeile, bis du eine
230 
+    neue <var>HiddenServiceDir</var>-Zeile einfügst: </p>
231 
+
232 
+    <pre> HiddenServiceDir /usr/local/etc/tor/hidden_service/ HiddenServicePort 80
233 
+    127.0.0.1:8080
234 
+
235 
+    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/ HiddenServicePort
236 
+    6667 127.0.0.1:6667 HiddenServicePort 22 127.0.0.1:22 </pre>
237 
+
238 
+    <p>Du solltest dir ein paar Gedanken über deine Anonymität machen: </p>
239 
+
240 
+    <ul>
241 
+    <li>Wie bereits erwähnt, solltest du aufpassen, dass dein Webserver keine
242 
+    Informationen über dich, deinen Computer oder deinen Aufenthaltsort
243 
+    herausgibt. Zum Beispiel könnte jemand herausfinden, ob du thttpd oder Apache
244 
+    einsetzt und könnte dann auch noch etwas über dein Betriebssystem
245 
+    herausfinden.</li>
246 
+    <li>Wenn dein Rechner nicht immer online ist, ist es auch
247 
+    dein verstecker Dienst nicht. Dadurch hinterlässt du Spuren, die jemand
248 
+    interessieren könnten.</li> <!-- increased risks over time -->
249 
+    </ul>
250 
+
251 
+    <hr />
252 
+
253 
+    <p>Wenn du Vorschläge hast, wie wir dieses Dokument verbessern könnten, <a
254 
+    href="<page about/contact>">schick Sie uns bitte zu.</a> Danke!</p>
255 
+  </div>
256 
+  <!-- END MAINCOL -->
257 
+  <div id = "sidecol">
258 
+#include "side.wmi"
259 
+#include "info.wmi"
260 
+  </div>
261 
+  <!-- END SIDECOL -->
262 
+</div>
263 
+<!-- END CONTENT -->
264 
+#include <foot.wmi>
docs/el/N900.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,157 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21979 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: N900 Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/N900>">N900</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="Maemo"></a>
14 
+    <h2><a class="anchor" href="#Maemo">Εγκατάσταση του Tor στο Maemo</a></h2>
15 
+    <br />
16 
+    <p>
17 
+    Αν έχετε κάποια συσκευή Maemo εκτός της <a href="#N900">N900</a>,
18 
+    προτείνουμε αν εγκαταστήσετε το πακέτο Tor από την <a
19 
+    href="http://maemo.org/packages/view/tor/">ιστοσελια του Maemo</a>. Το Tor
20 
+    Project δεν δημιουργεί τέτοιο πακέτο. Αυτό συντηρείται από την κοινότητα του
21 
+    Maemo.
22 
+    </p>
23 
+
24 
+    <a id="N900"></a>
25 
+    <h2><a class="anchor" href="#N900">Εγκατάσταση του Tor στο Ν900</a></h2>
26 
+    <br />
27 
+    <p>
28 
+    Οι οδηγίες που ακολουθούν θα σας βοηθήσουν να εγκαταστήσετε έναν <a
29 
+    href="https://garage.maemo.org/projects/tor-status">πειραματικό ελεγκτή
30 
+    Tor</a> και το Tor στο τηλέφωνο Nokia N900. Πρόκειται για μη ελεγμένες
31 
+    ρυθμίσεις. Ο φυλλομετριτής ιστού σε αυτή την ρύθμιση δεν περιλαμβάνει το
32 
+    Torbutton και προς το παρόν δεν θα πρέπει να χρησιμοποιείται για ανάγκες
33 
+    ανωνυμίας υψηλής ασφάλειας.
34 
+    </p>
35 
+
36 
+    <p>
37 
+    Ανοίξτε τον διαχειριστή Εφαρμογών: <br /> <a
38 
+    href="../img/N900/1_app_menu.png"> <img border="0" alt="N900 application
39 
+    menu" src="../img/N900/1_app_menu-small.png"/> </a>
40 
+    </p>
41 
+
42 
+    <p>
43 
+    Κάνετε κλικ στο μενού του διαχειριστή Εφαρμογών στην κορυφή της οθόνης: <br
44 
+    /> <a href="../img/N900/2_app_manager.png"> <img border="0" alt="N900
45 
+    application manager" src="../img/N900/2_app_manager-small.png"/> </a>
46 
+    </p>
47 
+
48 
+    <p>
49 
+    Επιλέξτε 'κατάλογοι Εφαρμογών': <br /> <a
50 
+    href="../img/N900/3_app_managermenu.png"> <img border="0" alt="N900
51 
+    application catalogs" src="../img/N900/3_app_managermenu-small.png"/> </a>
52 
+    </p>
53 
+
54 
+    <p>
55 
+    Πατήστε 'Νέο' για να ενεργοποιήσετε το αποθετήριο maemo extras-level. <br />
56 
+    <small>Σημείωση: Το αποθετήριο αυτό περιέχει μη ελεγμένα πακέτα τα οποία
57 
+    ίσως βλάψουν τη συσκεύ σας. <br /> Διαβάστε το <a
58 
+    href="http://wiki.maemo.org/Extras-devel">Extras-devel</a> για
59 
+    λεπτομέρειες. Ίσως χρειαστεί να απενεργοποιήσετε το αποθετήριο extras-level
60 
+    μετά την εγκατάσταση του Tor, ή συνεχίστε με δική σας ευθύνη.</small> <br />
61 
+    <a href="../img/N900/4_catalog_list.png"> <img border="0" alt="N900 catalog
62 
+    list" src="../img/N900/4_catalog_list-small.png"/> </a>
63 
+    </p>
64 
+
65 
+    <p>
66 
+    Εισάγετε τις ακόλουθες πληροφορίες στην οθόνη προσθήκης καταλόγου:
67 
+    <p>
68 
+    <pre>
69 
+    Όνομα Καταλόγου:    Extras devel
70 
+    Διεύθυνση Web:    http://repository.maemo.org/extras-devel/
71 
+    Διανομή:        fremantle
72 
+    Συστατικά:    free non-free
73 
+    </pre>
74 
+    </p>
75 
+    <br /> Βεβαιωθείτε ότι το 'Απενεργοποιημένο' δεν είναι επιλεγμένο και
76 
+    πατήστε 'Αποθήκευση' και περιμένετε να ανανεωθεί η λίστα των πακέτων.<br />
77 
+    <a href="../img/N900/5_new_catalog.png"> <img border="0" alt="N900 new
78 
+    catalog" src="../img/N900/5_new_catalog-small.png"/> </a>
79 
+    </p>
80 
+
81 
+    <p>
82 
+    Πατήστε 'Λήψη' στον διαχειριστή Εφαρμογών: <br /> <a
83 
+    href="../img/N900/6_app_manager.png"> <img border="0" alt="N900 app manager"
84 
+    src="../img/N900/6_app_manager-small.png"/> </a>
85 
+    </p>
86 
+
87 
+    <p>
88 
+    Επιλέξτε την κατηγορία Δικτύου (ή αναζητήστε το Tor): <br /> <a
89 
+    href="../img/N900/7_app_categories.png"> <img border="0" alt="N900
90 
+    application categories" src="../img/N900/7_app_categories-small.png"/> </a>
91 
+    </p>
92 
+
93 
+    <p>
94 
+    Κυλήστε την λίστα προς τα κάτω και επιλέξτε 'Εφαρμογίδιο Περιοχής Κατάστασης
95 
+    Tor': <br /> <a href="../img/N900/8_app_list.png"> <img border="0" alt="N900
96 
+    application list" src="../img/N900/8_app_list-small.png"/> </a>
97 
+    </p>
98 
+
99 
+    <p>
100 
+    Συμφωνήστε με την δήλωση και πατήστε 'Συνέχεια': <br /> <a
101 
+    href="../img/N900/9_disclaimer.png"> <img border="0" alt="N900 disclaimer"
102 
+    src="../img/N900/9_disclaimer-small.png"/> </a>
103 
+    </p>
104 
+
105 
+    <p>
106 
+    Όταν η εγκατάσταση ολοκληρωθεί απενεργοποιήστε το αποθετήριο extras-level
107 
+    και επανεκκινήστε την συσκευή σας: <br /> <a
108 
+    href="../img/N900/10_success.png"> <img border="0" alt="N900 success"
109 
+    src="../img/N900/10_success-small.png"/> </a>
110 
+    </p>
111 
+
112 
+    <p>
113 
+    Μετά την επανεκκίνηση του Ν900 ανοίξτε το μενού κατάσταση: <br /> <a
114 
+    href="../img/N900/11_after_rebooting.png"> <img border="0" alt="N900 status
115 
+    menu post-reboot" src="../img/N900/11_after_rebooting-small.png"/> </a>
116 
+    </p>
117 
+
118 
+    <p>
119 
+    Επιλέξτε από την λίστα "Ο Δρομολογητής Onion': <br /> <a
120 
+    href="../img/N900/12_status_menu.png"> <img border="0" alt="N900 status menu
121 
+    selection" src="../img/N900/12_status_menu-small.png"/> </a>
122 
+    </p>
123 
+
124 
+    <p>
125 
+    Ενεργοποιήστε την δρομολόγηση onion και πατήστε 'Αποθήκευση': <br /> <a
126 
+    href="../img/N900/13_enable_tor.png"> <img border="0" alt="N900 enabling
127 
+    Tor" src="../img/N900/13_enable_tor-small.png"/> </a>
128 
+    </p>
129 
+
130 
+    <p>
131 
+    Επισκεφθείτε την ιστοσελίδα <a
132 
+    href="https://check.torproject.org/">TorCheck</a> για να επιβεβαιώσετε ότι
133 
+    κατευθείνετε την κυκλοφορία του φυλλομετρητή σας μέσω του Tor: <br /> <a
134 
+    href="../img/N900/14_check_tor.png"> <img border="0" alt="N900 check Tor"
135 
+    src="../img/N900/14_check_tor-small.png"/> </a>
136 
+    </p>
137 
+
138 
+    <p>
139 
+    Σημειώστε ότι η διαδικασία αυτή δεν παρέχει πάντοτε την πιο πρόσφατη σταθερή
140 
+    έκδοση.  Επιπρόσθετε, ο φυλλομετρητής του Ν900 δεν διαθέτει Torbutton. Αυτό
141 
+    δεν είναι κατάλληλο για απαιτήσεις ισχυρής ανωνυμίας.
142 
+    </p>
143 
+
144 
+    <hr />
145 
+
146 
+    <p>Αν έχετε προτάσεις για βελτίωση αυτού του εγγράφου, παρακαλούμε να μας τις
147 
+    <a href="<page about/contact>">στείλετε</a>. Ευχαριστούμε!</p>
148 
+  </div>
149 
+  <!-- END MAINCOL -->
150 
+  <div id = "sidecol">
151 
+#include "side.wmi"
152 
+#include "info.wmi"
153 
+  </div>
154 
+  <!-- END SIDECOL -->
155 
+</div>
156 
+<!-- END CONTENT -->
157 
+#include <foot.wmi>
docs/el/debian-vidalia.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,120 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22269 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Vidalia: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian-vidalia>">Vidalia Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a> <a id="packages"></a>
14 
+    <h2><a class="anchor" href="#debian">Το Vidalia σε Ubuntu ή Debian</a></h2>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>Μην χρησιμοποιείτε τα πακέτα universe του Ubuntu.</b> Δεν συντηρούνται
19 
+    και είναι παρωχημένα. Αυτό σημαίνει ότι δεν θα έχετε ενημερώσεις βελτίωσης
20 
+    της σταθερότητας και της ασφάλειας.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    You'll need to set up our package repository before you can fetch
25 
+    Vidalia. First, you need to figure out the name of your distribution. If
26 
+    you're using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty",
27 
+    8.10 is "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's
28 
+    "etch", and Debian Lenny is "lenny". Then add this line to your
29 
+    <tt>/etc/apt/sources.list</tt> file:<br />
30 
+    <pre>
31 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
32 
+    </pre>
33 
+    στην οποία πρέπει να θέσετε τις παραπάνω λέξεις (etch, lenny, sid, karmic,
34 
+    jaunty, intrepid, hardy) στην θέση της λέξης &lt;DISTRIBUTION&gt;.
35 
+    </p>
36 
+
37 
+    <p>
38 
+    Προσθέστε μετά το κλειδί gpg που χρησιμοποιείται για την υπογραφή των
39 
+    πακέτων, εκτελώντας τις ακόλουθες εντολές σε ένα τερματικό:
40 
+    <pre>
41 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
42 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
43 
+    </pre>
44 
+    Ανανεώστε τις πηγές λογισμικού και εγκαταστήστε το Vidalia εκτελώντας τις
45 
+    ακόλουθες εντολές στην γραμμή εντολής:
46 
+    <pre>
47 
+    apt-get update
48 
+    apt-get install vidalia
49 
+    </pre>
50 
+    </p>
51 
+
52 
+    <p>
53 
+    Το Vidalia εγκαταστάθηκε και εκτελείται. Πηγαίνετε στο <a href="<page
54 
+    docs/tor-doc-unix>#polipo">δεύτερο βήμα</a> των οδηγιών "Το Vidalia σε
55 
+    Linux/Unix".
56 
+    </p>
57 
+
58 
+    <p style="font-size: small">
59 
+    Το όνομα DNS <code>deb.torproject.org</code> είναι ένα σύνολο ανεξάρτητων
60 
+    διακομιστών με ρύθμιση για Round Robin DNS. Αν για κάποιον λόγο δεν έχετε
61 
+    πρόσβαση σε αυτό, μπορείτε αντ' αυτού να χρησιμοποιήσετε το όνομα ενός
62 
+    τμήματός του. Δοκιμάστε τα <code>deb-master.torproject.org</code>,
63 
+    <code>mirror.netcologne.de</code> ή <code>vidalia.mirror.youam.de</code>.
64 
+    </p>
65 
+
66 
+    <hr />
67 
+
68 
+    <a id="source"></a>
69 
+    <h2><a class="anchor" href="#source">Εγκατάσταση από τον πηγαίο κώδικα</a></h2>
70 
+    <br />
71 
+
72 
+    <p>
73 
+    Αν θέλετε να φτιάξετε τα δικά σας αρχεία deb από τον πηγαίο κώδικα, πρέπει
74 
+    πρώτα να προσθέσετε την κατάλληλη γραμμή <tt>deb-src</tt> στο αρχείο
75 
+    <tt>sources.list</tt>.
76 
+    <pre>
77 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
78 
+    </pre>
79 
+    Πρέπει επίσης να εγκαταστήσετε τα απαραίτητα πακέτα που βοηθούν στην
80 
+    κατασκευή των αρχείων deb και τα πακέτα που χρειάζονται για την δημιουργία
81 
+    των πακέτων deb για το Vidalia:
82 
+    <pre>
83 
+    apt-get install build-essential fakeroot devscripts qt4-dev-tools qt4-designer libqt4-dev g++ cmake
84 
+    apt-get build-dep vidalia
85 
+    </pre>
86 
+    Έπειτα μπορείτε να δημιουργήσετε τα αρχεία deb για το Vidalia στον κατάλογο
87 
+    ~/debian-packages:
88 
+    <pre>
89 
+    mkdir ~/debian-packages; cd ~/debian-packages
90 
+    apt-get source vidalia
91 
+    cd vidalia-*
92 
+    debuild -rfakeroot -uc -us
93 
+    cd ..
94 
+    </pre>
95 
+    Τώρα μπορείτε να εγκαταστήσετε τα νέα πακέτα:
96 
+    <pre>
97 
+    sudo dpkg -i vidalia_*.deb
98 
+    </pre>
99 
+    </p>
100 
+
101 
+    <p>
102 
+    Το Vidalia εγκαταστάθηκε και εκτελείται. Πηγαίνετε στο <a href="<page
103 
+    docs/tor-doc-unix>#polipo">δεύτερο βήμα</a> των οδηγιών "Το Vidalia σε
104 
+    Linux/Unix".
105 
+    </p>
106 
+
107 
+    <hr />
108 
+
109 
+    <p>Αν έχετε προτάσεις για την βελτίωση του παρόντος εγγράφου, παρακαλούμε <a
110 
+    href="<page about/contact>">να τις υποβάλετε</a>. Ευχαριστούμε!</p>
111 
+  </div>
112 
+  <!-- END MAINCOL -->
113 
+  <div id = "sidecol">
114 
+#include "side.wmi"
115 
+#include "info.wmi"
116 
+  </div>
117 
+  <!-- END SIDECOL -->
118 
+</div>
119 
+<!-- END CONTENT -->
120 
+#include <foot.wmi>
docs/el/debian.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,189 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22268 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian>">Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <h2><a class="anchor" href="#debian">Επιλογή πρώτη: Το Tor σε Debian lenny,
15 
+    Debian sid ή Debian testing</a></h2>
16 
+    <br />
17 
+
18 
+    <p>
19 
+    If you're using Debian stable (lenny), unstable (sid), or testing (squeeze),
20 
+    just run<br />
21 
+    <tt>apt-get install tor tor-geoipdb</tt> as root.
22 
+    </p>
23 
+
24 
+    <p>
25 
+    Σημειώστε ότι η διαδικασία αυτή δεν παρέχει πάντοτε την τελευταία σταθερή
26 
+    έκδοση, αλλά θα λαμβάνετε σημαντικές ενημερώσεις ασφαλείας. Για να
27 
+    βεβαιωθείτε ότι έχετε την πιο πρόσφατη σταθερή έκδοση του Tor, δείτε την
28 
+    δεύτερη επιλογή πιο κάτω.
29 
+    </p>
30 
+
31 
+    <p>
32 
+    Το Tor είναι τώρα εγκατεστημένο και εκτελείται. Πηγαίνετε στο <a href="<page
33 
+    docs/tor-doc-unix>#polipo">δεύτερο βήμα</a> των οδηγιών "Το Tor σε
34 
+    Linux/Unix".
35 
+    </p>
36 
+
37 
+    <hr />
38 
+
39 
+    <a id="ubuntu"></a> <a id="packages"></a>
40 
+    <h2><a class="anchor" href="#ubuntu">Δεύτερη επιλογή: Tο Tor σε Ubuntu ή
41 
+    Debian</a></h2>
42 
+    <br />
43 
+
44 
+    <p>
45 
+    <b>Μην χρησιμοποιείτε τα πακέτα του Ubuntu universe.</b> Δεν συντηρούνται
46 
+    και είναι παρωχημένα. Αυτό σημαίνει ότι δεν θα παραλαμβάνετε ενημερώσεις
47 
+    σταθερότητας και ασφάλειας.
48 
+    </p>
49 
+
50 
+    <p>
51 
+    You'll need to set up our package repository before you can fetch
52 
+    Tor. First, you need to figure out the name of your distribution. If you're
53 
+    using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty", 8.10 is
54 
+    "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's "etch",
55 
+    and Debian Lenny is "lenny". Then add this line to your
56 
+    <tt>/etc/apt/sources.list</tt> file:<br />
57 
+    <pre>
58 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
59 
+    </pre>
60 
+    όπου στην θέση &lt;DISTRIBUTION&gt; πληκτρολογείτε την κωδική ονομασία της
61 
+    διανομής σας (δηλαδή, etch, lenny, sid, karmic, jaunty, intrepid, hardy ή
62 
+    όποια είναι η ονομασία αυτή).
63 
+    </p>
64 
+
65 
+    <p>
66 
+    Μετά προσθέστε το κλειδί gpg με το οποίο υπογράφονται τα πακέτα εκτελώντας
67 
+    την ακόλουθη εντολή στην γραμμή εντολής:
68 
+    <pre>
69 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
70 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
71 
+    </pre>
72 
+    Ανανεώστε τις πηγές λογισμικού και εγκαταστήστε το Tor εκτελώντας την
73 
+    ακόλουθη εντολή στην γραμμή εντολής:
74 
+    <pre>
75 
+    apt-get update
76 
+    apt-get install tor tor-geoipdb
77 
+    </pre>
78 
+    </p>
79 
+
80 
+    <p>
81 
+    Το Tor είναι τώρα εγκατεστημένο και εκτελείται. Πηγαίνετε στο <a href="<page
82 
+    docs/tor-doc-unix>#polipo">δεύτερο βήμα</a> των οδηγιών "Το Tor σε
83 
+    Linux/Unix".
84 
+    </p>
85 
+
86 
+    <p style="font-size: small">
87 
+    Το όνομα DNS <code>deb.torproject.org</code> είναι απλώς ένα σύνολο
88 
+    ανεξάρτητων διακομιστών ρυθμισμένο ως DNS round robin. Αν για κάποιον λόγο
89 
+    δεν έχετε πρόσβαση σε αυτό, δοκιμάστε να χρησιμοποιήσετε κάποιο από τα μέρη
90 
+    του. Δοκιμάστε <code>deb-master.torproject.org</code>,
91 
+    <code>mirror.netcologne.de</code> ή <code>tor.mirror.youam.de</code>.
92 
+    </p>
93 
+
94 
+    <hr />
95 
+
96 
+    <a id="development"></a>
97 
+    <h2><a class="anchor" href="#development">Τρίτη επιλογή: Χρήση του κλάδου
98 
+    ανάπτυξης του Tor σε Debian ή Ubuntu</a></h2>
99 
+    <br />
100 
+
101 
+    <p>If you want to use the <a href="<page download/download>#packagediff">development
102 
+    branch</a> of Tor instead (more features and more bugs), you need to add a
103 
+    different set of lines to your <tt>/etc/apt/sources.list</tt> file:<br />
104 
+    <pre>
105 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
106 
+    deb     http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
107 
+    </pre>
108 
+    όπου και πάλι βάζετε το όνομα της διανομής σας (etch, lenny, sid, karmic,
109 
+    jaunty, intrepid, hardy) στη θέστη του &lt;DISTRIBUTION&gt;.
110 
+    </p>
111 
+
112 
+    <p>
113 
+    Μετά εκτελέστε την ακόλουθη εντολή από την γραμμή εντολής:
114 
+    <pre>
115 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
116 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
117 
+    apt-get update
118 
+    apt-get install tor tor-geoipdb
119 
+    </pre>
120 
+    </p>
121 
+
122 
+    <p>
123 
+    Το Tor είναι τώρα εγκατεστημένο και εκτελείται. Πηγαίνετε στο <a href="<page
124 
+    docs/tor-doc-unix>#polipo">δεύτερο βήμα</a> των οδηγιών "Το Tor σε
125 
+    Linux/Unix".
126 
+    </p>
127 
+
128 
+    <hr />
129 
+
130 
+    <a id="source"></a>
131 
+    <h2><a class="anchor" href="#source">Εγκατάσταση από τον πηγαίο κώδικα</a></h2>
132 
+    <br />
133 
+
134 
+    <p>
135 
+    Εάν θέλετε να δημιουργήσετε τα δικά σας αρχεία deb από τον πηγαίο κώδικα,
136 
+    πρώτα πρέπει να προσθέσετε μια κατάλληλη γραμμή <tt>deb-src</tt> στο αρχείο
137 
+    <tt>sources.list</tt>.
138 
+    <pre>
139 
+    # For the stable version.
140 
+    # For the unstable version.
141 
+
142 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
143 
+
144 
+
145 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
146 
+    deb-src http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
147 
+    </pre>
148 
+    Πρέπει, επίσης, να εγκαταστήσετε τα αναγκαία πακέτα για την δημιουργία των
149 
+    δικών σας αρχείων deb και τα πακέτα που χρειάζονται για την δημιουργία του
150 
+    Tor:
151 
+    <pre>
152 
+    apt-get install build-essential fakeroot devscripts
153 
+    apt-get build-dep tor
154 
+    </pre>
155 
+    Έπειτα μπορείτε να δημιουργήσετε τα αρχεία deb για το Tor στον κατάλογο
156 
+    ~/debian-packages:
157 
+    <pre>
158 
+    mkdir ~/debian-packages; cd ~/debian-packages
159 
+    apt-get source tor
160 
+    cd tor-*
161 
+    debuild -rfakeroot -uc -us
162 
+    cd ..
163 
+    </pre>
164 
+    Μπορείτε, τώρα, να εγκαταστήσετε τα νέα πακέτα:
165 
+    <pre>
166 
+    sudo dpkg -i tor_*.deb
167 
+    </pre>
168 
+    </p>
169 
+
170 
+    <p>
171 
+    Το Tor είναι τώρα εγκατεστημένο και εκτελείται. Πηγαίνετε στο <a href="<page
172 
+    docs/tor-doc-unix>#polipo">δεύτερο βήμα</a> των οδηγιών "Το Tor σε
173 
+    Linux/Unix".
174 
+    </p>
175 
+
176 
+    <hr />
177 
+
178 
+    <p>Αν έχετε προτάσεις για την βελτίωση του παρόντος εγγράφου, παρακαλούμε να
179 
+    μας τις href="<page about/contact>">στείλετε</a>. Ευχαριστούμε!</p>
180 
+  </div>
181 
+  <!-- END MAINCOL -->
182 
+  <div id = "sidecol">
183 
+#include "side.wmi"
184 
+#include "info.wmi"
185 
+  </div>
186 
+  <!-- END SIDECOL -->
187 
+</div>
188 
+<!-- END CONTENT -->
189 
+#include <foot.wmi>
docs/el/rpms.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,78 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21907 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: CentOS/Fedora/OpenSUSE Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/rpms>">RPMs</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="rpms"></a>
14 
+    <h2><a class="anchor" href="#rpms">Πακέτα Tor για διανομές Linux που βασίζονται
15 
+    σε rpm.</a></h2>
16 
+    <br />
17 
+
18 
+    <p>Μην χρησιμοποιείτε τα πακέτα των εσωτερικών ή τοπικών αποθετηρίων. Συχνά
19 
+    είναι παρωχημένα. Αυτό σημαίνει ότι δεν θα έχετε ενημερώσεις σταθερότητας
20 
+    και ασφάλειας.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    Πριν κατεβάσετε το Tor πρέπει να ρυθμίσετε το αποθετήριο των πακέτων
25 
+    μας. Υποθέτοντας ότι χρησιμοποιείτε yum, στον κατάλογο /etc/yum.repos.d/
26 
+    δημιουργείστε ένα αρχείο με όνομα torproject.repo. Επεξεργαστείτε το αρχείο
27 
+    αυτό με τις ακόλουθες πληροφορίες:
28 
+    <pre>[torproject]
29 
+    name=Tor and Vidalia
30 
+    enabled=1
31 
+    autorefresh=0
32 
+    baseurl=http://deb.torproject.org/torproject.org/rpm/DISTRIBUTION/
33 
+    type=rpm-md
34 
+    gpgcheck=1
35 
+    gpgkey=http://deb.torproject.org/torproject.org/rpm/RPM-GPG-KEY-torproject.org
36 
+    </pre>
37 
+
38 
+    Αν θέλετε να ακολουθήσετε τις σταθερές εκδόσεις του Tor, πρέπει να
39 
+    αντικαταστήσετε τη λέξη DISTRIBUTION με ένα από τα ακόλουθα: centos4,
40 
+    centos5, fc10, fc11, fc12, suse</p>
41 
+
42 
+    <p>Αν θέλετε να ακολουθείτε τις πειραματικές εκδόσεις, αντικαταστήστε τη λέξη
43 
+    DISTRIBUTION με κάποιο από τα ακόλουθα: centos4-experimental,
44 
+    centos5-experimental, fc10-experimental, fc11-experimental,
45 
+    fc12-experimental, suse-experimental</p>
46 
+
47 
+    <p>
48 
+    To Tor είναι εγκατεστημένο και εκτελείται. Πηγαίνετε στο <a href="<page
49 
+    docs/tor-doc-unix>#polipo">δεύτερο βήμα</a> των οδηγιών "Το Tor σε
50 
+    Linux/Unix".
51 
+    </p>
52 
+
53 
+    <p style="font-size: small">
54 
+    Το όνομα DNS <code>deb.torproject.org</code> είναι στην πραγματικότητα ένα
55 
+    σύνολο ανεξάρτητων διακομιστών ρυθμισμένων ως DNS round robin. Αν για
56 
+    κάποιον λόγο δεν έχετε πρόσβαση σε αυτό, δοκιμάστε το όνομα ενός από τα μέρη
57 
+    του. Δοκιμάστε τα <code>deb-master.torproject.org</code>,
58 
+    <code>mirror.netcologne.de</code> ή <code>tor.mirror.youam.de</code>.
59 
+    </p>
60 
+
61 
+    <hr />
62 
+
63 
+    <hr />
64 
+
65 
+    <a id="source"></a>
66 
+    <h2><a class="anchor" href="#source">Κατασκευή από τον πηγαίο κώδικα</a></h2>
67 
+    <br />
68 
+
69 
+    <p>
70 
+    Αν θέλετε να κατασκευάσετε τα αρχεία από τον πηγαίο κώδικα, διαβάστε τις <a
71 
+    href="<gitblob>doc/tor-rpm-creation.txt">οδηγίες δημιουργίας rpm</a>.
72 
+    </p>
73 
+
74 
+    <hr />
75 
+
76 
+    <p>Αν έχετε προτάσεις για βελτίωση του παρόντος εγγράφου, παρακαλούμε να μας
77 
+    τις <a href="<page about/contact>">στείλετε</a>. Ευχαριστούμε!</p>
78 
+
docs/el/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/el/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,219 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Εκτέλεση του προγράμματος-πελάτη <a href="<page index>">Tor</a> σε Mac OS X</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Αυτές οι οδηγίες εγκατάστασης ενός πελάτη Tor είναι για Mac OS X.  Αν
18 
+    επιθυμείτε να αναμεταδίδετε την κυκλοφορία του δικτύου για άλλους ώστε να
19 
+    αναπτυχθεί το δίκτυο (παρακαλούμε να το κάνετε), διαβάστε τον οδηγό <a
20 
+    href="<page docs/tordoc-relay>">Ρυθμίζοντας έναν ενδιάμεσο</a>.</b>
21 
+    </p>
22 
+
23 
+    <hr />
24 
+    <a id="installing"></a>
25 
+    <h2><a class="anchor" href="#installing">Βήμα Πρώτο: Λήψη και Εγκατάσταση του
26 
+    Tor</a></h2>
27 
+    <br />
28 
+
29 
+    <p>
30 
+    The install for Macintosh OS X bundles <a href="<page index>">Tor</a>, <a
31 
+    href="<page projects/vidalia>">Vidalia</a> (a graphical interface for Tor), <a
32 
+    href="<page projects/torbutton>">Torbutton</a>, and <a
33 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (a web
34 
+    proxy)  into one package, with the four applications pre-configured to work
35 
+    together.  Download either the <a
36 
+    href="../<package-osx-bundle-stable>">stable</a> or the <a
37 
+    href="../<package-osx-bundle-alpha>">experimental</a> version of the OS X
38 
+    bundle for Intel, or look for more options on the <a href="<page
39 
+    download/download>">download page</a>.
40 
+    </p>
41 
+
42 
+    <p>Όταν παραλάβετε το αρχείο dmg κάνετε δυο κλικ στην εικόνα του ώστε να
43 
+    συνδεθεί.  Μέσα από τον Finder περιηγηθείτε στο Πακέτο Vidalia το οποίο
44 
+    εγκαθίσταται εύκολα· απλά σύρετε την εικόνα του κρεμυδιού του Vidalia και
45 
+    αποθέστε την στον κατάλογο Applications.  Εναλλακτικά, κάνετε διπλό κλικ στο
46 
+    σενάριο "εγκατάσταση του torbutton" για να ενσωματωθεί το torbutton στo
47 
+    Firefox.  Επίσης, μπορείτε να λάβετε το Torbutton από τα Mozilla Add-ons
48 
+    αναζητώντας για "torbutton".</p>
49 
+
50 
+    <p>Όταν ολοκληρώσετε την εγκατάσταση μπορείτε να εκκινήσετε το Vidalia
51 
+    επιλέγοντας το εικονίδιό του απο τον κατάλογο Applications.  Το μαύρο
52 
+    κρεμύδι με ένα κόκκινο Χ στην περιοχή συστήματος σημαίνει ότι το Tor δεν
53 
+    εκτελείται.  Μπορείτε να εκκινήσετε το Tor επιλέγοντας "Εκκίνηση" από το
54 
+    μενού Tor στο επάνω μέρος της οθόνης σας.
55 
+    </p>
56 
+
57 
+    <p>Ότα το Tor εκτελείται, το εικονίδιο της περιοχής συστήματος του Vidalia θα
58 
+    μοιάζει με το ακόλουθο:
59 
+    </p>
60 
+
61 
+    <p><img alt="vidalia running tor"
62 
+    src="../img/screenshot-osx-vidalia.png"
63 
+    border="1"/></p>
64 
+
65 
+    <p>Το Polipo εγκαθίσαται ως μέρος του πακέτου εγκατάστασης Tor.  Όταν
66 
+    εγκατασταθεί θα εκκινεί κάθε φορά που θα εκκινεί ο υπολογιστής σας.  Δεν
67 
+    χρειάζεται να ρυθμίσετε το Polipo για να χρησιμοποιεί το Tor &mdash· υπάρχει
68 
+    εγκατεστημένη μια προσαρμοσμένη ρύθμιση του Polipo ως μέρος του πακέτου
69 
+    εγκατάστασης.
70 
+    </p>
71 
+
72 
+    <hr />
73 
+    <a id="using"></a>
74 
+    <h2><a class="anchor" href="#using">Βήμα Δεύτερο: Ρυθμίστε τις εφαρμογές σας
75 
+    ώστε να χρησιμοποιούν Tor</a></h2>
76 
+    <br />
77 
+
78 
+    <p>Μετά την εγκατάσταση, πρέπει να ρυθμίσετε τις εφαρμογές σας.  Το πρώτο βήμα
79 
+    είναι η ρύθμιση του περιηγητή σας.</p>
80 
+
81 
+    <p>Για μεγαλύτερη ασφάλεια, πρέπει να χρησιμοποιείται το Tor μαζί με το Firefox
82 
+    και το Torbutton.  Το Torbutton έχει ήδη εγκατασταθεί.  Κάνετε κλικ στο
83 
+    κόκκινο κουμπί "Απενεργοποιημένο Tor" για να το ενεργοποιήσετε και είστε
84 
+    έτοιμοι: </p>
85 
+
86 
+    <p><img alt="Torbutton plugin for Firefox"
87 
+    src="../img/screenshot-torbutton.png"
88 
+    border="1"/></p>
89 
+
90 
+    <p>
91 
+    Αν σκοπεύετε να εκτελείτε τον Firefox σε διαφορετικό υπολογιστή από εκείνον
92 
+    του Tor, διαβάστε το <a
93 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">FAQ
94 
+    για την εκτέλεση του Tor σε διαφορετικό υπολογιστή</a>.
95 
+    </p>
96 
+
97 
+    <p>Για να συνεργαστούν με το Tor οι άλλες εφαρμογές που χρησιμοποιούν
98 
+    πληρεξούσιους διακομιστές HTTP, απλώς δηλώστε τους στο Polipo (δηλαδή, ως
99 
+    localhost θύρα 8118).  Για απευθείας χρήση του SOCKS (για άμεσα μηνύματα,
100 
+    Jabber, IRC, κ.λ.π.) μπορείτε να δηλώσετε την εφαρμογή σας απευθείας στο Tor
101 
+    (localhost θύρα 9050), αλλά διαβάστε <a
102 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">αυτό
103 
+    το FAQ</a> για τους λόγους που αυτό είναι επικίνδυνο.  Για εφαρμογές που δεν
104 
+    υποστηρίζουν ούτε SOCKS ούτε HTTP, διαβάστε το <a
105 
+    href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a> ή το<a
106 
+    href="http://www.dest-unreach.org/socat/">socat</a>.</p>
107 
+
108 
+    <p>Για πληροφορίες πώς να ρυθμίσετε άλλες εφαρμογές, διαβάστε το <a
109 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
110 
+    HOWTO</a>.
111 
+    </p>
112 
+
113 
+    <hr />
114 
+    <a id="verify"></a>
115 
+    <h2><a class="anchor" href="#verify">Βήμα Τρίτο: Βεβαιωθείτε ότι δουλεύει</a></h2>
116 
+    <br />
117 
+
118 
+    <p>
119 
+    Επόμενο βήμα, χρησιμοποσιείστε τον περιηγητή σας με το Tor βεβαιωθείτε ότι η
120 
+    διεύθυνσή σας ΙΡ είναι ανώνυμη.  Κάνετε κλικ στον <a
121 
+    href="https://check.torproject.org/">ανιχνευτή Tor</a> και βεβαιωθείτε ότι
122 
+    πράγματι χρησιμοποιείτε το δίκτυ Tor.  (Αν ο ιστότοπος είναι εκτός
123 
+    λειτουργίας, διαβάστε <a
124 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">αυτό
125 
+    το FAQ</a> για περισσότερες επιλογές για τρόπους ελέγχου του Tor.
126 
+    </p>
127 
+
128 
+    <p>Αν έχετε κάποιο προσωπικό τείχος προστασίας που περιορίζει την δυνατότητα
129 
+    σύνδεσης του υπολογιστή σας, βεβαιωθείτε ότι επιτρέπετε τις συνδέσεις από
130 
+    τις εφαρμογές σας προς τις θύρες 8118 και 9050.  Αν το τείχος προστασίας
131 
+    εμποδίζει τις εξερχόμενες συνδέσεις, ρυθμίστε το ώστε να επιτρέπει συνδέσεις
132 
+    τουλάχιστον στις θύρες TCP 80 και 443 και έπειτα διαβάστε <a
133 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">αυτό
134 
+    το FAQ</a>.
135 
+    </p>
136 
+
137 
+    <p>Αν εξακολουθεί να μην δουλεύει, διαβάστε <a
138 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">αυτό
139 
+    το FAQ</a> για συμβουλές.</p>
140 
+
141 
+    <p>
142 
+    Όταν δουλέψει, διαβάστε <a href="<page download/download>#Warning">τι προσφέρει και
143 
+    τι όχι το Tor</a>.
144 
+    </p>
145 
+
146 
+    <hr />
147 
+    <a id="server"></a> <a id="relay"></a>
148 
+    <h2><a class="anchor" href="#relay">Βήμα Τέταρτο: Ρυθμίστε το ως ενδιάμεσο</a></h2>
149 
+    <br />
150 
+
151 
+    <p>Για να παρέχει (ικανοποιητικό) εύρος ζώνης, το δίκτυο Tor βασίζεται σε
152 
+    εθελοντές.  Όσο περισσότεροι λειτουργούν έναν ενδιάμεσο αναμεταδότη, τόσο
153 
+    ταχύτερο θα είναι το δίκτυο Tor.  Αν διαθέτετε τουλάχιστον 20 kilobytes/sec
154 
+    προς κάθε κατεύθυνση, παρακαλούμε βοηθείστε το Tor ρυθμίζοντάς το ώστε να
155 
+    λειτουργεί και σαν ενδιάμεσος.  Πολλά χαρακτηριστικά κάνουν τους ενδιάμεσους
156 
+    Tor εύκολους και βολικούς, όπως περιορισμός ρυθμού ευρυζωνικότητας,
157 
+    πολιτικές εξόδου ώστε να μην προκαλείτε διαμαρτυρίες κακομεταχείρισης ή
158 
+    κατάχρησης και υποστήριξη για δυναμικές διευθύνσεις ΙΡ.</p>
159 
+
160 
+    <p>Η ύπαρξη αναμεταδοτών σε πολλές διαφορετικές τοποθεσίες στο Διαδίκτυο είναι
161 
+    αυτό που καθιστά ασφαλείς τους χρηστες Tor.  <a
162 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Έχετε
163 
+    τη δυνατότητα να απολαμβάνετε και οι ίδιοι ισχυρή ανωνυμία</a>, αφού τα
164 
+    sites δεν θα γνωρίζουν αν οι συνδέσεις προέρχονται από τον υπολογιστή σας ή
165 
+    αναμεταδίδονται από άλλους.</p>
166 
+
167 
+    <p>Για περισσοτερα, διαβάστε τον οδηγό μας <a href="<page
168 
+    docs/tor-doc-relay>">Ρυθμίζοντας ένα ενδιάμεσο αναμεταδότη</a>.</p>
169 
+
170 
+    <hr />
171 
+    <a id="uninstall"></a>
172 
+    <h2><a class="anchor" href="#uninstall">Πώς να απεγκαταστήσω το Tor και το
173 
+    Privoxy</a></h2>
174 
+    <br />
175 
+
176 
+    <p>Δυο τρόποι υπάρχουν για την απεγκατάσταση του πακέτου από τον υπολογιστή
177 
+    σας: χρησιμοποιώντας το Finder ή την γραμμή εντολής ή το πρόγραμμα
178 
+    απεγκατάστασης που βασίζεται στο Τερματικό.  Ιδού πώς:</p>
179 
+
180 
+    <p>Αλλάξτε τις ρυθμίσεις του πληρεξούσιου διακομιστή σας (proxy server) στις
181 
+    αρχικές τους τιμές.  Μπορείτε να σταματήσετε σ' αυτό το σημείο, αν απλώς
182 
+    θέλετε να διακόψετε την χρήση του Tor.</p>
183 
+
184 
+    <p>Αν επιθυμείτε να απομακρύνετε ολοκληρωτικά το Tor και ο λογαριασμός σας
185 
+    διαθέτει προνόμια διαχειριστή, η διαδικασία έχει ως εξής:</p>
186 
+
187 
+    <ol>
188 
+    <li>Ανοίξτε τον Finder και κάνετε κλικ στο Applications.</li>
189 
+    <li>Σύρετε το /Applications/Vidalia στον Κάδο ανακύκλωσης.</li>
190 
+    <li>Διαγράψτε τον κατάλογο /Library/Torbutton από το σύστημά σας.</li>
191 
+    <li>Πηγαίνετε στον κατάλογο Library του καταλόγου χρήστη και διαγράψτε τον
192 
+    κατάλογο Vidalia</li>
193 
+    </ol>
194 
+
195 
+    <p>Τα Tor, Vidalia και Polipo έχουν τώρα διαγραφεί από το σύστημά σας.</p>
196 
+
197 
+    <p>Αν είστε εξοικειωμένοι με την γραμμή εντολής ή το Τερματικό, μπορείτε να
198 
+    απομακρύνετε το Tor χειρονακτικά ως εξής:</p>
199 
+    <ul>
200 
+    <li>/Applications/Vidalia.app/</li>
201 
+    <li>/Library/Torbutton/</li>
202 
+    <li>~/Library/Vidalia</li>
203 
+    <li>~/.tor</li>
204 
+    </ul>
205 
+
206 
+    <hr />
207 
+
208 
+    <p>Αν έχετε προτάσεις βελτίωσης του παρόντος εγγράφου, παρακαλούμε <a
209 
+    href="<page about/contact>">επικοινωνήστε μαζί μας</a>.  Ευχαριστούμε!</p>
210 
+  </div>
211 
+  <!-- END MAINCOL -->
212 
+  <div id = "sidecol">
213 
+#include "side.wmi"
214 
+#include "info.wmi"
215 
+  </div>
216 
+  <!-- END SIDECOL -->
217 
+</div>
218 
+<!-- END CONTENT -->
219 
+#include <foot.wmi>
docs/el/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,331 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Ρύθμιση ενός ενδιάμεσου αναμεταδότη Tor</h1>
14 
+
15 
+
16 
+    <!-- BEGIN SIDEBAR -->
17 
+    <div class="sidebar-left">
18 
+    <h3>Βήματα</h3>
19 
+    <ol>
20 
+    <li><a href="<page docs/tor-doc-relay>#install">Λήψη &amp; Εγκατάσταση</a></li>
21 
+    <li><a href="<page docs/tor-doc-relay>#setup">Ρυθμίσεις</a></li>
22 
+    <li><a href="<page docs/tor-doc-relay>#check">Έλεγχος &amp; Επιβεβαίωση</a></li>
23 
+    <li><a href="<page docs/tor-doc-relay>#after">Τελικά Βήματα</a></li>
24 
+    </ol>
25 
+    </div>
26 
+
27 
+
28 
+    <!-- END SIDEBAR -->
29 
+    <hr />
30 
+
31 
+    <p>
32 
+    Για να προσφέρει εύρος ζώνης, το δίκτυο Tor βασίζεται σε εθελοντές.  Όσο
33 
+    περισσότεροι άνθρωποι χρησιμοποιούν/λειτουργούν ενδιάμεσους αναμεταδότες,
34 
+    τόσο ταχύτερο θα γίνεται το δίκτυο Tor.  Αν διαθέτετε τουλάχιστον 20
35 
+    kilobytes/sec, παρακαλούμε βοηθείστε το Tor ρυθμίζοντάς το ώστε να
36 
+    λειτουργεί και ως ενδιάμεσος.  Πολλά χαρακτηριστικά καθιστούν τους
37 
+    αναμεταδότες Tor εύκολους και βολικούς, μεταξύ άλλων <a href="<page
38 
+    docs/faq>#RelayFlexible">κλίμακες περιορισμού του εύρους ζώνης, πολιτικές εξόδου
39 
+    ώστε να περιορίεζετε την έκθεσή σας σε διαμαρτυρίες κατάχρησης και
40 
+    υποστήριξη για δυναμικές διευθύνσεις ΙΡ</a>.
41 
+    </p>
42 
+
43 
+    <p>Μπορείτε να λειτουργείτε έναν ενδιάμεσο Tor <a
44 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">σε
45 
+    κάθε</a> λειτουργικό σύστημα.  Οι ενδιάμεσοι Tor δουλεύουν καλύτερα σε
46 
+    Linux, OS X Tiger ή νεότερο, FreeBSD 5.x+, NetBSD 5.x+ και Windows Server
47 
+    2003 ή νεότερο.
48 
+    </p>
49 
+
50 
+    <hr /> <a id="zero"></a> <a id="install"></a>
51 
+    <h2><a class="anchor" href="#install">Βήμα Πρώτο: Κατεβάστε και Εγκαταστήστε το
52 
+    Tor</a></h2>
53 
+    <br />
54 
+
55 
+    <p>Πριν ξεκινήσετε βεβαιωθείτε ότι το Tor λειτουργεί.
56 
+    </p>
57 
+
58 
+    <p>Επισκεφθείτε την <a href="<page download/easy-download>">σελια λήψεων</a> και
59 
+    εγκαταστείστε το το "Πακέτο Εγκατάστασης" για το δικό σας Λειτουργικό
60 
+    Σύστημα.
61 
+    </p>
62 
+
63 
+    <p>Αν σας βολεύει, μπορείτε να το χρησιμοποιήσετε για λίγο ως πελάτη-client για
64 
+    να βεβαιωθείτε ότι πράγματι δουεύει.</p>
65 
+
66 
+    <hr /> <a id="setup"></a>
67 
+    <h2><a class="anchor" href="#setup">Βήμα Τρίτο: Ρυθμίστε το ως ενδιάμεσο</a></h2>
68 
+    <br />
69 
+    <ol>
70 
+    <li>Βεβαιωθείτε ότι το ρολόι σας και η ζώνη ώρας έχουν ρυθμιστεί σωστά.  Αν
71 
+    είναι εφικτό, συγχρονίστε το ρολόι σας με κάποιον δημόσιο <a
72 
+    href="http://en.wikipedia.org/wiki/Network_Time_Protocol">διακομιστή
73 
+    ώρας</a>.
74 
+    </li>
75 
+
76 
+    <li><strong>Ρύθμιση του Tor μέσω του Γραφικού Περιβάλλοντος Vidalia</strong>:
77 
+    <ol>
78 
+
79 
+    <li>
80 
+    	<dt>Κάνετε δεξιό κλικ στο εικονίδιο του Vidalia που βρισκεται στην μπάρα
81 
+    εργασιών.  Επιλέξτε <tt>Πίνακας Ελέγχου</tt>.</dt>
82 
+    	<dd><img alt="vidalia right click menu"
83 
+    src="../img/screenshot-win32-vidalia.png"></dd>
84 
+    </li>
85 
+
86 
+    <li>Click <tt>Ρύθμιση αναμετάδοσης</tt>.</li>
87 
+
88 
+    <li>
89 
+    	<dt>Επιλεξτε <tt>Ανεμετάδοση κίνησης για το δίκτυο Tor</tt> αν θέλετε να είστε
90 
+    δημόσιος αναμεταδότης (συνίσταται), ή επιλέξτε 		<tt>Βοηθείστε λογοκριμένους
91 
+    χρήστες να συνδεθούν στο δίκτυο Tor</tt> αν θέλετε να γίνετε <a href="<page
92 
+    docs/faq>#RelayOrBridge">γέφυρα</a> για χρήστες χωρών που λογοκρίνεται το
93 
+    Διαδίκτυο.</dt>
94 
+    <dd><img alt="vidalia basic settings"
95 
+    src="../img/screenshot-win32-configure-relay-1.png"></dd>
96 
+    </li>
97 
+
98 
+    <li>Πληκτρολογήστε ένα όνομα για τον αναμεταδότη σας και γράψτε πληροφορίες
99 
+    επικοινωνίας σε περίπτωση που χρειαστεί να επικοινωνήσουμε μαζί σας για
100 
+    τυχόν προβλήματα.</li>
101 
+
102 
+    <li>Αφήστε επιλεγμένο το <tt>Προσπάθεια αυτόματης ρύθμισης της προώθησης
103 
+    θύρας</tt>.  Πατήστε το κουμπί <tt>Δοκιμή</tt> για να διαπιστώσετε ότι
104 
+    δουλεύει.  Αν δεν δουλεύει, δείτε τον αριθμό 3 πιο κάτω.</li>
105 
+
106 
+    <li><dt>Επιλέξτε τον φάκελο <tt>Περιορισμός εύρους ζώνης</tt>.  Διαλέξτε πόσο εύρος
107 
+    δικτύου θέλετε να παράσχετε σε χρήστες Tor σαν εσάς.</dt>
108 
+    <dd><img alt="vidalia bandwidth limits"
109 
+    src="../img/screenshot-win32-configure-relay-2.png"></dd>
110 
+    </li>
111 
+
112 
+    <li><dt>Επιλέξτε τον φάκελο <tt>Πολιτικές εξόδου</tt>.  Αν θέλετε να συνδέονται και
113 
+    άλλοι στον αναμεταδότη σας για να χρησιμοποιούν τις υπηρεσίες αυτές, μην
114 
+    αλλάξετε κάτι.  Απο-επιλέξτε τις υπηρεσίες που δεν θέλετε να χρησιμοποιούν
115 
+    οι άλλοι χρηστες <a href="<page docs/faq>#ExitPolicies">να χρησιμοποιούν μέσω του
116 
+    αναμεταδότη σας</a>.  Αν επιθυμείτε ο υπολογιστής σας να μην είναι
117 
+    ενδιάμεσος εξόδου, απο-επιλέξτε όλες τις υπηρεσείς.</dt>
118 
+    <dd><img alt="vidalia exit policies"
119 
+    src="../img/screenshot-win32-configure-relay-3.png"></dd>
120 
+    </li>
121 
+
122 
+    <li>Πατήστε το κουμπί <tt>ΟΚ</tt>.  Ανατρέξτε στο Τρίτο Βήμα που ακολουθεί για
123 
+    να βεβαιωθείτε ότι ο ενδιάμεσός σας λειτουργεί σωστά.</li>
124 
+    </ol>
125 
+
126 
+    <br /> <strong>Χειροκίνητη ρύθμιση</strong>:
127 
+    <ul>
128 
+    <li>Επεξεργαστείτε το τελευταίο τμήμα του αρχείου <a
129 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">torrc</a>.
130 
+    Αν θέλετε να είστε δημόσιος ενδιάμεσος αναμεταδότης (συνίσταται),
131 
+    βεβαιωθείτε ότι έχετε καθορίσει την τιμή ORPort και διαβάστε το <a
132 
+    href="<page docs/faq>#ExitPolicies">ExitPolicy</a>· αλλιώς, αν επιθυμείτε ο
133 
+    υπολογιστής σας να είναι <a href="<page docs/faq>#RelayOrBridge">γέφυρα</a> για
134 
+    χρήστες σε χώρες όπου το Διαδίκτυο λογοκρίνεται, χρησιμοποιείστε <a
135 
+    href="<page docs/bridges>#RunningABridge">αυτές τις γραμές</a>.
136 
+    </li>
137 
+
138 
+    </ul></li>
139 
+
140 
+    <li>Αν χρησιμοποιείτε τείχος προστασίας δημιουργείστε ένα άνοιγμα ώστε οι
141 
+    εισερχόμενες συνδέσεις να μπορούν να επικοινωνούν με τις θύρες που ρυθμίσατε
142 
+    (ORPort, συν την θύρα DirPort, αν την έχετε ενεργοποιήσει).  Αν διαθέτετε
143 
+    συσκευή τείχου προστασίας (Linksys, cablemodem, κ.λ.π.) συμβουλευτείτε τον
144 
+    ιστότοπο <a href="http://portforward.com/">portforward.com</a>.
145 
+    Βεβαιωθείτε, επίσης, ότι επιτρέπετε όλες τις <em>εξερχόμενες</em> συνδέσεις,
146 
+    ώστε ο αναμεταδότης σας να επικοινωνεί με άλλους ενδιάμεσους αναμεταδότες
147 
+    Tor.
148 
+    </li>
149 
+
150 
+    <li>Επανεκκινήστε τον ενδιάμεσο αναμεταδότη σας.  Αν <a
151 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">καταγράψει
152 
+    προειδοποιητικά μηνύματα</a>, μελετήστε τα.
153 
+    </li>
154 
+
155 
+    <li>Γίνετε συνδρομητής/τρια στιν λίστα ταχυδρομείου <a
156 
+    href="http://archives.seul.org/or/announce/">or-announce</a>.  Έχει μικρή
157 
+    κίνηση και θα σας ενημερώνει για νέες σταθερές εκδόσεις.  Ίσως θελήσετε να
158 
+    γίνετε συνδρομητής και στις <a href="<page
159 
+    docs/documentation>#MailingLists">λίστε με μεγαλύτερη κίνηση</a>.
160 
+    </li>
161 
+
162 
+    </ol>
163 
+
164 
+    <hr /> <a id="check"></a>
165 
+    <h2><a class="anchor" href="#check">Βήμα Τρίτο: Βεβαιωθείτε ότι δουλεύει</a></h2>
166 
+    <br />
167 
+
168 
+    <p>Μόλις ο ενδιάμεσος αναμεταδότης σας συνδεθεί στο δίκτυο, θα προσπαθήσει να
169 
+    διαπιστώσει αν οι θύρες που ρυθμίσατε  είναι ανοικτές για το δίκτυο.  Το
170 
+    στάδιο αυτό είναι, συνήθως, σύντομο αλλά ίσως χρειαστούν έως και 20 λεπτά.
171 
+    Αναζητείστε <a
172 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">κάποιο
173 
+    στοιχείο καταγραφής</a> που να μοιάζει με <tt>Ο αυτο-έλεγχος έδειξε ότι οι
174 
+    θύρες ORPort είναι ανοικτές για το δίκτυο. Έξοχα.</tt> Αν δεν δείτε αυτό το
175 
+    μήνυμα σημαίνει ότι ότι ο αναμεταδότης σας δεν είναι προσβάσιμος από το
176 
+    δίκτυο και θα πρέπει να ελέγξετε εκ νέου το τείχος προστασίας σας, να
177 
+    βεβαιωθείτε ότι δοκιμάζει την διεύθυνση ΙΡ και τις θύρες που πρέπει, κ.λ.π.
178 
+    </p>
179 
+
180 
+    <p>Όταν σας δείξει ότι ο αναμεταδότης σας είναι ανοικτός για το υπόλοιπο
181 
+    δίκτυο, θα αποστείλει προς τους καταλόγους μια "περιγραφή διακομηστή" ώστε
182 
+    να γνωρίζουν τα προγράμματα ποιά διεύθυνση, θύρες, κλείδες,
183 
+    κ.λ.π. χρησιμοποιεί ο αναμεταδότης σας.  Μπορείτε να δείτε <a
184 
+    href="http://194.109.206.212/tor/status-vote/current/consensus">μια
185 
+    κατάσταση του δικτύου χειροκίνητα</a> και να αναζητήσετε σε αυτή το όνομα
186 
+    που επιλέξατε για τον αναμεταδότη σας και να βεβαιωθείτε ότι βρίσκεται
187 
+    εκεί.  Ίσως χρειαστεί να περιμένετε έως και μια ώρα ώστε να δοθεί χρόνος για
188 
+    φρέσκια κατάσταση του δικτύου.</p>
189 
+
190 
+    <hr /> <a id="after"></a>
191 
+    <h2><a class="anchor" href="#after">Βήμα Τέταρτο: Όταν συνδεθείτε</a></h2>
192 
+    <br />
193 
+
194 
+    <p>
195 
+    Συνιστούμε και τα ακόλουθα βήματα:
196 
+    </p>
197 
+
198 
+    <p>
199 
+    6.  Διαβάστε <a
200 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">περί
201 
+    ασφάλειας</a> για να μάθετε πώς θα αυξήσετε την ασφάλεια του ενδιαμέσου σας.
202 
+    </p>
203 
+
204 
+    <p>
205 
+    7.  Αν θέλετε μπορείτε να λειτουργείτε περισσότερους του ενός ενδιάμεσους
206 
+    αναμεταδότες, αλλά παρακαλείστε να ορίσετε <a
207 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">την
208 
+    επιλογή MyFamily</a> σε όλα τα αρχεία ρυθμίσεων των αναμεταδοτών σας.
209 
+    </p>
210 
+
211 
+    <p>
212 
+    8.  Αποφασίστε κάποιο όριο εύρους ζώνης.  Τα καλωδιακά μόντεμς, το DSL και
213 
+    οι άλλοι χρήστες με ασύμμετρο εύρος ζώνης (π.χ. μεγαλύτερη ταχύτητα λήψεων
214 
+    από ό,τι αποστολής) πρέπει να περιορίσουν το όριο αυτό στο μικρότερο εύρος
215 
+    ζώνης που διαθέτου για να αποφύγουν την συμφόρηση.  Για λεπτομέρειες
216 
+    διαβάστε το <a
217 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">FAQ
218 
+    περιορισμού του εύρους ζώνης</a>
219 
+    </p>
220 
+
221 
+    <p>
222 
+    9.  Διατηρείτε αντίγραφα ασφαλείας του ιδιωτικού κλειδιού για το Tor
223 
+    (βρίσκεται αποθηκευμένο στον κατάλογο "keys/secret_id_key" του καταλόγου
224 
+    DataDirectory).  Το κλειδί αυτό αποτελεί την "ταυτότητα" του αναμεταδότη σας
225 
+    και πρέπει να αποθηκεύεται με ασφάλεια ώστε να μην μπορεί κάποιος να
226 
+    εντοπίσει την κίνηση που διεξάγεται μέσω αυτού.  Η ασφαλής αποθήκευση του
227 
+    αρχείου αυτού είναι ζωτικής σημασίας για την <a
228 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeRelay">μετακίνηση
229 
+    ή αποκατάσταση του αναμεταδότη σας Tor</a> σε περιπτώσεις που κάτι πάει
230 
+    στραβά.
231 
+    </p>
232 
+
233 
+    <p>
234 
+
235 
+    10.  Αν έχετε τον έλεγχο των διακομηστών (name servers) της δικτυακής
236 
+    περιοχής σας (domain) φροντίστε να ρυθμίσετε τον αντίστροφο διακομιστή DNS
237 
+    σε 'anonymous-relay', 'proxy' ή 'tor-proxy' ώστε, σε περίπτωση που άλλοι
238 
+    χρήστες βλέπουν την διεύθυνση στις δικές τους καταγραφές web, θα αντιληφθούν
239 
+    ταχύτερα το πρόβλημα.  Η προσθήκη της <a
240 
+    href="<gitblob>contrib/tor-exit-notice.html">σημείωσης εξόδου Tor</a> σε
241 
+    έναν vhost για το συγκεκριμένο όνομα υπολογιστή μπορεί να συμβάλει στην
242 
+    παρεμπόδιση των διαμαρτυριών για κακή χρήση προς εσάς τους ιδίους και τον
243 
+    ISP σας εάν λειτουργείτε έναν κόμβο εξόδου (exit node).
244 
+
245 
+    </p>
246 
+
247 
+    <p>
248 
+    11.  Αν ο υπολογιστής σας δεν εκτελεί κάποιον webserver φροντίστε να
249 
+    αλλάξετε τις θύρες ORPort σε 443 και DirPort σε 80.  Πολλοί χρήστες Tor
250 
+    συσωρρεύονται πίσω από τείχη προστασίας που τους επιτρέπουν μόνον να
251 
+    περιηγηθούν στον ιστό και η παραπάνω αλλαγή θα τους επιτρέψει να συνδεθούν
252 
+    με τον αναμεταδοτη σας.  Οι αναμεταδότες που εκτελούνται σε Windows 32bit
253 
+    μπορούν αλλάξουν τις θύρες τους ORPort και DirPort απευθείας μέσω του
254 
+    αρχείου torcc και να επανεκκινήσουν το Tor.  Οι αναμεταδότες OS X και Unix
255 
+    δεν δεσμεύουν απευθείας τις θύρες αυτές (αφού δεν εκτελούνται με δικαιώματα
256 
+    υπερδιαχειριστή) και γι' αυτό χρειάζεται να γίνουν κάποιες ρυθμίσεις <a
257 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">
258 
+    προώθησης θύρας</a> για να επικοινωνούν οι άλλοι στο δίκτυο με τους
259 
+    αναμεταδότες αυτών των Λειτουργικών Συστημάτων.  Αν ήδη χρησιμοποιείτε τις
260 
+    θυρες 443 και 80 αλλά εξακολουθείτε να θέλετε να βοηθήσετε, άλλες χρήσιμες
261 
+    θύρες είναι οι 22, 110 και 143.
262 
+    </p>
263 
+
264 
+    <p>
265 
+    12.  Αν ο αναμεταδότης σας Tor παρέχει άλλες υπηρεσίες με την ίδια διεύθυνση
266 
+    ΙΡ &mdash; όπως ένας δημόσιος διακομιστής ιστού &mdash; βεβαιωθείτε ότι
267 
+    επιτρέπονται οι συνδέσεις στον διακομιστή από τοπικούς υπολογιστές.  Πρέπει
268 
+    να επιτρέπετε αυτές τις συνδέσεις επειδή οι πελάτες Tor θα βλέπουν ότι ο
269 
+    αναμεταδότης σας είναι <a
270 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">ο
271 
+    ασφαλέστερος τρόπος σύνδεσης σε αυτόν τον διακομιστή</a> και θα δημιουργούν
272 
+    πάντοτε ένα κύκλωμα που θα καταλήγει στον αναμεταδότη σας.  Αν δεν
273 
+    επιθυμείτε να επιτρέπονται οι συνδέσεις αυτές πρέπει να τους απορρίπτετε
274 
+    ρητώς μέσα από τις ρυθμίσεις σας των πολιτικών εξόδου.
275 
+    </p>
276 
+
277 
+    <p>
278 
+    13.  (Μόνο για Unix). Δημιουργήστε ξεχωριστό χρήστη για την εκτέλεση του
279 
+    αναμεταδότη.  Αν εγκαταστήσατε το πακέτο για OS X ή το πακέτο deb ή το
280 
+    πακέτο rpm, έχει ήδη γίνει αυτό.  Αλλιώς μπορείτε να δημιουργήσετε νέο
281 
+    χρήστη χειροκίνητα. (Ο αναμεταδότης Tor δεν χρειάζεται να εκτελείται ως
282 
+    root, γι' αυτό είναι καλό να μην εκτελείται ως χρήστης root.  Η εκτέλεσή του
283 
+    ως χρήστης 'tor' αποφεύγει προβλήματα με το identd και με άλλες υπηρεσίες
284 
+    που ανιχνεύουν το όνομα χρήστη.  Αν είστε ριψοκίνδυνος τύπος, <a
285 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">εγκαταστήστε
286 
+    το Tor σε περιβάλλον chroot</a>.)
287 
+    </p>
288 
+
289 
+    <p>
290 
+    14. (Μόνο Unix). Πιθανόν το λειτουργικό σας σύστημα περιορίζει τον αριθμό
291 
+    των ανοικτών περιγραφικών αρχείων (file descriptors) ανά διεργασία στα 1024
292 
+    (ή και ακόμη λιγότερα). Αν θέλετε να εκτελείτε έναν γρήγορο κόμβο εξόδου,
293 
+    αυτός ο αριθμός πιθανόν να μην είναι αρκετός.  Στο Linux πρέπει να
294 
+    προσθέσετε μια γραμμή όπως "toruser hard nofile 8192" στο αρχείο
295 
+    /etc/security/limits.conf (όπου toruser είναι ο χρήστης που εκτελεί την
296 
+    διεργασία Tor) και έπειτα να εκκινήσετε τον υπολογιστή σας αν εγκαταστάθηκε
297 
+    ως πακέτο (ή να επανασυνδεθείτε αν την εκτελείτε ο ίδιος).
298 
+    </p>
299 
+
300 
+    <p>
301 
+    15. Αν εγκαταστήσατε το Tor μέσω κάποιου πακέτου ή εγκαταστάτη, πιθανόν το
302 
+    Tor να εκκινεί αυτόματα όταν εκκινεί ο υπολογιστής σας. Αλλά αν το
303 
+    εγκαταστήσατε από τον πηγαίο κώδικα μπορείτε να βρείτε χρήσιμα τα
304 
+    initscripts των αρχείων contrib/tor.sh ή contrib/torctl.
305 
+    </p>
306 
+
307 
+    <p>
308 
+    Όταν αλλάζετε τις ρυθμίσεις του Tor, βεβαιωθείτε ότι ο αναμεταδότης σας
309 
+    λειτουργεί σωστά μετά τις αλλαγές. Βεβαιωθείτε ότι ρυθμίσατε την γραμμή
310 
+    "ConcactInfo" του αρχείου torrc ώστε να επικοινωνήσουμε μαζί σας αν
311 
+    χρειάζεστε κάποια αναβάθμιση ή αν κάτι είναι λάθος. Αν αντιμετωπίσετε
312 
+    προβλήματα ή έχετε ερωτήσεις, δείτε τις ενότητες <a href="<page
313 
+    docs/documentation>#Support">Υποστήριξη</a> ή <a href="<page
314 
+    about/contact>">επικοινωνία</a> στην λίστα των tor-ops. Ευχαριστούμε που βοηθάτε
315 
+    στην ανάπτυξη του δικτύου Tor.
316 
+    </p>
317 
+
318 
+    <hr />
319 
+
320 
+    <p>Αν έχετε προτάσεις βελτίωσης αυτού του εγγράφου, παρακαλώ να μας <a
321 
+    href="<page about/contact>">πείτε ποιές είναι</a>.  Ευχαριστούμε!</p>
322 
+  </div>
323 
+  <!-- END MAINCOL -->
324 
+  <div id = "sidecol">
325 
+#include "side.wmi"
326 
+#include "info.wmi"
327 
+  </div>
328 
+  <!-- END SIDECOL -->
329 
+</div>
330 
+<!-- END CONTENT -->
331 
+#include <foot.wmi>
docs/el/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,195 @@
1 
+    <h1>Εκτέλεση του πελάτη <a href="<page index>">Tor</a> σε Linux/BSD/Unix</h1>
2 
+    <br />
3 
+
4 
+    <p>
5 
+    <b>Σημειώστε ότι αυτές είναι οδηγίες εγκατάστασης για την εκτέλεση του
6 
+    προγράμματος/πελάτη Tor. Αν θέλετε να αναμεταδίδετε κυκλοφορία για άλλους
7 
+    ώστε να συμβάλλετε στην ανάπτυξη του δικτύου (παρακαλούμε να το κάνετε),
8 
+    διαβάστε τον οδηγό <a href="<page docs/tor-doc-relay>">Ρύθμιση ενός
9 
+    αναμεταδότη</a>.</b>
10 
+    </p>
11 
+
12 
+    <hr /> <a id="installing"></a>
13 
+    <h2><a class="anchor" href="#installing">Πρώτο βήμα: Λήψη και εγκατάσταση του
14 
+    Tor</a></h2>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    Η τελευταία έκδοση του Tor μπορεί να βρεθεί στη σελίδα <a href="<page
19 
+    download/download>">λήψεων</a>. Διαθέτουμε πακέτα για Debian, Red Hat, Gentoo,
20 
+    *BSD και άλλα. Αν χρησιμοποιειτε Ubuntu μην χρησιμοποιείτε τα αρχικά πακέτα:
21 
+    αντ' αυτών χρησιμοποιείστε <a href="<page docs/debian>#ubuntu">το αποθετήριο
22 
+    των deb</a>.
23 
+    </p>
24 
+
25 
+    <p>Αν κατασκευάζετε τα αρχεία από τον πηγαίο κώδικα, πρώτα εγκαταστήστε το <a
26 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a> και βεβαιωθείτε
27 
+    ότι έχετε τα openssl και zlib (συμπεριλαμβανομένων και των πακέτων -devel,
28 
+    αν υπάρχουν). Μετά εκτελέστε: <br /> <tt>tar xzf
29 
+    tor-<version-stable>.tar.gz; cd tor-<version-stable></tt><br />
30 
+    <tt>./configure &amp;&amp; make</tt><br />.  Τώρα μπορείτε να τρέξετε το Tor
31 
+    από <tt>src/or/tor</tt> ή μπορείτε να εκτελέσετε <tt>make install</tt> (ως
32 
+    root, αν είναι αναγκαίο) για να εγκατασταθεί στον κατάλογο /usr/local και
33 
+    μετά μπορείτε να το ξεκινήσετε εκτελώντας <tt>tor</tt>.
34 
+    </p>
35 
+
36 
+    <p>Το Tor είναι προρυθμισμένο ως πελάτης. Χρησιμοποιεί ένα ενσωματωμένο αρχείο
37 
+    αρχικών ρυθμίσεων και οι περισσότεροι χρήστες δεν θα χρειαστεί να κάνουν
38 
+    αλλαγές. Το Tor είναι τώρα εγκατεστημένο.
39 
+    </p>
40 
+
41 
+    <hr /> <a id="privoxy"></a> <a id="polipo"></a>
42 
+    <h2><a class="anchor" href="#polipo">Δεύτερο βήμα: Εγκατάσταση του Polipo για
43 
+    περιήγηση στον Ιστό</a></h2>
44 
+    <br />
45 
+
46 
+    <p>Μετά την εγκατάσταση του Tor πρέπει να ρυθμίσετε τις εφαρμογές σας ώστε να
47 
+    το χρησιμοποιούν.
48 
+    </p>
49 
+
50 
+    <p>
51 
+    Το πρώτο βήμα είναι η ρύθμιση της περιήγησης στον ιστό. Ξεκινήστε
52 
+    εγκαθιστώντας το <a
53 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> από το
54 
+    αποθετήριο της προτίμησής σας. Το Polipo είναι ένας πληρεξουσιος διακομιστής
55 
+    ιστού (proxy server) που υποστηρίζει http pipelining και γι' αυτό είναι
56 
+    κατάλληλο για τις καθυστερήσεις του Tor.  Βεβαιωθείτε ότι θα παραλάβετε το
57 
+    Polipo με έκδοση τουλάχιστον 1.0.4, αφού οι παλαιότερες εκδόσεις δεν
58 
+    υποστηρίζουν το πρωτόκολο SOCKS που είναι απαραίτητο για το δίκτυο Tor. Σε
59 
+    αυτό το σημείο πρέπει να απεγκαταστήσετε το privoxy (π.χ., apt-get remove
60 
+    privoxy ή yum remove privoxy) για να μην υπάρχουν διενέξεις μεταξύ τους.
61 
+    </p>
62 
+
63 
+    <p>Όταν εγκαταστήσετε το Polipo (είτε από πακέτο ή από τον πηγαίο κώδικα)
64 
+    <b>πρέπει να ρυθμίσετε το Polipo ώστε να χρησιμοποιεί το Tor</b>. Κατεβάστε
65 
+    τις <a
66 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/polipo.conf">τις
67 
+    ρυθμίσεις του Polipo για το Tor</a> και αντιγράψτε το στην τρέχουσα θέση του
68 
+    αρχείου ρυθμίσεων (π.χ., /etc/polipo/config ή ~/.polipo). Πρέπει να
69 
+    επανεκκινήσετε το Polipo για να εφαρμοστούν οι αλλαγές.  Για παράδειγμα: <br
70 
+    /> <tt>/etc/init.d/polipo restart</tt>.
71 
+    </p>
72 
+
73 
+    <p>Αντί για το Polipo μπορείτε να χρησιμοποιήσετε το Privoxy με <a
74 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">αυτό
75 
+    το παράδειγμα ρύθμισης</a>. Αλλά αφού και τα δύο αρχεία ρυθμίσεων
76 
+    χρησιμοποιούν την θύρα 8118, δεν πρέπει να εκτελείτε το Polipo και το
77 
+    Privoxy ταυτόχρονα.</p>
78 
+
79 
+    <hr /> <a id="using"></a>
80 
+    <h2><a class="anchor" href="#using">Τρίτο Βημα: Ρυθμίστε τις εφαρμογές σας ώστε
81 
+    να χρησιμοποιούν το Tor</a></h2>
82 
+    <br />
83 
+
84 
+    <p>Μετά την εγκατάσταση των Tor και Polipo πρέπει να ρυθμίσετε τις εφαρμογές
85 
+    σας για να τα χρησιμοποιούν. Το πρώτο βήμα είναι η ρύθμιση της περιήγησης
86 
+    στον ιστό.</p>
87 
+
88 
+    <p>You should use Tor with Firefox and Torbutton, for best safety.  Simply
89 
+    install the <a href="https://addons.mozilla.org/firefox/2275/">πρόσθετο
90 
+    Torbutton</a>, επανεκκινήστε το Firefox και είστε έτοιμοι.
91 
+    </p>
92 
+
93 
+    <img alt="Torbutton plugin for Firefox"
94 
+    src="../img/screenshot-torbutton.png" border="1"> <br />
95 
+
96 
+    <p>
97 
+    Αν θέλετε να εκτελείτε τον Firefox σε διαφορετικό υπολογιστή, δείτε <a
98 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">
99 
+    τις οδηγίες του FAQ για την εκτέλεση του Firefox σε διαφορετικό
100 
+    υπολογιστή</a>.
101 
+    </p>
102 
+
103 
+    <p>Για να χρησιμοποιούν το Tor οι άλλες εφαρμογές που υποστηρίζουν
104 
+    πληρεξούσιους διακομιστές (proxy) HTTP, ενεργοποιείστε σε αυτές το Polipo
105 
+    (δηλαδή, την τοπική θύρα 8118). Για απευθείας χρήση του SOCKS (για άμεσα
106 
+    μηνύματα, Jabber, IRC, κλπ) μπορείτε να κατευθύνετε την εφαρμογή σας
107 
+    κατευθείαν στο Tor (τοπική θύρα 5050), αλλά διαβάστε <a
108 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">αυτή
109 
+    την καταχώρηση FAQ</a> για το πώς κάτι τέτοιο μπορεί να αποδειχθεί
110 
+    επικίνδυνο. Για εφαρμογές που δεν υποστήριζουν SOCKS ούτε HTTP, διαβάστε το
111 
+    <a href="http://tsocks.sourceforge.net/">tsocks</a> ή το <a
112 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
113 
+    </p>
114 
+
115 
+    <p>Για πληροφορίες του τρόπου χρήσης του Tor από άλλες εφαρμογές, διαβάστε το
116 
+    <a
117 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
118 
+    HOWTO</a>.
119 
+    </p>
120 
+
121 
+    <hr /> <a id="verify"></a>
122 
+    <h2><a class="anchor" href="#verify">Βήμα Τέταρτο: Βεβαιωθείτε ότι δουλεύει</a></h2>
123 
+    <br />
124 
+
125 
+    <p>
126 
+    <!--PO4ASHARPBEGIN<a href="http://ipchicken.com/">
127 
+    this site</a>PO4ASHARPEND-->
128 
+    #to see what IP address it thinks you're using.
129 
+    Χρησιμοποιείστε τον περιηγητή ιστού με το Tor βεβαιωθείτε ότι η διεύθυνσή
130 
+    σας IP είναι ανώνυμη. Κάνετε κλικ στον <a
131 
+    href="https://check.torproject.org/">Ανιχνευτή Tor</a> και θα διαπιστώσετε
132 
+    αν χρησιμοποιείτε Tor. (Αν η ιστοσελίδα αυτή δεν είναι διαθέσιμη, διαβάστε
133 
+    αυτό το <a
134 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">FAQ</a>
135 
+    για περισσότερες προτάσεις πώς να ελέγξετε το Tor σας.
136 
+    </p>
137 
+
138 
+    <p>Αν έχετε κάποιο προσωπικό τείχος προστασίας που περιορίζει την δυνατότητα
139 
+    σύνδεσης του υπολογιστή στον ίδιο (κάτι σαν το SELinux του Fedora Core 4,
140 
+    μεταξύ άλλων), βεβαιωθείτε ότι επιτρέπετε συνδέσεις από τις τοπικές σας
141 
+    εφαρμογές προς το Polipo (τοπική θύρα 8118) και το Tor (τοπική θύρα
142 
+    9050). Αν το τείχος προστασίας φράσσει τις εξερχόμενες συνδέσεις,
143 
+    δημιουργήστε ένα "άνοιγμα" ώστε να μπορεί να συνδέεται τουλάχιστον με τις
144 
+    θύρες TCP 80 και 443 και διαβάστε <a
145 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">αυτό
146 
+    το FAQ</a>. Αν οι ρυθμίσεις του SELinux δεν επιτρέπουν στο tor ή στο privoxy
147 
+    να εκτελούνται ορθά, δημιουργήστε ένα αρχείο με όνομα booleans.local στον
148 
+    κατάλογο /etc/selinux/targeted. Επεξεργαστείτε το αρχείο αυτό με τον
149 
+    συντάκτη κειμένου της αρεσκείας σας και προσθέστε την γραμμή
150 
+    "allow_ypbind=1". Επανεκκινήστε τον υπολογιστή σας ώστε να εφαρμοσθούν οι
151 
+    αλλαγές.
152 
+    </p>
153 
+
154 
+    <p>Αν εξακολουθεί να μην δουλεύει, ρίξτε μια ματιά <a
155 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">σε
156 
+    αυτό το FAQ</a> για συμβουλές.</p>
157 
+
158 
+    <hr /> <a id="server"></a> <a id="relay"></a>
159 
+    <h2><a class="anchor" href="#relay">Βήμα Πέμπτο: Ρύθμιση ως ενδιάμεσου
160 
+    αναμεταδότη</a></h2>
161 
+    <br />
162 
+
163 
+    <p>Το δίκτυο Tor βασίζεται σε εθελοντές που του παρέχουν εύρος ζώνης. Όσο
164 
+    περισσότεροι άνθρωποι εκτελούν ενδιάμεσους αναμεταδότες, τόσο γρηγορότερο θα
165 
+    είναι το δίκτυο Tor. Αν διαθέτετε τουλάχιστον 20 kilobytes/second προς κάθε
166 
+    κατεύθυνση, βοηθήστε το Tor ρυθμίζοντάς το ώστε να είναι και
167 
+    αναμεταδότης. Διαθέτουμε πολλά χαρακτηριστικά που καθιστούν τους
168 
+    αναμεταδότες Tor εύκολους και βολικούς, όπως τον περιορισμό του εύρους
169 
+    ζώνης, πολιτικές εξόδου ώστε να περιορίζετε την έκθεση σε διαμαρτυρίες κακής
170 
+    χρήσης και υποστήριξη δυναμικής διεύθυνσης ΙΡ, μεταξύ άλλων.</p>
171 
+
172 
+    <p>Η ύπαρξη αναμεταδοτών σε πολλά σημεία του Διαδικτύου καθιστά το Tor ασφαλές
173 
+    για τους χρήστες. <a
174 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Εσείς
175 
+    οι ίδιοι θα απολαμβάνετε ισυχρότερη ανωνυμία</a>, αφού οι απομακρυσμένοι
176 
+    διαδικτυακοί τόποι δεν μπορούν να γνωρίζουν αν οι συνδέσεις προέρχονται από
177 
+    τον υπολογιστή σας ή αναμεταδίδονται από άλλους.</p>
178 
+
179 
+    <p>Διαβάστε περισσότερα στον οδηγό μας <a href="<page
180 
+    docs/tor-doc-relay>">Ρύθμιση ενός αναμεταδότη</a>.</p>
181 
+
182 
+    <hr />
183 
+
184 
+    <p>Αν έχετε προτάσεις για την βελτίωση αυτού του εγγράφου, παρακαλούμε να <a
185 
+    href="<page about/contact>">μας τις στείλετε</a>. Ευχαριστούμε!</p>
186 
+  </div>
187 
+  <!-- END MAINCOL -->
188 
+  <div id = "sidecol">
189 
+#include "side.wmi"
190 
+#include "info.wmi"
191 
+  </div>
192 
+  <!-- END SIDECOL -->
193 
+</div>
194 
+<!-- END CONTENT -->
195 
+#include <foot.wmi>
docs/el/tor-doc-web.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,62 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Configuring your browser to use Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-web>">Configure Your Browser</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Ρύθμιση του περιηγητή ιστού για χρήστη του <a href="<page index>">Tor</a></h1>
14 
+    <br />
15 
+
16 
+    <p>Αν χρησιμοποιείτε Firefox (τον συνιστούμε) δεν χρειάζεστε αυτη την
17 
+    σελίδα. Απλώς εγκαταστείστε το <a
18 
+    href="https://addons.mozilla.org/firefox/2275/">πρόσθετο Torbutton</a>,
19 
+    επανεκκινήστε τον Firefox και είστε έτοιμοι:
20 
+    </p>
21 
+
22 
+    <img alt="Torbutton plugin for Firefox"
23 
+    src="../img/screenshot-torbutton.png" border="1"/> <br />
24 
+
25 
+    <p>Σε διαφορετική περίπτωση, πρέπει να ρυθμίσετε χειροκίνητα τις ρυθμίσεις
26 
+    πληρεξούσιου διακομιστή (proxy server) του φυλλομετρητή σας. <br/>Στον
27 
+    Mozilla και τον Firefox για Windows αυτό γίνεται μέσω
28 
+    Εργαλεία-Επιλογές-Γενικά-Ρυθμίσεις σύνδεσης.  <br/>Στον Firefox σε OS X,
29 
+    μέσω Firefox-Προτιμήσεις-Γενικά-Ρυθμίσεις σύνδεσης. <br/>Στον Firefox σε
30 
+    Linux μέσω Επεξεργασία-Προτιμήσεις-Για προχωρημένους-Δίκτυο. <br/>Στον Opera
31 
+    μέσω Εργαλεία-Προτιμήσεις (για προχωρημένους)-Δίκτυο-Διακομιστές. <br/>Αν
32 
+    και δεν συνιστούμε την χρήση ΙΕ, οι ρυθμίσεις για ανωνυμία περιορισμένου
33 
+    βαθμού είναι μέσω Εργαλείων-Επιλογές Internet-Συνδέσεις-Ρυθμίσεις
34 
+    LAN-Έλεγχος Διακομιστή Proxy-Για προχωρημένους.</p>
35 
+
36 
+    <img alt="Proxy settings in Firefox"
37 
+    src="../img/screenshot-win32-firefox-proxies.jpg" />
38 
+
39 
+    <p>
40 
+    Πρέπει να συμπληρώσετε τα "localhost" και "8118" ώστε να αντιστοιχούν στα
41 
+    τέσσερα πρωτόκολα του Polipo, όπως φαίνεται εδώ. (Αν και το Polipo δεν
42 
+    υποστηρίζει FTP και Gopher, <a
43 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">πρέπει
44 
+    παρ' όλα αυτά να τα ενεργοποιήσετε</a>. Πρέπει επίσης να συμπληρώσετε τον
45 
+    πληρεξούσιο διακομιστή socks ώστε να κατευθύνεται άμεσα στο Tor
46 
+    ("localhost", "9050" και socks5) ώστε να καλύπτονται και πρωτόκολα πέραν των
47 
+    τεσσάρων πρώτων. Πατήστε "ΟΚ".</p>
48 
+
49 
+    <hr />
50 
+
51 
+    <p>Αν έχετε προτάσεις για βελτίωση αυτού του εγγράφου, παρακλούμε <a
52 
+    href="<page about/contact>">να μας τις στείλετε</a>. Ευχαριστούμε!</p>
53 
+  </div>
54 
+  <!-- END MAINCOL -->
55 
+  <div id = "sidecol">
56 
+#include "side.wmi"
57 
+#include "info.wmi"
58 
+  </div>
59 
+  <!-- END SIDECOL -->
60 
+</div>
61 
+<!-- END CONTENT -->
62 
+#include <foot.wmi>
docs/el/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,194 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Εκτέλεση του <a href="<page index>">Tor</a> στα Microsoft Windows</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Οι οδηγίες αυτές είναι για την εγκατάσταση του Tor ώστε να τρέχουν σε
18 
+    Microsoft Windows (2000, XP, Vista, 7 και Server Edition).  Αν θέλετε να
19 
+    αναμεταδίδετε κυκλοφορία προς τρίτους ώστε να βοηθήσετε στην ανάπτυξη του
20 
+    δικτύου (παρακαλούμε να το κάνετε), διαβάστε τον οδηγό <a href="<page
21 
+    docs/tor-doc-relay>">Ρύθμιση ενός ενδιάμεσου</a>.</b>
22 
+    </p>
23 
+
24 
+    <p>Η Freedom House έχει δημιουργήσει ένα βίντεο για τον τρόπο εγκατάσταση του
25 
+    Tor.  Μπορείτε να το δείτε στην διεύθυνση <a
26 
+    href="http://media.torproject.org/video/2009-install-and-use-tor.ogv">Πώς να
27 
+    εγκαταστήσω το Tor σε Windows</a>.  Γνωρίζετε κάποι καλύτερο βίντεο;
28 
+    Ενημερώστε μας!</p>
29 
+
30 
+    <div class="center">
31 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor.ogv" autobuffer="true" controls="controls"></video></p>
32 
+    </div>
33 
+
34 
+    <hr /> <a id="installing"></a>
35 
+    <h2><a class="anchor" href="#installing">Βήμα Πρώτο: Κατεβάστε και εγκαταστήστε
36 
+    το Tor</a></h2>
37 
+    <br />
38 
+
39 
+    <p>
40 
+    Το πακέτο Microsoft Windows περιέχει <a href="<page index>">Tor</a>, <a
41 
+    href="<page projects/vidalia>">Vidalia</a> (a GUI for Tor), <a
42 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> (ένα πρόσθετο
43 
+    για το Mozilla Firefox), and <a
44 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (ένας
45 
+    πληρεξούσιος ιστού) σε πακέτο, όπου οι τέσσερεις εφαρμογές είναι
46 
+    προ-ρυθμισμένες να λειτουργούν μαζί. Κατεβάστε είτε την <a
47 
+    href="../<package-win32-bundle-stable>">σταθερή</a> ή την <a
48 
+    href="../<package-win32-bundle-alpha>">πειραματική</a> έκδοση του πακέτου
49 
+    Windows ή βρείτε περισσότερες επιλογές στην <a href="<page download/download>">σελίδα
50 
+    λήψεων</a>.
51 
+    </p>
52 
+
53 
+    <img alt="tor installer splash page"
54 
+    src="../img/screenshot-win32-installer-splash.png" />
55 
+
56 
+    <p>Αν έχετε εγκαταστήσει τα Tor, Vidalia ή Polipo προηγούμενα, μπορείτε να
57 
+    αποεπιλέξετε όποιο συστατικό δεν θέλετε να εγκατασταθεί, μέσα από τον
58 
+    διάλογο που φαίνεται παρακάτω.
59 
+    </p>
60 
+
61 
+    <img alt="select components to install"
62 
+    src="../img/screenshot-win32-installer-components.png" />
63 
+
64 
+    <p>Αφού ολοκληρωθεί η εγκατάσταση, τα συστατικά που επιλέξατε θα ξεκινήσουν
65 
+    αυτόματα.
66 
+    </p>
67 
+
68 
+    <p>Το Tor λειτουργεί αρχικά ως πρόγραμμα-client. Χρησιμοποιεί ένα ενσωματωμένο
69 
+    αρχικό αρχείο ρυθμίσεων και οι περισσότεροι χρήστες δεν χρειάζεται να κάνουν
70 
+    αλλαγές. Το Tor έχει τώρα εγκτασταθεί.
71 
+    </p>
72 
+
73 
+    <hr /> <a id="using"></a>
74 
+    <h2><a class="anchor" href="#using">Βήμα Δεύτερο: Ρυθμίστε τις εφαρμογές σας
75 
+    ώστε να χρησιμοποιούν το Tor</a></h2>
76 
+    <br />
77 
+
78 
+    <p>Μετά την εγκατάσταση των Tor και Polipo πρέπει να ρυθμίσετε τις εφαρμογές
79 
+    σας ώστε να τα χρησιμοποιούν. Το πρώτο βήμα είναι η ρύθμιση της περιήγησης
80 
+    στον ιστό.</p>
81 
+
82 
+    <p>Για μεγαλύτερη ασφάλεια χρησιμοποιείτε το Tor με Firefox και Torbutton.  Το
83 
+    πακέτο θα εγκαταστήσει για εσάς το <a
84 
+    href="https://addons.mozilla.org/firefox/2275/">πρόσθετο
85 
+    Torbutton</a>. Επανεκκινήστε τον Firefox και είστε έτοιμοι:
86 
+    </p>
87 
+
88 
+    <img alt="Torbutton plugin for Firefox"
89 
+    src="../img/screenshot-torbutton.png" border="1"/> <br />
90 
+
91 
+    <p>
92 
+    Αν σκοπεύετε να εκτελείτε τον Firefox σε υπολογιστή διαφορετικό από εκείνον
93 
+    του Tor, δείτε <a
94 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">το
95 
+    τμήμα του FAQ για την εκτέλεση του Tor σε άλλον υπολογιστή</a>.
96 
+    </p>
97 
+
98 
+    <p>Για να χρησιμοποιήσουν οι άλλες εφαρμογές που υποστηρίζουν πληρεξούσιους
99 
+    HTTP το Tor, απλώς ρυθμίστε τις να  επικοινωνούν με το Polipo (δηλαδή,
100 
+    ορίζοντας ως διεύθυνσή του localhost θύρα 8118). Για να χρησιμοποιείται
101 
+    άμεσα το SOCKS (για άμεσα μηνύματα, Jaber, IRC, κ.λ.π.) ρυθμίστε το
102 
+    πρόγραμμά σας να επικοινωνεί κατευθείαν με το Tor (localhost θύρα 9050) και
103 
+    διαβάστε <a
104 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">αυτό
105 
+    το θέμα στο FAQ</a>  για ποιό λόγο κάτι τέτοιο ίσως είναι επικίνδυνο. Για
106 
+    εφαρμογές που δεν υποστηρίζουν ούτε SOCKS ούτε HTTP, διαβάστε το SocksCap ή
107 
+    το <a href="http://www.freecap.ru/eng/">FreeCap</a>. (Το FreeCap είναι
108 
+    ελεύθερο λογισμικό, το SocksCap είναι ιδιωταγές).</p>
109 
+
110 
+    <p>Για πληροφορίες χρήσης άλλων εφαρμογών με το Tor δείτε το <a
111 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
112 
+    HOWTO</a>.
113 
+    </p>
114 
+
115 
+    <hr /> <a id="verify"></a>
116 
+    <h2><a class="anchor" href="#verify">Βήμα Τρίτο: Βεβαιωθείτε ότι δουλεύει</a></h2>
117 
+    <br />
118 
+
119 
+    <p>
120 
+    Βεβαιωθείτε ότι το Vidalia εκτελείται.  Το Vidalia χρησιμοποιεί ένα μικρό
121 
+    πράσινο κρεμύδι για να δείξει ότι το Tor εκτελείται, ή ένα μαύρο κρεμύδι με
122 
+    ένα κόκκινο "Χ" όταν το Tor δεν εκτελείται. Μπορείτε να εκκινήσετε ή να
123 
+    σταματήσετε το Tor κάνοντας δεξιό κλικ στο εικονίδιο του Vidalia στην
124 
+    περιοχή ειδοποιήσεων και επιλέγονας "Έναρξη" ή "Διακοπή" από το μενού, όπως
125 
+    φαίνεται πιο κάτω:
126 
+    </p>
127 
+
128 
+    <img alt="Vidalia Tray Icon" src="../img/screenshot-win32-vidalia.png"/>
129 
+
130 
+    <p>
131 
+    Έπειτα χρησιμοποιείστε τον περιηγητή σας με το Tor και βεβαιωθείτε ότι η
132 
+    διεύθυνσή σας ΙΡ είναι ανώνυμη. Κάνετε κλικ στον <a
133 
+    href="https://check.torproject.org/">ανιχνευτή Tor</a> και δείτε αν είστε
134 
+    συνδεδεμένος στο δίκτυο Tor. (Αν αυτός ο ιστότοπος είναι εκτός λειτουργίας,
135 
+    δείτε a
136 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">αυτό
137 
+    το θέμα του FAQ</a> για περισσότερες πληροφορίες πώς να ελέγξετε την σύνδεσή
138 
+    σας με το Tor).
139 
+    </p>
140 
+
141 
+    <p>Αν έχετε κάποιο τείχος προστασίας που περιορίζει τη δυνατότητα σύνδεσης στο
142 
+    δίκτυο, βεβαιωθείτε ότι έχετε επιτρέψει τις συνδέσεις από τις τοπικές
143 
+    εφαρμογές σας προς τις τοπικές θύρες 8118 και 9050. Αν το τείχος προστασίας
144 
+    σας φράσσει τις εξερχόμενες συνδέσεις σας ρυθμίστε το ώστε να μπορεί να
145 
+    συνδεθεί τουλάχιστον στις θύρες TCP 80 και 443 και μετά διαβάστε <a
146 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">αυτότ
147 
+    ο θέμα στο FAQ</a>.
148 
+    </p>
149 
+
150 
+    <p>Αν εξακολουθεί να μην δουλεύει, διαβάστε αυτό το <a
151 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">
152 
+    θέμα του FAQ</a> για συμβουλές.</p>
153 
+
154 
+    <p>
155 
+    Μόλις συνδεθείτε με επιτυχία στο δίκτυο Tor, διαβάστε περισσότερα <a
156 
+    href="<page download/download>#Warning">τι κάνει και τι όχι το Tor</a>.
157 
+    </p>
158 
+
159 
+    <hr /> <a id="server"></a> <a id="relay"></a>
160 
+    <h2><a class="anchor" href="#relay">Βήμα Τέταρτο: Ρυθμίστε το ως ενδιάμεσο</a></h2>
161 
+    <br />
162 
+
163 
+    <p>Για να προσφέρει εύρος ζώνης, το δίκτυο Tor βασίζεται στους εθελοντές. Όσο
164 
+    περισσότερο άνθρωποι γίνονται ενδιάμεσοι αναμεταδότες, τόσο πιο γρήγορο θα
165 
+    είναι το δίκτυο Tor.  Αν έχετε τουλάχιστον 20 kilobytes/sec προς κάθε
166 
+    κατεύθυνση, βοηθείστε το Tor ρυθμίζοντάς το ως ενδιάμεσο.  Υπάρχουν πολλά
167 
+    στοιχεία που καθιστούν τους ενδιάμεσους Tor εύκολους και βολικούς, όπως
168 
+    περιορισμός της κλίμακας εύρους ζώνης, πολιτικές εξόδου ώστε να μην
169 
+    εκτίθεστε σε διαμαρτυρίες και υποστήριξη για δυναμικές ΙΡ διευθύνσεις.</p>
170 
+
171 
+    <p>Όταν υπάρχουν ενδιάμεσοι σε διάφορα σημεία το Διαδικτύου, το Tor γίνεται
172 
+    ασφαλέστερο.  <a
173 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Κι
174 
+    εσει οι ίδιοι απολαμβάνεται μεγαλύτερη ανωνυμία</a>, αφού οι απομακρυσμένοι
175 
+    ιστότοποι δεν γνωρίζουν αν οι συνδέσεις σας έγιναν από τον υπολογιστή σας ή
176 
+    αναμεταδόθηκαν από άλλους.</p>
177 
+
178 
+    <p>Διαβάστε περισσότερα στο οδηγό μας <a href="<page
179 
+    docs/tor-doc-relay>">Ρυθμίζοντας έναν ενδιάμεσο αναμεταδότη</a>.</p>
180 
+
181 
+    <hr />
182 
+
183 
+    <p>Αν έχετε προτάσεις για βελτίωση αυτού του εγγράφου, παρακαλώ <a href="<page
184 
+    about/contact>">υποβάλετέ τις εδώ</a>. Ευχαριστούμε!</p>
185 
+  </div>
186 
+  <!-- END MAINCOL -->
187 
+  <div id = "sidecol">
188 
+#include "side.wmi"
189 
+#include "info.wmi"
190 
+  </div>
191 
+  <!-- END SIDECOL -->
192 
+</div>
193 
+<!-- END CONTENT -->
194 
+#include <foot.wmi>
docs/en/N900.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,188 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21979 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: N900 Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/N900>">N900</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="Maemo"></a>
14 
+    <h2><a class="anchor" href="#Maemo">Installing Tor on Maemo</a></h2>
15 
+    <br />
16 
+    <p>
17 
+    If you have a Maemo device that is not the <a href="#N900">N900</a>, we
18 
+    suggest you install the Tor package from the
19 
+    <a href="http://maemo.org/packages/view/tor/">Maemo website</a>. The Tor
20 
+    Project does not produce these packages. They are maintained by the
21 
+    Maemo community.
22 
+    </p>
23 
+
24 
+    <a id="N900"></a>
25 
+    <h2><a class="anchor" href="#N900">Installing Tor on the N900</a></h2>
26 
+    <br />
27 
+    <p>
28 
+    The following instructions should help install an
29 
+    <a href="https://garage.maemo.org/projects/tor-status">experimental
30 
+    Tor controller</a> and Tor as packaged for the N900 Nokia telephone. This is
31 
+    currently an untested configuration. The browser in this configuration does
32 
+    not have Torbutton and it should not be used for high security anonymity needs
33 
+    at this time.
34 
+    </p>
35 
+
36 
+    <p>
37 
+    Open the Application manager: <br />
38 
+    <a href="../img/N900/1_app_menu.png">
39 
+    <img border="0" alt="N900 application menu"
40 
+    src="../img/N900/1_app_menu-small.png"/>
41 
+    </a>
42 
+    </p>
43 
+
44 
+    <p>
45 
+    Click on the Application manager menu at the top of the screen: <br />
46 
+    <a href="../img/N900/2_app_manager.png">
47 
+    <img border="0" alt="N900 application manager"
48 
+    src="../img/N900/2_app_manager-small.png"/>
49 
+    </a>
50 
+    </p>
51 
+
52 
+    <p>
53 
+    Select 'Application catalogs': <br />
54 
+    <a href="../img/N900/3_app_managermenu.png">
55 
+    <img border="0" alt="N900 application catalogs"
56 
+    src="../img/N900/3_app_managermenu-small.png"/>
57 
+    </a>
58 
+    </p>
59 
+
60 
+    <p>
61 
+    Press 'New' to enable the maemo extras-devel repository. <br />
62 
+    <small>Note: This repository contains untested packages that might harm your
63 
+    device. <br />
64 
+    See <a href="http://wiki.maemo.org/Extras-devel">Extras-devel</a> for
65 
+    details. You should probably disable extras-devel after installing Tor, or
66 
+    proceed at your own risk.</small>
67 
+    <br />
68 
+    <a href="../img/N900/4_catalog_list.png">
69 
+    <img border="0" alt="N900 catalog list"
70 
+    src="../img/N900/4_catalog_list-small.png"/>
71 
+    </a>
72 
+    </p>
73 
+
74 
+    <p>
75 
+    Enter the following information into the catalog addition screen:
76 
+    <p>
77 
+    <pre>
78 
+    Catalog name:    Extras devel
79 
+    Web address:    http://repository.maemo.org/extras-devel/
80 
+    Distribution:        fremantle
81 
+    Components:    free non-free
82 
+    </pre>
83 
+    </p>
84 
+    <br />
85 
+    Make sure 'Disabled' is unchecked, hit 'Save', and wait for the package list
86 
+    to update.<br />
87 
+    <a href="../img/N900/5_new_catalog.png">
88 
+    <img border="0" alt="N900 new catalog"
89 
+    src="../img/N900/5_new_catalog-small.png"/>
90 
+    </a>
91 
+    </p>
92 
+
93 
+    <p>
94 
+    Press 'Download' in the App manager: <br />
95 
+    <a href="../img/N900/6_app_manager.png">
96 
+    <img border="0" alt="N900 app manager"
97 
+    src="../img/N900/6_app_manager-small.png"/>
98 
+    </a>
99 
+    </p>
100 
+
101 
+    <p>
102 
+    Select the Network category (or search for Tor): <br />
103 
+    <a href="../img/N900/7_app_categories.png">
104 
+    <img border="0" alt="N900 application categories"
105 
+    src="../img/N900/7_app_categories-small.png"/>
106 
+    </a>
107 
+    </p>
108 
+
109 
+    <p>
110 
+    Scroll down and select 'Tor Status Area Applet': <br />
111 
+    <a href="../img/N900/8_app_list.png">
112 
+    <img border="0" alt="N900 application list"
113 
+    src="../img/N900/8_app_list-small.png"/>
114 
+    </a>
115 
+    </p>
116 
+
117 
+    <p>
118 
+    Agree to the disclaimer and press 'Continue': <br />
119 
+    <a href="../img/N900/9_disclaimer.png">
120 
+    <img border="0" alt="N900 disclaimer"
121 
+    src="../img/N900/9_disclaimer-small.png"/>
122 
+    </a>
123 
+    </p>
124 
+
125 
+    <p>
126 
+    When the install is done, disable the extras-devel repository, and reboot
127 
+    the device: <br />
128 
+    <a href="../img/N900/10_success.png">
129 
+    <img border="0" alt="N900 success"
130 
+    src="../img/N900/10_success-small.png"/>
131 
+    </a>
132 
+    </p>
133 
+
134 
+    <p>
135 
+    After rebooting the N900, open the status menu: <br />
136 
+    <a href="../img/N900/11_after_rebooting.png">
137 
+    <img border="0" alt="N900 status menu post-reboot"
138 
+    src="../img/N900/11_after_rebooting-small.png"/>
139 
+    </a>
140 
+    </p>
141 
+
142 
+    <p>
143 
+    Select 'The Onion Router' from the list: <br />
144 
+    <a href="../img/N900/12_status_menu.png">
145 
+    <img border="0" alt="N900 status menu selection"
146 
+    src="../img/N900/12_status_menu-small.png"/>
147 
+    </a>
148 
+    </p>
149 
+
150 
+    <p>
151 
+    Enable onion routing, and press 'Save': <br />
152 
+    <a href="../img/N900/13_enable_tor.png">
153 
+    <img border="0" alt="N900 enabling Tor"
154 
+    src="../img/N900/13_enable_tor-small.png"/>
155 
+    </a>
156 
+    </p>
157 
+
158 
+    <p>
159 
+    Visit <a href="https://check.torproject.org/">TorCheck</a> to confirm that
160 
+    you are routing browser traffic through Tor: <br />
161 
+    <a href="../img/N900/14_check_tor.png">
162 
+    <img border="0" alt="N900 check Tor"
163 
+    src="../img/N900/14_check_tor-small.png"/>
164 
+    </a>
165 
+    </p>
166 
+
167 
+    <p>
168 
+    Note that this might not always give you the latest stable Tor version.
169 
+    Additionally, the N900 web browser does not have Torbutton. This means that
170 
+    while it may be useful for circumvention, it probably is unsuitable for strong
171 
+    web browser anonymity requirements.
172 
+    </p>
173 
+
174 
+    <hr />
175 
+
176 
+    <p>If you have suggestions for improving this document, please <a
177 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
178 
+  </div>
179 
+  <!-- END MAINCOL -->
180 
+  <div id = "sidecol">
181 
+#include "side.wmi"
182 
+#include "info.wmi"
183 
+  </div>
184 
+  <!-- END SIDECOL -->
185 
+</div>
186 
+<!-- END CONTENT -->
187 
+#include <foot.wmi>
188 
+
docs/en/android.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,156 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22402 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Android Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/android>">Android</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h2><a class="anchor" href="#Android">Tor on Android</a></h2>
14 
+    <br />
15 
+    <p>
16 
+    Tor is available for Android by installing our package named Orbot.
17 
+    </p>
18 
+    <p>
19 
+    Orbot is an application that allows mobile phone users to access the web,
20 
+    instant messaging and email without being monitored or blocked by their mobile
21 
+    internet service provider. Orbot brings the features and functionality of Tor
22 
+    to the Android mobile operating system.
23 
+    </p>
24 
+    <p>
25 
+    Orbot contains Tor, libevent and privoxy. Orbot provides a local HTTP proxy
26 
+    and the standard SOCKS4A/SOCKS5 proxy interfaces into the Tor network. Orbot
27 
+    has the ability to transparently torify all of the TCP traffic on your Android
28 
+    device when it has the correct permissions.
29 
+    </p>
30 
+
31 
+    <a id="QrCode"></a>
32 
+    <h2><a class="anchor" href="#QrCode">Installing Tor with a QR code</a></h2>
33 
+    <br />
34 
+    <p>
35 
+    Orbot is easy to install by simply scanning the following QR code with your
36 
+    Android Barcode scanner.
37 
+    </p>
38 
+
39 
+    <p>
40 
+    <a href="../img/android/orbot-qr-code-latest.png">
41 
+    <img border="0" alt="Android QR code"
42 
+    src="../img/android/orbot-qr-code-latest.png"/>
43 
+    </a>
44 
+    </p>
45 
+
46 
+    <a id="Market"></a>
47 
+    <h2><a class="anchor" href="#Market">Installing Tor from the Android Market</a></h2>
48 
+    <br />
49 
+    <p>
50 
+    Orbot is not currently in the Android Market. It will be available in the
51 
+    market in the very near future.
52 
+    </p>
53 
+
54 
+    <a id="Manual"></a>
55 
+    <h2><a class="anchor" href="#Manual">Installing Tor from our website manually</a></h2>
56 
+    <br />
57 
+    <p>
58 
+    You can download <a href="../<package-androidbundle-alpha>">our most recent version of Orbot</a> and <a href="../<package-androidbundle-alpha-sig>">the gpg signature</a> from our server.
59 
+    </p>
60 
+
61 
+    <a id="Screenshots"></a>
62 
+    <h2><a class="anchor" href="#Screenshots">Screenshots of Tor on Android</a></h2>
63 
+    <br />
64 
+    <p>
65 
+    <a href="../img/android/android-off.jpg">
66 
+    <img border="0" alt="Android Tor off"
67 
+    src="../img/android/android-off-150x150.jpg"/>
68 
+    </a>
69 
+    <a href="../img/android/android-bootstrapping.jpg">
70 
+    <img border="0" alt="Android Tor bootstrapping"
71 
+    src="../img/android/android-bootstrapping-150x150.jpg"/>
72 
+    </a>
73 
+    <a href="../img/android/android-activated.jpg">
74 
+    <img border="0" alt="Android Tor activated"
75 
+    src="../img/android/android-activated-150x150.jpg"/>
76 
+    </a>
77 
+    <a href="../img/android/android-settings.jpg">
78 
+    <img border="0" alt="Android Tor settings"
79 
+    src="../img/android/android-settings-150x150.jpg"/>
80 
+    </a>
81 
+    </p>
82 
+
83 
+    <a id="ProxySettings"></a>
84 
+    <h2><a class="anchor" href="#ProxySettings">Proxy settings and configuration
85 
+    </a></h2>
86 
+    <br />
87 
+    <p>
88 
+    Orbot offers three interfaces into the Tor network:
89 
+    <ul>
90 
+    <li>SOCKS 4A/5 proxy 127.0.0.1:9050</li>
91 
+    <li>HTTP proxy 127.0.0.1:8118 </li>
92 
+    <li>Transparent proxying (on select devices)</li>
93 
+    </ul>
94 
+    </p>
95 
+
96 
+    <a id="Notes"></a>
97 
+    <h2><a class="anchor" href="#Notes">Platform specific notes</a></h2>
98 
+    <br />
99 
+    <p>
100 
+    The current version of Orbot ships with the following components:
101 
+    <b><version-android-components></b>
102 
+    </p>
103 
+    <br />
104 
+    <p>
105 
+    For standard Android 1.x devices (G1, MyTouch3G, Hero, Droid Eris, Cliq, Moment):
106 
+    <ul>
107 
+    <li>The “ProxySurf” browser available in the Android Market allows for use
108 
+        of a proxy. Simply set the HTTP Proxy to '127.0.0.1' and port '8118'.
109 
+        <b>This only proxies some traffic and should not be considered secure.</b>
110 
+        </li>
111 
+    <li>For Instant Messsaging, try “Beem” in the market, and set the Proxy to SOCKS5 '127.0.0.1' and port '9050'.</li>
112 
+    </ul>
113 
+    </p>
114 
+    <p>
115 
+    For Android 2.x devices: Droid, Nexus One
116 
+    <ul>
117 
+    <li>You must root your device for Orbot to transparently proxy all TCP traffic.</li>
118 
+    <li>For non-modified and non-rooted phones, you'll want to manually configure
119 
+        your specific applications.</li>
120 
+    <li>If you root your device, whether it is 1.x or 2.x based, Orbot will
121 
+        automatically, transparently proxy all web traffic on port 80 and 443
122 
+        and all DNS requests. This includes the built-in Browser, Gmail, YouTube,
123 
+        Maps and any other application that uses standard web traffic.</li>
124 
+    </ul>
125 
+    </p>
126 
+
127 
+    <a id="Source"></a>
128 
+    <h2><a class="anchor" href="#Source">Source code access</a></h2>
129 
+    <br />
130 
+    <p>
131 
+    All of the source code is available in the
132 
+    <a href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/">Orbot
133 
+    subversion repository</a>.
134 
+    </p>
135 
+
136 
+    <p>
137 
+    Note that this might not always give you the latest stable Tor version.
138 
+    Additionally, the Android web browser does not have Torbutton. This means that
139 
+    while it may be useful for circumvention, it probably is unsuitable for strong
140 
+    web browser anonymity requirements.
141 
+    </p>
142 
+
143 
+    <hr />
144 
+
145 
+    <p>If you have suggestions for improving this document, please <a
146 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
147 
+  </div>
148 
+  <!-- END MAINCOL -->
149 
+  <div id = "sidecol">
150 
+#include "side.wmi"
151 
+#include "info.wmi"
152 
+  </div>
153 
+  <!-- END SIDECOL -->
154 
+</div>
155 
+<!-- END CONTENT -->
156 
+#include <foot.wmi>
docs/en/bridges.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,209 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22432 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Bridges" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/bridges>">Bridges</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="BridgeIntroduction"></a>
14 
+    <h2><a class="anchor" href="#BridgeIntroduction">Tor: Bridges</a></h2>
15 
+    <hr />
16 
+
17 
+    <p>
18 
+    Bridge relays (or "bridges" for short) are Tor relays that aren't listed in
19 
+    the main Tor directory. Since there is no complete public list of them, even if
20 
+    your ISP is filtering connections to all the known Tor relays, they probably
21 
+    won't be able to block all the bridges. If you suspect your access to the
22 
+    Tor network is being blocked, you may want to use the bridge feature of Tor.
23 
+    </p>
24 
+
25 
+    <p>
26 
+    The addition of bridges to Tor is a step forward in the blocking
27 
+    resistance race. It is perfectly possible that even if your ISP filters
28 
+    the Internet, you do not require a bridge to use Tor. Many filtering
29 
+    programs look for unencrypted Tor directory requests to recognize that
30 
+    you're using Tor, but Tor version 0.2.0.23-rc and later use encrypted
31 
+    directory queries by default. This change means that most filtering
32 
+    programs are now unable to recognize Tor connections. So you should try
33 
+    to use Tor without bridges first, since it might work.
34 
+    </p>
35 
+
36 
+    <p>
37 
+    Note that it's also possible that Tor is non-functional for other
38 
+    reasons. The latest version of <a href="<page projects/torbrowser>">The
39 
+    Tor Browser Bundle</a> on Windows tries to give you better hints about
40 
+    why Tor is having problems connecting. You should also read <a
41 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#IinstalledTorandPolipobutitsnotworking.">the
42 
+    FAQ about problems with running Tor properly</a> when you have issues.
43 
+    If you feel that the issue is clearly blocking, or you'd simply like to try
44 
+    because you're unsure or feeling adventurous, please read on. Ensure
45 
+    that you're using the <a href="<page download/download>#Dev">latest 0.2.1.x or
46 
+    0.2.2.x bundle for your platform</a>.
47 
+    </p>
48 
+
49 
+    <p>
50 
+    To use a bridge, you'll need to locate one. Furthermore, you'll need to
51 
+    configure Tor with whatever bridge address you intend to use. You'll do this
52 
+    with Vidalia, the Tor controller.
53 
+    If your Internet connection requires the use of a proxy, you'll probably
54 
+    need to configure Vidalia to do so first. If you don't think you need
55 
+    to configure a proxy for your Internet connection, you probably don't.
56 
+    Give it a try and if you have issues, ask us for help.
57 
+    </p>
58 
+
59 
+    <p>Freedom House has produced a video on how to get and use Tor bridges.
60 
+    If you don't see a video below, view it at <a
61 
+    href="http://www.youtube.com/thetorproject">Youtube:
62 
+    Freedom4Internet</a> Know of a better video, or one translated into
63 
+    your language?  Let us know!</p>
64 
+
65 
+    <div class="center">
66 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-using-a-bridge-relay-to-access-tor.ogv" autobuffer="true" controls="controls"></video></p>
67 
+    </div>
68 
+
69 
+    <p>
70 
+    At the moment, you can get a bridge by visiting
71 
+    <a href="https://bridges.torproject.org/">https://bridges.torproject.org/</a>
72 
+    with your web browser. If this page is filtered for you, and you
73 
+    don't have any other proxies or ways to reach it, there are <a
74 
+    href="#FindingMore">other ways to find bridges</a> too.
75 
+    </p>
76 
+
77 
+    <a id="Understanding"></a>
78 
+    <h2><a class="anchor" href="#Understanding">Understanding bridges</a></h2>
79 
+    <hr />
80 
+
81 
+    <p>
82 
+    As an example, you'll get a bridge entry that looks like the
83 
+    following:
84 
+    </p>
85 
+    <pre><samp>
86 
+    bridge 141.201.27.48:443 4352e58420e68f5e40bf7c74faddccd9d1349413
87 
+    </samp>
88 
+    </pre>
89 
+
90 
+    <p>
91 
+    Understanding the components of a bridge line isn't strictly required
92 
+    but may prove useful. You can skip this section if you'd like.<br />
93 
+    The first element is the IP address: <tt>'141.201.27.48'</tt><br />
94 
+    The second element is the port: <tt>'443'</tt><br />
95 
+    The third element, the fingerprint, is optional:
96 
+    <tt>'4352e58420e68f5e40bf7c74faddccd9d1349413'</tt><br />
97 
+    </p>
98 
+
99 
+    <a id="UsingBridges"></a>
100 
+    <h2><a class="anchor" href="#UsingBridges">Using bridges with Tor and
101 
+    Vidalia</a></h2>
102 
+    <hr />
103 
+
104 
+    <p>
105 
+    To use the example bridge address above, go to Vidalia's Network settings
106 
+    page, and click "My ISP blocks connections to the Tor network".  Add each
107 
+    bridge address one at a time in the Vidalia Network settings page,
108 
+    by pasting it into the "Add a Bridge" window and then clicking the "+"
109 
+    sign. Adding a bridge is pictured below:
110 
+    </p>
111 
+
112 
+    <br /><br />
113 
+    <img src="$(IMGROOT)/vidalia-bridges.png" alt="Vidalia's Network settings page" />
114 
+    <br /><br />
115 
+
116 
+    <p>
117 
+    You'll want to add as many bridge addresses as you know about, since
118 
+    additional bridges will increase reliability. One bridge should be enough
119 
+    to reach the Tor network, but if you only have one bridge and it goes
120 
+    down, you will be cut off from the Tor network.
121 
+    </p>
122 
+
123 
+    <a id="FindingMore"></a>
124 
+    <h2><a class="anchor" href="#FindingMore">Finding more bridges for Tor</a></h2>
125 
+    <hr />
126 
+
127 
+    <p>
128 
+    Another way to find public bridge addresses is to send mail to
129 
+    bridges@torproject.org with the line "get bridges" by itself in the
130 
+    body of the mail. You'll need to send this request from a gmail
131 
+    account, though &mdash; otherwise we make it too easy for an attacker
132 
+    to make a lot of email addresses and learn about all the bridges.
133 
+    Almost instantly, you'll receive a reply that includes:
134 
+    </p>
135 
+    <pre>
136 
+    Here are your bridge relays:
137 
+
138 
+     bridge 60.16.182.53:9001 c9111bd74a710c0d25dda6b35e181f1aa7911133
139 
+     bridge 87.237.118.139:444 c18dde4804e8fcb48464341ca1375eb130453a39
140 
+     bridge 60.63.97.221:443 ab5c849ed5896d53052e43966ee9aba2ff92fb82
141 
+
142 
+    </pre>
143 
+    <p>
144 
+    Once you've received the email with bridge information, you can continue the Vidalia configuration steps outlined <a href="#UsingBridges">above</a>.
145 
+    </p>
146 
+
147 
+    <a id="RunningABridge"></a>
148 
+    <h2><a class="anchor" href="#RunningABridge">Running a Tor Bridge</a></h2>
149 
+    <hr />
150 
+
151 
+    <p>
152 
+    If you want to help out and you can't run a <a href="<page
153 
+    docs/tor-doc-relay>">normal Tor relay</a>, you should
154 
+    run a bridge relay. You can configure it either way:
155 
+    <ul>
156 
+    <li> manually <a
157 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
158 
+    your torrc file</a> to be just these four lines:<br />
159 
+    <pre><code>
160 
+    SocksPort 0
161 
+    ORPort 443
162 
+    BridgeRelay 1
163 
+    Exitpolicy reject *:*
164 
+    </code></pre></li>
165 
+    <li><a href="<page docs/tor-doc-relay>">or using Vidalia</a>:<br />
166 
+    <img src="$(IMGROOT)/vidalia-bridges-setup.png" alt="Vidalia's Sharing
167 
+    settings page" /></li>
168 
+    </ul>
169 
+    </p>
170 
+
171 
+    <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
172 
+    on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
173 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Myfirewallonlyallowsafewoutgoingports.">some
174 
+    complex port forwarding</a>.
175 
+    </p>
176 
+
177 
+    <p>
178 
+    When configured as a bridge, your server will <b>not</b> appear in the public
179 
+    Tor network.
180 
+    </p>
181 
+
182 
+    <p>
183 
+    Your bridge relay will automatically publish its address to the bridge
184 
+    authority, which will give it out via https or email as above. You can
185 
+    also tell a user about your bridge directly: if you're using Vidalia,
186 
+    you can copy-and-paste the bridge address from the Settings window. If
187 
+    you're on Linux or BSD, you can construct the bridge address manually
188 
+    using the <a href="#Understanding">format above</a> (you can find the
189 
+    fingerprint in your Tor log files or in <tt>/var/lib/tor/fingerprint</tt>
190 
+    depending on your platform).
191 
+    </p>
192 
+
193 
+    <p>
194 
+    If you would like to learn more about our bridge
195 
+    design from a technical standpoint, please read the <a
196 
+    href="<gitblob>doc/spec/bridges-spec.txt">Tor bridges
197 
+    specification</a>. If you're interested in running an unpublished bridge
198 
+    or other non-standard uses, please do read the specification.
199 
+    </p>
200 
+  </div>
201 
+  <!-- END MAINCOL -->
202 
+  <div id = "sidecol">
203 
+#include "side.wmi"
204 
+#include "info.wmi"
205 
+  </div>
206 
+  <!-- END SIDECOL -->
207 
+</div>
208 
+<!-- END CONTENT -->
209 
+#include <foot.wmi>
docs/en/debian-vidalia.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,120 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22269 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Vidalia: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian-vidalia>">Vidalia Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <a id="packages"></a>
15 
+    <h2><a class="anchor" href="#debian">Vidalia on Ubuntu or Debian</a></h2>
16 
+    <br />
17 
+
18 
+    <p>
19 
+    <b>Do not use the packages in Ubuntu's universe.</b> They are unmaintained
20 
+    and out of date. That means you'll be missing stability and security
21 
+    fixes.
22 
+    </p>
23 
+
24 
+    <p>
25 
+    You'll need to set up our package repository before you can fetch
26 
+    Vidalia. First, you need to figure out the name of your distribution. If
27 
+    you're using Ubuntu 9.10 or 10.04, it's  "karmic", while 9.04 is "jaunty",
28 
+    8.10 is "intrepid", and 8.04 is "hardy". If you're using Debian
29 
+    Etch, it's "etch", and Debian Lenny is "lenny". Then add this line to your
30 
+    <tt>/etc/apt/sources.list</tt>
31 
+    file:<br />
32 
+    <pre>
33 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
34 
+    </pre>
35 
+    where you substitute the above word (etch, lenny, sid, karmic, jaunty,
36 
+    intrepid, hardy) in place of &lt;DISTRIBUTION&gt;.
37 
+    </p>
38 
+
39 
+    <p>
40 
+    Then add the gpg key used to sign the packages by running the following
41 
+    commands at your command prompt:
42 
+    <pre>
43 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
44 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
45 
+    </pre>
46 
+    Now refresh your sources and install Vidalia by running the following
47 
+    commands at your command prompt:
48 
+    <pre>
49 
+    apt-get update
50 
+    apt-get install vidalia
51 
+    </pre>
52 
+    </p>
53 
+
54 
+    <p>
55 
+    Now Vidalia is installed and running. Move on to <a href="<page
56 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Vidalia on Linux/Unix"
57 
+    instructions.
58 
+    </p>
59 
+
60 
+    <p style="font-size: small">
61 
+    The DNS name <code>deb.torproject.org</code> is actually a set of independent
62 
+    servers in a DNS round robin configuration.  If you for some reason cannot
63 
+    access it you might try to use the name of one of its part instead.  Try
64 
+    <code>deb-master.torproject.org</code>,
65 
+    <code>mirror.netcologne.de</code> or
66 
+    <code>vidalia.mirror.youam.de</code>.
67 
+    </p>
68 
+
69 
+    <hr />
70 
+
71 
+    <a id="source"></a>
72 
+    <h2><a class="anchor" href="#source">Building from source</a></h2>
73 
+    <br />
74 
+
75 
+    <p>
76 
+    If you want to build your own debs from source you must first add an
77 
+    appropriate <tt>deb-src</tt> line to <tt>sources.list</tt>.
78 
+    <pre>
79 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
80 
+    </pre>
81 
+    You also need to install the necessary packages to build your own debs and the
82 
+    packages needed to build Vidalia:
83 
+    <pre>
84 
+    apt-get install build-essential fakeroot devscripts qt4-dev-tools qt4-designer libqt4-dev g++ cmake
85 
+    apt-get build-dep vidalia
86 
+    </pre>
87 
+    Then you can build Vidalia in ~/debian-packages:
88 
+    <pre>
89 
+    mkdir ~/debian-packages; cd ~/debian-packages
90 
+    apt-get source vidalia
91 
+    cd vidalia-*
92 
+    debuild -rfakeroot -uc -us
93 
+    cd ..
94 
+    </pre>
95 
+    Now you can install the new package:
96 
+    <pre>
97 
+    sudo dpkg -i vidalia_*.deb
98 
+    </pre>
99 
+    </p>
100 
+
101 
+    <p>
102 
+    Now Vidalia is installed and running. Move on to <a href="<page
103 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Vidalia on Linux/Unix"
104 
+    instructions.
105 
+    </p>
106 
+
107 
+    <hr />
108 
+
109 
+    <p>If you have suggestions for improving this document, please <a
110 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
111 
+  </div>
112 
+  <!-- END MAINCOL -->
113 
+  <div id = "sidecol">
114 
+#include "side.wmi"
115 
+#include "info.wmi"
116 
+  </div>
117 
+  <!-- END SIDECOL -->
118 
+</div>
119 
+<!-- END CONTENT -->
120 
+#include <foot.wmi>
docs/en/debian.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,187 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22268 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian>">Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <h2><a class="anchor" href="#debian">Option one: Tor on Debian lenny,
15 
+    Debian sid, or Debian testing</a></h2>
16 
+    <br />
17 
+
18 
+    <p>
19 
+    If you're using Debian stable (lenny), unstable (sid), or testing
20 
+    (squeeze), just run<br />
21 
+    <tt>apt-get install tor tor-geoipdb</tt>
22 
+    as root.
23 
+    </p>
24 
+
25 
+    <p>
26 
+    Note that this might not always give you the latest stable Tor version, but
27 
+    you will receive important security fixes. To make sure that you're running
28 
+    the latest stable version of Tor, see option two below.
29 
+    </p>
30 
+
31 
+    <p>
32 
+    Now Tor is installed and running. Move on to <a href="<page
33 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Tor on Linux/Unix"
34 
+    instructions.
35 
+    </p>
36 
+
37 
+    <hr />
38 
+
39 
+    <a id="ubuntu"></a>
40 
+    <a id="packages"></a>
41 
+    <h2><a class="anchor" href="#ubuntu">Option two: Tor on Ubuntu or
42 
+    Debian</a></h2>
43 
+    <br />
44 
+
45 
+    <p>
46 
+    <b>Do not use the packages in Ubuntu's universe.</b> They are unmaintained
47 
+    and out of date. That means you'll be missing stability and security
48 
+    fixes.
49 
+    </p>
50 
+
51 
+    <p>
52 
+    You'll need to set up our package repository before you can fetch
53 
+    Tor. First, you need to figure out the name of your distribution. If
54 
+    you're using Ubuntu 9.10 or 10.04, it's  "karmic", while 9.04 is "jaunty",
55 
+    8.10 is "intrepid", and 8.04 is "hardy". If you're using Debian
56 
+    Etch, it's "etch", and Debian Lenny is "lenny". Then add this line to your
57 
+    <tt>/etc/apt/sources.list</tt>
58 
+    file:<br />
59 
+    <pre>
60 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
61 
+    </pre>
62 
+    where you put the codename of your distribution (i.e. etch, lenny, sid, karmic,
63 
+    jaunty, intrepid, hardy or whatever it is) in place of &lt;DISTRIBUTION&gt;.
64 
+    </p>
65 
+
66 
+    <p>
67 
+    Then add the gpg key used to sign the packages by running the following
68 
+    commands at your command prompt:
69 
+    <pre>
70 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
71 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
72 
+    </pre>
73 
+    Now refresh your sources and install Tor by running the following
74 
+    commands at your command prompt:
75 
+    <pre>
76 
+    apt-get update
77 
+    apt-get install tor tor-geoipdb
78 
+    </pre>
79 
+    </p>
80 
+
81 
+    <p>
82 
+    Now Tor is installed and running. Move on to <a href="<page
83 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Tor on Linux/Unix"
84 
+    instructions.
85 
+    </p>
86 
+
87 
+    <p style="font-size: small">
88 
+    The DNS name <code>deb.torproject.org</code> is actually a set of independent
89 
+    servers in a DNS round robin configuration.  If you for some reason cannot
90 
+    access it you might try to use the name of one of its part instead.  Try
91 
+    <code>deb-master.torproject.org</code>,
92 
+    <code>mirror.netcologne.de</code> or
93 
+    <code>tor.mirror.youam.de</code>.
94 
+    </p>
95 
+
96 
+    <hr />
97 
+
98 
+    <a id="development"></a>
99 
+    <h2><a class="anchor" href="#development">Option three: Using the
100 
+    development branch of Tor on Debian or Ubuntu</a></h2>
101 
+    <br />
102 
+
103 
+    <p>If you want to use the <a href="<page
104 
+    download/download>#packagediff">development branch</a> of Tor instead (more
105 
+    features and more bugs), you need to add a different set of lines to
106 
+    your <tt>/etc/apt/sources.list</tt> file:<br />
107 
+    <pre>
108 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
109 
+    deb     http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
110 
+    </pre>
111 
+    where you again substitute the name of your distro (etch, lenny, sid, karmic,
112 
+    jaunty, intrepid, hardy) in place of &lt;DISTRIBUTION&gt;.
113 
+    </p>
114 
+
115 
+    <p>
116 
+    Then run the following commands at your command prompt:
117 
+    <pre>
118 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
119 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
120 
+    apt-get update
121 
+    apt-get install tor tor-geoipdb
122 
+    </pre>
123 
+    </p>
124 
+
125 
+    <p>
126 
+    Now Tor is installed and running. Move on to <a href="<page
127 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Tor on Linux/Unix"
128 
+    instructions.
129 
+    </p>
130 
+
131 
+    <hr />
132 
+
133 
+    <a id="source"></a>
134 
+    <h2><a class="anchor" href="#source">Building from source</a></h2>
135 
+    <br />
136 
+
137 
+    <p>
138 
+    If you want to build your own debs from source you must first add an
139 
+    appropriate <tt>deb-src</tt> line to <tt>sources.list</tt>.
140 
+    <pre>
141 
+    # For the stable version.
142 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
143 
+
144 
+    # For the unstable version.
145 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
146 
+    deb-src http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
147 
+    </pre>
148 
+    You also need to install the necessary packages to build your own debs and the
149 
+    packages needed to build Tor:
150 
+    <pre>
151 
+    apt-get install build-essential fakeroot devscripts
152 
+    apt-get build-dep tor
153 
+    </pre>
154 
+    Then you can build Tor in ~/debian-packages:
155 
+    <pre>
156 
+    mkdir ~/debian-packages; cd ~/debian-packages
157 
+    apt-get source tor
158 
+    cd tor-*
159 
+    debuild -rfakeroot -uc -us
160 
+    cd ..
161 
+    </pre>
162 
+    Now you can install the new package:
163 
+    <pre>
164 
+    sudo dpkg -i tor_*.deb
165 
+    </pre>
166 
+    </p>
167 
+
168 
+    <p>
169 
+    Now Tor is installed and running. Move on to <a href="<page
170 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Tor on Linux/Unix"
171 
+    instructions.
172 
+    </p>
173 
+
174 
+    <hr />
175 
+
176 
+    <p>If you have suggestions for improving this document, please <a
177 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
178 
+  </div>
179 
+  <!-- END MAINCOL -->
180 
+  <div id = "sidecol">
181 
+#include "side.wmi"
182 
+#include "info.wmi"
183 
+  </div>
184 
+  <!-- END SIDECOL -->
185 
+</div>
186 
+<!-- END CONTENT -->
187 
+#include <foot.wmi>
docs/en/documentation.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,289 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22359 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor: Documentation" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation</a>
10 
+  </div>
11 
+  <div id="maincol">
12 
+    <a id="RunningTor"></a>
13 
+    <h1><a class="anchor" href="#RunningTor">Running Tor</a></h1>
14 
+    <ul>
15 
+    <li><a href="<page docs/tor-doc-windows>">Installing Tor
16 
+    on Win32</a></li>
17 
+    <li><a href="<page docs/tor-doc-osx>">Installing Tor on
18 
+    Mac OS X</a></li>
19 
+    <li><a href="<page docs/tor-doc-unix>">Installing Tor on
20 
+    Linux/BSD/Unix</a></li>
21 
+    <li><a href="<page projects/torbutton>">Installing
22 
+    Torbutton for Tor</a></li>
23 
+    <li><a href="<page docs/tor-doc-relay>">Configuring a
24 
+    Tor relay</a></li>
25 
+    <li><a href="<page docs/tor-hidden-service>">Configuring
26 
+    a Tor hidden service</a></li>
27 
+    </ul>
28 
+
29 
+    <a id="Support"></a>
30 
+    <a id="UpToSpeed"></a>
31 
+    <h1><a class="anchor" href="#UpToSpeed">Getting up to speed on Tor's past,
32 
+    present, and future</a></h1>
33 
+
34 
+    <ol>
35 
+    <li>
36 
+    First, read the <a href="<page about/overview>">overview page</a> to get a
37 
+    basic idea of how Tor works, what it's for, and who uses it.
38 
+    </li>
39 
+
40 
+    <li>
41 
+    <a href="<page download/download>">Install the Tor bundle</a> and try it out.
42 
+    Make sure you've got Firefox installed first, and be sure to read the
43 
+    <a href="<page download/download>#Warning">list of warnings</a> about ways you
44 
+    can screw up your anonymity.
45 
+    </li>
46 
+
47 
+    <li>
48 
+    Our <a
49 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">FAQ</a>
50 
+    covers all sorts of topics, including questions about setting up a client
51 
+    or relay, concerns about anonymity attacks, why we didn't build Tor in
52 
+    other ways, etc.
53 
+    There's a separate <a href="<page docs/faq-abuse>">Abuse FAQ</a> to answer
54 
+    common questions from or for relay operators.
55 
+    The <a href="<page eff/tor-legal-faq>">Tor Legal FAQ</a> is written by
56 
+    EFF lawyers, and aims to give you an overview of some of the legal issues
57 
+    that arise from the Tor project in the US.
58 
+    </li>
59 
+
60 
+    <li>The <a href="<page docs/tor-manual>">manual</a>
61 
+    lists all the possible entries you can put in your <a
62 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc
63 
+    file</a>. We also provide a <a href="<page docs/tor-manual-dev>">manual for
64 
+    the development version of Tor</a>.</li>
65 
+
66 
+    <li>If you have questions, we have an IRC channel (for users, relay
67 
+    operators, and developers)
68 
+    at <a href="irc://irc.oftc.net/tor">#tor on irc.oftc.net</a>. If
69 
+    you have a bug, especially a crash bug, read <a
70 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#MyTorkeepscrashing.">how
71 
+    to report a Tor bug</a> first and then tell us as much information
72 
+    about it as you can in
73 
+    <a href="https://bugs.torproject.org/tor">our bugtracker</a>.
74 
+    (If your bug is
75 
+    with Polipo, your browser, or some other application, please don't put
76 
+    it in our bugtracker.) The
77 
+    <a href="#MailingLists">or-talk mailing list</a> can also be useful.
78 
+    </li>
79 
+
80 
+    <li>
81 
+    <a href="https://blog.torproject.org/">Tor has a blog now</a>.
82 
+    We try to keep it updated every week or two with the latest news.
83 
+    </li>
84 
+
85 
+    <li>
86 
+    Download and watch Roger's overview talk from What The Hack (<a
87 
+    href="http://freehaven.net/~arma/wth-anonymous-communication-58.mp4">video</a>,
88 
+    <a href="http://freehaven.net/~arma/wth1.pdf">slides</a>, <a
89 
+    href="http://wiki.whatthehack.org/index.php/Anonymous_communication_for_the_United_States_Department_of_Defense...and_you">abstract</a>).
90 
+    This talk was given in July 2005, back when we were funded by EFF and back
91 
+    when the network was quite small, but it still provides good background
92 
+    on how Tor works and what it's for.
93 
+    </li>
94 
+
95 
+    <li>
96 
+    Look through our <a href="#DesignDoc">Design
97 
+    Documents</a>. Notice that we have RFC-style specs to tell you exactly
98 
+    how Tor is built.
99 
+    </li>
100 
+
101 
+    <li>
102 
+    There's a skeletal <a
103 
+    href="https://svn.torproject.org/svn/projects/roadmaps/2008-12-19-roadmap-full.pdf">list
104 
+    of items we'd like to tackle in the future</a>. Alas, many of those
105 
+    items need to be fleshed out more before they'll make sense to people
106 
+    who aren't Tor developers, but you can still get a general sense of
107 
+    what issues need to be resolved next.
108 
+    </li>
109 
+
110 
+    <li>
111 
+    Download and watch Nick's "Technical changes since 2004" talk from
112 
+    Defcon in July 2007 (<a
113 
+    href="http://freehaven.net/~arma/Defcon15-Mathewson-Technical_Changes_since_you_Last_Heard_about_Tor.mp4">video</a>, <a
114 
+    href="http://freehaven.net/~nickm/slides/Defcon07/TorChanges.pdf">slides</a>),
115 
+    Roger's "blocking-resistance
116 
+    and circumvention" talk from 23C3 in December 2006 (<a
117 
+    href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
118 
+    <a href="http://freehaven.net/~arma/slides-23c3.pdf">slides</a>,
119 
+    <a href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstract</a>,
120 
+    <a href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">design paper</a>),
121 
+    and Roger's "Current events in 2007" talk from 24C3 in December
122 
+    2007 (<a
123 
+    href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
124 
+    <a href="http://freehaven.net/~arma/slides-24c3.pdf">slides</a>,
125 
+    <a href="http://events.ccc.de/congress/2007/Fahrplan/events/2325.en.html">abstract</a>).
126 
+    We also have the What The Hack tutorial on hidden services (<a
127 
+    href="http://freehaven.net/~arma/wth_tor_hidden_services.mp4">video</a>,
128 
+    <a href="http://freehaven.net/~arma/wth3.pdf">slides</a>).
129 
+    </li>
130 
+
131 
+    <li>
132 
+    See Mike's "Securing the Tor network" talk from Defcon in July 2007
133 
+    (<a href="http://freehaven.net/~arma/Defcon15-Mike_Perry-Securing_the_Tor_Network.mp4">video</a>,
134 
+     <a href="http://freehaven.net/~arma/SecuringTheTorNetwork.pdf">slides</a>).
135 
+    It describes common ways to attack networks like Tor and how we try
136 
+    to defend against them, and it introduces the <a
137 
+    href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>
138 
+    script collection.
139 
+    </li>
140 
+
141 
+    <li>
142 
+    Learn about the <a
143 
+    href="<gitblob>doc/spec/proposals/001-process.txt">Tor
144 
+    proposal process for changing our design</a>, and look over the <a
145 
+    href="<gittree>doc/spec/proposals">existing proposals</a>.
146 
+    </li>
147 
+
148 
+    <li>
149 
+    Our <a href="<gitblob>doc/TODO">developer TODO file</a> starts with a
150 
+    timeline for external promises &mdash; things <a href="<page about/sponsors>">our
151 
+    sponsors</a> have paid to see done. It also lists many other tasks
152 
+    and topics we'd like to tackle next.
153 
+    </li>
154 
+
155 
+    <li>
156 
+    Once you're up to speed, things will continue to change surprisingly fast.
157 
+    The <a href="#MailingLists">or-dev mailing list</a> is where the complex
158 
+    discussion happens, and the #tor IRC channel
159 
+    is where the less complex discussion happens.
160 
+    </li>
161 
+
162 
+    </ol>
163 
+
164 
+    <a id="MailingLists"></a>
165 
+    <h1><a class="anchor" href="#MailingLists">Mailing List Information</a></h1>
166 
+    <ul>
167 
+    <li>The <a href="http://archives.seul.org/or/announce/">or-announce
168 
+    mailing list</a> is a low volume list for announcements of new releases
169 
+    and critical security updates. Everybody should be on this list.
170 
+    There is also an
171 
+    <a href="http://rss.gmane.org/gmane.network.onion-routing.announce">RSS
172 
+    feed</a> of or-announce at <a href="http://gmane.org">gmane.org</a>.</li>
173 
+    <li>The <a href="http://archives.seul.org/or/talk/">or-talk list</a>
174 
+    is where a lot of discussion happens, and is where we send notifications
175 
+    of prerelease versions and release candidates.</li>
176 
+    <li>The <a href="http://archives.seul.org/tor/relays/">tor-relays list</a>
177 
+    is where discussions about running, configuring, and handling your tor
178 
+    relay happen.  If you currently run a relay, or are thinking about doing
179 
+    so, this is the list for you.</li>
180 
+    <li>The <a href="http://archives.seul.org/or/dev/">or-dev list</a>
181 
+    is for posting by developers only, and is very low traffic.</li>
182 
+    <li>A list for <a href="http://archives.seul.org/tor/mirrors/">mirror
183 
+    operators</a> for new website mirrors, and supporting <a href="<page
184 
+    getinvolved/mirrors>">current website mirrors</a>.</li>
185 
+    <li>A list for <a href="http://archives.seul.org/or/cvs/">svn and git
186 
+    commits</a> may be interesting for developers.</li>
187 
+    <li>An automated list for <a href="http://archives.seul.org/tor/bugs/">bug
188 
+    reports from trac</a> may be interesting for users and developers.</li>
189 
+    </ul>
190 
+
191 
+    <a id="DesignDoc"></a>
192 
+    <h1><a class="anchor" href="#DesignDoc">Design Documents</a></h1>
193 
+    <ul>
194 
+    <li>The <b>design document</b> (published at Usenix Security 2004)
195 
+    gives our justifications and security analysis for the Tor design:
196 
+    <a href="https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf">PDF</a> and
197 
+    <a href="https://svn.torproject.org/svn/projects/design-paper/tor-design.html">HTML</a>
198 
+    versions available.</li>
199 
+    <li>Our follow-up paper on <b>challenges in low-latency anonymity</b>
200 
+    (still in draft form) details more recent experiences and directions:
201 
+    <a href="https://svn.torproject.org/svn/projects/design-paper/challenges.pdf">PDF
202 
+    draft</a>.</li>
203 
+    <li>Our paper at WEIS 2006 &mdash; <b>Anonymity Loves Company:
204 
+    Usability and the Network Effect</b> &mdash; explains why usability in
205 
+    anonymity systems matters for their security: <a
206 
+    href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
207 
+    <li>Our preliminary design to make it harder for large firewalls to
208 
+    prevent access to the Tor network is described in
209 
+    <b>design of a blocking-resistant anonymity system</b>:
210 
+    <a href="https://svn.torproject.org/svn/projects/design-paper/blocking.pdf">PDF draft</a> and
211 
+    <a href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">HTML draft</a>.
212 
+    Want to <a href="<page getinvolved/volunteer>#Coding">help us build it</a>?</li>
213 
+    <li>The <b>specifications</b> aim to give
214 
+    developers enough information to build a compatible version of Tor:
215 
+    <ul>
216 
+    <li><a href="<gitblob>doc/spec/tor-spec.txt">Main Tor specification</a></li>
217 
+    <li><a href="<gitblob>doc/spec/dir-spec.txt">Tor
218 
+    version 3 directory server specification</a> (and older <a
219 
+    href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> and <a
220 
+    href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> directory
221 
+    specifications)</li>
222 
+    <li><a href="<gitblob>doc/spec/control-spec.txt">Tor control protocol
223 
+    specification</a></li>
224 
+    <li><a href="<gitblob>doc/spec/rend-spec.txt">Tor rendezvous
225 
+    specification</a></li>
226 
+    <li><a href="<gitblob>doc/spec/path-spec.txt">Tor path selection
227 
+    specification</a></li>
228 
+    <li><a href="<gitblob>doc/spec/address-spec.txt">Special hostnames in
229 
+    Tor</a></li>
230 
+    <li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor's SOCKS support
231 
+    and extensions</a></li>
232 
+    <li><a href="<gitblob>doc/spec/version-spec.txt">How Tor version numbers
233 
+    work</a></li>
234 
+    <li><a href="<gitblob>doc/spec/proposals">In-progress drafts of
235 
+    new specifications and proposed changes</a></li>
236 
+    </ul></li>
237 
+
238 
+    </ul>
239 
+
240 
+    <a id="NeatLinks"></a>
241 
+    <h1><a class="anchor" href="#NeatLinks">Neat Links</a></h1>
242 
+    <ul>
243 
+    <li>The <a href="https://trac.torproject.org/projects/tor/wiki">Tor
244 
+    wiki</a> provides a plethora of helpful contributions from Tor
245 
+    users. Check it out!</li>
246 
+    <li><a
247 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">A
248 
+    list of supporting programs you might want to use in association with
249 
+    Tor</a>.</li>
250 
+    <li><a href="https://check.torproject.org/">The
251 
+    Tor detector</a> or <a href="http://torcheck.xenobite.eu/">the other
252 
+    Tor detector</a> try to guess if you're using Tor or not.</li>
253 
+    <li>Check out one of the Tor status pages, such as <a
254 
+    href="http://torstatus.blutmagie.de/">blutmagie's</a>, or <a
255 
+    href="http://trunk.torstatus.kgprog.com/index.php">kgprog's</a>, or
256 
+    Xenobite's <a href="https://torstat.xenobite.eu/">Tor node status</a> page.
257 
+    Remember that these lists may not be as accurate as what your Tor
258 
+    client uses, because your client fetches its own directory information and
259 
+    examines it locally.</li>
260 
+    <li>Read <a
261 
+    href="http://freehaven.net/anonbib/topic.html#Anonymous_20communication">these
262 
+    papers</a> (especially the ones in boxes) to get up to speed on the field
263 
+    of anonymous communication systems.</li>
264 
+    </ul>
265 
+
266 
+    <a id="Developers"></a>
267 
+    <h1><a class="anchor" href="#Developers">For Developers</a></h1>
268 
+      Browse the Tor <b>source repository</b>:
269 
+      <ul>
270 
+        <li><a href="<gitrepo>">Browse the repository's source tree directly</a></li>
271 
+        <li>Git and SVN access:
272 
+          <ul>
273 
+            <li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>
274 
+            <li>The development branch is <kbd>master</kbd>.  The active maintenance branches are <kbd>maint-0.2.0</kbd> and <kbd>maint-0.2.1</kbd>.</li>
275 
+            <li><kbd>svn checkout https://svn.torproject.org/svn/website/trunk website</kbd></li>
276 
+          </ul>
277 
+        </li>
278 
+        <li><a href="https://gitweb.torproject.org//githax.git?a=blob;f=doc/Howto.txt;hb=HEAD">Basic instructions for using Git to contribute to Tor software.</a></li>
279 
+      </ul>
280 
+  </div>
281 
+  <!-- END MAINCOL -->
282 
+  <div id = "sidecol">
283 
+#include "side.wmi"
284 
+#include "info.wmi"
285 
+  </div>
286 
+  <!-- END SIDECOL -->
287 
+</div>
288 
+<!-- END CONTENT -->
289 
+#include <foot.wmi>
docs/en/faq-abuse.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,388 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Abuse FAQ" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/faq-abuse>">Abuse FAQ</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+    <h1>Abuse FAQ</h1>
15 
+    #<!-- BEGIN SIDEBAR -->
16 
+    #<div class="sidebar-left">
17 
+    #<h3>Questions</h3>
18 
+    #<ul>
19 
+    #<li><a href="<page docs/faq-abuse>#WhatAboutCriminals">Doesn't Tor enable criminals to do bad things?</a></li>
20 
+    #<li><a href="<page docs/faq-abuse>#DDoS">What about distributed denial of service attacks?</a></li>
21 
+    #<li><a href="<page docs/faq-abuse>#WhatAboutSpammers">What about spammers?</a></li>
22 
+    #<li><a href="<page docs/faq-abuse>#HowMuchAbuse">Does Tor get much abuse?</a></li>
23 
+    #<li><a href="<page docs/faq-abuse>#TypicalAbuses">So what should I expect if I run an exit relay?</a></li>
24 
+    #<li><a href="<page docs/faq-abuse>#IrcBans">Tor is banned from the IRC network I want to use.</a></li>
25 
+    #<li><a href="<page docs/faq-abuse>#SMTPBans">Your nodes are banned from the mail server I want to use.</a></li>
26 
+    #<li><a href="<page docs/faq-abuse>#Bans">I want to ban the Tor network from my service.</a></li>
27 
+    #<li><a href="<page docs/faq-abuse>#TracingUsers">I have a compelling reason to trace a Tor user. Can you help?</a></li>
28 
+    #<li><a href="<page docs/faq-abuse>#RemoveContent">I want some content removed from a .onion address.</a></li>
29 
+    #<li><a href="<page docs/faq-abuse>#LegalQuestions">I have legal questions about Tor abuse.</a></li>
30 
+    #</ul>
31 
+    #</div>
32 
+    #<!-- END SIDEBAR -->
33 
+    #<hr />
34 
+
35 
+    <a id="WhatAboutCriminals"></a>
36 
+    <h3><a class="anchor" href="#WhatAboutCriminals">Doesn't Tor enable criminals to do bad things?</a></h3>
37 
+
38 
+    <p>Criminals can already do bad things. Since they're willing to
39 
+    break laws, they already have lots of options available that provide
40 
+    <em>better</em> privacy than Tor provides. They can steal cell phones,
41 
+    use them, and throw them in a ditch; they can crack into computers
42 
+    in Korea or Brazil and use them to launch abusive activities; they
43 
+    can use spyware, viruses, and other techniques to take control of
44 
+    literally millions of Windows machines around the world. </p>
45 
+
46 
+    <p>Tor aims to provide protection for ordinary people who want to follow
47 
+    the law. Only criminals have privacy right now, and we need to fix that. </p>
48 
+
49 
+    <p>Some advocates of anonymity explain that it's just a tradeoff &mdash;
50 
+    accepting the bad uses for the good ones &mdash; but there's more to it
51 
+    than that.
52 
+    Criminals and other bad people have the motivation to learn how to
53 
+    get good anonymity, and many have the motivation to pay well to achieve
54 
+    it. Being able to steal and reuse the identities of innocent victims
55 
+    (identify theft) makes it even easier. Normal people, on the other hand,
56 
+    don't have the time or money to spend figuring out how to get
57 
+    privacy online. This is the worst of all possible worlds. </p>
58 
+
59 
+    <p>So yes, criminals could in theory use Tor, but they already have
60 
+    better options, and it seems unlikely that taking Tor away from the
61 
+    world will stop them from doing their bad things. At the same time, Tor
62 
+    and other privacy measures can <em>fight</em> identity theft, physical
63 
+    crimes like stalking, and so on. </p>
64 
+
65 
+    <!--
66 
+    <a id="Pervasive"></a>
67 
+    <h3><a class="anchor" href="#Pervasive">If the whole world starts using
68 
+    Tor, won't civilization collapse?</a></h3>
69 
+    -->
70 
+
71 
+    <a id="DDoS"></a>
72 
+    <h3><a class="anchor" href="#DDoS">What about distributed denial of service attacks?</a></h3>
73 
+
74 
+    <p>Distributed denial of service (DDoS) attacks typically rely on having a group
75 
+    of thousands of computers all sending floods of traffic to a victim. Since
76 
+    the goal is to overpower the bandwidth of the victim, they typically send
77 
+    UDP packets since those don't require handshakes or coordination. </p>
78 
+
79 
+    <p>But because Tor only transports correctly formed TCP streams, not
80 
+    all IP packets, you cannot send UDP packets over Tor. (You can't do
81 
+    specialized forms of this attack like SYN flooding either.) So ordinary
82 
+    DDoS attacks are not possible over Tor. Tor also doesn't allow bandwidth
83 
+    amplification attacks against external sites: you need to send in a byte
84 
+    for every byte that the Tor network will send to your destination. So
85 
+    in general, attackers who control enough bandwidth to launch an effective
86 
+    DDoS attack can do it just fine without Tor. </p>
87 
+
88 
+    <a id="WhatAboutSpammers"></a>
89 
+    <h3><a class="anchor" href="#WhatAboutSpammers">What about spammers?</a></h3>
90 
+
91 
+    <p>First of all, the default Tor exit policy rejects all outgoing
92 
+    port 25 (SMTP) traffic. So sending spam mail through Tor isn't going to
93 
+    work by default. It's possible that some relay operators will enable
94 
+    port 25 on their particular exit node, in which case that computer will
95 
+    allow outgoing mails; but that individual could just set up an open mail
96 
+    relay too, independent of Tor. In short, Tor isn't useful for spamming,
97 
+    because nearly all Tor relays refuse to deliver the mail. </p>
98 
+
99 
+    <p>Of course, it's not all about delivering the mail. Spammers can use
100 
+    Tor to connect to open HTTP proxies (and from there to SMTP servers); to
101 
+    connect to badly written mail-sending CGI scripts; and to control their
102 
+    botnets &mdash; that is, to covertly communicate with armies of
103 
+    compromised computers that deliver the spam.
104 
+    </p>
105 
+
106 
+    <p>
107 
+    This is a shame, but notice that spammers are already doing great
108 
+    without Tor. Also, remember that many of their more subtle communication
109 
+    mechanisms (like spoofed UDP packets) can't be used over Tor, because
110 
+    it only transports correctly-formed TCP connections.
111 
+    </p>
112 
+
113 
+    <a id="ExitPolicies"></a>
114 
+    <h3><a class="anchor" href="#ExitPolicies">How do Tor exit policies work?</a></h3>
115 
+
116 
+    <p>
117 
+    <a href="<page docs/faq>#ExitPolicies">Moved to the new FAQ page</a>
118 
+    </p>
119 
+
120 
+    <a id="HowMuchAbuse"></a>
121 
+    <h3><a class="anchor" href="#HowMuchAbuse">Does Tor get much abuse?</a></h3>
122 
+
123 
+    <p>Not much, in the grand scheme of things. We've been running the network
124 
+    since October 2003, and it's only generated a handful of complaints. Of
125 
+    course, like all privacy-oriented networks on the net, we attract our
126 
+    share of jerks. Tor's exit policies help separate the role of "willing
127 
+    to donate resources to the network" from the role of "willing to deal
128 
+    with exit abuse complaints," so we hope our network is more sustainable
129 
+    than past attempts at anonymity networks. </p>
130 
+
131 
+    <p>Since Tor has
132 
+    <a href="<page about/overview>">many good uses as
133 
+    well</a>, we feel that we're doing pretty well at striking a balance
134 
+    currently. </p>
135 
+
136 
+    <a id="TypicalAbuses"></a>
137 
+    <h3><a class="anchor" href="#TypicalAbuses">So what should I expect if I run an exit relay?</a></h3>
138 
+
139 
+    <p>If you run a Tor relay that allows exit connections (such as the
140 
+    default exit policy), it's probably safe to say that you will eventually
141 
+    hear from somebody. Abuse
142 
+    complaints may come in a variety of forms. For example: </p>
143 
+    <ul>
144 
+    <li>Somebody connects to Hotmail, and sends a ransom note to a
145 
+    company. The
146 
+    FBI sends you a polite email, you explain that you run a Tor relay,
147 
+    and they say "oh well" and leave you alone. [Port 80]</li>
148 
+    <li>Somebody tries to get you shut down by using Tor to connect to Google
149 
+    groups and post spam to Usenet, and then sends an angry mail to
150 
+    your ISP about how you're destroying the world. [Port 80]</li>
151 
+    <li>Somebody connects to an IRC network and makes a nuisance of
152 
+    himself. Your ISP gets polite mail about how your computer has been
153 
+    compromised; and/or your computer gets DDoSed. [Port 6667]</li>
154 
+    <li>Somebody uses Tor to download a Vin Diesel movie, and
155 
+    your ISP gets a DMCA takedown notice. See EFF's
156 
+    <a href="<page eff/tor-dmca-response>">Tor DMCA Response
157 
+    Template</a>, which explains why your ISP can probably ignore
158 
+    the notice without any liability. [Arbitrary ports]</li>
159 
+    </ul>
160 
+
161 
+    <p>You might also find that your Tor relay's IP is blocked from accessing
162 
+    some Internet sites/services. This might happen regardless of your exit
163 
+    policy, because some groups don't seem to know or care that Tor has
164 
+    exit policies. (If you have a spare IP not used for other activities,
165 
+    you might consider running your Tor relay on it.) For example, </p>
166 
+
167 
+    <ul>
168 
+    <li>Because of a few cases of anonymous jerks messing with its web
169 
+    pages, Wikipedia is currently blocking many Tor relay IPs from writing
170 
+    (reading still works). We're talking to Wikipedia about how they might
171 
+    control abuse while still providing access to anonymous contributors,
172 
+    who often have hot news or inside info on a topic but don't want to risk
173 
+    revealing their identities when publishing it (or don't want to reveal
174 
+    to local observers that they're accessing Wikipedia). Slashdot is also
175 
+    in the same boat.</li>
176 
+
177 
+    <li>SORBS is putting some Tor relay IPs on their email
178 
+    blacklist as well. They do this because they passively detect whether your
179 
+    relay connects to certain IRC networks, and they conclude from this that
180 
+    your relay is capable of spamming. We tried to work with
181 
+    them to teach them that not all software works this way,
182 
+    but we have given up. We recommend you avoid them, and <a
183 
+    href="http://paulgraham.com/spamhausblacklist.html">teach your friends
184 
+    (if they use them) to avoid abusive blacklists too</a>.</li>
185 
+
186 
+    </ul>
187 
+
188 
+    <a id="IrcBans"></a>
189 
+    <h3><a class="anchor" href="#IrcBans">Tor is banned from the IRC network I want to use.</a></h3>
190 
+
191 
+    <p>Sometimes jerks make use of Tor to troll IRC channels. This abuse
192 
+    results in IP-specific temporary bans ("klines" in IRC lingo), as the
193 
+    network operators try to keep the troll off of their network. </p>
194 
+
195 
+    <p>This response underscores a fundamental flaw in IRC's security model:
196 
+    they assume that IP addresses equate to humans, and by banning the
197 
+    IP address they can ban the human. In reality this is not the case &mdash;
198 
+    many such trolls routinely make use of the literally millions of open
199 
+    proxies and compromised computers around the Internet. The IRC networks
200 
+    are fighting a losing battle of trying to block all these nodes,
201 
+    and an entire cottage industry of blacklists and counter-trolls has
202 
+    sprung up based on this flawed security model (not unlike the antivirus
203 
+    industry). The Tor network is just a drop in the bucket here. </p>
204 
+
205 
+    <p>On the other hand, from the viewpoint of IRC server operators, security
206 
+    is not an all-or-nothing thing.  By responding quickly to trolls or
207 
+    any other social attack, it may be possible to make the attack scenario
208 
+    less attractive to the attacker.  And most individual IP addresses do
209 
+    equate to individual humans, on any given IRC network at any given time.
210 
+    The exceptions include NAT gateways which may be allocated access as
211 
+    special cases. While it's a losing battle to try to stop the use of open
212 
+    proxies, it's not generally a losing battle to keep klining a single
213 
+    ill-behaved IRC user until that user gets bored and goes away. </p>
214 
+
215 
+    <p>But the real answer is to implement application-level auth systems,
216 
+    to let in well-behaving users and keep out badly-behaving users. This
217 
+    needs to be based on some property of the human (such as a password he
218 
+    knows), not some property of the way his packets are transported. </p>
219 
+
220 
+    <p>Of course, not all IRC networks are trying to ban Tor nodes. After
221 
+    all, quite a few people use Tor to IRC in privacy in order to carry
222 
+    on legitimate communications without tying them to their real-world
223 
+    identity. Each IRC network needs to decide for itself if blocking a few
224 
+    more of the millions of IPs that bad people can use is worth losing the
225 
+    contributions from the well-behaved Tor users. </p>
226 
+
227 
+    <p>If you're being blocked, have a discussion with the network operators
228 
+    and explain the issues to them. They may not be aware of the existence of
229 
+    Tor at all, or they may not be aware that the hostnames they're klining
230 
+    are Tor exit nodes.  If you explain the problem, and they conclude that
231 
+    Tor ought to be blocked, you may want to consider moving to a network that
232 
+    is more open to free speech.  Maybe inviting them to #tor on irc.oftc.net
233 
+    will help show them that we are not all evil people. </p>
234 
+
235 
+    <p>Finally, if you become aware of an IRC network that seems to be
236 
+    blocking Tor, or a single Tor exit node, please put that information on <a
237 
+    href="https://wiki.torproject.org/wiki/TheOnionRouter/BlockingIrc">The Tor
238 
+    IRC block tracker</a>
239 
+    so that others can share.  At least one IRC network consults that page
240 
+    to unblock exit nodes that have been blocked inadvertently. </p>
241 
+
242 
+    <a id="SMTPBans"></a>
243 
+    <h3><a class="anchor" href="#SMTPBans">Your nodes are banned from the mail server I want to use.</a></h3>
244 
+
245 
+    <p>Even though <a href="#WhatAboutSpammers">Tor isn't useful for
246 
+    spamming</a>, some over-zealous blacklisters seem to think that all
247 
+    open networks like Tor are evil &mdash; they attempt to strong-arm network
248 
+    administrators on policy, service, and routing issues, and then extract
249 
+    ransoms from victims. </p>
250 
+
251 
+    <p>If your server administrators decide to make use of these
252 
+    blacklists to refuse incoming mail, you should have a conversation with
253 
+    them and explain about Tor and Tor's exit policies. </p>
254 
+
255 
+    <a id="Bans"></a>
256 
+    <h3><a class="anchor" href="#Bans">I want to ban the Tor network from my service.</a></h3>
257 
+
258 
+    <p>We're sorry to hear that. There are some situations where it makes
259 
+    sense to block anonymous users for an Internet service. But in many
260 
+    cases, there are easier solutions that can solve your problem while
261 
+    still allowing users to access your website securely.</p>
262 
+
263 
+    <p>First, ask yourself if there's a way to do application-level decisions
264 
+    to separate the legitimate users from the jerks. For example, you might
265 
+    have certain areas of the site, or certain privileges like posting,
266 
+    available only to people who are registered. It's easy to build an
267 
+    up-to-date list of Tor IP addresses that allow connections to your
268 
+    service, so you could set up this distinction only for Tor users. This
269 
+    way you can have multi-tiered access and not have to ban every aspect
270 
+    of your service. </p>
271 
+
272 
+    <p>For example, the <a
273 
+    href="http://freenode.net/policy.shtml#tor">Freenode IRC network</a>
274 
+    had a problem with a coordinated group of abusers joining channels and
275 
+    subtly taking over the conversation; but when they labelled all users
276 
+    coming from Tor nodes as "anonymous users," removing the ability of the
277 
+    abusers to blend in, the abusers moved back to using their open proxies
278 
+    and bot networks. </p>
279 
+
280 
+    <p>Second, consider that hundreds of thousands of
281 
+    people use Tor every day simply for
282 
+    good data hygiene &mdash; for example, to protect against data-gathering
283 
+    advertising companies while going about their normal activities. Others
284 
+    use Tor because it's their only way to get past restrictive local
285 
+    firewalls. Some Tor users may be legitimately connecting
286 
+    to your service right now to carry on normal activities. You need to
287 
+    decide whether banning the Tor network is worth losing the contributions
288 
+    of these users, as well as potential future legitimate users. (Often
289 
+    people don't have a good measure of how many polite Tor users are
290 
+    connecting to their service &mdash; you never notice them until there's
291 
+    an impolite one.)</p>
292 
+
293 
+    <p>At this point, you should also ask yourself what you do about other
294 
+    services that aggregate many users behind a few IP addresses. Tor is
295 
+    not so different from AOL in this respect.</p>
296 
+
297 
+    <p>Lastly, please remember that Tor relays have <a
298 
+    href="<page docs/faq>#ExitPolicies">individual exit policies</a>. Many Tor relays do
299 
+    not allow exiting connections at all. Many of those that do allow some
300 
+    exit connections might already disallow connections to
301 
+    your service. When you go about banning nodes, you should parse the
302 
+    exit policies and only block the ones that allow these connections;
303 
+    and you should keep in mind that exit policies can change (as well as
304 
+    the overall list of nodes in the network).</p>
305 
+
306 
+    <p>If you really want to do this, we provide a
307 
+    <a href="https://check.torproject.org/cgi-bin/TorBulkExitList.py">Tor
308 
+    exit relay list</a> or a
309 
+    <a href="<page projects/tordnsel>">DNS-based list you can query</a>.
310 
+    </p>
311 
+
312 
+    <p>
313 
+    (Some system administrators block ranges of IP addresses because of
314 
+    official policy or some abuse pattern, but some have also asked about
315 
+    whitelisting Tor exit relays because they want to permit access to their
316 
+    systems only using Tor. These scripts are usable for whitelisting as well.)
317 
+    </p>
318 
+
319 
+    <a id="TracingUsers"></a>
320 
+    <h3><a class="anchor" href="#TracingUsers">I have a compelling reason to trace a Tor user. Can you help?</a></h3>
321 
+
322 
+    <p>
323 
+    There is nothing the Tor developers can do to trace Tor users. The same
324 
+    protections that keep bad people from breaking Tor's anonymity also
325 
+    prevent us from figuring out what's going on.
326 
+    </p>
327 
+
328 
+    <p>
329 
+    Some fans have suggested that we redesign Tor to include a <a
330 
+    href="<page docs/faq>#Backdoor">backdoor</a>.
331 
+    There are two problems with this idea. First, it technically weakens the
332 
+    system too far. Having a central way to link users to their activities
333 
+    is a gaping hole for all sorts of attackers; and the policy mechanisms
334 
+    needed to ensure correct handling of this responsibility are enormous
335 
+    and unsolved. Second, the bad people <a href="#WhatAboutCriminals">aren't
336 
+    going to get caught by this anyway</a>, since they will use other means
337 
+    to ensure their anonymity (identity theft, compromising computers and
338 
+    using them as bounce points, etc).
339 
+    </p>
340 
+
341 
+    <p>
342 
+    But remember that this doesn't mean that Tor is invulnerable. Traditional
343 
+    police techniques can still be very effective against Tor, such as
344 
+    interviewing suspects, surveillance and keyboard taps, writing style
345 
+    analysis, sting operations, and other physical investigations.
346 
+    </p>
347 
+
348 
+    <a id="RemoveContent"></a>
349 
+    <h3><a class="anchor" href="#RemoveContent">I want some content removed from a .onion address.</a></h3>
350 
+    <p>The Tor Project does not host, control, nor have the ability to
351 
+    discover the owner or location of a .onion address.  The .onion address is
352 
+    an address from <a href="<page docs/hidden-services>">a hidden
353 
+    service</a>.  The name you see ending in .onion is a hidden service descriptor.
354 
+    It's an automatically generated name which can be located on any Tor
355 
+    relay or client anywhere on the Internet.  Hidden services are designed
356 
+    to protect both the user and service provider from discovering who they
357 
+    are and where they are from.  The design of hidden services means the
358 
+    owner and location of the .onion site is hidden even from us.</p>
359 
+    <p>But remember that this doesn't mean that hidden services are
360 
+    invulnerable. Traditional police techniques can still be very effective
361 
+    against them, such as interviewing suspects, surveillance and keyboard
362 
+    taps, writing style analysis, sting operations, and other physical
363 
+    investigations.</p>
364 
+    <p>If you have a complaint about child pornography, you may wish to report
365 
+    it to the National Center for Missing and Exploited Children, which serves
366 
+    as a national coordination point for investigation of child pornography:
367 
+    <a href="http://www.missingkids.com/">http://www.missingkids.com/</a>.
368 
+    We do not view links you report.</p>
369 
+
370 
+    <a id="LegalQuestions"></a>
371 
+    <h3><a class="anchor" href="#LegalQuestions">I have legal questions about Tor abuse.</a></h3>
372 
+
373 
+    <p>We're only the developers. We can answer technical questions, but
374 
+    we're not the ones to talk to about legal questions or concerns. </p>
375 
+
376 
+    <p>Please take a look at the
377 
+    <a href="<page eff/tor-legal-faq>">Tor Legal FAQ</a>,
378 
+    and contact EFF directly if you have any further legal questions. </p>
379 
+  </div>
380 
+  <!-- END MAINCOL -->
381 
+  <div id = "sidecol">
382 
+#include "side.wmi"
383 
+#include "info.wmi"
384 
+  </div>
385 
+  <!-- END SIDECOL -->
386 
+</div>
387 
+<!-- END CONTENT -->
388 
+#include <foot.wmi>
docs/en/faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,1152 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: FAQ" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/faq>">FAQ</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+    <h1>Tor FAQ</h1>
15 
+    <hr />
16 
+
17 
+    <p>General questions:</p>
18 
+    <ul>
19 
+    <li><a href="#WhatIsTor">What is Tor?</a></li>
20 
+    <li><a href="#Torisdifferent">How is Tor different from other proxies?</a></li>
21 
+    <li><a href="#CompatibleApplications">What programs can I use with
22 
+    Tor?</a></li>
23 
+    <li><a href="#WhyCalledTor">Why is it called Tor?</a></li>
24 
+    <li><a href="#Backdoor">Is there a backdoor in Tor?</a></li>
25 
+    <li><a href="#DistributingTor">Can I distribute Tor on my magazine's
26 
+    CD?</a></li>
27 
+    <li><a href="#SupportMail">How can I get an answer to my
28 
+    Tor support mail?</a></li>
29 
+    <li><a href="#WhySlow">Why is Tor so slow?</a></li>
30 
+    <li><a href="#Funding">What would The Tor Project do with more
31 
+    funding?</a></li>
32 
+    </ul>
33 
+
34 
+    <p>Compilation and Installation:</p>
35 
+    <ul>
36 
+    <li><a href="#HowUninstallTor">How do I uninstall Tor?</a></li>
37 
+    <li><a href="#PGPSigs">What are these "sig" files on the download
38 
+    page?</a></li>
39 
+    <li><a href="#CompileTorWindows">How do I compile Tor under Windows?</a></li>
40 
+    <li><a href="#VirusFalsePositives">Why does my Tor executable appear to
41 
+    have a virus or spyware?</a></li>
42 
+    <li><a href="#LiveCD">Is there a LiveCD or other bundle that includes Tor?</a></li>
43 
+    </ul>
44 
+
45 
+    <p>Running Tor:</p>
46 
+
47 
+    <p>Running a Tor client:</p>
48 
+    <ul>
49 
+    <li><a href="#ChooseEntryExit">Can I control which nodes (or country) are used for entry/exit?</a></li>
50 
+    </ul>
51 
+
52 
+    <p>Running a Tor relay:</p>
53 
+    <ul>
54 
+    <li><a href="#RelayFlexible">How stable does my relay need to be?</a></li>
55 
+    <li><a href="#ExitPolicies">I'd run a relay, but I don't want to deal
56 
+    with abuse issues.</a></li>
57 
+    <li><a href="#RelayOrBridge">Should I be a normal relay or bridge
58 
+    relay?</a></li>
59 
+    <li><a href="#RelayMemory">Why is my Tor relay using so much memory?</a></li>
60 
+    <li><a href="#WhyNotNamed">Why is my Tor relay not named?</a></li>
61 
+    </ul>
62 
+
63 
+    <p>Running a Tor hidden service:</p>
64 
+
65 
+    <p>Anonymity and Security:</p>
66 
+    <ul>
67 
+    <li><a href="#KeyManagement">Tell me about all the keys Tor uses.</a></li>
68 
+    </ul>
69 
+
70 
+    <p>Alternate designs that we don't do (yet):</p>
71 
+    <ul>
72 
+    <li><a href="#EverybodyARelay">You should make every Tor user be a
73 
+    relay.</a></li>
74 
+    </ul>
75 
+
76 
+    <p>Abuse</p>
77 
+    <ul>
78 
+    <li><a href="#Criminals">Doesn't Tor enable criminals to do bad things?</a></li>
79 
+    <li><a href="#RespondISP">How do I respond to my ISP about my exit
80 
+    relay?</a></li>
81 
+    </ul>
82 
+
83 
+    <p>For other questions not yet on this version of the FAQ, see the <a
84 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">wiki
85 
+    FAQ</a> for now.</p>
86 
+
87 
+    <hr />
88 
+
89 
+    <a id="General"></a>
90 
+
91 
+    <a id="WhatIsTor"></a>
92 
+    <h3><a class="anchor" href="#WhatIsTor">What is Tor?</a></h3>
93 
+
94 
+    <p>
95 
+    The name "Tor" can refer to several different components.
96 
+    </p>
97 
+
98 
+    <p>
99 
+    The Tor software is a program you can run on your computer that helps keep
100 
+    you safe on the Internet. Tor protects you by bouncing your communications
101 
+    around a distributed network of relays run by volunteers all around
102 
+    the world: it prevents somebody watching your Internet connection from
103 
+    learning what sites you visit, and it prevents the sites you visit
104 
+    from learning your physical location. This set of volunteer relays is
105 
+    called the Tor network. You can read more about how Tor works on the <a
106 
+    href="<page about/overview>">overview page</a>.
107 
+    </p>
108 
+
109 
+    <p>
110 
+    The Tor Project is a non-profit (charity) organization that maintains
111 
+    and develops the Tor software.
112 
+    </p>
113 
+
114 
+    <hr />
115 
+
116 
+    <a id="Torisdifferent"></a>
117 
+    <h3><a class="anchor" href="#Torisdifferent">How is Tor different from other proxies?</a></h3>
118 
+    <p>
119 
+    A typical proxy provider sets up a server somewhere on the Internet and allows you to use it to relay your traffic.  This creates a simple, easy to maintain architecture.  The users all enter and leave through the same server.  The provider may charge for use of the proxy, or fund their costs through advertisements on the server.  In the simplest configuration, you don't have to install anything.  You just have to point your browser at their proxy server.  Simple proxy providers are fine solutions if you do not want protections for your privacy and anonymity online and you trust the provider from doing bad things.  Some simple proxy providers use SSL to secure your connection to them.  This may protect you against local eavesdroppers, such as those at a cafe with free wifi Internet.
120 
+    </p>
121 
+    <p>
122 
+    Simple proxy providers also create a single point of failure.  The provider knows who you are and where you browse on the Internet.  They can see your traffic as it passes through their server.  In some cases, they can see your encrypted traffic as they relay it to your banking site or to ecommerce stores.  You have to trust the provider isn't doing any number of things, such as watching your traffic, injecting their own advertisements into your traffic stream, and isn't recording your personal details.
123 
+    </p>
124 
+    <p>
125 
+    Tor passes your traffic through at least 3 different servers before sending it on to the destination.  Tor does not modify, or even know, what you are sending into it.  It merely relays your traffic, completely encrypted through the Tor network and has it pop out somewhere else in the world, completely intact.  The Tor client is required because we assume you trust your local computer.  The Tor client manages the encryption and the path chosen through the network.  The relays located all over the world merely pass encrypted packets between themselves.</p>
126 
+    <p>
127 
+    <dl>
128 
+    <dt>Doesn't the first server see who I am?</dt><dd>Possibly. A bad first of three servers can see encrypted Tor traffic coming from your computer.  It still doesn't know who you are and what you are doing over Tor.  It merely sees "This IP address is using Tor".  Tor is not illegal anywhere in the world, so using Tor by itself is fine.  You are still protected from this node figuring out who you are and where you are going on the Internet.</dd>
129 
+    <dt>Can't the third server see my traffic?</dt><dd>Possibly.  A bad third of three servers can see the traffic you sent into Tor.  It won't know who sent this traffic.  If you're using encryption, such as visiting a bank or e-commerce website, or encrypted mail connections, etc, it will only know the destination.  It won't be able to see the data inside the traffic stream.  You are still protected from this node figuring out who you are and if using encryption, what data you're sending to the destination.</dd>
130 
+    </dl>
131 
+    </p>
132 
+
133 
+    <hr />
134 
+
135 
+    <a id="CompatibleApplications"></a>
136 
+    <h3><a class="anchor" href="#CompatibleApplications">What programs can
137 
+    I use with Tor?</a></h3>
138 
+
139 
+    <p>
140 
+    There are two pieces to "Torifying" a program: connection-level anonymity
141 
+    and application-level anonymity. Connection-level anonymity focuses on
142 
+    making sure the application's Internet connections get sent through Tor.
143 
+    This step is normally done by configuring
144 
+    the program to use your Tor client as a "socks" proxy, but there are
145 
+    other ways to do it too. For application-level anonymity, you need to
146 
+    make sure that the information the application sends out doesn't hurt
147 
+    your privacy. (Even if the connections are being routed through Tor, you
148 
+    still don't want to include sensitive information like your name.) This
149 
+    second step needs to be done on a program-by-program basis, which is
150 
+    why we don't yet recommend very many programs for safe use with Tor.
151 
+    </p>
152 
+
153 
+    <p>
154 
+    Most of our work so far has focused on the Firefox web browser. The
155 
+    bundles on the <a href="<page download/download>">download page</a> automatically
156 
+    install the <a href="<page projects/torbutton>">Torbutton Firefox
157 
+    extension</a> if you have Firefox installed. As of version 1.2.0,
158 
+    Torbutton now takes care of a lot of the connection-level and
159 
+    application-level worries.
160 
+    </p>
161 
+
162 
+    <p>
163 
+    There are plenty of other programs you can use with Tor,
164 
+    but we haven't researched the application-level anonymity
165 
+    issues on them well enough to be able to recommend a safe
166 
+    configuration. Our wiki has a list of instructions for <a
167 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">Torifying
168 
+    specific applications</a>. There's also a <a
169 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">list
170 
+    of applications that help you direct your traffic through Tor</a>.
171 
+    Please add to these lists and help us keep them accurate!
172 
+    </p>
173 
+
174 
+    <hr />
175 
+
176 
+    <a id="WhyCalledTor"></a>
177 
+    <h3><a class="anchor" href="#WhyCalledTor">Why is it called Tor?</a></h3>
178 
+
179 
+    <p>
180 
+    Because Tor is the onion routing network. When we were starting the
181 
+    new next-generation design and implementation of onion routing in
182 
+    2001-2002, we would tell people we were working on onion routing,
183 
+    and they would say "Neat. Which one?" Even if onion routing has
184 
+    become a standard household term, Tor was born out of the actual <a
185 
+    href="http://www.onion-router.net/">onion routing project</a> run by
186 
+    the Naval Research Lab.
187 
+    </p>
188 
+
189 
+    <p>
190 
+    (It's also got a fine translation from German and Turkish.)
191 
+    </p>
192 
+
193 
+    <p>
194 
+    Note: even though it originally came from an acronym, Tor is not spelled
195 
+    "TOR". Only the first letter is capitalized. In fact, we can usually
196 
+    spot people who haven't read any of our website (and have instead learned
197 
+    everything they know about Tor from news articles) by the fact that they
198 
+    spell it wrong.
199 
+    </p>
200 
+
201 
+    <hr />
202 
+
203 
+    <a id="Backdoor"></a>
204 
+    <h3><a class="anchor" href="#Backdoor">Is there a backdoor in Tor?</a></h3>
205 
+
206 
+    <p>
207 
+    There is absolutely no backdoor in Tor. Nobody has asked us to put one
208 
+    in, and we know some smart lawyers who say that it's unlikely that anybody
209 
+    will try to make us add one in our jurisdiction (U.S.). If they do
210 
+    ask us, we will fight them, and (the lawyers say) probably win.
211 
+    </p>
212 
+
213 
+    <p>
214 
+    We think that putting a backdoor in Tor would be tremendously
215 
+    irresponsible to our users, and a bad precedent for security software
216 
+    in general. If we ever put a deliberate backdoor in our security
217 
+    software, it would ruin our professional reputations. Nobody would
218 
+    trust our software ever again &mdash; for excellent reason!
219 
+    </p>
220 
+
221 
+    <p>
222 
+    But that said, there are still plenty of subtle attacks
223 
+    people might try. Somebody might impersonate us, or break into our
224 
+    computers, or something like that. Tor is open source, and you should
225 
+    always check the source (or at least the diffs since the last release)
226 
+    for suspicious things. If we (or the distributors) don't give you
227 
+    source, that's a sure sign something funny might be going on. You
228 
+    should also check the <a href="<page docs/verifying-signatures>">PGP
229 
+    signatures</a> on the releases, to make sure nobody messed with the
230 
+    distribution sites.
231 
+    </p>
232 
+
233 
+    <p>
234 
+    Also, there might be accidental bugs in Tor that could affect your
235 
+    anonymity. We periodically find and fix anonymity-related bugs, so make
236 
+    sure you keep your Tor versions up-to-date.
237 
+    </p>
238 
+
239 
+    <hr />
240 
+
241 
+    <a id="DistributingTor"></a>
242 
+    <h3><a class="anchor" href="#DistributingTor">Can I distribute Tor on
243 
+    my magazine's CD?</a></h3>
244 
+
245 
+    <p>
246 
+    Yes.
247 
+    </p>
248 
+
249 
+    <p>
250 
+    The Tor software is <a href="https://www.fsf.org/">free software</a>. This
251 
+    means we give you the rights to redistribute the Tor software, either
252 
+    modified or unmodified, either for a fee or gratis. You don't have to
253 
+    ask us for specific permission.
254 
+    </p>
255 
+
256 
+    <p>
257 
+    However, if you want to redistribute the Tor software you must follow our
258 
+    <a href="<gitblob>LICENSE">LICENSE</a>.
259 
+    Essentially this means that you need to include our LICENSE file along
260 
+    with whatever part of the Tor software you're distributing.
261 
+    </p>
262 
+
263 
+    <p>
264 
+    Most people who ask us this question don't want to distribute just the
265 
+    Tor software, though. They want to distribute the Tor bundles, which
266 
+    typically include <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>
267 
+    and <a href="<page projects/vidalia>">Vidalia</a>.
268 
+    You will need to follow the licenses for those programs
269 
+    as well. Both of them are distributed under the <a
270 
+    href="https://www.fsf.org/licensing/licenses/gpl.html">GNU General
271 
+    Public License</a>. The simplest way to obey their licenses is to
272 
+    include the source code for these programs everywhere you include
273 
+    the bundles themselves. Look for "source" packages on the <a
274 
+    href="<page projects/vidalia>">Vidalia page</a> and the <a
275 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo
276 
+    download page</a>.
277 
+    </p>
278 
+
279 
+    <p>
280 
+    Also, you should make sure not to confuse your readers about what Tor is,
281 
+    who makes it, and what properties it provides (and doesn't provide). See
282 
+    our <a href="<page docs/trademark-faq>">trademark FAQ</a> for details.
283 
+    </p>
284 
+
285 
+    <p>
286 
+    Lastly, you should realize that we release new versions of the
287 
+    Tor software frequently, and sometimes we make backward incompatible
288 
+    changes. So if you distribute a particular version of the Tor software, it
289 
+    may not be supported &mdash; or even work &mdash; six months later. This
290 
+    is a fact of life for all security software under heavy development.
291 
+    </p>
292 
+
293 
+    <hr />
294 
+
295 
+    <a id="SupportMail"></a>
296 
+    <h3><a class="anchor" href="#SupportMail">How can I get an answer to my
297 
+    Tor support mail?</a></h3>
298 
+
299 
+    <p>
300 
+    Many people send the Tor developers mail privately, or send mail to
301 
+    our internal <a href="<page about/contact>">lists</a>, with questions about their
302 
+    specific setup &mdash; they can't get their firewall working right,
303 
+    they can't configure Polipo correctly, or so on. Sometimes our
304 
+    volunteers can answer these mails, but typically they need to spend
305 
+    most of their time on development tasks that will benefit more people.
306 
+    This is especially true if your question is already covered in the <a
307 
+    href="<page docs/documentation>">documentation</a> or on this FAQ.
308 
+    </p>
309 
+
310 
+    <p>
311 
+    So if we don't answer your mail, first check the <a href="<page
312 
+    docs/documentation>">documentation</a> page, along with this FAQ,
313 
+    to make sure your question isn't already answered.  Then read <a
314 
+    href="http://www.catb.org/~esr/faqs/smart-questions.html">"How to ask
315 
+    questions the smart way"</a>. If this doesn't help you, note that we
316 
+    have <a href="<page docs/documentation>#Support">an IRC channel</a> where you
317 
+    can ask your questions (but if they are still open-ended, ill-formed,
318 
+    or not about Tor, you likely won't get much help there either). Lastly,
319 
+    people on the <a href="<page docs/documentation>#MailingLists">or-talk
320 
+    mailing list</a> may be able to provide some hints for you, if
321 
+    others have experienced your problems too. Be sure to look over <a
322 
+    href="http://archives.seul.org/or/talk/">the archives</a> first.
323 
+    </p>
324 
+
325 
+    <p>
326 
+    Another strategy is to <a href="<page docs/tor-doc-relay>">run a Tor
327 
+    relay for a while</a>, and/or <a href="<page donate/donate>">donate money</a>
328 
+    <a href="<page getinvolved/volunteer>">or time</a> to the effort. We're more likely
329 
+    to pay attention to people who have demonstrated interest and commitment
330 
+    to giving back to the Tor community.
331 
+    </p>
332 
+
333 
+    <p>
334 
+    If you find your answer, please stick around on the IRC channel or the
335 
+    mailing list and answer questions from others.
336 
+    </p>
337 
+
338 
+    <hr />
339 
+
340 
+    <a id="WhySlow"></a>
341 
+    <h3><a class="anchor" href="#WhySlow">Why is Tor so slow?</a></h3>
342 
+
343 
+    <p>
344 
+    There are many reasons why the Tor network is currently slow.
345 
+    </p>
346 
+
347 
+    <p>
348 
+    Before we answer, though, you should realize that Tor is never going to
349 
+    be blazing fast. Your traffic is bouncing through volunteers' computers
350 
+    in various parts of the world, and some bottlenecks and network latency
351 
+    will always be present. You shouldn't expect to see university-style
352 
+    bandwidth through Tor.
353 
+    </p>
354 
+
355 
+    <p>
356 
+    But that doesn't mean that it can't be improved. The current Tor network
357 
+    is quite small compared to the number of people trying to use it, and
358 
+    many of these users don't understand or care that Tor can't currently
359 
+    handle file-sharing traffic load.
360 
+    </p>
361 
+
362 
+    <p>
363 
+    For the much more in-depth answer, see <a
364 
+    href="https://blog.torproject.org/blog/why-tor-is-slow">Roger's blog
365 
+    post on the topic</a>, which includes both a detailed PDF and a video
366 
+    to go with it.
367 
+    </p>
368 
+
369 
+    <p>
370 
+    What can you do to help?
371 
+    </p>
372 
+
373 
+    <ul>
374 
+
375 
+    <li>
376 
+    <a href="<page docs/tor-doc-relay>">Configure your Tor to relay traffic
377 
+    for others</a>. Help make the Tor network large enough that we can handle
378 
+    all the users who want privacy and security on the Internet.
379 
+    </li>
380 
+
381 
+    <li>
382 
+    <a href="<page projects/gui>">Help us make Tor more usable</a>. We
383 
+    especially need people to help make it easier to configure your Tor
384 
+    as a relay. Also, we need help with clear simple documentation to
385 
+    walk people through setting it up.
386 
+    </li>
387 
+
388 
+    <li>
389 
+    There are some bottlenecks in the current Tor network. Help us design
390 
+    experiments to track down and demonstrate where the problems are, and
391 
+    then we can focus better on fixing them.
392 
+    </li>
393 
+
394 
+    <li>
395 
+    There are some steps that individuals
396 
+    can take to improve their Tor performance. <a
397 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/FireFoxTorPerf">You
398 
+    can configure your Firefox to handle Tor better</a>, <a
399 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
400 
+    Polipo with Tor</a>, or you can try <a href="<page download/download>">upgrading
401 
+    to the latest version of Tor</a>.  If this works well, please help by
402 
+    documenting what you did, and letting us know about it.
403 
+    </li>
404 
+
405 
+    <li>
406 
+    Tor needs some architectural changes too. One important change is to
407 
+    start providing <a href="#EverybodyARelay">better service to people who
408 
+    relay traffic</a>. We're working on this, and we'll finish faster if we
409 
+    get to spend more time on it.
410 
+    </li>
411 
+
412 
+    <li>
413 
+    Help do other things so we can do the hard stuff. Please take a moment
414 
+    to figure out what your skills and interests are, and then <a href="<page
415 
+    getinvolved/volunteer>">look at our volunteer page</a>.
416 
+    </li>
417 
+
418 
+    <li>
419 
+    Help find sponsors for Tor. Do you work at a company or government agency
420 
+    that uses Tor or has a use for Internet privacy, e.g. to browse the
421 
+    competition's websites discreetly, or to connect back to the home servers
422 
+    when on the road without revealing affiliations? If your organization has
423 
+    an interest in keeping the Tor network working, please contact them about
424 
+    supporting Tor. Without sponsors, Tor is going to become even slower.
425 
+    </li>
426 
+
427 
+    <li>
428 
+    If you can't help out with any of the above, you can still help out
429 
+    individually by <a href="<page donate/donate>">donating a bit of money to the
430 
+    cause</a>. It adds up!
431 
+    </li>
432 
+
433 
+    </ul>
434 
+
435 
+    <hr />
436 
+
437 
+    <a id="Funding"></a>
438 
+    <h3><a class="anchor" href="#Funding">What would The Tor Project do with
439 
+    more funding?</a></h3>
440 
+
441 
+    <p>
442 
+    We have about 1800 relays right now, pushing over 150 MB/s average
443 
+    traffic. We have several hundred thousand active users. But the Tor
444 
+    network is not yet self-sustaining.
445 
+    </p>
446 
+
447 
+    <p>
448 
+    There are six main development/maintenance pushes that need attention:
449 
+    </p>
450 
+
451 
+    <ul>
452 
+
453 
+    <li>
454 
+    Scalability: We need to keep scaling and decentralizing the Tor
455 
+    architecture so it can handle thousands of relays and millions of
456 
+    users. The upcoming stable release is a major improvement, but there's
457 
+    lots more to be done next in terms of keeping Tor fast and stable.
458 
+    </li>
459 
+
460 
+    <li>
461 
+    User support: With this many users, a lot of people are asking questions
462 
+    all the time, offering to help out with things, and so on. We need good
463 
+    clean docs, and we need to spend some effort coordinating volunteers.
464 
+    </li>
465 
+
466 
+    <li>
467 
+    Relay support: the Tor network is run by volunteers, but they still need
468 
+    attention with prompt bug fixes, explanations when things go wrong,
469 
+    reminders to upgrade, and so on. The network itself is a commons, and
470 
+    somebody needs to spend some energy making sure the relay operators stay
471 
+    happy. We also need to work on <a href="#RelayOS">stability</a> on some
472 
+    platforms &mdash; e.g., Tor relays have problems on Win XP currently.
473 
+    </li>
474 
+
475 
+    <li>
476 
+    Usability: Beyond documentation, we also need to work on usability of the
477 
+    software itself. This includes installers, clean GUIs, easy configuration
478 
+    to interface with other applications, and generally automating all of
479 
+    the difficult and confusing steps inside Tor. We've got a start on this
480 
+    with the <a href="<page projects/gui>">GUI Contest</a>, but much more work
481 
+    remains &mdash; usability for privacy software has never been easy.
482 
+    </li>
483 
+
484 
+    <li>
485 
+    Incentives: We need to work on ways to encourage people to configure
486 
+    their Tors as relays and exit nodes rather than just clients.
487 
+    <a href="#EverybodyARelay">We need to make it easy to become a relay,
488 
+    and we need to give people incentives to do it.</a>
489 
+    </li>
490 
+
491 
+    <li>
492 
+    Research: The anonymous communications field is full
493 
+    of surprises and gotchas. In our copious free time, we
494 
+    also help run top anonymity and privacy conferences like <a
495 
+    href="http://petsymposium.org/">PETS</a>. We've identified a set of
496 
+    critical <a href="<page getinvolved/volunteer>#Research">Tor research questions</a>
497 
+    that will help us figure out how to make Tor secure against the variety of
498 
+    attacks out there. Of course, there are more research questions waiting
499 
+    behind these.
500 
+    </li>
501 
+
502 
+    </ul>
503 
+
504 
+    <p>
505 
+    We're continuing to move forward on all of these, but at this rate
506 
+    <a href="#WhySlow">the Tor network is growing faster than the developers
507 
+    can keep up</a>.
508 
+    Now would be an excellent time to add a few more developers to the effort
509 
+    so we can continue to grow the network.
510 
+    </p>
511 
+
512 
+    <p>
513 
+    We are also excited about tackling related problems, such as
514 
+    censorship-resistance.
515 
+    </p>
516 
+
517 
+    <p>
518 
+    We are proud to have <a href="<page about/sponsors>">sponsorship and support</a>
519 
+    from the Omidyar Network, the International Broadcasting Bureau, Bell
520 
+    Security Solutions, the Electronic Frontier Foundation, several government
521 
+    agencies and research groups, and hundreds of private contributors.
522 
+    </p>
523 
+
524 
+    <p>
525 
+    However, this support is not enough to keep Tor abreast of changes in the
526 
+    Internet privacy landscape. Please <a href="<page donate/donate>">donate</a>
527 
+    to the project, or <a href="<page about/contact>">contact</a> our executive
528 
+    director for information on making grants or major donations.
529 
+    </p>
530 
+
531 
+    <hr />
532 
+
533 
+    <a id="HowUninstallTor"></a>
534 
+    <h3><a class="anchor" href="#HowUninstallTor">How do I uninstall Tor?</a></h3>
535 
+
536 
+    <p>
537 
+    This depends entirely on how you installed it and which operating system you
538 
+    have. If you installed a package, then hopefully your package has a way to
539 
+    uninstall itself. The Windows packages include uninstallers. The proper way to
540 
+    completely remove Tor, Vidalia, Torbutton for Firefox, and Polipo on any
541 
+    version of Windows is as follows:
542 
+    </p>
543 
+
544 
+    <ol>
545 
+    <li>In your taskbar, right click on Vidalia (the green onion or the black head)
546 
+    and choose exit.</li>
547 
+    <li>Right click on the taskbar to bring up TaskManager. Look for tor.exe in the
548 
+    Process List. If it's running, right click and choose End Process.</li>
549 
+    <li>Click the Start button, go to Programs, go to Vidalia, choose Uninstall.
550 
+    This will remove the Vidalia bundle, which includes Tor and Polipo.</li>
551 
+    <li>Start Firefox. Go to the Tools menu, choose Add-ons. Select Torbutton.
552 
+    Click the Uninstall button.</li>
553 
+    </ol>
554 
+
555 
+    <p>
556 
+    If you do not follow these steps (for example by trying to uninstall
557 
+    Vidalia, Tor, and Polipo while they are still running), you will need to
558 
+    reboot and manually remove the directory "Program Files\Vidalia Bundle".
559 
+    </p>
560 
+
561 
+    <p>
562 
+    For Mac OS X, follow the <a
563 
+    href="<page docs/tor-doc-osx>#uninstall">uninstall directions</a>.
564 
+    </p>
565 
+
566 
+    <p>
567 
+    If you installed by source, I'm afraid there is no easy uninstall method. But
568 
+    on the bright side, by default it only installs into /usr/local/ and it should
569 
+    be pretty easy to notice things there.
570 
+    </p>
571 
+
572 
+    <hr />
573 
+
574 
+    <a id="PGPSigs"></a>
575 
+    <h3><a class="anchor" href="#PGPSigs">What are these "sig" files on the
576 
+    download page?</a></h3>
577 
+
578 
+    <p>
579 
+    These are PGP signatures, so you can verify that the file you've downloaded is
580 
+    exactly the one that we intended you to get.
581 
+    </p>
582 
+
583 
+    <p>
584 
+    Please read the <a
585 
+    href="<page docs/verifying-signatures>">verifying signatures</a> page for details.
586 
+    </p>
587 
+
588 
+    <hr />
589 
+
590 
+    <a id="CompileTorWindows"></a>
591 
+    <h3><a class="anchor" href="#CompileTorWindows">How do I compile Tor under
592 
+    Windows?</a></h3>
593 
+
594 
+    <p>
595 
+    Try following the steps at <a href="<gitblob>doc/tor-win32-mingw-creation.txt">
596 
+    tor-win32-mingw-creation.txt</a>.
597 
+    </p>
598 
+
599 
+    <p>
600 
+    (Note that you don't need to compile Tor yourself in order to use
601 
+    it. Most people just use the packages available on the <a href="<page
602 
+    download/download>">download page</a>.)
603 
+    </p>
604 
+
605 
+    <hr />
606 
+
607 
+    <a id="VirusFalsePositives"></a>
608 
+    <h3><a class="anchor" href="#VirusFalsePositives">Why does my Tor
609 
+    executable appear to have a virus or spyware?</a></h3>
610 
+
611 
+    <p>
612 
+    Sometimes, overzealous Windows virus and spyware detectors trigger on some
613 
+    parts of the Tor Windows binary. Our best guess is that these are false
614 
+    positives &mdash; after all, the anti-virus and anti-spyware business is just a
615 
+    guessing game anyway. You should contact your vendor and explain that you have
616 
+    a program that seems to be triggering false positives. Or pick a better vendor.
617 
+    </p>
618 
+
619 
+    <p>
620 
+    In the meantime, we encourage you to not just take our word for
621 
+    it. Our job is to provide the source; if you're concerned, please do <a
622 
+    href="#CompileTorWindows">recompile it yourself</a>.
623 
+    </p>
624 
+
625 
+    <hr />
626 
+
627 
+    <a id="LiveCD"></a>
628 
+    <h3><a class="anchor" href="#LiveCD">Is there a LiveCD or other bundle that
629 
+    includes Tor?</a></h3>
630 
+
631 
+    <p>
632 
+    There isn't any official LiveCD at this point. We're still trying to find good
633 
+    solutions and trying to understand the security and anonymity implications of
634 
+    the various options. In the mean time, feel free to check out the list below
635 
+    and use your best judgement:
636 
+    </p>
637 
+
638 
+    <p>
639 
+    LiveCDs:
640 
+    </p>
641 
+
642 
+    <ol>
643 
+    <li><a href="https://amnesia.boum.org/">The (Amnesic) Incognito Live
644 
+    System</a> is a Live System aimed at preserving your privacy and
645 
+    anonymity:
646 
+    <ul>
647 
+    <li> All outgoing connections to the Internet are forced to go through
648 
+    the Tor network.</li>
649 
+    <li> No trace is left on local storage devices unless explicitely asked.</li>
650 
+    <li> It includes Firefox, Tor, Torbutton, Vidalia graphical Tor
651 
+    controller, Pidgin Instant Messaging client, and lots of other
652 
+    software.</li>
653 
+    <li> It's based upon Debian gnu/linux and comes with the GNOME desktop
654 
+    environment.</li>
655 
+    </ul>
656 
+    <li><a href="http://tork.sourceforge.net/wiki/index.php/LiveCD">TorK LiveCD</a>
657 
+    is Knoppix-based with an emphasis on user-friendliness. You can work
658 
+    anonymously or non-anonymously while TorK tries to keep you informed of the
659 
+    consequences of your activity. The TorK LiveCD is experimental, so the aim is
660 
+    to provide regular releases through 2007 and beyond.</li>
661 
+    <li><a href="http://mandalka.name/privatix/">Privatix LiveCD/USB</a> is a
662 
+    debian based live-system including tor, firefox and torbutton which can save
663 
+    bookmarks and other settings or data on an encrypted usb-key</li>
664 
+    </li>
665 
+    </ol>
666 
+
667 
+    <p>
668 
+    Windows bundles:
669 
+    </p>
670 
+
671 
+    <ol>
672 
+    <li><a href="<page projects/torbrowser>">Tor Browser Bundle</a>
673 
+    for Windows comes with a pre-configured web browser and is self contained
674 
+    so you can run it from a USB stick.</li>
675 
+    <li><a href="http://www.janusvm.com/tor_vm/">Tor VM</a> is a successor
676 
+    to JanusVM. It needs testing from you!</li>
677 
+    <li><a href="http://janusvm.com/">JanusVM</a> is a Linux kernel and software
678 
+    running in VMWare that sits between your Windows computer and the Internet,
679 
+    making sure that your Internet traffic is scrubbed and anonymized.</li>
680 
+    <li><a href="http://www.xerobank.com/xB_browser.html">xB Browser</a>,
681 
+    previously known as Torpark, is a Firefox+Tor package for Win32 that can
682 
+    installed on a USB key. It needs a host Win32 operating system.</li>
683 
+    </ol>
684 
+
685 
+    <p>
686 
+    Not currently maintained as far as we know:
687 
+    </p>
688 
+
689 
+    <ol>
690 
+    <li>Polippix / Privatlivets Fred is a Danish Knoppix-based LiveCD with Tor
691 
+    and utilities to encrypt IP-telephony. <a href="http://polippix.org/">Info and
692 
+    download</a>.</li>
693 
+    <li>ELE is a Linux LiveCD which is focused on privacy related
694 
+    software. It includes Tor and you can download it at
695 
+    <a
696 
+    href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity.net/download/ele/</a>.</li>
697 
+    <li>Virtual Privacy Machine is a Linux LiveCD that includes Firefox, Privoxy,
698 
+    Tor, some IRC and IM applications, and a set of ipchains rules aimed to prevent
699 
+    non-Tor traffic from accidentally leaving your computer. More information at
700 
+    <a
701 
+    href="https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine">https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine</a>.</li>
702 
+    <li>Anonym.OS is a LiveCD similar to the above but is based on OpenBSD rather
703 
+    than Linux for maximum security. It was designed to be anonymous and secure
704 
+    from the ground up, and thus has some features and limitations not found in
705 
+    other LiveCDs (Tor related or otherwise). You can obtain more information and
706 
+    download Anonym.OS from <a href="http://theory.kaos.to/projects.html">Kaos.Theory</a>.</li>
707 
+    <li>Phantomix is a LiveCD for anonymous surfing and chatting based on the most
708 
+    recent KNOPPIX release. It comes preconfigured with Privoxy, Tor and Polipo. You can
709 
+    get it from the <a href="http://phantomix.ytternhagen.de/">Phantomix
710 
+    Website</a>.</li>
711 
+    </ol>
712 
+
713 
+    <p>
714 
+    Please contact us if you know any others.
715 
+    </p>
716 
+
717 
+    <hr />
718 
+
719 
+    <a id="ChooseEntryExit"></a>
720 
+    <h3><a class="anchor" href="#ChooseEntryExit">Can I control which nodes (or country) are used for entry/exit?</a></h3>
721 
+
722 
+    <p>
723 
+    Yes. You can set preferred entry and exit nodes as well as
724 
+    inform Tor which nodes you do not want to use.
725 
+    The following options can be added to your config file "torrc"
726 
+    or specified on the command line:
727 
+    </p>
728 
+    <dl>
729 
+      <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
730 
+        <dd>A list of preferred nodes to use for the first hop in the circuit, if possible.
731 
+        </dd>
732 
+      <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>
733 
+        <dd>A list of preferred nodes to use for the last hop in the circuit, if possible.
734 
+        </dd>
735 
+      <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>
736 
+        <dd>A list of nodes to never use when building a circuit.
737 
+        </dd>
738 
+      <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>
739 
+        <dd>A list of nodes to never use when picking an exit.
740 
+            Nodes listed in <tt>ExcludeNodes</tt> are automatically in this list.
741 
+        </dd>
742 
+    </dl>
743 
+    <p>
744 
+    <em>We recommend you do not use these</em>
745 
+    &mdash; they are intended for testing and may disappear in future versions.
746 
+    You get the best security that Tor can provide when you leave the route selection to Tor;
747 
+    overriding the entry / exit nodes can mess up your anonymity in ways we don't understand.
748 
+    </p>
749 
+    <p>
750 
+    The <tt>EntryNodes</tt> and <tt>ExitNodes</tt> config options are treated as a request,
751 
+    meaning if the nodes are down or seem slow, Tor will still avoid them.
752 
+    You can make the option mandatory by setting
753 
+    <tt>StrictExitNodes 1</tt> or <tt>StrictEntryNodes 1</tt>
754 
+    &mdash; but if you do, your Tor connections will stop working
755 
+    if all of the nodes you have specified become unreachable.
756 
+    See the <a href="https://www.torproject.org/documentation.html.en#NeatLinks">Tor status pages</a>
757 
+    for some nodes you might pick.
758 
+    </p>
759 
+    <p>
760 
+    Instead of <tt>$fingerprint</tt> you can also specify
761 
+    a 2 letter ISO3166 country code in curly braces
762 
+    (for example {de}),
763 
+    or an ip address pattern (for example 255.254.0.0/8),
764 
+    or a node nickname.
765 
+    Make sure there are no spaces between the commas and the list items.
766 
+    </p>
767 
+    <p>
768 
+    If you want to access a service directly through Tor's SOCKS interface
769 
+    (eg. using ssh via connect.c), another option is to
770 
+    set up an internal mapping in your configuration file using <tt>MapAddress</tt>.
771 
+    See the manual page for details.
772 
+    </p>
773 
+
774 
+    <hr />
775 
+
776 
+    <a id="RelayFlexible"></a>
777 
+    <h3><a class="anchor" href="#RelayFlexible">How stable does my relay
778 
+    need to be?</a></h3>
779 
+
780 
+    <p>
781 
+    We aim to make setting up a Tor relay easy and convenient:
782 
+    </p>
783 
+
784 
+    <ul>
785 
+    <li>Tor has built-in support for <a
786 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#LimitBandwidth">
787 
+    rate limiting</a>. Further, if you have a fast
788 
+    link but want to limit the number of bytes per
789 
+    day (or week or month) that you donate, check out the <a
790 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Hibernation">hibernation
791 
+    feature</a>.
792 
+    </li>
793 
+    <li>Each Tor relay has an <a href="#ExitPolicies">exit policy</a> that
794 
+    specifies what sort of outbound connections are allowed or refused from
795 
+    that relay. If you are uncomfortable allowing people to exit from your
796 
+    relay, you can set it up to only allow connections to other Tor relays.
797 
+    </li>
798 
+    <li>It's fine if the relay goes offline sometimes. The directories
799 
+    notice this quickly and stop advertising the relay. Just try to make
800 
+    sure it's not too often, since connections using the relay when it
801 
+    disconnects will break.
802 
+    </li>
803 
+    <li>We can handle relays with dynamic IPs just fine &mdash; simply
804 
+    leave the Address config option blank, and Tor will try to guess.
805 
+    </li>
806 
+    <li>If your relay is behind a NAT and it doesn't know its public
807 
+    IP (e.g. it has an IP of 192.168.x.y), you'll need to set up port
808 
+    forwarding. Forwarding TCP connections is system dependent but
809 
+    <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this FAQ entry</a>
810 
+    offers some examples on how to do this.
811 
+    </li>
812 
+    <li>Your relay will passively estimate and advertise its recent
813 
+    bandwidth capacity, so high-bandwidth relays will attract more users than
814 
+    low-bandwidth ones. Therefore having low-bandwidth relays is useful too.
815 
+    </li>
816 
+    </ul>
817 
+
818 
+    <hr />
819 
+
820 
+    <a id="RunARelayBut"></a>
821 
+    <a id="ExitPolicies"></a>
822 
+    <h3><a class="anchor" href="#ExitPolicies">I'd run a relay, but I don't
823 
+    want to deal with abuse issues.</a></h3>
824 
+
825 
+    <p>
826 
+    Great. That's exactly why we implemented exit policies.
827 
+    </p>
828 
+
829 
+    <p>
830 
+    Each Tor relay has an exit policy that specifies what sort of
831 
+    outbound connections are allowed or refused from that relay. The exit
832 
+    policies are propagated to Tor clients via the directory, so clients
833 
+    will automatically avoid picking exit relays that would refuse to
834 
+    exit to their intended destination. This way each relay can decide
835 
+    the services, hosts, and networks he wants to allow connections to,
836 
+    based on abuse potential and his own situation. Read the FAQ entry on
837 
+    <a href="<page docs/faq-abuse>#TypicalAbuses">issues you might encounter</a>
838 
+    if you use the default exit policy, and then read Mike Perry's
839 
+    <a href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">tips
840 
+    for running an exit node with minimal harassment</a>.
841 
+    </p>
842 
+
843 
+    <p>
844 
+    The default exit policy allows access to many popular services (e.g. web browsing), but
845 
+    <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
846 
+    some due to abuse potential (e.g. mail) and some since
847 
+    the Tor network can't handle the load (e.g. default
848 
+    file-sharing ports). You can change your exit policy
849 
+    using Vidalia's "Sharing" tab, or by manually editing your
850 
+    <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc">torrc</a>
851 
+    file. If you want to avoid most if not all abuse potential, set it to
852 
+    "reject *:*" (or un-check all the boxes in Vidalia). This setting means
853 
+    that your relay will be used for relaying traffic inside the Tor network,
854 
+    but not for connections to external websites or other services.
855 
+    </p>
856 
+
857 
+    <p>
858 
+    If you do allow any exit connections, make sure name resolution works
859 
+    (that is, your computer can resolve Internet addresses correctly).
860 
+    If there are any resources that your computer can't reach (for example,
861 
+    you are behind a restrictive firewall or content filter), please
862 
+    explicitly reject them in your exit policy &mdash; otherwise Tor users
863 
+    will be impacted too.
864 
+    </p>
865 
+
866 
+    <hr />
867 
+
868 
+    <a id="RelayOrBridge"></a>
869 
+    <h3><a class="anchor" href="#RelayOrBridge">Should I be a normal relay
870 
+    or bridge relay?</a></h3>
871 
+
872 
+    <p><a href="<page docs/bridges>">Bridge relays</a> (or "bridges" for short)
873 
+    are <a href="<page docs/tor-doc-relay>">Tor relays</a> that aren't listed
874 
+    in the main Tor directory. That means
875 
+    that even an ISP or government trying to filter connections to the Tor
876 
+    network probably won't be able to block all the bridges.
877 
+    </p>
878 
+
879 
+    <p>Being a normal relay vs being a bridge relay is almost the same
880 
+    configuration: it's just a matter of whether your relay is listed
881 
+    publically or not.
882 
+    </p>
883 
+
884 
+    <p>Right now, there are roughly zero places in the world that filter
885 
+    connections to the Tor network. So getting a lot of bridges running
886 
+    right now is mostly a backup measure, a) in case the Tor network does
887 
+    get blocked somewhere, and b) for people who want an extra layer of
888 
+    security because they're worried somebody will recognize that it's a
889 
+    public Tor relay IP address they're contacting.
890 
+    </p>
891 
+
892 
+    <p>So should you run a normal relay or bridge relay? If you have
893 
+    lots of bandwidth, you should definitely run a normal relay &mdash;
894 
+    bridge relays see very little use these days. If you're willing to
895 
+    <a href="#ExitPolicies">be an exit</a>, you should definitely run a normal
896 
+    relay, since we need more exits. If you can't be an exit and only have
897 
+    a little bit of bandwidth, then flip a coin. Thanks for volunteering!
898 
+    </p>
899 
+
900 
+    <hr />
901 
+
902 
+    <a id="RelayMemory"></a>
903 
+    <h3><a class="anchor" href="#RelayMemory">Why is my Tor relay using so
904 
+    much memory?</a></h3>
905 
+
906 
+    <p>If your Tor relay is using more memory than you'd like, here are some
907 
+    tips for reducing its footprint:
908 
+    </p>
909 
+
910 
+    <ol>
911 
+    <li>If you're on Linux, you may be encountering memory fragmentation
912 
+    bugs in glibc's malloc implementation. That is, when Tor releases memory
913 
+    back to the system, the pieces of memory are fragmented so they're hard
914 
+    to reuse. The Tor tarball ships with OpenBSD's malloc implementation,
915 
+    which doesn't have as many fragmentation bugs (but the tradeoff is higher
916 
+    CPU load). You can tell Tor to use this malloc implementation instead:
917 
+    <tt>./configure --enable-openbsd-malloc</tt></li>
918 
+
919 
+    <li>If you're running a fast relay, meaning you have many TLS connections
920 
+    open, you are probably losing a lot of memory to OpenSSL's internal
921 
+    buffers (38KB+ per socket). We've patched OpenSSL to <a
922 
+    href="http://archives.seul.org/or/dev/Jun-2008/msg00001.html">release
923 
+    unused buffer memory more aggressively</a>. If you update to OpenSSL
924 
+    1.0.0-beta5, Tor's build process will automatically recognize and use
925 
+    this feature.</li>
926 
+
927 
+    <li>If you're running on Solaris, OpenBSD, NetBSD, or
928 
+    old FreeBSD, Tor is probably forking separate processes
929 
+    rather than using threads. Consider switching to a <a
930 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayOS">better
931 
+    operating system</a>.</li>
932 
+
933 
+    <li>If you still can't handle the memory load, consider reducing the
934 
+    amount of bandwidth your relay advertises. Advertising less bandwidth
935 
+    means you will attract fewer users, so your relay shouldn't grow
936 
+    as large. See the <tt>MaxAdvertisedBandwidth</tt> option in the man
937 
+    page.</li>
938 
+
939 
+    </ol>
940 
+
941 
+    <p>
942 
+    All of this said, fast Tor relays do use a lot of ram. It is not unusual
943 
+    for a fast exit relay to use 500-1000 MB of memory.
944 
+    </p>
945 
+
946 
+    <hr />
947 
+
948 
+    <a id="WhyNotNamed"></a>
949 
+    <h3><a class="anchor" href="#WhyNotNamed">Why is my Tor relay not named?</a></h3>
950 
+
951 
+    <p>
952 
+    We currently use these metrics to determine if your relay should be named:<br />
953 
+    </p>
954 
+    <ul>
955 
+    <li>The name is not currently mapped to a different key. Existing mappings
956 
+    are removed after 6 months of inactivity from a relay.</li>
957 
+    <li>The relay must have been around for at least two weeks.</li>
958 
+    <li>No other router may have wanted the same name in the past month.</li>
959 
+    </ul>
960 
+
961 
+    <hr />
962 
+
963 
+    <a id="KeyManagement"></a>
964 
+    <h3><a class="anchor" href="#KeyManagement">Tell me about all the keys
965 
+    Tor uses.</a></h3>
966 
+
967 
+    <p>
968 
+    Tor uses a variety of different keys, with three goals in mind: 1)
969 
+    encryption to ensure privacy of data within the Tor network, 2)
970 
+    authentication so clients know they're
971 
+    talking to the relays they meant to talk to, and 3) signatures to make
972 
+    sure all clients know the same set of relays.
973 
+    </p>
974 
+
975 
+    <p>
976 
+    <b>Encryption</b>: first, all connections in Tor use TLS link encryption,
977 
+    so observers can't look inside to see which circuit a given cell is
978 
+    intended for. Further, the Tor client establishes an ephemeral encryption
979 
+    key with each relay in the circuit, so only the exit relay can read
980 
+    the cells. Both sides discard the circuit key when the circuit ends,
981 
+    so logging traffic and then breaking into the relay to discover the key
982 
+    won't work.
983 
+    </p>
984 
+
985 
+    <p>
986 
+    <b>Authentication</b>:
987 
+    Every Tor relay has a public decryption key called the "onion key".
988 
+    When the Tor client establishes circuits, at each step it <a
989 
+    href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demands
990 
+    that the Tor relay prove knowledge of its onion key</a>. That way
991 
+    the first node in the path can't just spoof the rest of the path.
992 
+    Each relay rotates its onion key once a week.
993 
+    </p>
994 
+
995 
+    <p>
996 
+    <b>Coordination</b>:
997 
+    How do clients know what the relays are, and how do they know that they
998 
+    have the right keys for them? Each relay has a long-term public signing
999 
+    key called the "identity key". Each directory authority additionally has a
1000 
+    "directory signing key". The directory authorities <a
1001 
+    href="<gitblob>doc/spec/dir-spec.txt">provide a signed list</a>
1002 
+    of all the known relays, and in that list are a set of certificates from
1003 
+    each relay (self-signed by their identity key) specifying their keys,
1004 
+    locations, exit policies, and so on. So unless the adversary can control
1005 
+    a threshold of the directory authorities, he can't trick the Tor client
1006 
+    into using other Tor relays.
1007 
+    </p>
1008 
+
1009 
+    <p>
1010 
+    How do clients know what the directory authorities are? The Tor software
1011 
+    comes with a built-in list of location and public key for each directory
1012 
+    authority. So the only way to trick users into using a fake Tor network
1013 
+    is to give them a specially modified version of the software.
1014 
+    </p>
1015 
+
1016 
+    <p>
1017 
+    How do users know they've got the right software? When we distribute
1018 
+    the source code or a package, we digitally sign it with <a
1019 
+    href="http://www.gnupg.org/">GNU Privacy Guard</a>. See the <a
1020 
+    href="<page docs/verifying-signatures>">instructions
1021 
+    on how to check Tor's signatures</a>.
1022 
+    </p>
1023 
+
1024 
+    <p>
1025 
+    In order to be certain that it's really signed by us, you need to have
1026 
+    met us in person and gotten a copy of our GPG key fingerprint, or you
1027 
+    need to know somebody who has. If you're concerned about an attack on
1028 
+    this level, we recommend you get involved with the security community
1029 
+    and start meeting people.
1030 
+    </p>
1031 
+
1032 
+    <hr />
1033 
+
1034 
+    <a id="EverybodyARelay"></a>
1035 
+    <h3><a class="anchor" href="#EverybodyARelay">You should make every Tor
1036 
+    user be a relay.</a></h3>
1037 
+
1038 
+    <p>
1039 
+    Requiring every Tor user to be a relay would help with scaling the
1040 
+    network to handle all our users, and <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">running a Tor
1041 
+    relay may help your anonymity</a>. However, many Tor users cannot be good
1042 
+    relays &mdash; for example, some Tor clients operate from behind restrictive
1043 
+    firewalls, connect via modem, or otherwise aren't in a position where they
1044 
+    can relay traffic. Providing service to these clients is a critical
1045 
+    part of providing effective anonymity for everyone, since many Tor users
1046 
+    are subject to these or similar constraints and including these clients
1047 
+    increases the size of the anonymity set.
1048 
+    </p>
1049 
+
1050 
+    <p>
1051 
+    That said, we do want to encourage Tor users to run relays, so what we
1052 
+    really want to do is simplify the process of setting up and maintaining
1053 
+    a relay. We've made a lot of progress with easy configuration in the past
1054 
+    few years: Vidalia has an easy relay configuration interface, and supports
1055 
+    uPnP too. Tor is good at automatically detecting whether it's reachable and
1056 
+    how much bandwidth it can offer.
1057 
+    </p>
1058 
+
1059 
+    <p>
1060 
+    There are five steps we need to address before we can do this though:
1061 
+    </p>
1062 
+
1063 
+    <p>
1064 
+    First, we need to make Tor stable as a relay on all common
1065 
+    operating systems. The main remaining platform is Windows,
1066 
+    and we plan to finally address that in 2009. See Section 4.1 of <a
1067 
+    href="https://www.torproject.org/press/2008-12-19-roadmap-press-release">our
1068 
+    development roadmap</a>.
1069 
+    </p>
1070 
+
1071 
+    <p>
1072 
+    Second, we still need to get better at automatically estimating
1073 
+    the right amount of bandwidth to allow. See item #7 on the
1074 
+    <a href="<page getinvolved/volunteer>#Research">research section of the
1075 
+    volunteer page</a>: "Tor doesn't work very well when relays
1076 
+    have asymmetric bandwidth (e.g. cable or DSL)". It might be that <a
1077 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching
1078 
+    to UDP transport</a> is the simplest answer here &mdash; which alas is
1079 
+    not a very simple answer at all.
1080 
+    </p>
1081 
+
1082 
+    <p>
1083 
+    Third, we need to work on scalability, both of the network (how to
1084 
+    stop requiring that all Tor relays be able to connect to all Tor
1085 
+    relays) and of the directory (how to stop requiring that all Tor
1086 
+    users know about all Tor relays). Changes like this can have large
1087 
+    impact on potential and actual anonymity. See Section 5 of the <a
1088 
+    href="<svnprojects>design-paper/challenges.pdf">Challenges</a> paper
1089 
+    for details. Again, UDP transport would help here.
1090 
+    </p>
1091 
+
1092 
+    <p>
1093 
+    Fourth, we need to better understand the risks from
1094 
+    letting the attacker send traffic through your relay while
1095 
+    you're also initiating your own anonymized traffic. <a
1096 
+    href="http://freehaven.net/anonbib/#back01">Three</a> <a
1097 
+    href="http://freehaven.net/anonbib/#clog-the-queue">different</a>
1098 
+    <a href="http://freehaven.net/anonbib/#torta05">research</a> papers
1099 
+    describe ways to identify the relays in a circuit by running traffic
1100 
+    through candidate relays and looking for dips in the traffic while the
1101 
+    circuit is active. These clogging attacks are not that scary in the Tor
1102 
+    context so long as relays are never clients too. But if we're trying to
1103 
+    encourage more clients to turn on relay functionality too (whether as
1104 
+    <a href="<page docs/bridges>">bridge relays</a> or as normal relays), then
1105 
+    we need to understand this threat better and learn how to mitigate it.
1106 
+    </p>
1107 
+
1108 
+    <p>
1109 
+    Fifth, we might need some sort of incentive scheme to encourage people
1110 
+    to relay traffic for others, and/or to become exit nodes. Here are our
1111 
+    <a href="https://blog.torproject.org/blog/two-incentive-designs-tor">current
1112 
+    thoughts on Tor incentives</a>.
1113 
+    </p>
1114 
+
1115 
+    <p>
1116 
+    Please help on all of these!
1117 
+    </p>
1118 
+
1119 
+    <hr />
1120 
+
1121 
+    <a id="Criminals"></a>
1122 
+    <h3><a class="anchor" href="#Criminals">Doesn't Tor enable criminals to do bad
1123 
+    things?</a></h3>
1124 
+
1125 
+    <p>
1126 
+    For the answer to this question and others, please see our <a
1127 
+    href="<page docs/faq-abuse>">Tor Abuse FAQ</a>.
1128 
+    </p>
1129 
+
1130 
+    <hr />
1131 
+
1132 
+    <a id="RespondISP"></a>
1133 
+    <h3><a class="anchor" href="#RespondISP">How do I respond to my ISP about my
1134 
+    exit relay?</a></h3>
1135 
+
1136 
+    <p>
1137 
+    A collection of templates for successfully responding to ISPs is <a
1138 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates">collected
1139 
+    here</a>.
1140 
+    </p>
1141 
+
1142 
+    <hr />
1143 
+  </div>
1144 
+  <!-- END MAINCOL -->
1145 
+  <div id = "sidecol">
1146 
+#include "side.wmi"
1147 
+#include "info.wmi"
1148 
+  </div>
1149 
+  <!-- END SIDECOL -->
1150 
+</div>
1151 
+<!-- END CONTENT -->
1152 
+#include <foot.wmi>
docs/en/glossary.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,24 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22359 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor: Glossary" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/documentation>">Glossary</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+
14 
+  <h1>Tor Glossary</h1>
15 
+  </div>
16 
+  <!-- END MAINCOL -->
17 
+  <div id = "sidecol">
18 
+#include "side.wmi"
19 
+#include "info.wmi"
20 
+  </div>
21 
+  <!-- END SIDECOL -->
22 
+</div>
23 
+<!-- END CONTENT -->
24 
+#include <foot.wmi>
docs/en/hidden-services.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,167 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22359 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Hidden Service Protocol" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/hidden-services>">Hidden Services</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h2>Tor: Hidden Service Protocol</h2>
14 
+    <hr />
15 
+
16 
+    <p>
17 
+    Tor makes it possible for users to hide their locations while offering
18 
+    various kinds of services, such as web publishing or an instant
19 
+    messaging server.  Using Tor "rendezvous points," other Tor users can
20 
+    connect to these hidden services, each without knowing the other's
21 
+    network identity. This page describes the technical details of how
22 
+    this rendezvous protocol works. For a more direct how-to, see our <a
23 
+    href="<page docs/tor-hidden-service>">configuring hidden services</a>
24 
+    page.
25 
+    </p>
26 
+
27 
+    <p>
28 
+    A hidden service needs to advertise its existence in the Tor network before
29 
+    clients will be able to contact it. Therefore, the service randomly picks
30 
+    some relays, builds circuits to them, and asks them to act as
31 
+    <em>introduction points</em> by telling them its public key. Note
32 
+    that in the following figures the green links are circuits rather
33 
+    than direct connections. By using a full Tor circuit, it's hard for
34 
+    anyone to associate an introduction point with the hidden server's IP
35 
+    address. While the introduction points and others are told the hidden
36 
+    service's identity (public key), we don't want them to learn about the
37 
+    hidden server's location (IP address).
38 
+    </p>
39 
+
40 
+    <img alt="Tor hidden service step one" src="$(IMGROOT)/THS-1.png" />
41 
+    # maybe add a speech bubble containing "PK" to Bob, because that's what
42 
+    # Bob tells to his introduction points
43 
+
44 
+    <p>
45 
+    Step two: the hidden service assembles a <em>hidden service
46 
+    descriptor</em>, containing its public key and a summary of each
47 
+    introduction point, and signs this descriptor with its private key.
48 
+    It uploads that descriptor to a distributed hash table. The descriptor will be
49 
+    found by clients requesting XYZ.onion where XYZ is a 16 character
50 
+    name that can be uniquely derived from the service's public key. After
51 
+    this step, the hidden service is set up.
52 
+    </p>
53 
+
54 
+    <p>
55 
+    Although it might seem impractical to use an automatically-generated
56 
+    service name, it serves an important goal: Everyone &ndash; including
57 
+    the introduction points, the distributed hash table directory, and of course the
58 
+    clients &ndash; can verify that they are talking to the right hidden
59 
+    service. See also <a href="https://zooko.com/distnames.html">Zooko's
60 
+    conjecture</a> that out of Decentralized, Secure, and Human-Meaningful,
61 
+    you can achieve at most two. Perhaps one day somebody will implement a <a
62 
+    href="http://www.skyhunter.com/marcs/petnames/IntroPetNames.html">Petname</a>
63 
+    design for hidden service names?
64 
+    </p>
65 
+
66 
+    <img alt="Tor hidden service step two" src="$(IMGROOT)/THS-2.png" />
67 
+    # maybe replace "database" with "DHT"; further: how incorrect
68 
+    # is it to *not* add DB to the Tor cloud, now that begin dir cells are in
69 
+    # use?
70 
+
71 
+    <p>
72 
+    Step three: A client that wants to contact a hidden service needs to
73 
+    learn about its
74 
+    onion address first. After that, the client can initiate connection
75 
+    establishment by downloading the descriptor from the distributed hash
76 
+    table. If
77 
+    there is a descriptor for XYZ.onion (the hidden service could also be
78 
+    offline or have left long ago, or there could be a typo in the onion
79 
+    address), the client now knows the set of introduction points and the
80 
+    right public key to use. Around this time, the client also creates
81 
+    a circuit to another randomly picked relay and asks it to act as
82 
+    <em>rendezvous point</em> by telling it a one-time secret.
83 
+    </p>
84 
+
85 
+    <img alt="Tor hidden service step three" src="$(IMGROOT)/THS-3.png" />
86 
+    # maybe add "cookie" to speech bubble, separated from the surrounded
87 
+    # "IP1-3" and "PK"
88 
+
89 
+    <p>
90 
+    Step four: When the descriptor is present and the rendezvous point is
91 
+    ready, the client assembles an <em>introduce</em>
92 
+    message (encrypted to the hidden service's public key) including the
93 
+    address of the rendezvous point and the one-time secret. The client sends
94 
+    this message to one of the introduction points, requesting it be delivered
95 
+    to the hidden service. Again, communication takes place via a Tor circuit:
96 
+    nobody can relate sending the introduce message to the client's IP
97 
+    address, so the client remains anonymous.
98 
+    </p>
99 
+
100 
+    <img alt="Tor hidden service step four" src="$(IMGROOT)/THS-4.png" />
101 
+
102 
+    <p>
103 
+    Step five: The hidden service decrypts the client's introduce message
104 
+    and finds the
105 
+    address of the rendezvous point and the one-time secret in it. The service
106 
+    creates a circuit to the rendezvous point and sends the one-time secret to
107 
+    it in a rendezvous message.
108 
+    </p>
109 
+
110 
+    <p>
111 
+    At this point it is of special importance that the hidden service sticks to
112 
+    the same set of <a
113 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Whatsthisaboutentryguardformerlyknownashelpernodes">entry
114 
+    guards</a> when creating new circuits. Otherwise an attacker
115 
+    could run his own relay and force a hidden service to create an arbitrary
116 
+    number of circuits in the hope that the corrupt relay is picked as entry
117 
+    node and he learns the hidden server's IP address via timing analysis. This
118 
+    attack was described by &Oslash;verlier and Syverson in their paper titled
119 
+    <a href="http://freehaven.net/anonbib/#hs-attack06">Locating Hidden
120 
+    Servers</a>.
121 
+    </p>
122 
+
123 
+    <img alt="Tor hidden service step five" src="$(IMGROOT)/THS-5.png" />
124 
+    # it should say "Bob connects to Alice's ..."
125 
+
126 
+    <p>
127 
+    In the last step, the rendezvous point notifies the client about successful
128 
+    connection establishment. After that, both client and hidden service can
129 
+    use their circuits to the rendezvous point for communicating with each
130 
+    other. The rendezvous point simply relays (end-to-end encrypted) messages
131 
+    from client to service and vice versa.
132 
+    </p>
133 
+
134 
+    <p>
135 
+    One of the reasons for not using the introduction circuit
136 
+    for actual communication is that no single relay should
137 
+    appear to be responsible for a given hidden service. This is why the
138 
+    rendezvous point never learns about the hidden service's identity.
139 
+    </p>
140 
+
141 
+    <p>
142 
+    In general, the complete connection between client and hidden service
143 
+    consists of 6 relays: 3 of them were picked by the client with the third
144 
+    being the rendezvous point and the other 3 were picked by the hidden
145 
+    service.
146 
+    </p>
147 
+
148 
+    <img alt="Tor hidden service step six" src="$(IMGROOT)/THS-6.png" />
149 
+
150 
+    <p>
151 
+    There are more detailed descriptions about the hidden service protocol than
152 
+    this one. See the
153 
+    <a href="<svnprojects>design-paper/tor-design.pdf">Tor design paper</a>
154 
+    for an in-depth design description and the
155 
+    <a href="<gitblob>doc/spec/rend-spec.txt">rendezvous specification</a>
156 
+    for the message formats.
157 
+    </p>
158 
+  </div>
159 
+  <!-- END MAINCOL -->
160 
+  <div id = "sidecol">
161 
+#include "side.wmi"
162 
+#include "info.wmi"
163 
+  </div>
164 
+  <!-- END SIDECOL -->
165 
+</div>
166 
+<!-- END CONTENT -->
167 
+#include <foot.wmi>
docs/en/installguide.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,25 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Installtion Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/installguide>">Installation Guides</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor Installation guides</h1>
14 
+    <br />
15 
+
16 
+  </div>
17 
+  <!-- END MAINCOL -->
18 
+  <div id = "sidecol">
19 
+#include "side.wmi"
20 
+#include "info.wmi"
21 
+  </div>
22 
+  <!-- END SIDECOL -->
23 
+</div>
24 
+<!-- END CONTENT -->
25 
+#include <foot.wmi>
docs/en/manual.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,23 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor: Manuals" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/documentation>">Manuals</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+  <h1>Tor Manuals</h1>
14 
+  </div>
15 
+  <!-- END MAINCOL -->
16 
+  <div id = "sidecol">
17 
+#include "side.wmi"
18 
+#include "info.wmi"
19 
+  </div>
20 
+  <!-- END SIDECOL -->
21 
+</div>
22 
+<!-- END CONTENT -->
23 
+#include <foot.wmi>
docs/en/rpms.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,86 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21907 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: CentOS/Fedora/OpenSUSE Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/rpms>">RPMs</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="rpms"></a>
14 
+    <h2><a class="anchor" href="#rpms">Tor packages for rpm-based
15 
+    linux distributions.</a></h2>
16 
+    <br />
17 
+
18 
+    <p>Do not use the packages in the native repositories. They are
19 
+    frequently out of date. That means you'll be missing stability and
20 
+    security fixes.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    You'll need to set up our package repository before you can fetch
25 
+    Tor.  Assuming yum, in /etc/yum.repos.d/, create a file called
26 
+    torproject.repo.  Edit this file with the following information:
27 
+    <pre>[torproject]
28 
+    name=Tor and Vidalia
29 
+    enabled=1
30 
+    autorefresh=0
31 
+    baseurl=http://deb.torproject.org/torproject.org/rpm/DISTRIBUTION/
32 
+    type=rpm-md
33 
+    gpgcheck=1
34 
+    gpgkey=http://deb.torproject.org/torproject.org/rpm/RPM-GPG-KEY-torproject.org
35 
+    </pre>
36 
+
37 
+    If you wish to track the stable releases of Tor, you should substitute
38 
+    DISTRIBUTION with one of the following: centos4, centos5, fc10, fc11, fc12,
39 
+    suse</p>
40 
+
41 
+    <p>To track experimental releases, substitute DISTRIBUTION with one of these:
42 
+    centos4-experimental, centos5-experimental, fc10-experimental,
43 
+    fc11-experimental, fc12-experimental, suse-experimental</p>
44 
+
45 
+    <p>
46 
+    Now Tor is installed and running. Move on to <a href="<page
47 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Tor on Linux/Unix"
48 
+    instructions.
49 
+    </p>
50 
+
51 
+    <p style="font-size: small">
52 
+    The DNS name <code>deb.torproject.org</code> is actually a set of independent
53 
+    servers in a DNS round robin configuration.  If you for some reason cannot
54 
+    access it you might try to use the name of one of its part instead.  Try
55 
+    <code>deb-master.torproject.org</code>,
56 
+    <code>mirror.netcologne.de</code> or
57 
+    <code>tor.mirror.youam.de</code>.
58 
+    </p>
59 
+
60 
+    <hr />
61 
+
62 
+    <hr />
63 
+
64 
+    <a id="source"></a>
65 
+    <h2><a class="anchor" href="#source">Building from source</a></h2>
66 
+    <br />
67 
+
68 
+    <p>
69 
+    If you'd like to build from source, please follow the <a
70 
+    href="<gitblob>doc/tor-rpm-creation.txt">rpm creation instructions</a>.
71 
+    </p>
72 
+
73 
+    <hr />
74 
+
75 
+    <p>If you have suggestions for improving this document, please <a
76 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
77 
+  </div>
78 
+  <!-- END MAINCOL -->
79 
+  <div id = "sidecol">
80 
+#include "side.wmi"
81 
+#include "info.wmi"
82 
+  </div>
83 
+  <!-- END SIDECOL -->
84 
+</div>
85 
+<!-- END CONTENT -->
86 
+#include <foot.wmi>
docs/en/running-a-mirror.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,104 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22356 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor: Running a Mirror" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/running-a-mirror>">Running a Mirror</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor: Running a Mirror</h1>
14 
+    <hr />
15 
+
16 
+    <p>Thank you for wanting to mirror the Tor website.  All of
17 
+    our mirrors are publicly listed on <a href="<page getinvolved/mirrors>">our mirrors
18 
+    page</a>.  We've included some sample commands and configuration below
19 
+    to make the initial setup and ongoing maintenance a minimal effort.
20 
+    The Tor website and distribution directory currently require 5.0 GB of
21 
+    disk space.</p>
22 
+
23 
+    <p>
24 
+    If you would like to run a mirror, it's as easy as this command to download
25 
+    everything a mirror should share with the world:
26 
+    <br /> <br />
27 
+    <tt>
28 
+    rsync -av --delete rsync://rsync.torproject.org/tor tor-mirror/
29 
+    </tt>
30 
+
31 
+    <p>
32 
+    In order to assure we have reliable and up to date mirrors,
33 
+    please ensure your mirror does at least the following:<br/><br/>
34 
+
35 
+    Updates <b>no less</b> than every six hours, but no more frequent than every
36 
+    hour.<br/><br/>
37 
+
38 
+    Allows "Directory Index / Indexes" (Index viewing) of the /dist
39 
+    directory.<br/><br/>
40 
+
41 
+    Allows "Multiviews" or equivalent for language localization.<br/><br/>
42 
+
43 
+    Have a valid contact email for administrative communications should your
44 
+    server have issues.<br/><br/>
45 
+
46 
+    It is highly recommended for all mirror operators to subscribe to <A
47 
+    href="http://archives.seul.org/tor/mirrors/">tor-mirrors mailing
48 
+    list</A> where all mirror listing modification requests should go (ADD,
49 
+    CHANGE, DELETE, any other requests/notifications).  Also, any technical
50 
+    assistance in setting up your mirror may be found here as well.<br/><br/>
51 
+
52 
+    </p>
53 
+    <br /><br />
54 
+    <p>
55 
+    An example cronjob to update a full mirror once every 6 hours may look like so:
56 
+    <tt>
57 
+    <pre>
58 
+    # m h  dom mon dow   command
59 
+    0 */6 * * * rsync -aq --delete rsync://rsync.torproject.org/tor/ /var/www/mirrors/torproject.org
60 
+    </pre>
61 
+    </tt>
62 
+    </p>
63 
+    <br/>
64 
+    For mirror operators that use Apache, we have created a sample virtual host
65 
+    configuration file to use:
66 
+    <tt>
67 
+    <pre>
68 
+    &lt;VirtualHost 0.1.2.3:80&gt;
69 
+            ServerAdmin youremail@example.com<br/>
70 
+            ServerName  0.1.2.3<br/>
71 
+
72 
+            DocumentRoot /var/www/mirrors/torproject.org<br/>
73 
+
74 
+            &lt;Directory /var/www/mirrors/torproject.org/&gt;<br/>
75 
+                Options MultiViews Indexes<br/>
76 
+                DirectoryIndex index<br/>
77 
+                AllowOverride None<br/>
78 
+            &lt;/Directory&gt;<br/>
79 
+
80 
+    &lt;/VirtualHost&gt;
81 
+    </pre>
82 
+    </tt>
83 
+    <br/> <br/>
84 
+    Please ensure that you keep your mirror updated (we suggest automating this
85 
+    task with something like '<tt>cron</tt>'). Our website, source code and
86 
+    binary releases change often. An update frequency of six hours is recommended.  Tor users everywhere will thank you.
87 
+    </p>
88 
+    <br/>
89 
+    <p>
90 
+    If you are running a mirror, please subscribe to the
91 
+    <A href="http://archives.seul.org/tor/mirrors/">tor-mirrors mailing list</A>, and introduce yourself there.
92 
+    We will add you to the mirror list.
93 
+    Help for mirror support and configuration issues may also be found on the list.
94 
+    </p>
95 
+  </div>
96 
+  <!-- END MAINCOL -->
97 
+  <div id = "sidecol">
98 
+#include "side.wmi"
99 
+#include "info.wmi"
100 
+  </div>
101 
+  <!-- END SIDECOL -->
102 
+</div>
103 
+<!-- END CONTENT -->
104 
+#include <foot.wmi>
docs/en/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/en/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,210 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Running the <a href="<page home>">Tor</a> client on Mac OS X</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Note that these are the installation instructions for running a Tor client on
18 
+      Mac OS X. If you want to relay traffic for others to help the network
19 
+      grow (please do), read the <a
20 
+      href="<page docs/tor-doc-relay>">Configuring a relay</a> guide.</b>
21 
+    </p>
22 
+
23 
+    <hr />
24 
+    <a id="installing"></a>
25 
+    <h2><a class="anchor" href="#installing">Step One: Download and Install Tor</a></h2>
26 
+    <br />
27 
+
28 
+    <p>
29 
+    The install for Macintosh OS X bundles
30 
+    <a href="<page home>">Tor</a>,
31 
+    <a href="<page projects/vidalia>">Vidalia</a> (a graphical interface for Tor),
32 
+    <a href="<page projects/torbutton>">Torbutton</a>,
33 
+    and <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (a web proxy)
34 
+    into one package, with the four applications pre-configured to work
35 
+    together.
36 
+    Download either the <a href="../<package-osx-bundle-stable>">stable</a>
37 
+    or the <a href="../<package-osx-bundle-alpha>">experimental</a> version
38 
+    of the OS X bundle for Intel, or look for more options on the <a href="<page
39 
+    download/download>">download page</a>.
40 
+    </p>
41 
+
42 
+    <p>Once you've downloaded the dmg, double-click and let it mount.
43 
+    Browse to the now open Vidalia Bundle in Finder.  It's easy to install the bundle; simply drag and drop the Vidalia
44 
+    onion icon to the Applications folder.  Optionally, double click the
45 
+    "install torbutton" script and let it install torbutton into Firefox.
46 
+    You can also get Torbutton from Mozilla Add-ons by searching for
47 
+    "torbutton".</p>
48 
+
49 
+    <p>When you are finished installing, you can start Vidalia by selecting its icon
50 
+    from your Applications folder. A dark onion with a red X in your dock means
51 
+    Tor is not currently running. You can start Tor by selecting Start from the
52 
+    "Tor" menu at the top of your screen.
53 
+    </p>
54 
+
55 
+    <p>When Tor is running, Vidalia's dock icon will look like the following:
56 
+    </p>
57 
+
58 
+    <p><img alt="vidalia running tor"
59 
+    src="../img/screenshot-osx-vidalia.png"
60 
+    border="1"/></p>
61 
+
62 
+    <p>Polipo is installed as part of the Tor bundle package
63 
+    installer. Once it is installed, it will start automatically when your
64 
+    computer is restarted.
65 
+    You do not need to configure Polipo to use Tor &mdash; a custom Polipo
66 
+    configuration for Tor has been installed as part of the installer package.
67 
+    </p>
68 
+
69 
+    <hr />
70 
+    <a id="using"></a>
71 
+    <h2><a class="anchor" href="#using">Step Two: Configure your applications to use Tor</a></h2>
72 
+    <br />
73 
+
74 
+    <p>After installing, you need to configure your
75 
+    applications to use them. The first step is to set up web browsing.</p>
76 
+
77 
+    <p>You should use Tor with Firefox and Torbutton, for best safety.
78 
+    Torbutton was installed for you.  Click on the red "Tor Disabled" toggle button to
79 
+    turn Tor on, and you're all set: </p>
80 
+
81 
+    <p><img alt="Torbutton plugin for Firefox"
82 
+    src="../img/screenshot-torbutton.png"
83 
+    border="1"/></p>
84 
+
85 
+    <p>
86 
+    If you plan to run Firefox on a different computer than Tor, see the <a
87 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">FAQ
88 
+    entry for running Tor on a different computer</a>.
89 
+    </p>
90 
+
91 
+    <p>To Torify other applications that support HTTP proxies, just
92 
+    point them at Polipo (that is, localhost port 8118). To use SOCKS
93 
+    directly (for instant messaging, Jabber, IRC, etc), you can point
94 
+    your application directly at Tor (localhost port 9050), but see <a
95 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">this
96 
+    FAQ entry</a> for why this may be dangerous. For applications
97 
+    that support neither SOCKS nor HTTP, take a look at <a
98 
+    href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a> or
99 
+    <a href="http://www.dest-unreach.org/socat/">socat</a>.</p>
100 
+
101 
+    <p>For information on how to Torify other applications, check out the
102 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
103 
+    HOWTO</a>.
104 
+    </p>
105 
+
106 
+    <hr />
107 
+    <a id="verify"></a>
108 
+    <h2><a class="anchor" href="#verify">Step Three: Make sure it's working</a></h2>
109 
+    <br />
110 
+
111 
+    <p>
112 
+    Next, you should try using your browser with Tor and make
113 
+    sure that your IP address is being anonymized. Click on
114 
+    <a href="https://check.torproject.org/">the
115 
+    Tor detector</a>
116 
+    and see whether it thinks you're using Tor or not.
117 
+    (If that site is down, see <a
118 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">this
119 
+    FAQ entry</a> for more suggestions on how to test your Tor.)
120 
+    </p>
121 
+
122 
+    <p>If you have a personal firewall that limits your computer's
123 
+    ability to connect to itself, be sure to allow connections from
124 
+    your local applications to local port 8118 and port 9050. If
125 
+    your firewall blocks outgoing connections, punch a hole so
126 
+    it can connect to at least TCP ports 80 and 443, and then see <a
127 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">this
128 
+    FAQ entry</a>.
129 
+    </p>
130 
+
131 
+    <p>If it's still not working, look at <a
132 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">this
133 
+    FAQ entry</a> for hints.</p>
134 
+
135 
+    <p>
136 
+    Once it's working, learn more about
137 
+    <a href="<page download/download>#Warning">what Tor does and does not offer</a>.
138 
+    </p>
139 
+
140 
+    <hr />
141 
+    <a id="server"></a>
142 
+    <a id="relay"></a>
143 
+    <h2><a class="anchor" href="#relay">Step Four: Configure it as a relay</a></h2>
144 
+    <br />
145 
+
146 
+    <p>The Tor network relies on volunteers to donate bandwidth. The more
147 
+    people who run relays, the faster the Tor network will be. If you have
148 
+    at least 20 kilobytes/s each way, please help out Tor by configuring your
149 
+    Tor to be a relay too. We have many features that make Tor relays easy
150 
+    and convenient, including rate limiting for bandwidth, exit policies so
151 
+    you can limit your exposure to abuse complaints, and support for dynamic
152 
+    IP addresses.</p>
153 
+
154 
+    <p>Having relays in many different places on the Internet is what
155 
+    makes Tor users secure. <a
156 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">You
157 
+    may also get stronger anonymity yourself</a>,
158 
+    since remote sites can't know whether connections originated at your
159 
+    computer or were relayed from others.</p>
160 
+
161 
+    <p>Read more at our <a href="<page docs/tor-doc-relay>">Configuring a relay</a>
162 
+    guide.</p>
163 
+
164 
+    <hr />
165 
+    <a id="uninstall"></a>
166 
+    <h2><a class="anchor" href="#uninstall">How To Uninstall Tor and Privoxy</a></h2>
167 
+    <br />
168 
+
169 
+    <p>There are two ways to uninstall the bundle from your computer, using
170 
+    Finder or a command line or Terminal-based uninstaller.  If you want to remove Tor on OSX, here's how:</p>
171 
+
172 
+    <p>Change your application proxy settings back to their original values.
173 
+       If you just want to stop using Tor, you can end at this point.</p>
174 
+
175 
+    <p>If you want to completely remove Tor, and your account has Admin
176 
+    Privileges, then proceed as follows:</p>
177 
+
178 
+    <ol>
179 
+    <li>Open Finder and click on Applications.</li>
180 
+    <li>Drag /Applications/Vidalia to the Trash.</li>
181 
+    <li>Remove /Library/Torbutton from your system.</li>
182 
+    <li>In your home directory, go to Library, remove the Vidalia
183 
+    directory</li>
184 
+    </ol>
185 
+
186 
+    <p>Tor, Vidalia, and Polipo are now completely removed from your system.</p>
187 
+
188 
+    <p>If you're familiar with the command line or Terminal, you can
189 
+    manually remove the following:</p>
190 
+    <ul>
191 
+    <li>/Applications/Vidalia.app/</li>
192 
+    <li>/Library/Torbutton/</li>
193 
+    <li>~/Library/Vidalia</li>
194 
+    <li>~/.tor</li>
195 
+    </ul>
196 
+
197 
+    <hr />
198 
+
199 
+    <p>If you have suggestions for improving this document, please <a
200 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
201 
+  </div>
202 
+  <!-- END MAINCOL -->
203 
+  <div id = "sidecol">
204 
+#include "side.wmi"
205 
+#include "info.wmi"
206 
+  </div>
207 
+  <!-- END SIDECOL -->
208 
+</div>
209 
+<!-- END CONTENT -->
210 
+#include <foot.wmi>
docs/en/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,301 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+
14 
+    <h1>Configuring a Tor relay</h1>
15 
+
16 
+    #<!-- BEGIN SIDEBAR -->
17 
+    #<div class="sidebar-left">
18 
+    #<h3>Config Steps</h3>
19 
+    #<ol>
20 
+    #<li><a href="<page docs/tor-doc-relay>#install">Download &amp; Install</a></li>
21 
+    #<li><a href="<page docs/tor-doc-relay>#setup">Configuration</a></li>
22 
+    #<li><a href="<page docs/tor-doc-relay>#check">Check &amp; Confirm</a></li>
23 
+    #<li><a href="<page docs/tor-doc-relay>#after">Final Steps</a></li>
24 
+    #</ol>
25 
+    #</div>
26 
+    #<!-- END SIDEBAR -->
27 
+    #
28 
+    <hr />
29 
+
30 
+    <p>
31 
+    The Tor network relies on volunteers to donate bandwidth. The more
32 
+    people who run relays, the faster the Tor network will be. If you have
33 
+    at least 20 kilobytes/s each way, please help out Tor by configuring your
34 
+    Tor to be a relay too. We have many features that make Tor relays easy
35 
+    and convenient, including <a href="<page docs/faq>#RelayFlexible">rate limiting
36 
+    for bandwidth, exit policies so you can limit your exposure to abuse
37 
+    complaints, and support for dynamic IP addresses</a>.
38 
+    </p>
39 
+
40 
+    <p>You can run a Tor relay on <a
41 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">pretty
42 
+    much any</a> operating system. Tor relays work best on Linux, OS X Tiger
43 
+    or later, FreeBSD 5.x+, NetBSD 5.x+, and Windows Server 2003 or later.
44 
+    </p>
45 
+
46 
+    <hr />
47 
+    <a id="zero"></a>
48 
+    <a id="install"></a>
49 
+    <h2><a class="anchor" href="#install">Step One: Download and Install Tor</a></h2>
50 
+    <br />
51 
+
52 
+    <p>Before you start, you need to make sure that Tor is up and running.
53 
+    </p>
54 
+
55 
+    <p>Visit our <a href="<page download/easy-download>">download page</a> and
56 
+    install the "Installation Bundle" for your OS.
57 
+    </p>
58 
+
59 
+    <p>If it's convenient, you might also want to use it as a client for a
60 
+    while to make sure it's actually working.</p>
61 
+
62 
+    <hr />
63 
+    <a id="setup"></a>
64 
+    <h2><a class="anchor" href="#setup">Step Two: Set it up as a relay</a></h2>
65 
+    <br />
66 
+    <ol>
67 
+    <li>Verify that your clock and timezone are set
68 
+    correctly. If possible, synchronize your clock with public <a
69 
+    href="http://en.wikipedia.org/wiki/Network_Time_Protocol">time
70 
+    servers</a>.
71 
+    </li>
72 
+
73 
+    <li><strong>Configuring Tor with the Vidalia Graphical Interface</strong>:
74 
+    <ol>
75 
+
76 
+    <li>
77 
+    	<dt>Right click on the Vidalia icon in your task bar.  Choose <tt>Control Panel</tt>.</dt>
78 
+    	<dd><img alt="vidalia right click menu" src="../img/screenshot-win32-vidalia.png"></dd>
79 
+    </li>
80 
+
81 
+    <li>Click <tt>Setup Relaying</tt>.</li>
82 
+
83 
+    <li>
84 
+    	<dt>Choose <tt>Relay Traffic for the Tor network</tt> if you want to be a public relay (recommended), or choose 		<tt>Help censored users reach the Tor network</tt> if you want to be a <a href="<page docs/faq>#RelayOrBridge">bridge</a> for users in countries that censor their Internet.</dt>
85 
+    <dd><img alt="vidalia basic settings" src="../img/screenshot-win32-configure-relay-1.png"></dd>
86 
+    </li>
87 
+
88 
+    <li>Enter a nickname for your relay, and enter contact information in
89 
+    case we need to contact you about problems.</li>
90 
+
91 
+    <li>Leave <tt>Attempt to automatically configure port forwarding</tt> clicked.
92 
+    Push the <tt>Test</tt> button to see if it works.  If it does work, great.
93 
+    If not, see number 3 below.</li>
94 
+
95 
+    <li><dt>Choose the <tt>Bandwidth Limits</tt> tab.  Select how much bandwidth you want to provide for Tor users like yourself.</dt>
96 
+    <dd><img alt="vidalia bandwidth limits" src="../img/screenshot-win32-configure-relay-2.png"></dd>
97 
+    </li>
98 
+
99 
+    <li><dt>Choose the <tt>Exit Policies</tt> tab.  If you want to allow others
100 
+    to use your relay for these services, don't change anything.  Un-check
101 
+    the services you don't want to allow people to <a href="<page
102 
+    docs/faq>#ExitPolicies">reach from your relay</a>.  If you want to be a non-exit relay, un-check all services.</dt>
103 
+    <dd><img alt="vidalia exit policies" src="../img/screenshot-win32-configure-relay-3.png"></dd>
104 
+    </li>
105 
+
106 
+    <li>Click the <tt>Ok</tt> button.  See Step Three below for confirmation
107 
+    that the relay is working correctly.</li>
108 
+    </ol>
109 
+
110 
+    <br />
111 
+    <strong>Manual Configuration</strong>:
112 
+    <ul>
113 
+    <li>Edit the bottom part of <a
114 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">your
115 
+    torrc file</a>. If you want to be a public relay (recommended),
116 
+    make sure to define ORPort and <a href="<page
117 
+    docs/faq>#ExitPolicies">look at ExitPolicy</a>; otherwise
118 
+    if you want to be a <a href="<page docs/faq>#RelayOrBridge">bridge</a>
119 
+    for users in countries that censor their Internet,
120 
+    just use <a href="<page docs/bridges>#RunningABridge">these lines</a>.
121 
+    </li>
122 
+
123 
+    </ul></li>
124 
+
125 
+    <li>If you are using a firewall, open a hole in your firewall
126 
+    so incoming connections can reach the ports you configured
127 
+    (ORPort, plus DirPort if you enabled it). If you have a
128 
+    hardware firewall (Linksys box, cablemodem, etc) you might like <a
129 
+    href="http://portforward.com/">portforward.com</a>. Also, make sure you
130 
+    allow all <em>outgoing</em> connections too, so your relay can reach the
131 
+    other Tor relays.
132 
+    </li>
133 
+
134 
+    <li>Restart your relay. If it <a
135 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">logs
136 
+    any warnings</a>, address them.
137 
+    </li>
138 
+
139 
+    <li>Subscribe to the <a
140 
+    href="http://archives.seul.org/or/announce/">or-announce</a>
141 
+    mailing list. It is very low volume, and it will keep you informed
142 
+    of new stable releases. You might also consider subscribing to <a
143 
+    href="<page docs/documentation>#MailingLists">the higher-volume Tor lists</a>
144 
+    too.
145 
+    </li>
146 
+
147 
+    </ol>
148 
+
149 
+    <hr />
150 
+    <a id="check"></a>
151 
+    <h2><a class="anchor" href="#check">Step Three: Make sure it is working</a></h2>
152 
+    <br />
153 
+
154 
+    <p>As soon as your relay manages to connect to the network, it will
155 
+    try to determine whether the ports you configured are reachable from
156 
+    the outside. This step is usually fast, but may take up to 20
157 
+    minutes. Look for a
158 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">log
159 
+    entry</a> like
160 
+    <tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt>
161 
+    If you don't see this message, it means that your relay is not reachable
162 
+    from the outside &mdash; you should re-check your firewalls, check that it's
163 
+    testing the IP and port you think it should be testing, etc.
164 
+    </p>
165 
+
166 
+    <p>When it decides that it's reachable, it will upload a "server
167 
+    descriptor" to the directories, to let clients know
168 
+    what address, ports, keys, etc your relay is using. You can <a
169 
+    href="http://194.109.206.212/tor/status-vote/current/consensus">load one of
170 
+    the network statuses manually</a> and
171 
+    look through it to find the nickname you configured, to make sure it's
172 
+    there. You may need to wait up to one hour to give enough time for it to
173 
+    make a fresh directory.</p>
174 
+
175 
+    <hr />
176 
+    <a id="after"></a>
177 
+    <h2><a class="anchor" href="#after">Step Four: Once it is working</a></h2>
178 
+    <br />
179 
+
180 
+    <p>
181 
+    We recommend the following steps as well:
182 
+    </p>
183 
+
184 
+    <p>
185 
+    6. Read
186 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">about operational security</a>
187 
+    to get ideas how you can increase the security of your relay.
188 
+    </p>
189 
+
190 
+    <p>
191 
+    7. If you want to run more than one relay that's great, but please set <a
192 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">the
193 
+    MyFamily option</a> in all your relays' configuration files.
194 
+    </p>
195 
+
196 
+    <p>
197 
+    8. Decide about rate limiting. Cable modem, DSL, and other users
198 
+    who have asymmetric bandwidth (e.g. more down than up) should
199 
+    rate limit to their slower bandwidth, to avoid congestion. See the <a
200 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">rate
201 
+    limiting FAQ entry</a> for details.
202 
+    </p>
203 
+
204 
+    <p>
205 
+    9. Back up your Tor relay's private key (stored in "keys/secret_id_key"
206 
+    in your DataDirectory). This is your relay's "identity," and
207 
+    you need to keep it safe so nobody can read the traffic that goes
208 
+    through your relay. This is the critical file to keep if you need to <a
209 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeRelay">move
210 
+    or restore your Tor relay</a> if something goes wrong.
211 
+    </p>
212 
+
213 
+    <p>
214 
+
215 
+    10. If you control the name servers for your domain, consider setting your
216 
+    reverse DNS hostname to 'anonymous-relay', 'proxy' or 'tor-proxy', so when
217 
+    other people see the address in their web logs, they will more quickly
218 
+    understand what's going on. Adding the <a
219 
+    href="<gitblob>contrib/tor-exit-notice.html">Tor
220 
+    exit notice</a> on a vhost for this name can go a long way to deterring abuse
221 
+    complaints to you and your ISP if you are running an exit node.
222 
+
223 
+    </p>
224 
+
225 
+    <p>
226 
+    11. If your computer isn't running a webserver, please consider
227 
+    changing your ORPort to 443 and your DirPort to 80. Many Tor
228 
+    users are stuck behind firewalls that only let them browse the
229 
+    web, and this change will let them reach your Tor relay. Win32
230 
+    relays can simply change their ORPort and DirPort directly
231 
+    in their torrc and restart Tor. OS X or Unix relays can't bind
232 
+    directly to these ports (since they don't run as root), so they will
233 
+    need to set up some sort of <a
234 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">
235 
+    port forwarding</a> so connections can reach their Tor relay. If you are
236 
+    using ports 80 and 443 already but still want to help out, other useful
237 
+    ports are 22, 110, and 143.
238 
+    </p>
239 
+
240 
+    <p>
241 
+    12. If your Tor relay provides other services on the same IP address
242 
+    &mdash; such as a public webserver &mdash; make sure that connections to the
243 
+    webserver are allowed from the local host too. You need to allow these
244 
+    connections because Tor clients will detect that your Tor relay is the <a
245 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">safest
246 
+    way to reach that webserver</a>, and always build a circuit that ends
247 
+    at your relay. If you don't want to allow the connections, you must
248 
+    explicitly reject them in your exit policy.
249 
+    </p>
250 
+
251 
+    <p>
252 
+    13. (Unix only). Make a separate user to run the relay. If you
253 
+    installed the OS X package or the deb or the rpm, this is already
254 
+    done. Otherwise, you can do it by hand. (The Tor relay doesn't need to
255 
+    be run as root, so it's good practice to not run it as root. Running
256 
+    as a 'tor' user avoids issues with identd and other services that
257 
+    detect user name. If you're the paranoid sort, feel free to <a
258 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">put Tor
259 
+    into a chroot jail</a>.)
260 
+    </p>
261 
+
262 
+    <p>
263 
+    14. (Unix only.) Your operating system probably limits the number
264 
+    of open file descriptors per process to 1024 (or even less). If you
265 
+    plan to be running a fast exit node, this is probably not enough. On
266 
+    Linux, you should add a line like "toruser hard nofile 8192" to your
267 
+    /etc/security/limits.conf file (where toruser is the user that runs the
268 
+    Tor process), and then restart Tor if it's installed as a package (or log
269 
+    out and log back in if you run it yourself).
270 
+    </p>
271 
+
272 
+    <p>
273 
+    15. If you installed Tor via some package or installer, it probably starts
274 
+    Tor for you automatically on boot. But if you installed from source,
275 
+    you may find the initscripts in contrib/tor.sh or contrib/torctl useful.
276 
+    </p>
277 
+
278 
+    <p>
279 
+    When you change your Tor configuration, remember to verify that your
280 
+    relay still works correctly after the change. Be sure to set your
281 
+    "ContactInfo" line in the torrc so we can contact you if you need to
282 
+    upgrade or something goes wrong. If you have problems or questions, see
283 
+    the <a href="<page docs/documentation>#Support">Support</a> section or
284 
+    <a href="<page about/contact>">contact us</a> on the tor-ops list. Thanks
285 
+    for helping to make the Tor network grow!
286 
+    </p>
287 
+
288 
+    <hr />
289 
+
290 
+    <p>If you have suggestions for improving this document, please <a
291 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
292 
+  </div>
293 
+  <!-- END MAINCOL -->
294 
+  <div id = "sidecol">
295 
+#include "side.wmi"
296 
+#include "info.wmi"
297 
+  </div>
298 
+  <!-- END SIDECOL -->
299 
+</div>
300 
+<!-- END CONTENT -->
301 
+#include <foot.wmi>
docs/en/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,204 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21798 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Linux/BSD/Unix Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-unix>">Linux/BSD/Unix Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Running the <a href="<page home>">Tor</a> client on Linux/BSD/Unix</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Note that these are the installation instructions for running a Tor
18 
+    client. If you want to relay traffic for others to help the network grow
19 
+    (please do), read the <a
20 
+    href="<page docs/tor-doc-relay>">Configuring a relay</a> guide.</b>
21 
+    </p>
22 
+
23 
+    <hr />
24 
+    <a id="installing"></a>
25 
+    <h2><a class="anchor" href="#installing">Step One: Download and Install Tor</a></h2>
26 
+    <br />
27 
+
28 
+    <p>
29 
+    The latest release of Tor can be found on the <a
30 
+    href="<page download/download>">download</a> page. We have packages for Debian,
31 
+    Red Hat, Gentoo, *BSD, etc there too. If you're
32 
+    using Ubuntu, don't use the default packages: use <a
33 
+    href="<page docs/debian>#ubuntu">our deb repository</a> instead.
34 
+    </p>
35 
+
36 
+    <p>If you're building from source, first install <a
37 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a>, and
38 
+    make sure you have openssl and zlib (including the -devel packages if
39 
+    applicable). Then run:<br />
40 
+    <tt>tar xzf tor-<version-stable>.tar.gz; cd tor-<version-stable></tt><br />
41 
+    <tt>./configure &amp;&amp; make</tt><br />
42 
+    Now you can run tor as <tt>src/or/tor</tt>, or you can run <tt>make install</tt>
43 
+    (as root if necessary) to install it into /usr/local/, and then you can
44 
+    start it just by running <tt>tor</tt>.
45 
+    </p>
46 
+
47 
+    <p>Tor comes configured as a client by default. It uses a built-in
48 
+    default configuration file, and most people won't need to change any of
49 
+    the settings. Tor is now installed.
50 
+    </p>
51 
+
52 
+    <hr />
53 
+    <a id="privoxy"></a>
54 
+    <a id="polipo"></a>
55 
+    <h2><a class="anchor" href="#polipo">Step Two: Install Polipo for Web Browsing</a></h2>
56 
+    <br />
57 
+
58 
+    <p>After installing Tor, you need to configure your applications to use it.
59 
+    </p>
60 
+
61 
+    <p>
62 
+    The first step is to set up web browsing. Start by installing <a
63 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> from
64 
+    your favorite repository. Polipo is a caching web proxy that does http
65 
+    pipelining well, so it's well-suited for Tor's latencies. Make sure
66 
+    to get at least Polipo 1.0.4, since earlier versions lack the SOCKS support
67 
+    required to use Polipo with Tor. You should uninstall privoxy at this
68 
+    point (e.g. apt-get remove privoxy or yum remove privoxy), so they don't
69 
+    conflict.
70 
+    </p>
71 
+
72 
+    <p>Once you've installed Polipo (either from package or from
73 
+    source), <b>you will need to configure Polipo to use Tor</b>. Grab our <a
74 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/polipo.conf">Polipo
75 
+    configuration for Tor</a> and put it in place of your current polipo
76 
+    config file (e.g. /etc/polipo/config or ~/.polipo).
77 
+    You'll need to restart Polipo for the changes to take effect. For
78 
+    example:<br />
79 
+    <tt>/etc/init.d/polipo restart</tt>
80 
+    </p>
81 
+
82 
+    <p>If you prefer, you can instead use Privoxy with <a
83 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">this
84 
+    sample Privoxy configuration</a>. But since the config files both use
85 
+    port 8118, you shouldn't run both Polipo and Privoxy at the same time.</p>
86 
+
87 
+    <hr />
88 
+    <a id="using"></a>
89 
+    <h2><a class="anchor" href="#using">Step Three: Configure your applications to use Tor</a></h2>
90 
+    <br />
91 
+
92 
+    <p>After installing Tor and Polipo, you need to configure your
93 
+    applications to use them. The first step is to set up web browsing.</p>
94 
+
95 
+    <p>You should use Tor with Firefox and Torbutton, for best safety.
96 
+    Simply install the <a
97 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton
98 
+    plugin</a>, restart your Firefox, and you're all set:
99 
+    </p>
100 
+
101 
+    <img alt="Torbutton plugin for Firefox"
102 
+    src="../img/screenshot-torbutton.png"
103 
+    border="1">
104 
+
105 
+    <br />
106 
+
107 
+    <p>
108 
+    If you plan to run Firefox on a different computer than Tor, see the <a
109 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">
110 
+    FAQ
111 
+    entry for running Tor on a different computer</a>.
112 
+    </p>
113 
+
114 
+    <p>To Torify other applications that support HTTP proxies, just
115 
+    point them at Polipo (that is, localhost port 8118). To use SOCKS
116 
+    directly (for instant messaging, Jabber, IRC, etc), you can point
117 
+    your application directly at Tor (localhost port 9050), but see <a
118 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">this
119 
+    FAQ entry</a> for why this may be dangerous. For applications
120 
+    that support neither SOCKS nor HTTP, take a look at <a
121 
+    href="http://tsocks.sourceforge.net/">tsocks</a> or <a
122 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
123 
+    </p>
124 
+
125 
+    <p>For information on how to Torify other applications, check out the
126 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
127 
+    HOWTO</a>.
128 
+    </p>
129 
+
130 
+    <hr />
131 
+    <a id="verify"></a>
132 
+    <h2><a class="anchor" href="#verify">Step Four: Make sure it's working</a></h2>
133 
+    <br />
134 
+
135 
+    <p>
136 
+    Next, you should try using your browser with Tor and make
137 
+    sure that your IP address is being anonymized. Click on
138 
+    <a href="https://check.torproject.org/">the
139 
+    Tor detector</a>
140 
+    and see whether it thinks you're using Tor or not.
141 
+    #<a href="http://ipchicken.com/">this site</a>
142 
+    #to see what IP address it thinks you're using.
143 
+    (If that site is down, see <a
144 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">this
145 
+    FAQ entry</a> for more suggestions on how to test your Tor.)
146 
+    </p>
147 
+
148 
+    <p>If you have a personal firewall that limits your computer's
149 
+    ability to connect to itself (this includes something like SELinux on
150 
+    Fedora Core 4), be sure to allow connections from
151 
+    your local applications to Polipo (local port 8118) and Tor (local port
152 
+    9050). If
153 
+    your firewall blocks outgoing connections, punch a hole so
154 
+    it can connect to at least TCP ports 80 and 443, and then see <a
155 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">this
156 
+    FAQ entry</a>.  If your SELinux config is not allowing tor or privoxy to
157 
+    run correctly, create a file named booleans.local in the directory
158 
+    /etc/selinux/targeted.  Edit this file in your favorite text editor and
159 
+    insert "allow_ypbind=1".  Restart your machine for this change to take
160 
+    effect.
161 
+    </p>
162 
+
163 
+    <p>If it's still not working, look at <a
164 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">this
165 
+    FAQ entry</a> for hints.</p>
166 
+
167 
+    <hr />
168 
+    <a id="server"></a>
169 
+    <a id="relay"></a>
170 
+    <h2><a class="anchor" href="#relay">Step Five: Configure it as a relay</a></h2>
171 
+    <br />
172 
+
173 
+    <p>The Tor network relies on volunteers to donate bandwidth. The more
174 
+    people who run relays, the faster the Tor network will be. If you have
175 
+    at least 20 kilobytes/s each way, please help out Tor by configuring your
176 
+    Tor to be a relay too. We have many features that make Tor relays easy
177 
+    and convenient, including rate limiting for bandwidth, exit policies so
178 
+    you can limit your exposure to abuse complaints, and support for dynamic
179 
+    IP addresses.</p>
180 
+
181 
+    <p>Having relays in many different places on the Internet is what
182 
+    makes Tor users secure. <a
183 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">You
184 
+    may also get stronger anonymity yourself</a>,
185 
+    since remote sites can't know whether connections originated at your
186 
+    computer or were relayed from others.</p>
187 
+
188 
+    <p>Read more at our <a href="<page docs/tor-doc-relay>">Configuring a relay</a>
189 
+    guide.</p>
190 
+
191 
+    <hr />
192 
+
193 
+    <p>If you have suggestions for improving this document, please <a
194 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
195 
+  </div>
196 
+  <!-- END MAINCOL -->
197 
+  <div id = "sidecol">
198 
+#include "side.wmi"
199 
+#include "info.wmi"
200 
+  </div>
201 
+  <!-- END SIDECOL -->
202 
+</div>
203 
+<!-- END CONTENT -->
204 
+#include <foot.wmi>
docs/en/tor-doc-web.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,64 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Configuring your browser to use Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-web>">Configure Your Browser</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configuring your browser to use <a href="<page home>">Tor</a></h1>
14 
+    <br />
15 
+
16 
+    <p>If you're using Firefox (we recommend it), you don't need this page.
17 
+    Simply install the <a
18 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton
19 
+    plugin</a>, restart your Firefox, and you're all set:
20 
+    </p>
21 
+
22 
+    <img alt="Torbutton plugin for Firefox"
23 
+    src="../img/screenshot-torbutton.png"
24 
+    border="1"/>
25 
+
26 
+    <br />
27 
+
28 
+    <p>Otherwise, you need to manually configure your browser's proxy
29 
+    settings.
30 
+    <br/>In Mozilla and Firefox on Windows, this is in
31 
+    Tools - Options - General - Connection Settings.
32 
+    <br/>In Firefox on OS X, it's Firefox - Preferences - General - Connection Settings.
33 
+    <br/>In Firefox on Linux, this is in
34 
+    Edit - Preferences - Advanced - Proxies.
35 
+    <br/>In Opera it's Tools - Preferences(Advanced) - Network - Proxy servers.
36 
+    <br/>While we cannot advise using IE, for those wishing less-than-real
37 
+    anonymity:  In IE, it's Tools - Internet Options - Connections - LAN Settings - Check Proxy
38 
+    Server - Advanced.</p>
39 
+
40 
+    <img alt="Proxy settings in Firefox"
41 
+    src="../img/screenshot-win32-firefox-proxies.jpg" />
42 
+
43 
+    <p>
44 
+    You should fill in "localhost"
45 
+    and "8118" to point the top four protocols to Polipo, as shown here. (Even
46 
+    though Polipo doesn't support FTP and Gopher, <a
47 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">you
48 
+    should set them up anyway</a>.) You should also fill out the socks proxy entry to point directly to Tor ("localhost", "9050", and socks5)
49 
+    to cover protocols besides the first four. Then click "OK".</p>
50 
+
51 
+    <hr />
52 
+
53 
+    <p>If you have suggestions for improving this document, please <a
54 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
55 
+  </div>
56 
+  <!-- END MAINCOL -->
57 
+  <div id = "sidecol">
58 
+#include "side.wmi"
59 
+#include "info.wmi"
60 
+  </div>
61 
+  <!-- END SIDECOL -->
62 
+</div>
63 
+<!-- END CONTENT -->
64 
+#include <foot.wmi>
docs/en/tor-doc-win32.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,7 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 13195 $
3 
+# Status: obsolete
4 
+
5 
+#include "head.wmi" TITLE="Redirecting" REDIRECT="docs/tor-doc-windows"
6 
+
7 
+#include <foot.wmi>
docs/en/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,187 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Running the <a href="<page home>">Tor</a> client on Microsoft Windows</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Note that these are the installation instructions for running a Tor
18 
+    client on Microsoft Windows (2000, XP, Vista, 7, and Server Editions).
19 
+    If you want to relay traffic for others to help the network grow (please
20 
+    do), read the <a href="<page docs/tor-doc-relay>">Configuring a relay</a>
21 
+    guide.</b>
22 
+    </p>
23 
+
24 
+    <p>Freedom House has produced a video on how to install Tor.  You can
25 
+    view it at <a href="http://media.torproject.org/video/2009-install-and-use-tor.ogv">How
26 
+    to install Tor on Windows</a>.  Know of a better video, or one
27 
+    translated into your language?  Let us know!</p>
28 
+
29 
+    <div class="center">
30 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor.ogv" autobuffer="true" controls="controls"></video></p>
31 
+    </div>
32 
+
33 
+    <hr />
34 
+    <a id="installing"></a>
35 
+    <h2><a class="anchor" href="#installing">Step One: Download and Install Tor</a></h2>
36 
+    <br />
37 
+
38 
+    <p>
39 
+    Microsoft Windows bundles contain <a href="<page home>">Tor</a>, <a
40 
+    href="<page projects/vidalia>">Vidalia</a> (a GUI for Tor), <a
41 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> (a plugin for Mozilla Firefox), and <a
42 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>
43 
+    (a web proxy) packaged into one bundle, with the four applications
44 
+    pre-configured to work together.  Download either the <a
45 
+    href="../<package-win32-bundle-stable>">stable</a> or the <a
46 
+    href="../<package-win32-bundle-alpha>">experimental</a> version of
47 
+    the Windows bundle, or look for more options on the <a href="<page
48 
+    download/download>">download page</a>.
49 
+    </p>
50 
+
51 
+    <img alt="tor installer splash page" src="../img/screenshot-win32-installer-splash.png" />
52 
+
53 
+    <p>If you have previously installed Tor, Vidalia, or Polipo
54 
+    you can deselect whichever components you do not need to install
55 
+    in the dialog shown below.
56 
+    </p>
57 
+
58 
+    <img alt="select components to install" src="../img/screenshot-win32-installer-components.png" />
59 
+
60 
+    <p>After you have completed the installer, the components
61 
+    you selected will automatically be started for you.
62 
+    </p>
63 
+
64 
+    <p>Tor comes configured as a client by default. It uses a built-in
65 
+    default configuration file, and most people won't need to change any of
66 
+    the settings. Tor is now installed.
67 
+    </p>
68 
+
69 
+    <hr />
70 
+    <a id="using"></a>
71 
+    <h2><a class="anchor" href="#using">Step Two: Configure your applications to use Tor</a></h2>
72 
+    <br />
73 
+
74 
+    <p>After installing Tor and Polipo, you need to configure your
75 
+    applications to use them. The first step is to set up web browsing.</p>
76 
+
77 
+    <p>You should use Tor with Firefox and Torbutton,
78 
+    for best safety. The bundle installs the <a
79 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton plugin</a>
80 
+    for you. Restart your Firefox, and you're all set:
81 
+    </p>
82 
+
83 
+    <img alt="Torbutton plugin for Firefox" src="../img/screenshot-torbutton.png" border="1"/>
84 
+
85 
+    <br />
86 
+
87 
+    <p>
88 
+    If you plan to run Firefox on a different computer than Tor, see the <a
89 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">FAQ
90 
+    entry for running Tor on a different computer</a>.
91 
+    </p>
92 
+
93 
+    <p>To Torify other applications that support HTTP proxies, just
94 
+    point them at Polipo (that is, localhost port 8118). To use SOCKS
95 
+    directly (for instant messaging, Jabber, IRC, etc), you can point
96 
+    your application directly at Tor (localhost port 9050), but see <a
97 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">this
98 
+    FAQ entry</a> for why this may be dangerous. For applications
99 
+    that support neither SOCKS nor HTTP, take a look at SocksCap or
100 
+    <a href="http://www.freecap.ru/eng/">FreeCap</a>.
101 
+    (FreeCap is free software; SocksCap is proprietary.)</p>
102 
+
103 
+    <p>For information on how to Torify other applications, check out the
104 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
105 
+    HOWTO</a>.
106 
+    </p>
107 
+
108 
+    <hr />
109 
+    <a id="verify"></a>
110 
+    <h2><a class="anchor" href="#verify">Step Three: Make sure it's working</a></h2>
111 
+    <br />
112 
+
113 
+    <p>
114 
+    Check to see that Vidalia is running.  Vidalia uses a small green onion
115 
+    to indicate Tor is running or a dark onion with a red "X" when Tor is
116 
+    not running. You can start or stop Tor by right-clicking
117 
+    on Vidalia's icon in your system tray and selecting "Start" or "Stop"
118 
+    from the menu as shown below:
119 
+    </p>
120 
+
121 
+    <img alt="Vidalia Tray Icon" src="../img/screenshot-win32-vidalia.png"/>
122 
+
123 
+    <p>
124 
+    Next, you should try using your browser with Tor and make
125 
+    sure that your IP address is being anonymized. Click on <a
126 
+    href="https://check.torproject.org/">the Tor detector</a> and see
127 
+    whether it thinks you're using Tor or not.  (If that site is down, see <a
128 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">this
129 
+    FAQ entry</a> for more suggestions on how to test your Tor.)
130 
+    </p>
131 
+
132 
+    <p>If you have a personal firewall that limits your computer's
133 
+    ability to connect to itself, be sure to allow connections from
134 
+    your local applications to local port 8118 and port 9050. If
135 
+    your firewall blocks outgoing connections, punch a hole so
136 
+    it can connect to at least TCP ports 80 and 443, and then see <a
137 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">this
138 
+    FAQ entry</a>.
139 
+    </p>
140 
+
141 
+    <p>If it's still not working, look at <a
142 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">this
143 
+    FAQ entry</a> for hints.</p>
144 
+
145 
+    <p>
146 
+    Once it's working, learn more about
147 
+    <a href="<page download/download>#Warning">what Tor does and does not offer</a>.
148 
+    </p>
149 
+
150 
+    <hr />
151 
+    <a id="server"></a>
152 
+    <a id="relay"></a>
153 
+    <h2><a class="anchor" href="#relay">Step Four: Configure it as a relay</a></h2>
154 
+    <br />
155 
+
156 
+    <p>The Tor network relies on volunteers to donate bandwidth. The more
157 
+    people who run relays, the faster the Tor network will be. If you have
158 
+    at least 20 kilobytes/s each way, please help out Tor by configuring your
159 
+    Tor to be a relay too. We have many features that make Tor relays easy
160 
+    and convenient, including rate limiting for bandwidth, exit policies so
161 
+    you can limit your exposure to abuse complaints, and support for dynamic
162 
+    IP addresses.</p>
163 
+
164 
+    <p>Having relays in many different places on the Internet is what
165 
+    makes Tor users secure. <a
166 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">You
167 
+    may also get stronger anonymity yourself</a>,
168 
+    since remote sites can't know whether connections originated at your
169 
+    computer or were relayed from others.</p>
170 
+
171 
+    <p>Read more at our <a href="<page docs/tor-doc-relay>">Configuring a relay</a>
172 
+    guide.</p>
173 
+
174 
+    <hr />
175 
+
176 
+    <p>If you have suggestions for improving this document, please <a
177 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
178 
+  </div>
179 
+  <!-- END MAINCOL -->
180 
+  <div id = "sidecol">
181 
+#include "side.wmi"
182 
+#include "info.wmi"
183 
+  </div>
184 
+  <!-- END SIDECOL -->
185 
+</div>
186 
+<!-- END CONTENT -->
187 
+#include <foot.wmi>
docs/en/tor-hidden-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,274 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22314 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configuring Hidden Services for <a href="<page home>">Tor</a></h1>
14 
+    <hr />
15 
+
16 
+    <p>Tor allows clients and relays to offer hidden services. That is,
17 
+    you can offer a web server, SSH server, etc., without revealing your
18 
+    IP address to its users. In fact, because you don't use any public address,
19 
+    you can run a hidden service from behind your firewall.
20 
+    </p>
21 
+
22 
+    <p>If you have Tor installed, you can see hidden services
23 
+    in action by visiting <a href="http://duskgytldkxiuqc6.onion/">our
24 
+    example hidden service</a>.
25 
+    </p>
26 
+
27 
+    <p>This howto describes the steps for setting up your own hidden service
28 
+    website. For the technical details of how the hidden service protocol
29 
+    works, see our <a href="<page docs/hidden-services>">hidden service protocol</a> page.
30 
+    </p>
31 
+
32 
+    <hr />
33 
+    <a id="zero"></a>
34 
+    <h2><a class="anchor" href="#zero">Step Zero: Get Tor working</a></h2>
35 
+    <br />
36 
+
37 
+    <p>Before you start, you need to make sure:</p>
38 
+    <ol>
39 
+    <li>Tor is up and running,</li>
40 
+    <li>You actually set it up correctly.</li>
41 
+    </ol>
42 
+
43 
+
44 
+    <p>Windows users should follow the <a
45 
+    href="<page docs/tor-doc-windows>">Windows
46 
+    howto</a>, OS X users should follow the <a
47 
+    href="<page docs/tor-doc-osx>">OS
48 
+    X howto</a>, and Linux/BSD/Unix users should follow the <a
49 
+    href="<page docs/tor-doc-unix>">Unix howto</a>.
50 
+    </p>
51 
+
52 
+    <p>Once you've got Tor installed and configured,
53 
+    you can see hidden services in action by following this link to <a
54 
+    href="http://duskgytldkxiuqc6.onion/">our example hidden service</a>
55 
+    or the <a
56 
+    href="http://gaddbiwdftapglkq.onion/">Wikileaks hidden service</a>.
57 
+    It will typically take 10-60 seconds to load
58 
+    (or to decide that it is currently unreachable). If it fails
59 
+    immediately and your browser pops up an alert saying that
60 
+    "www.duskgytldkxiuqc6.onion could not be found, please check the name and
61 
+    try again" then you haven't configured Tor correctly; see <a
62 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">the
63 
+    it-doesn't-work FAQ entry</a> for some help.
64 
+    </p>
65 
+
66 
+    <hr />
67 
+    <a id="one"></a>
68 
+    <h2><a class="anchor" href="#one">Step One: Install a web server locally</a></h2>
69 
+    <br />
70 
+
71 
+    <p>First, you need to set up a web server locally. Setting up a web
72 
+    server can be tricky,
73 
+    so we're just going to go over a few basics here. If you get stuck
74 
+    or want to do more, find a friend who can help you. We recommend you
75 
+    install a new separate web server for your hidden service, since even
76 
+    if you already have one installed, you may be using it (or want to use
77 
+    it later) for an actual website.
78 
+    </p>
79 
+
80 
+    <p>If you're on Unix or OS X and you're comfortable with
81 
+    the command-line, by far the best way to go is to install <a
82 
+    href="http://www.acme.com/software/thttpd/">thttpd</a>. Just grab the
83 
+    latest tarball, untar it (it will create its own directory), and run
84 
+    <kbd>./configure &amp;&amp; make</kbd>. Then <kbd>mkdir hidserv; cd
85 
+    hidserv</kbd>, and run
86 
+    <kbd>../thttpd -p 5222 -h localhost</kbd>. It will give you back your prompt,
87 
+    and now you're running a webserver on port 5222. You can put files to
88 
+    serve in the hidserv directory.
89 
+    </p>
90 
+
91 
+    <p>If you're on Windows, you might pick <a
92 
+    href="http://savant.sourceforge.net/">Savant</a> or <a
93 
+    href="http://httpd.apache.org/">Apache</a>, and be sure to configure it
94 
+    to bind only to localhost. You should also figure out what port you're
95 
+    listening on, because you'll use it below.
96 
+    </p>
97 
+
98 
+    <p>(The reason we bind the web server only to localhost is to make
99 
+    sure it isn't publically accessible. If people could get to it directly,
100 
+    they could confirm that your computer is the one offering the hidden
101 
+    service.)
102 
+    </p>
103 
+
104 
+    <p>Once you've got your web server set up, make sure it works: open your
105 
+    browser and go to <a
106 
+    href="http://localhost:5222/">http://localhost:5222/</a>, where 5222 is
107 
+    the port that you picked above. Then try putting a file in the main html
108 
+    directory, and make sure it shows up when you access the site.
109 
+    </p>
110 
+
111 
+    <hr />
112 
+    <a id="two"></a>
113 
+    <h2><a class="anchor" href="#two">Step Two: Configure your hidden service</a></h2>
114 
+    <br />
115 
+
116 
+    <p>Next, you need to configure your hidden service to point to your
117 
+    local web server.
118 
+    </p>
119 
+
120 
+    <p>First, open your torrc file in your favorite text editor. (See <a
121 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">the
122 
+    torrc FAQ entry</a> to learn what this means.) Go to the middle section and
123 
+    look for the line</p>
124 
+
125 
+    <pre>
126 
+    \############### This section is just for location-hidden services ###
127 
+    </pre>
128 
+
129 
+    <p>
130 
+    This section of the file consists of groups of lines, each representing
131 
+    one hidden service. Right now they are all commented out (the lines
132 
+    start with #), so hidden services are disabled. Each group of lines
133 
+    consists of one <var>HiddenServiceDir</var> line, and one or more
134 
+    <var>HiddenServicePort</var> lines:</p>
135 
+    <ul>
136 
+    <li><var>HiddenServiceDir</var> is a directory where Tor will store information
137 
+    about that hidden service.  In particular, Tor will create a file here named
138 
+    <var>hostname</var> which will tell you the onion URL.  You don't need to
139 
+    add any files to this directory. Make sure this is not the same directory
140 
+    as the hidserv directory you created when setting up thttpd, as your
141 
+    HiddenServiceDir contains secret information!</li>
142 
+    <li><var>HiddenServicePort</var> lets you specify a virtual port (that is, what
143 
+    port people accessing the hidden service will think they're using) and an
144 
+    IP address and port for redirecting connections to this virtual port.</li>
145 
+    </ul>
146 
+
147 
+    <p>Add the following lines to your torrc:
148 
+    </p>
149 
+
150 
+    <pre>
151 
+    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
152 
+    HiddenServicePort 80 127.0.0.1:5222
153 
+    </pre>
154 
+
155 
+    <p>You're going to want to change the <var>HiddenServiceDir</var> line, so it points
156 
+    to an actual directory that is readable/writeable by the user that will
157 
+    be running Tor. The above line should work if you're using the OS X Tor
158 
+    package. On Unix, try "/home/username/hidden_service/" and fill in your own
159 
+    username in place of "username". On Windows you might pick:</p>
160 
+    <pre>
161 
+    HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\\
162 
+    HiddenServicePort 80 127.0.0.1:5222
163 
+    </pre>
164 
+
165 
+    <p>Now save the torrc, shut down
166 
+    your Tor, and then start it again.
167 
+    </p>
168 
+
169 
+    <p>If Tor starts up again, great. Otherwise, something is wrong. First look at
170 
+    your logfiles for hints. It will print some warnings or error messages. That
171 
+    should give you an idea what went wrong. Typically there are typos in the torrc
172 
+    or wrong directory permissions (See <a
173 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">the
174 
+    logging FAQ entry</a> if you don't know how to enable or find your
175 
+    log file.)
176 
+    </p>
177 
+
178 
+    <p>When Tor starts, it will automatically create the <var>HiddenServiceDir</var>
179 
+    that you specified (if necessary), and it will create two files there.</p>
180 
+
181 
+    <dl>
182 
+    <dt><var>private_key</var></dt>
183 
+    <dd>First, Tor will generate a new public/private keypair for your hidden
184 
+    service. It is written into a file called "private_key". Don't share this key
185 
+    with others -- if you do they will be able to impersonate your hidden
186 
+    service.</dd>
187 
+    <dt><var>hostname</var></dt>
188 
+    <dd>The other file Tor will create is called "hostname". This contains
189 
+    a short summary of your public key -- it will look something like
190 
+    <tt>duskgytldkxiuqc6.onion</tt>. This is the public name for your service,
191 
+    and you can tell it to people, publish it on websites, put it on business
192 
+    cards, etc.</dd>
193 
+    </dl>
194 
+
195 
+    <p>If Tor runs as a different user than you, for example on
196 
+    OS X, Debian, or Red Hat, then you may need to become root to be able
197 
+    to view these files.</p>
198 
+
199 
+    <p>Now that you've restarted Tor, it is busy picking introduction points
200 
+    in the Tor network, and generating a <em>hidden service
201 
+    descriptor</em>. This is a signed list of introduction points along with
202 
+    the service's full public key. It anonymously publishes this descriptor
203 
+    to the directory servers, and other people anonymously fetch it from the
204 
+    directory servers when they're trying to access your service.
205 
+    </p>
206 
+
207 
+    <p>Try it now: paste the contents of the hostname file into your web
208 
+    browser. If it works, you'll get the html page you set up in step one.
209 
+    If it doesn't work, look in your logs for some hints, and keep playing
210 
+    with it until it works.
211 
+    </p>
212 
+
213 
+    <hr />
214 
+    <a id="three"></a>
215 
+    <h2><a class="anchor" href="#three">Step Three: More advanced tips</a></h2>
216 
+    <br />
217 
+
218 
+    <p>If you plan to keep your service available for a long time, you might
219 
+    want to make a backup copy of the <var>private_key</var> file somewhere.
220 
+    </p>
221 
+
222 
+    <p>We avoided recommending Apache above, a) because many people might
223 
+    already be running it for a public web server on their computer, and b)
224 
+    because it's big
225 
+    and has lots of places where it might reveal your IP address or other
226 
+    identifying information, for example in 404 pages. For people who need
227 
+    more functionality, though, Apache may be the right answer. Can
228 
+    somebody make us a checklist of ways to lock down your Apache when you're
229 
+    using it as a hidden service? Savant probably has these problems too.
230 
+    </p>
231 
+
232 
+    <p>If you want to forward multiple virtual ports for a single hidden
233 
+    service, just add more <var>HiddenServicePort</var> lines.
234 
+    If you want to run multiple hidden services from the same Tor
235 
+    client, just add another <var>HiddenServiceDir</var> line. All the following
236 
+    <var>HiddenServicePort</var> lines refer to this <var>HiddenServiceDir</var> line, until
237 
+    you add another <var>HiddenServiceDir</var> line:
238 
+    </p>
239 
+
240 
+    <pre>
241 
+    HiddenServiceDir /usr/local/etc/tor/hidden_service/
242 
+    HiddenServicePort 80 127.0.0.1:8080
243 
+
244 
+    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
245 
+    HiddenServicePort 6667 127.0.0.1:6667
246 
+    HiddenServicePort 22 127.0.0.1:22
247 
+    </pre>
248 
+
249 
+    <p>There are some anonymity issues you should keep in mind too:
250 
+    </p>
251 
+    <ul>
252 
+    <li>As mentioned above, be careful of letting your web server reveal
253 
+    identifying information about you, your computer, or your location.
254 
+    For example, readers can probably determine whether it's thttpd or
255 
+    Apache, and learn something about your operating system.</li>
256 
+    <li>If your computer isn't online all the time, your hidden service
257 
+    won't be either. This leaks information to an observant adversary.</li>
258 
+    <!-- increased risks over time -->
259 
+    </ul>
260 
+
261 
+    <hr />
262 
+
263 
+    <p>If you have suggestions for improving this document, please <a
264 
+    href="<page about/contact>">send them to us</a>. Thanks!</p>
265 
+  </div>
266 
+  <!-- END MAINCOL -->
267 
+  <div id = "sidecol">
268 
+#include "side.wmi"
269 
+#include "info.wmi"
270 
+  </div>
271 
+  <!-- END SIDECOL -->
272 
+</div>
273 
+<!-- END CONTENT -->
274 
+#include <foot.wmi>
docs/en/tor-manual-dev.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,30 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21567 $
3 
+
4 
+#include "head.wmi" TITLE="Tor Project: manual"
5 
+
6 
+# Translators shouldn't translate this file, unless they want
7 
+# to translate the whole man page too.
8 
+<div id="content" class="clearfix">
9 
+  <div id="breadcrumbs">
10 
+    <a href="<page home>">Home &raquo; </a>
11 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
12 
+    <a href="<page docs/tor-doc-osx>">Tor Dev Manual</a>
13 
+  </div>
14 
+  <div id="maincol">
15 
+    <:
16 
+    	die "Missing git clone at $(TORGIT)" unless -d "$(TORGIT)";
17 
+    	my $man = `GIT_DIR=$(TORGIT) git show $(DEVTAG):doc/tor.1.txt | asciidoc -d manpage -s -o - -`;
18 
+    	die "No manpage because of asciidoc error or file not available from git" unless $man;
19 
+    	print $man;
20 
+    :>
21 
+  </div>
22 
+  <!-- END MAINCOL -->
23 
+  <div id = "sidecol">
24 
+#include "side.wmi"
25 
+#include "info.wmi"
26 
+  </div>
27 
+  <!-- END SIDECOL -->
28 
+</div>
29 
+<!-- END CONTENT -->
30 
+#include <foot.wmi>
docs/en/tor-manual.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,37 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 13768 $
3 
+
4 
+#include "head.wmi" TITLE="Tor Project: manual"
5 
+
6 
+# Translators shouldn't translate this file, unless they want
7 
+# to translate the whole man page too.
8 
+
9 
+<div id="content" class="clearfix">
10 
+  <div id="breadcrumbs">
11 
+    <a href="<page home>">Home &raquo; </a>
12 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
13 
+    <a href="<page docs/tor-doc-osx>">Tor Manual</a>
14 
+  </div>
15 
+  <div id="maincol">
16 
+    <:
17 
+    	#die "Missing manpage" unless -f "$(TORSVNSTABLE)/doc/tor.1.txt";
18 
+    	die "Missing manpage" unless -f "$(TORSVNSTABLE)/doc/tor.1.in";
19 
+    	my $man = `man2html -M '' $(TORSVNSTABLE)/doc/tor.1.in`;
20 
+    	#my $man = `man2html -M '' $(TORSVNSTABLE)/doc/tor.1.txt`;
21 
+    	die "No manpage" unless $man;
22 
+
23 
+    	$man =~ s,.*<body>,,is;
24 
+    	$man =~ s,</body>.*,,is;
25 
+
26 
+    	print $man;
27 
+    :>
28 
+  </div>
29 
+  <!-- END MAINCOL -->
30 
+  <div id = "sidecol">
31 
+#include "side.wmi"
32 
+#include "info.wmi"
33 
+  </div>
34 
+  <!-- END SIDECOL -->
35 
+</div>
36 
+<!-- END CONTENT -->
37 
+#include <foot.wmi>
docs/en/trademark-faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,93 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22138 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Trademark FAQ" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/trademark-faq>">Trademark FAQ</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+    <h1>Tor Trademark Frequently Asked Questions</h1>
15 
+    <hr />
16 
+
17 
+    <a id="usage"></a>
18 
+    <h2>How can I use the name "Tor"?</h2>
19 
+    <p>The Tor Project encourages developers to use the name Tor in ways that
20 
+    do not confuse the public about the source of anonymity software and
21 
+    services.  If you are building open-source non-commercial software or
22 
+    services that incorporate or work with The Tor Project's code, you may
23 
+    use the name “Tor” in an accurate description of your work.  We ask you
24 
+    to include a link to the official Tor website
25 
+    <a href="https://www.torproject.org/">https://www.torproject.org/</a> so users can verify the original source of
26 
+    Tor for themselves, and a note indicating that your project is not
27 
+    sponsored by The Tor Project. For example, “This product is produced
28 
+    independently from the Tor&#174; anonymity software and carries no guarantee
29 
+    from The Tor Project about quality, suitability or anything else.”</p>
30 
+
31 
+    <a id="onionlogo"></a>
32 
+    <h2>Can I use the Tor onion logo?</h2>
33 
+    <p>If you're making non-commercial use of Tor software, you may also use
34 
+    the Tor onion logo (as an illustration, not as a brand for your
35 
+    products).  Please don't modify the design or colors of the logo.  You
36 
+    can use items that look like the Tor onion logo to illustrate a point
37 
+    (e.g. an exploded onion with layers, for instance), so long as they're
38 
+    not used as logos in ways that would confuse people.</p>
39 
+
40 
+    <a id="combining"></a>
41 
+    <h2>Can I use the word "Tor" as part of the name of my product or my domain name?</h2>
42 
+    <p>We recommend that you don't do this, but rather find a name that will
43 
+    accurately identify <i>your</i> products or services.  Remember that our goal
44 
+    is to make sure that people aren't confused about whether your product
45 
+    or project is made or endorsed by The Tor Project. Creating a new brand
46 
+    that incorporates the Tor brand is likely to lead to confusion.</p>
47 
+
48 
+    <a id="enforcing"></a>
49 
+    <h2>Does this mean you're enforcing trademark rights?</h2>
50 
+    <p>The Tor Project is a non-profit corporation organized to research and
51 
+    develop the Tor anonymity software and network.  We don't want to be
52 
+    trademark bullies, but we will use trademark to protect the public's
53 
+    ability to recognize Tor Project software.  Trademark law helps us to assure
54 
+    that the name is used only in connection with genuine Tor anonymity
55 
+    software and for accurate description of software and services.
56 
+    After all, to protect their anonymity securely, computer users must be
57 
+    able to identify the software they are using, so they can account
58 
+    properly for its strengths and weaknesses.  Tor has become well-known as
59 
+    a software package and associated network of onion-routing anonymizing
60 
+    proxies, with online documentation, instructions for strengthening
61 
+    anonymity protection, and warnings that even at this stage it remains
62 
+    experimental software.  We work with developers to improve the software
63 
+    and network and actively encourage researchers to document attacks to
64 
+    help us strengthen its anonymity protection further.  We distribute the
65 
+    software itself freely, but require correct attribution. </p>
66 
+
67 
+    <a id="commercial"></a>
68 
+    <h2>What if I produce non-open source, commercial products based on
69 
+    Tor?</h2>
70 
+    <p>Contact us, and let's talk.</p>
71 
+
72 
+    <a id="licensee"></a>
73 
+    <h2>Are there official licensees of the Tor trademarks?</h2>
74 
+    <p>Yes.  A few open source, non-commercial projects are Tor trademark
75 
+    licensees:</p>
76 
+    <ul>
77 
+    <li><a href="https://amnesia.boum.org/">The (Amnesic) Incognito Live
78 
+    System</a></li>
79 
+    <li><a href="http://portabletor.sourceforge.net/">Portable Tor</a></li>
80 
+    <li><a href="http://torstatus.kgprog.com/">Kprog Tor Status</a></li>
81 
+    <li><a href="<page projects/vidalia>">Vidalia</a></li>
82 
+    <li><a href="http://www.anonymityanywhere.com/tork/">TorK</a></li>
83 
+    </ul>
84 
+  </div>
85 
+  <!-- END MAINCOL -->
86 
+  <div id = "sidecol">
87 
+#include "side.wmi"
88 
+#include "info.wmi"
89 
+  </div>
90 
+  <!-- END SIDECOL -->
91 
+</div>
92 
+<!-- END CONTENT -->
93 
+#include <foot.wmi>
docs/en/verifying-signatures.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,208 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22418 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Verifying Signatures" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/verifying-signatures>">Verifying Signatures</a>
10 
+  </div>
11 
+  <div id="maincol">
12 
+    <h1>How to verify signatures for packages</h1>
13 
+    <hr />
14 
+
15 
+    <p>Each file on <a href="<page download/download>">our download page</a> is accompanied
16 
+    by a file with the same name as the package and the extension
17 
+    ".asc". These .asc files are GPG signatures. They allow you to verify
18 
+    the file you've downloaded is exactly the one that we intended you to
19 
+    get. For example, vidalia-bundle-0.2.1.25-0.2.7.exe is accompanied by
20 
+    vidalia-bundle-0.2.1.25-0.2.7.exe.asc.</p>
21 
+
22 
+    <p>Of course, you'll need to have our GPG keys in your keyring: if you don't
23 
+    know the GPG key, you can't be sure that it was really us who signed it. The
24 
+    signing keys we use are:</p>
25 
+    <ul>
26 
+    <li>Roger's (0x28988BF5) typically signs the source code file.</li>
27 
+    <li>Nick's (0x165733EA, or its subkey 0x8D29319A).</li>
28 
+    <li>Andrew's (0x31B0974B) typically signs packages for windows and mac.</li>
29 
+    <li>Peter's (0x94C09C7F, or its subkey 0xAFA44BDD).</li>
30 
+    <li>Matt's (0x5FA14861).</li>
31 
+    <li>Jacob's (0xE012B42D).</li>
32 
+    <li>Erinn's (0x63FEE659) and (0xF1F5C9B5) typically signs the linux packages.</li>
33 
+    <li>Mike's (0xDDC6C0AD) signs the Torbutton xpi.</li>
34 
+    </ul>
35 
+
36 
+    <h3>Step Zero: Install GnuPG</h3>
37 
+    <hr />
38 
+    <p>You need to have GnuPG installed before you can verify
39 
+    signatures.</p>
40 
+
41 
+    <ul>
42 
+    <li>Linux: see <a
43 
+    href="http://www.gnupg.org/download/">http://www.gnupg.org/download/</a>
44 
+    or install <i>gnupg</i> from the package management system.</li>
45 
+    <li>Windows: see <a
46 
+    href="http://www.gnupg.org/download/">http://www.gnupg.org/download/</a>. Look
47 
+    for the "version compiled for MS-Windows" under "Binaries".</li>
48 
+    <li>Mac: see <a
49 
+    href="http://macgpg.sourceforge.net/">http://macgpg.sourceforge.net/</a>.</li>
50 
+    </ul>
51 
+
52 
+    <h3>Step One:  Import the keys</h3>
53 
+    <hr />
54 
+    <p>The next step is to import the key. This can be done directly from
55 
+    GnuPG. Make sure you import the correct key. For example, if you
56 
+    downloaded a Windows package, you will need to import Andrew's key.</p>
57 
+
58 
+    <p><b>Windows:</b></p>
59 
+    <p>GnuPG for Windows is a command line tool, and you will need to use
60 
+    <i>cmd.exe</i>. Unless you edit your PATH environment variable, you will
61 
+    need to tell Windows the full path to the GnuPG program. If you installed GnuPG
62 
+    with the default values, the path should be something like this: <i>C:\Program
63 
+    Files\Gnu\GnuPg\gpg.exe</i>.</p>
64 
+
65 
+    <p>To import the key 0x28988BF5, start <i>cmd.exe</i> and type:</p>
66 
+
67 
+    <pre>C:\Program Files\Gnu\GnuPg\gpg.exe --recv-keys 0x28988BF5</pre>
68 
+
69 
+    <p><b>Mac and Linux</b></p>
70 
+    <p>Whether you have a Mac or you run Linux, you will need to use the terminal
71 
+    to run GnuPG. Mac users can find the terminal under "Applications". If you run
72 
+    Linux and use Gnome, the terminal should be under "Applications menu" and
73 
+    "Accessories". KDE users can find the terminal under "Menu" and "System".</p>
74 
+
75 
+    <p>To import the key 0x28988BF5, start the terminal and type:</p>
76 
+
77 
+    <pre>gpg --recv-keys 0x28988BF5</pre>
78 
+
79 
+    <h3>Step Two:  Verify the fingerprints</h3>
80 
+    <hr />
81 
+    <p>After importing the key, you will want to verify that the fingerprint is correct.</p>
82 
+
83 
+    <p><b>Windows:</b></p>
84 
+    <pre>C:\Program Files\Gnu\GnuPg\gpg.exe --fingerprint (insert keyid here)</pre>
85 
+
86 
+    <p><b>Mac and Linux</b></p>
87 
+    <pre>gpg --fingerprint (insert keyid here)</pre>
88 
+
89 
+    The fingerprints for the keys should be:
90 
+
91 
+    <pre>
92 
+    pub   1024D/28988BF5 2000-02-27
93 
+          Key fingerprint = B117 2656 DFF9 83C3 042B  C699 EB5A 896A 2898 8BF5
94 
+    uid                  Roger Dingledine &lt;arma@mit.edu&gt;
95 
+
96 
+    pub   3072R/165733EA 2004-07-03
97 
+          Key fingerprint = B35B F85B F194 89D0 4E28  C33C 2119 4EBB 1657 33EA
98 
+    uid                  Nick Mathewson &lt;nickm@alum.mit.edu&gt;
99 
+    uid                  Nick Mathewson &lt;nickm@wangafu.net&gt;
100 
+    uid                  Nick Mathewson &lt;nickm@freehaven.net&gt;
101 
+
102 
+    pub  1024D/31B0974B 2003-07-17
103 
+         Key fingerprint = 0295 9AA7 190A B9E9 027E  0736 3B9D 093F 31B0 974B
104 
+    uid                  Andrew Lewman (phobos) &lt;phobos@rootme.org&gt;
105 
+    uid                  Andrew Lewman &lt;andrew@lewman.com&gt;
106 
+    uid                  Andrew Lewman &lt;andrew@torproject.org&gt;
107 
+    sub   4096g/B77F95F7 2003-07-17
108 
+
109 
+    pub   1024D/94C09C7F 1999-11-10
110 
+          Key fingerprint = 5B00 C96D 5D54 AEE1 206B  AF84 DE7A AF6E 94C0 9C7F
111 
+    uid                  Peter Palfrader
112 
+    uid                  Peter Palfrader &lt;peter@palfrader.org&gt;
113 
+    uid                  Peter Palfrader &lt;weasel@debian.org&gt;
114 
+
115 
+    pub   1024D/5FA14861 2005-08-17
116 
+          Key fingerprint = 9467 294A 9985 3C9C 65CB  141D AF7E 0E43 5FA1 4861
117 
+    uid                  Matt Edman &lt;edmanm@rpi.edu&gt;
118 
+    uid                  Matt Edman &lt;Matt_Edman@baylor.edu&gt;
119 
+    uid                  Matt Edman &lt;edmanm2@cs.rpi.edu&gt;
120 
+    sub   4096g/EA654E59 2005-08-17
121 
+
122 
+    pub   1024D/9D0FACE4 2008-03-11 [expires: 2010-10-07]
123 
+          Key fingerprint = 12E4 04FF D3C9 31F9 3405  2D06 B884 1A91 9D0F ACE4
124 
+    uid                  Jacob Appelbaum &lt;jacob@appelbaum.net&gt;
125 
+    sub   4096R/F8D04B59 2010-03-11 [expires: 2010-10-07]
126 
+
127 
+    pub   2048R/63FEE659 2003-10-16
128 
+          Key fingerprint = 8738 A680 B84B 3031 A630  F2DB 416F 0610 63FE E659
129 
+    uid                  Erinn Clark &lt;erinn@torproject.org&gt;
130 
+    uid                  Erinn Clark &lt;erinn@debian.org&gt;
131 
+    uid                  Erinn Clark &lt;erinn@double-helix.org&gt;
132 
+    sub   2048R/EB399FD7 2003-10-16
133 
+
134 
+    pub   1024D/F1F5C9B5 2010-02-03
135 
+          Key fingerprint = C2E3 4CFC 13C6 2BD9 2C75  79B5 6B8A AEB1 F1F5 C9B5
136 
+    uid                  Erinn Clark &lt;erinn@torproject.org&gt;
137 
+    sub   1024g/7828F26A 2010-02-03
138 
+
139 
+    pub   1024D/DDC6C0AD 2006-07-26
140 
+          Key fingerprint = BECD 90ED D1EE 8736 7980  ECF8 1B0C A30C DDC6 C0AD
141 
+    uid                  Mike Perry &lt;mikeperry@fscked.org&gt;
142 
+    uid                  Mike Perry &lt;mikepery@fscked.org&gt;
143 
+    sub   4096g/AF0A91D7 2006-07-26
144 
+
145 
+    </pre>
146 
+
147 
+    <h3>Step Three:  Verify the downloaded package</h3>
148 
+    <hr />
149 
+    <p> To verify the signature of the package you downloaded, you will need
150 
+    to download the ".asc" file as well.</p>
151 
+
152 
+    <p>In the following examples, the user Alice downloads packages for
153 
+    Windows, Mac OS X and Linux and also verifies the signature of each
154 
+    package. All files are saved on the desktop.</p>
155 
+
156 
+    <p><b>Windows:</b></p>
157 
+    <pre>C:\Program Files\Gnu\GnuPg\gpg.exe --verify C:\Users\Alice\Desktop\vidalia-bundle-0.2.1.25-0.2.7.exe.asc C:\Users\Alice\Desktop\vidalia-bundle-0.2.1.25-0.2.7.exe</pre>
158 
+
159 
+    <p><b>Mac:</b></p>
160 
+    <pre>gpg --verify /Users/Alice/vidalia-bundle-0.2.1.25-0.2.7-i386.dmg.asc /Users/Alice/vidalia-bundle-0.2.1.25-0.2.7-i386.dmg</pre>
161 
+
162 
+    <p><b>Linux</b></p>
163 
+    <pre>gpg --verify /home/Alice/Desktop/tor-0.2.1.25.tar.gz.asc /home/Alice/Desktop/tor-0.2.1.25.tar.gz</pre>
164 
+
165 
+    <p>After verifying, GnuPG will come back saying something like "Good
166 
+    signature" or "BAD signature". The output should look something like
167 
+    this:</p>
168 
+
169 
+    <pre>
170 
+    gpg: Signature made Tue 16 Mar 2010 05:55:17 AM CET using DSA key ID 28988BF5
171 
+    gpg: Good signature from "Roger Dingledine &lt;arma@mit.edu&gt;"
172 
+    gpg: WARNING: This key is not certified with a trusted signature!
173 
+    gpg:          There is no indication that the signature belongs to the owner.
174 
+    Primary key fingerprint: B117 2656 DFF9 83C3 042B  C699 EB5A 896A 2898 8BF5
175 
+    </pre>
176 
+
177 
+    <p>
178 
+    Notice that there is a warning because you haven't assigned a trust
179 
+    index to this person. This means that GnuPG verified that the key made
180 
+    that signature, but it's up to you to decide if that key really belongs
181 
+    to the developer. The best method is to meet the developer in person and
182 
+    exchange key fingerprints.
183 
+    </p>
184 
+
185 
+    <p>For your reference, this is an example of a <em>BAD</em> verification. It
186 
+    means that the signature and file contents do not match. In this case,
187 
+    you should not trust the file contents:</p>
188 
+
189 
+    <pre>
190 
+    gpg: Signature made Tue 20 Apr 2010 12:22:32 PM CEST using DSA key ID 28988BF5
191 
+    gpg: BAD signature from "Roger Dingledine &lt;arma@mit.edu&gt;"
192 
+    </pre>
193 
+
194 
+    <p>If you are running Tor on Debian you should read the instructions on
195 
+    <a href="<page docs/debian>#packages">importing these keys to apt</a>.</p>
196 
+
197 
+    <p>If you wish to learn more about GPG, see <a
198 
+    href="http://www.gnupg.org/documentation/">http://www.gnupg.org/documentation/</a>.</p>
199 
+  </div>
200 
+  <!-- END MAINCOL -->
201 
+  <div id = "sidecol">
202 
+#include "side.wmi"
203 
+#include "info.wmi"
204 
+  </div>
205 
+  <!-- END SIDECOL -->
206 
+</div>
207 
+<!-- END CONTENT -->
208 
+#include <foot.wmi>
docs/es/debian-vidalia.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,116 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22269 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Vidalia: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian-vidalia>">Vidalia Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a> <a id="packages"></a>
14 
+    <h2><a class="anchor" href="#debian">Vidalia en Ubuntu o Debian</a></h2>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>No utilizar los paquetes en el universo de Ubuntu.</ b> Son Unmaintained
19 
+    y fuera de fecha. Eso significa que se le falta estabilidad y parches de
20 
+    seguridad.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    You'll need to set up our package repository before you can fetch
25 
+    Vidalia. First, you need to figure out the name of your distribution. If
26 
+    you're using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty",
27 
+    8.10 is "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's
28 
+    "etch", and Debian Lenny is "lenny". Then add this line to your
29 
+    <tt>/etc/apt/sources.list</tt> file:<br />
30 
+    <pre>
31 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
32 
+    </pre>
33 
+    en la que sustituir la palabra por encima de (etch, lenny, sid, kármica,
34 
+    alegre, intrépido, fuerte) en lugar de &lt;DISTRIBUCIÓN&gt;
35 
+    </p>
36 
+
37 
+    <p>
38 
+    Then add the gpg key used to sign the packages by running the following
39 
+    commands at your command prompt:
40 
+    <pre>
41 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
42 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
43 
+    </pre>
44 
+    Now refresh your sources and install Vidalia by running the following
45 
+    commands at your command prompt:
46 
+    <pre>
47 
+    apt-get update
48 
+    apt-get install vidalia
49 
+    </pre>
50 
+    </p>
51 
+
52 
+    <p>
53 
+    Now Vidalia is installed and running. Move on to <a href="<page
54 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Vidalia on Linux/Unix"
55 
+    instructions.
56 
+    </p>
57 
+
58 
+    <p style="font-size: small">
59 
+    El nombre DNS <code>deb.torproject.org</code> es en realidad un conjunto de
60 
+    servidores independientes en un petirrojo ronda de configuración de DNS. Si
61 
+    por alguna razón no pueden acceder a él puede intentar utilizar el nombre de
62 
+    uno de su parte en su lugar. Intentar
63 
+    <code>deb-master.torproject.org</code>, <code>mirror.netcologne.de</code> o
64 
+    <code>vidalia.mirror.youam.de</code>.
65 
+    </p>
66 
+
67 
+    <hr /> <a id="source"></a>
68 
+    <h2><a class="anchor" href="#source">Edificio de la fuente</a></h2>
69 
+    <br />
70 
+
71 
+    <p>
72 
+    Si desea construir su propia debs de la fuente, primero debe agregar una
73 
+    línea adecuada <tt>deb-src</ tt> para <tt>sources.list</tt>.
74 
+    <pre>
75 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUCIÓN&gt; main
76 
+    </pre>
77 
+    También es necesario instalar los paquetes necesarios para construir su
78 
+    propia Debs y los paquetes necesarios para construir Vidalia:
79 
+    <pre>
80 
+    apt-get install build-essential fakeroot devscripts qt4-dev-tools qt4-designer libqt4-dev g++ cmake
81 
+    apt-get build-dep vidalia
82 
+    </pre>
83 
+    Entonces usted puede construir en Vidalia ~/debian-packages:
84 
+    <pre>
85 
+    mkdir ~/debian-packages; cd ~/debian-packages
86 
+    apt-get source vidalia
87 
+    cd vidalia-*
88 
+    debuild -rfakeroot -uc -us
89 
+    cd ..
90 
+    </pre>
91 
+    Ahora usted puede instalar el nuevo paquete:
92 
+    <pre>
93 
+    sudo dpkg -i vidalia_*.deb
94 
+    </pre>
95 
+    </p>
96 
+
97 
+    <p>
98 
+    Now Vidalia is installed and running. Move on to <a href="<page
99 
+    docs/tor-doc-unix>#polipo">step two</a> of the "Vidalia on Linux/Unix"
100 
+    instructions.
101 
+    </p>
102 
+
103 
+    <hr />
104 
+
105 
+    <p>Si tiene sugerencias para mejorar este documento, por favor <a href="<page
106 
+    about/contact>">envíanoslas</a>. Gracias!</p>
107 
+  </div>
108 
+  <!-- END MAINCOL -->
109 
+  <div id = "sidecol">
110 
+#include "side.wmi"
111 
+#include "info.wmi"
112 
+  </div>
113 
+  <!-- END SIDECOL -->
114 
+</div>
115 
+<!-- END CONTENT -->
116 
+#include <foot.wmi>
docs/es/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/es/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,210 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Ejecución de la cliente<a href="<page index>">Tor</a> en Mac OS X</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Tenga en cuenta que estas son las instrucciones de instalación para
18 
+    ejecutar un cliente Tor en Mac OS X. Si quiere retransmitir tráfico para
19 
+    otros y ayudar a crecer la red (por favor), lee la guía <a href="<page
20 
+    docs/tor-doc-relay>">Configurar un repetidor</a>.</b>
21 
+    </p>
22 
+
23 
+    <hr />
24 
+    <a id="installing"></a>
25 
+    <h2><a class="anchor" href="#installing">Paso Uno: Descargar e Instalar Tor</a></h2>
26 
+    <br />
27 
+
28 
+    <p>
29 
+    The install for Macintosh OS X bundles <a href="<page index>">Tor</a>, <a
30 
+    href="<page projects/vidalia>">Vidalia</a> (a graphical interface for Tor), <a
31 
+    href="<page projects/torbutton>">Torbutton</a>, and <a
32 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (a web
33 
+    proxy)  into one package, with the four applications pre-configured to work
34 
+    together.  Download either the <a
35 
+    href="../<package-osx-bundle-stable>">stable</a> or the <a
36 
+    href="../<package-osx-bundle-alpha>">experimental</a> version of the OS X
37 
+    bundle for Intel, or look for more options on the <a href="<page
38 
+    download/download>">download page</a>.
39 
+    </p>
40 
+
41 
+    <p>Una vez que haya descargado el dmg, haga doble clic y se deja montar. Busque
42 
+    el paquete Vidalia abierto en el Finder. Es fácil de instalar el paquete,
43 
+    simplemente arrastre y suelte el icono de la cebolla Vidalia a la carpeta
44 
+    Aplicaciones. Opcionalmente, haga doble clic en "Instalar Torbutton" script
45 
+    y permitir que se instale Torbutton en Firefox. También puede obtener
46 
+    Torbutton de Mozilla Add-ons al buscar "Torbutton".</p>
47 
+
48 
+    <p>Cuando haya terminado la instalación, puede arrancar Vidalia seleccionando
49 
+    su icono de la carpeta Aplicaciones. Una cebolla oscura con una X roja en su
50 
+    Dock significa que Tor no está actualmente en ejecución. Puede iniciar Tor
51 
+    seleccionando Start desde el menu "Tor" en la parte superior de la pantalla.
52 
+    </p>
53 
+
54 
+    <p>Cuando Tor se está ejecutando, el icono de Vidalia se verá como la
55 
+    siguiente:
56 
+    </p>
57 
+
58 
+    <p><img alt="vidalia running tor"
59 
+    src="../img/screenshot-osx-vidalia.png"
60 
+    border="1"/></p>
61 
+
62 
+    <p>Polipo se instala como parte del paquete instalador unificado de Tor. Una
63 
+    vez instalado, se iniciará automáticamente cuando se reinicie el
64 
+    equipo. Usted no necesita configurar Polipo para usar Tor - una
65 
+    configuración a medida Polipo para Tor se instala como parte del paquete de
66 
+    instalación.
67 
+    </p>
68 
+
69 
+    <hr />
70 
+    <a id="using"></a>
71 
+    <h2><a class="anchor" href="#using">Paso Dos: Configurar tus aplicaciones para
72 
+    Tor</a></h2>
73 
+    <br />
74 
+
75 
+    <p>Después de la instalación, necesita configurar sus aplicaciones para
76 
+    usarlos. El primer paso es configurar la navegación web.</p>
77 
+
78 
+    <p>Usted debe usar Tor con Firefox y Torbutton, para la mejor
79 
+    seguridad. Torbutton fue instalado para usted. Haga clic en el botón rojo
80 
+    "Tor Disabled" para activar Tor, y eso es todo: </p>
81 
+
82 
+    <p><img alt="Torbutton plugin for Firefox"
83 
+    src="../img/screenshot-torbutton.png"
84 
+    border="1"/></p>
85 
+
86 
+    <p>
87 
+    Si planea ejecutar Firefox en un ordenador distinto del de Tor, vea la <a
88 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">entrada
89 
+    de la FAQ para ejecutar Tor en un ordenador distinto</a>.
90 
+    </p>
91 
+
92 
+    <p>Para usar con TOR otras aplicaciones que soportan proxies HTTP, simplemente
93 
+    dirigirlas a Polipo (es decir, localhost, puerto 8118). Para usar SOCKS
94 
+    directamente (para mensajería instantanea, Jabber, IRC, etc), puede apuntar
95 
+    su aplicación directamente a Tor (localhost, puerto 9050), pero vea <a
96 
+    href="https://wiki.torproject.org
97 
+    noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">esta FAQ</a> por qué esto puede
98 
+    ser peligroso. Para aplicaciones que no soportan ni SOCKS ni HTTP, mire <a
99 
+    href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a> o <a
100 
+    href="http://www.dest-unreach.org/socat/">socat</a>.</p>
101 
+
102 
+    <p>Para obtener información sobre cómo usar con TOR otras aplicaciones,
103 
+    compruebe el <a
104 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
105 
+    HOWTO</a>.
106 
+    </p>
107 
+
108 
+    <hr />
109 
+    <a id="verify"></a>
110 
+    <h2><a class="anchor" href="#verify">Paso Tres: Asegurarse de que funciona </a></h2>
111 
+    <br />
112 
+
113 
+    <p>
114 
+    Después, deberías intentar usar tu explorador con Tor y asegurarse de que su
115 
+    dirección IP está siendo anonimizada. Haga clic en <a
116 
+    href="https://check.torproject.org/">el detector de Tor</a> y compruebe si
117 
+    cree que usas Tor o no. (Si el sitio está caído, vea <a
118 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">esta
119 
+    FAQ</ a> para más sugerencias sobre cómo comprobar su Tor.)
120 
+    </p>
121 
+
122 
+    <p>Si tiene un cortafuegos personal que limita la capacidad de su ordenador
123 
+    para conectarse a sí mismo, asegúrate que permite conexiones de aplicaciones
124 
+    locales al puerto local 8118 y al puerto 9050. Si tu cortafuegos bloquea
125 
+    conexiones salientes, abra un agujero para que pueda conectarse al menos a
126 
+    los puertos TCP 80 y 443, y luego vea <a
127 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">esta
128 
+    FAQ</a>.
129 
+    </p>
130 
+
131 
+    <p>Si aún no funciona, mire <a
132 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">esta
133 
+    FAQ</a> para seguir consejos.</p>
134 
+
135 
+    <p>
136 
+    Una vez que funcione, aprender más acerca de <a href="<page
137 
+    download/download>#Warning">lo que hace Tor y no ofrece</a>.
138 
+    </p>
139 
+
140 
+    <hr />
141 
+    <a id="server"></a> <a id="relay"></a>
142 
+    <h2><a class="anchor" href="#relay">Paso Cuatro: Configurarlo como repetidor</a></h2>
143 
+    <br />
144 
+
145 
+    <p>La red Tor se apoya en voluntarios que donen ancho de banda. Cuanta más
146 
+    gente ejecute repetidores, más rápida será la red Tor ser. Si tiene al menos
147 
+    20 kilobytes / s bidireccional, por favor ayuda a Tor configurando su Tor
148 
+    para que sea repetidor también. Tenemos muchas características que hacen los
149 
+    repetidores Tor fáciles y convenientes, incluyendo limitación del ancho de
150 
+    banda, políticas de salida que pueden limitar su exposición a quejas de
151 
+    abuso, y soporte para direcciones IP dinámicas.</p>
152 
+
153 
+    <p>Tener repetidores en muchos sitios diferentes de Internet es lo que hace a
154 
+    los usuarios de Tor seguros. <a
155 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">También
156 
+    puede obtener más anonimato</a>, haciendo que sitios remotos no puedan saber
157 
+    si las conexiones se originaron en su ordenador o fueron reenviadas desde
158 
+    otros.</p>
159 
+
160 
+    <p>Lea más en nuestro guía<a href="<page docs/tor-doc-relay>"> Configurar un
161 
+    repetidor</a>.</p>
162 
+
163 
+    <hr />
164 
+    <a id="uninstall"></a>
165 
+    <h2><a class="anchor" href="#uninstall">Cómo desinstalar Tor y Privoxy</a></h2>
166 
+    <br />
167 
+
168 
+    <p>Hay dos maneras para desinstalar el paquete de su computadora, utilizando
169 
+    Finder o una línea de comandos o terminal basado en programa de
170 
+    desinstalación. Si quiere eliminar Tor en OSX, he aquí cómo:</p>
171 
+
172 
+    <p>Cambiar la configuración del proxy de la aplicación de vuelta a sus valores
173 
+    originales. Si sólo desea dejar de usar Tor, puede detenerse en este punto.</p>
174 
+
175 
+    <p>Si quiere eliminar Tor completamente, y su cuenta tiene privilegios de
176 
+    administrador, proceda como sigue:</p>
177 
+
178 
+    <ol>
179 
+    <li>Abra Finder y haga clic en Aplicaciones.</li>
180 
+    <li>Arrastre/Aplicaciones/Vidalia a la Papelera.</li>
181 
+    <li>Quitar/Library/Torbutton de su sistema.</li>
182 
+    <li>En su directorio principal, vaya a la Biblioteca, quitar el directorio de
183 
+    Vidalia</li>
184 
+    </ol>
185 
+
186 
+    <p>Tor, Vidalia, y Polipo están ahora totalmente eliminados de su sistema.</p>
187 
+
188 
+    <p>Si usted está familiarizado con la línea de comandos o terminal, puede
189 
+    quitar manualmente la siguiente:</p>
190 
+    <ul>
191 
+    <li>/Applications/Vidalia.app/</li>
192 
+    <li>/Library/Torbutton/</li>
193 
+    <li>~/Library/Vidalia</li>
194 
+    <li>~/.tor</li>
195 
+    </ul>
196 
+
197 
+    <hr />
198 
+
199 
+    <p>Si tiene sugerencias para mejorar este documento, por favor<a href="<page
200 
+    about/contact>">envíanoslas</a>. Gracias!</p>
201 
+  </div>
202 
+  <!-- END MAINCOL -->
203 
+  <div id = "sidecol">
204 
+#include "side.wmi"
205 
+#include "info.wmi"
206 
+  </div>
207 
+  <!-- END SIDECOL -->
208 
+</div>
209 
+<!-- END CONTENT -->
210 
+#include <foot.wmi>
docs/es/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,313 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurar un servidor Tor</h1>
14 
+
15 
+
16 
+    <!-- BEGIN SIDEBAR -->
17 
+    <div class="sidebar-left">
18 
+    <h3>Pasos de configuración</h3>
19 
+    <ol>
20 
+    <li><a href="<page docs/tor-doc-relay>#install">Descarga e instalación</a></li>
21 
+    <li><a href="<page docs/tor-doc-relay>#setup">Configuración</a></li>
22 
+    <li><a href="<page docs/tor-doc-relay>#check">Check & Confirmar</a></li>
23 
+    <li><a href="<page docs/tor-doc-relay>#after">Pasos finales</a></li>
24 
+    </ol>
25 
+    </div>
26 
+
27 
+
28 
+    <!-- END SIDEBAR -->
29 
+    <hr />
30 
+
31 
+    <p>
32 
+    La red Tor se apoya en voluntarios que donen ancho de banda. Cuanta más
33 
+    gente ejecute repetidores, más rápida será la red Tor ser. Si tiene al menos
34 
+    20 kilobytes / s bidireccional, por favor ayuda a Tor configurando su Tor
35 
+    para que sea repetidor también. Tenemos muchas características que hacen los
36 
+    repetidores Tor fáciles y convenientes, incluyendo la <a href="<page docs/faq>
37 
+    RelayFlexible">limitación del ancho de banda, políticas de salida para que
38 
+    pueda limitar su exposición a quejas de abuso, y soporte para direcciones IP
39 
+    dinámicas</a>.
40 
+    </p>
41 
+
42 
+    <p>Se puede ejecutar un repetidor Tor en <a
43 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">casi
44 
+    cualquier</a>sistema operativo. Los repetidores Tor funcionan mejor en
45 
+    Linux, OS X Tiger o posterior, 5.x + FreeBSD, NetBSD 5.x +, y Windows Server
46 
+    2003 o posterior.
47 
+    </p>
48 
+
49 
+    <hr /> <a id="zero"></a> <a id="install"></a>
50 
+    <h2><a class="anchor" href="#install">Paso Uno: Descargar e Instalar Tor</a></h2>
51 
+    <br />
52 
+
53 
+    <p>Antes de empezar, es necesario asegurarse de que Tor está activo y
54 
+    ejecutándose.
55 
+    </p>
56 
+
57 
+    <p>Visite nuestro <a href="<page download/easy-download>">página de descarga</a> e
58 
+    instalar el "paquete de instalación" para su sistema operativo.
59 
+    </p>
60 
+
61 
+    <p>Si es oportuno, también podría utilizar como un cliente por un tiempo para
62 
+    asegurarse de que realmente funciona.</p>
63 
+
64 
+    <hr /> <a id="setup"></a>
65 
+    <h2><a class="anchor" href="#setup">Paso Dos: Configurarlo como repetidor</a></h2>
66 
+    <br />
67 
+    <ol>
68 
+    <li>Verifique que su reloj y la zona horaria están configurados
69 
+    correctamente. Si es posible, sincronice su reloj con <a público
70 
+    href="http://en.wikipedia.org/wiki/Network_Time_Protocol">servidores de
71 
+    tiempo</a>.
72 
+    </li>
73 
+
74 
+    <li><strong>Configuración de Tor con la interfaz gráfica de Vidalia</strong>:
75 
+    <ol>
76 
+
77 
+    <li>
78 
+    	<dt>Haga clic derecho sobre el icono de Vidalia en la barra de tareas. Elija
79 
+    <tt>Panel de control</tt>.</dt>
80 
+    	<dd><img alt="vidalia right click menu"
81 
+    src="../img/screenshot-win32-vidalia.png"></dd>
82 
+    </li>
83 
+
84 
+    <li>Haga clic en <tt>Configuración de la retransmisión</tt>.</li>
85 
+
86 
+    <li>
87 
+    	<dt>Elija <tt>tráfico para la red Tor</tt> si desea que sea un repetidor público
88 
+    (recomendado), o elegir 		<tt> Ayuda censurado llegar a los usuarios de la
89 
+    red Tor</tt> si desea una <a href="<page docs/faq>#RelayOrBridge">puente</a> para
90 
+    los usuarios en los países que censuran la Internet.</dt>
91 
+    <dd><img alt="vidalia basic settings"
92 
+    src="../img/screenshot-win32-configure-relay-1.png"></dd>
93 
+    </li>
94 
+
95 
+    <li>Introduzca un alias para su servidor, y escriba la información de contacto
96 
+    en caso de que necesitemos comunicarnos con usted acerca de los problemas.</li>
97 
+
98 
+    <li>Deja <tt>Intenta configurar automáticamente el reenvío de
99 
+    puertos</tt>clic. Empuje el <tt>Test</tt> botón para ver si funciona. Si
100 
+    funciona, estupendo. Si no, véase el número 3.</li>
101 
+
102 
+    <li><dt>Elija el <tt>límites de ancho de banda</tt> ficha. Seleccione la cantidad de
103 
+    ancho de banda que desea proporcionar a los usuarios de Tor como tú.</dt>
104 
+    <dd><img alt="vidalia bandwidth limits"
105 
+    src="../img/screenshot-win32-configure-relay-2.png"></dd>
106 
+    </li>
107 
+
108 
+    <li><dt>Elija el <tt>políticas de salida</tt> ficha. Si desea permitir que otros
109 
+    utilicen su servidor para estos servicios, no cambia nada. Elimina la marca
110 
+    de los servicios que usted no quiere permitir a la gente a la <a href="<page
111 
+    docs/faq>#ExitPolicies"> alcance de su servidor </a>. Si usted desea ser un
112 
+    no-relé de salida, elimina la marca de todos los servicios.</dt>
113 
+    <dd><img alt="vidalia exit policies"
114 
+    src="../img/screenshot-win32-configure-relay-3.png"></dd>
115 
+    </li>
116 
+
117 
+    <li>Haga clic en el <tt>Ok</tt> botón. Vea el Paso Tres por debajo de la
118 
+    confirmación de que el relé está funcionando correctamente.</li>
119 
+    </ol>
120 
+
121 
+    <br /> <strong>Manual de configuración</strong>:
122 
+    <ul>
123 
+    <li>Modificar la parte inferior de <a
124 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">su
125 
+    fichero torrc</a>. Si usted desea ser un relé público (recomendado),
126 
+    asegúrese de definir ORPort y <a href="<page docs/faq>#ExitPolicies">ver
127 
+    ExitPolicy</a>, de lo contrario, si usted desea ser un <a href="<page
128 
+    docs/faq>#RelayOrBridge">puente</a> para los usuarios en los países que censuran
129 
+    la Internet, sólo tiene que utilizar <a href="<page
130 
+    docs/bridges>#RunningABridge">estas líneas</a>.
131 
+    </li>
132 
+
133 
+    </ul></li>
134 
+
135 
+    <li>Si usted está usando un cortafuegos, abra un agujero en el cortafuegos para
136 
+    que las conexiones entrantes puedan alcanzar los puertos que ha configurado
137 
+    (ORPort, más DirPort si lo ha activado). Si usted tiene un firewall de
138 
+    hardware (cuadro de Linksys, cablemodem, etc) que te gustaría <a
139 
+    href="http://portforward.com/">portforward.com</a>. También, asegúrese de
140 
+    que todos los <em>saliente</em> demasiadas conexiones, por lo que su
141 
+    repetidor pueda llegar a los otros repetidores Tor.
142 
+    </li>
143 
+
144 
+    <li>Rearranque su repetidor. Si <a
145 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">log
146 
+    aparecen advertencias</a>, la dirección de ellos.
147 
+    </li>
148 
+
149 
+    <li>Suscribirse a la <a
150 
+    href="http://archives.seul.org/or/announce/">or-announce</a> lista de
151 
+    correo. Es muy poco tráfico, y le mantendrá informado de nuevas versiones
152 
+    estables. También puede considerar subscribirse a la <a href="<page
153 
+    docs/documentation>#MailingLists">el mayor volumen de las listas de Tor</a>
154 
+    también.
155 
+    </li>
156 
+
157 
+    </ol>
158 
+
159 
+    <hr /> <a id="check"></a>
160 
+    <h2><a class="anchor" href="#check">Paso Tres: Asegurarse de que funciona</a></h2>
161 
+    <br />
162 
+
163 
+    <p>En cuanto su repetidor consiga conectarse a la red, intentará determinar si
164 
+    los puertos que configuró son accesibles desde el exterior. Este paso suele
165 
+    ser rápido, pero puede tardar hasta 20 minutos. Busque un <a
166 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">registro
167 
+    de entrada</a> como <tt>Autoevaluación indica su ORPort es accesible desde
168 
+    el exterior. Excelente.</tt> Si no ve este mensaje, significa que su
169 
+    servidor no es accesible desde el exterior &mdash; debería re-revisar sus
170 
+    cortafuegos, comprobar que esté comprobando la IP y el puerto que usted crea
171 
+    que debería estar comprobando, etc.
172 
+    </p>
173 
+
174 
+    <p>When it decides that it's reachable, it will upload a "server descriptor" to
175 
+    the directories, to let clients know what address, ports, keys, etc your
176 
+    relay is using. You can <a
177 
+    href="http://194.109.206.212/tor/status-vote/current/consensus">load one of
178 
+    the network statuses manually</a> and look through it to find the nickname
179 
+    you configured, to make sure it's there. You may need to wait up to one hour
180 
+    to give enough time for it to make a fresh directory.</p>
181 
+
182 
+    <hr /> <a id="after"></a>
183 
+    <h2><a class="anchor" href="#after">Cuarto paso: Una vez que se está
184 
+    trabajando</a></h2>
185 
+    <br />
186 
+
187 
+    <p>
188 
+    Nosotros recomendamos los siguientes pasos, así:
189 
+    </p>
190 
+
191 
+    <p>
192 
+    6. Leer <a
193 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">sobre
194 
+    seguridad operacional</a> para obtener ideas de cómo aumentar la seguridad
195 
+    de su repetidor.
196 
+    </p>
197 
+
198 
+    <p>
199 
+    7. Si quiere ejecutar más de un repetidor estupendo, pero por favor active
200 
+    <a
201 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">la
202 
+    opción MyFamily</a> en todos sus repetidores archivos de configuración.
203 
+    </p>
204 
+
205 
+    <p>
206 
+    8. Decidir acerca de la limitación de velocidad. El módem de cable, DSL, y
207 
+    otros usuarios que tienen ancho de banda asimétrico (por ejemplo, más que de
208 
+    subida) deberían limitar la velocidad a su ancho de banda más lento, para
209 
+    evitar la congestión. Ver la <a
210 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">limitación
211 
+    de velocidad de la FAQ</a> para más detalles.
212 
+    </p>
213 
+
214 
+    <p>
215 
+    9. Copias de seguridad de la clave privada de su servidor Tor (almacenada en
216 
+    "keys/secret_id_key" en su DataDirectory). Esto es "de su repetidor de
217 
+    identidad", y que necesita para mantener a salvo para que nadie pueda leer
218 
+    el tráfico que pasa a través de su repetidor. Este es el fichero crítico a
219 
+    guardar si necesita <a
220 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeRelay">mover
221 
+    o restaurar su servidor Tor</a> si algo va mal.
222 
+    </p>
223 
+
224 
+    <p>
225 
+
226 
+    10. Si controla los servidores de nombres para su dominio, considere llamar
227 
+    a su host 'anonymous-relay', 'proxy' o 'tor-proxy', para que cuando otra
228 
+    gente vea la dirección en sus web logs, entiendan más rápido lo que está
229 
+    pasando. Adición de la <a
230 
+    href="<gitblob>contrib/tor-salida-notice.html">aviso de salida de Tor</a> en
231 
+    un vhost para este nombre puede ir un largo camino para disuadir a las
232 
+    denuncias de abuso a usted y su proveedor de Internet si usted está
233 
+    ejecutando un nodo de salida.
234 
+
235 
+    </p>
236 
+
237 
+    <p>
238 
+    11. Si su equipo no está ejecutando un servidor web, por favor considere
239 
+    cambiar su ORPort a 443 y su DirPort el 80. Muchos usuarios de Tor están
240 
+    atrapados detrás de cortafuegos que sólo les permiten ver la web, y este
241 
+    cambio les permitirá acceder a su servidor Tor. Los repetidores en Win32
242 
+    pueden simplemente cambiar su ORPort y DirPort directamente en su torrc y
243 
+    reiniciar Tor. Repetidores OS X y Unix servers no pueden escuchar
244 
+    directamente en esos puertos (ya que no se ejecutan como root), por lo que
245 
+    tendrán que establecer algún tipo de <a
246 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">reenvío
247 
+    de puertos </a> para que las conexiones puedan acceder a su servidor Tor. Si
248 
+    usted está usando los puertos 80 y 443 pero todavía quiere ayudar, otros
249 
+    puertos útiles son el 22, 110 y 143.
250 
+    </p>
251 
+
252 
+    <p>
253 
+    12. Si su servidor Tor da otros servicios en la misma dirección IP - como un
254 
+    servidor web público - asegúrese de que las conexiones al servidor web se
255 
+    permiten desde el host local también. Necesitará permitir estas conexiones
256 
+    porque los clientes Tor detectarán que su repetidor Tor es la <a
257 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">manera
258 
+    más segura de llegar a ese servidor web</a>, y siempre construirán un
259 
+    circuito que termine en su relevo. Si usted no quiere permitir las
260 
+    conexiones, debe rechazarlas explícitamente en su política de salida.
261 
+    </p>
262 
+
263 
+    <p>
264 
+    13. (Sólo Unix). Cree un usuario separado para ejecutar el repetidor. Si
265 
+    instaló el paquete OS X o el deb o el rpm, ya está hecho. De lo contrario,
266 
+    usted puede hacerlo a mano. (El repetidor Tor no necesita ejecutarse como
267 
+    root, así que es buena práctica no ejecutarlo como root. Ejecuta como el
268 
+    usuario 'tor' evita problemas con identd y otros servicios que detectan el
269 
+    nombre de usuario. Si usted es el paranoico tipo, no dude en <a
270 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">poner
271 
+    Tor en una cárcel chroot</a>.)
272 
+    </p>
273 
+
274 
+    <p>
275 
+    14. (Sólo Unix.) Su sistema operativo probablemente limita el número de
276 
+    descriptores de fichero abiertos por proceso a 1024 (o incluso menos). Si
277 
+    planea ejecutar un nodo de salida rápido, probablemente no sea
278 
+    suficiente. En Linux, debería añadir una línea como "toruser hard nofile
279 
+    8192" a su archivo / etc / security / limits.conf (donde toruser es el
280 
+    usuario que ejecuta el proceso Tor), y reiniciar Tor si se instaló como
281 
+    paquete (o cerrar la sesión y vuelva a entrar si lo ejecuta directamente).
282 
+    </p>
283 
+
284 
+    <p>
285 
+    15. Si instaló Tor usando algún paquete o instalador, probablemente ejecute
286 
+    Tor automáticamente al arrancar. Pero si lo instaló desde las fuentes, puede
287 
+    encontrar los scripts de arranque en contrib/tor.sh o contrib/torctl útiles.
288 
+    </p>
289 
+
290 
+    <p>
291 
+    Cuando cambie su configuración Tor, recuerde verificar que su repetidor
292 
+    todavía funciona correctamente tras el cambio. Asegúrese de configurar su
293 
+    línea "ContactInfo" en el torrc para que podamos contactar con usted si
294 
+    necesita actualizarse o algo va mal. Si tiene problemas o preguntas,
295 
+    consulte la <a href="<page docs/documentation>#Support">Support</a> o <a
296 
+    href="<page about/contact>">contacto</a> en el tor-ops lista. Gracias por ayudar a
297 
+    hacer crecer la red Tor!
298 
+    </p>
299 
+
300 
+    <hr />
301 
+
302 
+    <p>Si tiene sugerencias para mejorar este documento, por favor <a href="<page
303 
+    about/contact>">envíanoslas</a>. Gracias!</p>
304 
+  </div>
305 
+  <!-- END MAINCOL -->
306 
+  <div id = "sidecol">
307 
+#include "side.wmi"
308 
+#include "info.wmi"
309 
+  </div>
310 
+  <!-- END SIDECOL -->
311 
+</div>
312 
+<!-- END CONTENT -->
313 
+#include <foot.wmi>
docs/es/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,197 @@
1 
+    <h1>Ejecutar el cliente <a href="<page index>">Tor</a> en Linux/BSD/Unix</h1>
2 
+    <br />
3 
+
4 
+    <p><b>N&oacute;tese que estas son las instrucciones de instalaci&oacute;n para e
5 
+    jecutar un cliente Tor.
6 
+    Si quieres gestionar tr&aacute;fico para otros y ayudar a crecer la red Tor,
7 
+     (h&aacute;zlo por favor), lee la gu&iacute;a
8 
+    <a href="<page docs/tor-doc-relay>">Configurar un repetidor</a>
9 
+    </b>
10 
+    </p>
11 
+
12 
+    <hr />
13 
+    <a id="installing"></a>
14 
+    <h2><a class="anchor" href="#installing">Paso Uno: Descarga e Instala Tor</a></h2>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    La última versión de Tor se encuentra en la página de <a
19 
+    href="<page download/download>">descarga</a>. También tenemos paquetes para Debian,
20 
+    Red Hat, Gentoo, *BSD, etc allí.
21 
+    </p>
22 
+
23 
+    <p>Si vas a compilar desde las fuentes, primero instala <a
24 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a>, y
25 
+    asegúrate de tener openssl y zlib (incluyendo los paquetes -devel si existen).
26 
+    Entonces ejecuta:<br />
27 
+    <tt>tar xzf tor-<version-stable>.tar.gz; cd tor-<version-stable><br />
28 
+    ./configure &amp;&amp; make</tt><br />
29 
+    Ahora se puede ejecutar tor como <tt>src/or/tor</tt>, o puedes ejecutar <tt>make install</tt>
30 
+    (como root en caso necesario) para instalarlo en /usr/local/, tras lo cual se puede
31 
+    arrancar simplemente ejecutando <tt>tor</tt>.
32 
+    </p>
33 
+
34 
+    <p>Tor viene configurado como cliente por defecto. Usa un fichero de configuración
35 
+    integrado, y la mayoría de la gente no nesitará cambiar ningún parámetro. Tor está ya
36 
+    instalado.
37 
+    </p>
38 
+
39 
+    <hr />
40 
+    <a id="privoxy"></a>
41 
+    <h2><a class="anchor" href="#privoxy">Paso Dos: Instalar Privoxy para Navegar por la Web</a></h2>
42 
+    <br />
43 
+
44 
+    <p>Tras instalar Tor, necesita configurar sus aplicaciones para usarlo.
45 
+    </p>
46 
+
47 
+    <p>
48 
+    El primer paso es configurar la navegación web. Empiece instalando <a
49 
+    href="http://www.privoxy.org/">Privoxy</a>: haga click en 'recent releases'
50 
+    y elija su paquete favorito o instale desde las fuentes. Privoxy es un
51 
+    proxy web que hace filtrado y que se integra bien con Tor.
52 
+    </p>
53 
+
54 
+    <p>Una vez que haya instalado Privoxy (o bien desde paquete o desde fuentes),
55 
+    <b>necesitará configurar Privoxy para que use Tor</b>. Puede que <a
56 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">esta
57 
+    muestra de configuración de Privoxy</a> le sea útil. En caso contrario, debería
58 
+    configurar Privoxy a mano, usando las indicaciones que siguen.
59 
+    </p>
60 
+
61 
+    <p>
62 
+    Abra el fichero "config" de Privoxy (busque en /etc/privoxy/ o /usr/local/etc/)
63 
+    y añada la línea <br>
64 
+    <tt>forward-socks4a / 127.0.0.1:9050 .</tt><br>
65 
+    al principio del fichero de configuración. No se olvide de añadir el punto al final.
66 
+    </p>
67 
+
68 
+    <p>Privoxy mantiene un fichero de log de todo lo que pasa a su través. Para
69 
+    evitar esto tendrá que comentar tres líneas insertando un
70 
+    \# antes de la línea. Las tres líneas son:<br>
71 
+    <tt>logfile logfile</tt><br>
72 
+    y la línea <br>
73 
+    <tt>jarfile jarfile</tt><br>
74 
+    y (en algunos sistemas) la línea <br>
75 
+    <tt>debug 1  # show each GET/POST/CONNECT request</tt><br>
76 
+    </p>
77 
+
78 
+    <p>Dependiendo de qué fichero de configuración por defecto tenga para Privoxy,
79 
+    puede que también tenga que desactivar <tt>enable-remote-toggle</tt>,
80 
+    <tt>enable-remote-http-toggle</tt>, y <tt>enable-edit-actions</tt>.
81 
+    </p>
82 
+
83 
+    <p>Tendrá que reiniciar Privoxy para que los cambios tengan efecto.</p>
84 
+
85 
+    <hr />
86 
+    <a id="using"></a>
87 
+    <h2><a class="anchor" href="#using">Paso Tres: Configurar tus aplicaciones para que usen Tor</a></h2>
88 
+    <br />
89 
+
90 
+    <p>Tras instalar Tor y Privoxy, debes configurar tus aplicaciones para usarlos.
91 
+    El primer paso es configurar tu navegador.</p>
92 
+
93 
+    <p>Si usa Firefox (lo recomendamos), simplemente instale el <a
94 
+    href="https://addons.mozilla.org/firefox/2275/">plugin Torbutton
95 
+    </a>, reinicie Firefox, y eso es todo:
96 
+    </p>
97 
+
98 
+    <img alt="Torbutton plugin for Firefox"
99 
+    src="../img/screenshot-torbutton.png"
100 
+    border="1">
101 
+
102 
+    <br />
103 
+
104 
+    <p>
105 
+    (<a href="https://torbutton.torproject.org/">Aprenda más sobre
106 
+    Torbutton aquí</a>.
107 
+    Si planea usar Firefox en un ordenador distinto del de Tor, vea la <a
108 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">
109 
+    entrada en la FAQ para ejecutar Tor en un ordenador distinto</a>. Si necesita usar
110 
+    un navegador distinto de Firefox, tendrá que <a href="<page
111 
+    docs/tor-doc-web>">configurar sus opciones de proxies usted mismo.</a>.)
112 
+    </p>
113 
+
114 
+    <p>Usar Privoxy es <strong>necesario</strong> porque
115 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">
116 
+    los exploradores fallan al hacer peticiones DNS cuando usan un proxy SOCKS directamente</a>,
117 
+    lo cual es malo para el anonimato. Privoxy también elimina ciertas cabeceras
118 
+    peligrosas de tus peticiones web, y bloquea inc&oacute;modos sitios como Doubleclick.</p>
119 
+
120 
+    <p>Para usar con TOR otras aplicaciones que soportan proxies HTTP, simplemente
121 
+    dirigirlas a Privoxy (localhost, puerto 8118). Para usar SOCKS directamente (para
122 
+    mensajer&iacute;a instantanea, Jabber, IRC, etc.) puedes dirigir tu aplicaci&oacute;n directamente
123 
+    a Tor (localhost, puerto 9050), pero visita <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">esta FAQ</a>
124 
+    donde se explica por qu&eacute; esto puede ser peligroso. Para aplicaciones que no soportan ni SOCKS ni HTTP,
125 
+    visitar <a
126 
+    href="http://tsocks.sourceforge.net/">tsocks</a> o <a
127 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
128 
+    </p>
129 
+
130 
+    <p>Para m&aacute;s informaci&oacute;n sobre como "TOR"ificar otras aplicaciones
131 
+    visitar <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
132 
+    HOWTO</a>.
133 
+    </p>
134 
+
135 
+    <hr />
136 
+    <a id="verify"></a>
137 
+    <h2><a class="anchor" href="#verify">Paso Cuatro: Asegurarse de que funciona</a></h2>
138 
+    <br />
139 
+
140 
+    <p>Despu&eacute;s, deber&iacute;as intentar usar tu explorador con Tor y asegurarte que tu dirección
141 
+    IP esta siendo anonimizada.
142 
+    Visite <a href="https://check.torproject.org/">el detector de Tor</a>
143 
+    y compruebe si cree que usa Tor o no.
144 
+    #<a href="http://ipchicken.com/">this site</a>
145 
+    #to see what IP address it thinks you're using.
146 
+    (Si este sitio no responde, visite <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">
147 
+    esta FAQ</a> para más sugerencias sobre como testear su Tor.)
148 
+    </p>
149 
+
150 
+    <p>Si usa un cortafuegos personal que limita la capacidad de conexi&oacute;n de su computadora
151 
+    a sí misma (esto incluye también SELinux en Fedora Core 4),
152 
+    asegúrese que permite conexiones de aplicaciones locales a Privoxy (puerto local 8118) y a Tor
153 
+    (puerto local 9050). Si su cortafuegos bloquea conexiones salientes, configúrelo para que puedan
154 
+    hacerse conexiones al menos a los puertos TCP 80 y 443 y visite
155 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">este apartado de la FAQ</a>. Si su fichero de configuración SELinux no permite a tor o a privoxy ejecutarse
156 
+    correctamente, cree un fichero llamado booleans.local en el directorio
157 
+    /etc/selinux/targeted. Edite este fichero en su editor de textos favorito e inserte
158 
+    "allow_ypbind=1". Reinicie su máquina para que este cambio tenga efecto.
159 
+    </p>
160 
+
161 
+    <p>Si a&uacute;n no funciona, visite
162 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">este apartado de la FAQ</a>
163 
+    para seguir consejos.</p>
164 
+
165 
+    <hr />
166 
+    <a id="server"></a>
167 
+    <a id="relay"></a>
168 
+    <h2><a class="anchor" href="#relay">Paso Cinco: Configurarlo como repetidor</a></h2>
169 
+    <br/>
170 
+
171 
+    <p>La red Tor se basa en voluntarios que donan su ancho de banda.
172 
+    Cuantos m&aacute;s repetidores, m&aacute;s rápida ser&aacute; la red Tor. Si tienes al menos 20 Kbytes/s en ambos sentidos,
173 
+    por favor ayuda a Tor configur&aacute;ndolo para que sea repetidor tambi&eacute;n. Tenemos varias caracter&iacute;sticas para que
174 
+    hacer a Tor repetidor sea fácil y conveniente, incluyendo limitaci&oacute;n del ancho de banda cedido, políticas de
175 
+    conexiones de salida que pueden limitar tu exposici&oacute;n a casos de abuso, y soporte para IP din&aacute;micas.
176 
+
177 
+    <p>Tener repetidores en varios y diferentes sitios en la Internet es lo que convierte a los usuarios de Tor en seguros.
178 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Puedes reforzar tu propio anonimato</a>,
179 
+    haciendo que sitios remotos no puedan saber si las conexiones se originaron en
180 
+    tu computadora o fueron iniciadas desde otras.</p>
181 
+
182 
+    <p>Lee más en nuestra gu&iacute;a <a href="<page docs/tor-doc-relay>">Configurando un repetidor</a></p>
183 
+
184 
+    <hr/>
185 
+
186 
+    <p>Si tienes sugerencias para mejorar este documento, por favor <a
187 
+    href="<page about/contact>">envíanoslas</a>. ¡Gracias!</p>
188 
+  </div>
189 
+  <!-- END MAINCOL -->
190 
+  <div id = "sidecol">
191 
+#include "side.wmi"
192 
+#include "info.wmi"
193 
+  </div>
194 
+  <!-- END SIDECOL -->
195 
+</div>
196 
+<!-- END CONTENT -->
197 
+#include <foot.wmi>
docs/es/tor-doc-web.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,63 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Configuring your browser to use Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-web>">Configure Your Browser</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurar su navegador para usar <a href="<page index>">Tor</a></h1>
14 
+    <br />
15 
+
16 
+    <p>Si está usando Firefox (lo recomendamos), no necesita esta página.
17 
+    Simplemente instale el <a
18 
+    href="https://addons.mozilla.org/firefox/2275/">plugin Torbutton
19 
+    </a>, reinicie Firefox, y eso es todo:
20 
+    </p>
21 
+
22 
+    <img alt="Plugin Torbutton para Firefox"
23 
+    src="../img/screenshot-torbutton.png"
24 
+    border="1"/>
25 
+
26 
+    <br />
27 
+
28 
+    <p>En caso contrario, tiene que configurar manualmente los proxies del navegador.
29 
+    <br/>En Mozilla y Firefox en Windows, están en
30 
+    Herramientas - Opciones - General - Opciones de Conexión.
31 
+    <br/>En Firefox en OS X, es Firefox - Preferencias - General - Opciones de Conexión.
32 
+    <br/>En Firefox en Linux, es
33 
+    Editar - Preferencias - Advanzado - Proxies.
34 
+    <br/>En Opera es Herramientas - Preferencias (Advanzado) - Red - Servidores Proxy.
35 
+    <br/>En IE, es Herramientas - Opciones de Internet - Connexiones - Opciones LAN - Comprobar Servidor
36 
+    Proxy - Advanzado.</p>
37 
+
38 
+    <img alt="Configuración Proxy en Firefox"
39 
+    src="../img/screenshot-win32-firefox-proxies.jpg" />
40 
+
41 
+    <p>
42 
+    Debería rellenar "localhost"
43 
+    y "8118" para que los primeros cuatro protocolos señalen a  Privoxy, como se muestra aquí. (Aunque
44 
+    Privoxy no soporta FTP ni Gopher, <a
45 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">debería
46 
+    ponerlos de todas formas</a>.) Debería también rellenar la entrada del proxy socks
47 
+    para apuntar directamente a Tor ("localhost", "9050", y socks5)
48 
+    para cubrir protocolos además de los cuatro primeros. Luego pulse "OK".</p>
49 
+
50 
+    <hr />
51 
+
52 
+    <p>Si tiene sugerencias para mejorar este documento, por favor <a
53 
+    href="<page about/contact>">envíenoslas</a>. ¡Gracias!</p>
54 
+  </div>
55 
+  <!-- END MAINCOL -->
56 
+  <div id = "sidecol">
57 
+#include "side.wmi"
58 
+#include "info.wmi"
59 
+  </div>
60 
+  <!-- END SIDECOL -->
61 
+</div>
62 
+<!-- END CONTENT -->
63 
+#include <foot.wmi>
docs/es/tor-doc-win32.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,7 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 13195
3 
+# Last-Translator: ruben at ugr es
4 
+
5 
+#include "head.wmi"
6 
+TITLE="Redirecting"
7 
+REDIRECT="docs/tor-doc-windows"
docs/es/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,186 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>La ejecución de el cliente <a href="<page index>"> Tor</a> en Microsoft
14 
+    Windows</h1>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    Tenga en cuenta que estas son las instrucciones de instalación para ejecutar
19 
+    un cliente Tor en Microsoft Windows (2000, XP, Vista, 7, yediciones de
20 
+    Servidor). Si quieres gestionar tráfico para otros y ayudar a crecer la red
21 
+    (por favor), lee la guía de <a href="<page
22 
+    docs/tor-doc-relay>">Configuración de un relé."</a></b>
23 
+    </p>
24 
+
25 
+    <p>Freedom House has produced a video on how to install Tor.  You can view it
26 
+    at <a
27 
+    href="http://media.torproject.org/video/2009-install-and-use-tor.ogv">How to
28 
+    install Tor on Windows</a>.  Know of a better video, or one translated into
29 
+    your language? Let us know!</p>
30 
+
31 
+    <div class="center">
32 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor.ogv" autobuffer="true" controls="controls"></video></p>
33 
+    </div>
34 
+
35 
+    <hr /> <a id="installing"></a>
36 
+    <h2><a class="anchor" href="#installing">Paso Uno: Descargar e Instalar Tor</a></h2>
37 
+    <br />
38 
+
39 
+    <p>
40 
+    Paquetes de Microsoft Windows contienen, <a href="<page index>">Tor</a>, <a
41 
+    href="<page projects/vidalia>">Vidalia</a> (una GUI para Tor), <a
42 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> (un plugin
43 
+    para Mozilla Firefox), y <a
44 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo </a> (un proxy
45 
+    web) envasados en un solo paquete, con las cuatro aplicaciones
46 
+    preconfiguradas para trabajar juntas. Descargue el <a
47 
+    href="../<package-win32-bundle-stable>"> estable</a> o el <a
48 
+    href="../<package-win32-bundle-alpha>"> experimental</a> versión del paquete
49 
+    de Windows, o buscar más opciones en la <a href="<page download/download>"> página de
50 
+    descarga </a>.
51 
+    </p>
52 
+
53 
+    <img alt="tor installer splash page"
54 
+    src="../img/screenshot-win32-installer-splash.png" />
55 
+
56 
+    <p>Si ya has instalado Tor, Vidalia, o Polipo puedes deseleccionar cualquier
57 
+    componente que no es necesario instalar en el diálogo que se muestra a
58 
+    continuación.
59 
+    </p>
60 
+
61 
+    <img alt="select components to install"
62 
+    src="../img/screenshot-win32-installer-components.png" />
63 
+
64 
+    <p>Después de haber completado la instalación, los componentes seleccionados se
65 
+    iniciarán automáticamente para usted.
66 
+    </p>
67 
+
68 
+    <p>Tor viene configurado como cliente por defecto. Se utiliza un incorporada en
69 
+    el archivo de configuración por defecto, y la mayoría de la gente no tendrá
70 
+    que cambiar cualquiera de las opciones. Tor está ya instalado.
71 
+    </p>
72 
+
73 
+    <hr /> <a id="using"></a>
74 
+    <h2><a class="anchor" href="#using">Paso Dos: Configurar tus aplicaciones para
75 
+    Tor</a></h2>
76 
+    <br />
77 
+
78 
+    <p>Tras instalar Tor y Polipo, necesita configurar sus aplicaciones para
79 
+    usarlos. El primer paso es configurar la navegación web.</p>
80 
+
81 
+    <p>Usted debe usar Tor con Firefox y Torbutton, para la mejor seguridad. El
82 
+    paquete instala el <a href="https://addons.mozilla.org/firefox/2275/">plugin
83 
+    Torbutton</a> para ti. Reinicia Firefox, y eso es todo:
84 
+    </p>
85 
+
86 
+    <img alt="Torbutton plugin for Firefox"
87 
+    src="../img/screenshot-torbutton.png" border="1"/> <br />
88 
+
89 
+    <p>
90 
+    Si planea ejecutar Firefox en un ordenador distinto del de Tor, vea la <a
91 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">Entrada
92 
+    de la FAQ para ejecutar Tor en un ordenador diferente</a>.
93 
+    </p>
94 
+
95 
+    <p>Para usar con Tor otras aplicaciones que soportan proxies HTTP, simplemente
96 
+    dirigirlas a Polipo (es decir, localhost, puerto 8118). Para usar SOCKS
97 
+    directamente (para mensajería instantanea, Jabber, IRC, etc), puede apuntar
98 
+    su aplicación directamente a Tor (localhost, puerto 9050), pero vea <a
99 
+    href="https://wiki.torproject.org
100 
+    noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">esta FAQ</a> por qué esto puede
101 
+    ser peligroso. Para aplicaciones que no soportan ni SOCKS ni HTTP, visitar
102 
+    SocksCap o <a href="http://www.freecap.ru/eng/">FreeCap</a>. (FreeCap es
103 
+    software libre; SocksCap es propietario).</p>
104 
+
105 
+    <p>For information on how to Torify other applications, check out the <a
106 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
107 
+    HOWTO</a>.
108 
+    </p>
109 
+
110 
+    <hr /> <a id="verify"></a>
111 
+    <h2><a class="anchor" href="#verify">Paso Tres: Asegurarse de que funciona</a></h2>
112 
+    <br />
113 
+
114 
+    <p>
115 
+    Compruebe que Vidalia se está ejecutando. Vidalia usa una pequeña cebolla
116 
+    verde para indicar que Tor se está ejecutando, o una cebolla oscura con una
117 
+    "X" roja cuando Tor no está ejecutándose. Puedes arrancar o detener Tor
118 
+    haciendo clic derecho sobre el icono de Vidalia en la bandeja del sistema y
119 
+    seleccionando "Inicio" o "Stop" del menú como se muestra a continuación:
120 
+    </p>
121 
+
122 
+    <img alt="Vidalia Tray Icon" src="../img/screenshot-win32-vidalia.png"/>
123 
+
124 
+    <p>
125 
+    Después, deberías intentar usar tu explorador con Tor y asegurarse de que su
126 
+    dirección IP está siendo anonimizada. Haga clic en <a
127 
+    href="https://check.torproject.org/">el detector de Tor</a> y compruebe si
128 
+    cree que usas Tor o no. (Si el sitio está caído, vea <a
129 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">esta
130 
+    FAQ</a> para más sugerencias sobre cómo comprobar su Tor.)
131 
+    </p>
132 
+
133 
+    <p>Si tiene un cortafuegos personal que limita la capacidad de su ordenador
134 
+    para conectarse a sí mismo, asegúrate que permite conexiones de aplicaciones
135 
+    locales al puerto local 8118 y al puerto 9050. Si tu cortafuegos bloquea
136 
+    conexiones salientes, abra un agujero para que pueda conectarse al menos a
137 
+    los puertos TCP 80 y 443, y luego vea <a
138 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">esta
139 
+    FAQ</a>.
140 
+    </p>
141 
+
142 
+    <p>Si aún no funciona, mire <a
143 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">esta
144 
+    FAQ</a> para seguir consejos.</p>
145 
+
146 
+    <p>
147 
+    Una vez que funcione, aprender más acerca de <a href="<page
148 
+    download/download>#Warning">lo que hace Tor y no ofrece</a>.
149 
+    </p>
150 
+
151 
+    <hr /> <a id="server"></a> <a id="relay"></a>
152 
+    <h2><a class="anchor" href="#relay">Paso Cuatro: Configurarlo como repetidor</a></h2>
153 
+    <br />
154 
+
155 
+    <p>La red Tor se apoya en voluntarios que donen ancho de banda. Cuanta más
156 
+    gente ejecute repetidores, más rápida será la red Tor ser. Si tiene al menos
157 
+    20 kilobytes / s bidireccional, por favor ayuda a Tor configurando su Tor
158 
+    para que sea repetidor también. Tenemos muchas características que hacen los
159 
+    repetidores Tor fáciles y convenientes, incluyendo limitación del ancho de
160 
+    banda, políticas de salida que pueden limitar su exposición a quejas de
161 
+    abuso, y soporte para direcciones IP dinámicas.</p>
162 
+
163 
+    <p>Tener repetidores en muchos sitios diferentes de Internet es lo que hace a
164 
+    los usuarios de Tor seguros. <a
165 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">También
166 
+    puede obtener más anonimato</a>, haciendo que sitios remotos no puedan saber
167 
+    si las conexiones se originaron en su ordenador o fueron reenviadas desde
168 
+    otros.</p>
169 
+
170 
+    <p>Lea más en nuestro guía<a href="<page docs/tor-doc-relay>"> Configurar un
171 
+    repetidor</ a>.</p>
172 
+
173 
+    <hr />
174 
+
175 
+    <p>Si tiene sugerencias para mejorar este documento, por favor <a href="<page
176 
+    about/contact>"> envíanoslas</a>. Gracias!</p>
177 
+  </div>
178 
+  <!-- END MAINCOL -->
179 
+  <div id = "sidecol">
180 
+#include "side.wmi"
181 
+#include "info.wmi"
182 
+  </div>
183 
+  <!-- END SIDECOL -->
184 
+</div>
185 
+<!-- END CONTENT -->
186 
+#include <foot.wmi>
docs/es/tor-hidden-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,269 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22314 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurar Servicios Ocultos para <a href="<page index>">Tor</a></h1>
14 
+    <hr />
15 
+
16 
+    <p>Tor permite a los clientes y a los repetidores que ofrezcan servicios ocultos.
17 
+    Eso significa que puede ofrecer un servidor web, servidor SSH, etc., sin revelar
18 
+    su dirección IP a sus usuarios. De hecho, como no se usa ninguna dirección pública,
19 
+    puedes ejecutar un servicio oculto desde detrás de un cortafuegos.
20 
+    </p>
21 
+
22 
+    <p>Si tiene Tor y Privoxy instalado, puede ver los servicios ocultos
23 
+    en acción visitando <a href="http://duskgytldkxiuqc6.onion/">un ejemplo de
24 
+    servicio oculto</a>.
25 
+    </p>
26 
+
27 
+    <p>Este howto describe los pasos para configurar tu propio sitio web en
28 
+    un servicio oculto.
29 
+    </p>
30 
+
31 
+    <hr />
32 
+    <a id="zero"></a>
33 
+    <h2><a class="anchor" href="#zero">Paso Cero: Hacer que Tor y Privoxy funcionen</a></h2>
34 
+    <br />
35 
+
36 
+    <p>Antes de empezar, necesitará asegurarse de que: </p>
37 
+    <ol>
38 
+    <li>Tor está activo y ejecutándose,</li>
39 
+    <li>Privoxy está activo y ejecutándose,</li>
40 
+    <li>Privoxy está configurado para apuntar a Tor, y </li>
41 
+    <li>Lo ha configurado correctamente.</li>
42 
+    </ol>
43 
+
44 
+    <p>Los usuarios de Windows deberían seguir el <a
45 
+    href="<page docs/tor-doc-windows>">howto para Windows
46 
+    </a>, Los usuarios de OS X deberían seguir el <a
47 
+    href="<page docs/tor-doc-osx>">howto para OS
48 
+    X</a>, y los usuarios de Linux/BSD/Unix deberían seguir el <a
49 
+    href="<page docs/tor-doc-unix>">howto para Unix</a>.
50 
+    </p>
51 
+
52 
+    <p>Una vez que tenga Tor y Privoxy instalados y configurados,
53 
+    puede ver los servicios ocultos en acción siguiendo este enlace a <a
54 
+    href="http://duskgytldkxiuqc6.onion/">un ejemplo de servicio oculto</a>.
55 
+    Tardará típicamente 10-60 segundos en cargarse
56 
+    (o en decidir que no se puede acceder por el momento). Si falla
57 
+    inmediatamente y tu navegador muestra una alerta diciendo que
58 
+    "www.duskgytldkxiuqc6.onion no se encontró, compruebe por favor el nombre e
59 
+    inténtelo de nuevo" no ha configurado Tor y Privoxy correctamente; vea <a
60 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">la
61 
+    entrada Tor-o-Privoxy-no-funcionan de la FAQ</a> para ayuda.
62 
+    </p>
63 
+
64 
+    <hr />
65 
+    <a id="one"></a>
66 
+    <h2><a class="anchor" href="#one">Paso Uno: Instalar un servidor web localmente</a></h2>
67 
+    <br />
68 
+
69 
+    <p>Primero, necesitará configurar un servidor web localmente. Configurar un
70 
+    servidor web puede ser complicado,
71 
+    así que sólo explicaremos algunas cosas básicas. Si se atranca o
72 
+    quiere hacer más, busque un amigo que pueda ayudarle. Recomendamos que
73 
+    instale un nuevo servidor web separado para su servicio oculto, ya que
74 
+    incluso si ya tiene uno instalado, puede estar usándolo (o querer usarlo
75 
+    más tarde) para un sitio web real.
76 
+    </p>
77 
+
78 
+    <p>Si está en Unix u OS X y está cómodo en la línea de órdenes,
79 
+    la mejor forma con diferencia es instalar <a
80 
+    href="http://www.acme.com/software/thttpd/">thttpd</a>. Coja el último
81 
+    fichero tar, descomprímalo (creará su propio directorio), y ejecute
82 
+    <kbd>./configure &amp;&amp; make</kbd>. Luego <kbd>mkdir hidserv; cd
83 
+    hidserv</kbd>, y ejecute
84 
+    <kbd>../thttpd -p 5222 -h localhost</kbd>. Volverá a la línea de órdenes,
85 
+    y ya está usted ejecutando un servidor web en el puerto 5222. Puede poner
86 
+    ficheros para servir en el directorio hidserv.
87 
+    </p>
88 
+
89 
+    <p>Si está en Windows, podría elegir <a
90 
+    href="http://savant.sourceforge.net/">Savant</a> o <a
91 
+    href="http://httpd.apache.org/">Apache</a>, y asegúrese de configurarlo
92 
+    para que escuche sólo a localhost. También debería averiguar en que
93 
+    puerto está escuchando, porque lo usará más abajo.
94 
+    </p>
95 
+
96 
+    <p>(La razón de que el servidor web sólo escuche a localhost es para
97 
+    asegurarse de que no es accesible públicamente. Si la gente
98 
+    pudiera conectarse a él directamente, podrían confirmar que su
99 
+    ordenador es el que está ofreciendo el servicio oculto.)
100 
+    </p>
101 
+
102 
+    <p>Una vez que tenga su servidor web configurado, asegúrese de que funciona:
103 
+    abra su navegador y vaya a <a
104 
+    href="http://localhost:5222/">http://localhost:5222/</a>, donde 5222 es
105 
+    el puerto que eligió antes. Intente poner un fichero en el directorio html
106 
+    principal, y asegúrese de que aparece cuando accede al sitio.
107 
+    </p>
108 
+
109 
+    <hr />
110 
+    <a id="two"></a>
111 
+    <h2><a class="anchor" href="#two">Paso Dos: Configure su servicio oculto</a></h2>
112 
+    <br />
113 
+
114 
+    <p>Para lo siguiente, necesita configurar su servicio oculto para que apunte
115 
+    a su servidor web local.
116 
+    </p>
117 
+
118 
+    <p>Primero, abra su fichero torrc en su editor de texto favorito. (Vea <a
119 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">la
120 
+    entrada de la FAQ torrc</a> para aprender lo que esto significa.)
121 
+    Vaya a la sección del medio y busque la línea</p>
122 
+
123 
+    <pre>
124 
+    \############### This section is just for location-hidden services ###
125 
+    </pre>
126 
+
127 
+    <p>
128 
+    Esta sección del fichero consiste en grupos de líneas, cada una representando
129 
+    un servicio oculto. Ahora mismo están todas comentadas (las líneas comienzan con
130 
+    #), así que los servicios ocultos están deshabilitados. Cada grupo de líneas
131 
+    consiste en una línea <var>HiddenServiceDir</var>, y una o más líneas
132 
+    <var>HiddenServicePort</var>:</p>
133 
+    <ul>
134 
+    <li><var>HiddenServiceDir</var> es un directorio donde Tor almacenará información
135 
+    acerca de ese servicio oculto. En particular, Tor creará un fichero aquí de
136 
+    nombre <var>hostname</var> que le dirá la URL onion.  No necesita añadir ningún
137 
+    fichero a este directorio.</li>
138 
+    <li><var>HiddenServicePort</var> le permite especificar un puerto virtual (eso es, qué
139 
+    puerto creerán que están usando la gente que acceda al servicio oculto) y una
140 
+    dirección IP y puerto para redireccionar conexiones a este puerto virtual.</li>
141 
+    </ul>
142 
+
143 
+    <p>Añada las siguientes líneas a su torrc:
144 
+    </p>
145 
+
146 
+    <pre>
147 
+    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
148 
+    HiddenServicePort 80 127.0.0.1:5222
149 
+    </pre>
150 
+
151 
+    <p>Querrá cambiar la línea <var>HiddenServiceDir</var>, para que apunte
152 
+    a un directorio real que sea legible/escribible por el usuario que
153 
+    ejecutará Tor. La línea anterior debería funcionar si está usando el
154 
+    paquete Tor para OS X. En Unix, pruebe "/home/username/hidserv/" y complete su propio
155 
+    nombre de usuario en lugar de "username". En Windows puede escoger:</p>
156 
+    <pre>
157 
+    HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\\
158 
+    HiddenServicePort 80 127.0.0.1:5222
159 
+    </pre>
160 
+
161 
+    <p>Ahora grabe el torrc, apague su Tor, e inícielo de nuevo.
162 
+    </p>
163 
+
164 
+    <p>Si tor reinicia, estupendo. En caso contrario, algo está mal. Primero
165 
+    mire los logs de tor para consejos. Mostrará algunos mensajes con advertencias
166 
+    o errores. Eso debería darle alguna idea de qué está mal. Lo típico es que haya
167 
+    palabras mal escritas o permisos erróneos en los directorios. (Vea  <a
168 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">la
169 
+    entrada FAQ sobre log</a> si no está seguro de cómo activar o encontrar
170 
+    su fichero de log.)
171 
+    </p>
172 
+
173 
+    <p>Cuando Tor arranque, automáticamente creará el <var>HiddenServiceDir</var>
174 
+    que especificó (en caso necesario), y creará dos ficheros allí.</p>
175 
+    <dl>
176 
+    <dt><var>private_key</var></dt>
177 
+    <dd>
178 
+    Primero, Tor generará una pareja de llaves pública/privada para su servicio
179 
+    oculto. Se escribe en un fichero llamado "private_key". No comparta esta
180 
+    clave con otros -- si lo hace podrán impersonar su servicio oculto.
181 
+    </dd>
182 
+    <dt><var>hostname</var></dt>
183 
+    <dd>El otro fichero que Tor creará se llama "hostname". Contiene un pequeño
184 
+    resumen de su llave pública -- parecerá algo como
185 
+    <tt>duskgytldkxiuqc6.onion</tt>. Este es el nombre público de su servicio,
186 
+    y puede decírselo a la gente, publicarlo en sitios web, ponerlo en tarjetas
187 
+    de visita, etc.</dd>
188 
+    </dl>
189 
+
190 
+    <p>Si Tor se ejecuta como un usuario diferente de usted, por
191 
+    ejemplo en OS X, Debian, o Red Hat, puede que necesite hacerse root para
192 
+    poder ver esos ficheros.</p>
193 
+
194 
+    <p>Ahora que ha reiniciado Tor, está ocupado eligiendo puntos de introducción en
195 
+    la red Tor, y generando lo que se llama un <em>descriptor de servicio oculto</em>.
196 
+    Esto es una lista firmada de puntos de introducción junto con la llave pública
197 
+    completa del servicio. Publica anónimamente este descriptor a los servidores
198 
+    de directorio, y otra gente lo obtiene anónimamente de los servidores de
199 
+    directorio cuando intentan acceder a su servicio.
200 
+    </p>
201 
+
202 
+    <p>Pruebe ahora: pegue el contenido del fichero hostname en tu navegador
203 
+    web. Si funciona, obtendrá la página html que configuró en el paso uno.
204 
+    Si no funciona, mire en sus logs buscando sugerencias, y siga jugando con
205 
+    él hasta que funcione.
206 
+    </p>
207 
+
208 
+    <hr />
209 
+    <a id="three"></a>
210 
+    <h2><a class="anchor" href="#three">Paso Tres: Consejos más avanzados</a></h2>
211 
+    <br />
212 
+
213 
+    <p>Si planea mantener su servicio disponible durante largo tiempo, puede que
214 
+    quiera hacer una copia de seguridad del fichero <var>private_key</var> en alguna parte.
215 
+    </p>
216 
+
217 
+    <p>Hemos evitado recomendar Apache antes, a) porque mucha gente podría
218 
+    estar ya ejecutándolo para su servidor web público en su ordenador, y b)
219 
+    porque es grande y tiene muchos sitios donde podría revelar su dirección
220 
+    IP u otra información identificadora, por ejemplo en páginas 404. Para
221 
+    la gente que necesite más funcionalidad, sin embargo, Apache puede ser la
222 
+    respuesta correcta. ¿Puede alguien hacernos una lista de formas de bloquear
223 
+    el Apache cuando se usa como servicio oculto? Savant probablemente también
224 
+    tenga esos problemas también.
225 
+    </p>
226 
+
227 
+    <p>Si quiere redireccionar múltiples puertos virtuales para un mismo servicio
228 
+    oculto, simplemente añada más líneas <var>HiddenServicePort</var>.
229 
+    Si quiere ejecutar múltiples servicios ocultos desde el mismo cliente Tor,
230 
+    simplemente añada otra línea <var>HiddenServiceDir</var>. Todas las líneas
231 
+    <var>HiddenServicePort</var> subsiguientes se refieren a esta línea <var>HiddenServiceDir</var>, hasta
232 
+    que añada otra línea <var>HiddenServiceDir</var>:
233 
+    </p>
234 
+
235 
+    <pre>
236 
+    HiddenServiceDir /usr/local/etc/tor/hidden_service/
237 
+    HiddenServicePort 80 127.0.0.1:8080
238 
+
239 
+    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
240 
+    HiddenServicePort 6667 127.0.0.1:6667
241 
+    HiddenServicePort 22 127.0.0.1:22
242 
+    </pre>
243 
+
244 
+    <p>Hay algunas consideraciones de anonimato que debería tener en cuenta también:
245 
+    </p>
246 
+    <ul>
247 
+    <li>Como se mencionó antes, tenga cuidado de dejar que su servidor web
248 
+    revele información identificatiba sobre usted, su ordenador, o su posición.
249 
+    Por ejemplo, los lectores pueden probablemente determinar si es thttpd o
250 
+    Apache, y aprender algo acerca de su sistema operativo.</li>
251 
+    <li>Si su ordenador no está online todo el tiempo, su servicio oculto
252 
+    tampoco lo estará. Esto filtra información a un adversario observador.</li>
253 
+    <!-- increased risks over time -->
254 
+    </ul>
255 
+
256 
+    <hr />
257 
+
258 
+    <p>Si tiene sugerancias para mejorar este documento, por favor <a
259 
+    href="<page about/contact>">envíenoslas</a>. ¡Gracias!</p>
260 
+  </div>
261 
+  <!-- END MAINCOL -->
262 
+  <div id = "sidecol">
263 
+#include "side.wmi"
264 
+#include "info.wmi"
265 
+  </div>
266 
+  <!-- END SIDECOL -->
267 
+</div>
268 
+<!-- END CONTENT -->
269 
+#include <foot.wmi>
docs/fsidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/ftor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,119 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>اجرای سرويس گيرنده <a href="<page index>">Tor</a> روی MS Windows</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+
18 
+    <b>توجه داشته باشيد که اين دستورالعمل های نصب برای اجرای سرويس گيرنده Tor روی ويندوز MS (98، 98SE، NT4، 2000 ،XP، ويستا، سررو) است. اگر می خواهيد برای کمک به توسعه شبکه، ترافيک را برای ديگران تقويت کنيد (لطفاً اين کار را بکنيد)، راهنماي<a href="<page docs/tor-doc-relay>">پيکربندی ايستگاه واسطه</a> را مطالعه کنيد.</b>
19 
+    </p>
20 
+
21 
+    <hr />
22 
+    <a id="installing"></a>
23 
+    <h2><a class="anchor" href="#installing">گام اول: بارگيری و نصب Tor</a></h2>
24 
+    <br />
25 
+
26 
+    <p>
27 
+    نصب برای ويندوز MS شامل <a href="<page index>">Tor</a> <a href="http://www.vidalia-project.net/">Vidalia</a> (يک GUI برای Tor) و <a href="http://www.privoxy.org">Privoxy</a> (يک پروکسی فيلترينگ وب) در يک بسته، با سه برنامه از قبل پيکربندی شده برای کار با يکديگر، می باشد. نسخه <a href="../<package-win32-bundle-stable>">ثابت</a> يا <a href="../<package-win32-bundle-alpha>">آزمايشي</a> vبسته نرم افزاری ويندوز را بارگيری کنيد، يا برای گزينه های ديگر در <a href="<page download/download>">صفحه بارگيري</a> جستجو کنيد.
28 
+
29 
+    </p>
30 
+
31 
+    <img alt="صفحه شروع نصب کننده Tor" src="../img/screenshot-win32-installer-splash.png" />
32 
+
33 
+    <p>اگر قبلاً Tor، Vidalia، يا Privoxy را نصب کرده ايد، می توانيد هريک از مؤلفه هايی را که لازم نداريد را در کادر گفتگوی زير از حالت انتخاب بيرون آوريد.
34 
+    </p>
35 
+
36 
+    <img alt="مؤلفه های مورد نظر را جهت نصب انتخاب کنيد" src="../img/screenshot-win32-installer-components.png" />
37 
+
38 
+    <p>پس از کامل کردن نصب کننده، مؤلفه هايی که انتخاب کرده ايد به طور خودکار شروع خواهند شد.
39 
+    </p>
40 
+
41 
+    <!-- <p>Tor comes configured as a client by default. It uses a built-in default configuration file, and most people won't need to change any of the settings. Tor is now installed. </p> -->
42 
+
43 
+    <hr />
44 
+    <a id="using"></a>
45 
+    <h2><a class="anchor" href="#using">گام دوم: پيکربندی برنامه ها برای استفاده از Tor</a></h2>
46 
+
47 
+    <br />
48 
+
49 
+    <p>پس از نصب Tor و Privoxy، بايد برنامه های خود را برای استفاده از آنها پيکربندی کنيد. گام اول راه اندازی مرورگر وب است.</p>
50 
+
51 
+    <p>اگر از Privoxy استفاده می کنيد (ما توصيه می کنيم از ان استفاده کنيد)، بسته نرم افزاری Vidalia  <a href="https://addons.mozilla.org/firefox/2275/">پلاگين Torbutton </a> را برای شما نصب می کند. Firefox را دوباره شروع کنيد، اکنون همه را تنظيم کرده ايد:
52 
+    </p>
53 
+
54 
+    <img alt="پلاگين Torbutton برای Firefox" src="../img/screenshot-torbutton.png" border="1">
55 
+
56 
+    <br />
57 
+
58 
+    <p>
59 
+    (<a href="https://torbutton.torproject.org/">اطلاعات بيشتر درباره Torbutton را در اينجا مشاهده کنيد</a>. اگر می خواهيد Firefox را روی رايانه ديگری غير از آنکه Tor روی آن است، اجرا کنيد، به <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">مدخل سؤالات متدوال درمورد اجرای Tor روی رايانه متفاوت</a> مراجعه کنيد. اگر لازم است از مرورگر ديگری غير از Firefox استفاده کنيد، بايد <a href="<page docs/tor-doc-web>">تنظيمات پروکسی را خودتان پيکربندی کنيد</a>.)
60 
+
61 
+    </p>
62 
+
63 
+    <p>استفاده از Privoxy <strong>ضروری است</strong> زيرا <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">اگر مرورگرها مستقيماً از پروکسی SOCKS استفاده کنند، درخواست های DNS شما را فاش می کنند</a> و اين برای گمنام ماندن شما بد است. Privoxy همچنين سرصفحه های خطرناک خاص را از درخواست های وب شما حذف می کند و سايت های تبليغی مضر مانند Doubleclick را مسدود می کند.</p>
64 
+
65 
+    <p>برای Torify ساير برنامه هايی که از پروکسی های HTTP پشتيبانی می کنند، فقط آنها را به Privoxy (يعنی درگاه ميزبان محلی 8118) دلالت دهيد. برای استفاده از SOCKS به طور مستقيم (برای پيام رسانی فوری، Jabber، IRC و غيره) می توانيد برنامه خود را مستقيماً در Tor (يدرگاه ميزبان محلی 9050) دلالت دهيد، اما به<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">اين مدخل سؤالات متداول</a> مراجعه کنيد تا ببينيد چرا ممکن است اين کار خطرناک باشد.  در خصوص برنامه هايی که نه از SOCKS و نه از HTTP پشتيبانی می کنند به SocksCap يا <a href="http://www.freecap.ru/eng/">FreeCap</a> مراجعه کنيد. (FreeCap يک نرم افزار رايگان است؛ SocksCap اختصاصی است.)</p>
66 
+
67 
+    <p>برای کسب اطلاعات در مورد نحوه Torify ساير برنامه ها، <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify HOWTO</a> را بررسی کنيد.
68 
+    </p>
69 
+
70 
+    <hr />
71 
+    <a id="verify"></a>
72 
+    <h2><a class="anchor" href="#verify">گام سوم: کسب اطمينان از اينکه برنامه کار می کند</a></h2>
73 
+    <br />
74 
+
75 
+    <p>
76 
+    بررسی کنيد که Privoxy و Vidalia در حال اجرا باشند. نماد Privoxy يک دايره آبی يا سبز با يک "P" در آن است، Vidalia برای نشان دادن اينکه Tor در حال اجرا است از يک پياز سبز کوچک و برای نشان دادن اينکه  در حال اجرا نيست از يک پياز تيره با يک "X" قرمز استفاده می کند. با کليک راست بر نماد Vidalia در سينی سيستم خود و انتخاب "شروع" يا "توقف" از منو (همانطور که در زير نشان داده شده است)، می توانيد Tor را شروع يا متوقف کنيد.
77 
+
78 
+    </p>
79 
+
80 
+    <img alt="نماد صفحه Vidalia" src="../img/screenshot-win32-vidalia.png">
81 
+
82 
+    <p>
83 
+    بعد، بايد می توانيد با Tor از مرورگر خود استفاده کنيد و اطمينان حاصل کنيد که آدرس IP شما ناشناخته خواهد ماند. بر روی <a href="https://check.torproject.org/">تشخيص دهنده Tor</a> کليک کنيد و ببينيد آيا فکر می کند شما از Tor استفاده می کنيد يا خير. #<a href="http://ipchicken.com/">اين سايت</a> #برای مشاهده اينکه فکر می کند شما از چه آدرس IP استفاده می کنيد. (اگر آن سايت فعال نيست، درخصوص پيشنهادات ديگر در مورد نحوه آزمايش Tor خود، به <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">اين مدخل سؤالات متداول</a> مراجعه کنيد.)
84 
+    </p>
85 
+
86 
+    <p>اگر از يک ديوار آتش شخصی استفاده می کنيد که قابليت رايانه شما را به اتصال به خودش محدود می کند، دقت کنيد که اتصالات از برنامه های محلی را به درگاه محلی 8118 و 9050 مجاز کنيد. اگر ديوار آتش شما اتصالات خروجی را مسدود می کند، يک منفذ ايجاد کنيد تا بتواند حداقل به درگاه های TCP 80 و 443 متصل شود، سپس به <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">اين مدخل سؤالات متداول</a> مراجعه کنيد.
87 
+    </p>
88 
+
89 
+    <p>اگر هنوز کار نمی کند، برای تذکرات به <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">اين مدخل سؤالات متداول</a> مراجعه کنيد.</p>
90 
+
91 
+    <p>
92 
+    اگر کار می کند، برای اطلاعات بيشتر به <a href="<page download/download>#Warning">Tor چه چيزهای ارائه می کند و چه چيزهايی ارائه نمی کند</a> مراجعه کنيد.
93 
+
94 
+    </p>
95 
+
96 
+    <hr />
97 
+    <a id="server"></a> <a id="relay"></a>
98 
+    <h2><a class="anchor" href="#relay">گام چهارم: پيکربندی Tor به عنوان ايستگاه واسطه</a></h2>
99 
+    <br />
100 
+
101 
+    <p>شبکه Tor برای اهدای پهنای باند بر داوطلبان متکی است. هرچه تعداد کسانی که ايستگاه های واسطه را اداره می کنند بيستر باشد، شبکه Tor سريع تر خواهد بود. اگر به هر طريق حداقل 20 کيلوبايت داريد، لطفاً با پيکربندی Tor خود به عنوان يک ايستگاه واسطه، کمک کنيد. استفاده از ايستگاه های واسطه Tor به دليل ويژگی های زيادی آسان و راحت است، از جمله محدودکردن سرعت پهنای باند، روش های خروج، بنابراين می توانيد خود از معرض شکايات سوء استفاده محدود کنيد، و آدرس های IP پويا را پشتيبانی کنيد.</p>
102 
+
103 
+    <p>آنچه کاربران Tor را ايمن نگه می دارد، داشتن ايستگاه های واسطه در مکان های مختلف در اينترنت است. ازآنجاکه سايت های دور نمی توانند بفهمند که اتصالات از رايانه شما ايجاد شده يا توسط ديگران، <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">شما همچنين می توانيد خودتان گمنامی قوی تری داشته باشيد</a>. </p>
104 
+
105 
+    <p>موارد بيشتر را در راهنمای <a href="<page docs/tor-doc-relay>">پيکربندی ايستگاه واسطه</a> مطالعه کنيد.</p>
106 
+
107 
+    <hr />
108 
+
109 
+    <p>اگر پيشنهاداتی برای بهبود اين سند داريد، لطفاً <a href="<page about/contact>">آنها را برای ما ارسال کنيد</a>. سپاسگزاريم!</p>
110 
+  </div>
111 
+  <!-- END MAINCOL -->
112 
+  <div id = "sidecol">
113 
+#include "side.wmi"
114 
+#include "info.wmi"
115 
+  </div>
116 
+  <!-- END SIDECOL -->
117 
+</div>
118 
+<!-- END CONTENT -->
119 
+#include <foot.wmi>
docs/fr/N900.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,158 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21979 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: N900 Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/N900>">N900</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="Maemo"></a>
14 
+    <h2><a class="anchor" href="#Maemo">Installer Tor sur Maemo</a></h2>
15 
+    <br />
16 
+    <p>
17 
+    Si vous avez un appareil fonctionnant sous Maemo qui n'est pas <a
18 
+    href="#N900">le N900</a>, nous vous suggérons d'installer le paquet Tor
19 
+    depuis le <a href="http://maemo.org/packages/view/tor/">site web de
20 
+    Maemo</a>. Le projet Tor ne compile pas ces paquets. Ils sont maintenus par
21 
+    la communauté Maemo.
22 
+    </p>
23 
+
24 
+    <a id="N900"></a>
25 
+    <h2><a class="anchor" href="#N900">Installer Tor sur le N900</a></h2>
26 
+    <br />
27 
+    <p>
28 
+    Les instructions qui suivent devraient vous aider à installer <a
29 
+    href="https://garage.maemo.org/projects/tor-status">un contrôleur Tor
30 
+    expérimental</a> ainsi que Tor packagé pour le téléphone Nokia N900. C'est
31 
+    pour le moment une configuration non testée. Le navigateur dans cette
32 
+    configuration ne dispose pas de Torbutton et il ne devrait pas être utilisé
33 
+    pour le moment si vous avez des besoins impératifs d'anonymat sécurisé.
34 
+    </p>
35 
+
36 
+    <p>
37 
+    Ouvrez le gestionnaire d'applications: <br /> <a
38 
+    href="../img/N900/1_app_menu.png"> <img border="0" alt="N900 application
39 
+    menu" src="../img/N900/1_app_menu-small.png"/> </a>
40 
+    </p>
41 
+
42 
+    <p>
43 
+    Cliquez sur le menu du gestionnaire d'applications en haut de l'écran: <br
44 
+    /> <a href="../img/N900/2_app_manager.png"> <img border="0" alt="N900
45 
+    application manager" src="../img/N900/2_app_manager-small.png"/> </a>
46 
+    </p>
47 
+
48 
+    <p>
49 
+    Selectionnez 'Catalogues d'Applications': <br /> <a
50 
+    href="../img/N900/3_app_managermenu.png"> <img border="0" alt="N900
51 
+    application catalogs" src="../img/N900/3_app_managermenu-small.png"/> </a>
52 
+    </p>
53 
+
54 
+    <p>
55 
+    Appuyez sur 'New' pour activer les dépôts développement externes Maemo. <br
56 
+    /> <small>Note: Ce dépôt contient des paquets non testés qui peuvent
57 
+    endommager votre appareil. <br /> Consultez <a
58 
+    href="http://wiki.maemo.org/Extras-devel">Extra-devel</a> pour plus de
59 
+    détails. Vous devriez probablement désactiver ces dépôts après avoir
60 
+    installé Tor, vous êtes prévenus des risques.</small> <br /> <a
61 
+    href="../img/N900/4_catalog_list.png"> <img border="0" alt="N900 catalog
62 
+    list" src="../img/N900/4_catalog_list-small.png"/> </a>
63 
+    </p>
64 
+
65 
+    <p>
66 
+    Entrez les informations suivantes dans l'écran d'ajout de catalogue:
67 
+    <p>
68 
+    <pre>
69 
+    Catalog name:    Extras devel
70 
+    Web address:    http://repository.maemo.org/extras-devel/
71 
+    Distribution:        fremantle
72 
+    Components:    free non-free
73 
+    </pre>
74 
+    </p>
75 
+    <br /> Assurez vous que 'Désactivé' est décoché et appuyez sur 'Enregistrer'
76 
+    et attendez que la liste des paquets se mette à jour.<br /> <a
77 
+    href="../img/N900/5_new_catalog.png"> <img border="0" alt="N900 new catalog"
78 
+    src="../img/N900/5_new_catalog-small.png"/> </a>
79 
+    </p>
80 
+
81 
+    <p>
82 
+    Pressez sur 'Download' dans le gestionnaire d'applications: <br /> <a
83 
+    href="../img/N900/6_app_manager.png"> <img border="0" alt="N900 app manager"
84 
+    src="../img/N900/6_app_manager-small.png"/> </a>
85 
+    </p>
86 
+
87 
+    <p>
88 
+    Sélectionnez la catégorie Réseau (ou recherchez Tor): <br /> <a
89 
+    href="../img/N900/7_app_categories.png"> <img border="0" alt="N900
90 
+    application categories" src="../img/N900/7_app_categories-small.png"/> </a>
91 
+    </p>
92 
+
93 
+    <p>
94 
+    Descendez et sélectionnez 'Tor Status Area Applet': <br /> <a
95 
+    href="../img/N900/8_app_list.png"> <img border="0" alt="N900 application
96 
+    list" src="../img/N900/8_app_list-small.png"/> </a>
97 
+    </p>
98 
+
99 
+    <p>
100 
+    Acceptez l'avertissement et appuyez sur 'Continue': <br /> <a
101 
+    href="../img/N900/9_disclaimer.png"> <img border="0" alt="N900 disclaimer"
102 
+    src="../img/N900/9_disclaimer-small.png"/> </a>
103 
+    </p>
104 
+
105 
+    <p>
106 
+    Lorsque l'installation est terminée, désactivez les dépôts de développement
107 
+    externes et redémarrez l'appareil: <br /> <a
108 
+    href="../img/N900/10_success.png"> <img border="0" alt="N900 success"
109 
+    src="../img/N900/10_success-small.png"/> </a>
110 
+    </p>
111 
+
112 
+    <p>
113 
+    Après avoir redémarrer le N900, ouvrez le menu d'état: <br /> <a
114 
+    href="../img/N900/11_after_rebooting.png"> <img border="0" alt="N900 status
115 
+    menu post-reboot" src="../img/N900/11_after_rebooting-small.png"/> </a>
116 
+    </p>
117 
+
118 
+    <p>
119 
+    Sélectionnez 'The Onion Router' dans la liste: <br /> <a
120 
+    href="../img/N900/12_status_menu.png"> <img border="0" alt="N900 status menu
121 
+    selection" src="../img/N900/12_status_menu-small.png"/> </a>
122 
+    </p>
123 
+
124 
+    <p>
125 
+    Activez le routage en oignon, et appuyez sur 'Save': <br /> <a
126 
+    href="../img/N900/13_enable_tor.png"> <img border="0" alt="N900 enabling
127 
+    Tor" src="../img/N900/13_enable_tor-small.png"/> </a>
128 
+    </p>
129 
+
130 
+    <p>
131 
+    Visitez <a href="https://check.torproject.org/">TorCheck</a> afin de
132 
+    confirmer que vous faîtes circuler votre trafic à travers Tor: <br /> <a
133 
+    href="../img/N900/14_check_tor.png"> <img border="0" alt="N900 check Tor"
134 
+    src="../img/N900/14_check_tor-small.png"/> </a>
135 
+    </p>
136 
+
137 
+    <p>
138 
+    A noter que cela ne vous installera pas forcément la dernière version stable
139 
+    de Tor.  De plus, Torbutton n'est pas disponible sur le navigateur web du
140 
+    N900. Ainsi, même si ce dernier reste utile pour le contournement, il est
141 
+    n'est probablement pas adapté à de grandes exigences en matière d'anonymat
142 
+    sur le web.
143 
+    </p>
144 
+
145 
+    <hr />
146 
+
147 
+    <p>Si vous avez des suggestions pour améliorer ce document, n'hésitez pas <a
148 
+    href="<page about/contact>">à nous les faire parvenir</a>. Merci !</p>
149 
+  </div>
150 
+  <!-- END MAINCOL -->
151 
+  <div id = "sidecol">
152 
+#include "side.wmi"
153 
+#include "info.wmi"
154 
+  </div>
155 
+  <!-- END SIDECOL -->
156 
+</div>
157 
+<!-- END CONTENT -->
158 
+#include <foot.wmi>
docs/fr/android.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,138 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22402 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Android Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/android>">Android</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="Android"></a>
14 
+    <h2><a class="anchor" href="#Android">Tor sur Android</a></h2>
15 
+    <br />
16 
+    <p>
17 
+    Tor est disponible sous Android en installant un paquet nommé Orbot.
18 
+    </p>
19 
+    <p>
20 
+    Orbot est une application qui permet aux utilisateurs de téléphone mobile
21 
+    d'accéder au web, à la messagerie électronique et à la messagerie
22 
+    instantanée sans être observé ou bloqué par le fournisseur d'accès internet
23 
+    mobile. Orbot apporte les fonctionnalités de Tor sur le système
24 
+    d'exploitation mobile Android.
25 
+    </p>
26 
+    <p>
27 
+    Orbot contien Tor, libevent et privoxy. Orbot fournit un proxy HTTP local et
28 
+    les interfaces de proxy standardes SOCKS4A/SOCKS pour accéder au réseau
29 
+    Tor. Orbot a la possibilité, lorsqu'il dispose des autorisations requises,
30 
+    de "torifier" de manière transparente l'ensemble du trafic TCP de votre
31 
+    appareil Android.
32 
+    </p>
33 
+
34 
+    <a id="Market"></a>
35 
+    <h2><a class="anchor" href="#Market">Installer Tor depuis l'Android Market</a></h2>
36 
+    <br />
37 
+    <p>
38 
+    Orbot n'est pas pour le moment dans l'Android Market. Il le sera dans un
39 
+    futur assez proche.
40 
+    </p>
41 
+
42 
+    <a id="Manual"></a>
43 
+    <h2><a class="anchor" href="#Manual">Installer Tor depuis notre site web</a></h2>
44 
+    <br />
45 
+    <p>
46 
+    Vous pouvez télécharger notre version béta la plus récente d'Orbot ainsi
47 
+    qu'une signature gpg depuis notre serveur.
48 
+    </p>
49 
+
50 
+    <a id="Screenshots"></a>
51 
+    <h2><a class="anchor" href="#Screenshots">Copies d'écran de Tor sur Android</a></h2>
52 
+    <br />
53 
+    <p>
54 
+    <a href="../img/android/android-off.jpg"> <img border="0" alt="Android Tor
55 
+    off" src="../img/android/android-off-150x150.jpg"/> </a> <a
56 
+    href="../img/android/android-bootstrapping.jpg"> <img border="0"
57 
+    alt="Android Tor bootstrapping"
58 
+    src="../img/android/android-bootstrapping-150x150.jpg"/> </a> <a
59 
+    href="../img/android/android-activated.jpg"> <img border="0" alt="Android
60 
+    Tor activated" src="../img/android/android-activated-150x150.jpg"/> </a> <a
61 
+    href="../img/android/android-settings.jpg"> <img border="0" alt="Android Tor
62 
+    settings" src="../img/android/android-settings-150x150.jpg"/> </a>
63 
+    </p>
64 
+
65 
+    <a id="ProxySettings"></a>
66 
+    <h2><a class="anchor" href="#ProxySettings">Paramètres de proxy et configuration
67 
+    </a></h2>
68 
+    <br />
69 
+    <p>
70 
+    Orbot offre trois interfaces pour accéder au réseau Tor:
71 
+    <ul>
72 
+    <li>SOCKS 4A/5 proxy 127.0.0.1:9050</li>
73 
+    <li>HTTP proxy 127.0.0.1:8118 </li>
74 
+    <li>Proxy transparent (sur certains appareils)</li>
75 
+    </ul>
76 
+    </p>
77 
+
78 
+    <a id="Notes"></a>
79 
+    <h2><a class="anchor" href="#Notes">Notes spécifiques à cette platforme</a></h2>
80 
+    <br />
81 
+    <p>
82 
+    Pour les appareils Android 1.x (G1, MyTouch3G, Hero, Droid Eris, Cliq,
83 
+    Moment):
84 
+    <ul>
85 
+    <li>Le navigateur "ProxySurf" disponible sur l'Android Market permet d'utiliser
86 
+    un proxy. Paramétrez simplement le proxy HTTP avec l'adresse '127.0.0.1' et
87 
+    le port '8118'.</li>
88 
+    <li>En ce qui concerne la messagerie instantanée, vous pouvez essayer "Beem"
89 
+    disponible sur le marché et de paramétrer le proxy sur SOCKS5 '127.0.0.1' et
90 
+    sur le port '9050'.</li>
91 
+    </ul>
92 
+    </p>
93 
+    <p>
94 
+    Pour les appareils Android 2.x: Droid, Nexus One
95 
+    <ul>
96 
+    <li>Vous devez être disposer du mot de passe root pour qu'Orbot relaye
97 
+    l'ensemble du traffic TCP de manière transparente.</li>
98 
+    <li>Pour les téléphones non-modifiés et qui ne disposent pas d'un accès root,
99 
+    vous devrez configurer manuellement chacune de vos applications.</li>
100 
+    <li>Si vous disposez du mot de passe root, que votre appareil soit basé sur
101 
+    Android 1.x ou 2.x , Orbot relayera automatiquement tout le traffic vers les
102 
+    ports 80 et 443 ainsi que l'intégralité des requêtes DNS de manière
103 
+    transparente. Cela inclus le navigateur web interne, Gmail, YouTube, Maps et
104 
+    toutes les applications qui utilisent le trafic web standard.</li>
105 
+    </ul>
106 
+    </p>
107 
+
108 
+    <a id="Source"></a>
109 
+    <h2><a class="anchor" href="#Source">Accès au code source</a></h2>
110 
+    <br />
111 
+    <p>
112 
+    L'intégralité du code source est disponible sur le <a
113 
+    href="https://svn.torproject.org/svn/projects/android/trunk/Orbot/">dépôt
114 
+    subversion Orbot</a>.
115 
+    </p>
116 
+
117 
+    <p>
118 
+    A noter que cela ne vous installera pas forcément la dernière version stable
119 
+    de Tor.  De plus, Torbutton n'est pas disponible sur le navigateur web
120 
+    d'Android. Ainsi, même si ce dernier reste utile pour le contournement, il
121 
+    est n'est probablement pas adapté à un de grandes exigences en matière
122 
+    d'anonymat sur le web.
123 
+    </p>
124 
+
125 
+    <hr />
126 
+
127 
+    <p>Si vous avez des suggestions pour améliorer ce document, n'hésitez pas <a
128 
+    href="<page contact>">à nous les faire parvenir</a>. Merci !</p>
129 
+  </div>
130 
+  <!-- END MAINCOL -->
131 
+  <div id = "sidecol">
132 
+#include "side.wmi"
133 
+#include "info.wmi"
134 
+  </div>
135 
+  <!-- END SIDECOL -->
136 
+</div>
137 
+<!-- END CONTENT -->
138 
+#include <foot.wmi>
docs/fr/debian-vidalia.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,121 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22269 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Vidalia: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian-vidalia>">Vidalia Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a> <a id="packages"></a>
14 
+    <h2><a class="anchor" href="#debian">Vidalia sur Ubuntu ou Debian</a></h2>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>N'utilisez pas les paquets du dépôt Ubuntu universe.</b> Ils ne sont pas
19 
+    maintenus et sont périmés. En les utilisant, vous passez à côté de
20 
+    nombreuses corrections de failles de sécurité et vous manquerez de
21 
+    stabilité.
22 
+    </p>
23 
+
24 
+    <p>
25 
+    You'll need to set up our package repository before you can fetch
26 
+    Vidalia. First, you need to figure out the name of your distribution. If
27 
+    you're using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty",
28 
+    8.10 is "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's
29 
+    "etch", and Debian Lenny is "lenny". Then add this line to your
30 
+    <tt>/etc/apt/sources.list</tt> file:<br />
31 
+    <pre>
32 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
33 
+    </pre>
34 
+    substituez le mot approprié (etch, lenny, sid, karmic, jaunty, intrepid,
35 
+    hardy) à la place de &lt;DISTRIBUTION&gt;.
36 
+    </p>
37 
+
38 
+    <p>
39 
+    Ensuite, ajoutez la clef gpg utilisée pour signer les paquets en lançant les
40 
+    commandes suivantes sur votre shell:
41 
+    <pre>
42 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
43 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
44 
+    </pre>
45 
+    Rafraîchissez ensuite vos sources et installez Vidalia en lançant les
46 
+    commandes suivantes dans voter shell:
47 
+    <pre>
48 
+    apt-get update
49 
+    apt-get install vidalia
50 
+    </pre>
51 
+    </p>
52 
+
53 
+    <p>
54 
+    Maintenant, Vidalia est installé et fonctionne. Allez à <a href="<page
55 
+    docs/tor-doc-unix>#polipo">la deuxième étape</a> des instructions "Vidalia
56 
+    sur Linux/Unix".
57 
+    </p>
58 
+
59 
+    <p style="font-size: small">
60 
+    Le nom DNS <code>deb.torproject.org</code> est en fait un jeu de serveurs
61 
+    indépendants conservés dans une base de données DNS tournante.  Si pour une
62 
+    raison quelconque, vous ne pouvez y accéder, vous pouvez utiliser l'un des
63 
+    noms spécifiques à la place. Essayez avec
64 
+    <code>deb-master.torproject.org</code>, <code>mirror.netcologne.de</code> ou
65 
+    <code>vidalia.mirror.youam.de</code>.
66 
+    </p>
67 
+
68 
+    <hr />
69 
+
70 
+    <a id="source"></a>
71 
+    <h2><a class="anchor" href="#source">Construire à partir des sources</a></h2>
72 
+    <br />
73 
+
74 
+    <p>
75 
+    Si vous désirez construire vos propres paquets deb à partir des sources,
76 
+    vous devez ajouter la bonne configuration <tt>deb-src</tt> à votre fichier
77 
+    <tt>sources.list</tt>.
78 
+    <pre>
79 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
80 
+    </pre>
81 
+    Vous aurez également besoin d'installer les paquets nécéssaires à la
82 
+    construction des paquets debian et des paquets de Vidalia.
83 
+    <pre>
84 
+    apt-get install build-essential fakeroot devscripts qt4-dev-tools qt4-designer libqt4-dev g++ cmake
85 
+    apt-get build-dep vidalia
86 
+    </pre>
87 
+    Ensuite, vous pouvez lancer la construction de Vidalia dans
88 
+    ~/debian-packages!
89 
+    <pre>
90 
+    mkdir ~/debian-packages; cd ~/debian-packages
91 
+    apt-get source vidalia
92 
+    cd vidalia-*
93 
+    debuild -rfakeroot -uc -us
94 
+    cd ..
95 
+    </pre>
96 
+    Maintenant, vous pouvez installer le nouveau paquet:
97 
+    <pre>
98 
+    sudo dpkg -i vidalia_*.deb
99 
+    </pre>
100 
+    </p>
101 
+
102 
+    <p>
103 
+    Maintenant, Vidalia est installé et fonctionne. Allez à <a href="<page
104 
+    docs/tor-doc-unix>#polipo">la deuxième étape</a> des instructions "Vidalia
105 
+    sur Linux/Unix".
106 
+    </p>
107 
+
108 
+    <hr />
109 
+
110 
+    <p>Si vous avez des suggestions pour améliorer le contenu de ce document, merci
111 
+    <a href="<page about/contact>">de nous les faire parvenir</a>. Merci !</p>
112 
+  </div>
113 
+  <!-- END MAINCOL -->
114 
+  <div id = "sidecol">
115 
+#include "side.wmi"
116 
+#include "info.wmi"
117 
+  </div>
118 
+  <!-- END SIDECOL -->
119 
+</div>
120 
+<!-- END CONTENT -->
121 
+#include <foot.wmi>
docs/fr/debian.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,189 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22268 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian>">Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <h2><a class="anchor" href="#debian">Option un: Tor sur Debian lenny, Debian
15 
+    sid, ou Debian testing</a></h2>
16 
+    <br />
17 
+
18 
+    <p>
19 
+    If you're using Debian stable (lenny), unstable (sid), or testing (squeeze),
20 
+    just run<br />
21 
+    <tt>apt-get install tor tor-geoipdb</tt> as root.
22 
+    </p>
23 
+
24 
+    <p>
25 
+    Attention, cela n'installe pas forcément la toute dernière version stable de
26 
+    Tor. Néanmoins, vous recevrez d'importantes corrections de failles de
27 
+    sécurité. Pour être certain d'utiliser la dernière version stable de Tor,
28 
+    utilisez la deuxième option ci-dessous.
29 
+    </p>
30 
+
31 
+    <p>
32 
+    Désormais, Tor est installé et fonctionne. Rendez-vous à <a href="<page
33 
+    docs/tor-doc-unix>#polipo">l'étape deux</a> des instructions "Tor sur
34 
+    Linux/Unix".
35 
+    </p>
36 
+
37 
+    <hr />
38 
+
39 
+    <a id="ubuntu"></a> <a id="packages"></a>
40 
+    <h2><a class="anchor" href="#ubuntu">Option deux: Tor sur Ubuntu ou Debian</a></h2>
41 
+    <br />
42 
+
43 
+    <p>
44 
+    <b>N'utilisez pas les paquets du dépôt universe d'Ubuntu.</b> Ils ne sont
45 
+    pas maintenus et sont périmés. Cela signifie que vous manquerez de stabilité
46 
+    et de correction de failles de sécurité.
47 
+    </p>
48 
+
49 
+    <p>
50 
+    You'll need to set up our package repository before you can fetch
51 
+    Tor. First, you need to figure out the name of your distribution. If you're
52 
+    using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty", 8.10 is
53 
+    "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's "etch",
54 
+    and Debian Lenny is "lenny". Then add this line to your
55 
+    <tt>/etc/apt/sources.list</tt> file:<br />
56 
+    <pre>
57 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
58 
+    </pre>
59 
+    ou vous substituez le nom de votre distribution (etch, lenny, sid, karmic,
60 
+    jaunty, intrepid, hardy ou n'importe quoi d'autre) à la place de
61 
+    &lt;DISTRIBUTION&gt;.
62 
+    </p>
63 
+
64 
+    <p>
65 
+    Ajoutez alors la clef gpg utilisée pour signer les paquets en lançant les
66 
+    commandes suivantes dans votre shell:
67 
+    <pre>
68 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
69 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
70 
+    </pre>
71 
+    Maintenant, vous pouvez rafraîchir vos sources et installer Tor en lançant
72 
+    les commandes suivantes dans votre shell:
73 
+    <pre>
74 
+    apt-get update
75 
+    apt-get install tor tor-geoipdb
76 
+    </pre>
77 
+    </p>
78 
+
79 
+    <p>
80 
+    Désormais, Tor est installé et fonctionne. Rendez-vous à <a href="<page
81 
+    docs/tor-doc-unix>#polipo">l'étape deux</a> des instructions "Tor sur
82 
+    Linux/Unix".
83 
+    </p>
84 
+
85 
+    <p style="font-size: small">
86 
+    Le nom DNS <code>deb.torproject.org</code> est en fait un ensemble de
87 
+    serveurs indépendants dans une configuration DNS round-robin.  Si pour une
88 
+    raison, vous ne pouvez pas y accéder, vous pouvez utiliser le nom d'un
89 
+    serveur dans la liste suivante à la place.  Essayez
90 
+    <code>deb-master.torproject.org</code>, <code>mirror.netcologne.de</code> ou
91 
+    <code>tor.mirror.youam.de</code>.
92 
+    </p>
93 
+
94 
+    <hr />
95 
+
96 
+    <a id="development"></a>
97 
+    <h2><a class="anchor" href="#development">Option trois: Utiliser la branche de
98 
+    développement de Tor sur Debian ou Ubuntu</a></h2>
99 
+    <br />
100 
+
101 
+    <p>If you want to use the <a href="<page download/download>#packagediff">development
102 
+    branch</a> of Tor instead (more features and more bugs), you need to add a
103 
+    different set of lines to your <tt>/etc/apt/sources.list</tt> file:<br />
104 
+    <pre>
105 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
106 
+    deb     http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
107 
+    </pre>
108 
+    ou vous substituez, une fois de plus, le nom de votre distribution (etch,
109 
+    lenny, sid, karmic, jaunty, intrepid, hardy) à la place de
110 
+    &lt;DISTRIBUTION&gt;.
111 
+    </p>
112 
+
113 
+    <p>
114 
+    Lancez ensuite les commandes qui suivent dans vote shell:
115 
+    <pre>
116 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
117 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
118 
+    apt-get update
119 
+    apt-get install tor tor-geoipdb
120 
+    </pre>
121 
+    </p>
122 
+
123 
+    <p>
124 
+    Désormais, Tor est installé et fonctionne. Rendez-vous à <a href="<page
125 
+    docs/tor-doc-unix>#polipo">l'étape deux</a> des instructions "Tor sur
126 
+    Linux/Unix".
127 
+    </p>
128 
+
129 
+    <hr />
130 
+
131 
+    <a id="source"></a>
132 
+    <h2><a class="anchor" href="#source">Construire à partir du code source</a></h2>
133 
+    <br />
134 
+
135 
+    <p>
136 
+    Si vous désirez construire vos propres paquets deb à partir des fichiers
137 
+    sources, vous devez d'abord ajouter un <tt>deb-src</tt> approprié à
138 
+    <tt>sources.list</tt>.
139 
+    <pre>
140 
+    # For the stable version.
141 
+    # For the unstable version.
142 
+
143 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
144 
+
145 
+
146 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
147 
+    deb-src http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
148 
+    </pre>
149 
+    Vous avez également besoin d'installer les paquets nécessaires pour
150 
+    construire vos propres paquets deb ainsi que les paquets requis pour
151 
+    construire Tor:
152 
+    <pre>
153 
+    apt-get install build-essential fakeroot devscripts
154 
+    apt-get build-dep tor
155 
+    </pre>
156 
+    Maintenant, vous pouvez construire Tor dans ~/debian-packages:
157 
+    <pre>
158 
+    mkdir ~/debian-packages; cd ~/debian-packages
159 
+    apt-get source tor
160 
+    cd tor-*
161 
+    debuild -rfakeroot -uc -us
162 
+    cd ..
163 
+    </pre>
164 
+    Maintenant, vous pouvez installer le nouveau paquet:
165 
+    <pre>
166 
+    sudo dpkg -i tor_*.deb
167 
+    </pre>
168 
+    </p>
169 
+
170 
+    <p>
171 
+    Désormais, Tor est installé et fonctionne. Rendez-vous à <a href="<page
172 
+    docs/tor-doc-unix>#polipo">l'étape deux</a> des instructions "Tor sur
173 
+    Linux/Unix".
174 
+    </p>
175 
+
176 
+    <hr />
177 
+
178 
+    <p>Si vous avez des suggestions pour améliorer ce document, merci de <a
179 
+    href="<page about/contact>">nous en faire part</a>. Merci !</p>
180 
+  </div>
181 
+  <!-- END MAINCOL -->
182 
+  <div id = "sidecol">
183 
+#include "side.wmi"
184 
+#include "info.wmi"
185 
+  </div>
186 
+  <!-- END SIDECOL -->
187 
+</div>
188 
+<!-- END CONTENT -->
189 
+#include <foot.wmi>
docs/fr/rpms.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,88 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21907 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: CentOS/Fedora/OpenSUSE Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/rpms>">RPMs</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="rpms"></a>
14 
+    <h2><a class="anchor" href="#rpms">Paquets Tor pour les distributions basées sur
15 
+    RPM.</a></h2>
16 
+    <br />
17 
+
18 
+    <p>N'utilisez pas les paquets des dépôts officiels. Ils sont très souvent
19 
+    périmés et vous ne bénéficieriez pas de corrections de sécurité et de
20 
+    stabilité.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    Vous aurez besoin de configurer votre dépôt de paquets avant de récupérer
25 
+    Tor.  En assumant que yum utilise le fichier /etc/yum.repos.d/, créez un
26 
+    fichier nommé torproject.repo.  Editez ce fichier avec les informations
27 
+    suivantes:
28 
+    <pre>[torproject]
29 
+    name=Tor and Vidalia
30 
+    enabled=1
31 
+    autorefresh=0
32 
+    baseurl=http://deb.torproject.org/torproject.org/rpm/DISTRIBUTION/
33 
+    type=rpm-md
34 
+    gpgcheck=1
35 
+    gpgkey=http://deb.torproject.org/torproject.org/rpm/RPM-GPG-KEY-torproject.org
36 
+    </pre>
37 
+
38 
+    Si vous désirez suivre les versions stables de Tor, vous devriez remplacer
39 
+    le mot DISTRIBUTION par l'un des mots suivants: centos4, centos5, fc10,
40 
+    fc11, fc12, suse</p>
41 
+
42 
+    <p>Pour suivre les versions expérimentales, remplacez le mot DISTRIBUTION avec
43 
+    l'un des mots suivants: centos4-experimental, centos5-experimental,
44 
+    fc10-experimental, fc11-experimental, fc12-experimental, suse-experimental</p>
45 
+
46 
+    <p>
47 
+    Maintenant, Tor est installé et fonctionne. Allez à <a href="<page
48 
+    docs/tor-doc-unix>#polipo">la deuxième étape</a> des instructions "Tor sur
49 
+    Linux/Unix".
50 
+    </p>
51 
+
52 
+    <p style="font-size: small">
53 
+    Le nom DNS <code>deb.torproject.org</code> est en fait un jeu de serveurs
54 
+    indépendant dans une configuration DNS round robin.  Si pour une raison ou
55 
+    une autre, vous ne pouvez pas y accéder, vous pouvez utiliser le nom d'un
56 
+    des serveurs à la place.  Essayez avec
57 
+    <code>deb-master.torproject.org</code>, <code>mirror.netcologne.de</code> ou
58 
+    <code>tor.mirror.youam.de</code>.
59 
+    </p>
60 
+
61 
+    <hr />
62 
+
63 
+    <hr />
64 
+
65 
+    <a id="source"></a>
66 
+    <h2><a class="anchor" href="#source">Compiler à partir des sources</a></h2>
67 
+    <br />
68 
+
69 
+    <p>
70 
+    Si vous désirez compiler à partir des sources, merci de suivre <a
71 
+    href="<gitblob>doc/tor-rpm-creation.txt">les instructions de création des
72 
+    RPM</a>.
73 
+    </p>
74 
+
75 
+    <hr />
76 
+
77 
+    <p>Si vous avez des suggestions pour améliorer le contenu de ce document, merci
78 
+    <a href="<page about/contact>">de nous les faire parvenir</a>. Merci !</p>
79 
+  </div>
80 
+  <!-- END MAINCOL -->
81 
+  <div id = "sidecol">
82 
+#include "side.wmi"
83 
+#include "info.wmi"
84 
+  </div>
85 
+  <!-- END SIDECOL -->
86 
+</div>
87 
+<!-- END CONTENT -->
88 
+#include <foot.wmi>
docs/fr/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/fr/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,221 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Utiliser le client <a href="<page index>">Tor</a> sous Mac OS X</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Notez que ce sont les instructions d'installation pour utiliser le client
18 
+    Tor sous MacOSX. Si vous désirez installer un relais Tor pour agrandir le
19 
+    réseau (n'hésitez pas), lisez la page <a href="<page
20 
+    docs/tor-doc-relay>">Configurer un serveur</a>.</b>
21 
+    </p>
22 
+
23 
+    <hr />
24 
+    <a id="installing"></a>
25 
+    <h2><a class="anchor" href="#installing">Étape une : Télécharger et installer
26 
+    Tor</a></h2>
27 
+    <br />
28 
+
29 
+    <p>
30 
+    The install for Macintosh OS X bundles <a href="<page index>">Tor</a>, <a
31 
+    href="<page projects/vidalia>">Vidalia</a> (a graphical interface for Tor), <a
32 
+    href="<page projects/torbutton>">Torbutton</a>, and <a
33 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (a web
34 
+    proxy)  into one package, with the four applications pre-configured to work
35 
+    together.  Download either the <a
36 
+    href="../<package-osx-bundle-stable>">stable</a> or the <a
37 
+    href="../<package-osx-bundle-alpha>">experimental</a> version of the OS X
38 
+    bundle for Intel, or look for more options on the <a href="<page
39 
+    download/download>">download page</a>.
40 
+    </p>
41 
+
42 
+    <p>Une fois que vous avez téléchargé le fichier dmg, double-cliquez dessus pour
43 
+    le monter.  Naviguez sur le Pack Vidalia qui est maintenant ouvert dans
44 
+    Finder.  L'installation de ce pack est facile: glissez-déposez l'icône en
45 
+    oignon de Vidalia dans le répertoire Applications.  Optionnellement,
46 
+    double-cliquez sur le script "install torbutton" et laissez torbutton
47 
+    s'installer dans Firefox.  Vous pouvez également récupérer Torbutton depuis
48 
+    le site des extensions Mozilla en recherchant "torbutton".</p>
49 
+
50 
+    <p>Une fois l'installation terminée, vous pouvez lancer Vidalia en
51 
+    sélectionnant son icône depuis le répertoire "Applications". Un oignon noir
52 
+    avec une croix rouge signifie que Tor n'est pas actif. Vous pouvez le
53 
+    démarrer en sélectionnant "Start" dans le menu « Tor » en haut de votre
54 
+    écran.
55 
+    </p>
56 
+
57 
+    <p>Lorsque Tor est lancé, l'icône Vidalia ressemble à ce qui suit :
58 
+    </p>
59 
+
60 
+    <p><img alt="vidalia running tor"
61 
+    src="../img/screenshot-osx-vidalia.png"
62 
+    border="1"/></p>
63 
+
64 
+    <p>Polipo est installé avec le reste du paquet Tor. Une fois qu'il est
65 
+    installé, il sera démarré automatiquement au prochain redémarrage de votre
66 
+    machine.  Il n'est pas nécessaire de configurer Polipo pour utiliser Tor
67 
+    &mdash; une version adaptée pour Tor de Polipo a été installée avec le reste
68 
+    du paquet.
69 
+    </p>
70 
+
71 
+    <hr />
72 
+    <a id="using"></a>
73 
+    <h2><a class="anchor" href="#using">Étape deux : Configurer vos applications
74 
+    pour utiliser Tor</a></h2>
75 
+    <br />
76 
+
77 
+    <p>Après l'installation, vous aurez besoin de configurer vos applications pour
78 
+    les utiliser. La première étape est de configurer le navigateur web.</p>
79 
+
80 
+    <p>Vous devriez utiliser Tor avec Firefox et Torbutton, pour une meilleur
81 
+    sécurité.  Torbutton a été installé pour vous.  Cliquez sur le bouton rouge
82 
+    "Tor Disabled" pour l'activer, et vous êtes prêt :  </p>
83 
+
84 
+    <p><img alt="Torbutton plugin for Firefox"
85 
+    src="../img/screenshot-torbutton.png"
86 
+    border="1"/></p>
87 
+
88 
+    <p>
89 
+    Si vous envisagez de faire tourner Firefox sur un ordinateur différent de
90 
+    celui qui fait tourner Tor, jetez un œil à <a
91 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">l'entrée
92 
+    FAQ traitant de l'utilisation de Tor sur un ordinateur différent</a>.
93 
+    </p>
94 
+
95 
+    <p>Pour torréfier d'autres applications qui savent utiliser des proxys HTTP, il
96 
+    suffit de leur indiquer de passer par Polipo (c'est à dire "localhost" sur
97 
+    le port "8118"). Pour celles qui utilisent SOCKS directement (messagerie
98 
+    instantanée, Jabber, IRC, etc), vous pouvez les faire passer directement par
99 
+    Tor ("localhost", port "9050"), mais consultez d'abord <a
100 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">cette
101 
+    entrée de la FAQ</a> qui vous indiquera quels sont les risques que cela
102 
+    comporte. Pour les applications qui n'utilisent ni SOCKS ni HTTP, jetez un
103 
+    oeil à <a href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a>
104 
+    ou <a href="http://www.dest-unreach.org/socat/">socat</a>.</p>
105 
+
106 
+    <p>Pour davantage d'information sur comment torréfier d'autres applications,
107 
+    consultez <a
108 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">le
109 
+    HOWTO Torréfaction</a>.
110 
+    </p>
111 
+
112 
+    <hr />
113 
+    <a id="verify"></a>
114 
+    <h2><a class="anchor" href="#verify">Étape trois : s'assurer que ça
115 
+    fonctionne</a></h2>
116 
+    <br />
117 
+
118 
+    <p>
119 
+    Ensuite, vous devriez essayer d'utiliser votre navigateur avec Tor et vous
120 
+    assurer que votre adresse IP est bien anonymisée. Cliquez sur <a
121 
+    href="https://check.torproject.org/">le détecteur Tor</a> et voyez s'il
122 
+    pense que vous passez par Tor ou non. (si ce site est inaccessible,
123 
+    consultez <a
124 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">cette
125 
+    entrée de la FAQ</a> pour davantage de suggestions sur le sujet des tests de
126 
+    votre noeud Tor.)
127 
+    </p>
128 
+
129 
+    <p>Si vous avez un pare-feu personnel qui limite la capacité de votre
130 
+    ordinateur à se connecter à lui même, assurez vous de permettre les
131 
+    connexions à vos applications locales aux ports 8118 et 9050. Si votre
132 
+    pare-feu bloque les connexions sortantes, faites un trou pour qu'il puisse
133 
+    au moins se connecter sur les ports 80 et 443, et lisez <a
134 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">cette
135 
+    entrée de la FAQ</a>.
136 
+    </p>
137 
+
138 
+    <p>Si ça ne marche toujours pas, consultez <a
139 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">cette
140 
+    entrée de la FAQ</a> pour quelques astuces.</p>
141 
+
142 
+    <p>
143 
+    Une fois que tout fonctionne, vous pouvez apprendre en davantage sur <a
144 
+    href="<page download/download>#Warning">ce que Tor peut et ne peut pas offrir</a>.
145 
+    </p>
146 
+
147 
+    <hr />
148 
+    <a id="server"></a> <a id="relay"></a>
149 
+    <h2><a class="anchor" href="#relay">Étape quatre : configurer Tor comme
150 
+    relais</a></h2>
151 
+    <br />
152 
+
153 
+    <p>Le réseau Tor repose sur des contributeurs qui fournissent de la bande
154 
+    passante. Plus il y a de gens qui font tourner un noeuds, plus le réseau
155 
+    sera rapide. Si vous avez au moins 20 kilo octets/s dans chaque sens, aidez
156 
+    Tor en configurant votre logiciel en tant que noeud. Nous avons plusieurs
157 
+    options qui rendent Tor facile et agréable, par exemple la limitation de
158 
+    bande passante consommée, les contrôles sur ports de sortie pour que vous
159 
+    puissiez limiter votre exposition aux utilisations abusives, et le support
160 
+    des adresses dynamiques.</p>
161 
+
162 
+    <p>Avoir des relais dans plein de lieux différents sur Internet c'est ce qui
163 
+    sécurise les utilisateurs. Cela peut également <a
164 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">vous
165 
+    apporter d'avantage d'anonymat</a>, puisque les sites distants ne peuvent
166 
+    pas savoir si une connexion vient de votre ordinateur ou si elle est relayée
167 
+    d'un autre.</p>
168 
+
169 
+    <p>Lisez d'avantage sur le guide <a href="<page docs/tor-doc-relay>">Configurer
170 
+    un noeud</a> </p>
171 
+
172 
+    <hr />
173 
+    <a id="uninstall"></a>
174 
+    <h2><a class="anchor" href="#uninstall">Comment désinstaller Tor et Privoxy</a></h2>
175 
+    <br />
176 
+
177 
+    <p>Il existe deux moyens de désinstaller le pack de votre ordinateur: en
178 
+    utilisant Finder ou bien en utilisant la ligne de commande ou un
179 
+    désinstalleur en mode Terminal.  Voici comment procéder pour supprimer Tor
180 
+    sur OSX:</p>
181 
+
182 
+    <p>Mettez les paramètres d'origine sur votre proxy.  Si vous souhaitez
183 
+    simplement ne plus passer par Tor, vous pouvez vous arrêter là.</p>
184 
+
185 
+    <p>Si vous désirez complètement supprimer Tor , et que votre compte dispose des
186 
+    privilèges d'administrateur, procédez comme suit :</p>
187 
+
188 
+    <ol>
189 
+    <li>Ouvrez Finder et cliquez sur Applications.</li>
190 
+    <li>Glissez /Applications/Vidalia dans la Corbeille.</li>
191 
+    <li>Supprimez /Library/Torbutton de votre système.</li>
192 
+    <li>Dans votre répertoire home, allez dans Library, supprimez le répertoire
193 
+    Vidalia</li>
194 
+    </ol>
195 
+
196 
+    <p>Tor, Vidalia, and Polipo sont maintenant complètement supprimés de votre
197 
+    système.</p>
198 
+
199 
+    <p>Si vous êtes familier de la ligne de commande ou du Terminal, vous pouvez
200 
+    supprimer manuellement ce qui suit:</p>
201 
+    <ul>
202 
+    <li>/Applications/Vidalia.app/</li>
203 
+    <li>/Library/Torbutton/</li>
204 
+    <li>~/Library/Vidalia</li>
205 
+    <li>~/.tor</li>
206 
+    </ul>
207 
+
208 
+    <hr />
209 
+
210 
+    <p>Si vous avez des suggestions pour étoffer ce document, n'hésitez pas <a
211 
+    href="<page about/contact>">à nous les faire parvenir</a>. Merci !</p>
212 
+  </div>
213 
+  <!-- END MAINCOL -->
214 
+  <div id = "sidecol">
215 
+#include "side.wmi"
216 
+#include "info.wmi"
217 
+  </div>
218 
+  <!-- END SIDECOL -->
219 
+</div>
220 
+<!-- END CONTENT -->
221 
+#include <foot.wmi>
docs/fr/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,328 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurer un relais Tor</h1>
14 
+
15 
+
16 
+    <!-- BEGIN SIDEBAR -->
17 
+    <div class="sidebar-left">
18 
+    <h3>Étapes de configuration</h3>
19 
+    <ol>
20 
+    <li><a href="<page docs/tor-doc-relay>#install">Télécharger &amp; Installer</a></li>
21 
+    <li><a href="<page docs/tor-doc-relay>#setup">Configuration</a></li>
22 
+    <li><a href="<page docs/tor-doc-relay>#check">Vérifier &amp; Confirmer</a></li>
23 
+    <li><a href="<page docs/tor-doc-relay>#after">Étapes terminales</a></li>
24 
+    </ol>
25 
+    </div>
26 
+
27 
+
28 
+    <!-- END SIDEBAR -->
29 
+    <hr />
30 
+
31 
+    <p>
32 
+    Le réseau Tor repose sur des contributeurs qui fournissent de la bande
33 
+    passante. Plus il y aura de personnes que feront tourner un relais, plus le
34 
+    réseau sera rapide. Si vous avez au moins 20 kilo-octets/s dans chaque sens,
35 
+    aidez Tor en configurant votre logiciel comme relais. Nous avons plusieurs
36 
+    options qui rendent les relais de Tor facile et agréable à mettre en place,
37 
+    par exemple <a href="<page docs/faq>#RelayFlexible">la limitation de bande
38 
+    passante consommée, le contrôle sur ports de sortie pour que vous puissiez
39 
+    limiter votre exposition aux plaintes, et le support des adresses IP
40 
+    dynamiques</a>.
41 
+    </p>
42 
+
43 
+    <p>Vous pouvez faire tourner un relais Tor sur pratiquement <a
44 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">n'importe
45 
+    quel système d'exploitation</a>. Les relais Tor fonctionnent mieux sur
46 
+    Linux, OS X à partir de Tiger, FreeBSD 5.x+, NetBSD 5.x+, et Windows Server
47 
+    2003 ou plus.
48 
+    </p>
49 
+
50 
+    <hr /> <a id="zero"></a> <a id="install"></a>
51 
+    <h2><a class="anchor" href="#install">Première étape: télécharger et installer
52 
+    Tor</a></h2>
53 
+    <br />
54 
+
55 
+    <p>Avant de commencer, vous devez vous assurer que Tor fonctionne
56 
+    correctement.
57 
+    </p>
58 
+
59 
+    <p>Visitez notre <a href="<download/page easy-download>">page de téléchargement</a> et
60 
+    installez le paquet complet pour votre système d'exploitation.
61 
+    </p>
62 
+
63 
+    <p>Si vous pensez que c'est utile, vous pouvez également utiliser Tor comme un
64 
+    client pour être sûr qu'il fonctionne.</p>
65 
+
66 
+    <hr /> <a id="setup"></a>
67 
+    <h2><a class="anchor" href="#setup">Deuxième étape: le paramétrer comme
68 
+    relais</a></h2>
69 
+    <br />
70 
+    <ol>
71 
+    <li>Vérifiez que votre horloge est à l'heure. Si possible, synchronisez là sur
72 
+    un <a href="http://en.wikipedia.org/wiki/Network_Time_Protocol">serveur de
73 
+    temps</a> public.
74 
+    </li>
75 
+
76 
+    <li><strong>Configurer Tor à l'aide de l'interface graphique de
77 
+    Vidalia</strong>:
78 
+    <ol>
79 
+
80 
+    <li>
81 
+    	<dt>Faîtes un clic droit sur l'icône de Vidalia dans votre barre de tâches.
82 
+    Choisissez <tt>Panneau de Contrôle</tt>.</dt>
83 
+    	<dd><img alt="Menu bouton droit de Vidalia"
84 
+    src="../img/screenshot-win32-vidalia.png"></dd>
85 
+    </li>
86 
+
87 
+    <li>Cliquez sur <tt>Configuration du Relais</tt>.</li>
88 
+
89 
+    <li>
90 
+    	<dt>Choisir <tt>Relayer le trafic pour le réseau Tor</tt> si vous voulez devenir
91 
+    un relais public (recommandé), ou choisissez 		<tt>Aidez les utilisateurs
92 
+    censurés à se connecter au réseau Tor</tt> si vous désirez devenir une <a
93 
+    href="<page docs/faq>#RelayOrBridge">passerelle</a> pour les utilisateurs situés
94 
+    dans des pays qui censurent Internet.</dt>
95 
+    <dd><img alt="Paramètres de base de Vidalia"
96 
+    src="../img/screenshot-win32-configure-relay-1.png"></dd>
97 
+    </li>
98 
+
99 
+    <li>Entrer un surnom pour votre relais, et vos informations de contact au cas où
100 
+    nous aurions besoin de vous faire remonter des problèmes.</li>
101 
+
102 
+    <li>Choisissez <tt>Tenter de configurer automatiquement la translation de
103 
+    port</tt>.  Appuyez sur le bouton <tt>Test</tt> pour voir si ça fonctionne.
104 
+    Si ça marche, super. Sinon, voyez le point 3 ci-dessous.</li>
105 
+
106 
+    <li><dt>Choisisser le panneau <tt>Limitation de bande passante</tt>.  Sélectionnez
107 
+    combien de bande passante vous souhaitez fournir aux utilisateurs comme à
108 
+    vous même.</dt>
109 
+    <dd><img alt="Limites de bande passante sous vidalia"
110 
+    src="../img/screenshot-win32-configure-relay-2.png"></dd>
111 
+    </li>
112 
+
113 
+    <li><dt>Choisissez le panneau <tt>Politique de sortie</tt>.  Si vous souhaitez
114 
+    autoriser d'autres personnes à utiliser votre relais pour ces services, ne
115 
+    changez rien.  Décochez les services que vous ne souhaitez pas <a
116 
+    href="<page docs/faq>#ExitPolicies">autoriser à travers votre relais</a>.  Si
117 
+    vous ne souhaitez pas être un relais de sortie décochez tous les services.</dt>
118 
+    <dd><img alt="Politiques de sortie de Vidalia"
119 
+    src="../img/screenshot-win32-configure-relay-3.png"></dd>
120 
+    </li>
121 
+
122 
+    <li>Cliquez sur le bouton <tt>Valider</tt>.  Consultez la troisième étape pour
123 
+    confirmer que votre relais fonctionne correctement.</li>
124 
+    </ol>
125 
+
126 
+    <br /> <strong>Configuration Manuelle</strong>:
127 
+    <ul>
128 
+    <li>Éditez la partie basse de votre <a
129 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">fichier
130 
+    torrc</a>. Si vous désirez être un relais public (recommandé), assurez vous
131 
+    de définir au moins la variable ORPort et jeter un oeil à <a href="<page
132 
+    docs/faq>#ExitPolicies">ExitPolicy</a>. Si vous désirez être <a href="<page
133 
+    faq>#RelayOrBridge">une passerelle</a> pour les utilisateurs situés dans des
134 
+    pays qui censurent Internet, utilisez <a href="<page
135 
+    docs/bridges>#RunningABridge">ces quelques lignes</a>.
136 
+    </li>
137 
+
138 
+    </ul></li>
139 
+
140 
+    <li>Si vous utilisez un pare-feu, ouvrez y un trou de manière à ce que les
141 
+    connexions entrantes puissent atteindre le port que vous avez configuré
142 
+    (ORPort, et DirPort si vous l'avez activé). Si vous avez un pare-feu
143 
+    matériel (un boitier Linksys, un modem câble, etc...) vous aurez besoin de
144 
+    <a href="http://portforward.com/">portforward.com</a>. Assurez vous qu'il
145 
+    autorise toutes les connexions <em>sortantes</em> pour que votre relais
146 
+    puisse atteindre les autres relais Tor.
147 
+    </li>
148 
+
149 
+    <li>Relancer votre relais. S'il <a
150 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">trace
151 
+    n'importe quel dysfonctionnement</a>, faites nous en part.
152 
+    </li>
153 
+
154 
+    <li>Inscrivez vous à la liste de diffusion <a
155 
+    href="http://archives.seul.org/or/announce/">or-announce</a>. Il y a
156 
+    relativement peu de messages, et elle vous tiendra informé des nouvelles
157 
+    versions stables. Vous devriez aussi envisager de vous inscrire aux <a
158 
+    href="<page docs/documentation>#MailingLists">listes de diffusions de Tor</a>
159 
+    avec un trafic plus important.
160 
+    </li>
161 
+
162 
+    </ol>
163 
+
164 
+    <hr /> <a id="check"></a>
165 
+    <h2><a class="anchor" href="#check">Troisième étape s'assurer que ça
166 
+    fonctionne</a></h2>
167 
+    <br />
168 
+
169 
+    <p>Dès que votre relais va tenter de se connecter au réseau, il va essayer de
170 
+    déterminer si le port que vous avez configuré est joignable de
171 
+    l'extérieur. Ceci peut prendre jusqu'à 20 minutes. Jetez un œil sur les <a
172 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">entrées
173 
+    de logs</a> du genre <tt>Self-testing indicates your ORPort is reachable
174 
+    from the outside. Excellent</tt>. Si vous ne voyez pas ce message, ça
175 
+    signifie que votre relais n'est pas joignable de l'extérieur &mdash; vous
176 
+    devriez revérifier vos pare-feux, vérifier qu'il teste l'adresse IP et le
177 
+    port que vous pensez qu'il devrait tester, etc.
178 
+    </p>
179 
+
180 
+    <p>Lorsque votre relais a décidé qu'il était joignable, il envoie un
181 
+    "descripteur de serveur" aux annuaires. Ceci permettra aux clients de
182 
+    connaître l' adresse, les ports, les clés, etc que votre relais
183 
+    utilise. Vous pouvez manuellement <a
184 
+    href="http://194.109.206.212/tor/status/authority">télécharger l'un des
185 
+    états du réseau</a> et voir si vous y trouvez le nom que vous avez
186 
+    configuré, pour être certain de sa présence. Vous aurez probablement à
187 
+    attendre quelques secondes pour avoir un rafraîchissement du répertoire.</p>
188 
+
189 
+    <hr /> <a id="after"></a>
190 
+    <h2><a class="anchor" href="#after">Quatrième étape: une fois que ça
191 
+    fonctionne</a></h2>
192 
+    <br />
193 
+
194 
+    <p>
195 
+    Nous recommandons de suivre les étapes suivantes :
196 
+    </p>
197 
+
198 
+    <p>
199 
+    6. Lisez <a
200 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">ce
201 
+    document</a> pour avoir des idées sur comment accroître la sécurité de votre
202 
+    relais.
203 
+    </p>
204 
+
205 
+    <p>
206 
+    7. Si vous désirez faire tourner plus d'un seul relais, c'est bien mais
207 
+    merci de configurer <a
208 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">l'option
209 
+    MyFamily</a> dans tous les fichiers de configuration de tous vos relais.
210 
+    </p>
211 
+
212 
+    <p>
213 
+    8. Décidez de la limitation de débit. Le câble, le xDSL, et les utilisateurs
214 
+    qui ont une bande passante asymétrique (par exemple : plus de débit en
215 
+    téléchargement qu'en envoi) doivent limiter leur débit à la plus petite
216 
+    bande passante pour éviter les congestions. Voyez <a
217 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">l'entrée
218 
+    FAQ sur la limitation du débit</a> pour plus de détails.
219 
+    </p>
220 
+
221 
+    <p>
222 
+    9. Sauvegardez la clé privée de votre relais Tor (stockée dans
223 
+    "keys/secret_id_key" de votre DataDirectory). C'est l'« identité » de votre
224 
+    relais, et prenez soin de la garder en sécurité pour que personne ne puisse
225 
+    lire le trafic qui passe au travers de votre nœud. C'est un fichier critique
226 
+    à conserver si vous comptez <a
227 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeRelay">déplacer
228 
+    ou restorer votre relais Tor</a> si quelque chose se passe mal.
229 
+    </p>
230 
+
231 
+    <p>
232 
+
233 
+    10. Si vous contrôlez le serveur de nom de votre domaine, n'hésitez pas à
234 
+    paramétrer votre nom d'hôte inversé avec 'anonymous' or 'proxy' or
235 
+    'tor-proxy', pour que les autres personnes voyant l'adresse dans les traces
236 
+    web puissent facilement comprendre ce qui se passe. Ajoutez une <a
237 
+    href="<gitblob>contrib/tor-exit-notice.html">Note de Sortie Tor</a> sur un
238 
+    hôte virtuel du même nom peut simplement décourager l'envoi de plaintes à
239 
+    vous et votre fournisseur d'accès Internet si vous utilisez un noeud de
240 
+    sortie.
241 
+
242 
+    </p>
243 
+
244 
+    <p>
245 
+    11. Si votre ordinateur ne fait pas tourner de serveur web, envisagez de
246 
+    changer l'option ORPort à 443 et votre DirPort à 80. Un certain nombre
247 
+    d'utilisateurs Tor sont cloisonnés derrière des pare-feux qui ne leur
248 
+    permettent que d'aller sur le web, et ce changement leur permettra
249 
+    d'atteindre votre relais Tor. Les relais Windows peuvent simplement changer
250 
+    leurs options ORPort et DirPort directement dans leur configuration torrc et
251 
+    relancer Tor. Les relais OS X ou Unix ne peuvent pas attacher directement
252 
+    ces ports (puisqu'ils doivent être lancé en root), alors ils doivent
253 
+    paramétrer une sorte de <a
254 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">translation
255 
+    de port</a> pour que les connexions puissent atteindre leur relais Tor. Si
256 
+    vos ports 80 et 443 sont déjà utilisés mais que vous souhaitez quand même
257 
+    aider, d'autres sont intéressants comme les ports 22, 110, et 143.
258 
+    </p>
259 
+
260 
+    <p>
261 
+    12. Si votre relais Tor fournit d'autres services sur la même adresse IP
262 
+    &mdash; comme par exemple un site web &mdash; assurez vous que les
263 
+    connexions au serveur web sont autorisées à partir de l'hôte local
264 
+    également. Cette autorisation est indispensable car les clients Tor
265 
+    détecteront que le relais Tor est <a
266 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">le
267 
+    chemin le plus sûr pour atteindre ce serveur web</a>, et construiront
268 
+    toujours un chemin qui finira par votre relais. Si vous ne souhaitez pas
269 
+    autoriser les connexions, vous devrez explicitement les rejeter dans votre
270 
+    politique de sortie.
271 
+    </p>
272 
+
273 
+    <p>
274 
+    13. (Uniquement pour Unix). Créez un utilisateur séparé pour faire tourner
275 
+    le relais. Si vous installez le paquet OS X ou deb ou rpm, ceci est déjà
276 
+    fait. Sinon, vous devez le faire à la main. (Le relais Tor ne nécessite pas
277 
+    d'être lancé sous root, c'est une bonne pratique de ne pas le faire. Le
278 
+    lancer sous l'utilisateur 'tor' évite les problèmes avec identd et d'autres
279 
+    services qui détectent le nom d'utilisateur. Si vous êtes dans le genre
280 
+    paranoïaque, rien ne vous empêche <a
281 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">de
282 
+    mettre Tor dans une prison chroot</a>.)
283 
+    </p>
284 
+
285 
+    <p>
286 
+    14. (Uniquement pour Unix). Votre système d'exploitation limite probablement
287 
+    le nombre de fichiers ouverts par processus à 1024 (voir moins). Si vous
288 
+    envisagez de faire tourner un nœud de sortie rapide, ceci ne sera sans doute
289 
+    pas suffisant. Sous Linux, vous devriez ajouter une ligne genre "toruser
290 
+    hard nofile 8192" à votre fichier /etc/security/limits.conf (ou toruser est
291 
+    l'utilisateur qui fait tourner le processus Tor), et ensuite relancer Tor
292 
+    s'il est installé comme paquet (ou déconnectez vous puis reconnectez vous si
293 
+    vous le lancez par vous même).
294 
+    </p>
295 
+
296 
+    <p>
297 
+    15. Si vous avez installé Tor à partir d'un paquet ou d'une installation
298 
+    automatisée, il est probable que Tor se le lance automatiquement au
299 
+    démarrage du système. Mais si vous l'avez installé par les sources, vous
300 
+    trouverez utiles les scripts de démarrage présents dans contrib/tor.sh ou
301 
+    contrib/torctl.
302 
+    </p>
303 
+
304 
+    <p>
305 
+    Lorsque vous changez la configuration de Tor, assurez-vous qu'il fonctionne
306 
+    encore après les modifications. Assurez-vous de bien positionner votre ligne
307 
+    « ContactInfo » dans le fichier torrc pour que nous puissions vous contacter
308 
+    en cas de mise à jour ou si quelque chose se passait mal. Si vous avez des
309 
+    problèmes ou des questions, voyez la <a href="<page
310 
+    docs/documentation>#Support">section d'aide</a> ou <a href="<page
311 
+    about/contact>">contactez-nous</a> sur la liste tor-ops. Merci de nous aider à
312 
+    faire croître le réseau Tor !
313 
+    </p>
314 
+
315 
+    <hr />
316 
+
317 
+    <p>Si vous avez des suggestions pour améliorer le contenu de ce document, merci
318 
+    <a href="<page about/contact>">de nous les faire parvenir</a>. Merci !</p>
319 
+  </div>
320 
+  <!-- END MAINCOL -->
321 
+  <div id = "sidecol">
322 
+#include "side.wmi"
323 
+#include "info.wmi"
324 
+  </div>
325 
+  <!-- END SIDECOL -->
326 
+</div>
327 
+<!-- END CONTENT -->
328 
+#include <foot.wmi>
docs/fr/tor-doc-server.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,8 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 12076
3 
+# Last-Translator: fredzupy@gmail.com
4 
+
5 
+#include "head.wmi" CHARSET="UTF-8" TITLE="Redirecting" REDIRECT="docs/tor-doc-relay"
6 
+
7 
+#include <foot.wmi>
8 
+
docs/fr/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,192 @@
1 
+    <h1>Installer un client <a href="<page index>">Tor</a> sur système
2 
+    Linux/BSD/Unix</h1>
3 
+    <br />
4 
+
5 
+    <p>
6 
+    <b>Ces instructions ne s'appliquent qu'à l'installation d'un client Tor. Si
7 
+    vous voulez aider à la croissance du réseau Tor en relayant du trafic pour
8 
+    les autres (ce qui est une très bonne idée), lisez <a href="<page
9 
+    docs/tor-doc-relay>">le guide sur la configuration d'un noeud</a>.</b>
10 
+    </p>
11 
+
12 
+    <hr /> <a id="installing"></a>
13 
+    <h2><a class="anchor" href="#installing">Étape 1 : Télécharger et Installer
14 
+    Tor</a></h2>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    Vous pouvez trouver la dernière version de Tor sur la page de <a href="<page
19 
+    download/download>">téléchargement</a>. Des paquets pour Debian, Red Hat,
20 
+    Gentoo, *BSD, etc... y sont également présents. Si vous utilisez Ubuntu,
21 
+    n'utilisez pas les paquets officiels de l'archive Ubuntu: utilisez <a
22 
+    href="<page docs/debian>#ubuntu">notre répertoire deb</a> à la place.
23 
+    </p>
24 
+
25 
+    <p>Si vous compilez Tor à partir du code source, installez d'abord <a
26 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a>, et assurez-vous
27 
+    de disposer d'openssl et de zlib (avec les paquets -devel si
28 
+    possible). Tapez ensuite :<br /> <tt>tar xzf tor-<version-stable>.tar.gz; cd
29 
+    tor-<version-stable><br /> ./configure &amp;&amp; make</tt><br /> Vous
30 
+    pouvez maintenant lancer tor depuis <tt>src/or/tor</tt>, ou bien vous pouvez
31 
+    l'installer dans /usr/local/ avec <tt>make install</tt> (en root si
32 
+    nécessaire), ce qui vous permettra de le lancer en tapant simplement
33 
+    <tt>tor</tt>.
34 
+    </p>
35 
+
36 
+    <p>Tor est préconfiguré par défaut en tant que client. Le fichier de
37 
+    configuration qu'il utilise par défaut conviendra à la plupart des
38 
+    utilisateurs. Tor est maintenant installé.
39 
+    </p>
40 
+
41 
+    <hr /> <a id="privoxy"></a> <a id="polipo"></a>
42 
+    <h2><a class="anchor" href="#polipo">Étape 2 : Installer Polipo pour la
43 
+    navigation web</a></h2>
44 
+    <br />
45 
+
46 
+    <p>Une fois Tor installé, vous devez configurer vos applications pour
47 
+    l'utiliser.
48 
+    </p>
49 
+
50 
+    <p>
51 
+    Il faut tout d'abord s'occuper de la navigation web. Commencez par installer
52 
+    <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> depuis
53 
+    votre dépôt préféré. Polipo est un proxy cache web filtrant qui gère
54 
+    correctement les files http; il est bien adapté à la latence de
55 
+    Tor. Assurez-vous de disposer d'au moins la version 1.0.4 de Polipo car les
56 
+    versions antérieures ne gère pas le protocole SOCKS indispensable pour que
57 
+    Polipo puisse fonctionner avec Tor. Vous devriez dès maintenant désinstaller
58 
+    privoxy (e.g. apt-get remove privoxy ou yum remove privoxy) de manière à ce
59 
+    qu'ils n'y ait pas de conflit entre les deux.
60 
+    </p>
61 
+
62 
+    <p>Une fois  Polipo installé (par un paquet, ou par les sources), <b>il vous
63 
+    faudra configurer  Polipo pour utiliser Tor</b>. Récupérez notre <a
64 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/polipo.conf">configuration
65 
+    de Polipo pour Tor</a> et copiez la dans votre fichier de configuration de
66 
+    polipo (ex: /etc/polipo/config ou ~/.polipo).  Vous aurez besoin de
67 
+    redémarrer Polipo pour les changements prennent effet. Par exemple:<br />
68 
+    <tt>/etc/init.d/polipo restart</tt>
69 
+    </p>
70 
+
71 
+    <p>Si vous le préférez, vous pouvez utiliser Privoxy à la place avec <a
72 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">cet
73 
+    exemple de fichier de configuration</a>. Mais étant donné que les fichiers
74 
+    de configuration de Polipo et de Privoxy font appel au port 8118, vous ne
75 
+    devriez pas les faire tourner tous les deux en même temps.</p>
76 
+
77 
+    <hr /> <a id="using"></a>
78 
+    <h2><a class="anchor" href="#using">Étape 3 : Configurer vos applications pour
79 
+    utiliser Tor</a></h2>
80 
+    <br />
81 
+
82 
+    <p>Une fois Tor installé, vous devez configurer vos applications pour
83 
+    l'utiliser.</p>
84 
+
85 
+    <p>Vous devriez utiliser Tor avec Firefox et Torbutton pour plus de sécurité.
86 
+    Installez tout simplement <a
87 
+    href="https://addons.mozilla.org/firefox/2275/">l'extension Torbutton</a>,
88 
+    redémarrer Firefox et c'est terminé :
89 
+    </p>
90 
+
91 
+    <img alt="Torbutton plugin for Firefox"
92 
+    src="../img/screenshot-torbutton.png" border="1"> <br />
93 
+
94 
+    <p>
95 
+    Si vous envisagez d'utiliser Firefox sur un ordinateur différent de Tor,
96 
+    jetez un œil à <a
97 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">l'entrée
98 
+    FAQ traitant de l'utilisation de Tor sur un ordinateur différent</a>.
99 
+    </p>
100 
+
101 
+    <p>Pour Torréfier d'autres applications qui gèrent les proxies HTTP, faites les
102 
+    simplement utiliser Polipo (c'est à dire, localhost port 8118). Pour
103 
+    utiliser SOCKS directement (pour la messagerie instantanée, Jabber, IRC,
104 
+    etc), faites pointer votre application directement sur Tor (localhost port
105 
+    9050), mais consultez <a
106 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">cet
107 
+    article de la FAQ</a> pour comprendre en quoi cela peut être dangereux. Pour
108 
+    les applications qui ne gèrent ni SOCKS, ni le HTTP, vous pouvez utiliser <a
109 
+    href="http://tsocks.sourceforge.net/">tsocks</a> ou <a
110 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
111 
+    </p>
112 
+
113 
+    <p>Vous pouvez trouver des informations sur la Torréfaction d'autres
114 
+    applications sur <a
115 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">le
116 
+    HOWTO Torréfaction</a.
117 
+    </p>
118 
+
119 
+    <hr /> <a id="verify"></a>
120 
+    <h2><a class="anchor" href="#verify">Étape 4 : Vérifier que ça fonctionne</a></h2>
121 
+    <br />
122 
+
123 
+    <p>
124 
+    <!--PO4ASHARPBEGIN<a href="http://ipchicken.com/">
125 
+    this site</a>PO4ASHARPEND-->
126 
+    #to see what IP address it thinks you're using.
127 
+    Vous devriez ensuite essayer d'utiliser votre navigateur avec Tor, et
128 
+    vérifier que votre adresse IP est anonyme. Rendez vous sur <a
129 
+    href="https://check.torproject.org/">le détecteur Tor</a>, vous verrez s'il
130 
+    pense que vous utilisez Tor ou non.  (Si ce site ne marche pas, voyez <a
131 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">cet
132 
+    article de la FAQ</a> pour des suggestions supplémentaires sur la manière de
133 
+    tester Tor.)
134 
+    </p>
135 
+
136 
+    <p>Si vous avez un pare-feu personnel qui limite la possibilité de votre
137 
+    ordinateur à se connecter en local (par exemple SELinux sur Fedora Core 4),
138 
+    assurez vous de permettre les connexions de vos applications vers Polipo
139 
+    (local port 8118) et Tor (local port 9050). Si votre pare-feu bloque les
140 
+    connexions sortantes, faites une brèche dedans pour pouvoir vous connecter
141 
+    au moins sur les ports 80 et 443, et consultez ensuite <a
142 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">cet
143 
+    article de la FAQ</a>.  Si votre configuration de SELinux ne permet pas à
144 
+    tor ou privoxy de fonctionner correctement, créez un fichier nommé
145 
+    booleans.local dans votre répertoire /etc/selinux/targeted.  Éditez le avec
146 
+    votre éditeur de texte favori, et écrivez "allow_ypbind=1".  Redémarrez
147 
+    votre machine pour que cette modification prenne effet.
148 
+    </p>
149 
+
150 
+    <p>Si cela ne fonctionne toujours pas, consultez <a
151 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">cet
152 
+    article de la FAQ</a>.</p>
153 
+
154 
+    <hr /> <a id="server"></a> <a id="relay"></a>
155 
+    <h2><a class="anchor" href="#relay">Étape 5 : Configurer Tor en tant que
156 
+    relais</a></h2>
157 
+    <br />
158 
+
159 
+    <p>Le réseau Tor se base sur des volontaires qui fournissent de la bande
160 
+    passante. Plus il y a de personnes qui font tourner de relais, plus le
161 
+    réseau Tor sera rapide. Si vous disposez d'au moins 20 Ko/s dans chaque sens
162 
+    (débit montant et descendant), vous pouvez aider Tor en configurant votre
163 
+    noeud Tor en tant que relais. Nous avons beaucoup de fonctionnalités qui
164 
+    rendent les relais Tor simples et pratiques, comme la gestion des adresses
165 
+    IP dynamiques, ou la limitation de la bande passante maximale et les
166 
+    politiques de sortie afin que vous puissiez limiter votre exposition aux
167 
+    possibles plaintes suite à une utilisation abusive de Tor.</p>
168 
+
169 
+    <p>Tor est un système dont la sécurité dépend de la diversité des lieux
170 
+    géographiques où tournent les relais. Faire tourner un relais <a
171 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">renforce
172 
+    votre anonymat</a>, car les sites distants ne peuvent pas savoir si les
173 
+    connexions proviennent de votre ordinateur, ou si vous les avez juste
174 
+    relayées depuis un autre endroit.</p>
175 
+
176 
+    <p>Pour en savoir plus, consultez le guide de <a href="<page
177 
+    docs/tor-doc-relay>">configuration d'un relais</a>.</p>
178 
+
179 
+    <hr />
180 
+
181 
+    <p>Si vous avez des suggestions pour améliorer ce document, merci de <a
182 
+    href="<page about/contact>">nous les envoyez</a>. Merci !</p>
183 
+  </div>
184 
+  <!-- END MAINCOL -->
185 
+  <div id = "sidecol">
186 
+#include "side.wmi"
187 
+#include "info.wmi"
188 
+  </div>
189 
+  <!-- END SIDECOL -->
190 
+</div>
191 
+<!-- END CONTENT -->
192 
+#include <foot.wmi>
docs/fr/tor-doc-web.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,61 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Configuring your browser to use Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-web>">Configure Your Browser</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurer votre navigateur pour l'utilisation de <a href="<page
14 
+    index>">Tor</a></h1>
15 
+    <br />
16 
+
17 
+    <p>Si vous utilisez Firefox (ce que nous recommandons), vous n'avez pas besoin
18 
+    de cette page.  Installez simplement le <a
19 
+    href="https://addons.mozilla.org/firefox/2275/">Plugiciel Torbutton</a>,
20 
+    relancez Firefox, et c'est tout :
21 
+    </p>
22 
+
23 
+    <img alt="Plugiciel Torbutton pour Firefox"
24 
+    src="../img/screenshot-torbutton.png" border="1"/> <br />
25 
+
26 
+    <p>Sinon, vous devez configurer manuellement les paramètres du mandataire de
27 
+    votre navigateur.  <br/>Dans Mozilla et Firefox sous Windows, ceci est dans
28 
+    Outils - Options - Général - Paramètres de connexion.  <br/>Dans Firefox
29 
+    sous OS X, c'est - Firefox - Préférences - Général - Paramètres de
30 
+    connexion.  <br/>Dans Firefox sous Linux, c'est dans Édition - Préférences -
31 
+    Avancées - Proxy.  <br/>Dans Opera c'est Fichier - Préférences - Réseau -
32 
+    Serveurs proxy.  <br/>Dans IE, c'est Outils - Options Internet - Connexions
33 
+    - Paramètres Réseau - cocher Serveur proxy - Avancé.</p>
34 
+
35 
+    <img alt="Paramètres Proxy dans Firefox"
36 
+    src="../img/screenshot-win32-firefox-proxies.jpg" />
37 
+
38 
+    <p>
39 
+    Vous devriez remplir "localhost" et "8118" sur les quatres protocoles du
40 
+    haut pour pointer sur Polipo, comme montré ici. (Même si Polipo ne supporte
41 
+    pas les protocoles FTP et Gopher, <a
42 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">vous
43 
+    devriez les mettre aussi tout de même</a>.) Vous devriez également remplir
44 
+    le mandataire socks Pour pointer direcrement sur Tor ("localhost", "9050",
45 
+    et socks5)  pour couvrir l'ensemble des protocoles au delà des quatres
46 
+    premiers. Puis cliquer sur "OK".</p>
47 
+
48 
+    <hr />
49 
+
50 
+    <p>Si vous avez des commentaires pour améliorer ce document, n'hésitez pas à <a
51 
+    href="<page about/contact>">nous écrire</a>. Merci !</p>
52 
+  </div>
53 
+  <!-- END MAINCOL -->
54 
+  <div id = "sidecol">
55 
+#include "side.wmi"
56 
+#include "info.wmi"
57 
+  </div>
58 
+  <!-- END SIDECOL -->
59 
+</div>
60 
+<!-- END CONTENT -->
61 
+#include <foot.wmi>
docs/fr/tor-doc-win32.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,9 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 13195
3 
+# Last-Translator: fredzupy@gmail.com
4 
+
5 
+#include "head.wmi" CHARSET="UTF-8" TITLE="Redirection"
6 
+REDIRECT="docs/tor-doc-windows"
7 
+
8 
+#include <foot.wmi>
9 
+
docs/fr/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,199 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Installer et utiliser le client <a href="<page index>">Tor</a> sous MS
14 
+    Windows</h1>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>Notez que ce sont les instructions d'installation pour utiliser le client
19 
+    Tor sous MS Windows (2000, XP, Vista, 7, et les éditions Serveur).  Si vous
20 
+    voulez installer un relais Tor pour faire grandir le réseau (n'hésitez pas
21 
+    !), lisez le guide <a href="<page docs/tor-doc-relay>">Configurer un
22 
+    serveur</a>.</b>
23 
+    </p>
24 
+
25 
+    <p>Freedom House a produit une vidéo qui montre comment installer Tor.  Vous
26 
+    pouvez la regarder sur <a
27 
+    href="http://media.torproject.org/video/2009-install-and-use-tor.ogv">How to
28 
+    install Tor on Windows</a>.  Vous connaissez une meilleure vidéo ou une
29 
+    traduite dans votre lague ? Dites-le nous !</p>
30 
+
31 
+    <div class="center">
32 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor.ogv" autobuffer="true" controls="controls"></video></p>
33 
+    </div>
34 
+
35 
+    <hr /> <a id="installing"></a>
36 
+    <h2><a class="anchor" href="#installing">Étape un : Télécharger et installer
37 
+    Tor</a></h2>
38 
+    <br />
39 
+
40 
+    <p>
41 
+    L'installateur pour MS Windows contient <a href="<page index>">Tor</a>, <a
42 
+    href="<page projects/vidalia>">Vidalia</a> (Une interface graphique pour Tor),
43 
+    <a href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> (une
44 
+    extension pour Mozilla Firefox), et <a
45 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (un proxy
46 
+    web filtrant) en un seul paquet, avec ces quatres applications
47 
+    pré-configurées pour fonctionner ensemble. Téléchargez soit la version <a
48 
+    href="../<package-win32-bundle-stable>">stable</a>, soit la version <a
49 
+    href="../<package-win32-bundle-alpha>">expérimentale</a> du paquet Windows,
50 
+    ou consultez les autres options sur <a href="<page download/download>">la  page de
51 
+    téléchargement</a>.
52 
+    </p>
53 
+
54 
+    <img alt="tor installer splash page"
55 
+    src="../img/screenshot-win32-installer-splash.png" />
56 
+
57 
+    <p>Si vous aviez précédemment installé Tor, Vidalia ou Polipo, vous pouvez
58 
+    désélectionner les composants dont vous n'avez pas besoin dans la fenêtre
59 
+    présentée ci-dessous.
60 
+    </p>
61 
+
62 
+    <img alt="select components to install"
63 
+    src="../img/screenshot-win32-installer-components.png" />
64 
+
65 
+    <p>Une fois que vous aurez terminé l'installation, les composants logiciels que
66 
+    vous aurez sélectionnés seront automatiquement démarrés pour vous.
67 
+    </p>
68 
+
69 
+    <p>Tor est configuré en client par défaut. Il utilise un fichier de
70 
+    configuration par défaut que la majorité des utilisateurs n'ont pas besoin
71 
+    de modifier. Tor est maintenant installé.
72 
+    </p>
73 
+
74 
+    <hr /> <a id="using"></a>
75 
+    <h2><a class="anchor" href="#using">Étape deux : Configurer vos applications
76 
+    pour qu'elles utilisent Tor</a></h2>
77 
+    <br />
78 
+
79 
+    <p>Après avoir installé Tor et Polipo, vous devez configurer vos applications
80 
+    pour les utiliser. La prochaine action consiste à configurer le navigateur
81 
+    web. </p>
82 
+
83 
+    <p>Vous devriez utiliser Tor avec Firefox et Torbutton, pour une meilleur
84 
+    assurance. Le Pack d'installation installe le <a
85 
+    href="https://addons.mozilla.org/firefox/2275/">l'extension Torbutton</a>
86 
+    pour vous. Redémarrez votre Firefox et c'est tout :
87 
+    </p>
88 
+
89 
+    <img alt="Torbutton plugin for Firefox"
90 
+    src="../img/screenshot-torbutton.png" border="1"/> <br />
91 
+
92 
+    <p>
93 
+    Si vous envisagez de faire tourner Firefox sur un ordinateur différent de
94 
+    celui de Tor, consultez <a
95 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">l'entrée
96 
+    de la FAQ sur comment faire tourner Tor sur un ordinateur différent</a>.
97 
+    </p>
98 
+
99 
+    <p>Pour "Torréfier" d'autres application qui savent utiliser des proxys HTTP,
100 
+    il suffit de leur indiquer de passer par Polipo (c'est à dire "localhost"
101 
+    sur le port "8118"). Pour celles qui utilisent SOCKS directement (messagerie
102 
+    instantanée, Jabber, IRC, etc.), vous pouvez les faire passer directement
103 
+    par Tor ("localhost", port "9050"), mais regardez d'abord <a
104 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">cette
105 
+    entrée de la FAQ</a> qui vous dira les risques que cela comporte. Pour les
106 
+    applications qui n'utilisent ni SOCKS ni HTTP, jetez un oeil à SocksCap ou à
107 
+    <a href="http://www.freecap.ru/eng/">FreeCap</a>. (FreeCap est un logiciel
108 
+    libre; SocksCap est propriétaire.)</p>
109 
+
110 
+    <p>Pour davantage d'informations sur "comment torréfier d'autres applications",
111 
+    regardez <a
112 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">le
113 
+    HOWTO Torréfaction</a>.
114 
+    </p>
115 
+
116 
+    <hr /> <a id="verify"></a>
117 
+    <h2><a class="anchor" href="#verify">Étape trois : S'assurer que ça
118 
+    fonctionne</a></h2>
119 
+    <br />
120 
+
121 
+    <p>
122 
+    Vérifiez que Vidalia est fonctionel.  Vidalia utilise un petit oignon vert
123 
+    pour indiquer que Tor fonctionne ou un oignon gris avec un "X" rouge lorsque
124 
+    Tor ne fonctionne pas. Vous pouvez démarrer ou arrêter Tor en effectuant un
125 
+    clic-droit sur l'icône de Vidalia dans votre barre des tâches et en
126 
+    sélectionnant "Démarrer" ou "Arrêter" depuis le menu présenté ci-dessous:
127 
+    </p>
128 
+
129 
+    <img alt="Vidalia Tray Icon" src="../img/screenshot-win32-vidalia.png"/>
130 
+
131 
+    <p>
132 
+    Ensuite, vous devriez essayer votre navigateur web avec Tor activé pour vous
133 
+    assurer que votre adresse IP est anonymisée. Cliquez sur le <a
134 
+    href="https://check.torproject.org/">Tor detector</a> et voyez si vous
135 
+    utilisez bien Tor ou non.  (Si le site n'est pas disponible, regardez cette
136 
+    <a
137 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">rubrique
138 
+    de la FAQ</a> pour trouver d'autres moyens de tester le fonctionnement de
139 
+    votre client Tor.)
140 
+    </p>
141 
+
142 
+    <p>Si vous avez un pare-feu personnel qui empêche votre ordinateur de se
143 
+    connecter à lui-même, assurez-vous d'autoriser les connexions depuis vos
144 
+    applications locales vers les ports local "8118" et "9050". Si votre
145 
+    pare-feu bloque les connexions sortantes, ouvrez-le un peu, au moins pour
146 
+    les ports "TCP 80" et "TCP 443", et ensuite regardez <a
147 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">cette
148 
+    rubrique de la FAQ</a>.
149 
+    </p>
150 
+
151 
+    <p>Si ça ne marche toujours pas, allez-voir <a
152 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">cette
153 
+    rubrique de la FAQ</a> pour trouver des conseils.</p>
154 
+
155 
+    <p>
156 
+    Une fois que cela fonctionne, apprenez en plus sur <a href="<page
157 
+    download/download>#Warning">ce que Tor propose et ne propose pas</a>.
158 
+    </p>
159 
+
160 
+    <hr /> <a id="server"></a> <a id="relay"></a>
161 
+    <h2><a class="anchor" href="#relay">Étape quatre : Configurez Tor en mode
162 
+    relais</a></h2>
163 
+    <br />
164 
+
165 
+    <p>Le réseau Tor repose sur les personnes volontaires pour donner de la bande
166 
+    passante. Plus il y aura de personnes qui hébergent des relais Tor, plus le
167 
+    réseau Tor sera rapide. Si vous avez au moins 20ko/s symétriques, aidez le
168 
+    réseau Tor en configurant votre Tor en mode relais également. Nous avons
169 
+    implanté de nombreuses options pour faire que ce ne soit pas une grosse
170 
+    contrainte, par exemple la possibilité de fixer la bande-passante utilisée,
171 
+    celle de définir les règles de sorties du réseau Tor de manière à limiter
172 
+    les risques d'être ennuyé par des plaintes, ainsi que la gestion des
173 
+    connexions à adresses IP dynamiques. </p>
174 
+
175 
+    <p>C'est le fait d'avoir des relais partout sur internet qui sécurise son
176 
+    utilisation. C'est aussi <a
177 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">avantageux
178 
+    pour son propre anonymat</a> d'héberger un noeud Tor , car les sites
179 
+    distants auxquels vous vous connectez personnellement ne pourront pas savoir
180 
+    si c'est vous qui vous connectez ou si vous ne faites que relayer les
181 
+    connexions d'autres.</p>
182 
+
183 
+    <p>Pour plus d'informations, lire le guide : <a href="<page
184 
+    docs/tor-doc-relay>">Configurer un relais</a>. </p>
185 
+
186 
+    <hr />
187 
+
188 
+    <p>Si vous avez des suggestions à faire pour améliorer ce document, <a
189 
+    href="<page about/contact>">envoyez-nous un message</a>. Merci !</p>
190 
+  </div>
191 
+  <!-- END MAINCOL -->
192 
+  <div id = "sidecol">
193 
+#include "side.wmi"
194 
+#include "info.wmi"
195 
+  </div>
196 
+  <!-- END SIDECOL -->
197 
+</div>
198 
+<!-- END CONTENT -->
199 
+#include <foot.wmi>
docs/fr/tor-hidden-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,286 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22314 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurer des Services Cachés pour <a href="<page index>">Tor</a></h1>
14 
+    <hr />
15 
+
16 
+    <p>Tor permet aux clients et aux relais d'offrir des services cachés. Ainsi,
17 
+    vous pouvez rendre disponible un serveur web, un serveur SSH, etc., sans
18 
+    avoir à révéler votre adresse IP aux utilisateurs. Et même, du fait que vous
19 
+    n'utilisez pas d'adresse publique, vous pouvez faire tourner un service
20 
+    caché derrière votre pare-feu.
21 
+    </p>
22 
+
23 
+    <p>If you have Tor installed, you can see hidden services in action by visiting
24 
+    <a href="http://duskgytldkxiuqc6.onion/">our example hidden service</a>.
25 
+    </p>
26 
+
27 
+    <p>Ce « howto » décrit les étapes pour paramétrer votre propre site web en
28 
+    service caché. Si vous désirez plus de détails techniques sur le
29 
+    fonctionnement du protocole de service caché, consultez notre page sur <a
30 
+    href="<page docs/hidden-services>">le protocole de service caché</a>.
31 
+    </p>
32 
+
33 
+    <hr />
34 
+    <a id="zero"></a>
35 
+    <h2><a class="anchor" href="#zero">Étape zéro : s'assurer que Tor fonctionne</a></h2>
36 
+    <br />
37 
+
38 
+    <p>Avant de commencer, il est nécessaire de s'assurer que :</p>
39 
+    <ol>
40 
+    <li>Tor est lancé et fonctionne ;</li>
41 
+    <li>Vous l'avez configuré correctement.</li>
42 
+    </ol>
43 
+
44 
+
45 
+    <p>Les utilisateurs Windows devraient suivre le <a href="<page
46 
+    docs/tor-doc-windows>">howto Windows</a>, les utilisateurs d'OS X devraient
47 
+    regarder le <a href="<page docs/tor-doc-osx>">howto OS X</a>, et les
48 
+    utilisateurs Linux/BSD/Unix devraient suivre le <a href="<page
49 
+    docs/tor-doc-unix>">howto Unix</a>.
50 
+    </p>
51 
+
52 
+    <p>Une fois que vous avez installé et configuré Tor, vous pouvez accéder à des
53 
+    services cachés actifs sur le web en visitant <a
54 
+    href="http://duskgytldkxiuqc6.onion/">notre exemple de service caché</a> ou
55 
+    <a href="http://gaddbiwdftapglkq.onion/">le service caché Wikileaks</a>.  Ça
56 
+    prend généralement de 10 à 60 secondes pour charger (ou décider de
57 
+    l'inaccessibilité).  Si ça ne fonctionne pas immédiatement et que votre
58 
+    navigateur envoie une alerte disant que "www.duskgytldkxiuqc6.onion ne peut
59 
+    pas être trouvé, merci de vérifier le nom et de réessayer." alors vous
60 
+    n'avez pas configuré Tor correctement ; consultez <a
61 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">l'entrée
62 
+    « ça ne marche pas » de la FAQ</a> pour plus d'aide.
63 
+    </p>
64 
+
65 
+    <hr />
66 
+    <a id="one"></a>
67 
+    <h2><a class="anchor" href="#one">Première étape : installer un serveur Web
68 
+    localement</a></h2>
69 
+    <br />
70 
+
71 
+    <p>Premièrement, vous avez besoin de configurer un serveur web
72 
+    local. Paramétrer un serveur web peut s'avérer délicat, nous n'allons donc
73 
+    que survoler les bases ici. Si vous n'y arrivez pas ou cherchez à en faire
74 
+    plus, demandez à un ami de vous aider. Nous vous recommandons d'installer un
75 
+    serveur web séparé pour votre service caché, puisque même si vous en avez
76 
+    déjà un d'installé, vous l'utilisez peut-être déjà (ou planifiez de
77 
+    l'utiliser plus tard) pour un usage différent.
78 
+    </p>
79 
+
80 
+    <p>Si vous êtes sous Unix ou OS X et que vous vous sentez à l'aise avec la
81 
+    ligne de commande, le plus simple, et de loin, est d'installer <a
82 
+    href="http://www.acme.com/software/thttpd/">thttpd</a>. Rapatriez juste la
83 
+    dernière archive, décompressez la (elle créé son propre répertoire), et
84 
+    lancez <kbd>./configure &amp;&amp; make</kbd>. Puis <kbd>mkdir hidserv; cd
85 
+    hidserv</kbd>, et lancez <kbd>../thttpd -p 5222 -h localhost</kbd>. Vous
86 
+    devriez retrouver le prompt, et à ce stade vous êtes en train de faire
87 
+    tourner un serveur web sur le port 5222. Vous pouvez mettre des fichiers
88 
+    dans le répertoire hidserv.
89 
+    </p>
90 
+
91 
+    <p>Si vous êtes sous Windows, vous devriez prendre <a
92 
+    href="http://savant.sourceforge.net/">Savant</a> ou <a
93 
+    href="http://httpd.apache.org/">Apache</a>, et vous assurer que vous l'avez
94 
+    mis en écoute uniquement sur localhost. Vous devriez aussi connaître le port
95 
+    sur lequel vous écoutez, parce que vous allez l'utiliser plus tard.
96 
+    </p>
97 
+
98 
+    <p>(La raison pour laquelle nous connectons le serveur web seulement sur
99 
+    localhost est de s'assurer qu'il ne sera pas accessible publiquement. Si des
100 
+    gens peuvent se connecter directement, ils pourraient confirmer que votre
101 
+    ordinateur est bien celui qui offre le service caché.)
102 
+    </p>
103 
+
104 
+    <p>Une fois votre serveur web paramétré, assurez-vous qu'il fonctionne : ouvrez
105 
+    votre navigateur et allez sur <a
106 
+    href="http://localhost:5222/">http://localhost:5222/</a>, où 5222 est le
107 
+    port que vous avez choisi plus haut. Puis, essayez de mettre un fichier dans
108 
+    le repertoire html principal, et assurez-vous que vous pouvez y accéder.
109 
+    </p>
110 
+
111 
+    <hr />
112 
+    <a id="two"></a>
113 
+    <h2><a class="anchor" href="#two">Deuxième étape : configurer votre service
114 
+    caché</a></h2>
115 
+    <br />
116 
+
117 
+    <p>Ensuite, vous devez configurer votre service caché pour qu'il pointe sur
118 
+    votre serveur web local.
119 
+    </p>
120 
+
121 
+    <p>Premièrement, ouvrez votre fichier torrc dans votre éditeur de texte
122 
+    favoris. (Consultez <a
123 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">la
124 
+    FAQ torrc</a> pour plus d'information.) Allez au milieu du fichier et
125 
+    cherchez la ligne</p>
126 
+
127 
+    <pre>
128 
+    \############### This section is just for location-hidden services ###
129 
+    </pre>
130 
+
131 
+    <p>
132 
+    Cette section du fichier consiste en un groupe de lignes, chacune
133 
+    représentant un service caché. Actuellement elles sont toutes en commentaire
134 
+    (les lignes commençant par #), ainsi les services cachés sont
135 
+    désactivés. Chaque groupe de lignes consiste en une ligne
136 
+    <var>HiddenServiceDir</var>, et une ou plus <var>HiddenServicePort</var> : </p>
137 
+    <ul>
138 
+    <li><var>HiddenServiceDir</var> is a directory where Tor will store information
139 
+    about that hidden service.  In particular, Tor will create a file here named
140 
+    <var>hostname</var> which will tell you the onion URL.  You don't need to
141 
+    add any files to this directory. Make sure this is not the same directory as
142 
+    the hidserv directory you created when setting up thttpd, as your
143 
+    HiddenServiceDir contains secret information!</li>
144 
+    <li><var>HiddenServicePort</var> vous permet de spécifier un port virtuel (c'est
145 
+    celui que les gens penseront utiliser en accédant à votre service) et une
146 
+    adresse IP et un port pour les redirections vers ce port virtuel.</li>
147 
+    </ul>
148 
+
149 
+    <p>Ajoutez les lignes suivantes dans votre torrc :
150 
+    </p>
151 
+
152 
+    <pre>
153 
+    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
154 
+    HiddenServicePort 80 127.0.0.1:5222
155 
+    </pre>
156 
+
157 
+    <p>You're going to want to change the <var>HiddenServiceDir</var> line, so it
158 
+    points to an actual directory that is readable/writeable by the user that
159 
+    will be running Tor. The above line should work if you're using the OS X Tor
160 
+    package. On Unix, try "/home/username/hidden_service/" and fill in your own
161 
+    username in place of "username". On Windows you might pick:</p>
162 
+    <pre>
163 
+    HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\\
164 
+    HiddenServicePort 80 127.0.0.1:5222
165 
+    </pre>
166 
+
167 
+    <p>Maintenant sauvegardez votre torrc, coupez votre Tor, et ensuite redémarrez
168 
+    le.
169 
+    </p>
170 
+
171 
+    <p>Si Tor redémarre, c'est génial ! Sinon, quelque chose se passe
172 
+    mal. Premièrement regardez les logs pour avoir des pistes. Il devrait y
173 
+    avoir des avertissements ou des erreurs. Ça devrait vous donner une idée du
174 
+    pourquoi ça se passe mal. Souvent des erreurs de frappe dans le fichier
175 
+    torrc ou de droits d'accès aux répertoires. (Voyez <a
176 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">la FAQ
177 
+    sur les logs</a> si vous ne savez pas comment les activer ou bien où les
178 
+    trouver.)
179 
+    </p>
180 
+
181 
+    <p>Quand Tor se lance, il doit automatiquement créer le
182 
+    <var>HiddenServiceDir</var> que vous avez spécifié (si nécessaire), et il
183 
+    devrait y créer deux fichiers.</p>
184 
+
185 
+    <dl>
186 
+    <dt><var>private_key</var></dt>
187 
+    <dd>Premièrement, Tor va générer une nouvelle paire de clés publique/privée pour
188 
+    votre service caché, et les écrire dans un fichier appelé "private_key". Ne
189 
+    partagez pas cette clé avec d'autre ; si vous le faite ils peuvent découvrir
190 
+    qui fait fonctionner votre service caché.</dd>
191 
+    <dt><var>hostname</var></dt>
192 
+    <dd>L'autre fichier qui va être créé s'appelle "hostname". Il contient un court
193 
+    résumé de votre clé publique -- ça devrait ressembler à quelque chose comme
194 
+    <tt>duskgytldkxiuqc6.onion</tt>. C'est le nom public pour votre service, et
195 
+    vous pouvez l'annoncer à d'autre gens, le publier, le mettre sur votre carte
196 
+    de visite, etc.</dd>
197 
+    </dl>
198 
+
199 
+    <p>Si Tor tourne sous un utilisateur différent du votre, par exemple sous OS X,
200 
+    Debian, or Red Hat, vous devrez devenir root pour être autorisé à consulter
201 
+    ces fichiers.</p>
202 
+
203 
+    <p>Maintenant que vous avez redémarré Tor, il collecte des points
204 
+    d'introduction dans le réseau Tor, et génère ce qui est appelé un
205 
+    <em>descripteur de service caché</em>, qui est une liste de points
206 
+    d'introduction signée avec la pleine clé publique. Il publie ce descripteur
207 
+    anonymement aux serveurs d'annuaires, et d'autres utilisateurs peuvent
208 
+    anonymement le rapatrier à partir des serveurs d'annuaires lorsqu'ils
209 
+    souhaitent accéder à votre service.
210 
+    </p>
211 
+
212 
+    <p>Essayez maintenant : coller le contenu du fichier hostname dans votre
213 
+    navigateur web. Si ça marche, vous devriez avoir la page html que vous avez
214 
+    paramétré à la première étape.  Si ça ne fonctionne pas, jetez un œil dans
215 
+    vos logs pour vous aider, et continuez d'essayer jusqu'à ce que ça
216 
+    fonctionne.
217 
+    </p>
218 
+
219 
+    <hr />
220 
+    <a id="three"></a>
221 
+    <h2><a class="anchor" href="#three">Troisième étape : astuces plus avancées</a></h2>
222 
+    <br />
223 
+
224 
+    <p>Si vous envisagez de maintenir votre service pendant quelques temps, il est
225 
+    conseillé de faire une copie de votre fichier <var>private_key</var> quelque
226 
+    part.
227 
+    </p>
228 
+
229 
+    <p>Nous avons évité de recommander Apache au dessus, a) parce que beaucoup de
230 
+    personnes le font déjà tourner comme serveur public sur leur ordinateur et
231 
+    b) parce que c'est un programme assez lourd et qu'li est en mesure de
232 
+    révéler votre adresse IP ou des informations permettant de vous identifier à
233 
+    un grand nombre d'endroits, par exemple dans les pages 404. Pour les gens
234 
+    qui ont besoin de plus de fonctionnalités, Apache devrait-être la réponse
235 
+    juste. Est-ce que quelqu'un pourrait faire une liste des points sensibles
236 
+    pour verrouiller Apache lorsque vous l'utilisez comme service caché ? «
237 
+    Savant » doit aussi avoir ce genre de problème.
238 
+    </p>
239 
+
240 
+    <p>Si vous souhaitez renvoyer plusieurs ports virtuels pour un seul service
241 
+    caché, ajoutez simplement plus de lignes <var>HiddenServicePort</var>. Si
242 
+    vous voulez faire tourner plusieurs service cachés à partir du même client
243 
+    Tor, rajoutez simplement une autre ligne <var>HiddenServiceDir</var>. Toutes
244 
+    les lignes suivant le <var>HiddenServicePort</var> se réfèrent a la ligne
245 
+    <var>HiddenServiceDir</var> jusqu'a ce que vous ajoutiez une autre ligne
246 
+    <var>HiddenServiceDir</var> :
247 
+    </p>
248 
+
249 
+    <pre>
250 
+    HiddenServiceDir /usr/local/etc/tor/hidden_service/
251 
+    HiddenServicePort 80 127.0.0.1:8080
252 
+
253 
+    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
254 
+    HiddenServicePort 6667 127.0.0.1:6667
255 
+    HiddenServicePort 22 127.0.0.1:22
256 
+    </pre>
257 
+
258 
+    <p>Il y a quelques problèmes d'anonymat que vous devriez également garder à
259 
+    l'esprit :
260 
+    </p>
261 
+    <ul>
262 
+    <li>Comme cité au dessus, soyez vigilant sur ce que votre serveur web révèle de
263 
+    vous, de votre ordinateur, de votre emplacement géographique. Par exemple,
264 
+    les lecteurs peuvent facilement déterminer s'il s'agit de thttpd ou
265 
+    d'Apache, et apprendre quelque chose sur votre système d'exploitation.</li>
266 
+    <li>Si votre ordinateur n'est pas en ligne en permanence, votre service caché ne
267 
+    le sera pas non plus. Ceci apporte une information à un adversaire
268 
+    observateur.</li>
269 
+
270 
+    <!-- increased risks over time -->
271 
+    </ul>
272 
+
273 
+    <hr />
274 
+
275 
+    <p>Si vous avez des suggestions pour améliorer ce document, n'hésitez pas à <a
276 
+    href="<page about/contact>">nous écrire</a>. Merci !</p>
277 
+  </div>
278 
+  <!-- END MAINCOL -->
279 
+  <div id = "sidecol">
280 
+#include "side.wmi"
281 
+#include "info.wmi"
282 
+  </div>
283 
+  <!-- END SIDECOL -->
284 
+</div>
285 
+<!-- END CONTENT -->
286 
+#include <foot.wmi>
docs/it/N900.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,156 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21979 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: N900 Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/N900>">N900</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="Maemo"></a>
14 
+    <h2><a class="anchor" href="#Maemo">Installare Tor su Maemo</a></h2>
15 
+    <br />
16 
+    <p>
17 
+    If you have a Maemo device that is not the <a href="#N900">N900</a>, we
18 
+    suggest you install the Tor package from the <a
19 
+    href="http://maemo.org/packages/view/tor/">Maemo website</a>. The Tor
20 
+    Project does not produce these packages. They are maintained by the Maemo
21 
+    community.
22 
+    </p>
23 
+
24 
+    <a id="N900"></a>
25 
+    <h2><a class="anchor" href="#N900">Installare Tor sull'N900</a></h2>
26 
+    <br />
27 
+    <p>
28 
+    Le seguenti istruzioni dovrebbero permettere di installare un <a
29 
+    href="https://garage.maemo.org/projects/tor-status">controller Tor
30 
+    sperimentale</a> e Tor in pacchetti per il telefono N900. Attualmente questa
31 
+    è una configurazione non adeguatamente testata:il browser non dispone di
32 
+    Torbutton e non dovrebbe essere usato ancora per necessità di
33 
+    anonimizzazione in alta sicurezza.
34 
+    </p>
35 
+
36 
+    <p>
37 
+    Open the Application manager: <br /> <a href="../img/N900/1_app_menu.png">
38 
+    <img border="0" alt="N900 application menu"
39 
+    src="../img/N900/1_app_menu-small.png"/> </a>
40 
+    </p>
41 
+
42 
+    <p>
43 
+    Clicca sul menù di Gestione Applicazioni in alto nello schermo: <br /> <a
44 
+    href="../img/N900/2_app_manager.png"> <img border="0" alt="N900 application
45 
+    manager" src="../img/N900/2_app_manager-small.png"/> </a>
46 
+    </p>
47 
+
48 
+    <p>
49 
+    Seleziona 'Cataloghi applicazioni': <br /> <a
50 
+    href="../img/N900/3_app_managermenu.png"> <img border="0" alt="N900
51 
+    application catalogs" src="../img/N900/3_app_managermenu-small.png"/> </a>
52 
+    </p>
53 
+
54 
+    <p>
55 
+    Clicca su 'Nuovo' per abilitare il catalogo di maemo extras-devel. <br />
56 
+    <small>Nota: questo catalogo contiene pacchetti non testati che potrebbero
57 
+    danneggiare il tuo dispositivo. <br /> Vedi <a
58 
+    href="http://wiki.maemo.org/Extras-devel">Extras-devel</a> per i
59 
+    dettagli. Probabilmente è preferibile disabilitare questo catalogo dopo aver
60 
+    installato Tor oppure continuare a tuo rischio.</small> <br /> <a
61 
+    href="../img/N900/4_catalog_list.png"> <img border="0" alt="N900 catalog
62 
+    list" src="../img/N900/4_catalog_list-small.png"/> </a>
63 
+    </p>
64 
+
65 
+    <p>
66 
+    Inserisci i seguenti dati nella sezione di aggiunta di cataloghi:
67 
+    <p>
68 
+    <pre>
69 
+    Nome catalogo:    Extras devel
70 
+    Indirizzo web:    http://repository.maemo.org/extras-devel/
71 
+    Distribuzione:        fremantle
72 
+    Componenti:    free non-free
73 
+    </pre>
74 
+    </p>
75 
+    <br /> Assicurati che il bottone 'Disattivato' non sia selezionato, clicca
76 
+    su 'Salva' e attendi che la lista dei pacchetti sia aggiornata.<br /> <a
77 
+    href="../img/N900/5_new_catalog.png"> <img border="0" alt="N900 new catalog"
78 
+    src="../img/N900/5_new_catalog-small.png"/> </a>
79 
+    </p>
80 
+
81 
+    <p>
82 
+    Clicca su 'Installa' in Gestione Applicazioni: <br /> <a
83 
+    href="../img/N900/6_app_manager.png"> <img border="0" alt="N900 app manager"
84 
+    src="../img/N900/6_app_manager-small.png"/> </a>
85 
+    </p>
86 
+
87 
+    <p>
88 
+    Seleziona la categoria 'Rete' (oppure cerca Tor): <br /> <a
89 
+    href="../img/N900/7_app_categories.png"> <img border="0" alt="N900
90 
+    application categories" src="../img/N900/7_app_categories-small.png"/> </a>
91 
+    </p>
92 
+
93 
+    <p>
94 
+    Scorri fino a 'Tor Status Area Applet': <br /> <a
95 
+    href="../img/N900/8_app_list.png"> <img border="0" alt="N900 application
96 
+    list" src="../img/N900/8_app_list-small.png"/> </a>
97 
+    </p>
98 
+
99 
+    <p>
100 
+    Accetta l'informativa e clicca su 'Continua': <br /> <a
101 
+    href="../img/N900/9_disclaimer.png"> <img border="0" alt="N900 disclaimer"
102 
+    src="../img/N900/9_disclaimer-small.png"/> </a>
103 
+    </p>
104 
+
105 
+    <p>
106 
+    Quando l'installazione è terminata, disabilita il catalogo extras-devel e
107 
+    riavvia il telefono: <br /> <a href="../img/N900/10_success.png"> <img
108 
+    border="0" alt="N900 success" src="../img/N900/10_success-small.png"/> </a>
109 
+    </p>
110 
+
111 
+    <p>
112 
+    Dopo il riavvio dell'N900 apri il menù di stato: <br /> <a
113 
+    href="../img/N900/11_after_rebooting.png"> <img border="0" alt="N900 status
114 
+    menu post-reboot" src="../img/N900/11_after_rebooting-small.png"/> </a>
115 
+    </p>
116 
+
117 
+    <p>
118 
+    Seleziona 'The Onion Router' dalla lista: <br /> <a
119 
+    href="../img/N900/12_status_menu.png"> <img border="0" alt="N900 status menu
120 
+    selection" src="../img/N900/12_status_menu-small.png"/> </a>
121 
+    </p>
122 
+
123 
+    <p>
124 
+    Abilita l'onion routing e clicca su 'Save': <br /> <a
125 
+    href="../img/N900/13_enable_tor.png"> <img border="0" alt="N900 enabling
126 
+    Tor" src="../img/N900/13_enable_tor-small.png"/> </a>
127 
+    </p>
128 
+
129 
+    <p>
130 
+    Collegati a <a href="https://check.torproject.org/">TorCheck</a> per avere
131 
+    la conferma che il traffico del browser sia istradato via Tor: <br /> <a
132 
+    href="../img/N900/14_check_tor.png"> <img border="0" alt="N900 check Tor"
133 
+    src="../img/N900/14_check_tor-small.png"/> </a>
134 
+    </p>
135 
+
136 
+    <p>
137 
+    Nota che questa procedura potrebbe non renderti disponibile sempre l'ultima
138 
+    versione stabile di Tor.  Inoltre, poiché il browser dell'N900 non ha a
139 
+    disposizione Torbutton, rende tutto ciò utile valido per l'elusione ma
140 
+    probabilmente non adatto a necessità di forte anonimizzazione del browser.
141 
+    </p>
142 
+
143 
+    <hr />
144 
+
145 
+    <p>Se hai suggerimenti per migliorare questo documento <a  href="<page
146 
+    about/contact>">scrivici</a>. Grazie!</p>
147 
+  </div>
148 
+  <!-- END MAINCOL -->
149 
+  <div id = "sidecol">
150 
+#include "side.wmi"
151 
+#include "info.wmi"
152 
+  </div>
153 
+  <!-- END SIDECOL -->
154 
+</div>
155 
+<!-- END CONTENT -->
156 
+#include <foot.wmi>
docs/it/debian.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,185 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22268 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian>">Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <h2><a class="anchor" href="#debian">Prima possibilit&agrave;: Tor su Debian lenny,
15 
+    Debian sid, o Debian testing</a></h2>
16 
+    <br />
17 
+
18 
+    <p>
19 
+    Se usi Debian stable (lenny), unstable (sid), o testing
20 
+    (squeeze), esegui semplicemente<br />
21 
+    <tt>apt-get install tor tor-geoipdb</tt>
22 
+    </p>
23 
+
24 
+    <p>
25 
+    Non otterrai sempre l'ultima versione stabile di Tor, ma riceverai
26 
+    gli aggiornamenti di sicurezza importanti. Per utilizzare invece
27 
+    l'ultima versione stabile di Tor, vedi pi&ugrave; sotto la seconda possibilit&agrave;.
28 
+    </p>
29 
+
30 
+    <p>
31 
+    Ora Tor &egrave; installato ed attivo. Vai al <a href="<page
32 
+    docs/tor-doc-unix>#polipo">passo due</a> delle istruzioni per "Tor su Linux/Unix".
33 
+    </p>
34 
+
35 
+    <hr />
36 
+
37 
+    <a id="ubuntu"></a>
38 
+    <a id="packages"></a>
39 
+    <h2><a class="anchor" href="#ubuntu">Seconda possibilit&agrave;: Tor su Ubuntu o
40 
+    Debian</a></h2>
41 
+    <br />
42 
+
43 
+    <p>
44 
+    <b>Non usare i pacchetti in Ubuntu universe.</b> Non sono mantenuti
45 
+    e non sono aggiornati. Potresti non avere importanti aggiornamenti di stabilit&agrave;
46 
+    e sicurezza.
47 
+    </p>
48 
+
49 
+    <p>
50 
+    Devi anzitutto configurare un repository di pacchetti per potere installare
51 
+    Tor. Per prima cosa trova il nome della tua distribuzione. Se usi
52 
+    Ubuntu 9.04, &egrave; "jaunty". Ubuntu 8.10 &egrave; "intrepid",
53 
+    ed Ubuntu 8.04 &egrave; "hardy". Se usi Debian Etch, &egrave; "etch", Debian
54 
+    Lenny &egrave; "lenny". Poi aggiungi al file <tt>/etc/apt/sources.list</tt>
55 
+    questa riga:<br />
56 
+    <pre>
57 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
58 
+    </pre>
59 
+    dove sostituisci il nome (etch, lenny, sid, jaunty, intrepid,
60 
+    hardy) al posto di &lt;DISTRIBUTION&gt;.
61 
+    </p>
62 
+
63 
+    <p>
64 
+    Per ora non abbiamo pacchetti per Ubuntu 9.10 (Karmic Koala), ma quelli per
65 
+    Debian sid funzionano. Invece di mettere "karmic" nelle sources.list,
66 
+    usa "sid".
67 
+    </p>
68 
+
69 
+    <p>
70 
+    Esegui poi:
71 
+    <pre>
72 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
73 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
74 
+    apt-get update
75 
+    apt-get install tor tor-geoipdb
76 
+    </pre>
77 
+    </p>
78 
+
79 
+    <p>
80 
+    Ora Tor &egrave; installato ed attivo. Vai al <a href="<page
81 
+    docs/tor-doc-unix>#polipo">passo due</a> delle istruzioni"Tor su Linux/Unix"
82 
+    .
83 
+    </p>
84 
+
85 
+    <p style="font-size: small">
86 
+    Il nome DNS <code>deb.torproject.org</code> &egrave; in realt&agrave; un gruppo di server
87 
+    DNS indipendenti in configurazione round robin. Se per qualche motivo non puoi
88 
+    accedervi, prova ad usare il nome di uno dei suoi componenti, come
89 
+    <code>deb-master.torproject.org</code>,
90 
+    <code>mirror.netcologne.de</code> or
91 
+    <code>tor.mirror.youam.de</code>.
92 
+    </p>
93 
+
94 
+    <hr />
95 
+
96 
+    <a id="development"></a>
97 
+    <h2><a class="anchor" href="#development">Terza possibilit&agrave;: usare la versione
98 
+    di sviluppo di Tor su Debian od Ubuntu</a></h2>
99 
+    <br />
100 
+
101 
+    <p>Se vuoi usare la <a href="<page
102 
+    download/download>#packagediff">versione di sviluppo</a> di Tor (pi&ugrave; funzionalit&agrave; e
103 
+    pi&ugrave; bachi), devi aggiungere delle righe diverse al
104 
+    tuo file <tt>/etc/apt/sources.list</tt>:<br />
105 
+    <pre>
106 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
107 
+    deb     http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
108 
+    </pre>
109 
+    dove sostituisci la tua distribuzione (etch, lenny, sid, jaunty,
110 
+    intrepid, hardy) al posto di &lt;DISTRIBUTION&gt;.
111 
+    </p>
112 
+
113 
+    <p>
114 
+    Poi esegui
115 
+    <pre>
116 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
117 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
118 
+    apt-get update
119 
+    apt-get install tor tor-geoipdb
120 
+    </pre>
121 
+    </p>
122 
+
123 
+    <p>
124 
+    Ora Tor &egrave; installato ed attivo. Vai al <a href="<page
125 
+    docs/tor-doc-unix>#polipo">passo due</a> delle istruzioni "Tor su Linux/Unix"
126 
+    .
127 
+    </p>
128 
+
129 
+    <hr />
130 
+
131 
+    <a id="source"></a>
132 
+    <h2><a class="anchor" href="#source">Compilare dai sorgenti</a></h2>
133 
+    <br />
134 
+
135 
+    <p>
136 
+    Se vuoi compilare i tuoi deb dai sorgenti devi aggiungere la riga
137 
+    appropriata <tt>deb-src</tt> a <tt>sources.list</tt>.
138 
+    <pre>
139 
+    # Per la versione stabile
140 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
141 
+
142 
+    # Per la versione instabile
143 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
144 
+    deb-src http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
145 
+    </pre>
146 
+    Devi anche installare i pacchetti necessari a compilare i tuoi deb e
147 
+    Tor:
148 
+    <pre>
149 
+    apt-get install build-essential fakeroot devscripts
150 
+    apt-get build-dep tor
151 
+    </pre>
152 
+    Dopodich&eacute; puoi compilare Tor in ~/debian-packages:
153 
+    <pre>
154 
+    mkdir ~/debian-packages; cd ~/debian-packages
155 
+    apt-get source tor
156 
+    cd tor-*
157 
+    debuild -rfakeroot -uc -us
158 
+    cd ..
159 
+    </pre>
160 
+    Ora puoi installare il nuovo pacchetto:
161 
+    <pre>
162 
+    sudo dpkg -i tor_*.deb
163 
+    </pre>
164 
+    </p>
165 
+
166 
+    <p>
167 
+    Ora Tor &egrave; installato ed attivo. Vai al <a href="<page
168 
+    docs/tor-doc-unix>#polipo">passo due</a> delle istruzioni "Tor su Linux/Unix"
169 
+    .
170 
+    </p>
171 
+
172 
+    <hr />
173 
+
174 
+    <p>Se hai dei suggerimenti per migliorare questo documento, allora <a
175 
+    href="<page about/contact>">diccelo</a>. Grazie!</p>
176 
+  </div>
177 
+  <!-- END MAINCOL -->
178 
+  <div id = "sidecol">
179 
+#include "side.wmi"
180 
+#include "info.wmi"
181 
+  </div>
182 
+  <!-- END SIDECOL -->
183 
+</div>
184 
+<!-- END CONTENT -->
185 
+#include <foot.wmi>
docs/it/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/it/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,207 @@
1 
+ ## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Usare il client <a href="<page index>">Tor</a> su Mac OS X</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Queste sono le istruzioni per installare e usare un client Tor
18 
+    su Mac OS X. Se invece vuoi offrire banda e traffico per aiutare a fare crescere la rete Tor
19 
+    (s&igrave;, grazie!), leggi la guida per <a
20 
+     href="<page docs/tor-doc-relay>">configurare un relay</a>.</b>
21 
+    </p>
22 
+
23 
+    <hr />
24 
+    <a id="installing"></a>
25 
+    <h2><a class="anchor" href="#installing">Uno: scarica e installa Tor</a></h2>
26 
+    <br />
27 
+
28 
+    <p>
29 
+    L'installer per Macintosh OS X comprende
30 
+    <a href="<page index>">Tor</a>,
31 
+    <a href="<page projects/vidalia>">Vidalia</a> (una interfaccia grafica per Tor),
32 
+    <a href="<page projects/torbutton>">Torbutton</a>,
33 
+    e <a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (un proxy web)
34 
+    in  un pacchetto comprendente le quattro applicazioni preconfigurate in modo
35 
+    da funzionare insieme.
36 
+    Scarica la versione <a href="../<package-osx-bundle-stable>">stabile</a>
37 
+    o quella <a href="../<package-osx-bundle-alpha>">sperimentale</a>
38 
+    del pacchetto OS X, oppure scegli tra pi&ugrave; opzioni dalla <a href="<page
39 
+    download/download>">pagina di download</a>.
40 
+    </p>
41 
+
42 
+    <p>Una volta scaricato il file dmg, fai doppio clic per montarlo.
43 
+    Vai ora al Vidalia Bundle nel Finder. &Egrave; facile installare il pacchetto, trascina semplicemente
44 
+    l'icona a cipolla di Vidalia nella cartella Applicazioni. Facoltativamente, fai doppio clic sullo script
45 
+    "install torbutton" ed installa torbutton in Firefox.
46 
+    Puoi anche scaricare Torbutton dai componenti aggiuntivi di Mozilla facendo una ricerca per
47 
+    "torbutton".</p>
48 
+
49 
+    <p>Dopo aver finito l'installazione puoi avviare Vidalia selezionandone l'icona
50 
+    dalla cartella Applicazioni. Una cipolla di colore scuro con una X rossa nel dock significa
51 
+    che Tor non &egrave; in esecuzione. Puoi eseguire Tor selezionando Start dal menu
52 
+    "Tor" nella parte superiore dello schermo.
53 
+    </p>
54 
+
55 
+    <p>Quando Tor &egrave; in esecuzione, l'icona del dock di Vidalia ha questo aspetto:
56 
+    </p>
57 
+
58 
+    <p><img alt="vidalia running tor"
59 
+    src="../img/screenshot-osx-vidalia.png"
60 
+    border="1"/></p>
61 
+
62 
+    <p>Polipo viene installato insieme al pacchetto di installazione di Tor.
63 
+    Una volta installato viene eseguito automaticamente quando
64 
+    riavii il tuo computer.
65 
+    Non occorre configurare Polipo per usare Tor. Infatti col pacchetto di installazione
66 
+    &egrave; stata installata anche una configurazione ad hoc di Polipo per Tor.
67 
+    </p>
68 
+
69 
+    <hr />
70 
+    <a id="using"></a>
71 
+    <h2><a class="anchor" href="#using">Due: configura i tuoi programmi per usare Tor</a></h2>
72 
+    <br />
73 
+
74 
+    <p>Dopo avere installato Tor e Polipo, occorre configuare i propri
75 
+    programmi perch&eacute; li usino. Per prima cosa configuriamo il browser web.</p>
76 
+
77 
+    <p>Per una sicurezza ottimale dovresti usare Tor con Firefox e Torbutton.
78 
+    Torbutton &egrave; gi&agrave; installato per te: fai clic sul pulsante "Tor disattivato" per
79 
+    avviare Tor, ed &egrave; tutto:
80 
+
81 
+    <p><img alt="Torbutton plugin for Firefox"
82 
+    src="../img/screenshot-torbutton.png"
83 
+    border="1"/></p>
84 
+
85 
+    <p>
86 
+    Se usi Firefox su un computer diverso da quello su cui gira Tor, leggi la <a
87 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">FAQ
88 
+    per usare Tor su un computer diverso</a>.
89 
+    </p>
90 
+
91 
+    <p>Per usare Tor con altre applicazioni che supportano proxy HTTP, basta
92 
+    puntarli a Polpipo (ovvero a localhost porta 8118). Per usare SOCKS
93 
+    direttamente (per l'instant messaging, Jabber, IRC, etc), puoi puntare la tua applicazione
94 
+    direttamente a Tor (localhost porta 9050), ma leggi anche <a
95 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">questa
96 
+    FAQ</a> che spiega perch&eacute; pu&ograve; essere pericoloso. Per le applicazioni
97 
+    che non supportano n&eacute; SOCKS n&eacute; HTTP, dai un'occhiata a <a
98 
+    href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a> o a
99 
+    <a href="http://www.dest-unreach.org/socat/">socat</a>.</p>
100 
+
101 
+    <p>Per informazioni su come torificare altri programmi, guarda il
102 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
103 
+    HOWTO</a>.
104 
+    </p>
105 
+
106 
+    <hr />
107 
+    <a id="verify"></a>
108 
+    <h2><a class="anchor" href="#verify">Tre: controlla che funzioni</a></h2>
109 
+    <br />
110 
+
111 
+    <p>
112 
+    Ora devi provare Tor col tuo browser per controllare
113 
+    che il tuo indirizzo IP sia anonimo. Fai clic sul
114 
+    <a href="https://check.torproject.org/">Tor
115 
+    detector</a> e controlla se rileva che stai usando Tor oppure no
116 
+    (se questo sito &egrave; gi&ugrave;, vedi <a
117 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">questa
118 
+    FAQ</a> per altri modi di testare il tuo Tor).
119 
+    </p>
120 
+
121 
+    <p>Se hai un personal firewall che limita le connessioni del tuo pc
122 
+    a se stesso, controlla che siano permesse le connessioni dalle
123 
+    applicazioni locali alla porta locale 8118 e alla porta 9050. Se
124 
+    il tuo firewall blocca le connessioni in uscita, permettigli di
125 
+    collegarsi almeno alle porte TCP 80 e 443, poi leggi <a
126 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">questa
127 
+    FAQ</a>.
128 
+    </p>
129 
+
130 
+    <p>Se nemmeno ora funziona, guarda <a
131 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">questa
132 
+    FAQ</a> per ulteriori indicazioni.</p>
133 
+
134 
+    <p>
135 
+    Una volta che funziona, leggi bene
136 
+    <a href="<page download/download>#Warning">che cosa Tor fa e non fa</a>.
137 
+    </p>
138 
+
139 
+    <hr />
140 
+    <a id="server"></a>
141 
+    <a id="relay"></a>
142 
+    <h2><a class="anchor" href="#relay">Quattro: configura Tor come relay</a></h2>
143 
+    <br />
144 
+
145 
+    <p>La rete Tor funziona grazie alla banda donata dai volontari. Pi&ugrave;
146 
+    persone aprono un relay, pi&ugrave; veloce sar&agrave; la rete Tor. Se hai almeno
147 
+    20 kilobyte/s in download e upload, aiuta Tor e configura la tua installazione
148 
+    Tor come relay. Ci sono tante funzionalit&agrave; che rendono un Tor relay facile
149 
+    e pratico, come il controllo della banda, exit policy per
150 
+    limitare il rischio di abusi e lamentele, e il supporto per indirizzi
151 
+    IP dinamici.</p>
152 
+
153 
+    <p>La distribuzione di relay in tanti luoghi diversi della rete
154 
+    rende pi&ugrave; sicuri gli utenti di Tor. <a
155 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Puoi
156 
+    ottenere un migliore anonimato tu stesso</a>,
157 
+    dato che non sar&agrave; possibile sapere se una connessione &egrave; partita dal tuo
158 
+    computer o &egrave; stata trasportata da un altro nodo Tor.</p>
159 
+
160 
+    <p>Leggi la guida <a href="<page docs/tor-doc-relay>">come configurare un relay</a>
161 
+    .</p>
162 
+
163 
+    <hr />
164 
+    <a id="uninstall"></a>
165 
+    <h2><a class="anchor" href="#uninstall">Disinstallare Tor e Polipo</a></h2>
166 
+    <br />
167 
+
168 
+    <p>Puoi disinstallare il pacchetto dal tuo computer in due modi, con il
169 
+    Finder o con un disinstallatore da Terminale o riga di comando. Se vuoi rimuovere Tor da OSX, ecco come fare:</p>
170 
+
171 
+    <p>Riporta la configurazione proxy dei tuoi programmi ai valori originali.
172 
+    Se ti interessa semplicemente smettere di usare Tor, puoi fermarti qui.</p>
173 
+
174 
+    <p>Se invece vuoi rimuovere completamente Tor, e il tuo account ha privilegi di
175 
+    amministratore, fai cos&igrave;:</p>
176 
+    <ol>
177 
+    <li>Apri il Finder e fai clic su Applicazioni.</li>
178 
+    <li>Sposta /Applicazioni/Vidalia nel Cestino.</li>
179 
+    <li>Cancella /Libreria/Torbutton dal sistema.</li>
180 
+    <li>Nella tua cartella Inizio, vai a Libreria e cancella la cartella
181 
+    Vidalia</li>
182 
+    </ol>
183 
+    <p>Tor, Vidalia e Polipo sono ora completamente rimossi dal tuo sistema.</p>
184 
+
185 
+    <p>Se ti trovi a tuo agio con la riga di comando o con Terminale, puoi
186 
+    cancellare manualmente i file e cartelle seguenti:</p>
187 
+    <ul>
188 
+    <li>/Applicazioni/Vidalia.app/</li>
189 
+    <li>/Libreria/Torbutton/</li>
190 
+    <li>~/Libreria/Vidalia</li>
191 
+    <li>~/.tor</li>
192 
+    </ul>
193 
+
194 
+    <hr />
195 
+
196 
+    <p>Se hai delle proposte per migliorare questo documento, per favore
197 
+    <a href="<page about/contact>">inviacele</a>. Grazie!</p>
198 
+  </div>
199 
+  <!-- END MAINCOL -->
200 
+  <div id = "sidecol">
201 
+#include "side.wmi"
202 
+#include "info.wmi"
203 
+  </div>
204 
+  <!-- END SIDECOL -->
205 
+</div>
206 
+<!-- END CONTENT -->
207 
+#include <foot.wmi>
docs/it/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,295 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurare un relay Tor</h1>
14 
+
15 
+    <!-- BEGIN SIDEBAR -->
16 
+    <div class="sidebar-left">
17 
+    <h3>Istruzioni per la configurazione</h3>
18 
+    <ol>
19 
+    <li><a href="<page docs/tor-doc-relay>#install">Scarica &amp; Installa</a></li>
20 
+    <li><a href="<page docs/tor-doc-relay>#setup">Configura</a></li>
21 
+    <li><a href="<page docs/tor-doc-relay>#check">verifica &amp; Conferma</a></li>
22 
+    <li><a href="<page docs/tor-doc-relay>#after">Ultimi Passi</a></li>
23 
+    </ol>
24 
+    </div>
25 
+    <!-- END SIDEBAR -->
26 
+
27 
+    <hr />
28 
+
29 
+    <p>
30 
+    La rete Tor &egrave; formata da volontari che offrono la propria banda. Quante
31 
+    pi&ugrave; persone hanno un relay, tanto pi&ugrave; veloce sar&agrave; la rete Tor. Se hai
32 
+    almeno 20 kilobyte/s sia up che down, aiuta la rete configurando il tuo software Tor
33 
+    come relay. Gestire un relay Tor &egrave; semplice e ci sono funzionalit&agrave;
34 
+    molto comode, come il <a href="<page docs/faq>#RelayFlexible">controllo della banda</a> usata,
35 
+    exit policy che permettono di ridurre il rischio di lamentele ed abusi,
36 
+    ed il supporto per indirizzi IP dinamici.
37 
+    </p>
38 
+
39 
+    <p>Puoi realizzare un relay Tor su <a
40 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">quasi
41 
+    tutti</a> i sistemi operativi, ma Linux, FreeBSD 5.x+, OS X Tiger o
42 
+    successivi, Windows Server 2003 e successivi funzionano al meglio.
43 
+    </p>
44 
+
45 
+    <hr />
46 
+    <a id="zero"></a>
47 
+    <a id="install"></a>
48 
+    <h2><a class="anchor" href="#install">Fase Uno: Scarica e Installa Tor</a></h2>
49 
+    <br />
50 
+
51 
+    <p>Prima di iniziare, assicurati che Tor sia installato e funzioni.
52 
+    </p>
53 
+
54 
+    <p>Visita la <a href="<page download/easy-download>">pagina dei download</a> ed
55 
+    installa il "Pacchetto di installazione" per il tuo sistema operativo.
56 
+    </p>
57 
+
58 
+    <p>Per comodit&agrave; potresti usarlo come client per un po', in
59 
+    modo da assicurarti che funzioni correttamente.</p>
60 
+
61 
+    <hr />
62 
+    <a id="setup"></a>
63 
+    <h2><a class="anchor" href="#setup">Fase Due: configura Tor come relay</a></h2>
64 
+    <br />
65 
+
66 
+    <ol>
67 
+    <li> Controlla che l'orologio di sistema ed il fuso orario siano precisi. Se possibile sincronizzalo
68 
+    con un <a href="http://en.wikipedia.org/wiki/Network_Time_Protocol">time server</a> pubbico.
69 
+    </li>
70 
+
71 
+    <li> <strong>Configurare Tor con l'interfaccia grafica Vidalia</strong>:
72 
+    <ol>
73 
+
74 
+    <li>
75 
+           <dt>Fai clic destro sull'icona Vidalia nella barra delle attivit&agrave;. Seleziona <tt>Pannello di controllo</tt>.</dt>
76 
+           <dd><img src="../img/screenshot-win32-vidalia.png"></dd>
77 
+    </li>
78 
+
79 
+    <li>Fai clic su <tt>Avviamento del relaying</tt>.</li>
80 
+    <li>
81 
+    <dt>Scegli <tt>Dona traffico alla rete Tor</tt> Se vuoi essere un
82 
+    relay pubblico (raccomandato), o scegli <tt>Aiuta gli utenti sotto censura a raggiungere
83 
+    la rete Tor</tt> se vuoi fare da <a href="<page	docs/faq>#RelayOrBridge">bridge</a>
84 
+    per gli utenti in paesi che censurano Internet.</dt>
85 
+    <dd><img src="../img/screenshot-win32-configure-relay-1.png"></dd>
86 
+    </li>
87 
+    <li>Scegli un nickname per il tuo relay ed inserisci i tuoi contatti nel
88 
+    caso dobbiamo contattarti per qualche problema.</li>
89 
+    <li>Lascia selezionato <tt>Cerca di configurare automaticamente il port forwarding</tt>.
90 
+    Premi il pulsante <tt>Test</tt> per vedere se tutto funziona. Se funziona, bene.
91 
+    Altrimenti, vedi il numero 3 qui sotto.</li>
92 
+    <li><dt>Seleziona la scheda <tt>Limiti di Banda</tt>. Scegli quanta banda donare agli utenti Tor come te.</dt>
93 
+    <dd><img src="../img/screenshot-win32-configure-relay-2.png"></dd></li>
94 
+    <li><dt>Seleziona la scheda <tt>Policy delle uscite</tt>. Se vuoi permettere agli altri di
95 
+    usare il tuo relay per questi servizi, non cambiare nulla. Deseleziona
96 
+    i servizi <a href="<page docs/faq>#ExitPolicies">che non vuoi che la gente raggiunga dal tuo relay</a>.
97 
+    Se vuoi essere un relay intermedio, deseleziona tutti  servizi.</dt>
98 
+    <dd><img src="../img/screenshot-win32-configure-relay-3.png"></dd></li>
99 
+    <li>Fai clic sul pulsante <tt>Ok</tt>. Vedi il passo 3 qui sotto per controllare che
100 
+    il relay funzioni correttamente.</li>
101 
+    </ol>
102 
+
103 
+    <br />
104 
+
105 
+    <strong>Configurazione Manuale</strong>:
106 
+    <ul>
107 
+    <li>Modifica la parte finale del <a
108 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">file
109 
+    torrc</a>. Se vuoi essere un relay pubblico (raccomandato),
110 
+    definisci la ORPort e <a href="<page
111 
+    docs/faq>#ExitPolicies">dai un'occhiata alla ExitPolicy</a>; altrimenti
112 
+    se vuoi essere un <a href="<page docs/faq>#RelayOrBridge">bridge</a>
113 
+    per gli utenti nei paesi che censurano Internet,
114 
+    usa solo <a href="<page docs/bridges>#RunningABridge">queste righe</a>.
115 
+    </li>
116 
+
117 
+    </ul></li>
118 
+
119 
+    <li>Se usi un firewall, aprilo in modo da permettere alle connessioni
120 
+    in arrivo di raggiungerele porte che hai configurato (ORPort, anche
121 
+    DirPort se l'hai abilitata). Se hai un firewall hardware (Linksys box,
122 
+    cablemodem, etc) potrebbe interessarti <a
123 
+    href="http://portforward.com/">portforward.com</a>. Controlla inoltre che
124 
+    siano consentite anche le connessioni  <em>in uscita</em>, in modo che il tuo
125 
+    relay possa raggiungere gli altri relay Tor.
126 
+    </li>
127 
+
128 
+    <li> Riavvia il relay. Se <a
129 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">segnala
130 
+    dei messaggi di avviso</a>, esaminali.
131 
+
132 
+    </li>
133 
+
134 
+    <li>Iscriviti alla mailing list <a
135 
+    href="http://archives.seul.org/or/announce/">or-announce</a>.
136 
+    Ha un traffico molto basso e serve ad informarsi sulle
137 
+    nuove versioni stabili. Potresti anche iscriverti alle <a
138 
+    href="<page docs/documentation>#MailingLists">liste Tor ad alto traffico</a>.
139 
+    </li>
140 
+
141 
+    </ol>
142 
+
143 
+    <hr />
144 
+    <a id="check"></a>
145 
+    <h2><a class="anchor" href="#check">Fase Tre: controlla che funzioni</a></h2>
146 
+    <br />
147 
+
148 
+    <p>Appena il relay si collega alla rete, cerca
149 
+    di capire se le porte che hai configurato sono raggiungibili dall'
150 
+    esterno. Di solito &egrave; un'operazione rapida, ma potrebbe richiedere
151 
+    fino a 20 minuti. Cerca
152 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">riga del
153 
+    log</a> cos&igrave;
154 
+
155 
+    <tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt>
156 
+    Se non trovi questo messaggio, significa che il tuo relay non &egrave; raggiungibile
157 
+    dall'esterno &mdash; ricontrolla il firewall, controlla che il relay usi
158 
+    l'IP giusto, etc.
159 
+    </p>
160 
+
161 
+    <p>Quando il relay stabilisce di essere raggiungibile, invia un "server
162 
+    descriptor" alle directory per comunicare ai client
163 
+    quale indirizzo, che porta, che chiave, etc usi il tuo server. Puoi <a
164 
+    href="http://moria.seul.org:9032/tor/status/authority">caricare manualmente
165 
+    uno dei network status</a> e
166 
+    scorrerlo per cercare il nickname che hai configurato, per essere certo che
167 
+    sia l&igrave;. Potrebbe volerci qualche secondo per dare il tempo di
168 
+    creare una directory aggiornata.</p>
169 
+
170 
+    <hr />
171 
+    <a id="after"></a>
172 
+    <h2><a class="anchor" href="#after">Fase Quattro: quando funziona</a></h2>
173 
+    <br />
174 
+
175 
+    <p>
176 
+    Raccomandiamo anche le seguenti operazioni:
177 
+    </p>
178 
+
179 
+    <p>
180 
+    6. Leggi
181 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">documentazione sulla sicurezza operativa</a>
182 
+    per sapere come aumentare la sicurezza del tuo relay.
183 
+    </p>
184 
+
185 
+    <p>
186 
+    7. Se vuoi gestire pi&ugrave; di un relay va benissimo, ma per favore definisci <a
187 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">l'opzione
188 
+    MyFamily</a> nei file di configurazione di tutti i tuoi relay.
189 
+    </p>
190 
+
191 
+    <p>
192 
+    8. Decidi se applicare un rate limiting. Le ADSL, i modem via cavo e tutti
193 
+    coloro che hanno banda asimmetrica (es. pi&ugrave; down che up) dovrebbero
194 
+    definire un rate limit alla banda pi&ugrave; lenta, per evitare congestioni. vedi la <a
195 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">rate
196 
+    limiting FAQ </a> per maggiori dettagli.
197 
+    </p>
198 
+
199 
+    <p>
200 
+    9. Fai un backup della chiave privata del tuo relay Tor (&egrave; in "keys/secret_id_key"
201 
+    nella tua DataDirectory). Essa costituisce l'identit&agrave; del tuo relay ed
202 
+    &egrave; importante custodirla al sicuro in modo che nessuno possa leggere il traffico
203 
+    che passa dal tuo relay. Questo &egrave; un file importante da conservare se dovessi <a
204 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeServer">spostare o
205 
+    ripristinare il tuo server Tor</a> in caso di prolemi.
206 
+    </p>
207 
+
208 
+    <p>
209 
+    10. Se controlli il name server del tuo dominio, potresti impostare
210 
+    il reverse DNS hostname a 'anonymous-relay', 'proxy' o 'tor-proxy', in modo che quando
211 
+    altri ne vedranno l'indirizzo nel loro log sar&agrave; pi&ugrave; facile per loro
212 
+    capire di cosa si tratta. E' anche utilissimo aggiungere la <a
213 
+    href="https://tor-svn.freehaven.net/svn/tor/trunk/contrib/tor-exit-notice.html">Tor
214 
+    exit notice</a> su un virtual host configurato per l'hostname, per evitare segnalazioni di abuso
215 
+    a te e al tuo ISP se gestisci un exit node.
216 
+
217 
+    </p>
218 
+
219 
+    <p>
220 
+    11. Se non hai un webserver sul tuo computer, potresti cambiare
221 
+    la ORPort a 443 e la DirPort a 80. Molti utenti Tor
222 
+    si trovano dietro dei firewall che consentono solo di navigare
223 
+    sul web, e in questo modo potranno raggiungere comunque il tuo Tor relay. I relay Win32
224 
+    possono semplicemente cambiare la ORPort e la DirPort
225 
+    nel file torrc e riavviare Tor. I server OS X o Unix non possono
226 
+    collegare direttamente queste porte (perch&eacute; non girano come root), e quindi
227 
+    devono usare un apposito <a
228 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">
229 
+    port forwarding</a> per permettere alle connessioni di raggiungere il Tor relay. Se usi gi&agrave;
230 
+    le porte 80 e 443, ma vuoi aiutare comunque, altre porte
231 
+    molto utili sono la 22, 110, e 143.
232 
+    </p>
233 
+
234 
+    <p>
235 
+    12. Se il tuo relay Tor fornisce altri servizi sul medesimo indirizzo IP
236 
+    &mdash; ad esempio, un webserver &mdash; controlla che sia possibile collegarsi al
237 
+    webserver anche da localhost. &#200; necessario
238 
+    perch&eacute; i client Tor rileveranno che il tuo server &egrave; <a
239 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">il modo
240 
+    pi&ugrave; sicuro per raggiungere il webserver</a>, e creeranno sempre un circuito che termini
241 
+    sul tuo relay Tor. Se non vuoi permettere queste connessioni, devi
242 
+    rifiutarle esplicitamente nella tua exit policy.
243 
+    </p>
244 
+
245 
+    <p>
246 
+    13. (Solo per Unix). Crea un utente separato per il relay. Se hai
247 
+    installato il pacchetto OS X, il deb o l'rpm, &egrave; gi&agrave; cos&igrave;.
248 
+    Altrimenti puoi farlo a mano. (Il relay Tor non ha bisogno di girare
249 
+    come root, anzi &egrave; buona prassi non eseguirlo come root. Girando
250 
+    come utente 'tor' si evitano problemi con identd e altri serviziche
251 
+    rilevano il nome dell'utente. Se sei una persona paranoica, puoi <a
252 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">mettere Tor
253 
+    in un chroot jail</a>.)
254 
+    </p>
255 
+
256 
+    <p>
257 
+    14. (Solo per Unix). Il tuo sistema operativo probabilmente limita il numero
258 
+    dei file descriptor aperti per ogni processo a 1024 (o meno). Se vuoi
259 
+    gestire un exit node veloce, probabilmente non basta. Su
260 
+    Linux, aggiungi una riga come "toruser hard nofile 8192" al file
261 
+    /etc/security/limits.conf (dove toruser &egrave; l'utente del processo
262 
+    Tor), poi riavvia Tor se &egrave; stato installato da pacchetto (o fai un
263 
+    logout e login se lo avvii tu stesso).
264 
+    </p>
265 
+
266 
+    <p>
267 
+    15. Se hai installato Tor da qualche pacchetto o installer, Tor si avvier&agrave;
268 
+    automaticamente al boot del sistema. Se per&ograve; l'hai installato dai sorgenti,
269 
+    potrebbero esserti utili gli initscript in contrib/tor.sh o contrib/torctl.
270 
+    </p>
271 
+
272 
+    <p>
273 
+    Quando modifichi la configurazione di Tor, ricordati di controllare che
274 
+    il tuo relay funzioni regolarmente dopo le modifiche. Completa la voce
275 
+    "ContactInfo" nel file torrc in modo che possiamo contattarti se ci fosse bisogno
276 
+    di aggiornare o ci fossero dei problemi. Se hai problemi o domande, vedi
277 
+    la sezione <a href="<page docs/documentation>#Support">Supporto</a> o la pagina
278 
+    <a href="<page about/contact>">contact us</a> sulla lista tor-ops. Grazie
279 
+    del tuo aiuto per far crescere la rete Tor!
280 
+    </p>
281 
+
282 
+    <hr />
283 
+
284 
+    <p>Se hai suggerimenti per migliorare questo documento, per favore <a
285 
+    href="<page about/contact>">segnalaceli</a>. Grazie!</p>
286 
+  </div>
287 
+  <!-- END MAINCOL -->
288 
+  <div id = "sidecol">
289 
+#include "side.wmi"
290 
+#include "info.wmi"
291 
+  </div>
292 
+  <!-- END SIDECOL -->
293 
+</div>
294 
+<!-- END CONTENT -->
295 
+#include <foot.wmi>
docs/it/tor-doc-server.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,8 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 12076
3 
+# Last-Translator: jan at seul org
4 
+
5 
+#include "head.wmi" TITLE="Redirecting" REDIRECT="docs/tor-doc-relay"
6 
+
7 
+#include <foot.wmi>
8 
+
docs/it/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,189 @@
1 
+    <h1>Usare il client <a href="<page index>">Tor</a> su Linux/BSD/Unix</h1>
2 
+    <br />
3 
+
4 
+    <p>
5 
+    <b>Queste sono le istruzioni per installare e usare un client Tor.
6 
+    Se invece vuoi donare banda e traffico per aiutare a fare crescere
7 
+    la rete Tor (s&igrave; per favore), leggi la guida <a
8 
+    href="<page docs/tor-doc-relay>">Configurare un relay</a>.</b>
9 
+    </p>
10 
+
11 
+    <hr />
12 
+    <a id="installing"></a>
13 
+    <h2><a class="anchor" href="#installing">Uno: scarica e installa Tor</a></h2>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    L'ultima versione di Tor si trova sulla pagina <a
18 
+    href="<page download/download>">scarica</a>. Ci sono anche pacchetti per Debian,
19 
+    Red Hat, Gentoo, *BSD, etc. Se usi
20 
+    Ubuntu, non usare i pacchetti di default: usa invece <a
21 
+    href="<page docs/debian>#ubuntu">il nostro deb repository</a>.
22 
+    </p>
23 
+
24 
+    <p>Se compili dai sorgenti, installa prima <a
25 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a>, e
26 
+    controlla di avere openssl e zlib (inclui i pacchetti -devel se
27 
+    necessario). Poi esegui <br />
28 
+    <tt>tar xzf tor-<version-stable>.tar.gz; cd tor-<version-stable><br />
29 
+    ./configure &amp;&amp; make</tt><br />
30 
+    Ora puoi eseguire tor come <tt>src/or/tor</tt>, oppure puoi eseguire <tt>make install</tt>
31 
+    (come root, se necessario) per installarlo in /usr/local/. Infine, puoi
32 
+    avviare Tor eseguendo <tt>tor</tt>.
33 
+    </p>
34 
+
35 
+    <p>In partenza, Tor &egrave; configurato sempre come client e usa un file di
36 
+    configurazione di default, di cui la maggior parte delle persone non dovr&agrave;
37 
+    modificare i valori. Dopo queste operazioni, Tor &egrave; installato.
38 
+    </p>
39 
+
40 
+    <hr />
41 
+    <a id="privoxy"></a>
42 
+    <a id="polipo"></a>
43 
+    <h2><a class="anchor" href="#polipo">Due: installa Polipo per navigare sul web</a></h2>
44 
+    <br />
45 
+
46 
+    <p>Dopo avere installato Tor, occorre configurare i programmi affinch&eacute; lo usino.
47 
+    </p>
48 
+
49 
+    <p>
50 
+    Per prima cosa va configurata la navigazione web. Inizia installando <a
51 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> dal tuo
52 
+    repository preferito. Polipo &egrave; un caching web proxy che fa anche bene http
53 
+    pipelining, ed &egrave; quindi adatto alla latenza di Tor. Installa come minimo
54 
+    Polipo 1.0.4, perch&eacute; le versioni precedenti non hanno il supporto SOCKS
55 
+    pecessario per usare Polipo con Tor.
56 
+    </p>
57 
+
58 
+    <p>Una volta installato Polipo (da un pacchetto o dai sorgenti),
59 
+    <b>devi configurare Polipo per usare Tor</b>. Usa la nostra <a
60 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/polipo.conf">configurazione Polipo
61 
+    per Tor</a> e mettila al posto dell'attuale file di configurazione
62 
+    di Polipo (es. /etc/polipo/config o ~/.polipo).
63 
+    Devi riavviare Polipo per applicare i cambiamenti.</p>
64 
+
65 
+    <p>Se preferisci puoi usare invece Privoxy con <a
66 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">questa
67 
+    configurazione base di Privoxy</a>. Tuttavia dato che entrambi i file di configurazione usano
68 
+    la porta 8118, non devi far girare Polipo e Privoxy contemporaneamente.</p>
69 
+    </p>
70 
+
71 
+    <hr />
72 
+    <a id="using"></a>
73 
+    <h2><a class="anchor" href="#using">Tre: configura i tuoi programmi per usare Tor</a></h2>
74 
+    <br />
75 
+
76 
+    <p>Dopo aver installato Tor e Polipo, devi configurare i tuoi programmi per
77 
+    usarli. Il primo passo è la configurazione della navigazione web.</p>
78 
+
79 
+    <p>Per una protezione ottimale dovresti usare Tor con Firefox e Torbutton.
80 
+    Installa semplicemente il <a
81 
+    href="https://addons.mozilla.org/firefox/2275/">plugin Torbutton
82 
+    </a> e riavvia Firefox:
83 
+    </p>
84 
+
85 
+    <img alt="Torbutton plugin for Firefox"
86 
+    src="../img/screenshot-torbutton.png"
87 
+    border="1">
88 
+
89 
+    <br />
90 
+
91 
+    <p>
92 
+    Se vuoi usare Firefox su un computer diverso da quello su cui gira Tor, leggi la <a
93 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">
94 
+    FAQ
95 
+    per usare Tor su un pc diverso</a>.
96 
+    </p>
97 
+
98 
+    <p>Per torificare altri programmi che supportino un proxy HTTP, basta
99 
+    farli puntare a Polipo (ovvero, a localhost porta 8118). Per usare SOCKS
100 
+    direttamente (per instant messaging, Jabber, IRC, etc), puoi puntare
101 
+    l'applicazione direttamente a Tor (localhost porta 9050), ma leggi <a
102 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">questa
103 
+    FAQ</a> per capire perch&eacute; ci&ograve; pu&ograve; essere pericoloso. Per i programmi
104 
+    che non supportano n&eacute; SOCKS ne&eacute; HTTP, dai un'occhiata a <a
105 
+    href="http://tsocks.sourceforge.net/">tsocks</a> o a <a
106 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
107 
+    </p>
108 
+
109 
+    <p>Per informazioni su come torificare altre applicazioni, leggi il
110 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
111 
+    HOWTO</a>.
112 
+    </p>
113 
+
114 
+    <hr />
115 
+    <a id="verify"></a>
116 
+    <h2><a class="anchor" href="#verify">Quattro: controlla che tutto funzioni</a></h2>
117 
+    <br />
118 
+
119 
+    <p>
120 
+    Ora prova ad usare il tuo browser con Tor e controlla
121 
+    che il tuo indirizzo IP address venga anonimizzato. Fai clic sul
122 
+    <a href="https://check.torproject.org/">
123 
+    Tor detector</a>
124 
+    e controlla se secondo lui stai usando Tor o no.
125 
+    #<a href="http://ipchicken.com/">iquesto sito</a>
126 
+    #per vedere quale indirizzo IP crede che tu stia usando.
127 
+
128 
+    (Se questo sito non risponde, vedi <a
129 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">questa
130 
+    FAQ</a> per conoscere altri modi di verificare il tuo Tor.)
131 
+    </p>
132 
+
133 
+    <p>Se usi un personal firewall che limita le connessioni del tuo computer
134 
+    verso se stesso (compreso ad esempio SELinux su
135 
+    Fedora Core 4), devi consentire le connessioni dalla
136 
+    tua applicazione locale a Polipo (porta locale 8118) ed a Tor (porta locale
137 
+    9050). Se
138 
+    il tuo firewall blocca le connessioni in uscita, abilita almeno
139 
+    le connessioni alle porte TCP 80 e 443, e poi vedi <a
140 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">questa
141 
+    FAQ</a>.  Se la tua configurazione di SELinux non permette a tor o privoxy di
142 
+    girare correttamente, crea un file di nome booleans.local nella directory
143 
+    /etc/selinux/targeted.  Modifica questo file con un editor di testo e
144 
+    inserisci "allow_ypbind=1".  Riavvia la macchina perch&eacute; questa modifica abbia
145 
+    effetto.
146 
+    </p>
147 
+
148 
+    <p>Se ancora non funziona, leggi <a
149 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">questa
150 
+    FAQ</a> per altre indicazioni.</p>
151 
+
152 
+    <hr />
153 
+    <a id="server"></a>
154 
+    <a id="relay"></a>
155 
+    <h2><a class="anchor" href="#relayr">Cinque: configura Tor come relay</a></h2>
156 
+    <br />
157 
+
158 
+    <p>La rete Tor si fonda sulla banda donata da volontari. Pi&ugrave;
159 
+    persone aprono un relay, pi&ugrave; veloce sar&agrave; la rete Tor. Se hai almeno
160 
+    20 kilobyte/s sia up che down, per favore aiuta la rete Tor e configura
161 
+    il tuo Tor relay. Ci sono molte funzionalit&agrave; che facilitano la gestione
162 
+    di un relay Tor, come la limitazione della banda, exit policy per
163 
+    ridurre il rischio di abusi e lamentele, ed il supporto per indirizzi
164 
+    IP dinamici.</p>
165 
+
166 
+    <p>Con molti relay sparsi in luoghi diversi di Internet gli utenti
167 
+    Tor sono pi&ugrave; sicuri. <a
168 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Puoi
169 
+    anche avere un anonimato pi&ugrave; forte tu stesso</a>,
170 
+    dato che i siti remoti non potranno sapere se le connessioni nascono
171 
+    dal tuo computer o provengono da altrove.</p>
172 
+
173 
+    <p>Puoi approfondire leggendo la nostra guida <a href="<page docs/tor-doc-relay>">Configurare un relay</a>.
174 
+    </p>
175 
+
176 
+    <hr />
177 
+
178 
+    <p>Se hai dei suggerimenti per migliorare questo documento, per favore <a
179 
+    href="<page about/contact>">contattaci</a>. Grazie!</p>
180 
+  </div>
181 
+  <!-- END MAINCOL -->
182 
+  <div id = "sidecol">
183 
+#include "side.wmi"
184 
+#include "info.wmi"
185 
+  </div>
186 
+  <!-- END SIDECOL -->
187 
+</div>
188 
+<!-- END CONTENT -->
189 
+#include <foot.wmi>
docs/it/tor-doc-web.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,65 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Configuring your browser to use Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-web>">Configure Your Browser</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurire il browser per usare <a href="<page index>">Tor</a></h1>
14 
+    <br />
15 
+
16 
+    <p>Se usi Firefox (lo consigliamo), non hai bisogno di questa pagina.
17 
+    Basta installare il<a
18 
+    href="https://addons.mozilla.org/firefox/2275/">plugin Torbutton
19 
+    </a> e riavviare Firefox:
20 
+    </p>
21 
+
22 
+    <img alt="Torbutton plugin for Firefox"
23 
+    src="../img/screenshot-torbutton.png"
24 
+    border="1"/>
25 
+
26 
+    <br />
27 
+
28 
+    <p>Altrimenti devi configurare a mano il proxy del tuo
29 
+    browser.
30 
+    <br/>In Mozilla e Firefox su Windows, vai a
31 
+    Strumenti - Opzioni - Generale - Impostazioni Connessione.
32 
+    <br/>In Firefox su OS X, &egrave; Firefox - Preferenze - Generale - Impostazini Connessione.
33 
+    <br/>In Firefox su Linux, si trova in
34 
+    Modifica - Preferenze - Avanzate - Proxies.
35 
+    <br/>In Opera &egrave; Strumenti - Preferenze(Avanzate) - Rete - Proxy servers.
36 
+    <br/>Noi sconsigliamo di usare IE, ma se qualcuno vuole comunque un anonimato inferiore,
37 
+    &egrave; Strumenti - Opzioni Internet - Connessioni - Impostazioni LAN - Proxy
38 
+    Server - Avanzate.</p>
39 
+
40 
+    <img alt="Proxy settings in Firefox"
41 
+    src="../img/screenshot-win32-firefox-proxies.jpg" />
42 
+
43 
+    <p>
44 
+    Devi scrivere "localhost"
45 
+    e "8118" per puntare i primi 4 protocolli a Privoxy, come mostrato qui. (Anche
46 
+    se Privoxy non supporta FTP e Gopher, <a
47 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">devi
48 
+    configurarlo lo stesso</a>.) Devi anche compilare il socks
49 
+    proxy perch&eacute; punti direttamente a Tor ("localhost", "9050", e socks5)
50 
+    per coprire gli altri protocolli dopo i primi 4. Poi fai clic su "OK".</p>
51 
+
52 
+    <hr />
53 
+
54 
+    <p>Se hai proposte per migliorare questo documento, per favore <a
55 
+    href="<page about/contact>">scrivicele</a>. Grazie!</p>
56 
+  </div>
57 
+  <!-- END MAINCOL -->
58 
+  <div id = "sidecol">
59 
+#include "side.wmi"
60 
+#include "info.wmi"
61 
+  </div>
62 
+  <!-- END SIDECOL -->
63 
+</div>
64 
+<!-- END CONTENT -->
65 
+#include <foot.wmi>
docs/it/tor-doc-win32.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,6 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 13195
3 
+# Last-Translator: jan at seul . org
4 
+# Status: obsolete
5 
+
6 
+#include "head.wmi" TITLE="Redirecting" REDIRECT="docs/tor-doc-windows"
docs/it/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,177 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Usare il client <a href="<page index>">Tor</a> su Microsoft Windows</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Queste sono le istruzioni per installare e usare un client Tor
18 
+    su Microsoft Windows (versioni 2000, XP, Vista, 7, Server).
19 
+    Se invece vuoi offrire banda e traffico per aiutare a fare crescere la rete Tor (s&igrave;,
20 
+    per favore!), leggi la guida per <a href="<page docs/tor-doc-relay>">Configurare un relay</a>.
21 
+    </b>
22 
+    </p>
23 
+
24 
+    <hr />
25 
+    <a id="installing"></a>
26 
+    <h2><a class="anchor" href="#installing">Uno: scarica e installa Tor</a></h2>
27 
+    <br />
28 
+
29 
+    <p>
30 
+    Il pacchetto per Microsoft Windows comprende <a href="<page index>">Tor</a>,
31 
+    <a href="<page projects/vidalia>">Vidalia</a> (una interfaccia grafica per Tor), Torbutton (un
32 
+    plugin per Mozilla Firefox), e <a
33 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (un web proxy) in
34 
+    un pacchetto unico contenente le 4 applicazioni preconfigurate.
35 
+    Scarica la versione <a href="../<package-win32-bundle-stable>">stabile</a>
36 
+    o quella <a href="../<package-win32-bundle-alpha>">sperimentale</a>
37 
+    del pacchetto Windows, oppure scegli altre opzioni dalla
38 
+    <a href="<page download/download>">pagina di download</a>.
39 
+    </p>
40 
+
41 
+    <img alt="tor installer splash page" src="../img/screenshot-win32-installer-splash.png" />
42 
+
43 
+    <p>Se avevi gi&agrave; installato in precedenza Tor, Vidalia, o Polipo
44 
+    puoi deselezionare i componenti di cui non hai bisogno
45 
+    nella finestra di dialogo qui sotto.
46 
+    </p>
47 
+
48 
+    <img alt="select components to install" src="../img/screenshot-win32-installer-components.png" />
49 
+
50 
+    <p>Dopo aver terminato l'installazione, i componenti
51 
+    che hai scelto verranno avviati automaticamente.
52 
+    </p>
53 
+
54 
+    <p>Di default Tor &egrave; configurato come client. Usa un file di configurazione
55 
+    predefinito che la maggior parte degli utenti non avr&agrave; bisogno
56 
+    di modificare. Ora Tor &egrave; installato.
57 
+    </p>
58 
+
59 
+    <hr />
60 
+    <a id="using"></a>
61 
+    <h2><a class="anchor" href="#using">Due: configura i tuoi programmi per usare Tor</a></h2>
62 
+    <br />
63 
+
64 
+    <p>Dopo l'installazione di Tor e di Polipo, devi configurare i tuoi programmi affinch&eacute;
65 
+    li usino. Il primo passo &egrave; configurare il browser web.</p>
66 
+
67 
+    <p>Per una sicurezza ottimale dovresti usare Tor con Firefox e Torbutton. Il
68 
+    pacchetto installa
69 
+    il <a href="https://addons.mozilla.org/firefox/2275/">plugin Torbutton
70 
+    </a> e basta poi riavviare Firefox:
71 
+    </p>
72 
+
73 
+    <img alt="Torbutton plugin for Firefox" src="../img/screenshot-torbutton.png" border="1"/>
74 
+
75 
+    <br />
76 
+
77 
+    <p>
78 
+    Se vuoi usare Firefox su un computer diverso da dove gira To, leggi la <a
79 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">FAQ
80 
+    per usare Tor su un pc differente</a>.
81 
+    </p>
82 
+
83 
+    <p>Per usare Tor con altre applicazioni che supportano un HTTP proxy, basta
84 
+    puntarle a Polipo (ossia, a localhost porta 8118). Per usare SOCKS
85 
+    direttamente (con l'instant messaging, Jabber, IRC, etc), si pu&ograve; puntare
86 
+    il programma direttamente a Tor (localhost porta 9050), ma leggi <a
87 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">questa
88 
+    FAQ</a> che spiega perch&eacute; &egrave; pericoloso. Per quei programmi
89 
+    che non supportano n&eacute; SOCKS n&eacute; HTTP, vedi SocksCap o
90 
+    <a href="http://www.freecap.ru/eng/">FreeCap</a>.
91 
+    (FreeCap &egrave; software libero; SocksCap &egrave; proprietario.)</p>
92 
+
93 
+    <p>Per informazioni su come Torificare altri programmi, guarda il
94 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
95 
+    HOWTO</a>.
96 
+    </p>
97 
+
98 
+    <hr />
99 
+    <a id="verify"></a>
100 
+    <h2><a class="anchor" href="#verify">Tre: controlla che tutto funzioni</a></h2>
101 
+    <br />
102 
+
103 
+    <p>
104 
+    Controlla che Vidalia sia attivo.  Vidalia usa una piccola cipolla verde
105 
+    per indicare che Tor &egrave; attivo, ed una cipolla scura con una "X" rossa
106 
+    quando Tor &egrave; spento. Puoi avviare o fermare Tor facendo clic col tasto destro del mouse
107 
+    sulla icona di Vidalia nella barra di sistema e selezionando "Start" o "Stop"
108 
+    dal menu come mostrato qui sotto:
109 
+    </p>
110 
+
111 
+    <img alt="Vidalia Tray Icon" src="../img/screenshot-win32-vidalia.png"/>
112 
+
113 
+    <p>
114 
+    Ora devi provare Tor col tuo browser per controllare
115 
+    che il tuo indirizzo IP sia anonimizzato. Fai clic sul
116 
+    <a href="https://check.torproject.org/">
117 
+    Tor detector</a> e verifica se stai usando o meno Tor
118 
+    (se questo sito &egrave; gi&ugrave;, vedi <a
119 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">questa
120 
+    FAQ</a> per altri modi di testare il tuo client Tor).
121 
+    </p>
122 
+
123 
+    <p>Se hai un personal firewall che limita le connessioni del tuo pc
124 
+    verso se stesso, controlla che siano permesse le connessioni dalle
125 
+    applicazioni locali alla porta locale 8118 e alla porta 9050. Se
126 
+    il tuo firewall blocca le connessioni in uscita, permettigli di
127 
+    collegarsi almeno alle porte TCP 80 e 443, poi leggi <a
128 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">questa
129 
+    FAQ</a>.
130 
+    </p>
131 
+
132 
+    <p>Se nemmeno ora funziona, guarda <a
133 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">questa
134 
+    FAQ</a> per ulteriori indicazioni.</p>
135 
+
136 
+    <p>
137 
+    Una volta che tutto funziona, leggi meglio
138 
+    <a href="<page download/download>#Warning">quello che Tor fa e quello che non fa</a>.
139 
+    </p>
140 
+
141 
+    <hr />
142 
+    <a id="server"></a>
143 
+    <h2><a class="anchor" href="#relay">Quattro: configura Tor come relay</a></h2>
144 
+    <br />
145 
+
146 
+    <p>La rete Tor funziona grazie alla banda donata dai volontari. Pi&ugrave;
147 
+    persone aprono un relay, pi&ugrave; veloce sar&agrave; la rete Tor. Se hai almeno
148 
+    20 kilobyte/s in download e upload, aiutaci e configura la tua installazione
149 
+    Tor come relay. Ci sono tante funzionalit&agrave; che rendono un Tor relay facile
150 
+    e pratico, come il controllo della banda, exit policy per
151 
+    limitare il rischio di abusi e lamentele, ed il supporto per indirizzi
152 
+    IP dinamici.</p>
153 
+
154 
+    <p>La distribuzione di relay in tanti luoghi diversi della rete
155 
+    rende pi&ugrave; sicuri gli utenti di Tor. <a
156 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Puoi
157 
+    ottenere un migliore anonimato tu stesso</a>,
158 
+    dato che non sar&agrave; possibile sapere se una connessione &egrave; partita dal tuo
159 
+    computer o &egrave; stata trasportata da un altro nodo Tor.</p>
160 
+
161 
+    <p>Leggi la guida su <a href="<page docs/tor-doc-relay>">come configurare un relay</a>
162 
+    .</p>
163 
+
164 
+    <hr />
165 
+
166 
+    <p>Se hai delle proposte per migliorare questo documento, per favore <a
167 
+    href="<page about/contact>">contattaci</a>. Grazie!</p>
168 
+  </div>
169 
+  <!-- END MAINCOL -->
170 
+  <div id = "sidecol">
171 
+#include "side.wmi"
172 
+#include "info.wmi"
173 
+  </div>
174 
+  <!-- END SIDECOL -->
175 
+</div>
176 
+<!-- END CONTENT -->
177 
+#include <foot.wmi>
docs/it/tor-hidden-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,278 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22314 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Configurare i servizi nascosti (Hidden Service) per <a href="<page index>">Tor</a></h1>
14 
+    <hr />
15 
+
16 
+    <p>Tor permette a client e relay di offrire dei "servizi nascosti" (hidden service). In altre parole,
17 
+    puoi realizzare un server web, un server SSH, etc., senza rivelare il tuo
18 
+    indirizzo IP agli altri utenti. Di fatto, non usando un indirizzo IP pubblico,
19 
+    puoi avere un hidden service anche da dietro un firewall.
20 
+    </p>
21 
+
22 
+    <p>Se hai installato Tor e Privoxy, puoi vedere dei servizi nascoi
23 
+    dal vivo visitando <a href="http://duskgytldkxiuqc6.onion/">il nostro
24 
+    hidden service dimostrativo</a> od il <a
25 
+    href="http://gaddbiwdftapglkq.onion/">hidden service di Wikileaks</a>.
26 
+    </p>
27 
+
28 
+    <p>Questa guida spiega come realizzare il proprio sito web come hidden
29 
+    service. Per i dettagli tecnici sul funzionamento del protocollo hidden service,
30 
+    vedi la nostra pagina <a href="<page docs/hidden-services>">il protocollo hidden service</a>.
31 
+    </p>
32 
+
33 
+    <hr />
34 
+    <a id="zero"></a>
35 
+    <h2><a class="anchor" href="#zero">Zero: installa Tor e Privoxy</a></h2>
36 
+    <br />
37 
+
38 
+    <p>Prima di iniziare occorre che:</p>
39 
+    <ol>
40 
+    <li>Tor sia attivo e funzioni correttamente,</li>
41 
+    <li>Privoxy sia attivo e funzioni,</li>
42 
+    <li>Privoxy sia configurato per puntare a Tor e che</li>
43 
+    <li>l'installazione sia corretta e funzionante.</li>
44 
+    </ol>
45 
+
46 
+    <p>Gli utenti Windows possono seguire il <a
47 
+    href="<page docs/tor-doc-windows>">Windows
48 
+    howto</a>, gli utenti OS X possono seguire il <a
49 
+    href="<page docs/tor-doc-osx>">OS
50 
+    X howto</a>, e infine gli utenti Linux/BSD/Unix possono seguire lo <a
51 
+    href="<page docs/tor-doc-unix>">Unix howto</a>.
52 
+    </p>
53 
+
54 
+    <p>Una volta installati e configurati Tor e Privoxy,
55 
+    puoi vedere i hidden service dal vivo seguendo questo link al <a
56 
+    <a href="http://duskgytldkxiuqc6.onion/"> nostro
57 
+    hidden service dimostrativo</a> od al <a
58 
+    href="http://gaddbiwdftapglkq.onion/">hidden service di Wikileaks</a>.
59 
+    Ci impieger&agrave; di solito 10-60 secondi a caricare
60 
+    (o a decidere che non &egrave; raggiungibile al momento). Se d&agrave; un errore
61 
+    subito e il tuo browser mostra un messaggio che dice
62 
+    "Impossibile trovare www.duskgytldkxiuqc6.onion , controlla l'indirizzo
63 
+    e riprova", significa che Tor e Privoxy non sono configurati correttamente; leggi <a
64 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">questa
65 
+    FAQ</a> per aiuto e suggerimenti.
66 
+    </p>
67 
+
68 
+    <hr />
69 
+    <a id="one"></a>
70 
+    <h2><a class="anchor" href="#one">Uno: installa localmente un web server</a></h2>
71 
+    <br />
72 
+
73 
+    <p>Per prima cosa devi installare un web server in locale. Pu&ograve;
74 
+    essere una cosa delicata,
75 
+    per cui qui descriveremo solo alcuni passaggi elementari.Se ti trovi in difficolt&agrave;
76 
+    o se vuoi fare di pi&ugrave; cerca un amico che ti aiuti. Ti consigliamo di
77 
+    di installare un web server separato per il tuo hidden service, dato che
78 
+    se ne hai gi&agrave; uno installato forse lo stai gi&agrave; usando (o vorrai
79 
+    usarlo in futuro) per un altro sito web.
80 
+
81 
+    </p>
82 
+
83 
+    <p>Se usi Unix o OS X e sei a tuo agio con la linea di
84 
+    comando, la cosa migliore &egrave; installare <a
85 
+    href="http://www.acme.com/software/thttpd/">thttpd</a>. Piglia la tarball
86 
+    pi&ugrave; recente, scompattala (creer&agrave; la sua directory), ed esegui
87 
+    <kbd>./configure &amp;&amp; make</kbd>. Poi <kbd>mkdir hidserv; cd
88 
+    hidserv</kbd>, ed esegui
89 
+    <kbd>../thttpd -p 5222 -h localhost</kbd>. Ti restituir&agrave; il prompt
90 
+    e avrai un webserver sulla porta 5222. Puoi mettere dei file
91 
+    nella directory hidserv.
92 
+    </p>
93 
+
94 
+    <p>Su Windows, puoi usare <a
95 
+    href="http://savant.sourceforge.net/">Savant</a> o <a
96 
+    href="http://httpd.apache.org/">Apache</a>, e configurarlo per collegarsi
97 
+    solo da localhost. Devi anche sapere su quale porta &egrave; in
98 
+    ascolto, dato che servir&agrave; pi&ugrave; sotto.
99 
+    </p>
100 
+
101 
+    <p>(Il motivo per collegare il web server solo a localhost &egrave; per
102 
+    assicurarsi che non sia accessibile pubblicamente. Se si potesse accedere direttamente,
103 
+    si potrebbe avere la prova che &egrave; il tuo computer a offire l'hidden
104 
+    service.)
105 
+    </p>
106 
+
107 
+    <p>Una volta installato il web server, controlla che funzioni: apri un browser
108 
+    e vai a <a
109 
+    href="http://localhost:5222/">http://localhost:5222/</a>, dove 5222 &egrave;
110 
+    la porta scelta poco pi&ugrave; sopra. Prova poi a mettere unfile nella directory
111 
+    html principale e controlla che sia visibile quando accedi al sito.
112 
+    </p>
113 
+
114 
+    <hr />
115 
+    <a id="two"></a>
116 
+    <h2><a class="anchor" href="#two">Due: Configura il tuo hidden service</a></h2>
117 
+    <br />
118 
+
119 
+    <p>Ora devi configurare l'hidden service perch&eacute; punti al
120 
+    web server locale
121 
+    </p>
122 
+
123 
+    <p>Per prima cosa, apri il file torrc con un editor di testo. (Vedi <a
124 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">la
125 
+    torrc FAQ</a> per maggiori informazioni.) Vai alla sezione di mezzo e
126 
+    cerca la riga</p>
127 
+
128 
+    <pre>
129 
+    \############### This section is just for location-hidden services ###
130 
+    </pre>
131 
+
132 
+    <p>
133 
+    Questa sezione del file contiene un gruppo di righe che rappresentano ciascuna
134 
+    un hidden service. Per ora sono tutte commentate via (le linee
135 
+    iniziano con #), infatti i hidden service sono disabilitati. Ogni gruppo di righe
136 
+    consiste in una riga <var>HiddenServiceDir</var> e una o pi&ugrave;
137 
+    righe <var> HiddenServicePort</var>:</p>
138 
+
139 
+    <ul>
140 
+    <li><var>HiddenServiceDir</var> &egrave; una directory dove Tor metter&agrave; le informazioni
141 
+    su quel hidden service.  In particolare Tor vi creer&agrave; un file di nome
142 
+    <var>hostname</var> che indica l'onion URL.  Non occorre aggiungere
143 
+    altri file a questa directory.</li>
144 
+    <li><var>HiddenServicePort</var> permette di specificare una porta virtuale (ovvero, la porta
145 
+    che chi accede al servizio creder&agrave; di usare), e un
146 
+    indirizzo IP e una porta per redirigere le connessioni verso questa porta virtuale.</li>
147 
+    </ul>
148 
+
149 
+    <p>Aggiungi le seguenti righe a torrc:
150 
+    </p>
151 
+
152 
+    <pre>
153 
+    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
154 
+    HiddenServicePort 80 127.0.0.1:5222
155 
+    </pre>
156 
+
157 
+    <p>Sar&agrave; necessario modificare la riga <var>HiddenServiceDir</var> in modo che punti
158 
+    a una directory vera che sia leggibile e scrivibile dall'utente con cui
159 
+    gira Tor. L'esempio sopra dovrebbe funzionare con il pacchetto Tor
160 
+    per OS X. In Unix, prova "/home/nomeutente/hidserv/" e metti il tuo nome
161 
+    utente al posto di "nomeutente". Su Windows puoi provare:</p>
162 
+    <pre>
163 
+    HiddenServiceDir C:\Documents and Settings\nomeutente\Dati applicazioni\hidden_service\\
164 
+    HiddenServicePort 80 127.0.0.1:5222
165 
+    </pre>
166 
+
167 
+    <p>Ora salva il file torrc, chiudi
168 
+    Tor e riavvialo.
169 
+    </p>
170 
+
171 
+    <p>Se Tor riparte, bene. Altrimenti c'&egrave; qualcosa che non va. Per prima cosa dai
172 
+    un'occhiata ai file di log, che riportano avvisi o messaggi di errore. Ci&ograve;
173 
+    dovrebbe darti indicazioni sui problemi incontrati. Spesso ci sono errori di battitura nel file torrc
174 
+    o permessi di directory errati. (Vedi la <a
175 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">logging
176 
+    FAQ</a> se non sai come abilitare o trovare
177 
+    i file di log.)
178 
+
179 
+    </p>
180 
+
181 
+    <p>Quando Tor parte creer&agrave; automaticamente la  <var>HiddenServiceDir </var>
182 
+    che hai indicato (se serve), e vi creer&agrave; due file.</p>
183 
+    <dl>
184 
+    <dt><var>private_key</var></dt>
185 
+    <dd>Anzitutto Tor creer&agrave; un nuovo paio di chiavi pubblica/privata per il tuo hidden
186 
+    service. Esso viene scritto in un file detto "private_key". Non condividere questa chiave
187 
+    co altri -- altrimenti un altro otrebbe impersonare il tuo hidden
188 
+    service.</dd>
189 
+    <dt><var>hostname</var></dt>
190 
+    <dd>L'altro file creato da Tor &egrave; detto "hostname". Esso contiene
191 
+    un breve sommario della tua chiave pubblica -- qualcosa di smile a
192 
+    <tt>duskgytldkxiuqc6.onion</tt>. &#200; il nome pubblico del tuo servizio
193 
+    e puoi comunicarlo a tutti, pubblicarlo su siti web, scriverlo sul biglietto
194 
+    da visita, etc. .</dd>
195 
+    </dl>
196 
+
197 
+    <p>Se Tor gira con un diverso utente, ad esempio su
198 
+    OS X, Debian, o Red Hat, forse devi diventare root per leggere
199 
+    questi file.</p>
200 
+
201 
+    <p>Ora che hai riavviato Tor, lui cerca degli introduction point
202 
+    nella rete Tor, generando un cosiddetto <em>hidden service
203 
+    descriptor</em>. Esso &egrave; una lista firmata di introduction point e della chiave
204 
+    pubblica del servizio. Tor pubblica anonimamente questa descrizione
205 
+    ai directory server, cos&igrave; gli altri possono prelevarla anonimamente dai
206 
+    directory server quando cercano di accedere al tuo servizio.
207 
+    </p>
208 
+
209 
+    <p>Ora fai una prova: copia e incolla il contenuto del file hostname nel tuo
210 
+    browser. Se funziona vedrai la pagina html che hai preparato al punto uno.
211 
+    Se non funziona, guarda nei log e fai altre prove e modifiche finch&eacute; non
212 
+    funziona.
213 
+    </p>
214 
+
215 
+    <hr />
216 
+    <a id="three"></a>
217 
+    <h2><a class="anchor" href="#three">Tre: argomenti avanzati</a></h2>
218 
+    <br />
219 
+
220 
+    <p>Se pensi di rendere disponibile a lungo il tuo servizio, dovresti fare
221 
+    una copia di backup del file <var>private_key</var>.
222 
+    </p>
223 
+
224 
+    <p>Nell'esempio sopra abbiamo evitato di proposito Apache, a) perch&eacute; molti
225 
+    potrebbero gi&agrave; usarlo per un server web pubblico sul loro computer, e b)
226 
+    perch&eacute; &egrave; una grande applicazione
227 
+    che ha molti posti in cui potrebbe rivelare il tuo vero indirizzo IP o altre
228 
+    informazioni atte a identificarti, ad esempio nelle pagine 404. Per chi avesse bisogno
229 
+    di pi&ugrave; funzionalit&agrave;, Apache potrebbe essere la soluzione giusta. Puoi
230 
+    scrivere una lista di azioni per blindare Apache quando lo si usa come
231 
+    hidden service? Anche Savant probabilmente ha problemi del genere.
232 
+    </p>
233 
+
234 
+    <p>Se vuoi inoltrare pi&ugrave; porte virtuali a un unico hidden
235 
+    service, basta aggiungere altre righe <var>HiddenServicePort</var>.
236 
+    Se vuoi gestire pi&ugrave; hidden services dallo stesso client Tor,
237 
+    aggiungi un'altra riga <var>HiddenServiceDir</var>. Tutte le seguenti righe
238 
+    <var>HiddenServicePort</var> si riferiscono a questa riga <var>HiddenServiceDir</var>, fino
239 
+    a quando non aggiungi un'altra riga <var>HiddenServiceDir</var>:
240 
+    </p>
241 
+
242 
+    <pre>
243 
+    HiddenServiceDir /usr/local/etc/tor/hidden_service/
244 
+    HiddenServicePort 80 127.0.0.1:8080
245 
+
246 
+    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
247 
+    HiddenServicePort 6667 127.0.0.1:6667
248 
+    HiddenServicePort 22 127.0.0.1:22
249 
+    </pre>
250 
+
251 
+    <p>Alcuni problemi di anonimato da tenere a mente:
252 
+    </p>
253 
+    <ul>
254 
+    <li>Come detto sopra, fai attenzione che il server web non riveli
255 
+    informazioni che possano identificare te, il tuo computer, la tua posizione.
256 
+    Ad esempio, un visitatore potr&agrave; probabilmente capire se si tratta di thttpd o
257 
+    di Apache e che sistema operativo usi.</li>
258 
+    <li>Se il tuo computer non &egrave; sempre online, non lo sar&agrave; nemmeno il tuo
259 
+    hidden service. Questo rivela informazioni all'osservazione di un avversario.</li>
260 
+    <!-- increased risks over time -->
261 
+    </ul>
262 
+
263 
+
264 
+
265 
+    <hr />
266 
+
267 
+    <p>se hai suggerimenti per migliorare questo documento, per favore <a
268 
+    href="<page about/contact>">scrivici</a>. Grazie!</p>
269 
+  </div>
270 
+  <!-- END MAINCOL -->
271 
+  <div id = "sidecol">
272 
+#include "side.wmi"
273 
+#include "info.wmi"
274 
+  </div>
275 
+  <!-- END SIDECOL -->
276 
+</div>
277 
+<!-- END CONTENT -->
278 
+#include <foot.wmi>
docs/ko/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/ko/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,269 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>맥 OS X에서<a href="<page index>">Tor</a> 클라이언트 운영하기</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>이 문서는 맥 OS X에서 Tor 클라이언트 운영을 위한 설치 매뉴얼입니다.
18 
+    만약 다른 이용자들에게 중계 트래픽을 제공해서
19 
+    Tor 네트워크가 더 커지도록 돕고싶다면(꼭 해주세요),
20 
+    <a href="<page docs/tor-doc-relay>">중계서버 설정하기</a>를 읽어주세요.</b>
21 
+    </p>
22 
+
23 
+    <hr />
24 
+    <a id="installing"></a>
25 
+    <h2><a class="anchor" href="#installing">1단계: Tor 다운받아 설치하기</a></h2>
26 
+    <br />
27 
+
28 
+    <p>
29 
+    매킨토시 OS X 통합배포판은<a href="<page index>">Tor</a>,
30 
+    <a href="http://www.vidalia-project.net/">Vidalia</a> (Tor GUI),
31 
+    <a href="http://www.privoxy.org/">Privoxy</a> (필터링 웹 프록시)
32 
+    를 포함하고 있습니다. 그리고 이것들은 함께 작동하도록 설정되어 있습니다.
33 
+    <a href="../<package-osx-bundle-stable>">안정화된 버전</a>이나
34 
+    <a href="../<package-osx-bundle-alpha>">개발 버전</a>
35 
+    중 하나를 다운받을 수도 있고,<a href="<page
36 
+    download/download>">다운로드 페이지</a>에 가서 다른 버전들을 찾아볼 수도 있습니다.
37 
+    </p>
38 
+
39 
+    <p>Tor 인스톨러 사용은 아주 간단합니다. 아래는 셋업 페이지를 캡쳐한 모습입니다:
40 
+    </p>
41 
+
42 
+    <p><img alt="tor installer splash page"
43 
+    src="../img/screenshot-osx-installer-splash.png"
44 
+    border="1"></p>
45 
+
46 
+    <p>설치가 끝나면, Applications 폴더에서 Vidalia 아이콘을 선택해서 그것을 실행시킬 수 있습니다.
47 
+    빨간색 "X"가 새겨진 어두운 양파가 dock에 보인다면, Tor가 실행되지 않고 있는 것입니다.
48 
+    화면 위에 있는 Tor 메뉴에서 Start를 선택해서 Tor를 실행시킬 수 있습니다.
49 
+    </p>
50 
+
51 
+    <p>Tor가 실행 중일 때는 dock에 있는 Vidalia의 아이콘이 아래와 같이 보일 것입니다:
52 
+    </p>
53 
+
54 
+    <p><img alt="vidalia running tor"
55 
+    src="../img/screenshot-osx-vidalia.png"
56 
+    border="1"></p>
57 
+
58 
+    <p>Privoxy는 Tor 통합배포판에 포함되어 설치되어 있습니다. 일단 설치가 되고 나면, Privoxy는
59 
+    컴퓨터가 다시 시작할 때 자동으로 실행됩니다.
60 
+    Privoxy가 Tor를 사용하도록 설정할 필요는 없습니다 &mdash; Tor 사용을 위한 Privoxy 설정은
61 
+    이미 되어 있는 상태입니다.
62 
+    </p>
63 
+
64 
+    <hr />
65 
+    <a id="using"></a>
66 
+    <h2><a class="anchor" href="#using">2단계: 당신의 프로그램이 Tor를 사용하도록 설정하기</a></h2>
67 
+    <br />
68 
+
69 
+    <p>Tor와 Privoxy를 설치한 후에, 당신이 운영중인 프로그램들이 Tor를 사용하도록 설정해야 합니다.
70 
+    가장 먼저 할 일은 웹브라우저 설정을 변경하는 것입니다.</p>
71 
+
72 
+    <p>
73 
+    만약에 당신이 파이어폭스를 사용중이라면(파이어폭스를 권장합니다), Vidalia 통합배포판이
74 
+    <a href="https://addons.mozilla.org/firefox/2275/">Torbutton
75 
+    플러그인</a>을 자동으로 설치할 것입니다.
76 
+    설치 후 파이어폭스를 다시 시작하면, 모든 설정이 끝난 것입니다:
77 
+    </p>
78 
+
79 
+    <p><img alt="Torbutton plugin for Firefox"
80 
+    src="../img/screenshot-torbutton.png"
81 
+    border="1"></p>
82 
+
83 
+    <p>
84 
+    (<a href="https://torbutton.torproject.org/">Torbutton에 대해 더 알고 싶으면 여기를 클릭하세요</a>.
85 
+    만약에 다른 컴퓨터에서도 파이어폭스와 Tor를 사용할 계획이라면, 다음의
86 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">
87 
+    FAQ</a>를 참고하세요.
88 
+    만약에 파이어폭스가 아닌 다른 브라우저를 사용해야 한다면,
89 
+    <a href="<page docs/tor-doc-web>">프록시 설정을 직접 해줘야 합니다</a>.)
90 
+    </p>
91 
+
92 
+
93 
+    <h3>애플 사파리</h3>
94 
+
95 
+    <p>
96 
+    사파리에서 Tor를 사용하려면 네트워크 설정을 변경해줘야 합니다.
97 
+    아래 그림에 보이는 것처럼 Apple - Location - Network Preference를 선택합니다.</p>
98 
+
99 
+    <p><img alt="Network settings"
100 
+    src="../img/screenshot-osx-choose-network.png"
101 
+    border="1"></p>
102 
+
103 
+    <p>Network Interface를 선택한 후, Tor를 사용하도록 프록시 설정을 변경해줘야 합니다.
104 
+    만약에 다수의 인터페이스에서 Tor를 사용하고 싶다면 각각의 설정을 모두 변경해줘야 합니다.</p>
105 
+
106 
+    <p><img alt="Network preferences"
107 
+    src="../img/screenshot-osx-choose-interface.png"
108 
+    border="1"></p>
109 
+
110 
+    <p>웹 프록시(HTTP)와 HTTPS 모두에 127.0.0.1과 포트번호 8118을 입력하세요.
111 
+    FTP 프록시와 Gopher 프록시의 설정도 위와 같이 변경해줘야 합니다;
112 
+    Tor와 FTP 프록시들에 대해 더 알고 싶다면<a
113 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy"> 이 노트</a>
114 
+    를 참고하세요. Passive FTP 모드 (PASV)는 원래 있던대로 놔두면 됩니다.</p>
115 
+
116 
+    <p><img alt="Proxy settings"
117 
+    src="../img/screenshot-osx-proxy-settings.png"
118 
+    border="1"></p>
119 
+
120 
+    <p>Privoxy를 사용하는 것은 <strong>필수입니다</strong>. 왜냐하면 <a
121 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">브라우저들은
122 
+    SOCKS 프록시를 직접 운영하면서 당신이 보내는 DNS 요청을 곳곳에 흘리기 때문입니다</a>.
123 
+    이것은 당신의 익명성에 안 좋은 영향을 줍니다. 또 Privoxy는 당신의 통신요청에서
124 
+    위험한 헤더들을 제거하고, Doubleclick같은 불쾌한 광고사이트를 차단해주는 일도 합니다.</p>
125 
+
126 
+
127 
+    <p>HTTP 프록시를 사용하는 다른 프로그램에서도 Tor를 사용하려면,
128 
+    그들이 Privoxy를 가르키도록 설정하면 됩니다(즉, localhost 포트 8118로 연결).
129 
+    SOCKS를 직접 연결해서 사용하려면(메신저, Jabber, IRC 등), 당신의 프로그램이
130 
+    Tor를 가르키도록 직접 설정할 수 있습니다(localhost 포트 9050),
131 
+    그러나 이것이 왜 위험한지 알기 위해서 다음의<a
132 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">
133 
+    FAQ</a>를 한 번 볼 필요가 있습니다. SOCKS나 HTTP가 사용불가능한 프로그램을 위해선
134 
+    <a href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a>나
135 
+    <a href="http://www.dest-unreach.org/socat/">socat</a>를 참고하세요.</p>
136 
+
137 
+
138 
+
139 
+
140 
+    <p>이밖에 다른 프로그램들에서 어떻게 Tor를 사용할 수 있는지에 대한 정보가 필요하다면,
141 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
142 
+    HOWTO</a>를 참고하세요.
143 
+    </p>
144 
+
145 
+
146 
+    <hr />
147 
+    <a id="verify"></a>
148 
+    <h2><a class="anchor" href="#verify">3단계: 제대로 작동하는지 확인하기</a></h2>
149 
+    <br />
150 
+
151 
+    <p>
152 
+    다음으로, Tor를 사용하도록 설정된 브라우저를 통해 통신을 할 때
153 
+    IP주소가 제대로 익명화되고 있는지 확인해야 합니다.
154 
+    <a href="https://check.torproject.org/">Tor 확인기</a>를 클릭한 후
155 
+    당신이 Tor를 사용하고 있는지 아닌지 결과를 확인하세요.
156 
+    #<a href="http://ipchicken.com/">이 사이트</a>
157 
+    #에서는 당신이 사용하고 있다고 생각되는 IP주소를 알려줍니다.
158 
+    (만약 이 사이트가 안 열린다면, Tor를 테스트할 수 있는 다른 방법들이 나와있는 다음의<a
159 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">
160 
+    FAQ</a>를 확인하세요.)
161 
+    </p>
162 
+
163 
+
164 
+    <p>만약에 접속제한을 하는 개인 파이어월을 사용 중이라면,
165 
+    당신이 사용하는 프로그램들이 당신 컴퓨터의 8118 포트와 9050 포트에 접근을
166 
+    할 수 있도록 되어있는지 확인해야 합니다. 만약에 파이어월이
167 
+    밖으로 나가는 연결을 차단한다면, 최소한 TCP 포트 80번과 443번은
168 
+    연결이 되도록 허용해야 합니다. 그리고나서 다음의 <a
169 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">
170 
+    FAQ</a>를 참고하세요.
171 
+    </p>
172 
+
173 
+
174 
+    <p>그래도 작동하지 않는다면, 다음의<a
175 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">
176 
+    FAQ</a>에서 몇가지 힌트를 얻을 수 있습니다.</p>
177 
+
178 
+    <p>
179 
+    일단 Tor가 작동하기 시작했다면,
180 
+    <a href="<page download/download>#Warning">Tor가 무엇을 하고 무엇을 할 수 없는지</a>
181 
+    확인해보는 것이 좋습니다.
182 
+    </p>
183 
+
184 
+
185 
+    <hr />
186 
+    <a id="server"></a>
187 
+    <a id="relay"></a>
188 
+    <h2><a class="anchor" href="#relay">4단계: 중계서버로 설정하기</a></h2>
189 
+    <br />
190 
+
191 
+    <p>
192 
+    Tor 네트워크는 자발적으로 대역폭을 제공하는 자원자들에 의해 운영됩니다. 중계서버를
193 
+    운영하는 사람이 많아질수록, Tor 네트워크가 더 빨라질 것입니다.
194 
+    만약에 당신이 양방향으로 최소 20Kilobytes/s의 대역폭을 가지고 있다면,
195 
+    당신의 Tor도 중계서버로 운영되도록 설정할 것을 부탁드립니다.
196 
+    제공되는 대역폭을 제한하는 것, 당신의 컴퓨터를 이용해 인터넷을
197 
+    사용하는 사람들이 그것을 악용할 수 없도록 Exit 정책을 설정하는 것,
198 
+    그리고 동적 IP 주소를 지원하는 것 등, Tor중계서버를 설정하는 것은 아주 간단합니다.
199 
+    </p>
200 
+
201 
+
202 
+    <p>광활한 네트의 곳곳에서 중계서버가 운영되는 것이 Tor 이용자들을 안전하게 해줍니다.
203 
+    또 당신이 중계서버를 운영하는 경우, 웹사이트들은 당신의 컴퓨터에서 온 통신요청이 당신이 보낸 것인지
204 
+    아니면 다른 이의 통신요청을 중계해주는 것인지 알 수 없기 때문에<a
205 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">
206 
+    당신에게는 더욱 강한 익명성이 만들어질 수도 있습니다</a>
207 
+    .</p>
208 
+
209 
+
210 
+    <p><a href="<page docs/tor-doc-relay>">중계서버 설정하기</a>
211 
+    를 참고하시면, 더 많은 정보들을 얻을 수 있습니다.</p>
212 
+
213 
+    <hr />
214 
+    <a id="uninstall"></a>
215 
+    <h2><a class="anchor" href="#uninstall">Tor와 Privoxy를 제거하는 방법</a></h2>
216 
+    <br />
217 
+
218 
+    <p> Tor 0.1.0.x 시리즈 이상의 버전들은 커맨드라인을 통해 입력가능한
219 
+    제거명령을 가지고 있습니다. 만약에 OSX에서 Tor를 제거하고 싶다면,
220 
+    아래와 같이 하면 됩니다:</p>
221 
+
222 
+    <p>프로그램들의 프록시 설정을 기존의 초기값으로 돌려놓습니다.
223 
+    만약에 단순히 Tor의 사용을 중단하고 싶은 것이라면, 이것만으로 충분합니다.</p>
224 
+
225 
+    <p>만약에 당신이 Tor를 완전히 제거하고 싶다면, 그리고 당신계정이
226 
+    Admin 권한을 가지고 있다면, 아래와 같이 진행하면 됩니다:</p>
227 
+
228 
+    <ol>
229 
+    <li> 터미널이나 x-term 세션을 연다.</li>
230 
+    <li> cd /Library/Tor</li>
231 
+    <li> sudo -s</li>
232 
+    <li> ./uninstall_tor_bundle.sh</li>
233 
+    </ol>
234 
+
235 
+    <p>이제 컴퓨터에서 Tor와 Privoxy가 완전히 제거되었습니다.</p>
236 
+
237 
+    <p>만약에 당신이  Tor 제거 스크립트가 포함되지 않은 버전을 사용중이라면,
238 
+    아래와 같은 방법으로 수동적인 삭제를 할 수 있습니다:</p>
239 
+    <ul>
240 
+    <li>/Library/Tor</li>
241 
+    <li>/Library/Privoxy</li>
242 
+    <li>/usr/bin/tor</li>
243 
+    <li>/usr/bin/tor_resolve</li>
244 
+    <li>/var/log/tor</li>
245 
+    <li>/usr/share/man/man1/tor.1</li>
246 
+    <li>/usr/share/man/man1/tor-resolve.1</li>
247 
+    <li>/usr/share/man/man1/torify.1</li>
248 
+    <li>/Library/Receipts/Privoxy.pkg/</li>
249 
+    <li>/Library/Receipts/privoxyconf.pkg/</li>
250 
+    <li>/Library/Receipts/Tor.pkg/</li>
251 
+    <li>/Library/Receipts/torstartup.pkg/</li>
252 
+    <li>/Library/StartupItems/Tor</li>
253 
+    <li>/Library/StartupItems/Privoxy</li>
254 
+    </ul>
255 
+
256 
+    <hr />
257 
+
258 
+    <p>이 문서를 개선시킬 수 있는 제안이 있다면,  <a
259 
+    href="<page about/contact>">우리에게 보내주세요</a>. 감사합니다!</p>
260 
+  </div>
261 
+  <!-- END MAINCOL -->
262 
+  <div id = "sidecol">
263 
+#include "side.wmi"
264 
+#include "info.wmi"
265 
+  </div>
266 
+  <!-- END SIDECOL -->
267 
+</div>
268 
+<!-- END CONTENT -->
269 
+#include <foot.wmi>
docs/ko/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,324 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1><a href="<page index>">Tor</a> 중계서버 설정하기</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    Tor 네트워크는 자발적으로 대역폭을 제공하는 자원자들에 의해 운영됩니다. 중계서버를
18 
+    운영하는 사람이 많아질수록, Tor 네트워크가 더 빨라질 것입니다.
19 
+    만약에 당신이 양방향으로 최소 20Kilobytes/s의 대역폭을 가지고 있다면,
20 
+    당신의 Tor도 중계서버로 운영되도록 설정할 것을 부탁드립니다.
21 
+    제공되는 대역폭을 제한하는 것, 당신의 컴퓨터를 이용해 인터넷을
22 
+    사용하는 사람들이 그것을 악용할 수 없도록 Exit 정책을 설정하는 것,
23 
+    그리고 동적 IP 주소를 지원하는 것 등, Tor중계서버를 설정하는 것은 아주 간단합니다.
24 
+    </p>
25 
+
26 
+
27 
+    <p> 광활한 네트의 곳곳에서 중계서버가 운영되는 것이 Tor 이용자들을 안전하게 해줍니다.
28 
+    또 당신이 중계서버를 운영하는 경우, 웹사이트들은 당신의 컴퓨터에서 온 통신요청이 당신이 보낸 것인지
29 
+    아니면 다른 이의 통신요청을 중계해주는 것인지 알 수 없기 때문에<a
30 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">
31 
+    당신에게는 더욱 강한 익명성이 만들어질 수 있습니다</a>
32 
+    .</p>
33 
+
34 
+
35 
+    <p>Tor 중계서버를 설정하는 것은 쉽고 간단합니다:
36 
+    <ul>
37 
+
38 
+    <li>Tor 중계서버에는<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">
39 
+    대역폭 제한기능</a>이 내장되어 있습니다. 또, 당신이 충분한 대역폭을 가지고 있지만
40 
+    하루(혹은 일주일, 한달)에 제공하는 byte를 제한하고 싶다면
41 
+    <a
42 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Hibernation">hibernation
43 
+    기능</a>을 이용할 수 있습니다.
44 
+    </li>
45 
+
46 
+    <li>각각의 Tor 중계서버는 어떤 종류의 통신을 허용/거부하는지 설정하는
47 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RunARelayBut">
48 
+    출구 정책(exit policy)</a>을 가지고 있습니다.
49 
+    만약에 사람들이 당신의 중계서버를 통해 Tor 네트워크를 빠져나가는 것이 불편하다면
50 
+    다른 Tor 중계서버로 연결되는 것만을 허용하도록 설정할 수도 있습니다.
51 
+    </li>
52 
+
53 
+    <li>때때로 중계서버가 꺼지는 것은 괜찮습니다. Tor 디렉토리가 이러한 상태를
54 
+    재빠르게 공지하고 중지된 중계서버를 홍보하는 것을 그만둘 것입니다. 다만
55 
+    통신이 오가는 와중에 중계서버가 꺼진다면 통신이 날아가므로,
56 
+    너무 자주 꺼지는 것은 곤란합니다.
57 
+    </li>
58 
+
59 
+    <li>동적 IP주소로 운영되는 중계서버도 가능합니다. &mdash; IP주소
60 
+    설정칸을 빈칸으로 남겨놓기만 하면, Tor가 IP주소를 찾아낼 것입니다.
61 
+    </li>
62 
+
63 
+
64 
+    <li>만약에 당신의 중계서버가 공유기에 연결되어 있고, 공적 IP주소가 무엇인지 모른다면
65 
+    (예를 들어 IP주소 192.168.x.y), 포트 포워딩을 설정해야 합니다.
66 
+    TCP 연결을 포워딩하는 것은 시스템마다 다르지만 <a
67 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">이
68 
+    FAQ</a>를 보면 몇가지 방법을 확인할 수 있습니다.
69 
+    </li>
70 
+
71 
+    <li>Tor 중계서버는 최신의 가능한 대역폭을 측정하고 공지/홍보할 것입니다.
72 
+    따라서 높은 대역폭의 중계서버가 더 많은 사용자들을 끌어들이게 됩니다. 그러므로
73 
+    낮은 대역폭의 중계서버들도 매우 유용합니다.
74 
+    </li>
75 
+
76 
+    </ul>
77 
+
78 
+    <p>Tor 중계서버는 어떤 운영체제에서도 운영이 가능합니다만
79 
+    어느 운영체제에서 더 잘 작동하는지 어떤 문제가 있을 수 있는지에 대한 조언들을
80 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">이 FAQ</a>
81 
+    에서 확인할 수 있습니다.</p>
82 
+
83 
+
84 
+    <hr />
85 
+    <a id="zero"></a>
86 
+    <h2><a class="anchor" href="#zero">0단계: Tor를 다운받아 설치하기</a></h2>
87 
+    <br />
88 
+
89 
+    <p>시작하기 전에, Tor가 설치되어 있고, 운영되고 있는지 확인해야 합니다.</p>
90 
+
91 
+    <p>윈도우 사용자들은 윈도우 Tor 설치매뉴얼에서 최소한<a
92 
+    href="<page docs/tor-doc-windows>#installing">1단계</a>
93 
+    까지 완료가 된 상태여야 합니다.  맥 OS X 사용자들도 최소한
94 
+    설치매뉴얼의 <a href="<page docs/tor-doc-osx>#installing">1단계</a>
95 
+    까지 진행된 상태여야 하고,  리눅스/BSD/유닉스 사용자들도
96 
+    유닉스 설치설명서에서
97 
+    <a href="<page docs/tor-doc-unix>#installing">1단계</a>
98 
+    까지 진행된 상태여야 합니다.
99 
+    </p>
100 
+
101 
+    <p>제대로 작동하는지 확인하기 위해 당분간은 Tor를 클라이언트로 사용해볼 수도 있습니다.</p>
102 
+
103 
+    <hr />
104 
+    <a id="setup"></a>
105 
+    <h2><a class="anchor" href="#setup">1단계: 중계서버로 설정하기</a></h2>
106 
+    <br />
107 
+
108 
+    <p>
109 
+    1. 컴퓨터의 시계가 정확한 시각을 가르키고 있는지 확인합니다. 가능하다면, 공공
110 
+    시계 서버들과 당신 컴퓨터의 시계를 일치시켜야 합니다.
111 
+    </p>
112 
+
113 
+    <p>
114 
+    2. 도메인 연결 시스템이 제대로 작동하고 있어야 합니다. (당신의
115 
+    컴퓨터가 인터넷 도메인 주소들을 제대로 찾아가고 있으면 된 것입니다.)
116 
+    </p>
117 
+
118 
+    <p>
119 
+    3. torrc의 아랫부분을 수정해야 합니다. (도움말을 위해<a
120 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">이
121 
+    FAQ</a>를 보세요.)
122 
+    최소한 별명Nickname과 ORPort는 입력해야 합니다. 필요하다면 데이터 디렉토리DataDirectory를
123 
+    생성하고, 그 디렉토리가 Tor를 운영하는 사용자의 소유가 되도록 해야합니다.
124 
+    <em>만약 당신이 한 개 이상의 Tor 중계서버를 운영하길 원한다면 정말 대환영입니다. 하지만
125 
+    당신이 운영하는 모든 중계서버에서 <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">MyFamily 옵션</a>을 설정해줘야 합니다.</em>
126 
+    </p>
127 
+
128 
+
129 
+    <p>
130 
+    4. 만약에 당신이 파이어월을 사용하고 있다면, 연결요청들이 당신이 설정한 포트(ORPort, DirPort)
131 
+    에 도달할 수 있도록 파이어월을 열어줘야 합니다. 나가는 연결들은 모두 허용되도록 해야합니다.
132 
+    그래야만 당신의 중계서버가 다른 중계서버로 통신들을 전달할 수 있습니다.
133 
+    </p>
134 
+
135 
+
136 
+    <p>
137 
+    5. 이제 중계서버를 다시 시작하세요. 만약에 <a
138 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">경고메세지</a>가
139 
+    나온다면, 기록해 두세요.
140 
+    </p>
141 
+
142 
+    <p>
143 
+    6. <a
144 
+    href="http://archives.seul.org/or/announce/">or-announce</a>
145 
+    메일링리스트에 가입하세요. 이 메일링리스트는 아주 가끔 사용됩니다.
146 
+    안정화된 새로운 버전이 출시되는 것을 알려줄 것입니다.
147 
+    또는 새로운 개발버전이 나올 때마다 알려주는<a
148 
+    href="http://archives.seul.org/or/talk/">or-talk</a> 메일링리스트에 가입할 수도 있습니다
149 
+    (이 메일링리스트는 좀 더 자주 사용됩니다).
150 
+    </p>
151 
+
152 
+    <p>
153 
+    7. 매뉴얼을 읽어보세요.
154 
+    최신의 안정화된 버전에 대한 <a href="<page docs/tor-manual>">매뉴얼</a>은
155 
+    클라이언트와 중계서버 모두에 해당하는 모든 설정옵션을 알려줍니다.
156 
+    만약에 당신이 Tor의 개발버전을 사용중이라면,
157 
+    <a href="<page docs/tor-manual-dev>">여기</a>에 있는 매뉴얼을 보면 됩니다.
158 
+    </p>
159 
+
160 
+
161 
+
162 
+    <hr />
163 
+    <a id="check"></a>
164 
+    <h2><a class="anchor" href="#check">2단계: 제대로 작동하는지 확인하기</a></h2>
165 
+    <br />
166 
+
167 
+    <p>Tor 중계서버가 네트워크에 연결을 시도하자 마자, 설정된 포트가
168 
+    바깥쪽에서 접속가능한지 스스로 확인할 것입니다. 이 과정은 최대 20분정도 걸릴 수 있습니다.
169 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">로그기록</a>에서
170 
+    다음과 같은 문장이 있는지 찾아보세요
171 
+    <tt>Self-testing indicates your ORPort is reachable from the outside. Excellent.</tt>
172 
+    만약에 위와 같은 메세지가 없다면, 중계서버가 바깥쪽에서 접속할 수 없다는 뜻입니다
173 
+    &mdash; 이럴 경우 파이어월을 다시 한번 확인해야 합니다. 테스트해야한다고 생각하는
174 
+    IP주소와 포트를 테스트하고 있는지 확인하세요.
175 
+    </p>
176 
+
177 
+    <p>일단 접속이 가능하다고 판단이 되면, 디렉토리에 "server
178 
+    descriptor"를 올릴 것입니다.  이것을 통해 클라이언트들이
179 
+    Tor 중계서버의 주소, 포트, 키, 등의 정보를 알게 될 것입니다. 중계서버가 올라왔는지 확인하기 위해, <a
180 
+    href="http://moria.seul.org:9032/tor/status/authority">네트워크 상태 중 하나를
181 
+    보고</a> 앞에서 입력한 별명Nickname을 찾아볼 수도 있습니다.
182 
+    최신의 디렉토리 상태로 새로고침 하기 위해서 몇 초간 기다려야 합니다.
183 
+    </p>
184 
+
185 
+
186 
+    <hr />
187 
+    <a id="after"></a>
188 
+    <h2><a class="anchor" href="#after">3단계: 제대로 작동을 시작한 후에</a></h2>
189 
+    <br />
190 
+
191 
+    <p>
192 
+    아래의 단계들도 진행할 것을 권장합니다:
193 
+    </p>
194 
+
195 
+    <p>
196 
+    8. Tor 중계서버의 보안을 어떻게 강화할 수 있는지
197 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">이 문서</a>
198 
+    를 읽어보세요.
199 
+    </p>
200 
+
201 
+    <p>
202 
+    9. 어떤 출구정책을 원하는지 결정하세요. 몇 가지를 제외하고(예를 들어 포트 25)
203 
+    기본적으로 Tor 중계서버는 대부분의 서비스를 허용합니다. 출구정책이 좀 더
204 
+    많은 제한을 하게 하거나, 혹은 좀 더 적은 제한을 하게 할 수 있습니다;
205 
+    torrc 파일을 적당하게 수정하면 됩니다.
206 
+    <a
207 
+    href="<page docs/faq-abuse>#TypicalAbuses">기본 출구정책을 사용할 때 발생할 수 있는 문제들
208 
+    에 대한 FAQ</a>를 읽어보세요.
209 
+    만약에 개방된 출구정책을 정한다면, 당신이 사용하는 ISP가 그런 결정을
210 
+    수용할 수 있는지 확인해야 합니다.
211 
+    만약에 컴퓨터에 특정 접속제한이 있다면 (예를 들어,
212 
+    파이어월이나 콘테트 필터를 사용중이라면), 출구정책에도 그것들을 반영해야 합니다 &mdash;
213 
+    그렇지 않다면 Tor 이용자들이 영향을 받을 것입니다.
214 
+    </p>
215 
+
216 
+    <p>
217 
+    10. 대역폭 제한 문제도 결정해야 합니다. 케이블 모뎀 , DSL, 그리고
218 
+    비대칭적 대역폭을 가지고 있는 사용자들은
219 
+    (예를 들어, 다운로드 대역폭이 업로드 대역폭보다 큰 경우)
220 
+    통신이 느려지거나 혼잡해지는 것을 방지하기 위해 대역폭 제한 설정을 해줘야 합니다.
221 
+    구체적인 내용들은 <a
222 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">대역폭 제한 FAQ</a>에서 확인할 수 있습니다.
223 
+    </p>
224 
+
225 
+    <p>
226 
+    11. Tor 중계서버의 비밀키를 백업해야 합니다 (데이터디렉토리DataDirectory의 "keys/secret_id_key"
227 
+    에 저장되어 있습니다). 이것이 Tor 중계서버의 "identity"입니다. 그리고
228 
+    중계서버를 지나가는 트래픽들을 아무도 읽을 수 없도록 하기 위해서 이것을
229 
+    안전하게 보관해야 합니다. 이것은 무언가 잘못되어서 <a
230 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeRelay">Tor 중계서버를 옮기거나
231 
+    복구</a>해야할 때 필요한 매우 중요한 파일입니다.</p>
232 
+
233 
+    <p>
234 
+    12. 만약 당신의 도메인이 설정되어 있는 네임서버를 직접 관리한다면, 역 DNS 호스트네임을
235 
+     'anonymous-relay', 'proxy' 혹은 'tor-proxy'로 설정하는 것을 고려해 주세요. 이럴 경우
236 
+    다른 사람들이 그들의 웹로그에서 주소를 볼 때, 그들은 무슨 일이 일어나고 있는지
237 
+    더 빨리 이해할 수 있을 것입니다. 당신이 출구노드로서 Tor 중계서버를 운영하고 있는 경우,
238 
+    이러한 이름으로 가상 호스트vhost 에<a
239 
+    href="https://tor-svn.freehaven.net/svn/tor/trunk/contrib/tor-exit-notice.html">Tor
240 
+    출구 공지</a>를 추가하는 것은 당신과 당신의 ISP에 악의적인 불평을 하려는 시도들을
241 
+    막는데 큰 도움이 됩니다.
242 
+    </p>
243 
+
244 
+
245 
+    <p>
246 
+    13. 만약 당신의 컴퓨터가 웹서버를 운영하는 것이 아니라면,
247 
+    ORPort를 443으로, DirPort를  80으로 바꾸는 것을 고려해주세요.
248 
+    많은 Tor 이용자들 웹브라우징만 허용하는 파이어월 뒤에 갇히게 되는데,
249 
+    이 변화가 그들로 하여금 당신의 Tor 중계서버에 접속할 수 있도록 해줄 것입니다.
250 
+    윈도우 중계서버들은 torrc에서 ORPort 와 DirPort 수정해준 다음에
251 
+    Tor를 다시 시작하면 됩니다. OS X 나 Unix 중계서버들은  (루트가 아닌 이상) 이 포트들에 직접
252 
+    연결될 수 없습니다, 그래서 통신요청들이 Tor 중계서버에 도달할 수 있도록 <a
253 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">
254 
+    포트 포워딩</a>같은 설정이 필요합니다. 만약 당신이 포트 80과 443을 사용중인데도,
255 
+    제대로 작동하지 않는다면, 포트 22, 110, 143을 사용해보는 것도 할 수 있습니다.</p>
256 
+
257 
+    <p>
258 
+    14. 만약 당신의 Tor 중계서버가 같은 IP주소에서 다른 서비스를 제공하고 있다면
259 
+    &mdash; 예를 들어 웹서버 &mdash; 로컬호스트를 통해서도 웹서버에
260 
+    연결될 수 있도록 해야합니다. Tor 클라이언트가 Tor 중계서버를 <a
261 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">
262 
+    웹서버에 접속하는 가장 안전한 방법</a>으로
263 
+    인식하기 때문에 이러한 연결을 허용해줘야 합니다.
264 
+    그리고 중계서버로 끝나는 회로를 꼭 구성해야 합니다.
265 
+    만약에 연결을 허용하고 싶지 않다면,
266 
+    출구정책에서 그것들을 명확하게 차단해야 합니다.
267 
+    </p>
268 
+
269 
+    <p>
270 
+    15. (유닉스만 해당). 중계서버를 운영하는 별도의 계정을 만드세요.
271 
+    만약에 OS x 패키지나 deb나 rpm 을 설치했다면, 이 작업은 이미 되어
272 
+    있을 것입니다.
273 
+    그렇지않다면, 직접할 수 있습니다. (Tor 중계서버는 루트계정으로
274 
+    운영되어야 할 필요가 없습니다.
275 
+    그러므로 루트계정으로 운영하지 않는 것이 좋습니다. 'tor' 계정으로
276 
+    중계서버를 운영하는 것은  identd 데몬과 사용자 이름과 관련된 몇가지
277 
+    문제들을 해결해줍니다. 만약에 당신이 걱정이 많은 사람이라면, <a
278 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">
279 
+    chroot jail에 Tor를 놓을 수도 있습니다</a>.)
280 
+    </p>
281 
+
282 
+    <p>
283 
+    16. (유닉스만 해당) 당신의 운영체제는
284 
+    아마도 프로세스당 열려있는 파일 디스크립터의 갯수를 1024개로 제한하고 있을 것입니다.(때로는 더 적게)
285 
+    만약에 빠른 출구 노드를 운영할 계획이라면, 이 갯수는 충분하지 않습니다.
286 
+    리눅스에서는, /etc/security/limits.conf 파일에  "toruser hard nofile 8192"
287 
+    라고 추가해야 합니다. (toruser는 Tor 프로세스를 운영하는 계정을 말합니다)
288 
+    그리고 패키지 상태로 설치가 되었다면 Tor를 재시작해야 합니다.
289 
+    만약에 이것이 적용되지 않는다면,
290 
+    Tor를 시작하기 전에 "ulimit -n 8192"를 실행시킬 수 있는 다른 방법들이 나와있는<a
291 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FileDescriptors">이 FAQ</a>
292 
+    를 참고하세요. </p>
293 
+
294 
+
295 
+    <p>
296 
+    17. 만약에 당신이 패키지나 인스톨러를 통해 Tor를 설치했다면,
297 
+    Tor는 컴퓨터가 켜질 때 자동으로 실행될 것입니다. 그러나 만약에 소스에서 직접 설치했다면
298 
+    contrib/tor.sh나 contrib/torctl의 스크립트를 유용하게 사용할 수 있을 것입니다.
299 
+    </p>
300 
+
301 
+    <p>
302 
+    Tor 설정을 변경할 때는, 변경이 후에도 Tor 중계서버가 잘 작동하고 있는지
303 
+    꼭 확인해야 합니다. 만약에 당신의 Tor 중계서버가 업그레이드가 필요하거나
304 
+    무언가 잘못되고 있을 때 우리가 당신에게 연락할 수 있도록 torrc 파일에서
305 
+    "ContactInfo" 라인을 설정/유지하는 것을 잊지마세요.
306 
+    문제나 질문이 있다면, <a href="<page docs/documentation>#Support">지원 섹션</a>을 보거나
307 
+    tor-ops 리스트에서 <a href="<page about/contact>">contact us</a> 부분을 참고하세요.
308 
+    Tor 네트워크가 자랄 수 있도록 도와주셔서 감사합니다!</p>
309 
+
310 
+
311 
+    <hr />
312 
+
313 
+    <p>이 문서를 개선하기 위한 제안이 있다면, <a
314 
+    href="<page about/contact>">우리에게 보내주세요</a>.감사합니다!</p>
315 
+  </div>
316 
+  <!-- END MAINCOL -->
317 
+  <div id = "sidecol">
318 
+#include "side.wmi"
319 
+#include "info.wmi"
320 
+  </div>
321 
+  <!-- END SIDECOL -->
322 
+</div>
323 
+<!-- END CONTENT -->
324 
+#include <foot.wmi>
docs/ko/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,218 @@
1 
+    <h1>리눅스/BSD/유닉스에서 <a href="<page index>">Tor</a> 운영하기</h1>
2 
+    <br />
3 
+
4 
+    <p>
5 
+    <b>이 안내서는 Tor 클라이언트
6 
+    운영울 위한 설치 매뉴얼 입니다. 만약 다른 이용자들에게 중계 트래픽을 제공해서
7 
+    Tor 네트워크가 더 커지도록 돕고싶다면(꼭 해주세요),
8 
+    <a href="<page docs/tor-doc-relay>">중계서버 설정하기</a>를 읽어주세요.</b>
9 
+    </p>
10 
+
11 
+    <hr />
12 
+    <a id="installing"></a>
13 
+    <h2><a class="anchor" href="#installing">1단계: Tor 다운받아 설치하기</a></h2>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    Tor의 최신버전은
18 
+    <a href="<page download/download>">다운로드 페이지</a>에서 찾을 수 있습니다.
19 
+    데비안, 레드햇, 젠투, *BSD 등을 위한 Tor 패키지를 다운받을 수 있습니다.</p>
20 
+
21 
+    <p>소스를 가지고 직접 설치를 하려면 , 먼저 <a
22 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a>를 설치해야 합니다.
23 
+    그리고 openssl과 zlib도 설치되어 있는지 확인해야 합니다. (가능하다면 -devel 패키지도 포함해서)
24 
+    설치와 확인이 끝나면 다음 명령을 실행하세요:<br />
25 
+    <tt>tar xzf tor-<version-stable>.tar.gz; cd tor-<version-stable><br />
26 
+    ./configure &amp;&amp; make</tt><br />
27 
+    이제 <tt>src/or/tor</tt>를 통해 Tor를 실행시키거나,
28 
+    <tt>make install</tt>을 (필요하다면 루트권한으로) 실행시켜서
29 
+    /usr/local/에 인스톨한 후 <tt>tor</tt>
30 
+    명령어를 통해 Tor를 실행시킬 수 있습니다.
31 
+    </p>
32 
+
33 
+    <p>
34 
+    Tor는 기본적으로 클라이언트로 설정 되어 있습니다. 기본 설정 파일이 내장되어 있는데,
35 
+    대부분의 경우 이 설정을 변경할 필요가 없습니다. 이제 Tor가 설치된 것입니다.
36 
+    </p>
37 
+
38 
+    <hr />
39 
+    <a id="privoxy"></a>
40 
+    <h2><a class="anchor" href="#privoxy">2단계: 웹브라우저를 위해 Privoxy 설치하기</a></h2>
41 
+    <br />
42 
+
43 
+    <p>Tor를 설치한 다음에는, 프로그램들이 Tor를 사용하도록 설정해야 합니다.</p>
44 
+
45 
+    <p>
46 
+    첫 번째 할 일은 웹브라우저를 설정하는 것입니다. 우선 <a
47 
+    href="http://www.privoxy.org/">Privoxy</a>를 설치해야 합니다:
48 
+    'recent releases'를 클릭하고
49 
+    가장 적합한 패키지를 선택하거나, 소스를 가지고 직접 설치할 수 있습니다. Privoxy는
50 
+    Tor와 함께 작동하는 필터링 웹 프록시입니다.
51 
+    </p>
52 
+
53 
+
54 
+    <p>Privoxy를 설치하고 나면(패키지로 했던 소스로 했던지 간에),
55 
+    <b>Privoxy가 Tor를 사용하도록 설정해야 합니다</b>.
56 
+    <a
57 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">Privoxy 설정 샘플</a>
58 
+    을 보는게 도움이 될 수 있습니다. 아니면 아래 나와있는 방법을 이용해
59 
+    Privoxy 설정을 직접 할 수도 있습니다.</p>
60 
+
61 
+
62 
+    <p>
63 
+    Privoxy의 "config" 파일을 엽니다.(/etc/privoxy/나 /usr/local/etc/에 있을 것입니다)
64 
+    그리고 config 파일의 맨 위에 다음 줄을 추가하세요.<br>
65 
+    <tt>forward-socks4a / 127.0.0.1:9050 .</tt><br>
66 
+    마지막에 있는 점dot까지 입력해야 합니다.
67 
+    </p>
68 
+
69 
+    <p>Privoxy는 그것을 통과한 모든 것에 대한 기록을 로그파일로 보관합니다.
70 
+    이것을 멈추게 하기 위해서 아래의 세줄을 주석처리 해야합니다.
71 
+    맨 앞에 \#를 입력하면 주석처리가 됩니다. 그 세줄은: <br>
72 
+    <tt>logfile logfile</tt><br>
73 
+    그리고<br>
74 
+    <tt>jarfile jarfile</tt><br>
75 
+    그리고 (몇몇 시스템에서는) <br>
76 
+    <tt>debug 1  # show each GET/POST/CONNECT request</tt><br>
77 
+    입니다.
78 
+    </p>
79 
+
80 
+    <p>기본 config 파일이 어떤 것이냐에 따라,
81 
+    <tt>enable-remote-toggle</tt>와,
82 
+    <tt>enable-remote-http-toggle</tt>, 그리고 <tt>enable-edit-actions</tt>
83 
+    기능을 꺼야할 수도 있습니다.
84 
+    </p>
85 
+
86 
+
87 
+    <p>변경된 설정을 적용하기 위해서 Privoxy를 다시 시작해야 합니다.</p>
88 
+
89 
+    <hr />
90 
+    <a id="using"></a>
91 
+    <h2><a class="anchor" href="#using">3단계: 당신의 프로그램이 Tor를 사용하도록 설정하기</a></h2>
92 
+    <br />
93 
+
94 
+    <p>Tor와 Privoxy를 설치한 후에, 당신이 운영중인 프로그램들이 Tor를 사용하도록 설정해야 합니다.
95 
+    가장 먼저 할 일은 웹브라우저 설정을 변경하는 것입니다.</p>
96 
+
97 
+    <p>
98 
+    만약에 당신이 파이어폭스를 사용중이라면(파이어폭스를 권장합니다),
99 
+    <a href="https://addons.mozilla.org/firefox/2275/">Torbutton
100 
+    플러그인</a>만 설치하면 됩니다. 그러면 모든 설정이 끝난 것입니다:
101 
+    </p>
102 
+
103 
+    <img alt="Torbutton plugin for Firefox"
104 
+    src="../img/screenshot-torbutton.png"
105 
+    border="1">
106 
+
107 
+    <br />
108 
+
109 
+    <p>
110 
+    (<a href="https://torbutton.torproject.org/">Torbutton에 대해 더 알고 싶으면 여기를 클릭하세요</a>.
111 
+    만약에 다른 컴퓨터에서도 파이어폭스와 Tor를 사용할 계획이라면, 다음의
112 
+    <a
113 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">
114 
+    FAQ</a>를 참고하세요.
115 
+    만약에 파이어폭스가 아닌 다른 브라우저를 사용해야 한다면,
116 
+    <a href="<page docs/tor-doc-web>">프록시 설정을 직접 해줘야 합니다</a>.)
117 
+    </p>
118 
+
119 
+
120 
+    <p>Privoxy를 사용하는 것은 <strong>필수입니다</strong>. 왜냐하면 <a
121 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">브라우저들은
122 
+    SOCKS 프록시를 직접 운영하면서 당신이 보내는 DNS 요청을 곳곳에 흘리기 때문입니다</a>.
123 
+    이것은 당신의 익명성에 안 좋은 영향을 줍니다. 또 Privoxy는 당신의 통신요청에서
124 
+    위험한 헤더들을 제거하고, Doubleclick같은 불쾌한 광고사이트를 차단해주는 일도 합니다.</p>
125 
+
126 
+
127 
+    <p>HTTP 프록시를 사용하는 다른 프로그램에서도 Tor를 사용하려면,
128 
+    그들이 Privoxy를 가르키도록 설정하면 됩니다(즉, localhost 포트 8118로 연결).
129 
+    SOCKS를 직접 연결해서 사용하려면(메신저, Jabber, IRC 등), 당신의 프로그램이
130 
+    Tor를 가르키도록 직접 설정할 수 있습니다(localhost 포트 9050),
131 
+    그러나 이것이 왜 위험한지 알기 위해서 다음의<a
132 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">
133 
+    FAQ</a>를 한 번 볼 필요가 있습니다. SOCKS나 HTTP가 사용불가능한 프로그램을 위해선
134 
+    <a href="http://tsocks.sourceforge.net/">tsocks</a> or <a
135 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>을 참고하세요.
136 
+    </p>
137 
+
138 
+
139 
+    <p>이밖에 다른 프로그램들에서 어떻게 Tor를 사용할 수 있는지에 대한 정보가 필요하다면,
140 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
141 
+    HOWTO</a>를 참고하세요.
142 
+    </p>
143 
+
144 
+    <hr />
145 
+    <a id="verify"></a>
146 
+    <h2><a class="anchor" href="#verify">4단계: 제대로 작동하는지 확인하기</a></h2>
147 
+    <br />
148 
+
149 
+    <p>
150 
+    다음으로, Tor를 사용하도록 설정된 브라우저를 통해 통신을 할 때 IP주소가 제대로 익명화되고 있는지 확인해야 합니다.
151 
+    <a href="https://check.torproject.org/">Tor 확인기</a>를 클릭한 후
152 
+    당신이 Tor를 사용하고 있는지 아닌지 결과를 확인하세요.
153 
+    #<a href="http://ipchicken.com/">이 사이트</a>
154 
+    #에서는 당신이 사용하고 있다고 생각되는 IP주소를 알려줍니다.
155 
+    (만약 이 사이트가 안 열린다면, Tor를 테스트할 수 있는 다른 방법들이 나와있는 다음의<a
156 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">
157 
+    FAQ</a>를 확인하세요.)
158 
+    </p>
159 
+
160 
+    <p>만약에 접속제한을 하는 개인 파이어월을 사용 중이라면(예를 들어, 페도라 코어 4의 SELinux),
161 
+    당신이 사용하는 프로그램들이 Privoxy(8118 포트)와 Tor(9050 포트)에 접속
162 
+    할 수 있도록 되어있는지 확인해야 합니다. 만약에 파이어월이
163 
+    밖으로 나가는 연결을 차단한다면, 최소한 TCP 포트 80번과 443번은
164 
+    연결이 되도록 허용해야 합니다. 그리고나서 다음의 <a
165 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">
166 
+    FAQ</a>를 참고하세요. 만약에 SELinux가 tor나 privoxy가 제대로 작동하지 못하도록
167 
+    설정되어 있다면, /etc/selinux/targeted 폴더에 booleans.local 이라는 이름의 파일을 생성하세요.
168 
+    그리고 당신이 가장 좋아하는 텍스트 편집기로
169 
+    "allow_ypbind=1"이라고 파일에 입력한 후 저장합니다. 이제
170 
+    컴퓨터를 다시 시작하면, 이 설정이 적용될 것입니다.
171 
+    </p>
172 
+
173 
+
174 
+    <p>그래도 작동하지 않는다면, 다음의<a
175 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">
176 
+    FAQ</a>에서 몇가지 힌트를 얻을 수 있습니다.</p>
177 
+
178 
+    <hr />
179 
+    <a id="server"></a>
180 
+    <a id="relay"></a>
181 
+    <h2><a class="anchor" href="#relay">5단계: 중계서버로 설정하기</a></h2>
182 
+    <br />
183 
+
184 
+    <p>
185 
+    Tor 네트워크는 자발적으로 대역폭을 제공하는 자원자들에 의해 운영됩니다. 중계서버를
186 
+    운영하는 사람이 많아질수록, Tor 네트워크가 더 빨라질 것입니다.
187 
+    만약에 당신이 양방향으로 최소 20Kilobytes/s의 대역폭을 가지고 있다면,
188 
+    당신의 Tor도 중계서버로 운영되도록 설정할 것을 부탁드립니다.
189 
+    제공되는 대역폭을 제한하는 것, 당신의 컴퓨터를 이용해 인터넷을
190 
+    사용하는 사람들이 그것을 악용할 수 없도록 Exit 정책을 설정하는 것,
191 
+    그리고 동적 IP 주소를 지원하는 것 등, Tor중계서버를 설정하는 것은 아주 간단합니다.
192 
+    </p>
193 
+
194 
+    <p>광활한 네트의 곳곳에서 중계서버가 운영되는 것이 Tor 이용자들을 안전하게 해줍니다.
195 
+    또 당신이 중계서버를 운영하는 경우, 웹사이트들은 당신의 컴퓨터에서 온 통신요청이 당신이 보낸 것인지
196 
+    아니면 다른 이의 통신요청을 중계해주는 것인지 알 수 없기 때문에<a
197 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">
198 
+    당신에게는 더욱 강한 익명성이 만들어질 수도 있습니다</a>
199 
+    .</p>
200 
+
201 
+
202 
+    <p><a href="<page docs/tor-doc-relay>">중계서버 설정하기</a>
203 
+    를 참고하시면, 더 많은 정보들을 얻을 수 있습니다.</p>
204 
+
205 
+    <hr />
206 
+
207 
+    <p>이 문서를 개선시킬 수 있는 제안이 있다면,  <a
208 
+    href="<page about/contact>">우리에게 보내주세요</a>. 감사합니다!</p>
209 
+  </div>
210 
+  <!-- END MAINCOL -->
211 
+  <div id = "sidecol">
212 
+#include "side.wmi"
213 
+#include "info.wmi"
214 
+  </div>
215 
+  <!-- END SIDECOL -->
216 
+</div>
217 
+<!-- END CONTENT -->
218 
+#include <foot.wmi>
docs/ko/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,206 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>윈도우에서 <a href="<page index>">Tor</a> 운영하기</h1>
14 
+    <br />
15 
+
16 
+
17 
+    <p>
18 
+    <b>이 안내서는 윈도우(98m 98SE, NT4, 2000, XP, Vista, Server)에서의 Tor 클라이언트
19 
+    운영울 위한 설치 매뉴얼 입니다. 만약 다른 이용자들에게 중계 트래픽을 제공해서
20 
+    Tor 네트워크가 더 커지도록 돕고싶다면(꼭 해주세요),
21 
+    <a href="<page docs/tor-doc-relay>">중계서버 설정하기</a>를 읽어주세요.</b>
22 
+    </p>
23 
+
24 
+    <hr />
25 
+    <a id="installing"></a>
26 
+    <h2><a class="anchor" href="#installing">1단계: Tor 다운받아 설치하기</a></h2>
27 
+    <br />
28 
+
29 
+    <p>
30 
+    윈도우 버전 통합배포판은 Tor, Vidalia, <a
31 
+    href="http://www.privoxy.org">Privoxy</a>(필터핑 웹 프록시)를 포함하고 있습니다.
32 
+    그리고 이것들은 함께 작동하도록 설정되어 있습니다.
33 
+    <a href="../<package-win32-bundle-stable>">안정화된 버전</a>이나
34 
+    <a href="../<package-win32-bundle-alpha>">개발 버전</a> 중 하나를 다운받을 수도 있고,
35 
+    <a href="<page download/download>">다운로드 페이지</a>에서 다른 버전들을 찾아볼 수도 있습니다.
36 
+    </p>
37 
+
38 
+    <img alt="tor installer splash page"
39 
+    src="../img/screenshot-win32-installer-splash.png" />
40 
+
41 
+    <p>
42 
+    만약에 당신 컴퓨터에 기존에 설치해 놓은 Tor, Vidalia, Privoxy가 있다면
43 
+    아래에 보이는 대화창에서처럼 설치할 필요가 없는 프로그램을 제외시킬 수 있습니다.
44 
+    </p>
45 
+
46 
+    <img alt="select components to install"
47 
+    src="../img/screenshot-win32-installer-components.png" />
48 
+
49 
+    <p>설치가 끝나면, 당신이 선택한 프로그램이 자동적으로 실행될 것입니다.
50 
+    </p>
51 
+
52 
+    <!--
53 
+    <p>
54 
+    Tor는 기본적으로 클라이언트로 설정 되어 있습니다. 기본 설정 파일이 내장되어 있는데,
55 
+    대부분의 경우 이 설정을 변경할 필요가 없습니다. 이제 Tor가 설치된 것입니다.
56 
+    </p>
57 
+    -->
58 
+
59 
+    <hr />
60 
+    <a id="using"></a>
61 
+    <h2><a class="anchor" href="#using">2단계: 당신의 프로그램이 Tor를 사용하도록 설정하기</a></h2>
62 
+    <br />
63 
+
64 
+    <p>Tor와 Privoxy를 설치한 후에, 당신이 운영중인 프로그램들이 Tor를 사용하도록 설정해야 합니다.
65 
+    가장 먼저 할 일은 웹브라우저 설정을 변경하는 것입니다.</p>
66 
+
67 
+    <p>
68 
+    만약에 당신이 파이어폭스를 사용중이라면(파이어폭스를 권장합니다), Vidalia 통합배포판이
69 
+    <a href="https://addons.mozilla.org/firefox/2275/">Torbutton
70 
+    플러그인</a>을 자동으로 설치할 것입니다. 설치 후 파이어폭스를 다시 시작하면, 모든 설정이 끝난 것입니다:
71 
+    </p>
72 
+
73 
+    <img alt="Torbutton plugin for Firefox"
74 
+    src="../img/screenshot-torbutton.png"
75 
+    border="1">
76 
+
77 
+    <br />
78 
+
79 
+    <p>
80 
+    (<a href="https://torbutton.torproject.org/">Torbutton에 대해 더 알고 싶으면 여기를 클릭하세요</a>.
81 
+    만약에 다른 컴퓨터에서도 파이어폭스와 Tor를 사용할 계획이라면, 다음의
82 
+    <a
83 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">
84 
+    FAQ</a>를 참고하세요.
85 
+    만약에 파이어폭스가 아닌 다른 브라우저를 사용해야 한다면,
86 
+    <a href="<page docs/tor-doc-web>">프록시 설정을 직접 해줘야 합니다</a>.)
87 
+    </p>
88 
+
89 
+
90 
+    <p>Privoxy를 사용하는 것은 <strong>필수입니다</strong>. 왜냐하면 <a
91 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">브라우저들은
92 
+    SOCKS 프록시를 직접 운영하면서 당신이 보내는 DNS 요청을 곳곳에 흘리기 때문입니다</a>.
93 
+    이것은 당신의 익명성에 안 좋은 영향을 줍니다. 또 Privoxy는 당신의 통신요청에서
94 
+    위험한 헤더들을 제거하고, Doubleclick같은 불쾌한 광고사이트를 차단해주는 일도 합니다.</p>
95 
+
96 
+
97 
+
98 
+
99 
+    <p>HTTP 프록시를 사용하는 다른 프로그램에서도 Tor를 사용하려면,
100 
+    그들이 Privoxy를 가르키도록 설정하면 됩니다(즉, localhost 포트 8118로 연결).
101 
+    SOCKS를 직접 연결해서 사용하려면(메신저, Jabber, IRC 등), 당신의 프로그램이
102 
+    Tor를 가르키도록 직접 설정할 수 있습니다(localhost 포트 9050),
103 
+    그러나 이것이 왜 위험한지 알기 위해서 다음의<a
104 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">
105 
+    FAQ</a>를 한 번 볼 필요가 있습니다. SOCKS나 HTTP가 사용불가능한 프로그램을 위해선
106 
+    <a
107 
+    href="http://www.socks.permeo.com/Download/SocksCapDownload/index.asp">SocksCap</a> 이나
108 
+    <a href="http://www.freecap.ru/eng/">FreeCap</a>을 참고하세요.
109 
+    (FreeCap는 자유소프트웨어이고, SocksCap은 상용프로그램입니다.)</p>
110 
+
111 
+
112 
+    <p>이밖에 다른 프로그램들에서 어떻게 Tor를 사용할 수 있는지에 대한 정보가 필요하다면,
113 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
114 
+    HOWTO</a>를 참고하세요.
115 
+    </p>
116 
+
117 
+    <hr />
118 
+    <a id="verify"></a>
119 
+    <h2><a class="anchor" href="#verify">3단계: 제대로 작동하는지 확인하기</a></h2>
120 
+    <br />
121 
+
122 
+    <p>
123 
+    설치를 한 후에 Privoxy와 Vidalia가 잘 작동하고 있는지 확인이 필요합니다.
124 
+    파란색이나 녹색 원 안에  "P"가 쓰여져 있는 것이 Privoxy 아이콘입니다.
125 
+    Vidalia 아이콘은 Tor가 작동중일 때는 녹색 양파로 나타나며,
126 
+    작동중이지 않을 때는 빨간색 "X"가 새겨진 어두운 양파로 나타납니다.
127 
+    시스템 트레이에 있는 Vidalia 아이콘을 마우스 오른쪽 버튼으로 클릭한 후
128 
+    아래 그림에 보이는 메뉴에서 "Start"나 "Stop"을 선택해서
129 
+    Tor를 시작하거나 끝낼 수 있습니다.
130 
+    </p>
131 
+
132 
+    <img alt="Vidalia Tray Icon"
133 
+    src="../img/screenshot-win32-vidalia.png">
134 
+
135 
+    <p>
136 
+    다음으로, Tor를 사용하도록 설정된 브라우저를 통해 통신을 할 때 IP주소가 제대로 익명화되고 있는지 확인해야 합니다.
137 
+    <a href="https://check.torproject.org/">Tor 확인기</a>를 클릭한 후
138 
+    당신이 Tor를 사용하고 있는지 아닌지 결과를 확인하세요.
139 
+    #<a href="http://ipchicken.com/">이 사이트</a>
140 
+    #에서는 당신이 사용하고 있다고 생각되는 IP주소를 알려줍니다.
141 
+    (만약 이 사이트가 안 열린다면, Tor를 테스트할 수 있는 다른 방법들이 나와있는 다음의<a
142 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">
143 
+    FAQ</a>를 확인하세요.)
144 
+    </p>
145 
+
146 
+    <p>만약에 접속제한을 하는 개인 파이어월을 사용 중이라면,
147 
+    당신이 사용하는 프로그램들이 당신 컴퓨터의 8118 포트와 9050 포트에 접근을
148 
+    할 수 있도록 되어있는지 확인해야 합니다. 만약에 파이어월이
149 
+    밖으로 나가는 연결을 차단한다면, 최소한 TCP 포트 80번과 443번은
150 
+    연결이 되도록 허용해야 합니다. 그리고나서 다음의 <a
151 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">
152 
+    FAQ</a>를 참고하세요.
153 
+    </p>
154 
+
155 
+
156 
+    <p>그래도 작동하지 않는다면, 다음의<a
157 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">
158 
+    FAQ</a>에서 몇가지 힌트를 얻을 수 있습니다.</p>
159 
+
160 
+    <p>
161 
+    일단 Tor가 작동하기 시작했다면,
162 
+    <a href="<page download/download>#Warning">Tor가 무엇을 하고 무엇을 할 수 없는지</a>
163 
+    확인해보는 것이 좋습니다.
164 
+    </p>
165 
+
166 
+    <hr />
167 
+    <a id="server"></a>
168 
+    <a id="relay"></a>
169 
+    <h2><a class="anchor" href="#relay">4단계: 중계서버로 설정하기</a></h2>
170 
+    <br />
171 
+
172 
+    <p>
173 
+    Tor 네트워크는 자발적으로 대역폭을 제공하는 자원자들에 의해 운영됩니다. 중계서버를
174 
+    운영하는 사람이 많아질수록, Tor 네트워크가 더 빨라질 것입니다.
175 
+    만약에 당신이 양방향으로 최소 20Kilobytes/s의 대역폭을 가지고 있다면,
176 
+    당신의 Tor도 중계서버로 운영되도록 설정할 것을 부탁드립니다.
177 
+    제공되는 대역폭을 제한하는 것, 당신의 컴퓨터를 이용해 인터넷을
178 
+    사용하는 사람들이 그것을 악용할 수 없도록 Exit 정책을 설정하는 것,
179 
+    그리고 동적 IP 주소를 지원하는 것 등, Tor중계서버를 설정하는 것은 아주 간단합니다.
180 
+    </p>
181 
+
182 
+    <p>광활한 네트의 곳곳에서 중계서버가 운영되는 것이 Tor 이용자들을 안전하게 해줍니다.
183 
+    또 당신이 중계서버를 운영하는 경우, 웹사이트들은 당신의 컴퓨터에서 온 통신요청이 당신이 보낸 것인지
184 
+    아니면 다른 이의 통신요청을 중계해주는 것인지 알 수 없기 때문에<a
185 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">
186 
+    당신에게는 더욱 강한 익명성이 만들어질 수도 있습니다</a>
187 
+    .</p>
188 
+
189 
+
190 
+    <p><a href="<page docs/tor-doc-relay>">중계서버 설정하기</a>
191 
+    를 참고하시면, 더 많은 정보들을 얻을 수 있습니다.</p>
192 
+
193 
+    <hr />
194 
+
195 
+    <p>이 문서를 개선시킬 수 있는 제안이 있다면,  <a
196 
+    href="<page about/contact>">우리에게 보내주세요</a>. 감사합니다!</p>
197 
+  </div>
198 
+  <!-- END MAINCOL -->
199 
+  <div id = "sidecol">
200 
+#include "side.wmi"
201 
+#include "info.wmi"
202 
+  </div>
203 
+  <!-- END SIDECOL -->
204 
+</div>
205 
+<!-- END CONTENT -->
206 
+#include <foot.wmi>
docs/pl/N900.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,156 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21979 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: N900 Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/N900>">N900</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="Maemo"></a>
14 
+    <h2><a class="anchor" href="#Maemo">Instalacja Tora na Maemo</a></h2>
15 
+    <br />
16 
+    <p>
17 
+    Jeśli macie urządzenie z Maemo, które nie jest <a href="#N900">N900</a>,
18 
+    zalecamy instalację paczki Tora ze <a
19 
+    href="http://maemo.org/packages/view/tor/">strony Maemo</a>. Projekt Tor nie
20 
+    produkuje tych paczek. Zajmuje się nimi społeczeństwo Maemo
21 
+    </p>
22 
+
23 
+    <a id="N900"></a>
24 
+    <h2><a class="anchor" href="#N900">Instalacja Tora na N900</a></h2>
25 
+    <br />
26 
+    <p>
27 
+    Następujące instrukcje powinny pomóc w instalacji <a
28 
+    href="https://garage.maemo.org/projects/tor-status">eksperymentalnego
29 
+    kontrolera Tora</a> i Tora spakowanych dla telefonu Nokia N900. W chwili
30 
+    obenej jest to niesprawdzona konfiguracja. Przeglądarka w tej konfiguracji
31 
+    nie ma Torbuttona i nie powinna obecnie być wykorzystywana do działań
32 
+    wymagających anonimowości o wysokim bezpieczeństwie.
33 
+    </p>
34 
+
35 
+    <p>
36 
+    Otwórz Menadżera aplikacji: <br /> <a href="../img/N900/1_app_menu.png">
37 
+    <img border="0" alt="menu aplikacji N900"
38 
+    src="../img/N900/1_app_menu-small.png"/> </a>
39 
+    </p>
40 
+
41 
+    <p>
42 
+    Kliknij na menu Menadżera aplikacji na górze ekranu: <br /> <a
43 
+    href="../img/N900/2_app_manager.png"> <img border="0" alt="N900 menadżer
44 
+    aplikacji" src="../img/N900/2_app_manager-small.png"/> </a>
45 
+    </p>
46 
+
47 
+    <p>
48 
+    Wybierz 'Katalogi Aplikacji': <br /> <a
49 
+    href="../img/N900/3_app_managermenu.png"> <img border="0" alt="katalogi
50 
+    aplikacji N900" src="../img/N900/3_app_managermenu-small.png"/> </a>
51 
+    </p>
52 
+
53 
+    <p>
54 
+    Wciśnij 'Nowy', by włączyć repozytorium maemo extras-devel. <br />
55 
+    <small>Uwaga: To repozytorium zawiera nieprzetestowane paczki, które mogą
56 
+    uszkodzić Twoje urządzenie. <br /> Zobacz <a
57 
+    href="http://wiki.maemo.org/Extras-devel">Extras-devel</a> po więcej
58 
+    szczegółów. Powinieneś/aś raczej wyłączyć extras-devel po instalacji Tora
59 
+    lub kontynuować na własne ryzyko.</small> <br /> <a
60 
+    href="../img/N900/4_catalog_list.png"> <img border="0" alt="lista katalogów
61 
+    N900" src="../img/N900/4_catalog_list-small.png"/> </a>
62 
+    </p>
63 
+
64 
+    <p>
65 
+    Wprowadź następujące informacje na ekranie dodawania katalogu:
66 
+    <p>
67 
+    <pre>
68 
+    Catalog name:    Extras devel
69 
+    Web address:    http://repository.maemo.org/extras-devel/
70 
+    Distribution:        fremantle
71 
+    Components:    free non-free
72 
+    </pre>
73 
+    </p>
74 
+    <br /> Sprawdź, czy 'Disabled' ('Wyłączone') jest niezaznaczone, wciśnij
75 
+    'Save' ('Zapisz'), i poczekaj na aktualizację listy pakietów. <br /> <a
76 
+    href="../img/N900/5_new_catalog.png"> <img border="0" alt="nowy katalog
77 
+    N900" src="../img/N900/5_new_catalog-small.png"/> </a>
78 
+    </p>
79 
+
80 
+    <p>
81 
+    Wciśnij 'Download' ('Pobierz') w Menadżerze aplikacji: <br /> <a
82 
+    href="../img/N900/6_app_manager.png"> <img border="0" alt="menadżer
83 
+    aplikacji N900" src="../img/N900/6_app_manager-small.png"/> </a>
84 
+    </p>
85 
+
86 
+    <p>
87 
+    Wybierz kategosię Sieć (lub wyszukaj Tora): <br /> <a
88 
+    href="../img/N900/7_app_categories.png"> <img border="0" alt="kategorie
89 
+    aplikacji N900" src="../img/N900/7_app_categories-small.png"/> </a>
90 
+    </p>
91 
+
92 
+    <p>
93 
+    Przewiń w dół i wybierz 'Tor Status Area Applet' ('Aplet Obszaru Statusu
94 
+    Tora): <br /> <a href="../img/N900/8_app_list.png"> <img border="0"
95 
+    alt="lista aplikacji N900" src="../img/N900/8_app_list-small.png"/> </a>
96 
+    </p>
97 
+
98 
+    <p>
99 
+    Zgódź się na warunki i wciśnij 'Continue' ('Kontynuuj'): <br /> <a
100 
+    href="../img/N900/9_disclaimer.png"> <img border="0" alt="warunki N900"
101 
+    src="../img/N900/9_disclaimer-small.png"/> </a>
102 
+    </p>
103 
+
104 
+    <p>
105 
+    Po instalacji wyłącz repozytorium extras-devel i ponownie uruchom
106 
+    urządzenie: <br /> <a href="../img/N900/10_success.png"> <img border="0"
107 
+    alt="sukces N900" src="../img/N900/10_success-small.png"/> </a>
108 
+    </p>
109 
+
110 
+    <p>
111 
+    Po ponownym uruchomieniu N900 otwórz menu statusu: <br /> <a
112 
+    href="../img/N900/11_after_rebooting.png"> <img border="0" alt="menu statusu
113 
+    N900 po ponownym uruchomieniu"
114 
+    src="../img/N900/11_after_rebooting-small.png"/> </a>
115 
+    </p>
116 
+
117 
+    <p>
118 
+    Wybierz 'The Onion Router' z listy: <br /> <a
119 
+    href="../img/N900/12_status_menu.png"> <img border="0" alt="wybór menu
120 
+    statusu N900" src="../img/N900/12_status_menu-small.png"/> </a>
121 
+    </p>
122 
+
123 
+    <p>
124 
+    Włącz trasowanie cebulowe (onion routing), i wciśnij 'Save' ('Zapisz'): <br
125 
+    /> <a href="../img/N900/13_enable_tor.png"> <img border="0" alt="N900 włącza
126 
+    Tora" src="../img/N900/13_enable_tor-small.png"/> </a>
127 
+    </p>
128 
+
129 
+    <p>
130 
+    Odwiedź <a href="https://check.torproject.org/">TorCheck</a>, by
131 
+    potwierdzić, że przekierowujesz ruch z przeglądarki przez Tora: <br /> <a
132 
+    href="../img/N900/14_check_tor.png"> <img border="0" alt="N900 sprawdza
133 
+    Tora" src="../img/N900/14_check_tor-small.png"/> </a>
134 
+    </p>
135 
+
136 
+    <p>
137 
+    Zauważ, że to nie zawsze może dać Ci najnowszą stabilną wersję Tora. W
138 
+    dodatku, przeglądarka N900 nie ma Torbutton. To oznacza, że podczas gdy może
139 
+    być przydatna do obchodzenia, to prawdopodobnie nie nadaje się do działań
140 
+    wymagających mocnej anonimowości w przeglądarce.
141 
+    </p>
142 
+
143 
+    <hr />
144 
+
145 
+    <p>Jeśli masz pomysły na ulepszenie tej strony, prosimy <a href="<page
146 
+    about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
147 
+  </div>
148 
+  <!-- END MAINCOL -->
149 
+  <div id = "sidecol">
150 
+#include "side.wmi"
151 
+#include "info.wmi"
152 
+  </div>
153 
+  <!-- END SIDECOL -->
154 
+</div>
155 
+<!-- END CONTENT -->
156 
+#include <foot.wmi>
docs/pl/debian-vidalia.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,117 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22269 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Vidalia: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian-vidalia>">Vidalia Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a> <a id="packages"></a>
14 
+    <h2><a class="anchor" href="#debian">Vidalia na Ubuntu lub Debianie</a></h2>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>Nie używajcie paczek ze wszechświata Ubuntu.</b> Nikt się nimi nie
19 
+    zajmuje i są przestarzałe. To oznacza, że będziecie pozbawieni poprawek
20 
+    stabilności i bezpieczeństwa.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    You'll need to set up our package repository before you can fetch
25 
+    Vidalia. First, you need to figure out the name of your distribution. If
26 
+    you're using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty",
27 
+    8.10 is "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's
28 
+    "etch", and Debian Lenny is "lenny". Then add this line to your
29 
+    <tt>/etc/apt/sources.list</tt> file:<br />
30 
+    <pre>
31 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
32 
+    </pre>
33 
+    w której wstawicie powyższą nazwę (etch, lenny, sid, karmic, jaunty,
34 
+    intrepid, hardy) w miejsce &lt;DISTRIBUTION&gt;.
35 
+    </p>
36 
+
37 
+    <p>
38 
+    Potem dodajcie klucz gpg wykorzystywany do podpisywania paczek, wykonując
39 
+    następujące komendy w linii poleceń:
40 
+    <pre>
41 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
42 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
43 
+    </pre>
44 
+    Teraz odświeżcie swoje źródła i zainstalujcie Vidalię, wykonując następujące
45 
+    komendy w linii poleceń:
46 
+    <pre>
47 
+    apt-get update
48 
+    apt-get install vidalia
49 
+    </pre>
50 
+    </p>
51 
+
52 
+    <p>
53 
+    Teraz Vidalia jest zainstalowana i działa. Przejdźcie do <a href="<page
54 
+    docs/tor-doc-unix>#polipo">kroku drugiego</a> w instrukcji "Vidalia na
55 
+    Linux/Unix".
56 
+    </p>
57 
+
58 
+    <p style="font-size: small">
59 
+    Nazwa DNS <code>deb.torproject.org</code> jest w rzeczywistości zestawem
60 
+    niezależnych serwerów skonfigurowanych w okrężnej struktuzre DNS. Jeśli z
61 
+    jakiegoś powodu nie macie do niego dostępu, możecie spróbować nazwy jednej z
62 
+    jej części. Wypróbujcie <code>deb-master.torproject.org</code>,
63 
+    <code>mirror.netcologne.de</code> lub <code>tor.mirror.youam.de</code>.
64 
+    </p>
65 
+
66 
+    <hr />
67 
+
68 
+    <a id="source"></a>
69 
+    <h2><a class="anchor" href="#source">Kompilacja ze źródeł</a></h2>
70 
+    <br />
71 
+
72 
+    <p>
73 
+    Jeśli chcecie kompilować własne deby ze źródeł, musicie najpierw dodać
74 
+    odpowiednią linię <tt>deb-src</tt> do <tt>sources.list</tt>.
75 
+    <pre>
76 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
77 
+    </pre>
78 
+    Musicie też zainstalować niezbędne pakiety, by budować własne deby i pakiety
79 
+    nezbędne do kompilacji Vidalii:
80 
+    <pre>
81 
+    apt-get install build-essential fakeroot devscripts qt4-dev-tools qt4-designer libqt4-dev g++ cmake
82 
+    apt-get build-dep vidalia
83 
+    </pre>
84 
+    Wtedy możecie skompilować Vidalię w ~/debian-packages:
85 
+    <pre>
86 
+    mkdir ~/debian-packages; cd ~/debian-packages
87 
+    apt-get source vidalia
88 
+    cd vidalia-*
89 
+    debuild -rfakeroot -uc -us
90 
+    cd ..
91 
+    </pre>
92 
+    Teraz możecie zainstalować nową paczkę:
93 
+    <pre>
94 
+    sudo dpkg -i vidalia_*.deb
95 
+    </pre>
96 
+    </p>
97 
+
98 
+    <p>
99 
+    Teraz Vidalia jest zainstalowana i działa. Przejdźcie do <a href="<page
100 
+    docs/tor-doc-unix>#polipo">kroku drugiego</a> w instrukcji "Vidalia na
101 
+    Linux/Unix".
102 
+    </p>
103 
+
104 
+    <hr />
105 
+
106 
+    <p>Jeśli macie pomysły na ulepszenie tej strony, prosimy <a href="<page
107 
+    about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
108 
+  </div>
109 
+  <!-- END MAINCOL -->
110 
+  <div id = "sidecol">
111 
+#include "side.wmi"
112 
+#include "info.wmi"
113 
+  </div>
114 
+  <!-- END SIDECOL -->
115 
+</div>
116 
+<!-- END CONTENT -->
117 
+#include <foot.wmi>
docs/pl/debian.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,184 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22268 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian>">Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <h2><a class="anchor" href="#debian">Opcja pierwsza: Tor na Debianie lenny,
15 
+    Debianie sid lub Debianie testing</a></h2>
16 
+    <br />
17 
+
18 
+    <p>
19 
+    If you're using Debian stable (lenny), unstable (sid), or testing (squeeze),
20 
+    just run<br />
21 
+    <tt>apt-get install tor tor-geoipdb</tt> as root.
22 
+    </p>
23 
+
24 
+    <p>
25 
+    Zauważ, że to nie zawsze może dać Ci najnowszą stabilną wersję Tora, ale
26 
+    będziesz otrzymywać ważne poprawki bezpieczeństwa. By upewnić się, że masz
27 
+    najnowszą stabilną wersję Tora, spójrz na opcję drugą poniżej.
28 
+    </p>
29 
+
30 
+    <p>
31 
+    Teraz Tor jest zainstalowany i działa. Przejdźcie do <a href="<page
32 
+    docs/tor-doc-unix>#polipo">kroku drugiego</a> w instrukcjach dla "Tora na
33 
+    Linux/Unix"
34 
+    </p>
35 
+
36 
+    <hr />
37 
+
38 
+    <a id="ubuntu"></a> <a id="packages"></a>
39 
+    <h2><a class="anchor" href="#ubuntu">Opcja druga: Tor na Ubuntu lub Debianie</a></h2>
40 
+    <br />
41 
+
42 
+    <p>
43 
+    <b>Nie używajcie paczek ze wszechświata Ubuntu.</b> Nikt się nimi nie
44 
+    zajmuje i są przestarzałe. To oznacza, że będziecie pozbawieni poprawek
45 
+    stabilności i bezpieczeństwa.
46 
+    </p>
47 
+
48 
+    <p>
49 
+    You'll need to set up our package repository before you can fetch
50 
+    Tor. First, you need to figure out the name of your distribution. If you're
51 
+    using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty", 8.10 is
52 
+    "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's "etch",
53 
+    and Debian Lenny is "lenny". Then add this line to your
54 
+    <tt>/etc/apt/sources.list</tt> file:<br />
55 
+    <pre>
56 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
57 
+    </pre>
58 
+    w której wstawicie powyższą nazwę kodową swojej dystrybucji (etch, lenny,
59 
+    sid, karmic, jaunty, intrepid, hardy czy cokolwiek to jest) w miejsce
60 
+    &lt;DISTRIBUTION&gt;.
61 
+    </p>
62 
+
63 
+    <p>
64 
+    Potem dodajcie klucz gpg wykorzystywany do podpisywania paczek, wykonując
65 
+    następujące komendy w linii poleceń:
66 
+    <pre>
67 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
68 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
69 
+    </pre>
70 
+    Teraz odświeżcie swoje źródła i zainstalujcie Tora, wykonując następujące
71 
+    komendy w linii poleceń:
72 
+    <pre>
73 
+    apt-get update
74 
+    apt-get install tor tor-geoipdb
75 
+    </pre>
76 
+    </p>
77 
+
78 
+    <p>
79 
+    Teraz Tor jest zainstalowany i działa. Przejdźcie do <a href="<page
80 
+    docs/tor-doc-unix>#polipo">kroku drugiego</a> w instrukcjach dla "Tora na
81 
+    Linux/Unix"
82 
+    </p>
83 
+
84 
+    <p style="font-size: small">
85 
+    Nazwa DNS <code>deb.torproject.org</code> jest w rzeczywistości zestawem
86 
+    niezależnych serwerów skonfigurowanych w okrężnej struktuzre DNS. Jeśli z
87 
+    jakiegoś powodu nie macie do niego dostępu, możecie spróbować nazwy jednej z
88 
+    jej części. Wypróbujcie <code>deb-master.torproject.org</code>,
89 
+    <code>mirror.netcologne.de</code> lub <code>tor.mirror.youam.de</code>.
90 
+    </p>
91 
+
92 
+    <hr />
93 
+
94 
+    <a id="development"></a>
95 
+    <h2><a class="anchor" href="#development">Opcja trzecia: Używanie gałęzi
96 
+    rozwojowej Tora na Debianie lub Ubuntu</a></h2>
97 
+    <br />
98 
+
99 
+    <p>If you want to use the <a href="<page download/download>#packagediff">development
100 
+    branch</a> of Tor instead (more features and more bugs), you need to add a
101 
+    different set of lines to your <tt>/etc/apt/sources.list</tt> file:<br />
102 
+    <pre>
103 
+    deb     http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
104 
+    deb     http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
105 
+    </pre>
106 
+    w których ponownie wpisujecie nazwę swojej dystrybucji (etch, lenny, sid,
107 
+    karmic, jaunty, intrepid, hardy) zamiast &lt;DISTRIBUTION&gt;.
108 
+    </p>
109 
+
110 
+    <p>
111 
+    Potem wykonajcie następujące komendy w linii poleceń:
112 
+    <pre>
113 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
114 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
115 
+    apt-get update
116 
+    apt-get install tor tor-geoipdb
117 
+    </pre>
118 
+    </p>
119 
+
120 
+    <p>
121 
+    Teraz Tor jest zainstalowany i działa. Przejdźcie do <a href="<page
122 
+    docs/tor-doc-unix>#polipo">kroku drugiego</a> w instrukcjach dla "Tora na
123 
+    Linux/Unix"
124 
+    </p>
125 
+
126 
+    <hr />
127 
+
128 
+    <a id="source"></a>
129 
+    <h2><a class="anchor" href="#source">Kompilacja ze źródeł</a></h2>
130 
+    <br />
131 
+
132 
+    <p>
133 
+    Jeśli chcecie kompilować własne deby ze źródeł, musicie najpierw dodać
134 
+    odpowiednią linię <tt>deb-src</tt> do <tt>sources.list</tt>.
135 
+    <pre>
136 
+    # For the stable version.
137 
+    # For the unstable version.
138 
+
139 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
140 
+
141 
+
142 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
143 
+    deb-src http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
144 
+    </pre>
145 
+    Musicie też zainstalować niezbędne pakiety, by budować własne deby i pakiety
146 
+    nezbędne do kompilacji Tora:
147 
+    <pre>
148 
+    apt-get install build-essential fakeroot devscripts
149 
+    apt-get build-dep tor
150 
+    </pre>
151 
+    Wtedy możecie skompilować Tora w ~/debian-packages:
152 
+    <pre>
153 
+    mkdir ~/debian-packages; cd ~/debian-packages
154 
+    apt-get source tor
155 
+    cd tor-*
156 
+    debuild -rfakeroot -uc -us
157 
+    cd ..
158 
+    </pre>
159 
+    Teraz możecie zainstalować nową paczkę:
160 
+    <pre>
161 
+    sudo dpkg -i tor_*.deb
162 
+    </pre>
163 
+    </p>
164 
+
165 
+    <p>
166 
+    Teraz Tor jest zainstalowany i działa. Przejdźcie do <a href="<page
167 
+    docs/tor-doc-unix>#polipo">kroku drugiego</a> w instrukcjach dla "Tora na
168 
+    Linux/Unix"
169 
+    </p>
170 
+
171 
+    <hr />
172 
+
173 
+    <p>Jeśli macie pomysły na ulepszenie tej strony, prosimy <a href="<page
174 
+    about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
175 
+  </div>
176 
+  <!-- END MAINCOL -->
177 
+  <div id = "sidecol">
178 
+#include "side.wmi"
179 
+#include "info.wmi"
180 
+  </div>
181 
+  <!-- END SIDECOL -->
182 
+</div>
183 
+<!-- END CONTENT -->
184 
+#include <foot.wmi>
docs/pl/rpms.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,86 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21907 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: CentOS/Fedora/OpenSUSE Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/rpms>">RPMs</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="rpms"></a>
14 
+    <h2><a class="anchor" href="#rpms">PAczki Tora dla dystrybucji Linuksa opartych
15 
+    na RPM.</a></h2>
16 
+    <br />
17 
+
18 
+    <p>Nie używajcie paczek z natywnych repozytoriów. Są często przestarzałe. To
19 
+    oznacza, że będziecie pozbawieni poprawek stabilności i bezpieczeństwa.
20 
+    </p>
21 
+
22 
+    <p>
23 
+    Musicie skonfigurować nasze repozytorium z paczkami, zanim będziecie mogli
24 
+    pobrać Tora. Zakładając, że macie program yum, w katalogu /etc/yum.repos.d/
25 
+    stwórzcie plik o nazwie torproject.repo. Otwórzcie go w edytorze i wpiszcie
26 
+    następujące informacje:
27 
+    <pre>[torproject]
28 
+    name=Tor and Vidalia
29 
+    enabled=1
30 
+    autorefresh=0
31 
+    baseurl=http://deb.torproject.org/torproject.org/rpm/DISTRIBUTION/
32 
+    type=rpm-md
33 
+    gpgcheck=1
34 
+    gpgkey=http://deb.torproject.org/torproject.org/rpm/RPM-GPG-KEY-torproject.org
35 
+    </pre>
36 
+
37 
+    Jeśli chcecie być na bieżąco z wersjami stabilnymi Tora, powinniście zmienić
38 
+    DISTRIBUTION na jedno z następujących: centos4, centos5, fc10, fc11, fc12,
39 
+    suse</p>
40 
+
41 
+    <p>Jeśli chcecie być na bieżąco z wersjami eksperymentalnymi, zmieńcie
42 
+    DISTRIBUTION na jedno z następujących: centos4-experimental,
43 
+    centos5-experimental, fc10-experimental, fc11-experimental,
44 
+    fc12-experimental, suse-experimental</p>
45 
+
46 
+    <p>
47 
+    Teraz Tor jest zainstalowany i działa. Przejdźcie do <a href="<page
48 
+    docs/tor-doc-unix>#polipo">kroku drugiego</a> w instrukcjach dla "Tora na
49 
+    Linux/Unix"
50 
+    </p>
51 
+
52 
+    <p style="font-size: small">
53 
+    Nazwa DNS <code>deb.torproject.org</code> jest w rzeczywistości zestawem
54 
+    niezależnych serwerów skonfigurowanych w okrężnej struktuzre DNS. Jeśli z
55 
+    jakiegoś powodu nie macie do niego dostępu, możecie spróbować nazwy jednej z
56 
+    jej części. Wypróbujcie <code>deb-master.torproject.org</code>,
57 
+    <code>mirror.netcologne.de</code> lub <code>tor.mirror.youam.de</code>.
58 
+    </p>
59 
+
60 
+    <hr />
61 
+
62 
+    <hr />
63 
+
64 
+    <a id="source"></a>
65 
+    <h2><a class="anchor" href="#source">Kompilacja ze źródeł</a></h2>
66 
+    <br />
67 
+
68 
+    <p>
69 
+    Jeśli chcecie kompilować ze źródeł, postępujcie zgodnie z <a
70 
+    href="<gitblob>doc/tor-rpm-creation.txt">instrukcjami tworzenia rpm</a>.
71 
+    </p>
72 
+
73 
+    <hr />
74 
+
75 
+    <p>Jeśli macie pomysły na ulepszenie tej strony, prosimy <a href="<page
76 
+    about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
77 
+  </div>
78 
+  <!-- END MAINCOL -->
79 
+  <div id = "sidecol">
80 
+#include "side.wmi"
81 
+#include "info.wmi"
82 
+  </div>
83 
+  <!-- END SIDECOL -->
84 
+</div>
85 
+<!-- END CONTENT -->
86 
+#include <foot.wmi>
docs/pl/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/pl/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,210 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Uruchamianie klienta <a href="<page index>">Tor</a> na Mac OS X</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    To są instrukcje do instalacji klienta Tora na systemie Mac OS X. Jeśli
18 
+    chcesz przekazywać ruch innych, by wspomóc rozwój sieci (prosimy),
19 
+    przeczytaj poradnik o <a href="<page docs/tor-doc-relay>">Konfigurowaniu
20 
+    przekaźnika sieci Tor</a>.
21 
+    </p>
22 
+
23 
+    <hr />
24 
+    <a id="installing"></a>
25 
+    <h2><a class="anchor" href="#installing">Krok 1: Pobranie i instalacja Tora</a></h2>
26 
+    <br />
27 
+
28 
+    <p>
29 
+    The install for Macintosh OS X bundles <a href="<page index>">Tor</a>, <a
30 
+    href="<page projects/vidalia>">Vidalia</a> (a graphical interface for Tor), <a
31 
+    href="<page projects/torbutton>">Torbutton</a>, and <a
32 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (a web
33 
+    proxy)  into one package, with the four applications pre-configured to work
34 
+    together.  Download either the <a
35 
+    href="../<package-osx-bundle-stable>">stable</a> or the <a
36 
+    href="../<package-osx-bundle-alpha>">experimental</a> version of the OS X
37 
+    bundle for Intel, or look for more options on the <a href="<page
38 
+    download/download>">download page</a>.
39 
+    </p>
40 
+
41 
+    <p>Po pobraniu dmg, kliknij go dwukrotnie i pozwól, by się zamontował. Przejdź
42 
+    do teraz otwartej paczki Vidalia (Vidalia Bundle) w Finderze. Paczkę łatwo
43 
+    jest zainstalować; po prostu przenieś i upuść cebulową ikonę Vidalii do
44 
+    folderu Aplikacji. Opcjonalnie, kliknij dwukrotnie skrypt "install
45 
+    torbutton", by zainstalować Torbutton do Firefoksa. Możesz też pobrać
46 
+    Torbuttona ze strony z dodatkami Mozilli, wyszukując "torbutton".</p>
47 
+
48 
+    <p>Po zakończeniu instalacji możesz uruchomić program Vidalia poprzez wybranie
49 
+    jego ikony z twojego folderu Aplikacji. Ciemna cebula z czerwonym krzyżykiem
50 
+    na pasku oznacza, że w tej chwili Tor nie jest uruchomiony. Możesz uruchomić
51 
+    Tora wybierając Start z menu "Tor" u góry ekranu.
52 
+    </p>
53 
+
54 
+    <p>Gdy Tor działa, ikonka programu Vidalia wygląda następująco:
55 
+    </p>
56 
+
57 
+    <p><img alt="vidalia running tor"
58 
+    src="../img/screenshot-osx-vidalia.png"
59 
+    border="1"/></p>
60 
+
61 
+    <p>Polipo jest instalowane jako część pakietu Tora. Po jego instalacji,
62 
+    uruchomi się automatycznie po restarcie komputera. Nie musisz konfigurować
63 
+    Polipo, by używało Tora &mdash; odpowiednia konfiguracja Polipo została
64 
+    zainstalowana jako część pakietu instalacyjnego.
65 
+    </p>
66 
+
67 
+    <hr />
68 
+    <a id="using"></a>
69 
+    <h2><a class="anchor" href="#using">Krok 2: Konfiguracja aplikacji, by używały
70 
+    Tora</a></h2>
71 
+    <br />
72 
+
73 
+    <p>Po instalacji musisz skonfigurować swoje aplikacje, by ich
74 
+    używały. Pierwszym krokiem jest ustawienie sposobu przeglądania sieci WWW.</p>
75 
+
76 
+    <p>Powinieneś/aś używać Tora z Firefoksem i Torbuttonem, dla najlepszego
77 
+    bezpieczeństwa. Torbutton został zainstalowany za Ciebie. Kliknij na
78 
+    czerwony przycisk "Tor Disabled" ("Tor wyłączony"), by włączyć Tora i
79 
+    gotowe: </p>
80 
+
81 
+    <p><img alt="Torbutton plugin for Firefox"
82 
+    src="../img/screenshot-torbutton.png"
83 
+    border="1"/></p>
84 
+
85 
+    <p>
86 
+    Jeśli masz zamiar używać Firefoksa na innym komputerze niż tam, gdzie jest
87 
+    Tor, spójrz na <a
88 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">wpis
89 
+    w FAQ na temat uruchamiania Tora na innym komputerze</a>.
90 
+    </p>
91 
+
92 
+    <p>By "storyfikować" inne aplikacje, które używają proxy dla HTTP, po prostu
93 
+    skieruj je na Polipo (czyli localhost, port 8118). By aplikacje bezpośrednio
94 
+    używały serwera SOCKS (do komunikatorów, Jabbera, IRC, itp.), możesz
95 
+    skierować je bezpośrednio na Tora (localhost, port 9050), ale przeczytaj <a
96 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">ten
97 
+    wpis do FAQ</a>, dlaczego to może być niebezpieczne. Jeśli aplikacja nie
98 
+    obsługuje ani proxy dla HTTP, ani dla SOCKS, spójrz na  <a
99 
+    href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a> lub <a
100 
+    href="http://www.dest-unreach.org/socat/">socat</a>.</p>
101 
+
102 
+    <p>Po informacje, jak "storyfikować" inne aplikacje, spójrz na <a
103 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
104 
+    HOWTO</a>.
105 
+    </p>
106 
+
107 
+    <hr />
108 
+    <a id="verify"></a>
109 
+    <h2><a class="anchor" href="#verify">Krok 3: Upewnij się, że wszystko działa</a></h2>
110 
+    <br />
111 
+
112 
+    <p>
113 
+    Teraz powinieneś spróbować użyć swojej przeglądarki z Torem i upewnić się,
114 
+    że Twój adres IP jest anonimizowany. Kliknij na <a
115 
+    href="https://check.torproject.org/">wykrywacz Tora</a> i sprawdź, cze jego
116 
+    zdaniem używasz Tora czy nie. (Jeśli ta strona akurat nie działa, przeczytaj
117 
+    <a
118 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">ten
119 
+    wpis w FAQ</a>, by poznać więcej sposobów na testowanie swojego Tora.)
120 
+    </p>
121 
+
122 
+    <p>Jeśli masz zaporę ogniową, która ogranicza możliwości Twojego komputera co
123 
+    do łączenia się z samym sobą, zezwól w niej na połączenia od programów
124 
+    lokalnych na porty lokalne 8118 i 9050. Jeśli zapora blokuje połączenia
125 
+    wychodzące, spraw, by można się było połączyć choć z portami 80 i 433, po
126 
+    czym przeczytaj <a
127 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">ten
128 
+    wpis do FAQ</a>.
129 
+    </p>
130 
+
131 
+    <p>Jeśli dalej nie działa, spójrz na <a
132 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">ten
133 
+    wpis FAQ</a>, by poszukać wskazówek.</p>
134 
+
135 
+    <p>
136 
+    Gdy Tor już działa, poczytaj o tym, <a href="<page download/download>#Warning">co Tor
137 
+    oferuje, a czego nie</a>.
138 
+    </p>
139 
+
140 
+    <hr />
141 
+    <a id="server"></a> <a id="relay"></a>
142 
+    <h2><a class="anchor" href="#relay">Krok 4: Konfiguracja Tora jako przekaźnika
143 
+    sieci</a></h2>
144 
+    <br />
145 
+
146 
+    <p>Sieć Tora polega na ochotnikach oddających część swojego łącza. Im więcej
147 
+    ludzi uruchomi przekaxnik sieci, tym szybsza będzie sieć Tora. Jeśli masz co
148 
+    najmniej 20 kilobajtów/s w obie strony, pomóż Torowi, konfigurując swojego
149 
+    klienta tak, by był także przekaźikiem sieci. Mamy wiele cech, które czynią
150 
+    przekaźniki Tora łatwymi i wygodnymi, łącznie z ograniczeniem
151 
+    przepustowości, politykami wyjścia, byś mógł zmniejszyć ryzyko skarg, oraz
152 
+    obsługą dynamicznych adresów IP.</p>
153 
+
154 
+    <p>Posiadanie przekaźników w wielu różnych miejscach w sieci sprawia, że
155 
+    użytkownicy Tora są bezpieczni. <a
156 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Ty
157 
+    też możesz mieć lepszą anonimowość</a>, gdyż serwery, do których się
158 
+    łączysz, nie mogą stwierdzić, czy połączenie pochodzi z Twojego komputera,
159 
+    czy zostało przekierowane z innych.</p>
160 
+
161 
+    <p>Przeczytaj szczegóły w naszym przewodniku <a href="<page
162 
+    docs/tor-doc-relay>">Konfiguracji przekaźnika sieci Tor</a>.</p>
163 
+
164 
+    <hr />
165 
+    <a id="uninstall"></a>
166 
+    <h2><a class="anchor" href="#uninstall">Jak odinstalować Tora i Privoxy</a></h2>
167 
+    <br />
168 
+
169 
+    <p>Są dwa sposoby na odinstalowanie paczki z komputera, z wykorzystaniem
170 
+    Findera albo poprzez program odinstalowujący uruchamiany z linii poleceń
171 
+    (Terminala). Jeśli chcesz usunąć Tora z systemu OSX, oto jak to zrobić:</p>
172 
+
173 
+    <p>Przywróć ustawienia Proxy w aplikacjach do ich poprzednich wartości. Jeśli
174 
+    chcesz tylko przestać używać Tora, możesz przerwać na tym kroku.</p>
175 
+
176 
+    <p>Jeśli chcesz całkowicie usunąć Tora, a twoje konto ma prawa Administratora,
177 
+    wykonaj co następuje:</p>
178 
+
179 
+    <ol>
180 
+    <li>Otwórz Findera i kliknij Aplikacje.</li>
181 
+    <li>Przeciągnij /Applications/Vidalia do Kosza.</li>
182 
+    <li>Usuń /Library/Torbutton z systemu.</li>
183 
+    <li>W swoim katalogu domowym przejdź do Library, usuń katalog Vidalia</li>
184 
+    </ol>
185 
+
186 
+    <p>Tor, Vidalia i Polipo są teraz całkowicie usunięte z systemu.</p>
187 
+
188 
+    <p>Jeśli znasz linię poleceń lub Terminal, możesz ręcznie usunąć następujące
189 
+    elementy:</p>
190 
+    <ul>
191 
+    <li>/Applications/Vidalia.app/</li>
192 
+    <li>/Library/Torbutton/</li>
193 
+    <li>~/Library/Vidalia</li>
194 
+    <li>~/.tor</li>
195 
+    </ul>
196 
+
197 
+    <hr />
198 
+
199 
+    <p>Jeśli masz pomysły na ulepszenie tej strony, prosimy <a href="<page
200 
+    about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
201 
+  </div>
202 
+  <!-- END MAINCOL -->
203 
+  <div id = "sidecol">
204 
+#include "side.wmi"
205 
+#include "info.wmi"
206 
+  </div>
207 
+  <!-- END SIDECOL -->
208 
+</div>
209 
+<!-- END CONTENT -->
210 
+#include <foot.wmi>
docs/pl/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,319 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Konfiguracja przekaźnika Tora</h1>
14 
+
15 
+
16 
+    <!-- BEGIN SIDEBAR -->
17 
+    <div class="sidebar-left">
18 
+    <h3>Kroki konfiguracji</h3>
19 
+    <ol>
20 
+    <li><a href="<page docs/tor-doc-relay>#install">Pobieranie i instalacja</a></li>
21 
+    <li><a href="<page docs/tor-doc-relay>#setup">Konfiguracja</a></li>
22 
+    <li><a href="<page docs/tor-doc-relay>#check">Sprawdzenie i Potwierdzenie</a></li>
23 
+    <li><a href="<page docs/tor-doc-relay>#after">Ostatnie kroki</a></li>
24 
+    </ol>
25 
+    </div>
26 
+
27 
+
28 
+    <!-- END SIDEBAR -->
29 
+    <hr />
30 
+
31 
+    <p>
32 
+    Sieć Tora polega na ochotnikach oddających część swojego łącza. Im więcej
33 
+    ludzi uruchomi przekaźnik, tym szybsza będzie sieć Tora. Jeśli masz co
34 
+    najmniej 20 kilobajtów/s w obie strony, pomóż Torowi, konfigurując swojego
35 
+    klienta tak, by był także przekaźnikiem sieci. Mamy wiele cech, które czynią
36 
+    przekaźniki Tora łatwymi i wygodnymi, łącznie z <a href="<page
37 
+    docs/faq>#RelayFlexible">ograniczeniem przepustowości, politykami wyjścia, byś
38 
+    mógł zmniejszyć ryzyko skarg, oraz obsługą dynamicznych adresów IP</a>.
39 
+    </p>
40 
+
41 
+    <p>Możesz uruchomić przekaźnik sieci Tora na <a
42 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">prawie
43 
+    każdym</a> systemie operacyjnym. Przekaźniki Tora działają najlepiej na
44 
+    systemach Linux, OS X Tiger lub późniejszym, FreeBSD 5.x+, NetBSD 5.x+ oraz
45 
+    Windows Server 2003 lub późniejszym.
46 
+    </p>
47 
+
48 
+    <hr /> <a id="zero"></a> <a id="install"></a>
49 
+    <h2><a class="anchor" href="#install">Krok 1: Pobranie i instalacja Tora</a></h2>
50 
+    <br />
51 
+
52 
+    <p>Zanim zaczniesz, upewnij się, że Tor jest uruchomiony i działa.
53 
+    </p>
54 
+
55 
+    <p>Odwiedź naszą <a href="<page download/easy-download>">stronę pobierania</a> i
56 
+    zainstaluj "Paczkę Instalacyjną" dla swojego systemu.
57 
+    </p>
58 
+
59 
+    <p>Jeśli uznasz to za wygodne, możesz najpierw poużywać Tora jako klienta przez
60 
+    jakiś czas, by upewnić się, czy rzeczywiście działa.</p>
61 
+
62 
+    <hr /> <a id="setup"></a>
63 
+    <h2><a class="anchor" href="#setup">Krok 2: Ustawienie Tora jako przekaźnika
64 
+    sieci</a></h2>
65 
+    <br />
66 
+    <ol>
67 
+    <li>Sprawdź, czy twój zegar i strefa czasowa są dobrze ustawione. Jeśli jest to
68 
+    możliwe, zsynchronizuj swój zegar z publicznymi <a
69 
+    href="http://en.wikipedia.org/wiki/Network_Time_Protocol">serwerami
70 
+    czasu</a>.
71 
+    </li>
72 
+
73 
+    <li><strong>Konfiguracja Tora z Interfejsem Graficznym Vidalia</strong>:
74 
+    <ol>
75 
+
76 
+    <li>
77 
+    	<dt>Kliknij prawym klawiszem na ikonkę Vidalii w zasobniku systemowym. Wybierz
78 
+    <tt>Control Panel</tt> (Panel sterowania).</dt>
79 
+    	<dd><img alt="vidalia right click menu"
80 
+    src="../img/screenshot-win32-vidalia.png"></dd>
81 
+    </li>
82 
+
83 
+    <li>Klinkij <tt>Setup Relaying</tt> (Uruchomienie przekazywania).</li>
84 
+
85 
+    <li>
86 
+    	<dt>Wybierz <tt>Relay Traffic for the Tor network</tt> (Przekazuj ruch dla sieci
87 
+    Tor), jeśli chcesz być publicznym przekaźnikiem (zalecane), lub wybierz
88 
+    		<tt>Help censored users reach the Tor network</tt> (Pomóż cenzorowanym
89 
+    użytkownikom dostać się do sieci Tora), jeśli chcesz być <a href="<page
90 
+    docs/faq>#RelayOrBridge">mostkiem</a> dla użytkowników w krajach cenzurujących
91 
+    swój Internet.</dt>
92 
+    <dd><img alt="vidalia basic settings"
93 
+    src="../img/screenshot-win32-configure-relay-1.png"></dd>
94 
+    </li>
95 
+
96 
+    <li>Wprowadź nazwę dla swojego przekaźnika i wprowadź informacje kontaktowe, w
97 
+    razie gdybyśmy musieli skontaktować się z Tobą w przypadku problemów.</li>
98 
+
99 
+    <li>Zostaw <tt>Attempt to automatically configure port forwarding</tt> (Spróbuj
100 
+    automatycznie skonfigurować przekazywanie portów) włączone. Wciśnij przycisk
101 
+    <tt>Test</tt>, by sprawdzić, czy to działa. Jeśli tak, to wspaniale. Jeśli
102 
+    nie, spójrz na punkt numer 3 poniżej.</li>
103 
+
104 
+    <li><dt>Wybierz kartę <tt>Bandwidth Limits</tt> (Ograniczenia łącza). Określ, ile z
105 
+    przepustowości łącza chcesz dać uzytkownikom Tora, takim jak Ty.</dt>
106 
+    <dd><img alt="vidalia bandwidth limits"
107 
+    src="../img/screenshot-win32-configure-relay-2.png"></dd>
108 
+    </li>
109 
+
110 
+    <li><dt>Wybierz kartę <tt>Exit Policies</tt> (Polityki wyjścia). Jeśli chcesz, by
111 
+    inni mogli używać Twojego przekaźnika dla tych usług, nie zmieniaj
112 
+    niczego. Wyłącz te usługi, co do których nie chcesz, by były osiągalne przez
113 
+    ludzi z <a href="<page docs/faq>#ExitPolicies">Twojego przekaźnika</a>. Jeśli
114 
+    chcesz być przekaźnikiem nie-wyjściowym, wyłącz wszystkie usługi.</dt>
115 
+    <dd><img alt="vidalia exit policies"
116 
+    src="../img/screenshot-win32-configure-relay-3.png"></dd>
117 
+    </li>
118 
+
119 
+    <li>Kliknij przycisk <tt>Ok</tt>. Spójrz na krok 3 poniżej w celu potwierdzenia,
120 
+    że przekaźnik działa prawidłowo.</li>
121 
+    </ol>
122 
+
123 
+    <br /> <strong>Konfiguracja ręczna</strong>:
124 
+    <ul>
125 
+    <li>Wyedytuj dolną część <a
126 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">swojego
127 
+    pliku torrc</a>.) Jeśli chcesz być publicznym przekaźnikiem (zalecane),
128 
+    upewnij się, że podałeś ORPort i <a href="<page docs/faq>#ExitPolicies">sprawdź
129 
+    ExitPolicy</a>; w innym przypadku, jeśli chcesz być <a href="<page
130 
+    docs/faq>#RelayOrBridge">mostkiem</a> dla użytkowników w krajach cenzurujących
131 
+    swój Internet, skorzystaj z <a href="<page docs/bridges>#RunningABridge">tych
132 
+    linii</a>.
133 
+    </li>
134 
+
135 
+    </ul></li>
136 
+
137 
+    <li>Jeśli używasz zapory ogniowej, otwórz w niej przejście, by połączenia
138 
+    przychodzące mogły dostać się do skonfigurowanych portów (ORPort, plus
139 
+    DirPort, jeśli go włączyłeś). Jeśli masz firewall sprzętowy (Linksys, modem
140 
+    kablowy, itd), może spodobać Ci się <a
141 
+    href="http://portforward.com/">portforward.com</a>. Upewnij się też, że
142 
+    dozwolone są też wszystkie połączenia <em>wychodzące</em>, aby twój
143 
+    przekaźnik mógł dotrzeć do innych przekaźników Tora.
144 
+    </li>
145 
+
146 
+    <li>Uruchom ponownie swój przekaźnik. Jeśli <a
147 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">wypisze
148 
+    jakieś ostrzeżenia</a>, zajmij się nimi.
149 
+    </li>
150 
+
151 
+    <li>Zapisz się na listę mailingową <a
152 
+    href="http://archives.seul.org/or/announce/">or-announce</a>. Ma ona mały
153 
+    ruch, dzięki niej będziesz informowany o nowych stabilnych wydaniach. Możesz
154 
+    także zapisać się na <a href="<page docs/documentation>#MailingLists">listy Tora
155 
+    o większym ruchu</a>.
156 
+    </li>
157 
+
158 
+    </ol>
159 
+
160 
+    <hr /> <a id="check"></a>
161 
+    <h2><a class="anchor" href="#check">Krok 3: Sprawdzenie, czy wszystko działa</a></h2>
162 
+    <br />
163 
+
164 
+    <p>Jak tylko twój przekaźnik zdoła połączyć się z siecią, spróbuje określić,
165 
+    czy skonfigurowane porty są dostępne z zewnątrz. Ten krok jest zazwyczaj
166 
+    szybki, ale może potrwać do 20 minut. Szukaj <a
167 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">wpisów
168 
+    do logów</a> w postaci <tt>Self-testing indicates your ORPort is reachable
169 
+    from the outside. Excellent.</tt> Jeśli nie widzisz tej wiadomości, to
170 
+    znaczy, że twój przekaźnik nie jest osiągalny z zewnątrz &mdash;
171 
+    powinieneś/aś ponownie sprawdzić ustawienia zapory ogniowej, zobaczyć, czy
172 
+    sprawdza ten IP i port, który powinien sprawdzać etc.
173 
+    </p>
174 
+
175 
+    <p>When it decides that it's reachable, it will upload a "server descriptor" to
176 
+    the directories, to let clients know what address, ports, keys, etc your
177 
+    relay is using. You can <a
178 
+    href="http://194.109.206.212/tor/status-vote/current/consensus">load one of
179 
+    the network statuses manually</a> and look through it to find the nickname
180 
+    you configured, to make sure it's there. You may need to wait up to one hour
181 
+    to give enough time for it to make a fresh directory.</p>
182 
+
183 
+    <hr /> <a id="after"></a>
184 
+    <h2><a class="anchor" href="#after">Krok 4: Gdy już wszystko działa</a></h2>
185 
+    <br />
186 
+
187 
+    <p>
188 
+    Polecamy też następujące kroki:
189 
+    </p>
190 
+
191 
+    <p>
192 
+    6. Przeczytaj <a
193 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">o
194 
+    zabezpieczaniu działania</a>, by dowiedzieć się, jak możesz podnieść
195 
+    bezpieczeństwo swojego przekaźnika.
196 
+    </p>
197 
+
198 
+    <p>
199 
+    7. Jeśli chcesz prowadzić więcej niż jeden przekaźnik, to wspaniale, ale
200 
+    prosimy o ustawienie <a
201 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">opcji
202 
+    MyFamily</a> w plikach konfiguracyjnych wszystkich Twoich przekaźników.
203 
+    </p>
204 
+
205 
+    <p>
206 
+    8. Pomyśl o ograniczaniu przepustowości łącza. Użytkownicy sieci kablowych,
207 
+    DSL oraz inni z asymetrycznym łączem (np. większy download niż upload)
208 
+    powinni ograniczyć przepustowość Tora do tej mniejszej wartości, by uniknąć
209 
+    zatorów. Przeczytaj <a
210 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">wpis
211 
+    do FAQ na temat ograniczania przepustowości</a>.
212 
+    </p>
213 
+
214 
+    <p>
215 
+    9. Zrób kopię zapasową prywatnego klucza swojego przekaźnika
216 
+    (przechowywanego w "keys/secret_id_key" w katalogu DataDirectory). To jest
217 
+    "tożsamość" Twojego przekaźnika i musisz trzymać ją w bezpiecznym miejscu,
218 
+    by nikt nie mógł podsłuchać ruchu, który przechodzi przez Twój
219 
+    przekaźnik. To jest najważniejszy plik do zachowania w przypadku, gdy musisz
220 
+    <a
221 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeRelay">przenieść
222 
+    lub odbudować swój przekaźnik Tora</a> jeśli coś pójdzie nie tak.
223 
+    </p>
224 
+
225 
+    <p>
226 
+
227 
+    10. Jeśli kontrolujesz serwery nazw w swojej domenie, rozważ ustawienie
228 
+    swojej nazwy hosta w odwrotnym DNSie na 'anonymous-relay' lub 'proxy' lub
229 
+    'tor-proxy', aby inni mogli szybciej zrozumieć co się dzieje, gdy zobaczą
230 
+    twój adres w swoich logach. Dodanie <a
231 
+    href="https://tor-svn.freehaven.net/svn/tor/trunk/contrib/tor-exit-notice.html">infomracji
232 
+    o punkcie wyjścia z Tora</a> na wirtualnym hoście dla tej nazwy może bardzo
233 
+    pomóc w razie skarg o nadużycia kierowanych do Ciebie lub Twojego ISP, jeśli
234 
+    prowadzisz węzeł wyjściowy Tora.
235 
+
236 
+    </p>
237 
+
238 
+    <p>
239 
+    11. Jeśli na twoim komputerze nie ma serwera WWW, rozważ zmianę portu ORPort
240 
+    na 443, a portu katalogowego DirPort na 80. Wielu z użytkowników Tora jest
241 
+    za zaporami ogniowymi, które pozwalają tylko przeglądać sieć WWW, ta zmiana
242 
+    pozwoli takim użytkownikom połączyć się z Twoim przekaźnikiem. Operatorzy
243 
+    przekaźników pod Win32 mogą po prostu bezpośrednio zmienić swój ORPort i
244 
+    DirPort w pliku torrc i ponownie uruchomić Tora. Przekaźniki pod OS X i Unix
245 
+    nie mogą bezpośrednio podłączyć się do tych portów (gdyż nie są uruchamiane
246 
+    jako root), więc dla nich trzeba uruchomić jakieś <a
247 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">przekierowanie
248 
+    portów</a>, by połączenia mogły do nich dotrzeć. Jeśli już używasz portów 80
249 
+    i 443, ale i tak chcesz pomóc, to innymi użytecznymi portami są 22, 110 i
250 
+    143.
251 
+    </p>
252 
+
253 
+    <p>
254 
+    12. Jeśli twój przekaźnik sieci Tora ma też inne usługi na tym samym adresie
255 
+    IP &mdash; jak na przykład publiczny serwer WWW &mdash; upewnij się, że
256 
+    połączenia do tego serwera są dozwolone także z tego samego
257 
+    komputera. Musisz zezwolić na te połączenia, gdyż klienci Tora odkryją, że
258 
+    Twój przekaźnik Tora jest <a
259 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">najbezpieczniejszą
260 
+    drogą do połączenia się z tym serwerem</a>, i zawsze zbudują obwód, który
261 
+    będzie kończył się na Twoim przekaźniku. Jeśli nie chcesz zezwalać na takie
262 
+    połączenia, musisz jawnie wykluczyć je w swojej polityce wyjścia.
263 
+    </p>
264 
+
265 
+    <p>
266 
+    13. (Tylko Unix). Utwórz osobnego użytkownika, na którego prawach będzie
267 
+    uruchamiany przekaźnik. Jeśli zainstalowałeś paczkę OS X lub deb lub rpm, to
268 
+    wszystko już jest zrobione. W innym przypadku możesz zrobić to
269 
+    ręcznie. (Przekaźnik Tora nie musi być uruchamiany jako root, więc dobrze
270 
+    jest nie uruchamiać go jako root. Uruchamianie jako użytkownik 'tor' unika
271 
+    problemów z indent i innymi usługami, które sprawdzają nazwę
272 
+    użytkownika. Jeśli jesteś paranoikiem, możesz śmiało <a
273 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">umieścić
274 
+    Tora w chrootowanym środowisku</a>.)
275 
+    </p>
276 
+
277 
+    <p>
278 
+    14. (Tylko Unix) Twój system operacyjny prawdopodobnie ogranicza liczbę
279 
+    otwartych deskryptorów plików dla każdego procesu do 1024 (lub nawet
280 
+    mniej). Jeśli planujesz uruchomienie szybkiego węzła wyjściowego, to ta
281 
+    ilość prawdopodobnie nie wystarczy. W systemie Linux powinieneś dodać linię
282 
+    postaci "toruser hard nofile 8192" do swojego pliku
283 
+    /etc/security/limits.conf (gdzie toruser oznacza użytkownika, na którego
284 
+    prawach uruchomiony jest Tor), po czym ponownie uruchomić Tora, jeśli jest
285 
+    zainstalowany jako pakiet (lub wylogować się i zalogować ponownie, jeśli
286 
+    uruchamiasz go sam).
287 
+    </p>
288 
+
289 
+    <p>
290 
+    15. Jeśli zainstalowałeś Tora z jakiejś paczki lub instalatora,
291 
+    prawdopodobnie uruchamia to Tora automatycznie w czasie ładowania
292 
+    systemu. Ale jeśli instalowałeś ze źródeł, to mogą ci się przydać skrypty
293 
+    inicjalizacyjne contrib/tor.sh lub contrib/torctl.
294 
+    </p>
295 
+
296 
+    <p>
297 
+    Gdy zmieniasz konfigurację Tora, pamiętaj sprawdzić, czy Twój przekaźnik
298 
+    dalej działa po tych zmianach. Ustaw w pliku torrc opcję "ContactInfo",
299 
+    byśmy mogli się z Tobą skontaktować, jeśli powinieneś zainstalować nowszą
300 
+    wersję lub coś działa nie tak. Jeśli masz jakieś problemy lub pytania,
301 
+    przeczytaj sekcję the <a href="<page docs/documentation>#Support">Uzyskiwanie
302 
+    pomocy</a> lub <a href="<page about/contact>">skontaktuj się z nami</a> na liście
303 
+    tor-ops. Dziękujemy, że pomagasz rosnąć sieci Tora!
304 
+    </p>
305 
+
306 
+    <hr />
307 
+
308 
+    <p>Jeśli masz pomysły na ulepszenie tej strony, prosimy <a href="<page
309 
+    about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
310 
+  </div>
311 
+  <!-- END MAINCOL -->
312 
+  <div id = "sidecol">
313 
+#include "side.wmi"
314 
+#include "info.wmi"
315 
+  </div>
316 
+  <!-- END SIDECOL -->
317 
+</div>
318 
+<!-- END CONTENT -->
319 
+#include <foot.wmi>
docs/pl/tor-doc-server.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,8 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 12076
3 
+# Status: obsolete
4 
+# Last-Translator: bogdandr_at_op . pl
5 
+
6 
+#include "head.wmi" TITLE="Przekierowanie" REDIRECT="docs/tor-doc-relay" CHARSET="UTF-8"
7 
+
8 
+#include <foot.wmi>
docs/pl/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,179 @@
1 
+    <h1>Running the <a href="<page index>">Tor</a> client on Linux/BSD/Unix</h1>
2 
+    <br />
3 
+
4 
+    <p>
5 
+    <b>To są instrukcje do instalacji klienta Tora. Jeśli chcesz przekazywać
6 
+    ruch innych, by wspomóc rozwój sieci (prosimy), przeczytaj poradnik o <a
7 
+    href="<page docs/tor-doc-relay>">Konfigurowaniu przekaźnika sieci
8 
+    Tor</a>.</b>
9 
+    </p>
10 
+
11 
+    <hr /> <a id="installing"></a>
12 
+    <h2><a class="anchor" href="#installing">Krok 1: Pobranie i instalacja Tora</a></h2>
13 
+    <br />
14 
+
15 
+    <p>
16 
+    Najnowsze wydanie Tora można znaleźć na stronie <a href="<page
17 
+    download/download>">pobierania</a>. Mamy tam też pakiety dla systemów Debian, Red
18 
+    Hat, Gentoo, *BSD, etc. Jeśli używasz Ubuntu, nie używaj domyślnych paczek:
19 
+    zamiast nich użyj <a href="<page docs/debian>#ubuntu">naszego repozytorium
20 
+    deb</a>.
21 
+    </p>
22 
+
23 
+    <p>Jeśli masz zamiar kompilować Tora, najpierw zainstaluj <a
24 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a>, i upewnij się,
25 
+    że masz OpenSSL i zlib (łącznie z pakietami -devel, jeśli są). Potem
26 
+    uruchom:<br /> <tt>tar xzf tor-<version-stable>.tar.gz; cd
27 
+    tor-<version-stable><br /> ./configure &amp;&amp; make</tt><br /> Możesz
28 
+    teraz uruchomić Tora poprzez <tt>src/or/tor</tt>, lub możesz uruchomić
29 
+    <tt>make install</tt> (jako root, jeśli potrzeba), by zainstalować Tora do
30 
+    /usr/local, wtedy możesz go uruchamiać po prostu pisząc <tt>tor</tt>.
31 
+    </p>
32 
+
33 
+    <p>Tor comes configured as a client by default. It uses a built-in default
34 
+    configuration file, and most people won't need to change any of the
35 
+    settings. Tor is now installed.
36 
+    </p>
37 
+
38 
+    <hr /> <a id="privoxy"></a> <a id="polipo"></a>
39 
+    <h2><a class="anchor" href="#polipo">Krok 2: Instalacja Polipo do przeglądania
40 
+    sieci WWW</a></h2>
41 
+    <br />
42 
+
43 
+    <p>Po instalacji Tora musisz skonfigurować swoje aplikacje, by go używały.
44 
+    </p>
45 
+
46 
+    <p>
47 
+    The first step is to set up web browsing. Start by installing <a
48 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> from your
49 
+    favorite repository. Polipo is a caching web proxy that does http pipelining
50 
+    well, so it's well-suited for Tor's latencies. Make sure to get at least
51 
+    Polipo 1.0.4, since earlier versions lack the SOCKS support required to use
52 
+    Polipo with Tor. You should uninstall privoxy at this point (e.g. apt-get
53 
+    remove privoxy or yum remove privoxy), so they don't conflict.
54 
+    </p>
55 
+
56 
+    <p>Po instalacji Polipo (z paczki lub źródeł)  <b>musisz skonfigurować Polipo,
57 
+    by używało Tora</b>. Pobierz naszą <a
58 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/polipo.conf">konfigurację
59 
+    Polipo dla Tora</a> i umieść go zamiast swojego bieżącego pliku
60 
+    konfiguracyjnego Polipo (np. /etc/polipo/config lub ~/.polipo). Musisz
61 
+    ponownie uruchomić Polipo, by zmiany odniosły skutek. Na przykład:<br />
62 
+    <tt>/etc/init.d/polipo restart</tt>
63 
+    </p>
64 
+
65 
+    <p>Jeśli wolisz, możesz używać Privoxy z <a
66 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">tą
67 
+    przykładową konfiguracją Privoxy</a>. Ale jako że oba pliki konfiguracyjne
68 
+    używają portu 8118, nie powinieneś/aś używać Polipo i Privoxy jednocześnie.</p>
69 
+
70 
+    <hr /> <a id="using"></a>
71 
+    <h2><a class="anchor" href="#using">Krok 3: Konfiguracja aplikacji, by używały
72 
+    Tora</a></h2>
73 
+    <br />
74 
+
75 
+    <p>After installing Tor and Polipo, you need to configure your applications to
76 
+    use them. The first step is to set up web browsing.</p>
77 
+
78 
+    <p>You should use Tor with Firefox and Torbutton, for best safety.  Simply
79 
+    install the <a href="https://addons.mozilla.org/firefox/2275/">Torbutton
80 
+    plugin</a>, restart your Firefox, and you're all set:
81 
+    </p>
82 
+
83 
+    <img alt="Rozszerzenie Torbutton dla Firefoksa"
84 
+    src="../img/screenshot-torbutton.png" border="1"> <br />
85 
+
86 
+    <p>
87 
+    Jeśli masz zamiar używać Firefoksa na innym komputerze niż tam, gdzie jest
88 
+    Tor, spójrz na <a
89 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">wpis
90 
+    w FAQ na temat uruchamiania Tora na innym komputerze</a>.
91 
+    </p>
92 
+
93 
+    <p>By "storyfikować" inne aplikacje, które używają proxy dla HTTP, po prostu
94 
+    skieruj je na Polipo (czyli localhost, port 8118). By aplikacje bezpośrednio
95 
+    używały serwera SOCKS (do komunikatorów, Jabbera, IRC, itp.), skieruj je
96 
+    bezpośrednio na Tora (localhost, port 9050), ale przeczytaj <a
97 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">ten
98 
+    wpis do FAQ</a>, dlaczego to może być niebezpieczne. Jeśli aplikacja nie
99 
+    obsługuje ani proxy dla HTTP, ani dla SOCKS, spójrz na <a
100 
+    href="http://tsocks.sourceforge.net/">tsocks</a> lub <a
101 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
102 
+    </p>
103 
+
104 
+    <p>Po informacje, jak "storyfikować" inne aplikacje, spójrz na <a
105 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
106 
+    HOWTO</a>.
107 
+    </p>
108 
+
109 
+    <hr /> <a id="verify"></a>
110 
+    <h2><a class="anchor" href="#verify">Krok 4: Upewnij się, że wszystko działa</a></h2>
111 
+    <br />
112 
+
113 
+    <p>
114 
+    <!--PO4ASHARPBEGIN<a href="http://ipchicken.com/">
115 
+    this site</a>PO4ASHARPEND-->
116 
+    #to see what IP address it thinks you're using.
117 
+    Next, you should try using your browser with Tor and make sure that your IP
118 
+    address is being anonymized. Click on <a
119 
+    href="https://check.torproject.org/">the Tor detector</a> and see whether it
120 
+    thinks you're using Tor or not.  (If that site is down, see <a
121 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">this
122 
+    FAQ entry</a> for more suggestions on how to test your Tor.)
123 
+    </p>
124 
+
125 
+    <p>If you have a personal firewall that limits your computer's ability to
126 
+    connect to itself (this includes something like SELinux on Fedora Core 4),
127 
+    be sure to allow connections from your local applications to Polipo (local
128 
+    port 8118) and Tor (local port 9050). If your firewall blocks outgoing
129 
+    connections, punch a hole so it can connect to at least TCP ports 80 and
130 
+    443, and then see <a
131 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">this
132 
+    FAQ entry</a>.  If your SELinux config is not allowing tor or privoxy to run
133 
+    correctly, create a file named booleans.local in the directory
134 
+    /etc/selinux/targeted.  Edit this file in your favorite text editor and
135 
+    insert "allow_ypbind=1".  Restart your machine for this change to take
136 
+    effect.
137 
+    </p>
138 
+
139 
+    <p>Jeśli dalej nie działa, spójrz na <a
140 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">ten
141 
+    wpis FAQ</a>, by poszukać wskazówek.</p>
142 
+
143 
+    <hr /> <a id="server"></a> <a id="relay"></a>
144 
+    <h2><a class="anchor" href="#relay">Krok 5: Konfiguracja Tora jako przekaźnika
145 
+    sieci</a></h2>
146 
+    <br />
147 
+
148 
+    <p>Sieć Tora polega na ochotnikach oddających część swojego łącza. Im więcej
149 
+    ludzi uruchomi przekaźnik sieci, tym szybsza będzie sieć Tora. Jeśli masz co
150 
+    najmniej 20 kilobajtów/s w obie strony, pomóż Torowi, konfigurując swojego
151 
+    klienta tak, by był także przekaźnikiem sieci Tor. Mamy wiele cech, które
152 
+    czynią przekaźniki Tora łatwymi i wygodnymi, łącznie z ograniczeniem
153 
+    przepustowości, politykami wyjścia, byś mógł zmniejszyć ryzyko skarg, oraz
154 
+    obsługą dynamicznych adresów IP.</p>
155 
+
156 
+    <p>Posiadanie przekaźników w wielu różnych miejscach w sieci sprawia, że
157 
+    użytkownicy są bezpieczni. <a
158 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Ty
159 
+    też możesz mieć lepszą anonimowość</a>, gdyż serwery, do których się
160 
+    łączysz, nie mogą stwierdzić, czy połączenie pochodzi z Twojego komputera,
161 
+    czy zostało przekierowane z innych.</p>
162 
+
163 
+    <p>Przeczytaj szczegóły w naszym przewodniku <a href="<page
164 
+    docs/tor-doc-relay>">Konfiguracji przekaźnika sieci Tor</a>.</p>
165 
+
166 
+    <hr />
167 
+
168 
+    <p>Jeśli masz pomysły na ulepszenie tej strony, prosimy <a href="<page
169 
+    about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
170 
+  </div>
171 
+  <!-- END MAINCOL -->
172 
+  <div id = "sidecol">
173 
+#include "side.wmi"
174 
+#include "info.wmi"
175 
+  </div>
176 
+  <!-- END SIDECOL -->
177 
+</div>
178 
+<!-- END CONTENT -->
179 
+#include <foot.wmi>
docs/pl/tor-doc-web.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,64 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Configuring your browser to use Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-web>">Configure Your Browser</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Konfiguracja przeglądarki, by używała <a href="<page index>">Tora</a></h1>
14 
+    <br />
15 
+
16 
+    <p>Jeśli używasz przeglądarki Firefox (co zalecamy), nie musisz czytać tej strony.
17 
+     Po prostu zainstaluj <a
18 
+     href="https://addons.mozilla.org/firefox/2275/">rozszerzenie
19 
+     Torbutton</a>, ponownie uruchom Firefoksa i gotowe:
20 
+    </p>
21 
+
22 
+    <img alt="Rozszerzenie Torbutton dla Firefoksa"
23 
+     src="../img/screenshot-torbutton.png"
24 
+     border="1" />
25 
+
26 
+    <br />
27 
+
28 
+    <p>W innym przypadku, musisz ręcznie skonfigurować ustawienia proxy w swojej przeglądarce.
29 
+    <br />W przeglądarkach Mozilla i Firefox pod Windows, znajdują się w
30 
+    	Narzędzia - Opcje - Ogólne - Ustawienia połączenia.
31 
+    <br />W Firefoksie na OS X, są w Firefox - Preferencje - Ogólne - Ustawienia połączenia.
32 
+    <br />W Firefoksie pod systemem Linux, znajdują się w
33 
+      	 Edycja - Preferencje - Zaawansowane - Proxy [od tłum:
34 
+    	 W Firefoksie 1.5: Edycja - Preferencje - Ogólne - Ustawienia połączenia;
35 
+    	 w Firefoksie 2.0: Edycja - Preferencje - Zaawansowane - Sieć - Ustawienia ]
36 
+    <br />W Operze są w Narzędzia - Preferencje(Zaawansowane) - Sieć - Serwery Proxy.
37 
+    <br />Nie możemy zalecać używania IE, ale dla tych, którzy chcą mniej-niż-pełnej anonimowości:
38 
+      W IE, są w Narzędzia - Opcje internetowe - Połączenia - Ustawienia sieci LAN - zaznacz Serwer Proxy
39 
+    - Zaawansowane.</p>
40 
+
41 
+    <img alt="Ustawienia proxy w Firefoksie"
42 
+     src="../img/screenshot-win32-firefox-proxies.jpg" />
43 
+
44 
+    <p>Powinieneś wpisać "localhost" i "8118", by skierować górne cztery protokoły na
45 
+     Polipo, jak pokazano. (Nawet mimo tego, że Polipo nie obsługuje FTP i Gophera, <a
46 
+     href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">powinieneś
47 
+     i tak je ustawić</a>.) Powinieneś też wypełnić pole SOCKS Proxy, by wskazywało
48 
+     bezpośrednio na Tora ("localhost", "9050" i socks5), by pokryć inne protokoły
49 
+     poza pierwszymi czterema. Po wszystkim kliknij "OK".</p>
50 
+
51 
+    <hr />
52 
+
53 
+    <p>Jeśli masz pomysły na ulepszenie tej strony, prosimy <a
54 
+    href="<page about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
55 
+  </div>
56 
+  <!-- END MAINCOL -->
57 
+  <div id = "sidecol">
58 
+#include "side.wmi"
59 
+#include "info.wmi"
60 
+  </div>
61 
+  <!-- END SIDECOL -->
62 
+</div>
63 
+<!-- END CONTENT -->
64 
+#include <foot.wmi>
docs/pl/tor-doc-win32.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,10 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 13195
3 
+# Status: obsolete
4 
+# Translation-Priority: 2-medium
5 
+# Last-Translator: bogdandr_at_op . pl
6 
+
7 
+#include "head.wmi" TITLE="Przekierowanie" CHARSET="UTF-8" REDIRECT="docs/tor-doc-windows"
8 
+
9 
+#include <foot.wmi>
10 
+
docs/pl/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,189 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Uruchamianie klienta <a href="<page index>">Tor</a> na Microsoft Windows</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Note that these are the installation instructions for running a Tor
18 
+    client on Microsoft Windows (2000, XP, Vista, 7, and Server Editions).  If
19 
+    you want to relay traffic for others to help the network grow (please do),
20 
+    read the <a href="<page docs/tor-doc-relay>">Configuring a relay</a>
21 
+    guide.</b>
22 
+    </p>
23 
+
24 
+    <p>Freedom House has produced a video on how to install Tor.  You can view it
25 
+    at <a
26 
+    href="http://media.torproject.org/video/2009-install-and-use-tor.ogv">How to
27 
+    install Tor on Windows</a>.  Know of a better video, or one translated into
28 
+    your language? Let us know!</p>
29 
+
30 
+    <div class="center">
31 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor.ogv" autobuffer="true" controls="controls"></video></p>
32 
+    </div>
33 
+
34 
+    <hr /> <a id="installing"></a>
35 
+    <h2><a class="anchor" href="#installing">Krok 1: Pobranie i instalacja Tora</a></h2>
36 
+    <br />
37 
+
38 
+    <p>
39 
+    Paczki dla Microsoft Windows zawierają programy: <a href="<page
40 
+    index>">Tor</a>, <a href="<page projects/vidalia>">Vidalia</a> (GUI dla Tora),
41 
+    <a href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> (dodatek do
42 
+    Mozilla Firefox) i <a
43 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (serwer
44 
+    proxy do WWW)  w jednej paczce, wszystkie cztery aplikacje prekonfigurowane
45 
+    do współpracy ze sobą. Pobierz albo <a
46 
+    href="../<package-win32-bundle-stable>">stabilną</a> albo <a
47 
+    href="../<package-win32-bundle-alpha>">eksperymentalną</a> wersję paczki dla
48 
+    Windows, lub poszukaj innych rozwiązań na <a href="<page download/download>">stronie
49 
+    pobierania</a>.
50 
+    </p>
51 
+
52 
+    <img alt="Ekran instalacji Tora"
53 
+    src="../img/screenshot-win32-installer-splash.png" />
54 
+
55 
+    <p>Jeśli już wcześniej zainstalowałeś Tora, Vidalię lub Polipo, możesz
56 
+    odznaczyć elementy, których nie musisz instalować w oknie dialogowym
57 
+    pokazanym niżej.
58 
+    </p>
59 
+
60 
+    <img alt="Wybór składników instalacji"
61 
+    src="../img/screenshot-win32-installer-components.png" />
62 
+
63 
+    <p>Po zakończeniu instalacji wybrane składniki zostaną automatycznie
64 
+    uruchomione.
65 
+    </p>
66 
+
67 
+    <p>Tor jest domyślnie skonfigurowany jako klient. Używa wbudowanego domyślnego
68 
+    pliku konfiguracji, i większość użytkowników nie będzie musiała zmieniać
69 
+    żadnych ustawień. Tor jest teraz zainstalowany.
70 
+    </p>
71 
+
72 
+    <hr /> <a id="using"></a>
73 
+    <h2><a class="anchor" href="#using">Krok 2: Konfiguracja aplikacji, by używały
74 
+    Tora</a></h2>
75 
+    <br />
76 
+
77 
+    <p>Po instalacji Tora i Polipo musisz skonfigurować swoje aplikacje, by ich
78 
+    używały.  Pierwszym krokiem jest ustawienie sposobu przeglądania sieci WWW.</p>
79 
+
80 
+    <p>Powinieneś/aś używać Tora z Firefoksem i Torbuttonem, dla najlepszego
81 
+    bezpieczeństwa. Instalator programu zainstaluje <a
82 
+    href="https://addons.mozilla.org/firefox/2275/">rozszerzenie Torbutton</a>
83 
+    za Ciebie. Uruchom ponownie Firefoksa i gotowe:
84 
+    </p>
85 
+
86 
+    <img alt="Rozszerzenie Torbutton dla Firefoksa"
87 
+    src="../img/screenshot-torbutton.png" border="1" /> <br />
88 
+
89 
+    <p>
90 
+    Jeśli masz zamiar używać Firefoksa na innym komputerze niż tam, gdzie jest
91 
+    Tor, spójrz na <a
92 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">wpis
93 
+    w FAQ na temat uruchamiania Tora na innym komputerze</a>.
94 
+    </p>
95 
+
96 
+    <p>To Torify other applications that support HTTP proxies, just point them at
97 
+    Polipo (that is, localhost port 8118). To use SOCKS directly (for instant
98 
+    messaging, Jabber, IRC, etc), you can point your application directly at Tor
99 
+    (localhost port 9050), but see <a
100 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">this
101 
+    FAQ entry</a> for why this may be dangerous. For applications that support
102 
+    neither SOCKS nor HTTP, take a look at SocksCap or <a
103 
+    href="http://www.freecap.ru/eng/">FreeCap</a>.  (FreeCap is free software;
104 
+    SocksCap is proprietary.)</p>
105 
+
106 
+    <p>Po informacje, jak "storyfikować" inne aplikacje, spójrz na <a
107 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
108 
+    HOWTO</a>.
109 
+    </p>
110 
+
111 
+    <hr /> <a id="verify"></a>
112 
+    <h2><a class="anchor" href="#verify">Krok 3: Upewnij się, że wszystko działa</a></h2>
113 
+    <br />
114 
+
115 
+    <p>
116 
+    Sprawdź, czy Vidalia jest uruchomione. Vidalia używa małej zielonej cebuli,
117 
+    gdy Tor działa lub ciemnej cebuli z czerwonym "X", gdy Tor nie
118 
+    działa. Możesz zatrzymać lub uruchomić Tora, klikając prawym klawiszem
119 
+    myszki na ikonę Vidalii w zasobniku systemowym i wybierając "Start" lub
120 
+    "Stop" z menu, jak pokazano niżej:
121 
+    </p>
122 
+
123 
+    <img alt="Ikona Vidalii w zasobniku"
124 
+    src="../img/screenshot-win32-vidalia.png" />
125 
+
126 
+    <p>
127 
+    Teraz powinieneś spróbować użyć swojej przeglądarki z Torem i upewnić się,
128 
+    że Twój adres IP jest anonimizowany. Kliknij na <a
129 
+    href="https://check.torproject.org/">wykrywacz Tora</a> i sprawdź, czy jego
130 
+    zdaniem używasz Tora czy nie. (Jeśli ta strona akurat nie działa, przeczytaj
131 
+    <a
132 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">ten
133 
+    wpis w FAQ</a>, by poznać więcej sposobów na testowanie swojego Tora.)
134 
+    </p>
135 
+
136 
+    <p>Jeśli masz zaporę ogniową, która ogranicza możliwości Twojego komputera co
137 
+    do łączenia się z samym sobą, zezwól w niej na połączenia od programów
138 
+    lokalnych na porty lokalne 8118 i 9050. Jeśli zapora blokuje połączenia
139 
+    wychodzące, spraw, by można się było połączyć choć z portami 80 i 433, po
140 
+    czym przeczytaj <a
141 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">ten
142 
+    wpis do FAQ</a>.
143 
+    </p>
144 
+
145 
+    <p>Jeśli dalej nie działa, spójrz na <a
146 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">ten
147 
+    wpis FAQ</a>, by poszukać wskazówek.</p>
148 
+
149 
+    <p>
150 
+    Gdy Tor już działa, poczytaj o tym, <a href="<page download/download>#Warning">co Tor
151 
+    oferuje, a czego nie</a>.
152 
+    </p>
153 
+
154 
+    <hr /> <a id="server"></a> <a id="relay"></a>
155 
+    <h2><a class="anchor" href="#relay">Krok 4: Konfiguracja Tora jako przekaźnika
156 
+    sieci</a></h2>
157 
+    <br />
158 
+
159 
+    <p>The Tor network relies on volunteers to donate bandwidth. The more people
160 
+    who run relays, the faster the Tor network will be. If you have at least 20
161 
+    kilobytes/s each way, please help out Tor by configuring your Tor to be a
162 
+    relay too. We have many features that make Tor relays easy and convenient,
163 
+    including rate limiting for bandwidth, exit policies so you can limit your
164 
+    exposure to abuse complaints, and support for dynamic IP addresses.</p>
165 
+
166 
+    <p>Posiadanie przekaźników w wielu różnych miejscach w sieci sprawia, że
167 
+    użytkownicy są bezpieczni. <a
168 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Ty
169 
+    też możesz mieć lepszą anonimowość</a>, gdyż serwery, do których się
170 
+    łączysz, nie mogą stwierdzić, czy połączenie pochodzi z Twojego komputera,
171 
+    czy zostało przekierowane z innych.</p>
172 
+
173 
+    <p>Przeczytaj szczegóły w naszym przewodniku <a href="<page
174 
+    docs/tor-doc-relay>">Konfiguracji przekaźnika sieci Tor</a>.</p>
175 
+
176 
+    <hr />
177 
+
178 
+    <p>Jeśli masz pomysły na ulepszenie tej strony, prosimy <a href="<page
179 
+    about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
180 
+  </div>
181 
+  <!-- END MAINCOL -->
182 
+  <div id = "sidecol">
183 
+#include "side.wmi"
184 
+#include "info.wmi"
185 
+  </div>
186 
+  <!-- END SIDECOL -->
187 
+</div>
188 
+<!-- END CONTENT -->
189 
+#include <foot.wmi>
docs/pl/tor-hidden-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,269 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22314 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Konfiguracja usług ukrytych <a href="<page index>">Tora</a></h1>
14 
+    <hr />
15 
+
16 
+    <p>Tor umożliwia klientom i przekaźnikom sieci Tor oferowanie usług ukrytych. To znaczy,
17 
+     że możesz mieć serwer WWW, SSH etc. bez podawania swojego IP użytkownikom.
18 
+     Ponieważ nie używasz żadnego adresu publicznego, możesz prowadzić
19 
+     usługę ukrytą zza zapory ogniowej.
20 
+    </p>
21 
+
22 
+    <p>Jeśli masz zainstalowanego Tora, możesz zobaczyć usługi
23 
+     ukryte w działaniu, odwiedzając <a href="http://duskgytldkxiuqc6.onion/">naszą przykładową
24 
+     usługę ukrytą</a> lub <a
25 
+     href="http://gaddbiwdftapglkq.onion/">usługę ukrytą Wikileaks</a>.
26 
+    </p>
27 
+
28 
+    <p>Ten dokument opisuje kroki potrzebne do uruchomienia własnej ukrytej usługi WWW.
29 
+    By poznać szczegóły techniczne tego, jak działa protokół usług ukrytych, przeczytaj
30 
+    naszą stronę <a href="<page docs/hidden-services>">protokołu usług ukrytych</a>.
31 
+    </p>
32 
+
33 
+    <hr />
34 
+    <a id="zero"></a>
35 
+    <h2><a class="anchor" href="#zero">Krok 0: Uruchomienie Tora</a></h2>
36 
+    <br />
37 
+
38 
+    <p>Zanim zaczniesz sprawdź, czy:</p>
39 
+    <ol>
40 
+    <li> Tor jest uruchomiony i działa,</li>
41 
+    <li> rzeczywiście wszystko dobrze ustawiłeś.</li>
42 
+    </ol>
43 
+    <p>Użytkownicy Windows powinni przeczytać <a
44 
+     href="<page docs/tor-doc-windows>">instrukcje dla
45 
+     Windows</a>, użytkownicy OS X powinni przeczytać <a
46 
+     href="<page docs/tor-doc-osx>">instrukcje dla
47 
+     OS X</a>, a użytkownicy Linux/BSD/Unix powinni przeczytać <a
48 
+     href="<page docs/tor-doc-unix>">instrukcje dla systemów Unix</a>.
49 
+    </p>
50 
+
51 
+    <p>Po instalacji i konfiguracji Tora możesz zobaczyć ukryte usługi
52 
+     w działaniu, wchodząc na <a
53 
+     href="http://duskgytldkxiuqc6.onion/">naszą przykładową
54 
+     usługę ukrytą</a> lub <a
55 
+     href="http://gaddbiwdftapglkq.onion/">usługę ukrytą Wikileaks</a>.
56 
+     Zwykle trzeba poczekać 10-60 na załadowanie strony (lub stwierdzenie, że w
57 
+     danej chwili jest niedostępna). Jeśli próba od razu kończy się błędem mówiącym, że
58 
+     nie można znaleźć serwera "www.duskgytldkxiuqc6.onion", to znaczy, że nie skonfigurowałeś
59 
+     Tora poprawnie; zajrzyj do <a
60 
+     href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">wpisu
61 
+     "to nie działa" w FAQ</a> po pomoc.
62 
+    </p>
63 
+
64 
+
65 
+    <hr />
66 
+    <a id="one"></a>
67 
+    <h2><a class="anchor" href="#one">Krok 1: Zainstaluj lokalnie serwer WWW</a></h2>
68 
+    <br />
69 
+
70 
+    <p>Teraz gdy już masz działające usługi ukryte w Torze, musisz uruchomić
71 
+     lokalnie serwer WWW. Uruchamianie serwera WWW jest skomplikowane,
72 
+     więc podamy tu tylko trochę podstawowych informacji. Jeśli utkniesz
73 
+     lub będziesz chciał zrobić coś więcej, znajdź znajomego, który ci pomoże.
74 
+     Zalecamy instalację nowego, oddzielnego serwera do usługi ukrytej, gdyż
75 
+     nawet jeśli już masz jeden zainstalowany, możesz już go używać (lub
76 
+     później będziesz chciał go używać) do normalnego serwisu WWW.
77 
+    </p>
78 
+
79 
+    <p>Jeśli jesteś na systemie Unix lub OS X i nie przeszkadza ci używanie
80 
+     linii poleceń, najlepszym sposobem jest instalacja <a
81 
+     href="http://www.acme.com/software/thttpd/">thttpd</a>. Po prostu
82 
+     pobierz archiwum tar, rozpakuj je (utworzy się osobny katalog) i uruchom
83 
+     <kbd>./configure &amp;&amp; make</kbd>. Potem wykonaj <kbd>mkdir hidserv; cd hidserv</kbd>,
84 
+     i uruchom <kbd>../thttpd -p 5222 -h localhost</kbd>. Powrócisz do wiersza poleceń,
85 
+     a od tej pory masz uruchomiony serwer WWW na porcie 5222. Możesz umieścić
86 
+     pliki dla serwera w katalogu hidserv.
87 
+    </p>
88 
+
89 
+    <p>Jeśli używasz systemu Windows, możesz wybrać serwer WWW <a
90 
+     href="http://savant.sourceforge.net/">Savant</a> lub <a
91 
+     href="http://httpd.apache.org/">Apache</a>,
92 
+     konfigurując go tak, by podłączał się tylko do komputera, na którym jest
93 
+     zainstalowany (localhost). Powinieneś też jakoś sprawdzić na jakim porcie
94 
+     nasłuchuje, gdyż ta informacja przyda się potem.
95 
+    </p>
96 
+
97 
+    <p>(Powodem, dla którego serwer powinien działać tylko lokalnie jest upewnienie
98 
+     się, że nie jest on dostępny z zewnątrz. Jeśli ktoś mógłby się do niego
99 
+     połączyć bezpośrednio, mógłby potwierdzić, że to twój komputer oferuje
100 
+     tą ukrytą usługę.)
101 
+    </p>
102 
+
103 
+    <p>Po ustawieniu serwera WWW, sprawdź, czy działa: otwórz przeglądarkę i
104 
+     przejdź pod adres <a
105 
+     href="http://localhost:5222/">http://localhost:5222/</a>, gdzie 5222 jest numerem portu
106 
+     wybranym wcześniej. Potem spróbuj
107 
+     umieścić jakiś plik w głównym katalogu HTML serwera i sprawdź, czy pokazuje
108 
+     się on, gdy łączysz się ze swoim serwerem WWW.
109 
+    </p>
110 
+
111 
+
112 
+    <hr />
113 
+    <a id="two"></a>
114 
+    <h2><a class="anchor" href="#two">Krok 2: Konfiguracja twojej usługi ukrytej</a></h2>
115 
+    <br />
116 
+
117 
+    <p>Teraz musisz skonfigurować swoją usługę ukrytą, by wskazywała na twój lokalny
118 
+     serwer WWW.
119 
+    </p>
120 
+
121 
+    <p>Najpierw otwórz swój plik torrc swoim ulubionym edytorem. (Przeczytaj <a
122 
+     href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">wpis
123 
+     o torrc w FAQ</a>, by dowiedzieć się, co to znaczy.) Przejdź do środkowej sekcji i
124 
+     szukaj linii</p>
125 
+
126 
+    <pre>
127 
+    \############### This section is just for location-hidden services ###
128 
+    </pre>
129 
+
130 
+    <p>Ta sekcja pliku składa się z grup linii, z których każda reprezentuje
131 
+     jedną usługę ukrytą. W tej chwili wszystkie są zakomentowane (linie zaczynają
132 
+     się od krzyżyka #), więc usługi ukryte są wyłączone. Każda grupa linii
133 
+     składa się z jednej linii <var>HiddenServiceDir</var> i jednej lub więcej linii
134 
+     <var>HiddenServicePort</var>:</p>
135 
+    <ul>
136 
+    <li><var>HiddenServiceDir</var> jest katalogiem, w którym Tor będzie przechowywał
137 
+     informacje o tej usłudze ukrytej. W szczególności, Tor utworzy w tym katalogu
138 
+     plik o nazwie <var>hostname</var>, z którego odczytasz "adres cebulowy" (onion URL).
139 
+     Nie musisz dodawać żadnych plików do tego katalogu.</li>
140 
+    <li><var>HiddenServicePort</var> pozwala określić port wirtualny (tzn. użytkownikom
141 
+     łączącym się z usługą ukrytą będzie się zdawało, że używają tego właśnie portu) i
142 
+     adres IP wraz z portem do przekierowywania połączeń na ten wirtualny port.</li>
143 
+    </ul>
144 
+
145 
+    <p>Dodaj następujące linie do swojego pliku torrc:
146 
+    </p>
147 
+
148 
+    <pre>
149 
+    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
150 
+    HiddenServicePort 80 127.0.0.1:5222
151 
+    </pre>
152 
+
153 
+    <p>Powinieneś zmienić linię <var>HiddenServiceDir</var> tak, by pokazywała na istniejący
154 
+     katalog, który jest odczytywalny/zapisywalny przez użytkownika, który uruchamia
155 
+     Tora. Powyższa linia powinna działać, gdy używasz paczki z Torem dla OS X.
156 
+     Pod systemem Unix, sprobuj "/home/użytkownik/hidserv/", podając własną nazwę użytkownika
157 
+     w miejsce "użytkownik". Pod systemem Windows mógłbyś wpisać:</p>
158 
+    <pre>
159 
+    HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\\
160 
+    HiddenServicePort 80 127.0.0.1:5222
161 
+    </pre>
162 
+
163 
+    <p>Teraz zapisz zmiany w pliku torrc, zamknij Tora i uruchom go ponownie.
164 
+    </p>
165 
+
166 
+    <p>Jeśli Tor ponownie się uruchomi, to świetnie. W innym przypadku coś musi być
167 
+     źle. Najpierw przejrzyj plik z logami, by poszukać przyczyn. Będą w nim
168 
+     ostrzeżenia i błędy. Powinny one wskazać, co poszło nie tak. Zazwyczaj chodzi o
169 
+     literówki w pliku torrc lub złe uprawnienia do katalogów. (Przeczytaj <a
170 
+     href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">wpis
171 
+     o logach w FAQ</a>, jeśli nie wiesz jak włączyć lub znaleźć plik z logami.)
172 
+    </p>
173 
+
174 
+    <p>Gdy Tor się uruchomi, automatycznie utworzy podany katalog <var>HiddenServiceDir</var>
175 
+     (jeśli trzeba), a w nim utworzy dwa pliki.</p>
176 
+     <dl>
177 
+     <dt><var>private_key</var></dt>
178 
+     <dd>Po pierwsze, Tor wygeneruje nową
179 
+     parę kluczy publiczny/prywatny do twojej usługi ukrytej. Zostaje ona zapisana w
180 
+     pliku o nazwie "private_key". Nie dawaj tego klucza nikomu -- jeśli to zrobisz,
181 
+     inni będą mogli podszyć się pod twoją usługę ukrytą.</dd>
182 
+     <dt><var>hostname</var></dt>
183 
+     <dd>Drugim plikiem, który zostanie utworzony, jest plik o nazwie "hostname".
184 
+     Zawiera on krótkie podsumowanie twojego klucza publicznego -- będzie wyglądać
185 
+     podobnie do tego: <tt>duskgytldkxiuqc6.onion</tt>. To jest publiczna nazwa
186 
+     twojej usługi i możesz podawać ją innym, rozgłaszać w internecie,
187 
+     umieszczać na wizytówkach etc.</dd>
188 
+     </dl>
189 
+
190 
+    <p>Jeśli Tor jest uruchomiony z prawami innego
191 
+     użytkownika niż ty, np. na systemach OS X, Debian, Red Hat, możesz potrzebować
192 
+     uprawnień roota, by zobaczyć te pliki.
193 
+    </p>
194 
+
195 
+    <p>Po ponownym uruchomieniu, Tor zajmuje się pobieraniem punktów wstępu
196 
+     w sieci Tora i generowaniem <em>deskryptorem usługi ukrytej</em>.
197 
+     Jest to podpisana lista punktów wstępnych razem z pełnym publicznym kluczem
198 
+     usługi. Tor anonimowo umieszcza ten deskryptor na serwerach katalogowych, a
199 
+     inni ludzie anonimowo go pobierają z serwerów katalogowych, gdy próbują połączyć
200 
+     się z twoją usługą.
201 
+    </p>
202 
+
203 
+    <p>Wypróbuj to: wklej zawartość pliku "hostname" do swojej przeglądarki WWW.
204 
+     Jeśli działa, zobaczysz stronę Google, ale adres w przeglądarce będzie
205 
+     adresem twojej usługi. Jeśli nie działa, poszukaj wskazówek w logach i
206 
+     zajmuj się tym do chwili, w której zadziała.
207 
+    </p>
208 
+
209 
+    <hr />
210 
+    <a id="three"></a>
211 
+    <h2><a class="anchor" href="#three">Krok 3: Wskazówki dla zaawansowanych</a></h2>
212 
+    <br />
213 
+
214 
+    <p>Jeśli planujesz udostępniać swoją usługę przez dłuższy czas, zrób kopię
215 
+     zapasową pliku <var>private_key</var>.
216 
+    </p>
217 
+
218 
+    <p>Wcześniej unikaliśmy polecania serwera Apache, a) gdyż wielu ludzi
219 
+     może już go używać jako publicznego serwera na ich komputerach, i
220 
+     b) gdyż jest duży i ma wiele miejsc, w których mógłby podać twój adres IP
221 
+     lub inne informacje identyfikujące, np. na stronach 404. Jednak dla ludzi,
222 
+     którzy chcą więcej funkcjonalności, Apache może być dobrym rozwiązaniem.
223 
+     Czy ktoś mógłby napisać nam listę sposobów na zabezpieczenie Apache, gdy
224 
+     jest używany jako usługa ukryta? Savant prawdopodobnie też ma takie problemy.
225 
+    </p>
226 
+
227 
+    <p>Jeśli chcesz przekierować wiele portów wirtualnych w ramach pojedynczej
228 
+     usługi ukrytej, po prostu dodaj więcej linii <var>HiddenServicePort</var>.
229 
+     Jeśli chcesz uruchomić wiele usług ukrytych z tego samego klienta Tora,
230 
+     po prostu dodaj kolejną linię <var>HiddenServiceDir</var>. Wszystkie następujące po
231 
+     niej linie <var>HiddenServicePort</var> odnoszą się do aktualnej linii <var>HiddenServiceDir</var>,
232 
+     dopóki nie dodasz kolejnej linii <var>HiddenServiceDir</var>:
233 
+    </p>
234 
+
235 
+    <pre>
236 
+    HiddenServiceDir /usr/local/etc/tor/hidden_service/
237 
+    HiddenServicePort 80 127.0.0.1:8080
238 
+
239 
+    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
240 
+    HiddenServicePort 6667 127.0.0.1:6667
241 
+    HiddenServicePort 22 127.0.0.1:22
242 
+    </pre>
243 
+
244 
+    <p>Są też pewne sprawy dotyczące anonimowości, o których trzeba pamiętać:
245 
+    </p>
246 
+    <ul>
247 
+    <li>Jak wspomniano wyżej, uważaj z pozwoleniem dla serwera o podawaniu
248 
+     informacji identyfikujących ciebie, twój komputer lub położenie.
249 
+     Na przykład, czytelnicy mogą prawdopodobnie dowiedzieć się, czy
250 
+     używasz Apache czy thttpd i dowiedzieć sie czegoś o twoim systemie operacyjnym.</li>
251 
+    <li>Jeśli twój komputer nie jest cały czas on-line, twoja usługa ukryta też
252 
+     nie będzie. Jest to wyciek informacji dla obserwującego przeciwnika.</li>
253 
+    <!-- increased risks over time -->
254 
+    </ul>
255 
+
256 
+    <hr />
257 
+
258 
+    <p>Jeśli masz pomysły na ulepszenie tej strony, prosimy <a
259 
+    href="<page about/contact>">je do nas wysłać</a>. Dziękujemy!</p>
260 
+  </div>
261 
+  <!-- END MAINCOL -->
262 
+  <div id = "sidecol">
263 
+#include "side.wmi"
264 
+#include "info.wmi"
265 
+  </div>
266 
+  <!-- END SIDECOL -->
267 
+</div>
268 
+<!-- END CONTENT -->
269 
+#include <foot.wmi>
docs/pt/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/pt/tor-doc-win32.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,211 @@
1 
+    <p>
2 
+    [Note that this translation is very wrong at this point -- we
3 
+    include it here to encourage people to update it. -RD]
4 
+    </p>
5 
+
6 
+    <h1>Usando o cliente <a href="<page index>">Tor</a> em MS Windows</h1>
7 
+    <br />
8 
+
9 
+    <a name="installing"></a>
10 
+    <h2>Passo 1: Download e Instala��o do Tor</h2>
11 
+    <p>
12 
+    <b>Note que estas instru�es s�o para a instala��o do cliente <b>Tor</b> em MS Windows
13 
+    (98, 98SE, NT4, 2000, XP, Server). Se voc� pretende rodar um servidor (todos os servidores
14 
+    s�o bem-vindos), leia a se��o "Configurando um servidor" em
15 
+    <a href="<page docs/bridges>">tor-doc-server.html</a>.</b>
16 
+    </p>
17 
+    <p>
18 
+    Este documento foi atualizado em 14/06/2005.
19 
+    </p>
20 
+    <p>
21 
+    #A �ltima vers�o beta de Tor para MS Windows �
22 
+    #<a href="https://www.torproject.org/dist/win32/tor-0.1.0.10-win32.exe">0.1.0.10</a>.
23 
+    #Fa�a o download clicando no link.
24 
+    Voc� pode encontrar vers�es experimentais
25 
+    <a href="<page download/download>">aqui</a>, se voc� estiver procurando
26 
+    por novas facilidades e novos bugs.
27 
+    </p>
28 
+
29 
+    <p>
30 
+    Se voc� deseja rodar o Tor no SYSTRAY, ou como um servi�o, consulte o
31 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Win32SystemTrayService">nosso FAQ</a>.
32 
+    Se voc� n�o se importa em rodar o programa em uma janela (de forma que voc� possa ver
33 
+    os seus <i>logs</i> e mensagens de erro), ent�o o Instalador do Tor deve lhe servir
34 
+    de maneira bem simples. Abaixo vemos uma imagem do programa de instala��o (provavelmente
35 
+    a sua vers�o ser� mais nova do que a mostrada na imagem):
36 
+    </p>
37 
+    <p>
38 
+    <small>(NT: O Programa de instala��o, por enquanto, est� dispon�vel apenas em ingl�s.)</small>
39 
+    </p>
40 
+
41 
+    <img alt="tor installer splash page"
42 
+    src="../img/screenshot-win32-installer-splash.jpg" />
43 
+
44 
+    <p>
45 
+    Pof <i>default</i>, Tor n�o � configurado para ser executado na inicializa��o.
46 
+    <!--No entanto, n�s recomendamos fortemente que voc� ative esta op��o.-->
47 
+    Voc� pode ativar esta op��o clicando no controle <i>"Run at Startup"</i> como
48 
+    mostrado abaixo.
49 
+    Certifique-se de manter os outros controles ligados.
50 
+    </p>
51 
+
52 
+    <img alt="select components to install"
53 
+    src="../img/screenshot-win32-installer-components.jpg" />
54 
+
55 
+    <p>
56 
+    Assim que a instala��o � terminada, o programa Tor ser� executado numa janela,
57 
+    de forma que voc� possa ver seus <i>logs</i> e mensagens de erro.<br />
58 
+    Aten��o: Voc� pode minimizar esta janela, mas n�o fech�-la, ou o programa n�o
59 
+    estar� mais dispon�vel.
60 
+    </p>
61 
+
62 
+    <img alt="tor window screenshot"
63 
+    src="../img/screenshot-win32-dos-window.jpg" />
64 
+
65 
+    <p>
66 
+    O programa Tor vem pr�-configurado como cliente, por <i>default</i>. Ele usa
67 
+    um arquivo de configura��o interno pr�-definido, e na maioria das vezes n�o
68 
+    ser� necess�rio alterar nenhum dos seus ajustes.<br />
69 
+    Neste momento, o programa Tor j� estar� instalado e pronto para uso.
70 
+    </p>
71 
+
72 
+    <a name="privoxy"></a>
73 
+    <h2>Passo 2: Instalar o Privoxy para Navega��o Web</h2>
74 
+
75 
+    <p>
76 
+    Depois de instalar o programa Tor, voc� precisa configurar suas aplica�es para
77 
+    us�-lo. O primeiro passo � configurar a navega��o web. Comece instalando o programa
78 
+    <a href="http://www.privoxy.org/">Privoxy</a>
79 
+    (clique em 'recent releases' para baixar a vers�o mais atual, ent�o role a janela para
80 
+    selecionar os pacotes de instala��o para MS Windows).
81 
+    Privoxy � um proxy com filtros de navega��o que permite boa integra��o com o
82 
+    programa Tor. Assim que o Privoxy estiver instalado, ele aparecer� no seu SYSTRAY
83 
+    como um "P" num c�rculo, como na figura abaixo:
84 
+    </p>
85 
+
86 
+    <img alt="privoxy icon in the system tray"
87 
+    src="../img/screenshot-win32-privoxy-icon.jpg" />
88 
+
89 
+    <p>
90 
+    Voc� deve configurar o Privoxy para usar o Tor.
91 
+    Abra o arquivo de configura��o principal do Privoxy selecionando-o em "Iniciar &gt; Todos os Programas":
92 
+    </p>
93 
+
94 
+    <img border="1" alt="editing privoxy config"
95 
+    src="../img/screenshot-win32-privoxy-config.jpg" />
96 
+
97 
+    <p>
98 
+    Adicione a linha<br />
99 
+    <var>forward-socks4a / 127.0.0.1:9050 .</var><br />
100 
+    ao arquivo de configura��o do Privoxy. N�o esque�a de colocar o "." no final da linha.
101 
+    A maneira mais f�cil de fazer isso � copiar a linha acima e colar dentro do arquivo.
102 
+    N�o esque�a de salvar as altera�es.
103 
+    </p>
104 
+
105 
+    <img border="1" alt="privoxy points to tor"
106 
+    src="../img/screenshot-win32-privoxy-edit.jpg" />
107 
+
108 
+    <a name="using"></a>
109 
+    <h2>Passo 3: Configurando suas aplica�es para usar Tor</h2>
110 
+
111 
+    <p>
112 
+    Agora, mude a configura�ao de proxy HTTP do seu navegador para o endere�o 'localhost',
113 
+    porta 8118 (Essa � a porta onde o Privoxy trabalha).
114 
+    No Firefox, o caminho � "Ferramentas &gt; Op�es &gt; Geral &gt; Conex�o &gt; Proxy".
115 
+    No Mozilla, o caminho � "Editar &gt; Prefer�ncias &gt; Rede &gt; Servidores Proxy".
116 
+    No Internet Explorer, o caminho � "Ferramentas &gt; Op�es da Internet &gt; Conex�o &gt; Servidores Proxy".
117 
+    </p>
118 
+    <small>NT: Estes caminhos s�o para as vers�es em portugu�s dos navegadores, e podem variar
119 
+    conforme a vers�o em uso.</small>
120 
+    <p>
121 
+    Voc� tamb�m deve ajustar o seu proxy SSL (chamado pelo IE de "Seguro") para os mesmos
122 
+    valores, para esconder seu tr�fego SSL tamb�m. No Internet Explorer, essa configura��o
123 
+    fica parecida com isto:
124 
+    </p>
125 
+
126 
+    <img alt="LAN settings in IE"
127 
+    src="../img/screenshot-win32-ie-lan.jpg" />
128 
+    <img alt="Proxy settings in IE"
129 
+    src="../img/screenshot-win32-ie-proxies.jpg" />
130 
+
131 
+    <p>
132 
+    O uso do Privoxy � <strong>necess�rio</strong> pois
133 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">
134 
+    os navegadores deixam vazar as suas requisi�es DNS quando eles
135 
+    usam um proxy SOCKS diretamente</a>,
136 
+    o que � ruim para seu anonimato.
137 
+    Privoxy tamb�m remove certos cabe�alhos problem�ticos das suas requisi�es, e
138 
+    bloqueia sites irritantes de an�ncios tais como "DoubleClick".
139 
+    </p>
140 
+
141 
+    <p>
142 
+    Para testar o funcionamento, voc� deve conhecer o seu endere�o IP normal,
143 
+    de maneira que voc� possa comprovar que o endere�o realmente mude quando Tor
144 
+    est� em uso.
145 
+    Clique em "Iniciar &gt; Executar" e em seguida digite <kbd>cmd</kbd> para abrir
146 
+    uma janela de prompt de comando. Ao chegar ao prompt de comando, execute o
147 
+    comando <kbd>ipconfig</kbd>.
148 
+    Se voc� estiver trabalhando atr�s de um Firewall com NAT (<small>NT: Isso acontece
149 
+    se voc� usa um modem ADSL em modo router, ou usa conex�o de r�dio sem IP registrado.</small>),
150 
+    voc� pode usar um dos sites listados abaixo para verificar qual o IP da sua conex�o
151 
+    internet.<br />
152 
+    Quando souber o seu IP, inicie o Tor e o Privoxy e visite qualquer um desses sites
153 
+    novamente. Se tudo estiver funcionando corretamente, o endere�o IP mostrado ter� mudado.
154 
+    </p>
155 
+
156 
+    <p>
157 
+    <a href="http://www.showmyip.com/">showmyip.com</a> e
158 
+    <a href="http://ipid.shat.net">ipid.shat.net</a>
159 
+    s�o sites que mostram o seu endere�o IP atual, de forma que voc� pode saber
160 
+    qual o seu endere�o e pa�s de origem.
161 
+    </p>
162 
+
163 
+    <p>
164 
+    Se voc� usa um firewall pessoal que limita a capacidade de seu computador de
165 
+    abrir conex�es consigo mesmo, certifique-se de permitir conex�es das suas aplica�es locais
166 
+    para as portas locais 8118 e 9050. Se o seu firewall barra conex�es de sa�da, abra
167 
+    uma passagem nele de forma que se possa conectar pelo menos as portas TCP 80, 443 e 9001-9033.
168 
+    <br />
169 
+    Para mais sugest�es de resolu��o de problemas, visite o
170 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ">FAQ</a>.
171 
+    </p>
172 
+
173 
+    <p>
174 
+    Para "Torificar" outra aplica��o que suporte HTTP, simplesmente ajuste ela para
175 
+    usar o Privoxy como proxy HTTP (em localhost, porta 8118).
176 
+    Para usar diretamente o proxy SOCKS (por exemplo, para programas de mensagens
177 
+    instant�neas, Jabber, IRC, etc), ajuste sua aplica��o para usar diretamente
178 
+    o Tor (localhost, porta 9050).
179 
+    </p>
180 
+
181 
+    <p>
182 
+    Para aplica�es que n�o suportem nem SOCKS nem HTTP,
183 
+    tente
184 
+    <a href="http://www.socks.permeo.com/Download/SocksCapDownload/index.asp">SocksCap</a>,
185 
+    <a href="http://www.freecap.ru/eng/">FreeCap</a>,
186 
+    ou ent�o o cliente SOCKS
187 
+    <a href="http://www.hummingbird.com/products/nc/socks/index.html?cks=y">Hummingbird</a>.
188 
+    <br />
189 
+    (FreeCap � software livre; os outros s�o propriet�rios)
190 
+    </p>
191 
+
192 
+    <p>
193 
+    Para mais informa�es detalhadas sobre como "Torificar" outras aplica�es,visite o
194 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify HOWTO</a>.
195 
+    Se voc� tem mais sugest�es sobre como melhorar este documento, por favor
196 
+    <a href="<page about/contact>">envie-as para a gente</a>.
197 
+    </p>
198 
+
199 
+    <p>
200 
+    Obrigado!
201 
+    </p>
202 
+  </div>
203 
+  <!-- END MAINCOL -->
204 
+  <div id = "sidecol">
205 
+#include "side.wmi"
206 
+#include "info.wmi"
207 
+  </div>
208 
+  <!-- END SIDECOL -->
209 
+</div>
210 
+<!-- END CONTENT -->
211 
+#include <foot.wmi>
docs/ru/N900.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,159 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21979 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: N900 Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/N900>">N900</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="Maemo"></a>
14 
+    <h2><a class="anchor" href="#Maemo">Установка TOR на Maemo</a></h2>
15 
+    <br />
16 
+    <p>
17 
+    Если у Вас телефон Maemo модели, отличной от <a href="#N900">N900</a>, мы
18 
+    рекомендуем установить пакет TOR с <a
19 
+    href="http://maemo.org/packages/view/tor/">офф.сайта Maemo</a>. Tor Project
20 
+    не работает над этими пакетами, они разрабатываются сообществом Maemo.
21 
+    </p>
22 
+
23 
+    <a id="N900"></a>
24 
+    <h2><a class="anchor" href="#N900">Установка Tor на N900</a></h2>
25 
+    <br />
26 
+    <p>
27 
+    Данное руководство может облегчить Вам установку<a
28 
+    href="https://garage.maemo.org/projects/tor-status">опытного образца
29 
+    Tor-оператора</a> и собственно TOR в формате пакета для телефона N900 фирмы
30 
+    Nokia. На данный момент эта сборка не испытывалась. Браузер при
31 
+    использовании этой сборки не имеет средств наподобие Torbutton, настоятельно
32 
+    рекомендуется в ближайшее время не использовать сборку в целях, требующих
33 
+    высокую степень конфиденциальности пользователя.
34 
+    </p>
35 
+
36 
+    <p>
37 
+    Откройте Менеджер приложений: <br /> <a href="../img/N900/1_app_menu.png">
38 
+    <img border="0" alt="N900 application menu"
39 
+    src="../img/N900/1_app_menu-small.png"/> </a>
40 
+    </p>
41 
+
42 
+    <p>
43 
+    Вызовите меню Менеджера приложений в верху экрана: <br /> <a
44 
+    href="../img/N900/2_app_manager.png"> <img border="0" alt="N900 application
45 
+    manager" src="../img/N900/2_app_manager-small.png"/> </a>
46 
+    </p>
47 
+
48 
+    <p>
49 
+    Выберите 'Разделы приложений': <br /> <a
50 
+    href="../img/N900/3_app_managermenu.png"> <img border="0" alt="N900
51 
+    application catalogs" src="../img/N900/3_app_managermenu-small.png"/> </a>
52 
+    </p>
53 
+
54 
+    <p>
55 
+    Нажмите 'Создать', чтобы добавить источник разрабатываемых версий
56 
+    дополнительного ПО.<br /> <small>Обратите внимание: данный источник содержит
57 
+    непроверенные пакеты, которые могут нарушить работу Вашего устройства. <br
58 
+    /> Ознакомьтесь с  <a href="http://wiki.maemo.org/Extras-devel">информацией
59 
+    об источнике</a>. Вам стоит отключить источник разрабатываемого
60 
+    дополнительного ПО после установки TOR, или оставить его, на свой
61 
+    риск.</small> <br /> <a href="../img/N900/4_catalog_list.png"> <img
62 
+    border="0" alt="N900 catalog list"
63 
+    src="../img/N900/4_catalog_list-small.png"/> </a>
64 
+    </p>
65 
+
66 
+    <p>
67 
+    Enter the following information into the catalog addition screen:Введите
68 
+    следующую информацию в форму добавления дополнительного раздела:
69 
+    <p>
70 
+    <pre>
71 
+    Название каталога:    Extras devel
72 
+    Адрес каталога:    http://repository.maemo.org/extras-devel/
73 
+    Дистрибутив:        fremantle
74 
+    Компоненты:    free non-free
75 
+    </pre>
76 
+    </p>
77 
+    <br />Снимите опцию 'Раздел отключён', нажмите 'Сохранить'. Обновление
78 
+    разделов займёт некоторое время.<br /> <a
79 
+    href="../img/N900/5_new_catalog.png"> <img border="0" alt="N900 new catalog"
80 
+    src="../img/N900/5_new_catalog-small.png"/> </a>
81 
+    </p>
82 
+
83 
+    <p>
84 
+    Нажмите 'Скачать' в Менеджере приложений: <br /> <a
85 
+    href="../img/N900/6_app_manager.png"> <img border="0" alt="N900 app manager"
86 
+    src="../img/N900/6_app_manager-small.png"/> </a>
87 
+    </p>
88 
+
89 
+    <p>
90 
+    Выберите раздел Сеть (или воспользуйтесь поиском по ключевому слову TOR):
91 
+    <br /> <a href="../img/N900/7_app_categories.png"> <img border="0" alt="N900
92 
+    application categories" src="../img/N900/7_app_categories-small.png"/> </a>
93 
+    </p>
94 
+
95 
+    <p>
96 
+    Просмотрите раздел полностью и выберите 'Tor Status Area Applet': <br /> <a
97 
+    href="../img/N900/8_app_list.png"> <img border="0" alt="N900 application
98 
+    list" src="../img/N900/8_app_list-small.png"/> </a>
99 
+    </p>
100 
+
101 
+    <p>
102 
+    Ознакомьтесь с соглашением и нажмите 'Продолжить': <br /> <a
103 
+    href="../img/N900/9_disclaimer.png"> <img border="0" alt="N900 disclaimer"
104 
+    src="../img/N900/9_disclaimer-small.png"/> </a>
105 
+    </p>
106 
+
107 
+    <p>
108 
+    По завершению установки отключите раздел разрабатываемого доп.ПО и
109 
+    перезагрузите устройство: <br /> <a href="../img/N900/10_success.png"> <img
110 
+    border="0" alt="N900 success" src="../img/N900/10_success-small.png"/> </a>
111 
+    </p>
112 
+
113 
+    <p>
114 
+    После перезагрузки N900, откройте меню состояния: <br /> <a
115 
+    href="../img/N900/11_after_rebooting.png"> <img border="0" alt="N900 status
116 
+    menu post-reboot" src="../img/N900/11_after_rebooting-small.png"/> </a>
117 
+    </p>
118 
+
119 
+    <p>
120 
+    Выберите 'The Onion Router' из списка: <br /> <a
121 
+    href="../img/N900/12_status_menu.png"> <img border="0" alt="N900 status menu
122 
+    selection" src="../img/N900/12_status_menu-small.png"/> </a>
123 
+    </p>
124 
+
125 
+    <p>
126 
+    Включите шифруемую маршрутизацию и нажмите 'Save': <br /> <a
127 
+    href="../img/N900/13_enable_tor.png"> <img border="0" alt="N900 enabling
128 
+    Tor" src="../img/N900/13_enable_tor-small.png"/> </a>
129 
+    </p>
130 
+
131 
+    <p>
132 
+    Откройте <a href="https://check.torproject.org/">страницу проверки</a>,
133 
+    чтобы убедиться, что маршрутизация производится корректно: <br /> <a
134 
+    href="../img/N900/14_check_tor.png"> <img border="0" alt="N900 check Tor"
135 
+    src="../img/N900/14_check_tor-small.png"/> </a>
136 
+    </p>
137 
+
138 
+    <p>
139 
+    Обращаем Ваше внимание, что в репозитории ОС не всегда находятся последние
140 
+    версии TOR. Также браузер N900 не имеет дополнения Torbutton. Т.е. будучи
141 
+    пригодным для обхода ограничений по IP-адресам, браузер N900 не
142 
+    рекомендуется к использованию, если конфиденциальность просмотра является
143 
+    критическим требованием.
144 
+    </p>
145 
+
146 
+    <hr />
147 
+
148 
+    <p>Если у Вас есть предложения к правке этого документа, пожалуйста, <a
149 
+    href="<page about/contact>">присылайте их нам</a>. Спасибо!</p>
150 
+  </div>
151 
+  <!-- END MAINCOL -->
152 
+  <div id = "sidecol">
153 
+#include "side.wmi"
154 
+#include "info.wmi"
155 
+  </div>
156 
+  <!-- END SIDECOL -->
157 
+</div>
158 
+<!-- END CONTENT -->
159 
+#include <foot.wmi>
docs/ru/debian-vidalia.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,117 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22269 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Vidalia: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian-vidalia>">Vidalia Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a> <a id="packages"></a>
14 
+    <h2><a class="anchor" href="#debian">Vidalia на Ubuntu или Debian</a></h2>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>Не используйте пакеты из репозитория Ubuntu.</b> Они не поддерживаются и
19 
+    являются устаревшими. Вы не сможете получать важные обновления компонентов и
20 
+    критические обновления.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    You'll need to set up our package repository before you can fetch
25 
+    Vidalia. First, you need to figure out the name of your distribution. If
26 
+    you're using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty",
27 
+    8.10 is "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's
28 
+    "etch", and Debian Lenny is "lenny". Then add this line to your
29 
+    <tt>/etc/apt/sources.list</tt> file:<br />
30 
+    <pre>
31 
+    deb     http://deb.torproject.org/torproject.org &lt;ИМЯ_ДИСТРИБУТИВА&gt; main
32 
+    </pre>
33 
+    где Вы подставляете имя дистрибутива (etch, lenny, sid, karmic, jaunty,
34 
+    intrepid, hardy) вместо строки &lt;ИМЯ_ДИСТРИБУТИВА&gt;.
35 
+    </p>
36 
+
37 
+    <p>
38 
+    Then add the gpg key used to sign the packages by running the following
39 
+    commands at your command prompt:
40 
+    <pre>
41 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
42 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
43 
+    </pre>
44 
+    Now refresh your sources and install Vidalia by running the following
45 
+    commands at your command prompt:
46 
+    <pre>
47 
+    apt-get update
48 
+    apt-get install vidalia
49 
+    </pre>
50 
+    </p>
51 
+
52 
+    <p>
53 
+    Теперь Vidalia установлена и запущена. Ознакомьтесь со <a href="<page
54 
+    docs/tor-doc-unix>#polipo">следующим шагом</a> руководства "Vidalia на
55 
+    Linux/Unix".
56 
+    </p>
57 
+
58 
+    <p style="font-size: small">
59 
+    DNS-запись <code>deb.torproject.org</code> ссылается на множество
60 
+    независимых серверов. Если у Вас не получается получить доступ к серверам с
61 
+    использованием этого имени, вы моете попробовать одно из следующих имён:
62 
+    <code>deb-master.torproject.org</code>, <code>mirror.netcologne.de</code>
63 
+    или <code>vidalia.mirror.youam.de</code>.
64 
+    </p>
65 
+
66 
+    <hr />
67 
+
68 
+    <a id="source"></a>
69 
+    <h2><a class="anchor" href="#source">Сборка из исходных кодов</a></h2>
70 
+    <br />
71 
+
72 
+    <p>
73 
+    Если Вы хотите собрать свой пакет из исходных кодов, Вам потребуется
74 
+    добавить запись <tt>deb-src</tt> в файл <tt>sources.list</tt>.
75 
+    <pre>
76 
+    deb-src http://deb.torproject.org/torproject.org &lt;ИМЯ_ДИСТРИБУТИВА&gt; main
77 
+    </pre>
78 
+    Вам также потребуется установить пакеты, необходимые для сборки собственных
79 
+    пакетов, а также пакеты, необходимые для сборки Vidalia:
80 
+    <pre>
81 
+    apt-get install build-essential fakeroot devscripts qt4-dev-tools qt4-designer libqt4-dev g++ cmake
82 
+    apt-get build-dep vidalia
83 
+    </pre>
84 
+    Теперь Вы можете собрать Vidalia в ~/debian-packages:
85 
+    <pre>
86 
+    mkdir ~/debian-packages; cd ~/debian-packages
87 
+    apt-get source vidalia
88 
+    cd vidalia-*
89 
+    debuild -rfakeroot -uc -us
90 
+    cd ..
91 
+    </pre>
92 
+    Теперь Вы можете установить созданный пакет:
93 
+    <pre>
94 
+    sudo dpkg -i vidalia_*.deb
95 
+    </pre>
96 
+    </p>
97 
+
98 
+    <p>
99 
+    Теперь Vidalia установлена и запущена. Ознакомьтесь со <a href="<page
100 
+    docs/tor-doc-unix>#polipo">следующим шагом</a> руководства "Vidalia на
101 
+    Linux/Unix".
102 
+    </p>
103 
+
104 
+    <hr />
105 
+
106 
+    <p>Если у Вас есть предложения по улучшению этого документа, пожалуйста, <a
107 
+    href="<page about/contact>">ознакомьте нас с ними</a>. Спасибо!</p>
108 
+  </div>
109 
+  <!-- END MAINCOL -->
110 
+  <div id = "sidecol">
111 
+#include "side.wmi"
112 
+#include "info.wmi"
113 
+  </div>
114 
+  <!-- END SIDECOL -->
115 
+</div>
116 
+<!-- END CONTENT -->
117 
+#include <foot.wmi>
docs/ru/debian.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,177 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22268 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Debian/Ubuntu Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/debian>">Debian/Ubuntu Instructions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="debian"></a>
14 
+    <h2><a class="anchor" href="#debian">Вариант 1: TOR на Debian lenny, Debian sid
15 
+    или Debian testing</a></h2>
16 
+    <br />
17 
+
18 
+    <p>
19 
+    Если у Вас Debian lenny, sid или squeeze, просто выполните команду<br />
20 
+    <tt>apt-get install tor tor-geoipdb</tt>
21 
+    </p>
22 
+
23 
+    <p>
24 
+    Обратите внимание, что этот способ не гарантирует установку последней версии
25 
+    TOR, но у Вас будет возможность получать важные обновления
26 
+    безопасности. Чтобы установить последнюю версию TOR, см.вариант 2 ниже.
27 
+    </p>
28 
+
29 
+    <p>
30 
+    Теперь TOR установлен и работает. Ознакомьтесь со <a href="<page
31 
+    docs/tor-doc-unix>#polipo">следующим разделом</a> руководства "Tor на
32 
+    Linux/Unix".
33 
+    </p>
34 
+
35 
+    <hr /> <a id="ubuntu"></a> <a id="packages"></a>
36 
+    <h2><a class="anchor" href="#ubuntu">Вариант 2: Tor на Ubuntu или Debian</a></h2>
37 
+    <br />
38 
+
39 
+    <p>
40 
+    <b>Не используйте пакеты из репозиториев Ubuntu.</b> Они не поддерживаются и
41 
+    являются устаревшими. Т.е. Вы не сможете получать обновления компонентов и
42 
+    критические обновления.
43 
+    </p>
44 
+
45 
+    <p>
46 
+    You'll need to set up our package repository before you can fetch
47 
+    Tor. First, you need to figure out the name of your distribution. If you're
48 
+    using Ubuntu 9.10 or 10.04, it's "karmic", while 9.04 is "jaunty", 8.10 is
49 
+    "intrepid", and 8.04 is "hardy". If you're using Debian Etch, it's "etch",
50 
+    and Debian Lenny is "lenny". Then add this line to your
51 
+    <tt>/etc/apt/sources.list</tt> file:<br />
52 
+    <pre>
53 
+    deb     http://deb.torproject.org/torproject.org &lt;ИМЯ_ДИСТРИБУТИВА&gt; main
54 
+    </pre>
55 
+    Где &lt;ИМЯ_ДИСТРИБУТИВА&gt; следует заменить на имя вашего дистрибутива
56 
+    (например, etch, lenny, sid, karmic, jaunty, intrepid, hardy и т.д.).
57 
+    </p>
58 
+
59 
+    <p>
60 
+    Then add the gpg key used to sign the packages by running the following
61 
+    commands at your command prompt:
62 
+    <pre>
63 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
64 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
65 
+    </pre>
66 
+    Now refresh your sources and install Tor by running the following commands
67 
+    at your command prompt:
68 
+    <pre>
69 
+    apt-get update
70 
+    apt-get install tor tor-geoipdb
71 
+    </pre>
72 
+    </p>
73 
+
74 
+    <p>
75 
+    Теперь TOR установлен и работает. Ознакомьтесь со <a href="<page
76 
+    docs/tor-doc-unix>#polipo">следующим разделом</a> руководства "Tor на
77 
+    Linux/Unix".
78 
+    </p>
79 
+
80 
+    <p style="font-size: small">
81 
+    DNS-запись <code>deb.torproject.org</code> ссылается на множество
82 
+    независимых серверов. Если у Вас не получается получить доступ к серверам с
83 
+    использованием этого имени, вы моете попробовать одно из следующих имён:
84 
+    <code>deb-master.torproject.org</code>, <code>mirror.netcologne.de</code>
85 
+    или <code>tor.mirror.youam.de</code>.
86 
+    </p>
87 
+
88 
+    <hr /> <a id="development"></a>
89 
+    <h2><a class="anchor" href="#development">Вариант 3: Использование текущей ветки
90 
+    разработки TOR на Debian или Ubuntu</a></h2>
91 
+    <br />
92 
+
93 
+    <p>Если Вы хотите использовать <a href="<page
94 
+    download/download>#packagediff">разрабатываемую версию</a> TOR (более функциональную,
95 
+    но и более «сырую»), Вам понадобится установить другой набор источников в
96 
+    файл <tt>/etc/apt/sources.list</tt>:<br />
97 
+    <pre>
98 
+    deb     http://deb.torproject.org/torproject.org &lt;ИМЯ_ДИСТРИБУТИВА&gt; main
99 
+    deb     http://deb.torproject.org/torproject.org experimental-&lt;ИМЯ_ДИСТРИБУТИВА&gt; main
100 
+    </pre>
101 
+    Где Вы также подставляете имя своего дистрибутива (etch, lenny, sid, karmic,
102 
+    jaunty, intrepid, hardy) вместо строки &lt;ИМЯ_ДИСТРИБУТИВА&gt;.
103 
+    </p>
104 
+
105 
+    <p>
106 
+    Then run the following commands at your command prompt:
107 
+    <pre>
108 
+    gpg --keyserver keys.gnupg.net --recv 886DDD89
109 
+    gpg --export A3C4F0F979CAA22CDBA8F512EE8CBC9E886DDD89 | sudo apt-key add -
110 
+    apt-get update
111 
+    apt-get install tor tor-geoipdb
112 
+    </pre>
113 
+    </p>
114 
+
115 
+    <p>
116 
+    Теперь TOR установлен и работает. Ознакомьтесь со <a href="<page
117 
+    docs/tor-doc-unix>#polipo">следующим разделом</a> руководства "Tor на
118 
+    Linux/Unix".
119 
+    </p>
120 
+
121 
+    <hr /> <a id="source"></a>
122 
+    <h2><a class="anchor" href="#source">Сборка из исходных кодов</a></h2>
123 
+    <br />
124 
+
125 
+    <p>
126 
+    Если Вы хотите собрать свой пакет из исходных кодов, Вам потребуется
127 
+    добавить запись <tt>deb-src</tt> в файл <tt>sources.list</tt>.
128 
+    <pre>
129 
+    # For the stable version.
130 
+    # For the unstable version.
131 
+
132 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
133 
+
134 
+
135 
+    deb-src http://deb.torproject.org/torproject.org &lt;DISTRIBUTION&gt; main
136 
+    deb-src http://deb.torproject.org/torproject.org experimental-&lt;DISTRIBUTION&gt; main
137 
+    </pre>
138 
+    Вам также потребуется установить пакеты, необходимые для сборки собственных
139 
+    пакетов, а также пакеты, необходимые для сборки TOR:
140 
+    <pre>
141 
+    apt-get install build-essential fakeroot devscripts
142 
+    apt-get build-dep tor
143 
+    </pre>
144 
+    Теперь Вы можете собрать TOR в ~/debian-packages:
145 
+    <pre>
146 
+    mkdir ~/debian-packages; cd ~/debian-packages
147 
+    apt-get source tor
148 
+    cd tor-*
149 
+    debuild -rfakeroot -uc -us
150 
+    cd ..
151 
+    </pre>
152 
+    Теперь Вы можете установить собранный пакет:
153 
+    <pre>
154 
+    sudo dpkg -i tor_*.deb
155 
+    </pre>
156 
+    </p>
157 
+
158 
+    <p>
159 
+    Теперь TOR установлен и работает. Ознакомьтесь со <a href="<page
160 
+    docs/tor-doc-unix>#polipo">следующим разделом</a> руководства "Tor на
161 
+    Linux/Unix".
162 
+    </p>
163 
+
164 
+    <hr />
165 
+
166 
+    <p>Если у Вас есть предложения по улучшению этого документа, пожалуйста, <a
167 
+    href="<page about/contact>">присылайте их нам</a>. Спасибо!</p>
168 
+  </div>
169 
+  <!-- END MAINCOL -->
170 
+  <div id = "sidecol">
171 
+#include "side.wmi"
172 
+#include "info.wmi"
173 
+  </div>
174 
+  <!-- END SIDECOL -->
175 
+</div>
176 
+<!-- END CONTENT -->
177 
+#include <foot.wmi>
docs/ru/rpms.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,88 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21907 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: CentOS/Fedora/OpenSUSE Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/rpms>">RPMs</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <a id="rpms"></a>
14 
+    <h2><a class="anchor" href="#rpms">Пакеты Tor для дистрибутивов, основанных на
15 
+    Red Hat Packages' Manager (RPM).</a></h2>
16 
+    <br />
17 
+
18 
+    <p>Не используйте пакеты в основных репозиториях. Зачастую они являются
19 
+    устаревшими. То есть Вы не сможете получать обновления компонентов и
20 
+    критические обновления безопасности.
21 
+    </p>
22 
+
23 
+    <p>
24 
+    Вам потребуется настроить репозиторий Tor, прежде чем Вы сможете загрузить
25 
+    программу. В случае с использованием менеджера пакетов Yum, в каталоге
26 
+    /etc/yum.repos.d/, создайте файл с названием torproject.repo.  Заполните
27 
+    файл, как показано ниже:
28 
+    <pre>[torproject]
29 
+    name=Tor and Vidalia
30 
+    enabled=1
31 
+    autorefresh=0
32 
+    baseurl=http://deb.torproject.org/torproject.org/rpm/DISTRIBUTION/
33 
+    type=rpm-md
34 
+    gpgcheck=1
35 
+    gpgkey=http://deb.torproject.org/torproject.org/rpm/RPM-GPG-KEY-torproject.org
36 
+    </pre>
37 
+
38 
+    Если Вы хотите поддерживать Tor в актуальном состоянии, Вам потребуется
39 
+    изменить строку DISTRIBUTION на одну из следующих: centos4, centos5, fc10,
40 
+    fc11, fc12, suse</p>
41 
+
42 
+    <p>Если же Вы хотите, чтобы у Вас была установлена самая последняя (опытная)
43 
+    версия Tor, замените строку DISTRIBUTION одной из этих:
44 
+    centos4-experimental, centos5-experimental, fc10-experimental,
45 
+    fc11-experimental, fc12-experimental, suse-experimental</p>
46 
+
47 
+    <p>
48 
+    Теперь Tor установлен и запущен. Ознакомьтесь со <a href="<page
49 
+    docs/tor-doc-unix>#polipo">следующим разделом</a> руководства "Tor on
50 
+    Linux/Unix".
51 
+    </p>
52 
+
53 
+    <p style="font-size: small">
54 
+    DNS-запись <code>deb.torproject.org</code> ссылается на множество
55 
+    независимых серверов. Если у Вас не получается получить доступ к серверам
56 
+    обновления с использованием этого имени, вы моете попробовать одно из
57 
+    следующих имён: <code>deb-master.torproject.org</code>,
58 
+    <code>mirror.netcologne.de</code> или <code>tor.mirror.youam.de</code>.
59 
+    </p>
60 
+
61 
+    <hr />
62 
+
63 
+    <hr />
64 
+
65 
+    <a id="source"></a>
66 
+    <h2><a class="anchor" href="#source">Сборка из исходных кодов</a></h2>
67 
+    <br />
68 
+
69 
+    <p>
70 
+    Если вы хотите собрать пакет с Tor из исходных кодов, пожалуйста
71 
+    ознакомьтесь с <a href="<gitblob>doc/tor-rpm-creation.txt">инструкциями по
72 
+    созданию пакета</a>.
73 
+    </p>
74 
+
75 
+    <hr />
76 
+
77 
+    <p>Если у Вас есть предложения по улучшению этого документа <a href="<page
78 
+    about/contact>">сообщите нам</a>. Спасибо!</p>
79 
+  </div>
80 
+  <!-- END MAINCOL -->
81 
+  <div id = "sidecol">
82 
+#include "side.wmi"
83 
+#include "info.wmi"
84 
+  </div>
85 
+  <!-- END SIDECOL -->
86 
+</div>
87 
+<!-- END CONTENT -->
88 
+#include <foot.wmi>
docs/ru/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/ru/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,229 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Работа с клиентом <a href="<page index>">Tor</a> в операционной системе Mac
14 
+    OS X</h1>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>Обратите внимание на то, что в этом тексте представлены инструкции по
19 
+    установке клиента Tor в операционной системе Mac OS X. Если вы хотите
20 
+    ретранслировать трафик для других и, таким образом, поддержать рост сети
21 
+    (пожалуйста, сделайте это), прочитайте руководство <a href="<page
22 
+    docs/tor-doc-relay>">Настройка ретранслятора</a>.</b>
23 
+    </p>
24 
+
25 
+    <hr />
26 
+    <a id="installing"></a>
27 
+    <h2><a class="anchor" href="#installing">Шаг первый: Скачивание и Установка
28 
+    Tor</a></h2>
29 
+    <br />
30 
+
31 
+    <p>
32 
+    The install for Macintosh OS X bundles <a href="<page index>">Tor</a>, <a
33 
+    href="<page projects/vidalia>">Vidalia</a> (a graphical interface for Tor), <a
34 
+    href="<page projects/torbutton>">Torbutton</a>, and <a
35 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (a web
36 
+    proxy)  into one package, with the four applications pre-configured to work
37 
+    together.  Download either the <a
38 
+    href="../<package-osx-bundle-stable>">stable</a> or the <a
39 
+    href="../<package-osx-bundle-alpha>">experimental</a> version of the OS X
40 
+    bundle for Intel, or look for more options on the <a href="<page
41 
+    download/download>">download page</a>.
42 
+    </p>
43 
+
44 
+    <p>Когда вы скачали dmg-файл, кликните по нему два раза и
45 
+    установите. Просмотрите открывшийся пакет Vidalia Bundle в файловом
46 
+    менеджере Finder.  Установить пакет очень легко. Просто перенесите иконку
47 
+    Vidalia (луковица) в папку Приложения (Applications). При желании кликните
48 
+    два раза по скрипту "установить torbutton" (install torbutton) и он
49 
+    установит плагин torbutton в браузер Firefox. Вы можете получить плагин
50 
+    torbutton также на сайте Mozilla Add-ons путем поиска "torbutton".</p>
51 
+
52 
+    <p>После завершения установки вы можете запустить Vidalia, выбрав его иконку в
53 
+    папке "Приложения". Черная перечеркнутая луковица означает, что Tor не
54 
+    работает. Вы можете запустить работу Tor, выбрав Старт в меню "Tor",
55 
+    расположенном вверху экрана.
56 
+    </p>
57 
+
58 
+    <p>Когда Tor запущен, иконка программы Vidalia будет выглядеть следующим
59 
+    образом:
60 
+    </p>
61 
+
62 
+    <p><img alt="vidalia running tor"
63 
+    src="../img/screenshot-osx-vidalia.png"
64 
+    border="1"/></p>
65 
+
66 
+    <p>Программа Polipo устанавливается как часть установочного пакета Tor. После
67 
+    установки, она запустится автоматически сразу после перезагрузки вашего
68 
+    компьютера. Нет необходимости настраивать приложение Polipo на использование
69 
+    Tor; необходимая конфигурация Polipo для Tor была прописана во время
70 
+    установки.
71 
+    </p>
72 
+
73 
+    <hr />
74 
+    <a id="using"></a>
75 
+    <h2><a class="anchor" href="#using">Шаг второй: Настройка ваших приложений на
76 
+    использование сервиса Tor</a></h2>
77 
+    <br />
78 
+
79 
+    <p>После установки вам необходимо настроить ваши приложения на работу через
80 
+    Tor. Первым делом нужно настроить ваш браузер (программа для просмотра веб
81 
+    страниц).</p>
82 
+
83 
+    <p>Вам следует использовать Tor с браузером Firefox и дополнением Torbutton для
84 
+    обеспечения наилучшей безопасности. Чтобы включить Tor, кликните по красной
85 
+    кнопке "Tor отключен" и все настроено: </p>
86 
+
87 
+    <p><img alt="Torbutton plugin for Firefox"
88 
+    src="../img/screenshot-torbutton.png"
89 
+    border="1"/></p>
90 
+
91 
+    <p>
92 
+    Если вы планируете использовать Firefox не на том компьютере, куда
93 
+    установлен Tor, ознакомьтесь со <a
94 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">Списком
95 
+    часто задаваемых вопросов по использованию Tor на другом компьютере (FAQ for
96 
+    running Tor on a different computer)</a>.
97 
+    </p>
98 
+
99 
+    <p>Для "Торификации" других приложений, которые поддерживают HTTP прокси,
100 
+    просто укажите им на Polipo (который расположен здесь: localhost порт
101 
+    8118). Чтобы использовать SOCKS напрямую (для обмена мгновенными
102 
+    сообщениями, Jabber, IRC, и т.д.), вы можете направить свое приложение на
103 
+    Tor (localhost порт 9050), но прежде ознакомьтесь с содержимым<a
104 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">этого
105 
+    Списка часто задаваемых вопросов</a>, чтобы узнать почему это может быть
106 
+    опасно. Для настройки приложений, не поддерживающих ни SOCKS не HTTP,
107 
+    обратите внимание на <a
108 
+    href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a> или <a
109 
+    href="http://www.dest-unreach.org/socat/">socat</a>.</p>
110 
+
111 
+    <p>Чтобы получить информацию о том, как "Торифицировать" другие приложения,
112 
+    ознакомьтесь с <a
113 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Инструкцией
114 
+    по "Торификации"</a>.
115 
+    </p>
116 
+
117 
+    <hr />
118 
+    <a id="verify"></a>
119 
+    <h2><a class="anchor" href="#verify">Шаг третий: Убедитесь в том, что все
120 
+    работает корректно</a></h2>
121 
+    <br />
122 
+
123 
+    <p>
124 
+    Далее вам необходимо протестировать работу вашего браузера с Tor и
125 
+    убедиться, что ваш IP-адрес анонимизирован (т.е. скрыт). Откройте страницу
126 
+    <a href="https://check.torproject.org/">детектор Tor</a> и посмотрите,
127 
+    подтверждается ли сайтом использование сервиса Tor. (Если сайт не работает,
128 
+    обратитесь к <a
129 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">содержимому
130 
+    этого Списка часто задаваемых вопросов</a>, чтобы получить информацию о
131 
+    других методах тестирования работы Tor.)
132 
+    </p>
133 
+
134 
+    <p>Если у вас установлен персональный брандмауэр, который ограничивает
135 
+    возможность подключения вашего компьютера  к самому себе, убедитесь что вы
136 
+    разрешили подключения локальных приложений к локальным портам 8118 и
137 
+    9050. Если ваш брандмауэр блокирует исходящие подключения, измените
138 
+    настройки так, чтобы он мог подключаться хотя бы к TCP портам 80 и 443, а
139 
+    затем ознакомьтесь с <a
140 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">содержанием
141 
+    этого списка часто задаваемых вопросов</a>.
142 
+    </p>
143 
+
144 
+    <p>Если ничего из вышеперечисленного не помогло, обратитесь к <a
145 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">содержанию
146 
+    этого Списка часто задаваемых вопросов</a> для получения дополнительной
147 
+    информации.</p>
148 
+
149 
+    <p>
150 
+    Когда все заработало, узнайте больше о том <a href="<page
151 
+    download/download>#Warning">что предлагает, и что не предлагает сервис Tor </a>.
152 
+    </p>
153 
+
154 
+    <hr />
155 
+    <a id="server"></a> <a id="relay"></a>
156 
+    <h2><a class="anchor" href="#relay">Шаг четвертый: Настройте ретранслятор
157 
+    Tor</a></h2>
158 
+    <br />
159 
+
160 
+    <p>Сеть Tor полагается на волонтеров, предоставляющих пропускную способность
161 
+    своих компьютеров. Чем больше людей предоставляют ретрансляторы, тем быстрей
162 
+    будет работать сеть Tor. Если у вас есть как минимум 20Кб/сек. в обоих
163 
+    направлениях, пожалуйста поддержите Tor, настроив ретранслятор Tor. Мы
164 
+    создали множество возможностей, делающих ретрансляторы Tor простыми и
165 
+    удобными, включая ограничение предоставляемой пропускной способности,
166 
+    правила вывода (с тем чтобы вы могли ограничить вашу незащищенность к
167 
+    возможным жалобам), и поддержку динамических IP-адресов.</p>
168 
+
169 
+    <p>Наличие ретрансляторов в разных уголках сети Интернет - это то, что
170 
+    обеспечивает безопасность пользователей Tor. <a
171 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Создавая
172 
+    ретранслятор вы можете улучшить свою собственную анонимность</a>, так как
173 
+    удаленные сайты не могут установить происхождение запроса, ведь он может
174 
+    исходить как от вас, так и от других пользователей сети Tor, использующих
175 
+    ваш ретранслятор.</p>
176 
+
177 
+    <p>Больше информации на эту тему можно получить из руководства <a href="<page
178 
+    docs/tor-doc-relay>">Настройка ретранслятора</a>.</p>
179 
+
180 
+    <hr />
181 
+    <a id="uninstall"></a>
182 
+    <h2><a class="anchor" href="#uninstall">Как удалить Tor и Privoxy</a></h2>
183 
+    <br />
184 
+
185 
+    <p>Есть два пути удаления пакета с компьютера, с использованием системного
186 
+    файлового менеджера Finder; или с помощью командной строки или основанного
187 
+    на терминале (Terminal-based) деинсталлятора. Если вы хотите удалить Tor в
188 
+    операционной системе OS X, вот как это можно сделать:</p>
189 
+
190 
+    <p>Поменяйте настройки прокси в ваших приложениях на их изначальные значения.
191 
+    Если вы хотите просто перестать пользоваться сервисом Tor, вы можете
192 
+    остановиться на этом этапе.</p>
193 
+
194 
+    <p>Если вы хотите полностью удалить Tor и ваша учетная запись на компьютере
195 
+    обладает правами администратора, сделайте следующее:</p>
196 
+
197 
+    <ol>
198 
+    <li>Откройте системный файловый менеджер Finder и нажмите Приложения.</li>
199 
+    <li>Перенесите папку /Applications/Vidalia в корзину.</li>
200 
+    <li>Удалите из вашей системы папку /Library/Torbutton.</li>
201 
+    <li>В домашней директории перейдите в папку Library и удалите из неё директорию
202 
+    Vidalia.</li>
203 
+    </ol>
204 
+
205 
+    <p>Приложения Tor, Vidalia, и Polipo окончательно удалены из вашей системы.</p>
206 
+
207 
+    <p>Если вы умеете работать с командной строкой или Терминалом, вы можете
208 
+    удалить приложения вручную, как показано ниже:</p>
209 
+    <ul>
210 
+    <li>/Applications/Vidalia.app/</li>
211 
+    <li>/Library/Torbutton/</li>
212 
+    <li>~/Library/Vidalia</li>
213 
+    <li>~/.tor</li>
214 
+    </ul>
215 
+
216 
+    <hr />
217 
+
218 
+    <p>Если у вас есть предложения по улучшению этого документа, пожалуйста <a
219 
+    href="<page about/contact>">отправьте их нам</a>. Спасибо!</p>
220 
+  </div>
221 
+  <!-- END MAINCOL -->
222 
+  <div id = "sidecol">
223 
+#include "side.wmi"
224 
+#include "info.wmi"
225 
+  </div>
226 
+  <!-- END SIDECOL -->
227 
+</div>
228 
+<!-- END CONTENT -->
229 
+#include <foot.wmi>
docs/ru/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,330 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Настройка ретранслятора Tor</h1>
14 
+
15 
+
16 
+    <!-- BEGIN SIDEBAR -->
17 
+    <div class="sidebar-left">
18 
+    <h3>Этапы настройки</h3>
19 
+    <ol>
20 
+    <li><a href="<page docs/tor-doc-relay>#install">Скачивание и Установка</a></li>
21 
+    <li><a href="<page docs/tor-doc-relay>#setup">Настройка</a></li>
22 
+    <li><a href="<page docs/tor-doc-relay>#check">Проверка и Подтверждение</a></li>
23 
+    <li><a href="<page docs/tor-doc-relay>#after">Финальные шаги</a></li>
24 
+    </ol>
25 
+    </div>
26 
+
27 
+
28 
+    <!-- END SIDEBAR -->
29 
+    <hr />
30 
+
31 
+    <p>
32 
+    Сеть Tor полагается на волонтеров, предоставляющих пропускную способность
33 
+    своих компьютеров. Чем больше людей предоставляют ретрансляторы, тем быстрей
34 
+    будет работать сеть Tor. Если у вас есть как минимум 20Кб/сек. в обоих
35 
+    направлениях, пожалуйста поддержите Tor, настроив ретранслятор Tor. Мы
36 
+    создали множество возможностей, делающих ретрансляторы Tor простыми и
37 
+    удобными, включая <a href="<page docs/faq>#RelayFlexible">ограничение
38 
+    предоставляемой пропускной способности, правила вывода (с тем чтобы вы могли
39 
+    ограничить вашу незащищенность к возможным жалобам), и поддержку
40 
+    динамических IP-адресов</a>.
41 
+    </p>
42 
+
43 
+    <p>Вы можете установить ретранслятор Tor практически на <a
44 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">любую</a>
45 
+    операционную систему. Ретрансляторы Tor лучше всего работают на Linux, OS X
46 
+    Tiger или более поздних версиях, FreeBSD 5.x+, NetBSD 5.x+, и Windows Server
47 
+    2003 или более поздних версиях.
48 
+    </p>
49 
+
50 
+    <hr /> <a id="zero"></a> <a id="install"></a>
51 
+    <h2><a class="anchor" href="#install">Шаг первый: Скачивание и Установка Tor</a></h2>
52 
+    <br />
53 
+
54 
+    <p>Прежде чем начать, вы должны убедиться что программа Tor запущена и
55 
+    работает.
56 
+    </p>
57 
+
58 
+    <p>Посетите нашу <a href="<page download/easy-download>">страницу закачек</a> и
59 
+    установите "Установочный Пакет" для вашей Операционной Системы.
60 
+    </p>
61 
+
62 
+    <p>Если есть возможность, поэкспериментируйте с программой-клиентом некоторое
63 
+    время, чтобы убедиться, что сервис действительно работает.</p>
64 
+
65 
+    <hr /> <a id="setup"></a>
66 
+    <h2><a class="anchor" href="#setup">Шаг второй: Установка в качестве
67 
+    ретранслятора</a></h2>
68 
+    <br />
69 
+    <ol>
70 
+    <li>Проверьте правильно ли установлены ваши часы и временная зона. Если
71 
+    возможно, синхронизируйте ваши часы с публичными<a
72 
+    href="http://en.wikipedia.org/wiki/Network_Time_Protocol">серверами
73 
+    времени</a>.
74 
+    </li>
75 
+
76 
+    <li><strong>Настройка Tor с использованием графического интерфейса
77 
+    Vidalia</strong>:
78 
+    <ol>
79 
+
80 
+    <li>
81 
+    	<dt>Нажмите правой кнопкой мыши на иконку Vidalia, расположенную в системном
82 
+    трее. Выберете <tt>Панель Управления</tt>.</dt>
83 
+    	<dd><img alt="vidalia right click menu"
84 
+    src="../img/screenshot-win32-vidalia.png"></dd>
85 
+    </li>
86 
+
87 
+    <li>Нажмите <tt>Настроить Ретрансляцию</tt>.</li>
88 
+
89 
+    <li>
90 
+    	<dt>Выберете <tt>Ретранслировать трафик для сети Tor</tt> если вы хотите
91 
+    предоставлять публичный ретранслятор (рекомендуется), или выберете
92 
+    		<tt>Помочь заблокированным пользователям получить доступ к сети Tor</tt>
93 
+    если хотите предоставлять <a href="<page docs/faq>#RelayOrBridge">мост</a> для
94 
+    пользователей, находящихся в странах с Интернет цензурой.</dt>
95 
+    <dd><img alt="vidalia basic settings"
96 
+    src="../img/screenshot-win32-configure-relay-1.png"></dd>
97 
+    </li>
98 
+
99 
+    <li>Введите псевдоним для своего ретранслятора и свою контактную информацию на
100 
+    случай, если нам понадобиться связаться с вами по поводу возникших проблем.</li>
101 
+
102 
+    <li>Оставьте отмеченным пункт <tt>Пытаться настроить порт маршрутизации
103 
+    автоматически</tt>. Нажмите на кнопку <tt>Тест</tt>, чтобы проверить
104 
+    правильность работы. Если работает, отлично. Если нет, смотрите пункт номер
105 
+    3 ниже.</li>
106 
+
107 
+    <li><dt>Перейдите к вкладке <tt>Ограничения трафика</tt>.  Выберете ширину канала,
108 
+    которую вы хотите предоставить для других пользователей Tor.</dt>
109 
+    <dd><img alt="vidalia bandwidth limits"
110 
+    src="../img/screenshot-win32-configure-relay-2.png"></dd>
111 
+    </li>
112 
+
113 
+    <li><dt>Выберете вкладку <tt>Правила вывода/tt>. Если вы хотите разрешить остальным
114 
+    использовать ваш ретранслятор для этих сервисов, ничего не меняйте. Уберите
115 
+    галочку с тех сервисов, доступ к которым с <a href="<page
116 
+    docs/faq>#ExitPolicies">вашего ретранслятора вы хотите запретить</a>. Если вы не
117 
+    хотите предоставлять выводной ретранслятор, уберите галочки со всех
118 
+    сервисов.</dt>
119 
+    <dd><img alt="vidalia exit policies"
120 
+    src="../img/screenshot-win32-configure-relay-3.png"></dd>
121 
+    </li>
122 
+
123 
+    <li>Нажмите на кнопку <tt>Ok</tt>. Ознакомьтесь с шагом три (см. ниже), чтобы
124 
+    убедиться, что ретранслятор работает корректно.</li>
125 
+    </ol>
126 
+
127 
+    <br /> <strong>Ручная настройка</strong>:
128 
+    <ul>
129 
+    <li>Отредактируйте нижнюю часть <a
130 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">вашего
131 
+    torrc файла</a>. Если вы хотите предоставлять публичный ретранслятор
132 
+    (рекомендуется), убедитесь, что вы определили параметры ORPort и <a
133 
+    href="<page docs/faq>#ExitPolicies">обратите внимание на пункт ExitPolicy</a>; в
134 
+    противном случае если вы хотите предоставлять <a href="<page
135 
+    docs/faq>#RelayOrBridge">мост</a> для пользователей, находящихся в странах с
136 
+    Интернет цензурой, используйте только<a href="<page
137 
+    docs/bridges>#RunningABridge">эти строки</a>.
138 
+    </li>
139 
+
140 
+    </ul></li>
141 
+
142 
+    <li>Если вы используете брандмауэр, настройте его так, чтобы входящие
143 
+    подключения могли дойти до выбранных вами портов(ORPort, плюс DirPort, если
144 
+    вы его включили). Если у вас есть аппаратный брандмауэр (Linksys, кабельный
145 
+    модем и т.д.) вам стоит зайти на сайт <a
146 
+    href="http://portforward.com/">portforward.com</a>. Убедитесь также, что вы
147 
+    разрешили все <em>исходящие</em> подключения, так чтобы ваш ретранслятор мог
148 
+    подключаться ко всем остальным ретрансляторам сети Tor.
149 
+    </li>
150 
+
151 
+    <li>Перезапустите ваш ретранслятор. Если он <a
152 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">записывает
153 
+    предупреждения</a>, примите меры.
154 
+    </li>
155 
+
156 
+    <li>Подпишитесь на <a
157 
+    href="http://archives.seul.org/or/announce/">рассылку</a>. Она очень сжатая,
158 
+    информативная и позволит вам своевременно получать информацию о выходе новых
159 
+    стабильных версий программы. Возможно есть смысл подписаться также на <a
160 
+    href="<page docs/documentation>#MailingLists">более объемную рассылку Tor</a>.
161 
+    </li>
162 
+
163 
+    </ol>
164 
+
165 
+    <hr /> <a id="check"></a>
166 
+    <h2><a class="anchor" href="#check">Шаг третий: Убедитесь, что все работает</a></h2>
167 
+    <br />
168 
+
169 
+    <p>Как только ваш ретранслятор смог подключиться к сети, он попробует
170 
+    определить все ли настроенные вами порты доступны извне. Как правило, этот
171 
+    этап проходит быстро, но в отдельных случаях может занять до 20
172 
+    минут. Проверьте <a
173 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">содержание
174 
+    лог-файла</a>, он должен примерно выглядеть так: <tt>Внутреннее тестирование
175 
+    показало, что ваш ORPort доступен извне. Замечательно.</tt> Если вы не
176 
+    видите этого сообщения, это означает, что ваш ретранслятор не доступен
177 
+    извне; вы должны перепроверить ваши брандмауэры. Проверьте, что тестируются
178 
+    именно те IP-адреса и порты, которые вы собирались тестировать и т.д.
179 
+    </p>
180 
+
181 
+    <p>When it decides that it's reachable, it will upload a "server descriptor" to
182 
+    the directories, to let clients know what address, ports, keys, etc your
183 
+    relay is using. You can <a
184 
+    href="http://194.109.206.212/tor/status-vote/current/consensus">load one of
185 
+    the network statuses manually</a> and look through it to find the nickname
186 
+    you configured, to make sure it's there. You may need to wait up to one hour
187 
+    to give enough time for it to make a fresh directory.</p>
188 
+
189 
+    <hr /> <a id="after"></a>
190 
+    <h2><a class="anchor" href="#after">Шаг четвертый: Когда все работает</a></h2>
191 
+    <br />
192 
+
193 
+    <p>
194 
+    Мы также рекомендуем вам пройти следующие шаги:
195 
+    </p>
196 
+
197 
+    <p>
198 
+    6. Прочитайте <a
199 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">информацию
200 
+    об операционной безопасности</a>, где вы найдете несколько идей о том, как
201 
+    можно повысить безопасность вашего узла.
202 
+    </p>
203 
+
204 
+    <p>
205 
+    7. Если вы хотите установить более одного ретранслятора - это отлично, но,
206 
+    пожалуйста, установите <a
207 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">опцию
208 
+    МояСемья (MyFamily)</a> в конфигурационных файлах всех своих ретрансляторов.
209 
+    </p>
210 
+
211 
+    <p>
212 
+    8. Определитесь с ограничением трафика. Пользователи с кабельными модемами,
213 
+    DSL, и другие пользователи с асимметричным соединением (например, скорость
214 
+    скачивания выше скорости отдачи) должны установить лимиты своей нижней
215 
+    пропускной способности во избежание перегруженности. Прочитайте <a
216 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">Список
217 
+    часто задаваемых вопросов по ограничению трафика</a> для получения более
218 
+    подробной информации.
219 
+    </p>
220 
+
221 
+    <p>
222 
+    9. Сохраните резервную копию личного ключа вашего ретранслятора Tor
223 
+    (сохранен в папке "keys/secret_id_key" в вашей DataDirectory). Это
224 
+    идентификатор вашего ретранслятора и вам необходимо хранить его так, чтобы
225 
+    никто не смог просматривать трафик проходящий через ваш ретранслятор. Это
226 
+    очень важный файл, который нужно сохранить если вы хотите <a
227 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeRelay">перенести
228 
+    или восстановить ваш ретранслятор Tor</a>, на случай если что-то пойдет не
229 
+    так.
230 
+    </p>
231 
+
232 
+    <p>
233 
+
234 
+    10. Если вы контролируете DNS-сервера для вашего домена, подумайте об
235 
+    изменении вашего обратного хост-имени DNS на 'anonymous-relay', 'proxy' или
236 
+    'tor-proxy', так что когда другие люди увидят этот адрес в своих веб логах,
237 
+    они смогут быстрее понять, что происходит. Добавление <a
238 
+    href="<gitblob>contrib/tor-exit-notice.html">Уведомления от выводного узла
239 
+    Tor</a> на виртуальных хост для этого имени позволит существенно уменьшить
240 
+    количество жалоб, поступающих вам и вашему Интернет сервис провайдеру, если
241 
+    вы предоставляете выводной узел.
242 
+
243 
+    </p>
244 
+
245 
+    <p>
246 
+    11. Если на вашем компьютере не установлен веб сервер, пожалуйста, подумайте
247 
+    о том, чтобы изменить ваш ORPort на 443, а DirPort - на 80. Многие
248 
+    пользователи Tor блокируются брандмауэрами, которые позволяют им только
249 
+    просматривать веб страницы, и это изменение позволит им подключиться к
250 
+    вашему ретранслятору Tor. Пользователи ретрансляторов на базе Win32 могут
251 
+    просто изменить свои ORPort и DirPort напрямую в torrc-файлах и
252 
+    перезапустить Tor. Пользователи ретрансляторов, работающих на базе OS X или
253 
+    Unix не могут напрямую связываться с этими портами (так как они не
254 
+    корневые), так что им понадобится установить <a
255 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">
256 
+    переадресацию портов</a>, чтобы подключения могли доходить до ретрансляторов
257 
+    Tor. Если вы уже используете порты 80 и 443, но все же хотите помочь,
258 
+    другими полезными портами являются 22, 110, и 143.
259 
+    </p>
260 
+
261 
+    <p>
262 
+    12. Если ваш ретранслятор Tor предоставляет другие сервисы с того же
263 
+    IP-адреса, такие, например, как публичный веб сервер. Убедитесь, что
264 
+    подключения к нему разрешены с локального хоста. Вам необходимо разрешить
265 
+    эти подключения, потому что клиенты Tor неизбежно определят, ваш
266 
+    ретранслятор как <a
267 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">самый
268 
+    безопасный путь подключения к этому веб серверу</a>, и при подключении к
269 
+    нему будут всегда строить цепочку, в которой ваш ретранслятор будет
270 
+    последним. В случае, если вы не хотите разрешать эти подключения, вы должны
271 
+    полностью запретить их в ваших правилах вывода.
272 
+    </p>
273 
+
274 
+    <p>
275 
+    13. (Только для пользователей операционных систем Unix). Создайте отдельного
276 
+    пользователя для предоставления услуг ретранслятора. Если вы установили
277 
+    пакет для OS X, deb или rpm, это уже было сделано во время установки. В
278 
+    противном случае, вы можете сделать это вручную. (Ретранслятор Tor не
279 
+    обязательно должен работать из корня, так что лучше когда он работает не из
280 
+    корня. Работа от пользователя 'tor' позволяет избежать проблем с identd и
281 
+    другими сервисами, которые определяют имя пользователя. Если вы вроде как
282 
+    параноик, вы можете спокойно <a
283 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">поставить
284 
+    Tor в рамки chroot</a>.)
285 
+    </p>
286 
+
287 
+    <p>
288 
+    14. (Только для пользователей операционных систем Unix). Ваша операционная
289 
+    система скорее всего ограничивает число открытых файл дескрипторов для
290 
+    процесса до 1024 (а может и меньше). Если вы планируете предоставлять
291 
+    быстрый выводной узел, этого скорее всего не достаточно. На Linux, вы должны
292 
+    добавить строку "toruser hard nofile 8192" в ваш конфигурационный файл,
293 
+    расположенный здесь: /etc/security/limits.conf (где toruser - это
294 
+    пользователь запускающий процесс Tor), а после этого перезапустить Tor, если
295 
+    он установлен как пакет (или выйти из учетной записи и снова вернуться, если
296 
+    вы запускаете все вручную).
297 
+    </p>
298 
+
299 
+    <p>
300 
+    15. Если вы установили Tor с помощью пакета или инсталлятора, клиент Tor
301 
+    скорее всего будет запускаться автоматически при старте. Но если вы
302 
+    установили его из исходника, инитскрипты (initscripts), расположенные в
303 
+    contrib/tor.sh или в contrib/torctl могут оказаться для вас полезными.
304 
+    </p>
305 
+
306 
+    <p>
307 
+    Когда вы меняете настройку Tor, не забудьте проверить правильность работы
308 
+    вашего ретранслятора после внесенных изменений. Убедитесь, что вы указали
309 
+    контактную информацию (в строку "ContactInfo" файла torrc), с тем чтобы мы
310 
+    могли связаться с вами при необходимости (апгрэйт или возникновение
311 
+    проблем). Если у вас есть проблемы или вопросы, обратитесь к разделу<a
312 
+    href="<page docs/documentation>#Support">Поддержка</a> или <a href="<page
313 
+    about/contact>">сообщите нам</a> через tor-ops. Спасибо, что решили поддержать
314 
+    рост сети Tor!
315 
+    </p>
316 
+
317 
+    <hr />
318 
+
319 
+    <p>Если у вас появились предложения по улучшению этого документа, пожалуйста,
320 
+    <a href="<page about/contact>">отправьте их нам</a>. Спасибо!</p>
321 
+  </div>
322 
+  <!-- END MAINCOL -->
323 
+  <div id = "sidecol">
324 
+#include "side.wmi"
325 
+#include "info.wmi"
326 
+  </div>
327 
+  <!-- END SIDECOL -->
328 
+</div>
329 
+<!-- END CONTENT -->
330 
+#include <foot.wmi>
docs/ru/tor-doc-server.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,8 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 12076
3 
+# Status: obsolete
4 
+# Last-Translator: ygrekheretix/gmail/com
5 
+
6 
+#include "head.wmi" TITLE="Перенаправление" REFIRECT="docs/tor-doc-relay" CHARSET="UTF-8"
7 
+
8 
+#include <foot.wmi>
docs/ru/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,195 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21798 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Linux/BSD/Unix Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-unix>">Linux/BSD/Unix Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Запуск <a href="<page index>">Tor</a> на Linux/BSD/Unix</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>Обратите внимание, что это инструкции по запуску клиента Tor. Если бы Вы
18 
+    хотели предоставить свой траффик другим пользователям, чтобы помочь сети Tor
19 
+    расти, ознакомьтесь с руководством по <a href="<page
20 
+    docs/tor-doc-relay>">настройке узла</a>.</b>
21 
+    </p>
22 
+
23 
+    <hr /> <a id="installing"></a>
24 
+    <h2><a class="anchor" href="#installing">Шаг 1: загрузка и установка Tor</a></h2>
25 
+    <br />
26 
+
27 
+    <p>
28 
+    Последняя версия Tor находится на странице <a href="<page
29 
+    download/download>">загрузок</a>, где предоставлены пакеты для Debian, Red Hat,
30 
+    Gentoo, *BSD итд. Если Вы используете  Ubuntu, не используйте стандартные
31 
+    репозитории, лучше настройте <a href="<page docs/debian>#ubuntu">источник
32 
+    Tor</a>.
33 
+    </p>
34 
+
35 
+    <p>Если Вы собираете Tor из исходных кодов, сначала установите <a
36 
+    href="http://www.monkey.org/~provos/libevent/">библиотеку libevent</a>, а
37 
+    также убедитесь, что у Вас установлены библиотеки openssl и zlib (в том
38 
+    числе пакеы для разработчиков с окончанием -devel). Затем запустите:<br />
39 
+    <tt>tar xzf tor-<version-stable>.tar.gz; cd tor-<version-stable></tt><br />
40 
+    <tt>./configure &amp;&amp; make</tt><br /> После этого Вы можете запустить
41 
+    Tor как <tt>src/or/tor</tt>, или Вы можете выполнить команду <tt>make
42 
+    install</tt> (от имени суперпользователя root при необходимости) для
43 
+    установки Tor в папку /usr/local/, после чего Вы сможете запускать программу
44 
+    просто командой <tt>tor</tt>.
45 
+    </p>
46 
+
47 
+    <p>Изначально Tor настроен как клиент. В прогамме используется встроенный
48 
+    конфигурационный файл, и в большинстве случаев перенастройка Tor не
49 
+    потребуется. Теперь Tor установлен.
50 
+    </p>
51 
+
52 
+    <hr /> <a id="privoxy"></a> <a id="polipo"></a>
53 
+    <h2><a class="anchor" href="#polipo">Шаг 2: установка Polipo для браузера</a></h2>
54 
+    <br />
55 
+
56 
+    <p>После установки Tor Вам потребуется настроить используемые Вами приложения
57 
+    для работы с программой.
58 
+    </p>
59 
+
60 
+    <p>
61 
+    Прежде всего настраивается браузер. Загрузите <a
62 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> с Вашего
63 
+    репозитория. Polipo - кеширующий прокси-сервер, который имеет широкие
64 
+    возможности по туннелированию HTTP-траффика, поэтому он является подходящим
65 
+    для использования с Tor. Убедитесь, что версия загружаемого Polipo не
66 
+    меньше, чем 1.0.4, так как более ранние версии не поддерживают
67 
+    туннелирование в SOCKS, что необходимо для использования Polipo с Tor. Вам
68 
+    потребуется удалить Privoxy (например, apt-get remove privoxy or yum remove
69 
+    privoxy) для предотвращения  несовместимостей программ.
70 
+    </p>
71 
+
72 
+    <p>Установив Polipo (из пакета или из исходных кодов), <b>Вы должны настроить
73 
+    Polipo на работу с Tor</b>. Скачайте <a
74 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/polipo.conf">настройки
75 
+    Polipo для Tor</a> и перезапишите им конфигурационный файл Polipo (например,
76 
+    /etc/polipo/config or ~/.polipo).  Перезапустите Polipo для применения
77 
+    настроек. Например:<br /> <tt>/etc/init.d/polipo restart</tt>
78 
+    </p>
79 
+
80 
+    <p>Если Вы хотите, Вы можете использовать Privoxy с <a
81 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">данными
82 
+    настройками</a>. Так как оба прокси-сервера (Privoxy и Polipo) используют
83 
+    порт 8118, не стоит их использовать одновременно.</p>
84 
+
85 
+    <hr /> <a id="using"></a>
86 
+    <h2><a class="anchor" href="#using">Шаг 3: настройте Ваши приложения на работу с
87 
+    Tor</a></h2>
88 
+    <br />
89 
+
90 
+    <p>После установки Tor и Polipo, Вам потребуется настроить ваши приложения для
91 
+    работы с ними. Прежде всего следует настроить браузер.</p>
92 
+
93 
+    <p>При работе с Tor рекомендуется использовать браузер Firefox с дополнением
94 
+    Torbutton для обеспечения наивысшей безопасности. Просто установите <a
95 
+    href="https://addons.mozilla.org/firefox/2275/">дополнение Torbutton</a>,
96 
+    перезагрузите Firefox, и браузер будет готов к работе:
97 
+    </p>
98 
+
99 
+    <img alt="Torbutton plugin for Firefox"
100 
+    src="../img/screenshot-torbutton.png" border="1"> <br />
101 
+
102 
+    <p>
103 
+    Если Вы собираетесь использовать Firefox на компьютере без Tor, ознакомьтесь
104 
+    с <a
105 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">частыми
106 
+    вопросами по запуску Tor на другом компьютере</a>.
107 
+    </p>
108 
+
109 
+    <p>Чтобы направить через сеть Tor траффик приложений, поддерживающих настройку
110 
+    HTTP-прокси, укажите настройки Polipo (по умолчанию localhost порт
111 
+    8118). Для использования SOCKS5 (для быстрых сообщений, клиентов Jabber, IRC
112 
+    итд), Вы можете настроить приложение непосредственно на Tor (по умолчанию
113 
+    localhost порт 9050), но ознакомьтесь с <a
114 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">частыми
115 
+    вопросами</a> по поводу опасностей данного способа. Для приложений без
116 
+    поддержки настройки прокси-серверов протоколов SOCKS/HTTP, Вы можете
117 
+    воспользоваться приложениями <a
118 
+    href="http://tsocks.sourceforge.net/">tsocks</a> или <a
119 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>.
120 
+    </p>
121 
+
122 
+    <p>Дополнительную информацию по настройке различных приложений для работы с
123 
+    Tor, ознакомьтесь с  <a
124 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">данным
125 
+    руководством</a>.
126 
+    </p>
127 
+
128 
+    <hr /> <a id="verify"></a>
129 
+    <h2><a class="anchor" href="#verify">Шаг 4: проверка на корректность работы</a></h2>
130 
+    <br />
131 
+
132 
+    <p>
133 
+    <!--PO4ASHARPBEGIN<a href="http://ipchicken.com/">
134 
+    this site</a>PO4ASHARPEND-->
135 
+    #to see what IP address it thinks you're using.
136 
+    Теперь вам следует попробовать запустить браузер с использованием Tor и
137 
+    убедиться, что Ваш IP-адрес скрыт от получателя. Зайдите на страницу  <a
138 
+    href="https://check.torproject.org/">проверки Tor</a> и посмотрите, работает
139 
+    Tor или нет.  (если сайт не работает, посмотрите <a
140 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">частые
141 
+    вопросы</a> по дополнительным способам проверки Tor.)
142 
+    </p>
143 
+
144 
+    <p>Если у Вас стоит брандмауэр, который ограничивает возможность для компьютера
145 
+    подключиться к самому себе (например, средства наподобие SELinux на Fedora
146 
+    Core 4), проверьте, разрешено ли приложениям подключаться к Polipo
147 
+    (localhost, порт 8118) и Tor (localhost, порт 9050). Если Ваш брандмауэр
148 
+    ограничивает исходящие соединения, разрешите Tor подключаться хотя бы к
149 
+    TCP-портам 80 и 443, и ознакомьтесь с <a
150 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">частыми
151 
+    вопросами</a>. Если Ваши настройки SELinux нарушают работу tor или privoxy,
152 
+    создайте файл с именем booleans.local в каталоге /etc/selinux/targeted.
153 
+    Откройте файл в текстовом редакторе и добавьте строчку
154 
+    "allow_ypbind=1". Перезагрузите машину для применения изменений.
155 
+    </p>
156 
+
157 
+    <p>Если проблемы не исчезли, ознакомьтесь с <a
158 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">частыми
159 
+    вопросами</a>.</p>
160 
+
161 
+    <hr /> <a id="server"></a> <a id="relay"></a>
162 
+    <h2><a class="anchor" href="#relay">Шаг 5: настройка узла</a></h2>
163 
+    <br />
164 
+
165 
+    <p>Сеть Tor основана на добровольцах, которые предоставляют траффик
166 
+    пользователям сети. Чем больше узлов, тем быстрее сеть. Если у Вас есть хотя
167 
+    бы 20Кб/с в обе стороны, пожалуйста, помогите сети Tor - запустите
168 
+    узел. Программа предоставляет достаточно функций, которые делают настройку
169 
+    узла Tor лёгкой и удобной для Вас, в том числе ограничение скорости канала,
170 
+    поддержка динамических IP-адресов и политики выхода, которые могут
171 
+    предотвратить жалобы в Ваш адрес.</p>
172 
+
173 
+    <p>Множество узлов в разных точках Интернета даёт пользователям Tor
174 
+    безопасность и конфиденциальность.<a
175 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Вы
176 
+    можете повысить уровень безопасности</a>, так как при наличии узла удалённые
177 
+    серверы не смогут отличить Ваш запрос от перенаправленного с узла.</p>
178 
+
179 
+    <p>Подробности в руководстве по  <a href="<page docs/tor-doc-relay>">настройке
180 
+    узла</a>.</p>
181 
+
182 
+    <hr />
183 
+
184 
+    <p>Если у Вас есть предложения по улучшению этого документа, пожалуйста, <a
185 
+    href="<page about/contact>">ознакомьте нас с ними</a>. Спасибо!</p>
186 
+  </div>
187 
+  <!-- END MAINCOL -->
188 
+  <div id = "sidecol">
189 
+#include "side.wmi"
190 
+#include "info.wmi"
191 
+  </div>
192 
+  <!-- END SIDECOL -->
193 
+</div>
194 
+<!-- END CONTENT -->
195 
+#include <foot.wmi>
docs/ru/tor-doc-web.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,60 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Configuring your browser to use Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-web>">Configure Your Browser</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Настройка браузера для использования <a href="<page index>">Tor</a></h1>
14 
+    <br />
15 
+
16 
+    <p>Если вы используете Firefox (рекомендуется), Вам не потребуется это
17 
+    руководство.  Просто установите <a
18 
+    href="https://addons.mozilla.org/firefox/2275/">дополнение Torbutton</a>,
19 
+    перезапустите браузер, и можете приступать к работе:
20 
+    </p>
21 
+
22 
+    <img alt="Плагин Torbutton для Firefox"
23 
+    src="../img/screenshot-torbutton.png" border="1"/> <br />
24 
+
25 
+    <p>В другом случае Вам потребуется вручную задать настройки прокси-сервера в
26 
+    Вашем браузере.  <br/>Для Mozilla и Firefox на Windows, это Tools - Options
27 
+    - General - Connection Settings.  <br/>Для Firefox на OS X, это Firefox -
28 
+    Preferences - General - Connection Settings.  <br/>Для Firefox на Linux, это
29 
+    Edit - Preferences - Advanced - Proxies.  <br/>Для Opera это Tools -
30 
+    Preferences(Advanced) - Network - Proxy servers.  <br/>Браузер IE не
31 
+    рекомендуется для конфиденциальной работы в Интернете, но для сторонников
32 
+    менее-чем-реальной анонимности: Для IE, это Tools - Internet Options -
33 
+    Connections - LAN Settings - Check Proxy Server - Advanced.</p>
34 
+
35 
+    <img alt="Настройки прокси в Firefox"
36 
+    src="../img/screenshot-win32-firefox-proxies.jpg" />
37 
+
38 
+    <p>
39 
+    Вы должны указать "localhost" и "8118" чтобы перенаправлять четыре указанных
40 
+    протокола на Privoxy, как показано на рисунке. (Даже учитывая что Privoxy не
41 
+    поддерживает FTP и Gopher, <a
42 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FtpProxy">вы
43 
+    должны указать их в любом случае</a>.) Также надо заполнить поле socks в
44 
+    настройках прокси чтобы перенаправлять прямо в Tor ("localhost", "9050", и
45 
+    socks5)  остальные протоколы, кроме первых четырёх. Потом жмите "OK".</p>
46 
+
47 
+    <hr />
48 
+
49 
+    <p>Если у вас есть предложения по улучшению этого документа, пожалуйста <a
50 
+    href="<page about/contact>">присылайте их нам</a>. Спасибо!</p>
51 
+  </div>
52 
+  <!-- END MAINCOL -->
53 
+  <div id = "sidecol">
54 
+#include "side.wmi"
55 
+#include "info.wmi"
56 
+  </div>
57 
+  <!-- END SIDECOL -->
58 
+</div>
59 
+<!-- END CONTENT -->
60 
+#include <foot.wmi>
docs/ru/tor-doc-win32.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,8 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 13195
3 
+# Status: obsolete
4 
+# Last-Translator: ygrekheretix/gmail/com
5 
+
6 
+#include "head.wmi" TITLE="Перенаправление" REDIRECT="docs/tor-doc-windows" CHARSET="UTF-8"
7 
+
8 
+#include <foot.wmi>
docs/ru/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,199 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Работа с клиентом <a href="<page index>">Tor</a> в операционных системах
14 
+    Microsoft Windows</h1>
15 
+    <br />
16 
+
17 
+    <p>
18 
+    <b>Обратите внимание на то, что в этом руководстве представлены инструкции
19 
+    по установке клиента Tor в операционных системах Microsoft Windows (2000,
20 
+    XP, Vista, 7 и на серверных системах).  Если вы хотите создать узел и, таким
21 
+    образом, поддержать рост сети (пожалуйста, сделайте это), прочтите
22 
+    руководство <a href="<page docs/tor-doc-relay>">Настройка узла</a>.</b>
23 
+    </p>
24 
+
25 
+    <p>Организация Freedom House (Дом Свободы) создала видео ролик, рассказывающий
26 
+    о том, как установить Tor. Вы можете просмотреть его здесь: <a
27 
+    href="http://tinyvid.tv/show/3lejztnthk2tm">TinyVid: Установка Tor под ОС
28 
+    Windows (на английском языке)</a>. Вам известно о наличии более наглядного
29 
+    ролика или о переведенной на ваш язык версии? Сообщите нам!</p>
30 
+
31 
+    <div class="center">
32 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor.ogv" autobuffer="true" controls="controls"></video></p>
33 
+    </div>
34 
+
35 
+    <hr /> <a id="installing"></a>
36 
+    <h2><a class="anchor" href="#installing">Шаг первый: Загрузка и установка
37 
+    Tor</a></h2>
38 
+    <br />
39 
+
40 
+    <p>
41 
+    Сборки Tor для Microsoft Windows содержат <a href="<page index>">Tor</a>, <a
42 
+    href="<page projects/vidalia>">Vidalia</a> (графический интерфейс для Tor), <a
43 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton</a> (плагин для
44 
+    браузера Mozilla Firefox), и <a
45 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>
46 
+    (веб-прокси), собранные в один пакет и по умолчанию настроенные для
47 
+    совместной работы.  Скачайте либо <a
48 
+    href="../<package-win32-bundle-stable>">стабильную</a> или <a
49 
+    href="../<package-win32-bundle-alpha>">экспериментальную</a> версию пакета
50 
+    для Windows, или ознакомьтесь с характеристиками на <a href="<page
51 
+    download/download>">странице загрузок</a>.
52 
+    </p>
53 
+
54 
+    <img alt="tor installer splash page"
55 
+    src="../img/screenshot-win32-installer-splash.png" />
56 
+
57 
+    <p>Если вы ранее уже установили Tor, Vidalia, или Polipo, вы можете отказаться
58 
+    от установки любого из этих компонентов, как показано на рисунке ниже.
59 
+    </p>
60 
+
61 
+    <img alt="select components to install"
62 
+    src="../img/screenshot-win32-installer-components.png" />
63 
+
64 
+    <p>После окончания процесса установки, все выбранные вами компоненты
65 
+    автоматически будут запущены.
66 
+    </p>
67 
+
68 
+    <p>Программа Tor устанавливается в качестве клиентской программы по
69 
+    умолчанию. Она использует встроенный конфигурационный файл, и большинству
70 
+    пользователей не придется изменять какие-либо настройки. Сейчас программа
71 
+    Tor установлена.
72 
+    </p>
73 
+
74 
+    <hr /> <a id="using"></a>
75 
+    <h2><a class="anchor" href="#using">Шаг второй: Настройка ваших приложений на
76 
+    использование Tor</a></h2>
77 
+    <br />
78 
+
79 
+    <p>После установки Tor и Polipo вам необходимо настроить ваши приложения на
80 
+    работу через них. Первым делом нужно настроить ваш браузер (программа для
81 
+    просмотра веб страниц).</p>
82 
+
83 
+    <p>Вам следует использовать Tor с браузером Firefox и дополнением Torbutton для
84 
+    обеспечения наилучшей безопасности. Пакет установит для вас <a
85 
+    href="https://addons.mozilla.org/firefox/2275/">плагин
86 
+    Torbutton</a>. Перезапустите ваш браузер Firefox, и все будет настроено:
87 
+    </p>
88 
+
89 
+    <img alt="Torbutton plugin for Firefox"
90 
+    src="../img/screenshot-torbutton.png" border="1"/> <br />
91 
+
92 
+    <p>
93 
+    Если вы планируете использовать Firefox не на том компьютере, куда
94 
+    установлен Tor, ознакомьтесь с <a
95 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">частыми
96 
+    вопросами по использованию Tor на другом компьютере (FAQ for running Tor on
97 
+    a different computer)</a>.
98 
+    </p>
99 
+
100 
+    <p>Для "Торификации" других приложений, которые поддерживают HTTP прокси,
101 
+    просто укажите им на Polipo (который расположен здесь: localhost порт
102 
+    8118). Чтобы использовать SOCKS напрямую (для обмена мгновенными
103 
+    сообщениями, Jabber, IRC, и т.д.), вы можете настроить свое приложение на
104 
+    Tor (localhost порт 9050), но прежде ознакомьтесь с содержимым <a
105 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">частых
106 
+    вопросов</a>, чтобы узнать почему это может быть опасно. Для настройки
107 
+    приложений, не поддерживающих ни SOCKS не HTTP, обратите внимание на
108 
+    приложения SocksCap и <a href="http://www.freecap.ru/">FreeCap</a>.
109 
+    (FreeCap - это бесплатное ПО; SocksCap - платное).</p>
110 
+
111 
+    <p>Чтобы получить информацию о том, как "Торифицировать" другие приложения,
112 
+    ознакомьтесь с <a
113 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Инструкцией
114 
+    по "Торификации"</a>.
115 
+    </p>
116 
+
117 
+    <hr /> <a id="verify"></a>
118 
+    <h2><a class="anchor" href="#verify">Шаг третий: Убедитесь в том, что все
119 
+    работает корректно</a></h2>
120 
+    <br />
121 
+
122 
+    <p>
123 
+    Убедитесь, что приложение Vidalia запущено. Программа Vidalia использует
124 
+    следующие индикаторы: маленькая зеленая луковица означает, что Tor работает
125 
+    корректно; а черная перечеркнутая луковица означает, что Tor не работает. Вы
126 
+    можете запустить или остановить работу Tor нажав правой кнопкой мыши по
127 
+    иконке программы Vidalia, расположенной в системном трее и выбрав "Старт"
128 
+    или "Стоп" из меню, как показано ниже:
129 
+    </p>
130 
+
131 
+    <img alt="Vidalia Tray Icon" src="../img/screenshot-win32-vidalia.png"/>
132 
+
133 
+    <p>
134 
+    Далее вам необходимо протестировать работу вашего браузера с Tor и
135 
+    убедиться, что ваш IP-адрес был скрыт. Откройте страницу <a
136 
+    href="https://check.torproject.org/">проверки Tor</a> и посмотрите,
137 
+    подтверждается ли сайтом использование сервиса Tor. (Если сайт не работает,
138 
+    обратитесь к <a
139 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">частым
140 
+    вопросам</a>, чтобы получить информацию о других методах тестирования работы
141 
+    Tor.)
142 
+    </p>
143 
+
144 
+    <p>Если у вас установлен персональный брандмауэр, который ограничивает
145 
+    возможность подключения вашего компьютера  к самому себе, убедитесь что вы
146 
+    разрешили подключения локальных приложений к локальным портам 8118 и
147 
+    9050. Если ваш брандмауэр блокирует исходящие подключения, измените
148 
+    настройки так, чтобы он мог подключаться хотя бы к TCP портам 80 и 443, а
149 
+    затем ознакомьтесь с <a
150 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">частыми
151 
+    вопросами</a>.
152 
+    </p>
153 
+
154 
+    <p>Если ничего из вышеперечисленного не помогло, обратитесь к <a
155 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">частым
156 
+    вопросам</a> для получения дополнительной информации.</p>
157 
+
158 
+    <p>
159 
+    Когда все заработало, узнайте больше о том <a href="<page
160 
+    download/download>#Warning">что даёт и не даёт сервис Tor </a>.
161 
+    </p>
162 
+
163 
+    <hr /> <a id="server"></a> <a id="relay"></a>
164 
+    <h2><a class="anchor" href="#relay">Шаг четвертый: Настройте узел Tor</a></h2>
165 
+    <br />
166 
+
167 
+    <p>Сеть Tor полагается на добровольцев, предоставляющих пропускную способность
168 
+    своих компьютеров. Чем больше людей создают узлы, тем быстрей будет работать
169 
+    сеть Tor. Если у вас есть как минимум 20Кб/сек. в обоих направлениях,
170 
+    пожалуйста поддержите Tor, настроив узел Tor. Мы создали множество
171 
+    возможностей, делающих создание узлов Tor простым и удобным, включая
172 
+    ограничение предоставляемой пропускной способности, правила вывода (с тем
173 
+    чтобы вы могли ограничить вашу незащищенность к возможным жалобам), и
174 
+    поддержку динамических IP-адресов.</p>
175 
+
176 
+    <p>Наличие узлов в разных уголках сети Интернет - это то, что обеспечивает
177 
+    безопасность пользователей Tor. <a
178 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">Создавая
179 
+    узел, вы можете улучшить свою собственную анонимность</a>, так как удаленные
180 
+    сайты не могут установить происхождение запроса, ведь он может исходить как
181 
+    от вас, так и от других пользователей сети Tor, использующих ваш узел.</p>
182 
+
183 
+    <p>Больше информации на эту тему можно получить из руководства <a href="<page
184 
+    docs/tor-doc-relay>">Настройка узла</a>.</p>
185 
+
186 
+    <hr />
187 
+
188 
+    <p>Если у вас есть предложения по улучшению этого документа, пожалуйста <a
189 
+    href="<page about/contact>">отправьте их нам</a>. Спасибо!</p>
190 
+  </div>
191 
+  <!-- END MAINCOL -->
192 
+  <div id = "sidecol">
193 
+#include "side.wmi"
194 
+#include "info.wmi"
195 
+  </div>
196 
+  <!-- END SIDECOL -->
197 
+</div>
198 
+<!-- END CONTENT -->
199 
+#include <foot.wmi>
docs/ru/tor-hidden-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,277 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22314 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Настройка скрытых сервисов <a href="<page index>">Tor</a></h1>
14 
+    <hr />
15 
+
16 
+    <p>Tor позволяет клиентам и узлам предоставлять скрытые сервисы. Таким образом
17 
+    Вы можете предоставлять доступ к веб-серверам, SSH-серверам, итд., без
18 
+    разглашения своего IP-адреса пользователям. Также, так как Вы не используете
19 
+    какие-либо внешние адреса, Вы можете запустить скрытый сервис за
20 
+    брандмауэром (не имея внешнего IP-адреса).
21 
+    </p>
22 
+
23 
+    <p>If you have Tor installed, you can see hidden services in action by visiting
24 
+    <a href="http://duskgytldkxiuqc6.onion/">our example hidden service</a>.
25 
+    </p>
26 
+
27 
+    <p>Данное руководство описывает порядок настройки вашего собственного скрытого
28 
+    сервиса. Технические детали работы протокола скрытых сервисов описаны на
29 
+    странице <a href="<page docs/hidden-services>">описания протокола скрытых
30 
+    сервисов</a>.
31 
+    </p>
32 
+
33 
+    <hr />
34 
+    <a id="zero"></a>
35 
+    <h2><a class="anchor" href="#zero">Прежде всего: запуск Tor</a></h2>
36 
+    <br />
37 
+
38 
+    <p>Перед началом убедитесь в следующем:</p>
39 
+    <ol>
40 
+    <li>Что Tor запущен,</li>
41 
+    <li>Что Вы на самом деле настроили его корректно,</li>
42 
+    </ol>
43 
+
44 
+
45 
+    <p>Пользователи ОС Windows должны воспользоваться <a href="<page
46 
+    docs/tor-doc-windows>">руководством для пользователей Windows</a>,
47 
+    пользователи OS X должны воспользоваться <a href="<page
48 
+    docs/tor-doc-osx>">руководством для OS X</a>, и пользователи Linux/BSD/Unix
49 
+    должны воспользоваться <a href="<page docs/tor-doc-unix>">руководством для
50 
+    пользователей Unix</a>.
51 
+    </p>
52 
+
53 
+    <p>Когда Вы уже установили и настроили Tor, вы сможете ознакомиться с
54 
+    действующими скрытыми сервисами, доступными по адресам: <a
55 
+    href="http://duskgytldkxiuqc6.onion/">пример скрытого сервиса</a> или <a
56 
+    href="http://gaddbiwdftapglkq.onion/">скрытый сервер Wikileaks</a>. Загрузка
57 
+    занимает обычно 10-60 секунд (или решение о недоступности сервера). Если
58 
+    браузер немедленно выдаёт ошибку "www.duskgytldkxiuqc6.onion could not be
59 
+    found, please check the name and try again", то значит, что у Вас
60 
+    некорректно настроен Tor, ознакомьтесь с <a
61 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">частыми
62 
+    вопросами</a> - возможно, это поможет.
63 
+    </p>
64 
+
65 
+    <hr />
66 
+    <a id="one"></a>
67 
+    <h2><a class="anchor" href="#one">Шаг 1: установка локального веб-сервера</a></h2>
68 
+    <br />
69 
+
70 
+    <p>Прежде всего Вам следует установить локальный веб-сервер. Это может
71 
+    оказаться сложной задачей, поэтому в данном руководстве будут рассмотрены
72 
+    лишь базовые моменты. Если Вы запутались или хотите большего, попросите
73 
+    кого-нибудь о помощи. Рекомендуется установить отдельный сервер для скрытого
74 
+    сервиса, даже если у Вас уже есть один сервер, используемый для настоящего
75 
+    сайта.
76 
+    </p>
77 
+
78 
+    <p>Если Вы работаете из-под UNIX или OS X и работа с командной строкой не
79 
+    доставляет Вам неудобств, лучшим началом будет установка <a
80 
+    href="http://www.acme.com/software/thttpd/">thttpd</a>. Просто скачайте
81 
+    самый свежий архив, распакуйте его (будет создана папка с файлами), и
82 
+    запустите <kbd>./configure &amp;&amp; make</kbd>. Затем <kbd>mkdir hidserv;
83 
+    cd hidserv</kbd>, и выполните <kbd>../thttpd -p 5222 -h
84 
+    localhost</kbd>. Сервер вернёт ввод в командную строку, будет запущен сервер
85 
+    на порту 5222. Вы можете поместить размещаемые файлы в каталог hidserv.
86 
+    </p>
87 
+
88 
+    <p>Если Вы под Windows, Вы можете ознакомиться с <a
89 
+    href="http://savant.sourceforge.net/">Savant</a> или <a
90 
+    href="http://httpd.apache.org/">Apache</a>, проверьте, что сервер
91 
+    прослушивает только localhost. Также Вам потребуется узнать, какой порт
92 
+    прослушиает сервер - это Вам понадобится в дальнейшем.
93 
+    </p>
94 
+
95 
+    <p>(причина для прослушивания только localhost - убедиться, что сервер не
96 
+    является общедоступным. Если пользователи смогут получить доступ к серверу
97 
+    напрямую, они смогут убедиться, что именно этот компьютер предоставляет
98 
+    скрытый сервис.
99 
+    </p>
100 
+
101 
+    <p>После запуска сервера убедитесь, что он работает корректно: откройте адрес
102 
+    <a href="http://localhost:5222/">http://localhost:5222/</a> в Вашем
103 
+    браузере, где 5222 - порт, на который настроен сервер. После этого
104 
+    попробуйте запросить главную страницу, убедитесь, что она отображается
105 
+    корректно.
106 
+    </p>
107 
+
108 
+    <hr />
109 
+    <a id="two"></a>
110 
+    <h2><a class="anchor" href="#two">Шаг 2: настройка скрытого сервиса</a></h2>
111 
+    <br />
112 
+
113 
+    <p>Далее Вам потребуется настроить Ваш скрытый сервис на ваш локальный
114 
+    веб-сервер.
115 
+    </p>
116 
+
117 
+    <p>Откройте файл torrc в текстовом редакторе (см. <a
118 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">частые
119 
+    вопросы о torrc</a>). Перейдите на среднюю секцию и найдите строчку</p>
120 
+
121 
+    <pre>
122 
+    \############### This section is just for location-hidden services ###
123 
+    </pre>
124 
+
125 
+    <p>
126 
+    Эта секция состоит из набора сгруппированных строк, каждая группа
127 
+    соответствует одному скрытому сервису. На данный момент они все
128 
+    закомментированы (строки, начинающиеся с #), соответственно, скрытые сервисы
129 
+    неактивны. Каждая группа строк содержит строку <var>HiddenServiceDir</var> и
130 
+    одну (или более) строку <var>HiddenServicePort</var>:</p>
131 
+    <ul>
132 
+    <li><var>HiddenServiceDir</var> is a directory where Tor will store information
133 
+    about that hidden service.  In particular, Tor will create a file here named
134 
+    <var>hostname</var> which will tell you the onion URL.  You don't need to
135 
+    add any files to this directory. Make sure this is not the same directory as
136 
+    the hidserv directory you created when setting up thttpd, as your
137 
+    HiddenServiceDir contains secret information!</li>
138 
+    <li><var>HiddenServicePort</var> отвечает за назначение виртуального порта
139 
+    (т.е. какой порт будет доступен для пользователей) IP-адресу и порту для
140 
+    перенаправления соединений к запрошенному виртуальному порту.</li>
141 
+    </ul>
142 
+
143 
+    <p>Добавьте следующие строки в torrc:
144 
+    </p>
145 
+
146 
+    <pre>
147 
+    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
148 
+    HiddenServicePort 80 127.0.0.1:5222
149 
+    </pre>
150 
+
151 
+    <p>You're going to want to change the <var>HiddenServiceDir</var> line, so it
152 
+    points to an actual directory that is readable/writeable by the user that
153 
+    will be running Tor. The above line should work if you're using the OS X Tor
154 
+    package. On Unix, try "/home/username/hidden_service/" and fill in your own
155 
+    username in place of "username". On Windows you might pick:</p>
156 
+    <pre>
157 
+    HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\\
158 
+    HiddenServicePort 80 127.0.0.1:5222
159 
+    </pre>
160 
+
161 
+    <p>Сохраните torrc и перезапустите Tor.
162 
+    </p>
163 
+
164 
+    <p>Если Tor запустится - отлично. Если же нет - значит, где-то была ошибка. В
165 
+    первую очередь просмотрите отчёты в лог-файлах. Там должны быть какие-то
166 
+    предупреждения или сообщения об ошибках. Они должны Вам подсказать, в чём
167 
+    проблема. Обычно это опечатки в torrc или некорректно настроенные разрешения
168 
+    (см. <a
169 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">частые
170 
+    вопросы об отчётах</a>, если Вы не знаете, где включить протоколирование
171 
+    ошибок или найти отчёты).
172 
+    </p>
173 
+
174 
+    <p>Tor при запуске автоматически (при необходимости) создаст каталог
175 
+    <var>HiddenServiceDir</var> и создаст там два файла.</p>
176 
+
177 
+    <dl>
178 
+    <dt><var>private_key</var></dt>
179 
+    <dd>Сначала Tor создаст пару ключей (общий и личный) для вашего скрытого
180 
+    сервиса. Ключ записывается в файл с названием "private_key". Не давайте этот
181 
+    ключ никому и не публикуйте его нигде, иначе Вас смогут опознать и найти.</dd>
182 
+    <dt><var>имя_узла</var></dt>
183 
+    <dd>Следующий файл, который создаёт Tor, называется "hostname". Он содержит
184 
+    отпечаток Вашего общего ключа, и имя будет у файла похоже на нечто вроде
185 
+    <tt>duskgytldkxiuqc6.onion</tt>. Это общедоступное имя для Вашего узла, Вы
186 
+    можете его сообщать другим, публиковать на вебсайтах, печатать на визитках
187 
+    итд.</dd>
188 
+    </dl>
189 
+
190 
+    <p>Если Tor запускается не от Вашего имени, например, на OS X, Debian или Red
191 
+    hat, Вам возможно потребуются привилегии суперпользователя root для
192 
+    просмотра этих файлов.</p>
193 
+
194 
+    <p>После перезапуска Tor сохраняет точки доступа в сеть и создаёт
195 
+    <em>дескриптор скрытого сервиса</em>. Это подписанный список точек доступа,
196 
+    объединённый с общим ключом Вашего сервиса. Tor анонимно публикует
197 
+    дескриптор на сервера каталогов, и другие пользователи анонимно получают Ваш
198 
+    дескриптор при попытке зайти на Ваш сервис.
199 
+    </p>
200 
+
201 
+    <p>Попробуйте: вставьте содержимое файла hostname в адресную строку Вашего
202 
+    браузера. Если сервис настроен корректно, Вы увидите html-страницу,
203 
+    настроенную изначально. Если же Вы не увидите html-страницу, просмотрите
204 
+    файлы отчётов, информация в них поможет Вам установить причину некорректной
205 
+    работы сервиса.
206 
+    </p>
207 
+
208 
+    <hr />
209 
+    <a id="three"></a>
210 
+    <h2><a class="anchor" href="#three">Шаг 3: полезные советы</a></h2>
211 
+    <br />
212 
+
213 
+    <p>Если Вы собираетесь поддерживать скрытый сервис в течение долгого времени,
214 
+    возможно, Вам стоило бы где-нибудь сохранить резервную копию файла
215 
+    <var>private_key</var>.
216 
+    </p>
217 
+
218 
+    <p>Установка сервера Apache не была рекомендована в связи с тем, что: а) во
219 
+    многих случая пользователи уже используют этот сервер как публичный, б)
220 
+    сервер очень объёмный и в нём есть немало способов получить IP-адрес сервера
221 
+    или другую конфиденциальную информацию, например, на страницах ошибок
222 
+    наподобие генерируемой ошибки 404. Несмотря на это, пользователям с высокими
223 
+    требованиями к функциональности веб-серер Apache может быть правильным
224 
+    решением. Проект был бы благодарен за руководство по безопасности
225 
+    использования сервера Apache в качестве сервера для скрытого
226 
+    сервиса. Возможно, такие же проблемы есть у сервера Savant.
227 
+    </p>
228 
+
229 
+    <p>Если Вы хотите направить несколько виртуальных портов на один скрытый
230 
+    сервис, просто добавьте строку <var>HiddenServicePort</var> на каждый
231 
+    виртуальный порт. Если же Вы хотите поддерживать несколько скрытых сервисов
232 
+    на одном клиенте Tor, просто добавьте ещё одну строку
233 
+    <var>HiddenServiceDir</var> на каждый сервис. Все строки
234 
+    <var>HiddenServicePort</var> соответствуют строке
235 
+    <var>HiddenServiceDir</var> выше, группа оканчивается на новой строке
236 
+    <var>HiddenServiceDir</var>:
237 
+    </p>
238 
+
239 
+    <pre>
240 
+    HiddenServiceDir /usr/local/etc/tor/hidden_service/
241 
+    HiddenServicePort 80 127.0.0.1:8080
242 
+
243 
+    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
244 
+    HiddenServicePort 6667 127.0.0.1:6667
245 
+    HiddenServicePort 22 127.0.0.1:22
246 
+    </pre>
247 
+
248 
+    <p>Несколько моментов, о которых Вам стоит помнить в интересах Вашей
249 
+    конфиденциальности:
250 
+    </p>
251 
+    <ul>
252 
+    <li>Как было отмечено выше, будьте осторожны с возможностями сервера по
253 
+    предоставлению информации о Вас, Вашем компьютере или о Вашем
254 
+    местонахождении. Например, пользователи могут с некой вероятностью
255 
+    установить, какое ПО используется в качестве веб-сервера (Apache, thttpd,
256 
+    итд) и сделать какие-то выводы о Вашей операционной системе.</li>
257 
+    <li>Если Ваш компьютер функционирует не круглосуточно, скрытый сервис также
258 
+    функционировать не будет без компьютера. На этой информации можно также
259 
+    сделать некие выводы, например, предположить часовой пояс.</li>
260 
+
261 
+    <!-- increased risks over time -->
262 
+    </ul>
263 
+
264 
+    <hr />
265 
+
266 
+    <p>Если у Вас есть предложения по улучшению этого документа, пожалуйста, <a
267 
+    href="<page about/contact>">присылайте их нам</a>. Спасибо!</p>
268 
+  </div>
269 
+  <!-- END MAINCOL -->
270 
+  <div id = "sidecol">
271 
+#include "side.wmi"
272 
+#include "info.wmi"
273 
+  </div>
274 
+  <!-- END SIDECOL -->
275 
+</div>
276 
+<!-- END CONTENT -->
277 
+#include <foot.wmi>
docs/zh-cn/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,5 @@
1 
+include $(WMLBASE)/Makefile.common
2 
+TORSVNSTABLE = $(WMLBASE)/tor-stable
3 
+TORGIT = $(WMLBASE)/tor/.git
4 
+STABLETAG = tor-0.2.1.26
5 
+DEVTAG = tor-0.2.2.13-alpha
docs/zh-cn/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,77 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+# this structure defines the side nav bar for the /about pages
6 
+# and is the input for include/side.wmi
7 
+
8 
+# fields:
9 
+#
10 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
11 
+# that links will point to the current language if supported, and alternately
12 
+# the english version
13 
+#
14 
+# txt - the link text to be displayed. Different translations will
15 
+# need to supply alternate txt
16 
+
17 
+<:
18 
+  my $sidenav;
19 
+  $sidenav = [
20 
+      {'url'  => 'docs/documentation',
21 
+       'txt'  => 'Documentation Overview',
22 
+      },
23 
+      {
24 
+       'url'  => 'docs/installguide',
25 
+       'txt'  => 'Installation Guides',
26 
+       'subelements' => [
27 
+          {'url'  => 'docs/tor-doc-windows',
28 
+           'txt'  => 'Installing on Windows',
29 
+          },
30 
+          {'url'  => 'docs/tor-doc-unix',
31 
+           'txt'  => 'Installing on Linux/BSD/Unix',
32 
+          },
33 
+          {'url'  => 'docs/tor-doc-osx',
34 
+           'txt'  => 'Installing on Mac OS X',
35 
+          },
36 
+          {'url'  => 'docs/tor-doc-web',
37 
+           'txt'  => 'Configuring your browser to use Tor',
38 
+          }],
39 
+      },
40 
+      {'url'  => 'docs/manual',
41 
+       'txt'  => 'Manuals',
42 
+       'subelements' => [
43 
+          {'url'  => 'docs/tor-doc-relay',
44 
+           'txt'  => 'Configuring a Relay',
45 
+          },
46 
+          {'url'  => 'docs/tor-hidden-service',
47 
+           'txt'  => 'Configuring a Hidden Service',
48 
+          },
49 
+          {'url'  => 'docs/running-a-mirror',
50 
+           'txt'  => 'Configuring a Mirror',
51 
+          },
52 
+          {'url'  => 'docs/tor-manual',
53 
+           'txt'  => 'Tor Manual',
54 
+          },
55 
+          {'url'  => 'docs/tor-manual-dev',
56 
+           'txt'  => 'Tor Developer Manual',
57 
+          }],
58 
+      },
59 
+      {'url' => 'docs/glossary',
60 
+       'txt' => 'Glossary',
61 
+      },
62 
+      {
63 
+       'url'  => 'http://wiki.torproject.org',
64 
+       'txt'  => 'Tor Wiki',
65 
+      },
66 
+      {'url'  => 'docs/faq',
67 
+       'txt'  => 'FAQ',  #maybe stick this in about instead...
68 
+       'subelements' => [
69 
+          {'url'  => 'docs/faq-abuse',
70 
+           'txt'  => 'Abuse FAQ',
71 
+          },
72 
+          {'url'  => 'docs/trademark-faq',
73 
+           'txt'  => 'Trademark FAQ',
74 
+          }]
75 
+      },
76 
+  ];
77 
+:>
docs/zh-cn/tor-doc-osx.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,185 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22305 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mac OS X Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-osx>">Mac OS X Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- 本翻译不是由 Mac 用户所做，肯定存在不正确的地方，Mac 用户，
14 
+    请帮忙改进此翻译，谢谢！-->
15 
+
16 
+    <h1>在Mac OS X上运行 <a href="<page index>">Tor</a> 客户端</h1>
17 
+    <br />
18 
+
19 
+    <p>
20 
+    <b>请注意一下所述的是在 Mac OS X 上运行 Tor 客户端的指导。如果你希望运行中继，请阅读
21 
+     <a href="<page docs/tor-doc-relay>">配置中继</a> 的指导。</b>
22 
+    </p>
23 
+
24 
+    <hr />
25 
+    <a id="installing"></a>
26 
+    <h2><a class="anchor" href="#installing">步骤一：下载以及安装 Tor</a></h2>
27 
+    <br />
28 
+
29 
+    <p>
30 
+    Macintosh OS X 套件将 <a href="<page index>">Tor</a>,
31 
+    <a href="<page projects/vidalia>">Vidalia</a> (Tor 的一个图形界面),
32 
+    <a href="<page projects/torbutton>">Torbutton</a>,
33 
+    以及<a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> (一种 Web 代理)
34 
+    整合在一起，并且这四个应用程序已经被预先配置好，可以正常工作。
35 
+    下载 OS X 套件的<a href="../<package-osx-bundle-stable>">稳定版本</a>
36 
+    或者<a href="../<package-osx-bundle-alpha>">试验性质</a>版本，或者在
37 
+    <a href="<page download/download>">下载页面</a>中得到更多选择。
38 
+    </p>
39 
+
40 
+    <p>dmg 文件下载结束后，双击将其展开。在 Finder 中定位到打开的 Vidalia 套件。
41 
+    安装套件很简单，把 Vidalia 的洋葱图标拖放到 Applications 文件夹即可。
42 
+    双击 "install torbutton" 脚本还可以额外为 Firefox 安装 Torbutton。
43 
+    Torbutton 可以在 Mozilla Add-ons 站点通过搜索 "torbutton" 找到。</p>
44 
+
45 
+    <p>当安装结束时，你可以通过在你的“应用程序”档案夹中选择 Vidalia 的方式启动它。
46 
+    在 Dock 中一个有红色 X 的灰色洋葱图标意味着Tor现在没有运行。
47 
+    你可以通过在 "Tor" 菜单中选择启动的方式启动 Tor 。
48 
+    </p>
49 
+
50 
+    <p>当 Tor 运行时， Vidalia 的 Dock 图标会变成这样：
51 
+    </p>
52 
+
53 
+    <p><img alt="vidalia running tor"
54 
+    src="../img/screenshot-osx-vidalia.png"
55 
+    border="1"/></p>
56 
+
57 
+    <p>Polipo 是 Tor bundle package 的默认安装项。一旦安装好，他会随你的计算机的启动而
58 
+    自动启动。
59 
+    你不需要因为使用 Tor 而配置 Polipo &mdash; 在安装包内已经包含了一个已经定制好的 Polipo
60 
+    配置文件。
61 
+    </p>
62 
+
63 
+    <hr />
64 
+    <a id="using"></a>
65 
+    <h2><a class="anchor" href="#using">步骤二：配置你的应用程序使用 Tor</a></h2>
66 
+    <br />
67 
+
68 
+    <p>安装结束后，你需要配置你的应用程序使用他们。第一件事情是配置
69 
+    网络浏览。</p>
70 
+
71 
+    <p>为了最大的安全性，你应该在使用 Tor 时使用 Firefox 和 Torbutton。
72 
+    Torbutton 已经为你安装好了。 单击红色的 "Tor Disabled" 控制按钮来配置启动 Tor： </p>
73 
+
74 
+    <p><img alt="Torbutton plugin for Firefox"
75 
+    src="../img/screenshot-torbutton.png"
76 
+    border="1"/></p>
77 
+
78 
+    <p>
79 
+    你如果希望在另一台没有安装 Tor 的计算机上使用 Firefox，请看<a
80 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">在
81 
+    另一台计算机上运行 Tor 的 FAQ 条目</a>.
82 
+    </p>
83 
+
84 
+    <p>如果需要Tor化其他的支持HTTP代理服务器的应用程序，请将HTTP代理服务器指向
85 
+    Polipo (那就是 localhost 端口 8118)。如果向直接使用SOCKS代理(比如既时
86 
+    通信，Jabber, IRC 等等)你可以直接将你的应用程序代理指向 Tor (localhost
87 
+    端口 9050)，但是请看<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">
88 
+    这个FAQ条目</a> &mdash; 这样做可能是危险的。 如果应用程序即不支持SOCKS代理
89 
+    也不支持HTTP代理，请看<a href="http://www.taiyo.co.jp/~gotoh/ssh/connect.html">connect</a>
90 
+    或者<a href="http://www.dest-unreach.org/socat/">socat</a>.</p>
91 
+
92 
+    <p>看看<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">
93 
+    如何 Tor 化</a>以获取更多的关于如何 Tor 化其他应用程序的信息。
94 
+    </p>
95 
+
96 
+    <hr />
97 
+    <a id="verify"></a>
98 
+    <h2><a class="anchor" href="#verify">步骤三：确认它是不是工作</a></h2>
99 
+    <br />
100 
+
101 
+    <p>
102 
+    下一步，你应该通过浏览器试一试你是的IP是不是被匿名化了。点击
103 
+    <a href="https://check.torproject.org/">Tor 检测器</a>
104 
+    看看你是不是在用 Tor。(如果这个站点下线了，看一看 <a
105 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">这个
106 
+    FAQ条目</a>以获取更多的有关如何测试Tor的建议。)
107 
+    </p>
108 
+
109 
+    <p>如果你的个人防火墙限制你的计算机连接到它自己，一定要允许从本地应用程序到本地端口
110 
+    8118 和 9050 的连接。如果你的防火墙阻挡向外的连接，那么至少让它能够连接 TCP 端口 80 和 443，
111 
+    然后阅读<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">此 FAQ 条目</a>。
112 
+    </p>
113 
+
114 
+    <p>如果它还是罢工，那就看看<a
115 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">此 FAQ
116 
+    条目</a>寻找一些线索。
117 
+    </p>
118 
+
119 
+    <p>
120 
+    一旦工作正常，请了解更多 <a href="<page download/download>#Warning">Tor 提供什么，不提供什么</a>。
121 
+    </p>
122 
+
123 
+    <hr />
124 
+    <a id="server"></a>
125 
+    <a id="relay"></a>
126 
+    <h2><a class="anchor" href="#relay">步骤四：配置中继</a></h2>
127 
+    <br />
128 
+
129 
+    <p>Tor 网络依靠志愿者们贡献带宽运行。运行中继的人越多，Tor 网络的速度就越快。
130 
+    如果你的网络连接速度达到至少每秒 20KB，请运行一台中继以帮助 Tor。
131 
+    我们有许多特性使得 Tor 中继的运行简单而方便，包括带宽的速率限制，
132 
+    定制出口策略以避免滥用，以及对于动态 IP 地址的支持。
133 
+    </p>
134 
+
135 
+    <p>在互联网上的许多不同地方运行中继保护了 Tor 用户的安全。<a
136 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">你自身的
137 
+    匿名也能得到更好的保护</a>，因为站点不知道连接究竟来自你的电脑还是为他人传递。
138 
+    </p>
139 
+
140 
+    <p>阅读更详细的<a href="<page docs/tor-doc-relay>">配置中继</a>的指导。
141 
+    </p>
142 
+
143 
+    <hr />
144 
+    <a id="uninstall"></a>
145 
+    <h2><a class="anchor" href="#uninstall">如何卸载 Tor 和 Privoxy</a></h2>
146 
+    <br />
147 
+
148 
+    <p>有两种方法卸载 Tor 套件，使用 Finder 或者命令行/基于终端的卸载工具。
149 
+    如果你希望在 OSX 上卸载 Tor，请参照以下步骤：</p>
150 
+
151 
+    <p>修改你的应用程序代理设置到原始值。如果你只是希望停止使用 Tor，请到此为止。</p>
152 
+
153 
+    <p>如果你希望完全移除Tor并且你的账户有管理员权限，请参照以下步骤：</p>
154 
+
155 
+    <ol>
156 
+    <li>打开 Finder，点击 Applications。</li>
157 
+    <li>将 /Applications/Vidalia 拖至 Trash。</li>
158 
+    <li>从系统中删除 /Library/Torbutton。</li>
159 
+    <li>在你的 home 目录中，转到 Library，删除 Vidalia 目录。</li>
160 
+    </ol>
161 
+
162 
+    <p>现在，Tor、Vidalia 和 Polipo 已从系统中完全删除。</p>
163 
+
164 
+    <p>如果你熟悉命令行或者终端，你也可以手工删除：</p>
165 
+    <ul>
166 
+    <li>/Applications/Vidalia.app/</li>
167 
+    <li>/Library/Torbutton/</li>
168 
+    <li>~/Library/Vidalia</li>
169 
+    <li>~/.tor</li>
170 
+    </ul>
171 
+
172 
+    <hr />
173 
+
174 
+    <p>如果你有其他改进本文档的建议，请<a href="<page about/contact>">把他们发给我们</a>，
175 
+    谢谢！</p>
176 
+  </div>
177 
+  <!-- END MAINCOL -->
178 
+  <div id = "sidecol">
179 
+#include "side.wmi"
180 
+#include "info.wmi"
181 
+  </div>
182 
+  <!-- END SIDECOL -->
183 
+</div>
184 
+<!-- END CONTENT -->
185 
+#include <foot.wmi>
docs/zh-cn/tor-doc-relay.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,258 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22144 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Relay Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-relay>">Configure Tor Relay</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>配置 Tor 中继</h1>
14 
+
15 
+    <!-- BEGIN SIDEBAR -->
16 
+    <div class="sidebar-left">
17 
+    <h3>配置步骤</h3>
18 
+    <ol>
19 
+    <li><a href="<page docs/tor-doc-relay>#install">下载并安装</a></li>
20 
+    <li><a href="<page docs/tor-doc-relay>#setup">配置</a></li>
21 
+    <li><a href="<page docs/tor-doc-relay>#check">检查并确认</a></li>
22 
+    <li><a href="<page docs/tor-doc-relay>#after">最终步骤</a></li>
23 
+    </ol>
24 
+    </div>
25 
+    <!-- END SIDEBAR -->
26 
+
27 
+    <hr />
28 
+
29 
+    <p>Tor 网络依靠志愿者们贡献带宽运行。运行中继的人越多，Tor 网络的速度就越快。
30 
+    如果你的网络连接速度达到至少每秒 20KB，请运行一台中继以帮助 Tor。
31 
+    我们有许多特性使得 Tor 中继的运行简单而方便，包括<a href="<page docs/faq>#RelayFlexible">带宽的速率限制，
32 
+    定制出口策略以避免滥用，以及对于动态 IP 地址的支持。</a></p>
33 
+
34 
+    <p>你能在<a
35 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayOS">几乎
36 
+    所有</a>的操作系统上运行 Tor 中继，但是 Linux、FreeBSD 5.x+、OS X Tiger 或之后、
37 
+    和 Windows Server 2003 或之后效果最佳。
38 
+    </p>
39 
+
40 
+    <hr />
41 
+    <a id="zero"></a>
42 
+    <a id="install"></a>
43 
+    <h2><a class="anchor" href="#install">第一步：下载并安装 Tor</a></h2>
44 
+    <br />
45 
+
46 
+    <p>开始前，你需要确认 Tor 已经正常运行。</p>
47 
+
48 
+    <p>访问<a href="<page download/easy-download>">下载页面</a>，
49 
+    安装符合你所使用操作系统的“安装套件”。
50 
+    </p>
51 
+
52 
+    <p>如果可以的话，你也许还应该将它作为客户端使用一段时间以确认 Tor 确实工作正常。
53 
+    </p>
54 
+
55 
+    <hr />
56 
+    <a id="setup"></a>
57 
+    <h2><a class="anchor" href="#setup">第二步：将它设置成中继</a></h2>
58 
+    <br />
59 
+
60 
+    <ol>
61 
+    <li>检查时间和时区是否正确。可能的话，与公共的<a
62 
+    href="http://en.wikipedia.org/wiki/Network_Time_Protocol">时间服务器</a>同步时间。
63 
+    </li>
64 
+
65 
+    <li><strong>在 Vidalia 图形界面配置 Tor</strong>：
66 
+    <ol>
67 
+    <!-- 一些地方使用了：中文(英文)的形式，方便阅读 -->
68 
+    <!-- 引用了 Vidalia 软件界面文字的部分需参考最新 Vidalia 软件界面 -->
69 
+    <li>
70 
+    	<dt>右键单击在任务栏中的 Vidalia 图标，选择 <tt>控制面板(Control Panel)</tt>。</dt>
71 
+    	<dd><img src="../img/screenshot-win32-vidalia.png"></dd>
72 
+    </li>
73 
+
74 
+    <li>点击<tt>设置中继服务器(Setup Relaying)</tt>。</li>
75 
+
76 
+    <li>
77 
+    	<dt>如果你想成为公共中继（推荐），选择 <tt>Tor 网络中继(Relay Traffic for the Tor network)</tt>。或者如果你想成为 <a href="<page docs/faq>#RelayOrBridge">网桥</a> 帮助所在国家审查网络无法使用 Tor 的用户</dt>，选择 <tt>帮助用户访问 Tor 网络(Help censored users reach the Tor network)</tt> 。
78 
+    <dd><img src="../img/screenshot-win32-configure-relay-1.png"></dd>
79 
+    </li>
80 
+
81 
+    <li>为中继输入一个昵称，为了在出现问题时我们能及时和你联系，还请输入联系方式。</li>
82 
+
83 
+    <li>选择 <tt>Attempt to automatically configure port forwarding(尝试自动配置端口转发)</tt>。
84 
+    点击 <tt>Test(测试)</tt> 按钮检查是否能正常工作。如能正常工作继续往下配置；
85 
+    否则请查看下面第 3 点。
86 
+    <!-- FIXME: 上面的两个GUI短语目前并没有翻译。--></li>
87 
+
88 
+    <li><dt>选择 <tt>带宽限制(Bandwidth Limits)</tt> 标签。选择你想为像你一样的 Tor 用户提供的带宽。</dt>
89 
+    <dd><img src="../img/screenshot-win32-configure-relay-2.png"></dd>
90 
+    </li>
91 
+
92 
+    <li>选择<tt>服务策略(Exit Policies)</tt> 标签。如果你同意 Tor 用户通过你的中继使用这些服务，什么都不用修改。
93 
+    取消选中那些你不想其他用户<a href="<page docs/faq>#ExitPolicies">通过你的中继</a>。访问的服务。如果你只想成为非出口的中继，取消选中所有服务。</dt>
94 
+    <dd><img src="../img/screenshot-win32-configure-relay-3.png"></dd>
95 
+    </li>
96 
+
97 
+    <li>点击<tt>确定(OK)</tt>按钮。请看下面的第三步以确认中继工作正常。</li>
98 
+    </ol>
99 
+
100 
+    <br />
101 
+    <strong>手动配置</strong>：
102 
+    <ul>
103 
+    <li>修改<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">你的 torrc 文件</a>
104 
+    的最后部分。如果你想要成为公共中继（推荐），定义 ORPort，然后<a href="<page
105 
+    docs/faq>#ExitPolicies">查看出口策略</a>；如果你想要成为<a href="<page
106 
+    docs/faq>#RelayOrBridge">网桥</a>以帮助无法使用 Tor 的国家的用户，使用<a
107 
+    href="<page docs/bridges>#RunningABridge">这些行</a>即可。
108 
+    </li>
109 
+
110 
+    </ul></li>
111 
+
112 
+    <li>如果你使用防火墙，请为防火墙添加一个例外以使得进入的连接能够到达配置的端口
113 
+    （ORPort，如果启用的话，还有 DirPort）。如果你有硬件防火墙（Linksys 路由器、
114 
+    电缆调制解调器等），你需要参考 <a href="http://portforward.com/">portforward.com</a>。
115 
+    另外，请确认你允许所有的<em>向外</em>连接，这样你的中继才能与其他 Tor 中继通信。
116 
+    <!-- I'm always unable to figure out how to translate "incoming", "outgoing",
117 
+    "inbound", "outbound" and the similar into proper Chinese terms. :( -->
118 
+    </li>
119 
+
120 
+    <li>重启中继。如果<a
121 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">日志中有任何警告信息</a>，
122 
+    想办法解决它们。
123 
+    </li>
124 
+
125 
+    <li>订阅 <a href="http://archives.seul.org/or/announce/">or-announce</a> 邮件列表。
126 
+    该邮件列表流量非常小，它会在新的稳定版本发布时提醒你。你也可以考虑订阅<a
127 
+    href="<page docs/documentation>#MailingLists">更高流量的 Tor 邮件列表</a>。
128 
+    </li>
129 
+
130 
+    </ol>
131 
+
132 
+    <hr />
133 
+    <a id="check"></a>
134 
+    <h2><a class="anchor" href="#check">第三步：确认它在工作</a></h2>
135 
+    <br />
136 
+
137 
+    <p>一旦你的中继连接上了网络，它就会尝试检测能否从外部访问你所配置的端口。
138 
+    这一过程通常很快，但最长有可能持续 20 分钟。请查看是否有“<tt>Self-testing indicates your ORPort
139 
+    is reachable from the outside. Excellent.</tt>”这样的<a
140 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">日志条目</a>。
141 
+    如果你没有看到这条消息，说明从外部不能访问你的中继——你应该重新检查防火墙设置，
142 
+    检查测试的 IP 和端口是否正确，等等。
143 
+    </p>
144 
+
145 
+    <p>当确认能从外部访问中继时，它会向目录服务器上传一个“服务器描述符（server
146 
+    descriptor）”。客户端因此知道你的中继的地址、端口、公钥等。为了确认中继
147 
+    正常工作，你可以<a href="http://moria.seul.org:9032/tor/status/authority">手动
148 
+    下载一份网络状态</a>，从中查找你所配置的中继的名字。在获得最新的目录前，
149 
+    你需要等待几秒钟的时间。</p>
150 
+
151 
+    <hr />
152 
+    <a id="after"></a>
153 
+    <h2><a class="anchor" href="#after">第四步：一旦它开始正常工作</a></h2>
154 
+    <br />
155 
+
156 
+    <p>
157 
+    我们也推荐以下的步骤：
158 
+    </p>
159 
+
160 
+    <p>
161 
+    6、阅读有关<a
162 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/OperationalSecurity">安全操作</a>的信息，
163 
+    了解如何增强中继的安全性。
164 
+    </p>
165 
+
166 
+    <p>
167 
+    7、如果你运行一台以上的中继，这太好了！但是请在所有的中继配置文件中设置 <a
168 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#MultipleRelays">MyFamily
169 
+    选项</a>。
170 
+    </p>
171 
+
172 
+    <p>
173 
+    8、考虑速率限制。线缆调制解调器、DSL 和其他拥有非对称带宽（如下行速率大于上行速率）
174 
+    的用户应将速率限制为较低的那个带宽，以避免拥塞。请查看<a
175 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#LimitBandwidth">有关
176 
+    速率限制的 FAQ 条目</a>。
177 
+    </p>
178 
+
179 
+    <p>
180 
+    9、备份 Tor 中继的私钥（在 DataDirectory 目录里的“keys/secret_id_key”文件中）。
181 
+    这是你的中继的“身份证”，你需要保证它的安全，这样就没有人能读取通过你的中继的流量了。
182 
+    如果出于什么原因，你需要<a
183 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#UpgradeRelay">转移或还原
184 
+    Tor 中继</a>，这是你需要保存的关键文件。
185 
+    </p>
186 
+
187 
+    <p>
188 
+    10、如果你掌控你的域名的名字服务器，请考虑将反向的 DND 主机名设置成“anonymous-relay”、
189 
+    “proxy”或“tor-proxy”，这样当他人在他们的 Web 日志中看到你的服务器的地址时，
190 
+    他们将更快地知道发生了什么。如果你在运行出口节点，请将 <a
191 
+    href="https://tor-svn.freehaven.net/svn/tor/trunk/contrib/tor-exit-notice.html">Tor
192 
+    出口注意</a>放到与主机同名的虚拟主机上，这么做会使你和你的 ISP 收到的滥用指控少很多。
193 
+    </p>
194 
+
195 
+    <p>
196 
+    11、如果你的计算机不在运行 Web 服务器，请考虑将 ORPort 改成 443，将 DirPort
197 
+    改成 80。许多 Tor 用户由于防火墙的阻挡只能浏览 Web，这种修改使他们能够连接到你的
198 
+    Tor 中继。Win32 中继直接在 torrc 里修改 ORPort 和 DirPort，然后重启即可。OS X
199 
+    和 Unix 中继无法直接绑定这些端口（因为运行中继的用户不是 root），它们需要设置<a
200 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">端口
201 
+    转发</a>以使得连接能够到达 Tor 中继。如果 80 端口和 443 端口已被占用，其他常用
202 
+    的端口是 22、110 和 143。
203 
+    </p>
204 
+
205 
+    <p>
206 
+    12、如果你的 Tor 中继在同一 IP 地址运行其它服务——例如公开的 Web 服务器——请确认
207 
+    Web 服务器允许来自本地主机的连接。这是因为（当用户访问你的网站时）Tor 客户端会
208 
+    发现你的 Tor 中继是<a
209 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">访问
210 
+    你的 Web 服务器的最安全的方式</a>，总是会建立一条终止于你的中继的电路。
211 
+    如果你不想允许这种连接，你必须在出口策略中明确地拒绝它们。
212 
+    </p>
213 
+
214 
+    <p>
215 
+    13、（仅针对 Unix）。创建一个独立的用户运行中继。如果你安装的是 OS X 软件包、deb
216 
+    软件包或者 rpm 软件包，这一步已经完成。在其他情况下，你可以自己动手完成这一步。
217 
+    （Tor 中继不需要以 root 运行，因此不以 root 运行是一个好的实践。以一个“tor”用户运行
218 
+    避免了 identd 和其他检查用户名的服务会带来的问题。如果你非常谨小慎微，你自然可以<a
219 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorInChroot">将 Tor 置于
220 
+    chroot jail 中</a>。）
221 
+    </p>
222 
+
223 
+    <p>
224 
+    14、（仅针对 Unix）。你的操作系统可能将每一进程能够打开的文件标识符的数目限制在
225 
+    1024（甚至更少）。如果你计划运行一台快速的出口节点，这一数目也许不够。Linux 中，
226 
+    你应该在 /etc/security/limits.conf 文件中添加一行，如“toruser hard nofile 8192”
227 
+    （toruser 是运行 Tor 进程的用户），然后重新启动 Tor（如果 Tor 以软件包的方式
228 
+    安装）或者登出再登陆（如果运行 Tor 的用户就是你）。
229 
+    </p>
230 
+
231 
+    <p>
232 
+    15、如果你是通过软件包或安装文件安装的 Tor，它可能会在系统启动时自动启动 Tor。
233 
+    如果你是自源文件安装的 Tor，contrib/tor.sh 或者 contrib/torctl 中的初始脚本
234 
+    也许对你有用。
235 
+    </p>
236 
+
237 
+    <p>
238 
+    当你修改了 Tor 的配置，请记得检查中继在配置修改以后依旧正常工作。
239 
+    请确认你在 torrc 中设置了“ContactInfo”，这样当需要升级或者发生了什么问题时我们能与你取得联系。
240 
+    如果你有疑问或者问题，请查看文档的<a href="<page docs/documentation>#Support">获得支持</a>部分
241 
+    或者从 tor-ops 信箱<a href="<page about/contact>">联系我们</a>。
242 
+    感谢你为 Tor 网络成长做出的贡献！
243 
+    </p>
244 
+
245 
+    <hr />
246 
+
247 
+    <p>如果你有改进本文档的建议，请<a href="../contact.html.zh-cn">告诉我们</a>。
248 
+    谢谢！</p>
249 
+  </div>
250 
+  <!-- END MAINCOL -->
251 
+  <div id = "sidecol">
252 
+#include "side.wmi"
253 
+#include "info.wmi"
254 
+  </div>
255 
+  <!-- END SIDECOL -->
256 
+</div>
257 
+<!-- END CONTENT -->
258 
+#include <foot.wmi>
docs/zh-cn/tor-doc-unix.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,189 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21798 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor: Linux/BSD/Unix Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-unix>">Linux/BSD/Unix Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>在 Linux/BSD/Unix 上运行 <a href="<page index>">Tor</a> 客户端</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>
18 
+    请注意此处提供的是运行 Tor 客户端的安装指导。
19 
+    如果你想要贡献流量帮助网络增长（请这么做），
20 
+    请阅读<a href="<page docs/tor-doc-relay>">配置中继</a>指导。
21 
+    </b>
22 
+    </p>
23 
+
24 
+    <hr />
25 
+    <a id="installing"></a>
26 
+    <h2><a class="anchor" href="#installing">第一步：下载并安装 Tor</a></h2>
27 
+    <br />
28 
+
29 
+    <p>
30 
+    Tor 最新发布版本可以在<a href="<page download/download>">下载</a>页面获得。
31 
+    我们同样提供了 Debian，Red Hat，Gentoo，*BSD 等的软件包。
32 
+    如果你的操作系统是 Ubuntu，不要使用默认的软件包：请使用<a
33 
+    href="<page docs/debian>#ubuntu">我们的 deb 仓库</a>。
34 
+    </p>
35 
+
36 
+    <p>
37 
+    如果你打算从源文件编译，首先安装 <a href="http://www.monkey.org/~provos/libevent/">libevent</a>，
38 
+    并确认已安装 openssl 和 zlib（包括 -devel 软件包）。
39 
+    然后执行：<br />
40 
+    <tt>tar xzf tor-<version-stable>.tar.gz; cd tor-<version-stable><br />
41 
+    ./configure &amp;&amp; make</tt><br />
42 
+    现在你可以通过 <tt>src/or/tor</tt> 运行 Tor，
43 
+    或者你可以执行 <tt>make install</tt>（需要 root 权限）把它安装到 /usr/local，
44 
+    之后你就能通过 <tt>tor</tt> 启动 Tor。
45 
+    </p>
46 
+
47 
+    <p>
48 
+    默认状态下，Tor 被配置为客户端。它使用一个内置的默认配置文件，
49 
+    大多数人不需要修改其中的任何设置。Tor 安装完毕。
50 
+    </p>
51 
+
52 
+    <hr />
53 
+    <a id="privoxy"></a>
54 
+    <a id="polipo"></a>
55 
+    <h2><a class="anchor" href="#polipo">第二步：为 Web 浏览安装 Polipo</a></h2>
56 
+    <br />
57 
+
58 
+    <p>
59 
+    Tor 安装结束后，你需要配置应用程序来使用它。
60 
+    </p>
61 
+
62 
+    <p>
63 
+    第一步是配置 Web 浏览。首先从软件仓库安装 <a
64 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>。
65 
+    Polipo 是一种缓存 Web 代理，能很好地支持 HTTP 的 pipelining，
66 
+    因此适合 Tor 的延迟。Polipo 的版本至少应该是 1.0.4，因此早期的版本缺少 SOCKS 支持，
67 
+    无法与 Tor 配合使用。
68 
+    </p>
69 
+
70 
+    <p>
71 
+    Polipo 安装完成后（通过软件包或源文件），<b>你需要配置 Polipo 使用 Tor</b>。
72 
+    这里是为 Tor 准备的 <a
73 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/polipo.conf">Polipo
74 
+    配置文件</a>，用它替换当前的 Polipo 配置文件（如 /etc/polipo/config 或 ~/.polipo）。
75 
+    你需要重启 Polipo 以使修改生效。</p>
76 
+
77 
+    <p>如果愿意，你可以使用 Privoxy（<a
78 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/PrivoxyConfig">示例配置</a>）。
79 
+    需要说明的是，由于两个配置文件都设置了 8118 端口，你不能同时运行 Polipo 和 Privoxy。</p>
80 
+
81 
+    <hr />
82 
+    <a id="using"></a>
83 
+    <h2><a class="anchor" href="#using">第三步：配置应用程序使用 Tor</a></h2>
84 
+    <br />
85 
+
86 
+    <p>
87 
+    当 Tor 和 Polipo 安装结束后，你需要配置你的应用程序来使用它们。
88 
+    第一步是配置 Web 浏览。
89 
+    </p>
90 
+
91 
+    <p>
92 
+    为了取得最佳的安全性，你应该使用 Firefox 和 Torbutton。安装
93 
+    <a href="https://addons.mozilla.org/firefox/2275/">Torbutton 插件</a>，
94 
+    然后重新启动 Firefox，就这么简单：
95 
+    </p>
96 
+
97 
+    <img alt="Torbutton plugin for Firefox"
98 
+    src="../img/screenshot-torbutton.png"
99 
+    border="1">
100 
+
101 
+    <br />
102 
+
103 
+    <p>
104 
+    如果你打算在没有安装 Tor 的计算机上使用 Firefox，
105 
+    请阅读<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">在
106 
+    另一台计算机上运行 Tor 的 FAQ 条目</a>。
107 
+    </p>
108 
+
109 
+    <p>
110 
+    要让其他支持 HTTP 代理的应用程序使用 Tor，将它们指向 Polipo 即可（也就是 localhost 端口 8118）。
111 
+    直接使用 SOCKS（即时通讯、Jabber、IRC 等），可将你的应用程序直接指向 Tor（localhost 端口 9050），
112 
+    但是请阅读<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">此 FAQ 条目</a>——你得明白这么做可能是危险的。
113 
+    对于既不支持 SOCKS 也不支持 HTTP 的应用程序，考虑一下
114 
+    <a href="http://tsocks.sourceforge.net/">tsocks</a> 或者
115 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO#socat">socat</a>。
116 
+    </p>
117 
+
118 
+    <p>
119 
+    如何 Tor 化（Torify）其他应用程序的信息请查看
120 
+    <a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">Torify
121 
+    HOWTO</a>。
122 
+    </p>
123 
+
124 
+    <hr />
125 
+    <a id="verify"></a>
126 
+    <h2><a class="anchor" href="#verify">第四步：确定它在工作</a></h2>
127 
+    <br />
128 
+
129 
+    <p>
130 
+    然后，你应该通过浏览器来验证你的 IP 地址已经匿名化了。
131 
+    点击 <a href="https://check.torproject.org/">Tor 探测器</a>看看它是否认为你在使用 Tor。
132 
+    （如果这个站点下线了，<a
133 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">此
134 
+    FAQ 条目</a>有如何测试 Tor 的更多建议。）
135 
+    </p>
136 
+
137 
+    <p>
138 
+    如果你的个人防火墙限制你的计算机连接到它自己（包括 Fedora Core 4 上面的 SELinux 这样的东西），
139 
+    一定要允许从本地应用程序到 Polipo（本地端口 8118）和 Tor（本地端口 9050）的连接。
140 
+    如果你的防火墙阻挡向外的连接，那么至少让它能够连接 TCP 端口 80 和 443，
141 
+    然后阅读<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">此 FAQ 条目</a>。
142 
+    如果 SELinux 的配置使得 Tor 或者 Privoxy 无法正常运行，
143 
+    在目录 /etc/selinux/targeted 下创建一个名为 booleans.local 的文件。
144 
+    用你喜爱的文本编辑器修改这个文件加入“allow_ypbind=1”。
145 
+    然后重启机器使修改生效。
146 
+    </p>
147 
+    <p>
148 
+    如果它还是罢工，
149 
+    那就看看<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">此 FAQ 条目</a>寻找一些线索。
150 
+    </p>
151 
+
152 
+    <hr />
153 
+    <a id="relay"></a>
154 
+    <h2><a class="anchor" href="#relay">第五步：配置中继</a></h2>
155 
+    <br />
156 
+
157 
+    <p>
158 
+    Tor 网络依靠志愿者们贡献带宽运行。运行中继的人越多，Tor 网络的速度就越快。
159 
+    如果你的网络连接速度达到至少每秒 20KB，请运行一台中继以帮助 Tor。
160 
+    我们有许多特性使得 Tor 中继的运行简单而方便，包括带宽的速率限制，
161 
+    定制出口策略以避免滥用，以及对于动态 IP 地址的支持。
162 
+    </p>
163 
+
164 
+    <p>
165 
+    在互联网上的许多不同地方运行中继保护了 Tor 用户的安全。<a
166 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">你自身的
167 
+    匿名也能得到更好的保护</a>，因为站点不知道连接究竟来自你的电脑还是为他人传递。
168 
+    </p>
169 
+
170 
+    <p>
171 
+    阅读更详细的<a href="<page docs/tor-doc-relay>">配置中继</a>指导。
172 
+    </p>
173 
+
174 
+    <hr />
175 
+
176 
+    <p>
177 
+    如果你有改进本文档的建议，请<a href="<page about/contact>">告诉我们</a>。
178 
+    谢谢！
179 
+    </p>
180 
+  </div>
181 
+  <!-- END MAINCOL -->
182 
+  <div id = "sidecol">
183 
+#include "side.wmi"
184 
+#include "info.wmi"
185 
+  </div>
186 
+  <!-- END SIDECOL -->
187 
+</div>
188 
+<!-- END CONTENT -->
189 
+#include <foot.wmi>
docs/zh-cn/tor-doc-windows.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,152 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21995 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: MS Windows Install Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-doc-windows>">Windows Client</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Running the <a href="<page index>">Tor</a> Microsoft Windows 客户端</h1>
14 
+    <br />
15 
+
16 
+    <p>
17 
+    <b>请注意，这里是提供在 Microsoft Windows (2000, XP, Vista, 7, and Server Editions)
18 
+    上运行 Tor 客户端的安装指导。如果你想贡献流量帮助网络增长（请这么做），阅读 <a href="<page
19 
+    docs/tor-doc-relay>">配置一个中继</a> 指导。</b>
20 
+    </p>
21 
+
22 
+    <p>Freedom House has produced a video on how to install Tor.  You can view it
23 
+    at <a
24 
+    href="http://media.torproject.org/video/2009-install-and-use-tor.ogv">How to
25 
+    install Tor on Windows</a>.  Know of a better video, or one translated into
26 
+    your language? Let us know!</p>
27 
+
28 
+    <div class="center">
29 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor.ogv" autobuffer="true" controls="controls"></video></p>
30 
+    </div>
31 
+
32 
+    <hr /> <a id="installing"></a>
33 
+    <h2><a class="anchor" href="#installing">第一步：下载并安装 Tor</a></h2>
34 
+    <br />
35 
+
36 
+    <p>
37 
+    Microsoft Windows 套件包含 <a href="<page index>">Tor</a>，<a href="<page
38 
+    projects/vidalia>">Vidalia</a>（Tor 的图形用户界面），<a
39 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton</a>（Mozilla
40 
+    Firefox 的一个扩展）和 <a
41 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>
42 
+    （一种网络代理）整合了起来，并预先配置好能一起工作。下载 <a
43 
+    href="../<package-win32-bundle-stable>">稳定版</a> 或 <a
44 
+    href="../<package-win32-bundle-alpha>">测试版</a> 的 Windows 套件，<a href="<page
45 
+    download/download>">下载页面</a> 有更多选择。
46 
+    </p>
47 
+
48 
+    <img alt="tor installer splash page"
49 
+    src="../img/screenshot-win32-installer-splash.png" />
50 
+
51 
+    <p>如果你以前安装过 Tor、Vidalia 或 Polipo，您可以在如下所示的对话框中取消您不需要安装的部分。
52 
+    </p>
53 
+
54 
+    <img alt="选择要安装的组件" src="../img/screenshot-win32-installer-components.png"
55 
+    />
56 
+
57 
+    <p>在您完成安装程序后，您选择的组件会为您自动启动。
58 
+    </p>
59 
+
60 
+    <p>Tor 被配置为默认情况下的客户端。他使用内置的默认配置文件，大多数人不需要更改任何设置。Tor 安装完毕。
61 
+    </p>
62 
+
63 
+    <hr /> <a id="using"></a>
64 
+    <h2><a class="anchor" href="#using">第二步：配置应用程序使用 Tor</a></h2>
65 
+    <br />
66 
+
67 
+    <p>在安装完 Tor 和 Polipo 后，你需要配置应用程序来使用它们。第一步是配置 Web 浏览器。</p>
68 
+
69 
+    <p>您应该通过使用 Firefox  和 Torbutton 扩展让 Tor 获得最佳的安全性。该套件为您安装了 <a
70 
+    href="https://addons.mozilla.org/firefox/2275/">Torbutton 扩展</a>。重新启动
71 
+    Firefox，就这么简单：
72 
+    </p>
73 
+
74 
+    <img alt="Torbutton 用于 Firefox 的扩展" src="../img/screenshot-torbutton.png"
75 
+    border="1"/> <br />
76 
+
77 
+    <p>
78 
+    如果你打算在没有安装 Tor 的计算机上使用 Firefox，见 <a
79 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SocksListenAddress">常见问题条目——在不同的计算机运行
80 
+    Tor</a>。
81 
+    </p>
82 
+
83 
+    <p>要让其他支持 HTTP 代理的应用程序使用 Tor，将它们指向 Polipo 即可（也就是 localhost 端口 8118）。直接使用
84 
+    SOCKS（即时通讯、Jabber、IRC 等），可将你的应用程序直接指向 Tor（localhost 端口 9050），但是请阅读 <a
85 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#SOCKSAndDNS">此FAQ
86 
+    条目</a> ——你得明白这么做可能是危险的。对于既不支持 SOCKS 也不支持 HTTP 的应用程序，考虑一下 SocksCap 或者 <a
87 
+    href="http://www.freecap.ru/eng/">FreeCap</a>。（FreeCap 是自由软件；SocksCap 不是。）</p>
88 
+
89 
+    <p>如何 Tor 化（Torify）其他应用程序的信息请查看 <a
90 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorifyHOWTO">怎么
91 
+    Torify</a>。
92 
+    </p>
93 
+
94 
+    <hr /> <a id="verify"></a>
95 
+    <h2><a class="anchor" href="#verify">步骤三：请确保它在工作</a></h2>
96 
+    <br />
97 
+
98 
+    <p>
99 
+    检查 Vidalia 是否正在运行。Vidalia 用一个绿色洋葱的图标指示 Tor 正在运行，Tor
100 
+    不运行时是一个暗红色“X”的灰色洋葱图标。你可以通过右键单击系统托盘中 Vidalia 的图标，从菜单选择“开始”或者“停止”来启动或终止
101 
+    Tor，如下所示：
102 
+    </p>
103 
+
104 
+    <img alt="Vidalia 托盘图标" src="../img/screenshot-win32-vidalia.png"/>
105 
+
106 
+    <p>
107 
+    然后，你应该通过您的浏览器来验证你的 IP 地址是否已经匿名化了。点击 <a
108 
+    href="https://check.torproject.org/">Tor 探测器</a> 它是否认为你在使用 Tor。（如果这个站点下线了，看
109 
+    <a
110 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#IsMyConnectionPrivate">此
111 
+    FAQ条目</a> 有如何测试 Tor 的更多建议。）
112 
+    </p>
113 
+
114 
+    <p>如果您的个人防火墙限制您的计算机连接到它自己，一定要允许从本地应用程序到本地端口 8118 和 9050
115 
+    的连接。如果你的防火墙阻挡向外的连接，那么至少让它能够连接 TCP 端口 80 和 443，然后阅读 <a
116 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#FirewalledClient">此
117 
+    FAQ 条目</a>。
118 
+    </p>
119 
+
120 
+    <p>如果仍然没有工作，看看 <a
121 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">此
122 
+    FAQ 条目</a> 寻找原因。</p>
123 
+
124 
+    <p>
125 
+    一旦工作正常，请了解更多 <a href="<page download/download>#Warning">Tor 提供什么，不提供什么</a>。
126 
+    </p>
127 
+
128 
+    <hr /> <a id="server"></a> <a id="relay"></a>
129 
+    <h2><a class="anchor" href="#relay">第四步：配置它为中继</a></h2>
130 
+    <br />
131 
+
132 
+    <p>Tor 网络依靠志愿者们贡献带宽运行。运行中继的人越多，Tor 网络的速度就越快。如果你的网络连接速度达到每秒 20KB 以上，请帮忙运行一台中继以帮助
133 
+    Tor。我们有许多特性使得 Tor 中继的运行简单且方便，包括带宽的速率限制、定制出口策略以避免滥用、以及对于动态 IP 地址的支持。</p>
134 
+
135 
+    <p>在互联网上的许多不同的地方用户运行了中继保护了 Tor 用户的安全。<a
136 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">你自身的匿名也能得到更好的保护</a>，因为站点不知道连接究竟来自你的电脑还是为他人传递。</p>
137 
+
138 
+    <p>阅读更详细的 <a href="<page docs/tor-doc-relay>">配置中继</a> 指导。</p>
139 
+
140 
+    <hr />
141 
+
142 
+    <p>如果你有改进本文档的建议，请 <a href="<page about/contact>">发送给我们</a>。谢谢！</p>
143 
+  </div>
144 
+  <!-- END MAINCOL -->
145 
+  <div id = "sidecol">
146 
+#include "side.wmi"
147 
+#include "info.wmi"
148 
+  </div>
149 
+  <!-- END SIDECOL -->
150 
+</div>
151 
+<!-- END CONTENT -->
152 
+#include <foot.wmi>
docs/zh-cn/tor-hidden-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,225 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22314 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Hidden Service Configuration Instructions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page docs/documentation>">Documentation &raquo; </a>
10 
+    <a href="<page docs/tor-hidden-service>">Tor Hidden Service</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>配置 <a href="<page index>">Tor</a> 隐匿服务</h1>
14 
+    <hr />
15 
+
16 
+    <p>Tor 允许客户端和中继提供隐匿服务。即你能够在不向用户泄露你的 IP 地址的情况下
17 
+    提供 Web 服务、SSH 服务等等。事实上，因为你不需要任何公开的地址，你能在防火墙后面
18 
+    运行隐匿服务。
19 
+    </p>
20 
+
21 
+    <p>如果你已安装了 Tor，你能通过访问<a href="http://duskgytldkxiuqc6.onion/">我们的
22 
+    隐匿服务实例</a>或者 <a href="http://gaddbiwdftapglkq.onion/">Wikileaks
23 
+    隐匿服务</a>来感受隐匿服务是如何运行的。
24 
+    </p>
25 
+
26 
+    <p>本指导描述了设置你自己的隐匿服务网站的步骤。如需了解隐匿服务的工作原理，
27 
+    请查看<a href="<page docs/hidden-services>">隐匿服务协议</a>页面。
28 
+    </p>
29 
+
30 
+    <hr />
31 
+    <a id="zero"></a>
32 
+    <h2><a class="anchor" href="#zero">第零步：使 Tor 正常工作</a></h2>
33 
+    <br />
34 
+
35 
+    <p>开始前，你需要确认：</p>
36 
+    <ol>
37 
+    <li>Tor 正在运行，</li>
38 
+    <li>你确实正确地设置了一切。</li>
39 
+    </ol>
40 
+
41 
+
42 
+    <p>Windows 用户应该遵照 <a href="<page docs/tor-doc-windows>">Windows 指导</a>，OS
43 
+    X 用户应该遵照 <a href="<page docs/tor-doc-osx>">OS X 指导</a>，Linux/BSD/Unix
44 
+    用户应该遵照 <a href="<page docs/tor-doc-unix>">Unix 指导</a>。
45 
+    </p>
46 
+
47 
+    <p>一旦 Tor 安装与配置完成，你能通过访问<a
48 
+    href="http://duskgytldkxiuqc6.onion/">我们的隐匿服务实例</a>或者 <a
49 
+    href="http://gaddbiwdftapglkq.onion/">Wikileaks 隐匿服务</a>来感受隐匿服务是如何运行的。
50 
+    通常需要 10 到 60 秒的时间来载入页面（或者确定当前无法访问）。如果立刻失败并且
51 
+    浏览器弹出警告说“找不到 www.duskgytldkxiuqc6.onion，请检查地址重新尝试”，则说明
52 
+    你没能正确配置 Tor。请查看<a
53 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ItDoesntWork">此
54 
+    FAQ 条目</a>获得帮助。
55 
+    </p>
56 
+
57 
+    <hr />
58 
+    <a id="one"></a>
59 
+    <h2><a class="anchor" href="#one">第一步：在本地安装 Web 服务器</a></h2>
60 
+    <br />
61 
+
62 
+    <p>首先，你需要在本地设置一台 Web 服务器。设置 Web 服务器是一个棘手的难题，
63 
+    因此我们在这里将仅仅介绍一些基本步骤。如果你想知道更多，去找一位能帮助你的朋友。
64 
+    我们建议你为隐匿服务安装一台新的、独立的 Web 服务器，这是因为即使你已经有了一台，
65 
+    你也许正在用它（或打算用它）运行一个真实的网站。
66 
+    </p>
67 
+
68 
+    <p>如果你使用的是 Unix 或 OS X 并且对命令行不陌生，目前为止最好的方法是安装
69 
+    <a href="http://www.acme.com/software/thttpd/">thttpd</a>。获取最新的源文件压缩包，
70 
+    解压缩（它会创建自己的目录），运行 <kbd>./configure &amp;&amp; make</kbd>。
71 
+    然后 <kbd>mkdir hidserv; cd hidserv</kbd>，然后运行 <kbd>../thttpd -p 5222 -h
72 
+    localhost</kbd>。你将回到提示符，现在一台 Web 服务器已在端口 5222 运行。你可以在
73 
+    hidserv 目录放入（隐匿服务提供的）文件。
74 
+    </p>
75 
+
76 
+    <p>如果你使用的是 Windows，你可以选择 <a href="http://savant.sourceforge.net/">Savant</a>
77 
+    或者 <a href="http://httpd.apache.org/">Apache</a>，请配置其仅绑定本地主机。
78 
+    你还应该知道监听的端口，下面将用到。
79 
+    </p>
80 
+
81 
+    <p>（我们将 Web 服务器仅绑定本地主机的原因是为了保证它无法被公开地访问。如果有人
82 
+    可以直接访问它，他们将据此确认你的计算机正在提供隐匿服务。）
83 
+    </p>
84 
+
85 
+    <p>当 Web 服务器设置完成时，请确认它工作正常：打开浏览器，访问 <a
86 
+    href="http://localhost:5222/">http://localhost:5222/</a>，其中 5222 是上面你所
87 
+    选择的端口。然后在主目录中加入一个文件，看看它是否出现在你所访问的站点中。
88 
+    </p>
89 
+
90 
+    <hr />
91 
+    <a id="two"></a>
92 
+    <h2><a class="anchor" href="#two">第二步：配置你的隐匿服务</a></h2>
93 
+    <br />
94 
+
95 
+    <p>接下来，你需要将你的隐匿服务指向本地的 Web 服务器。
96 
+    </p>
97 
+
98 
+    <p>首先，在你的文本编辑器中打开 torrc 文件。（如果不明白这句话的意思，请看<a
99 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#torrc">关于 torrc 的
100 
+    FAQ 条目</a>。）在中间部分查找这样一行</p>
101 
+
102 
+    <pre>
103 
+    \############### This section is just for location-hidden services ###
104 
+    </pre>
105 
+
106 
+    <p>文件的这一部分包括了几组，每组由多行构成，每一组都代表了一项隐匿服务。现在
107 
+    它们都被注释掉了（以 # 开始的行），所以隐匿服务是禁止的。每组都包括一行
108 
+    <var>HiddenServiceDir</var>，另有一行或多行 <var>HiddenServicePort</var>：</p>
109 
+    <ul>
110 
+    <li><var>HiddenServiceDir</var> 是 Tor 将要保存隐匿服务信息的目录。特别地，Tor
111 
+    将创建一个名为 <var>hostname</var> 的文件记录 onion URL。你无需向此目录添加
112 
+    任何文件。</li>
113 
+    <li><var>HiddenServicePort</var> 让你指定虚拟端口（即当他人访问隐匿服务时认为他们
114 
+    在使用的端口）和虚拟端口的连接重定向到的 IP 地址和端口。</li>
115 
+    </ul>
116 
+
117 
+    <p>将以下两行加入 torrc：
118 
+    </p>
119 
+
120 
+    <pre>
121 
+    HiddenServiceDir /Library/Tor/var/lib/tor/hidden_service/
122 
+    HiddenServicePort 80 127.0.0.1:5222
123 
+    </pre>
124 
+
125 
+    <p>你需要修改 <var>HiddenServiceDir</var> 这一行，使其指向一个运行 Tor 的用户能够
126 
+    读写的目录。如果你正在使用 OS X 的 Tor 软件包，上面一行是有效的。在 Unix 上请
127 
+    尝试“/home/username/hidserv/”，“username”对应你自己的用户名。在 Windows 上或许可以
128 
+    这样：</p>
129 
+    <pre>
130 
+    HiddenServiceDir C:\Documents and Settings\username\Application Data\hidden_service\\
131 
+    HiddenServicePort 80 127.0.0.1:5222
132 
+    </pre>
133 
+
134 
+    <p>现在保存 torrc，关闭 Tor，然后再次启动它。
135 
+    </p>
136 
+
137 
+    <p>如果 Tor 再次成功启动，很好。否则的话，说明什么地方发生了问题。首先查看日志文件
138 
+    寻找线索。它将记录一些警告或错误消息。你应该能够由此明白错在哪里。典型的错误是
139 
+    torrc 中的笔误或不正确的目录权限。（如果你不知道如何激活日志或找不到日志文件，
140 
+    请查看<a href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#Logs">关于
141 
+    日志的 FAQ 条目</a>。）
142 
+    </p>
143 
+
144 
+    <p>Tor 在启动时会自动创建你所指定的 <var>HiddenServiceDir</var>（如果需要的话），
145 
+    它还将在那儿创建两个文件。</p>
146 
+
147 
+    <dl>
148 
+    <dt><var>private_key</var></dt>
149 
+    <dd>首先，Tor 将生成一对新的供隐匿服务使用的公钥/私钥对。它被写入一个
150 
+    名为“private_key”的文件中。不要与他人分享这一秘钥——如果你这么做，他们将能够冒充你的
151 
+    隐匿服务。</dd>
152 
+    <dt><var>hostname</var></dt>
153 
+    <dd>Tor 将创建的另一个文件是“hostname”。其中包括了你的公钥的简短摘要——它看起来像
154 
+    <tt>duskgytldkxiuqc6.onion</tt>。这是你的服务的公开名字，你能够将它告诉别人，
155 
+    把它发布在网站上，打印在商务名片上，等等。</dd>
156 
+    </dl>
157 
+
158 
+    <p>如果运行 Tor 的不是你而是其他用户，例如在 OS X、Debian 或 Red Hat 平台上，
159 
+    则你需要成为 root 来查看这些文件。</p>
160 
+
161 
+    <p>现在你已经重启了 Tor，它正忙于在 Tor 网络中选择介绍节点（introduction points），
162 
+    以及生成一个<em>隐匿服务描述符</em>。隐匿服务描述符是经过签名的介绍节点列表与服务
163 
+    的完整的公钥。它以匿名的方式将这一描述符发布到目录服务器，当其他用户尝试访问你的
164 
+    服务时，他们同样以匿名的方式从目录服务器获取这一描述符。
165 
+    </p>
166 
+
167 
+    <p>现在就来试试：将 hostname 文件中的内容粘贴到浏览器中。如果一切正常，你将看到
168 
+    你在第一步时添加的 HTML 页面。如果工作不正常，请查看日志寻找线索，不断尝试直至
169 
+    正常工作。
170 
+    </p>
171 
+
172 
+    <hr />
173 
+    <a id="three"></a>
174 
+    <h2><a class="anchor" href="#three">第三步：更多高级技巧</a></h2>
175 
+    <br />
176 
+
177 
+    <p>如果你打算长期运行服务，你或许需要在什么地方备份 <var>private_key</var> 文件。
178 
+    </p>
179 
+
180 
+    <p>在上面，我们避免推荐 Apache，这是因为 a) 许多人可能已在他们的计算机上用它来
181 
+    运行公开的 Web 服务器；b) 它很大，可能在许多地方泄露你的 IP 地址或其他信息，如
182 
+    404 页面中。但是对于需要更多功能的人来说，Apache 也许是正确的选择。有谁能为我们
183 
+    制作一份清单，列举使用 Apache 作为隐匿服务时需要注意的事项吗？Savant 可能也会有
184 
+    这些问题。
185 
+    </p>
186 
+
187 
+    <p>如果你需要为一项隐匿服务转发多个虚拟端口，添加多行 <var>HiddenServicePort</var>
188 
+    即可。如果你需要从同一个 Tor 客户端运行多项隐匿服务，添加另一行 <var>HiddenServiceDir</var>
189 
+    即可。紧接着的所有 <var>HiddenServicePort</var> 行都与这一行 <var>HiddenServiceDir</var>
190 
+    相关，直到你又添加另一行 <var>HiddenServiceDir</var>：
191 
+    </p>
192 
+
193 
+    <pre>
194 
+    HiddenServiceDir /usr/local/etc/tor/hidden_service/
195 
+    HiddenServicePort 80 127.0.0.1:8080
196 
+
197 
+    HiddenServiceDir /usr/local/etc/tor/other_hidden_service/
198 
+    HiddenServicePort 6667 127.0.0.1:6667
199 
+    HiddenServicePort 22 127.0.0.1:22
200 
+    </pre>
201 
+
202 
+    <p>你还需要记住一些与匿名有关的问题：
203 
+    </p>
204 
+    <ul>
205 
+    <li>如前所述，小心你的 Web 服务器泄露你的身份信息、你的计算机或你的位置。
206 
+    例如，访问者可能会知道它是 thttpd 还是 Apache，以及了解你的操作系统的一些信息。</li>
207 
+    <li>如果你的计算机不是一直在线的，你的隐匿服务也不会一直在线。这会向观察敏锐的敌手
208 
+    泄露信息。</li>
209 
+    <!-- increased risks over time -->
210 
+    </ul>
211 
+
212 
+    <hr />
213 
+
214 
+    <p>如果你有改进本文档的建议，请<a href="../contact.html.zh-cn">告诉我们</a>。
215 
+    谢谢！</p>
216 
+  </div>
217 
+  <!-- END MAINCOL -->
218 
+  <div id = "sidecol">
219 
+#include "side.wmi"
220 
+#include "info.wmi"
221 
+  </div>
222 
+  <!-- END SIDECOL -->
223 
+</div>
224 
+<!-- END CONTENT -->
225 
+#include <foot.wmi>
documentation/torproject.aux
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,16 @@
1 
+\relax
2 
+\@writefile{toc}{\contentsline {section}{\numberline {1}introduction}{1}}
3 
+\@writefile{toc}{\contentsline {section}{\numberline {2}/include}{1}}
4 
+\@writefile{toc}{\contentsline {subsection}{\numberline {2.1}head.wmi}{1}}
5 
+\@writefile{toc}{\contentsline {subsection}{\numberline {2.2}foot.wmi}{2}}
6 
+\newlabel{side-navigation}{{2.2}{2}}
7 
+\@writefile{toc}{\contentsline {subsection}{\numberline {2.3}side.wmi}{2}}
8 
+\@writefile{toc}{\contentsline {subsection}{\numberline {2.4}functions.wmi}{3}}
9 
+\@writefile{toc}{\contentsline {subsection}{\numberline {2.5}perl-globals.wmi}{3}}
10 
+\newlabel{cgi-trampoline}{{2.5}{3}}
11 
+\@writefile{toc}{\contentsline {section}{\numberline {3}languageswitch.cgi}{3}}
12 
+\@writefile{toc}{\contentsline {section}{\numberline {4}building the site}{4}}
13 
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.1}build prerequisites}{4}}
14 
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.2}build translation po files}{4}}
15 
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.3}import translated pages}{4}}
16 
+\@writefile{toc}{\contentsline {subsection}{\numberline {4.4}build}{4}}
documentation/torproject.log
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,94 @@
1 
+This is pdfTeXk, Version 3.141592-1.40.3 (Web2C 7.5.6) (format=pdflatex 2010.6.1)  21 JUN 2010 02:08
2 
+entering extended mode
3 
+ %&-line parsing enabled.
4 
+**torproject.tex
5 
+(./torproject.tex
6 
+LaTeX2e <2005/12/01>
7 
+Babel <v3.8h> and hyphenation patterns for english, usenglishmax, dumylang, noh
8 
+yphenation, loaded.
9 
+(/usr/share/texmf-texlive/tex/latex/base/article.cls
10 
+Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
11 
+(/usr/share/texmf-texlive/tex/latex/base/size11.clo
12 
+File: size11.clo 2005/09/16 v1.4f Standard LaTeX file (size option)
13 
+)
14 
+\c@part=\count79
15 
+\c@section=\count80
16 
+\c@subsection=\count81
17 
+\c@subsubsection=\count82
18 
+\c@paragraph=\count83
19 
+\c@subparagraph=\count84
20 
+\c@figure=\count85
21 
+\c@table=\count86
22 
+\abovecaptionskip=\skip41
23 
+\belowcaptionskip=\skip42
24 
+\bibindent=\dimen102
25 
+) (./torproject.aux)
26 
+\openout1 = `torproject.aux'.
27 
+
28 
+LaTeX Font Info:    Checking defaults for OML/cmm/m/it on input line 2.
29 
+LaTeX Font Info:    ... okay on input line 2.
30 
+LaTeX Font Info:    Checking defaults for T1/cmr/m/n on input line 2.
31 
+LaTeX Font Info:    ... okay on input line 2.
32 
+LaTeX Font Info:    Checking defaults for OT1/cmr/m/n on input line 2.
33 
+LaTeX Font Info:    ... okay on input line 2.
34 
+LaTeX Font Info:    Checking defaults for OMS/cmsy/m/n on input line 2.
35 
+LaTeX Font Info:    ... okay on input line 2.
36 
+LaTeX Font Info:    Checking defaults for OMX/cmex/m/n on input line 2.
37 
+LaTeX Font Info:    ... okay on input line 2.
38 
+LaTeX Font Info:    Checking defaults for U/cmr/m/n on input line 2.
39 
+LaTeX Font Info:    ... okay on input line 2.
40 
+
41 
+Underfull \hbox (badness 10000) in paragraph at lines 99--110
42 
+
43 
+ []
44 
+
45 
+[1
46 
+
47 
+{/var/lib/texmf/fonts/map/pdftex/updmap/pdftex.map}]
48 
+Overfull \hbox (76.90027pt too wide) in paragraph at lines 141--141
49 
+[]          \OT1/cmtt/m/n/10.95 onclick="window.location='tor-doc-relay.html.de
50 
+'">Deutsch</option>[]
51 
+ []
52 
+
53 
+
54 
+Overfull \hbox (82.64896pt too wide) in paragraph at lines 141--141
55 
+[]          \OT1/cmtt/m/n/10.95 onclick="window.location='tor-doc-relay.html.it
56 
+'">Italiano</option>[]
57 
+ []
58 
+
59 
+
60 
+Overfull \hbox (37.5869pt too wide) in paragraph at lines 152--153
61 
+\OT1/cmr/m/n/10.95 pages de-fault to the en-glish ver-sion. Ex-ter-nal links (e
62 
+.g. http://check.torproject.org)
63 
+ []
64 
+
65 
+[2] [3]
66 
+Overfull \hbox (7.09915pt too wide) in paragraph at lines 198--202
67 
+\OT1/cmr/m/n/10.95 libhtml-clean-perl, libimage-size-perl, libperl5.10, libtidy
68 
+-0.99-0, libyaml-syck-
69 
+ []
70 
+
71 
+
72 
+Overfull \hbox (25.16208pt too wide) in paragraph at lines 215--215
73 
+[]\OT1/cmtt/m/n/10.95 TORGIT = PATH_TO_TOR_DEVELOPMENT   # the path to developm
74 
+ent branch[]
75 
+ []
76 
+
77 
+[4] (./torproject.aux) )
78 
+Here is how much of TeX's memory you used:
79 
+ 214 strings out of 95086
80 
+ 2338 string characters out of 1183256
81 
+ 49015 words of memory out of 1500000
82 
+ 3469 multiletter control sequences out of 10000+50000
83 
+ 5318 words of font info for 20 fonts, out of 1200000 for 2000
84 
+ 28 hyphenation exceptions out of 8191
85 
+ 21i,5n,19p,618b,241s stack positions out of 5000i,500n,6000p,200000b,5000s
86 
+</usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmbx12
87 
+.pfb></usr/share/texmf-texlive/fonts/type1/bluesky/cm/cmr10.pfb></usr/share/tex
88 
+mf-texlive/fonts/type1/bluesky/cm/cmtt10.pfb>
89 
+Output written on torproject.pdf (4 pages, 42120 bytes).
90 
+PDF statistics:
91 
+ 27 PDF objects out of 1000 (max. 8388607)
92 
+ 0 named destinations out of 1000 (max. 131072)
93 
+ 1 words of extra memory for PDF output out of 10000 (max. 10000000)
94 
+
documentation/torproject.pdf
Zeige Datei @ 2a9aaa802
documentation/torproject.tex
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,233 @@
1 
+\documentclass[11pt]{article}
2 
+\begin{document}
3 
+
4 
+\section{introduction}
5 
+This document (which may be found in /documentation) explains the wml code used to generate the Tor Project website. The original Tor Project documentation in /include/README gives a brief overview of Tor Project's use of wml. Some additional embedded perl was added to generate static content, namely navigation bars and a language selection dropdown in the footer of the page. Adding new content to the site is done by adding the new wml source files and an entry in the relavent navigation bar. Section \ref{side-navigation} outlines the syntax for the menu structure and section.
6 
+
7 
+%\section{/}
8 
+%   home.wml
9 
+%
10 
+%\section{/about}
11 
+%   about.wml
12 
+%   board.wml
13 
+%   contact.wml
14 
+%   contributors.wml
15 
+%   future.wml
16 
+%   gsoc.wml
17 
+%   overview.wml
18 
+%   people.wml
19 
+%   sidenav.wmi
20 
+%   sponsors.wml
21 
+%   staying.wml
22 
+%   torusers.wml
23 
+%   translators.wml
24 
+%   volunteers.wml
25 
+%   why.wml
26 
+%
27 
+%\section{/docs}
28 
+%   android.wml
29 
+%   bridges.wml
30 
+%   debian-vidalia.wml
31 
+%   debian.wml
32 
+%   documentation.wml
33 
+%   faq-abuse.wml
34 
+%   faq.wml
35 
+%   gloassary.wml
36 
+%   hidden-services.wml
37 
+%   installguide.wml
38 
+%   manual.wml
39 
+%   N900.wml
40 
+%   rpms.wml
41 
+%   running-a-mirror.wml
42 
+%   sidenav.wmi
43 
+%   tor-doc-osx.wml
44 
+%   tor-doc-relay.wml
45 
+%   tor-doc-unix.wml
46 
+%   tor-doc-web.wml
47 
+%   tor-doc-windows.wml
48 
+%   tor-hidden-service.wml
49 
+%   tor-manual-dev.wml
50 
+%   tor-manual.wml
51 
+%   trademark-faq.wml
52 
+%   verifying-signatures.wml
53 
+%
54 
+%\section{/download}
55 
+%   download.wml
56 
+%   easy-download.wml
57 
+%   thankyou.wml
58 
+%
59 
+%\section{/getinvolved}
60 
+%   developers.wml
61 
+%   everyone.wml
62 
+%   getinvolved.wml
63 
+%   mirrors.wml
64 
+%   open-positions.wml
65 
+%   sidenav.wmi
66 
+%   technical.wml
67 
+%   translation-overview.wml
68 
+%   translation-portal.wml
69 
+%   translation-status.wml
70 
+%   translation.wml
71 
+%   tshirt.wml
72 
+%   volunteer.wml
73 
+%
74 
+%\section{/press}
75 
+%   2008-12-19-roadmap-press-release.wml
76 
+%   2009-03-12-performance-roadmap-press-release.wml
77 
+%   2010-03-25-tor-store-press-release.wml
78 
+%   index.wml
79 
+%   info.wmi
80 
+%   inthemedia.wml
81 
+%   pressreleases.wml
82 
+%   press.wml
83 
+%   sidenav.wmi
84 
+%
85 
+%\section{/projects}
86 
+%   clientside.wml
87 
+%   google.wml
88 
+%   hidserv.wml
89 
+%   index.wml
90 
+%   lowbandwidth.wml
91 
+%   projects.wml
92 
+%   sampleproject.wml
93 
+%   sidenav.wmi
94 
+%   torbutton-faq.wml
95 
+%   torbutton-options.wml
96 
+%   torbutton.wml
97 
+
98 
+\section{/include}
99 
+Files present:\\
100 
+foot.wmi - document footer\\
101 
+functions.wmi - translation functions\\
102 
+head.wmi - document head\\
103 
+info.wmi - info snippet\\
104 
+links.wmi - functions to generate links\\
105 
+mirrors-table.wmi - mirror list\\
106 
+navigation.wmi - input to head.wmi navigation menu\\
107 
+perl-globals.wmi - global variables\\
108 
+side.wmi - side menu navigation\\
109 
+versions.wmi - version number macros\\
110 
+
111 
+\subsection{head.wmi}
112 
+  This is the main header for all site documents. The main navigation bar is generated at build time here by referencing a language-specific file (navigation.wmi) which contains a list of URLs and the link text to display.
113 
+
114 
+\begin{verbatim}
115 
+   example path: /en/navigation.wmi
116 
+   example path: /de/navigation.wmi
117 
+\end{verbatim}
118 
+
119 
+  Translators can create a language-specific version in order to generate the top navbar.
120 
+
121 
+  The second navigation element, 'calltoaction' is generated similarly from the second list in navigation.wmi
122 
+
123 
+\subsection{foot.wmi}
124 
+   This is the footer for all site documents. There are quick links to site content as well as a translation selection menu.
125 
+   Translation selection:
126 
+  At build time, available languages are detected by the presence of a language subdirectory:
127 
+
128 
+  example:
129 
+
130 
+/about/en/about.wml contains valid translations for nl, and de if files /about/nl/about.wml and /about/de/about.wml exist. For each translated language a <select> <option> is created. Javascript onClick is used to direct clients that support javascript, but if the client does not support javascript a simple perl cgi trampoline may be used to redirect the client to the selected page on form submit. (see: \ref{cgi-trampoline})
131 
+\begin{verbatim}
132 
+<form action="../cgi-bin/languageswitch.cgi">
133 
+   <select name="Language" id="lang">
134 
+      <option value="docs/tor-doc-relay.html.de"
135 
+          onclick="window.location='tor-doc-relay.html.de'">Deutsch</option>
136 
+      <option value="docs/tor-doc-relay.html.it"
137 
+          onclick="window.location='tor-doc-relay.html.it'">Italiano</option>
138 
+   </select>
139 
+   <input class="go" type="submit" name="submit" value="Go">
140 
+</form>
141 
+\end{verbatim}
142 
+
143 
+\label{side-navigation}
144 
+\subsection{side.wmi}
145 
+This is the side navbar generator for documents that utilize a side navbar. A language-specific sidenav.wmi file contains a hierarchical structure of menu elements.
146 
+
147 
+\begin{verbatim}
148 
+example path: /about/en/sidenav.wmi
149 
+example path: /docs/de/sidenav.wmi
150 
+\end{verbatim}
151 
+
152 
+Each element contains url and txt fields and may also contain a list of subelements. At build time the navbar is rendered for each page so that nested elements are expanded/collapsed and css styles are set. Untranslated pages default to the english version. External links (e.g. http://check.torproject.org) are inserted without modification.
153 
+
154 
+example structure:
155 
+
156 
+\begin{verbatim}
157 
+
158 
+  $sidenav = [
159 
+      {'url'  => 'about/about',
160 
+       'txt'  => 'Tor Overview',
161 
+       'subelements' => [
162 
+          {'url'  => 'about/why',
163 
+           'txt'  => 'Why We Need Tor',
164 
+          },
165 
+          {'url'  => 'about/staying',
166 
+           'txt'  => 'Staying Anonymous',
167 
+          },
168 
+          {'url'  => 'about/future',
169 
+           'txt'  => 'Future of Tor',
170 
+          }]
171 
+      }
172 
+  ];
173 
+
174 
+\end{verbatim}
175 
+
176 
+\subsection{functions.wmi}
177 
+An additional function pageToURL(\$\$) performs the same conversion as <page> tags, but may be called from within eperl statements (such as those used to generate the navigation structure). The arguments to the function are \$page, \$lang, where \$page is the document path (e.g. /docs/tor-doc-osx) and \$lang is the language (e.g. en, de, it).
178 
+
179 
+\subsection{perl-globals.wmi}
180 
+An additional global variable (\$WML\_SRC\_DIRNAME) was added for use in determining the input file path.
181 
+
182 
+
183 
+\label{cgi-trampoline}
184 
+\section{languageswitch.cgi}
185 
+   The language selection dropdown (see document footer: foot.wmi) requires javascript support or a server-side script to handle a form submit. languageswitch.cgi is a perl cgi script that returns a URL passed by GET as a redirect.
186 
+\begin{verbatim}
187 
+#!/usr/bin/env perl
188 
+
189 
+use CGI qw(:standard);
190 
+my $lang = param('Language');
191 
+print "Status: 302 Moved\nLocation: /$lang\n\n";
192 
+\end{verbatim}
193 
+
194 
+\section{building the site}
195 
+\subsection{build prerequisites}
196 
+The ubuntu package wml has these dependencies:
197 
+
198 
+eperl, iselect, libbit-vector-perl, libcarp-clan-perl,
199 
+libgetopt-argvfile-perl, libhtml-clean-perl,
200 
+libimage-size-perl, libperl5.10, libtidy-0.99-0,
201 
+libyaml-syck-perl, linklint, m4, mp4h, slice, tidy, txt2html, wml
202 
+
203 
+Make sure that you have checked out the translation project: \\
204 
+https://svn.torproject.org/svn/translation/ \\
205 
+as well as the website project: \\
206 
+https://svn.torproject.org/svn/website/
207 
+
208 
+In addition to the translation project, you must also check out stable and development branches of tor, which are used to generate the online version of the manpages. The path to these repositories must be set the Makefile as follows:
209 
+
210 
+\begin{verbatim}
211 
+TORSVNSTABLE = PATH_TO_TOR_STABLE  # the path to stable branch
212 
+TORGIT = PATH_TO_TOR_DEVELOPMENT   # the path to development branch
213 
+STABLETAG = CURRENT_STABLE_TAG     # stable tag
214 
+DEVTAG = CURRENT_DEV_TAG           # dev tag
215 
+\end{verbatim}
216 
+
217 
+\subsection{build translation po files}
218 
+\begin{verbatim}
219 
+./wml2po.sh
220 
+\end{verbatim}
221 
+
222 
+This script parses the english wml and generates po files for use with pootle
223 
+\subsection{import translated pages}
224 
+\begin{verbatim}
225 
+make translations
226 
+\end{verbatim}
227 
+
228 
+This commands calls the script po2wml.sh, which converts translated po files to language-specific wml which will then build translated pages.
229 
+\subsection{build}
230 
+\begin{verbatim}
231 
+make
232 
+\end{verbatim}
233 
+\end{document}
donate/.deps/.stamp
Zeige Datei @ 2a9aaa802
donate/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1 @@
1 
+include $(WMLBASE)/Makefile.common
donate/en/become-sponsor.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,22 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Become a Sponsor" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page donate/become-sponsor>">Become a Sponsor</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+    <h1>Becoming a sponsor</h1>
13 
+  </div>
14 
+  <!-- END MAINCOL -->
15 
+  <div id = "sidecol">
16 
+#include "side.wmi"
17 
+#include "info.wmi"
18 
+  </div>
19 
+  <!-- END SIDECOL -->
20 
+</div>
21 
+<!-- END CONTENT -->
22 
+#include <foot.wmi>
donate/en/donate-hardware.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,22 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Donate to Tor" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page donate/donate-hardware>">Donate Hardware</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+    <h1>Hardware Donations</h1>
13 
+  </div>
14 
+  <!-- END MAINCOL -->
15 
+  <div id = "sidecol">
16 
+#include "side.wmi"
17 
+#include "info.wmi"
18 
+  </div>
19 
+  <!-- END SIDECOL -->
20 
+</div>
21 
+<!-- END CONTENT -->
22 
+#include <foot.wmi>
donate/en/donate-service.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,22 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Donate to Tor" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page donate/donate-service>">Donate Services</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+    <h1>Service Donations</h1>
13 
+  </div>
14 
+  <!-- END MAINCOL -->
15 
+  <div id = "sidecol">
16 
+#include "side.wmi"
17 
+#include "info.wmi"
18 
+  </div>
19 
+  <!-- END SIDECOL -->
20 
+</div>
21 
+<!-- END CONTENT -->
22 
+#include <foot.wmi>
donate/en/donate.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,125 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Donate to Tor" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page donate/donate>">Donate</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+  	<h1>Monetary Donations</h1>
13 
+    <p><strong>Your support is critical to our success.</strong> Consectetur adipiscing elit. Proin sit amet dolor justo, lacinia dapibus est. Lorem ipsum dolor sit amet, consectetur adipiscing elit. In orci est, pellentesque sit amet consequat eget, venenatis id augue. Quisque arcu velit, ultricies non porta a, dictum in lorem. Quisque pulvinar laoreet fermentum. Quisque mauris nulla, lobortis non facilisis at, lacinia in diam. Sed at enim tortor, vitae consequat elit.</p>
14 
+    <div class="title toptwenty">Donate via PayPal</div>
15 
+    <div class="left hundred">
16 
+    	<div class="paypal focus">
17 
+      	<h4>Make a recurring donation</h4>
18 
+        <form>
19 
+        	<div class="toppad">
20 
+            <input class="textfield" type="text" value="Amount" />
21 
+            <br />
22 
+            <select>
23 
+              <option selected="selected">$</option>
24 
+              <option>&euro;</option>
25 
+              <option>&pound;</option>
26 
+              <option>&yen;</option>
27 
+            </select>
28 
+            <select>
29 
+              <option selected="selected">How often?</option>
30 
+              <option>Weeks</option>
31 
+              <option>Months</option>
32 
+              <option>Years</option>
33 
+            </select>
34 
+          </div>
35 
+          <br />
36 
+      		<input class="donate-btn" type="submit" name="donate" value="Donate" />
37 
+        </form>
38 
+      </div>
39 
+      <div class="or left">OR</div>
40 
+      <div class="paypal focus">
41 
+      	<h4>Make a one-time donation</h4>
42 
+        <form>
43 
+        	<table>
44 
+          	<tr>
45 
+        			<td><input type="radio" value="10" /> $10</td>
46 
+              <td><input type="radio" value="20" /> $20</td>
47 
+              <td><input type="radio" value="50" /> $50</td>
48 
+              <td><input type="radio" value="100" /> $100</td>
49 
+            </tr>
50 
+            <tr>
51 
+              <td><input type="radio" value="250" /> $250</td>
52 
+              <td><input type="radio" value="500" /> $500</td>
53 
+              <td><input type="radio" value="1000" /> $1000</td>
54 
+              <td><input type="radio" value="other" /> Other</td>
55 
+            </tr>
56 
+          </table>
57 
+          <br />
58 
+          <input class="donate-btn right" type="submit" name="donate" value="Donate" />
59 
+          <div class="right">
60 
+            <img class="icon" src="$(IMGROOT)/icon-visa.gif" alt="Visa" />
61 
+            <img class="icon" src="$(IMGROOT)/icon-mc.gif" alt="Master Card" />
62 
+            <img class="icon" src="$(IMGROOT)/icon-ae.gif" alt="American Express" />
63 
+          </div>
64 
+        </form>
65 
+      </div>
66 
+    </div>
67 
+    <!-- END PAYPAL -->
68 
+    <div class="title topforty">Donate via Givv.org</div>
69 
+    	<div class="hundred left">
70 
+        <p>Givv.org is a new way to think about making your impact. Make one monthly donation. To as many nonprofits as you like. Automatic, one-click giving. You stay anonymous and stay in control! <strong><a href="#">Continue to Givv.org &raquo;</a></strong></p>
71 
+      </div>
72 
+			<!-- END GIVV -->
73 
+    <div class="title toptwenty">Donate via Check or Money Order</div>
74 
+    	<div class="left hundred">
75 
+      	<p>You can send checks or money orders to:</p>
76 
+				<p><strong>The Tor Project</strong><br />
77 
+        969 Main Street, Suite 206<br />
78 
+        Walpole, MA 02081</p>
79 
+      </div>
80 
+			<!-- END CHECK -->
81 
+    <div class="title toptwenty">Donate via International Bank Transfer</div>
82 
+    <div class="left hundred">
83 
+      <div class="left forty">
84 
+        <h3>Large Transfers (&gt;= $200)</h3>
85 
+        <p><strong>Official Organization Address:</strong><br />
86 
+        The Tor Project<br />
87 
+        969 Main Street, Suite 206<br />
88 
+        Walpole, MA 02081</p>
89 
+        <p>Sovereign Bank account number: 63904957725<br />
90 
+        Sovereign Bank routing number: 011075150</p>
91 
+        <p><strong>Bank Address:</strong><br />
92 
+        Sovereign Bank<br />
93 
+        1130 Berkshire Boulevard<br />
94 
+        Wyomissing, PA 19610</p>
95 
+        <p>SWIFT Code: SVRNUS33//FW011075150</p>
96 
+      </div>
97 
+      <div class="left sixty">
98 
+        <h3>Small Transfers (&lt;= $200)</h3>
99 
+        <p>Wau Holland Stiftung<br />
100 
+        IBAN DE57 5204 0021 0277 281202<br />
101 
+        SWIFT BIC COBADEFFXXX</p>
102 
+        <p><strong>Classic style German account information is:</strong><br />
103 
+        Konto: 2772812-02<br />
104 
+        Inhaber: Wau Holland Stiftung<br />
105 
+        Bank: Commerzbank Kassel<br />
106 
+        BLZ: 52040021</p>
107 
+        <p><em>For small transfers, we have an arrangement with CCC in Germany to provide tax-deductible donations for Europeans:</em></p>
108 
+        <ul>
109 
+          <li>Residents from any of the 31 SEPA[0] member states can wire up to 50.000 Euro at the cost of a domestic transaction (ie, usually free if submitted electronically).</li>
110 
+          <li>German citizens can make a charitable contribution that is tax-deductible to a certain degree (max 5% of total income, up to 1.650 Euro per annum). A new law has recently come into effect which changed this to 20% without a fixed ceiling.</li>
111 
+          <li>Corporate entities can deduct donations up to 4/1000 of their combined turnovers, wages and salaries. WHS issues a donation receipt upon request (if provided with address information).</li>
112 
+        </ul>
113 
+      </div>
114 
+    </div>
115 
+    <!-- END TRANSFER -->
116 
+  </div>
117 
+  <!-- END MAINCOL -->
118 
+  <div id = "sidecol">
119 
+#include "side.wmi"
120 
+#include "info.wmi"
121 
+  </div>
122 
+  <!-- END SIDECOL -->
123 
+</div>
124 
+<!-- END CONTENT -->
125 
+#include <foot.wmi>
donate/en/info.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+
5 
+<div class="img-shadow">
6 
+  <div class="important-infoblock">
7 
+    <h2>What Happens to my Donation?</h2>
8 
+    <img src="$(IMGROOT)/donationchart.jpg" alt="Donations Breakdown" />
9 
+    <p>If you've just donated, thank you for your donation. Your funds are deposited into our general fund. You join our many sponsors in funding the future of Tor and online anonymity. In 2008, the Tor Project spent and received its funds as the above chart depicts.</p>
10 
+  </div>
11 
+</div>
12 
+<!-- END INFOBLOCK -->
donate/en/matching-program.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,22 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Matching Program" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page donate/matching-program>">Matching Program</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+    <h1>Matching Program</h1>
13 
+  </div>
14 
+  <!-- END MAINCOL -->
15 
+  <div id = "sidecol">
16 
+#include "side.wmi"
17 
+#include "info.wmi"
18 
+  </div>
19 
+  <!-- END SIDECOL -->
20 
+</div>
21 
+<!-- END CONTENT -->
22 
+#include <foot.wmi>
donate/en/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,38 @@
1 
+#!/usr/bin/wml
2 
+
3 
+## translation metadata
4 
+# Revision: $Revision: 0 $
5 
+# Translation-Priority: 2-medium
6 
+
7 
+# this structure defines the side nav bar for the /about pages
8 
+# and is the input for include/side.wmi
9 
+
10 
+# fields:
11 
+#
12 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
13 
+# that links will point to the current language if supported, and alternately
14 
+# the english version
15 
+#
16 
+# txt - the link text to be displayed. Different translations will
17 
+# need to supply alternate txt
18 
+
19 
+<:
20 
+    my $sidenav;
21 
+    $sidenav = [
22 
+        {'url'  => 'donate/donate',
23 
+         'txt'  => 'Monetary Donations',
24 
+        },
25 
+        {'url'  => 'donate/donate-hardware',
26 
+         'txt'  => 'Hardware Donations',
27 
+        },
28 
+        {'url'  => 'donate/donate-service',
29 
+         'txt'  => 'Service Donations',
30 
+        },
31 
+        {'url'  => 'donate/matching-program',
32 
+         'txt'  => 'Matching Program',
33 
+        },
34 
+        {'url'  => 'donate/become-sponsor',
35 
+         'txt'  => 'Become a Sponsor',
36 
+        },
37 
+    ];
38 
+:>
download/.deps/.stamp
Zeige Datei @ 2a9aaa802
download/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1 @@
1 
+include $(WMLBASE)/Makefile.common
download/en/._thankyou.wml
Zeige Datei @ 2a9aaa802
download/en/download.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,210 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+#include "head.wmi" TITLE="Download Tor" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+
6 
+    <div id="content" class="clearfix">
7 
+			<div id="breadcrumbs"><a href="<page home>">Home &raquo; </a><a href="<page download/download>">Download</a></div>
8 
+    	<div id="maincol-left">
9 
+      	<h1>Download Tor</h1>
10 
+      	<div class="warning">
11 
+          <p>Tor does not magically encrypt all of your Internet activities. Understand what Tor does and does not do for you.
12 
+          <br /><a href="#">Read more »</a></p>
13 
+        </div>
14 
+        <!-- END WARNING -->
15 
+        <table class="topforty">
16 
+        	<tr>
17 
+          	<td class="nopad" colspan="4"><div class="title"><a name="wim">TorBrowser with Instant Messenger Client</a></div></td>
18 
+          </tr>
19 
+        	<tr>
20 
+          	<td class="intro" colspan="4">TorBrowser contains Tor, Vidalia, Tor-button, Polipo, Firefox, and Pidgen. This package requires the least effort installing.</td>
21 
+          </tr>
22 
+          <tr>
23 
+          	<td><span class="column-title">Language</span></td>
24 
+            <td><span class="column-title">Version</span></td>
25 
+            <td><span class="column-title">Windows</span></td>
26 
+            <td><span class="column-title">Source Code</span></td>
27 
+          </tr>
28 
+          <tr class="beige">
29 
+          	<td>English (en-US)</td>
30 
+            <td><version-torimbrowserbundle></td>
31 
+            <td><span class="windows"><a href="torbrowser/dist/tor-im-browser-<version-torimbrowserbundle>_en-US.exe">Download</a></span></td>
32 
+            <td><span class="windows"><a href="torbrowser/dist/tor-im-browser-<version-torimbrowserbundle>_en-US.tar.gz">Download Tarball</a></span></td>
33 
+          </tr>
34 
+        </table>
35 
+        <table class="topforty">
36 
+	        <tr>
37 
+          	<td class="nopad" colspan="5"><div class="title"><a name="tbb">TorBrowser Bundles</a></div></td>
38 
+          </tr>
39 
+              <tr>
40 
+                <td><span class="column-title">Language</span></td>
41 
+                <td><span class="column-title">Version</span></td>
42 
+                <td><span class="column-title">Windows</span></td>
43 
+                <td><span class="column-title">Linux</span></td>
44 
+                <td><span class="column-title">Source Code</span></td>
45 
+              </tr>
46 
+              <tr class="beige">
47 
+                <td>English (en-US)</td>
48 
+                <td><version-torbrowserbundle></td>
49 
+                <td><span class="windows"><a href="torbrowser/dist/tor-browser-<version-torbrowserbundle>_en-US.exe">Download</a></span></td>
50 
+                <td></td>
51 
+                <td><a href="#">Download Tarball</a></td>
52 
+              </tr>
53 
+              <tr>
54 
+                <td>English (en-US)</td>
55 
+                <td><version-torbrowserbundlelinux></td>
56 
+                <td></td>
57 
+                <td><span class="linux"><a href="torbrowser/dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-en-US.tar.gz">Download</a></td></span></td>
58 
+                <td><a href="#">Download Tarball</a></td>
59 
+              </tr>
60 
+          </tr>
61 
+  		</table>
62 
+        <table class="topforty">
63 
+	        <tr>
64 
+          	<td class="nopad" colspan="5"><div class="title"><a name="tor">Tor Bundles</a></div></td>
65 
+          </tr>
66 
+            <tr>
67 
+              <td><span class="column-title">Version</span></td>
68 
+              <td><span class="column-title">Windows</span></td>
69 
+              <td><span class="column-title">Mac</span></td>
70 
+              <td><span class="column-title">Linux</span></td>
71 
+              <td><span class="column-title">Source Code</span></td>
72 
+            </tr>
73 
+            <tr class="beige">
74 
+              <td><version-stable></td>
75 
+              <td><span class="windows"><a href="<package-win32-bundle-stable>">Download</a></span></td>
76 
+              <td><span class="mac"><a href="<package-osx-bundle-stable>">Download</a></span>
77 
+              <td><span class="linux"><a href="<package-source-stable>">Download</a></span></td>
78 
+              <td><a href="<package-source-stable>">Download Tarball</a></td>
79 
+          	</tr>
80 
+            <tr>
81 
+              <td><version-alpha></td>
82 
+              <td><span class="windows"><a href="<package-win32-bundle-alpha>">Download</a></span></td>
83 
+              <td><span class="mac"><a href="<package-osx-bundle-alpha>">Download</a></span>
84 
+              <td><span class="linux"><a href="<package-source-alpha>">Download</a></span></td>
85 
+              <td><a href="<package-source-alpha>">Download Tarball</a></td>
86 
+          	</tr>
87 
+        </table>
88 
+        <table class="topforty">
89 
+	        <tr>
90 
+          	<td class="nopad" colspan="4"><div class="title"><a name="smartphones">Tor for Smartphones</a></div></td>
91 
+          </tr>
92 
+          <tr>
93 
+              <td><span class="column-title">Device</span></td>
94 
+              <td><span class="column-title">Version</span></td>
95 
+              <td><span class="column-title">Download</span></td>
96 
+              <td><span class="column-title">Installation Guide</span></td>
97 
+            </tr>
98 
+            <tr class="beige">
99 
+              <td>Android</td>
100 
+              <td><span class="android"><a href="#">Download</a></span></td>
101 
+              <td>1.3.3</td>
102 
+              <td><a href="#">Android</a></td>
103 
+          	</tr>
104 
+            <tr>
105 
+              <td>iPhone</td>
106 
+              <td><span class="mac"><a href="#">Download</a></span></td>
107 
+              <td>1.3.3</td>
108 
+              <td><a href="#">iPhone</a></td>
109 
+          	</tr>
110 
+        </table>
111 
+        <table class="topforty">
112 
+	        <tr>
113 
+          	<td class="nopad" colspan="4"><div class="title"><a name="expert">Expert Packages</a></div></td>
114 
+          </tr>
115 
+          		<tr>
116 
+                <td><span class="column-title">Operating System</span></td>
117 
+                <td><span class="column-title">Notes</span></td>
118 
+                <td><span class="column-title">Stable</span></td>
119 
+                <td><span class="column-title">Unstable</span></td>
120 
+                <td><span class="column-title">Installation Guide</span></td>
121 
+              </tr>
122 
+              <tr class="beige">
123 
+                <td><span class="windows">Windows</span></td>
124 
+                <td>Windows 7, Vista, XP, 2000, 2003 Server</td>
125 
+                <td><a href="#">1.3.4</a></td>
126 
+                <td><a href="#">1.3.6</a></td>
127 
+                <td><a href="#">Windows</a></td>
128 
+              </tr>
129 
+              <tr>
130 
+                <td><span class="mac">Mac (Intel)</span></td>
131 
+                <td>Intel only</td>
132 
+                <td><a href="#">1.3.4</a></td>
133 
+                <td><a href="#">1.3.6</a></td>
134 
+                <td><a href="#">Mac (Intel)</a></td>
135 
+              </tr>
136 
+              <tr class="beige">
137 
+                <td><span class="mac">Mac (Power PC)</span></td>
138 
+                <td>Intel only</td>
139 
+                <td><a href="#">1.3.4</a></td>
140 
+                <td><a href="#">1.3.6</a></td>
141 
+                <td><a href="#">Mac (Power PC)</a></td>
142 
+              </tr>
143 
+              <tr>
144 
+                <td><span class="linux">Linux/Unix</span></td>
145 
+                <td>Redhat/CentOS, Fedora, Debian, Ubuntu, SUSE</td>
146 
+                <td><a href="#">1.3.4</a></td>
147 
+                <td><a href="#">1.3.6</a></td>
148 
+                <td><a href="#">Linux/Unix</a></td>
149 
+              </tr>
150 
+              <tr class="beige">
151 
+                <td>Source Tarballs</td>
152 
+                <td>./configure && make && src/or/tor  </td>
153 
+                <td><a href="#">1.3.4</a></td>
154 
+                <td>&nbsp;</td>
155 
+                <td><a href="#">Source Tarballs</a></td>
156 
+              </tr>
157 
+        </table>
158 
+      </div>
159 
+      <!-- END MAINCOL -->
160 
+      <div id="sidecol-right">
161 
+        <div class="img-shadow">
162 
+        	<div class="sidenav-sub">
163 
+          	<h2>Jump to:</h2>
164 
+          	<ul>
165 
+            	<li class="dropdown"><a href="#wim">TorBrowser with Instant Messenger Client</a></li>
166 
+            	<li class="dropdown"><a href="#tbb">TorBrowser Bundles</a></li>
167 
+            	<li class="dropdown"><a href="#tor">Tor Bundles</a></li>
168 
+            	<li class="dropdown"><a href="#smartphones">Tor for Smartphones</a></li>
169 
+            	<li class="dropdown"><a href="#expert">Expert Packages</a></li>
170 
+            </ul>
171 
+          </div>
172 
+      	</div>
173 
+        <!-- END SIDENAV -->
174 
+        <div class="img-shadow">
175 
+          <div class="infoblock">
176 
+          	<h2>Verify Signatures</h2>
177 
+            <p>Blurb about why you should verify the signatures before you download software off the internet.</p>
178 
+						<p><a href="#">Tor Bundle for Windows</a><br />
179 
+					    <a href="#">TorBrowser Bundle for Windows</a><br />
180 
+				      <a href="#">Tor Bundle for Mac</a><br />
181 
+			        <a href="#">Tor Bundle for Linux/Unix</a></p>
182 
+          </div>
183 
+        </div>
184 
+        <!-- END INFOBLOCK -->
185 
+        <div class="img-shadow">
186 
+        	<div class="sidenav-sub">
187 
+          	<h2>Having Trouble?</h2>
188 
+          	<ul>
189 
+            	<li class="dropdown"><a href="#">What are the differences between stable and unstable downloads?</a></li>
190 
+            	<li class="dropdown"><a href="#">Why is the TorBrowser Bundle only available for Windows?</a></li>
191 
+            	<li class="dropdown"><a href="#">What is the Expert Developer Package?</a></li>
192 
+            	<li class="dropdown"><a href="#">What are the differences between stable and unstable downloads?</a></li>
193 
+            	<li class="dropdown"><a href="#">Why is the TorBrowser Bundle only available for Windows?</a></li>
194 
+            	<li class="dropdown"><a href="#">What is the Expert Developer Package?</a></li>
195 
+            </ul>
196 
+          </div>
197 
+      	</div>
198 
+        <!-- END SIDENAV -->
199 
+        <div class="img-shadow">
200 
+        	<div class="infoblock">
201 
+          	<h2>Disclaimers</h2>
202 
+            <p>Blurb about how Tor wants to do right by its users, and list of things user should be aware of, like how if they download the TorBrowser and then use Internet Explorer, that they are not being adequately protected. You can use this space to advocate for knowledge about online security to augment Tor.</p>
203 
+          </div>
204 
+        </div>
205 
+      </div>
206 
+      <!-- END SIDECOL -->
207 
+    </div>
208 
+    <!-- END CONTENT -->
209 
+
210 
+#include <foot.wmi>
download/en/easy-download.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,95 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21396 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor: Download" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+
7 
+<div class="main-column">
8 
+
9 
+<h3>Download Now - Free &amp; Open Source Software</h3>
10 
+<hr />
11 
+<table width="99%" border="0" cellspacing="0" cellpadding="3">
12 
+<tr>
13 
+<th bgcolor="#e5e5e5" align="center" width="25%"><img src="$(IMGROOT)/logo.windows-header.gif"/></th>
14 
+<th align="center" width="25%"><img src="$(IMGROOT)/ref_leopard_box.jpg"/></th>
15 
+<th bgcolor="#e5e5e5" align="center" width="25%"><img src="$(IMGROOT)/logo.windows-header.gif"/></th>
16 
+<th align="center" width="25%"><img src="$(IMGROOT)/distros/generic.png"/><img src="$(IMGROOT)/distros/freebsd.png"/><img src="$(IMGROOT)/distros/package.png"/><img src="$(IMGROOT)/distros/src.png"/></th>
17 
+</tr>
18 
+<tr>
19 
+<td bgcolor="#e5e5e5" align="center">
20 
+# Translators: please point to the version of TBB in your language,
21 
+# if there is one.
22 
+<a href="torbrowser/dist/tor-browser-<version-torbrowserbundle>_en-US.exe">Tor Browser Bundle for Windows</a>
23 
+</td>
24 
+<td align="center">
25 
+<a href="<package-osx-bundle-stable>">Installation Bundle for Apple OS X</a>
26 
+</td>
27 
+<td bgcolor="#e5e5e5" align="center">
28 
+<a href="<package-win32-bundle-stable>">Installation Bundle for
29 
+Windows</a>
30 
+</td>
31 
+</tr>
32 
+<tr>
33 
+<td bgcolor="#e5e5e5" align="center">Zero installation.  Great for USB
34 
+drives! Pre-configured with Firefox and more. <a href="<page
35 
+projects/torbrowser>">More details and languages</a>.</td>
36 
+<td align="center">Simple.  Drag and Drop Install. i386-only.  <a href="<page
37 
+download/download>">PowerPC? Go here.</a></td>
38 
+<td bgcolor="#e5e5e5" align="center">Easy to Install.</td>
39 
+<td align="center">
40 
+<a href="<page download/download>">Linux/BSD/Unix/Source</a>
41 
+</td>
42 
+</tr>
43 
+</table>
44 
+
45 
+<div class="underline"></div>
46 
+<div class="warning">
47 
+Tor does <strong>not</strong> magically encrypt all of your Internet activities.
48 
+Understand what Tor does and does not do for you. <a href="<page
49 
+download/download>#Warning">Read more about this topic</a>.
50 
+</div>
51 
+
52 
+<div class="underline"></div>
53 
+<div class="nb">
54 
+<p>Need more download options?  <a href="<page download/download>">See advanced choices</a>.</p>
55 
+</div>
56 
+
57 
+<div class="underline"></div>
58 
+<div class="nb">
59 
+<p>Verify the signatures for the downloads above (<a href="<page docs/verifying-signatures>">How?</a>):</p>
60 
+  <ul>
61 
+    <li><a href="torbrowser/dist/tor-browser-<version-torbrowserbundle>_en-US.exe.asc">Tor Browser Bundle for Windows signature</a></li>
62 
+    <li><a href="<package-win32-bundle-stable-sig>">Installation Bundle for Windows signature</a></li>
63 
+    <li><a href="<package-osx-bundle-stable-sig>">Installation Bundle for OS X signature</a></li>
64 
+  </ul>
65 
+</div>
66 
+
67 
+<div class="underline"></div>
68 
+<div class="nb">
69 
+<p>Interested in <a href="<page about/overview>">learning more about Tor in general</a>?</p>
70 
+</div>
71 
+
72 
+<div class="underline"></div>
73 
+<div class="nb">
74 
+<p>
75 
+To keep informed of security advisories and new stable releases, subscribe
76 
+to the <a href="http://archives.seul.org/or/announce/">or-announce
77 
+mailing list</a> (you will be asked to confirm via email). You can also
78 
+<a href="http://rss.gmane.org/gmane.network.onion-routing.announce">watch
79 
+the list's RSS feed</a>.
80 
+</p>
81 
+
82 
+<form action="http://freehaven.net/cgi-bin/majordomo.cgi">
83 
+<input type="hidden" name="mlist" value="or-announce"/>
84 
+<input type="hidden" name="subscribe" value="1"/>
85 
+<input type="hidden" name="host" value="freehaven.net"/>
86 
+<input name="email" size="15"/>
87 
+<input type="submit" value="subscribe to or-announce"/>
88 
+</form>
89 
+</div>
90 
+
91 
+<p>All trademarks are the property of their respective owners.</p>
92 
+</div><!-- #main -->
93 
+
94 
+#include <foot.wmi>
95 
+
download/en/thankyou.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,78 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+#include "head.wmi" TITLE="Thank you for downloading Tor" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+    <div id="content" class="clearfix">
6 
+			<div id="breadcrumbs">
7 
+        <a href="<page home>">Home &raquo; </a>
8 
+        <a href="<page download/download>">Download &raquo; </a>
9 
+        <a href="<page download/thankyou>">Thank You</a>
10 
+      </div>
11 
+
12 
+      <h1>Thank you for downloading Tor!</h1>
13 
+      <p><strong>Your download should begin automatically in a few seconds, but if not,you can download with our <a href="#">direct link</a>.</strong></p>
14 
+    	<div id="maincol-left">
15 
+      	<div class="focus clearfix">
16 
+        	<h2>Installation Instructions for Mac OS X</h2>
17 
+            	<div class="fakeol">1. </div>
18 
+            	<div class="instructions">Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed lorem velit, faucibus non suscipit sit amet, iaculis sed lorem. Morbi nec nulla id felis dictum porta ut a lacus. Nunc vel est ut nisl tincidunt fermentum nec nec quam. In hac habitasse platea dictumst. Aliquam sagittis bibendum rhoncus.</div>
19 
+            	<div class="fakeol">2. </div>
20 
+            	<div class="instructions">Quisque tincidunt neque condimentum mauris suscipit posuere. Nullam ac nisl metus. Nunc vel est ut nisl tincidunt fermentum nec nec quam. In hac habitasse platea dictumst. Aliquam sagittis bibendum rhoncus.</div>
21 
+            	<div class="fakeol">3. </div>
22 
+              <div class="instructions">Aliquam sagittis bibendum rhoncus. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Sed lorem velit, faucibus non suscipit sit amet, iaculis sed lorem. Morbi nec nulla id felis dictum porta ut a lacus. Cras egestas lorem vitae arcu ullamcorper ut porttitor metus suscipit.</div>
23 
+          <p class="continue"><a href="<page docs/tor-doc-osx>">Read the full instructions &raquo;</a></p>
24 
+        </div>
25 
+        <div class="toptwenty">
26 
+          <div class="img-shadow">
27 
+        	<div class="sidenav-sub">
28 
+          	<h2>Need Help?</h2>
29 
+          	<ul>
30 
+            	<li class="dropdown"><a href="<page docs/installguide>">Read the Installation Guide</a></li>
31 
+            	<li class="dropdown"><a href="<page docs/faq>">Check out the FAQ</a></li>
32 
+            	<li class="dropdown"><a href="http://wiki.torproject.org">Read the Tor Wiki</a></li>
33 
+            	<li class="dropdown"><a href="#">Email our Techincal Support</a></li>
34 
+            </ul>
35 
+          </div>
36 
+      	</div>
37 
+        <!-- END SIDENAV -->
38 
+        <div class="right">
39 
+          <div class="img-shadow">
40 
+            <div class="custom-infoblock">
41 
+              <h2>Is Your Installation Working?</h2>
42 
+              <img class="project-icon" src="$(IMGROOT)/icon-default.jpg" alt="Default Icon" />
43 
+              <h4>Use TorCheck to test your Install</h4>
44 
+              <p>Visit <a href="http://check.torproject.org">check.torproject.org</a> to see if your install is working, and you’re being protected by the Tor onion router.</p>
45 
+            </div>
46 
+          </div>
47 
+        </div>
48 
+        </div>
49 
+      </div>
50 
+      <!-- END MAINCOL -->
51 
+      <div id="sidecol-right">
52 
+        <div class="img-shadow">
53 
+          <div class="infoblock clearfix">
54 
+          	<h2>Help Tor by Running a Relay</h2>
55 
+            <p>We’re trying to reach 5,000 relays by 2011. Help support the Tor Project by <a href="<page docs/tor-doc-relay>">running your own</a>! It’s free and easy!</p>
56 
+            <div class="fifty left toptwenty">
57 
+            	<p class="small"><em>Current</em></p>
58 
+              <p class="current-relay">3,542</p>
59 
+            </div>
60 
+            <div class="fifty left toptwenty">
61 
+            	<p class="small"><em>Target</em></p>
62 
+              <p class="target-relay">5,000</p>
63 
+            </div>
64 
+          </div>
65 
+        </div>
66 
+        <!-- END INFOBLOCK -->
67 
+        <div class="img-shadow">
68 
+          <div class="infoblock">
69 
+          	<h2 class="bulb">Tor Tip</h2>
70 
+            <p>If you take a step towards online privacy by downloading Tor, that’s great, but remember that Tor can only be effective if you use the programs it’s developed for!</p>
71 
+           </div>
72 
+        </div>
73 
+        <!-- END INFOBLOCK -->
74 
+      </div>
75 
+      <!-- END SIDECOL -->
76 
+    </div>
77 
+    <!-- END CONTENT -->
78 
+#include <foot.wmi>
eff/.deps/.stamp
Zeige Datei @ 2a9aaa802
eff/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1 @@
1 
+include $(WMLBASE)/Makefile.common
eff/en/tor-dmca-response.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,130 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 12419 $
3 
+
4 
+#include "head.wmi" TITLE="Response template for Tor relay operator to ISP"
5 
+
6 
+<div class="main-column">
7 
+
8 
+<!-- PUT CONTENT AFTER THIS TAG -->
9 
+
10 
+<h2>Response template for Tor relay maintainer to ISP</h2>
11 
+<hr />
12 
+<p>Written by the Electronic Frontier
13 
+Foundation (<a href="http://www.eff.org/">EFF</a>). Last updated 19 Feb 2005.</p>
14 
+
15 
+<p>Note to Tor relay operators:   In this litigous era, anyone
16 
+providing routing services may face copyright complaints under the
17 
+Digital Millennium Copyright Act. Thankfully, the DMCA safe harbors
18 
+provide immunity from many of them -- both to you and to your
19 
+upstream provider.  If your Internet host forwards a DMCA complaint
20 
+to you, here's a template you can use to write a response.  You can
21 
+tailor this to your own circumstances: if you think your host would
22 
+be disturbed to hear you're running a relay on the network, you may
23 
+want to take that part out.  Of course it's up to you to comply with
24 
+your ISP's terms of service.  If you're not comfortable including so
25 
+much legal explanation, feel free to invite the ISP to contact EFF
26 
+for a fuller discussion.</p>
27 
+
28 
+<p>This template letter is for informational purposes only and does not
29 
+constitute legal advice. Whether and how you should respond when you or
30 
+your ISP has received a DMCA notice will turn on the particular facts
31 
+of your situation. This template is intended as a starting point. Before
32 
+sending any response to your ISP, you may want to seek the advice of an
33 
+attorney licensed to practice in your jurisdiction.</p>
34 
+
35 
+<p>Also, if you received this document from anywhere besides <a
36 
+href="https://torproject.org/eff/tor-dmca-response.html">https://www.torproject.org/eff/tor-dmca-response.html</a>,
37 
+it may be out of date. Follow the link to get the latest version.</p>
38 
+
39 
+<hr />
40 
+
41 
+<p>Dear [ISP]:</p>
42 
+
43 
+<p>Thank you for forwarding me the notice you received from [copyright
44 
+claimant] regarding [content].  I would like to assure you that,
45 
+contrary to the assertions in the notice, 1) I am not hosting or
46 
+making available the claimed infringing materials, and 2) you are
47 
+already protected by the Digital Millennium Copyright Act's ("DMCA")
48 
+safe harbor from any liability arising from this complaint.   The
49 
+notice is incorrect, probably based upon misunderstandings about law
50 
+and about some of the software I run.
51 
+</p>
52 
+
53 
+<p>
54 
+First, in terms of legal liability, this notice does not create any
55 
+risk for you as a service provider.  As you know, the DMCA creates
56 
+four "safe harbors" for service providers to protect them from
57 
+copyright liability for the acts of their users, when the ISPs
58 
+fulfill certain requirements. (17 U.S.C. � 512)   The DMCA's
59 
+requirements vary depending on the ISP's role.  You may be most
60 
+familiar with the "notice and takedown" provisions of DMCA 512(c),
61 
+but those apply only to content hosted on your servers, or to linking
62 
+and caching activity. The "takedown notice" provisions do not apply
63 
+when an ISP merely acts as a conduit.  Instead, the "conduit" safe
64 
+harbor of DMCA 512(a) has different and less burdensome requirements,
65 
+as the D.C. Circuit Court of Appeals held in RIAA v. Verizon (see
66 
+<a href="http://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf">http://www.eff.org/legal/cases/RIAA_v_Verizon/opinion-20031219.pdf</a>)
67 
+and the Eighth Circuit Court of Appeals confirmed in RIAA v. Charter
68 
+(see <a href="http://www.eff.org/IP/P2P/Charter/033802P.pdf">http://www.eff.org/IP/P2P/Charter/033802P.pdf</a>).
69 
+</p>
70 
+
71 
+<p>
72 
+Here, any content that came from or through my computers merely
73 
+passed through your network, so DMCA 512(a) applies.  Under DMCA
74 
+512(a), you are immune from money damages for copyright infringement
75 
+claims if you maintain "a policy that provides for termination in
76 
+appropriate circumstances of subscribers and account holders of the
77 
+service provider's system or network who are repeat infringers."  If
78 
+you have and implement such a policy, you are free from fear of
79 
+copyright damages, period.
80 
+</p>
81 
+
82 
+<p>
83 
+As for what makes a reasonable policy, as the law says, it's one that
84 
+only terminates subscribers who are repeat infringers. A notice
85 
+claiming infringement is not the same as a determination of
86 
+infringement. The notification you received is not proof of any
87 
+copyright infringement, and it certainly is not proof of the "repeat
88 
+infringement" that is required under the law before you need to
89 
+terminate my account.  I have not infringed any copyrights and do not
90 
+intend to do so.  Therefore, you continue to be protected under the
91 
+DMCA 512(a) safe harbor, without taking any further action.
92 
+</p>
93 
+
94 
+<p>
95 
+You might be curious, though, about what did trigger the notice.  The
96 
+software that likely triggered the faulty notice is a program I run
97 
+called Tor.  Tor is network software that helps users to enhance
98 
+their privacy, security, and safety online. It does not host or make
99 
+available any content.  Rather, it is part of a network of nodes on
100 
+the Internet that simply pass packets among themselves before sending
101 
+them to their destinations, just as any Internet host does.  The
102 
+difference is that Tor tunnels the connections such that no hop can
103 
+learn both the source and destination of the packets, giving users
104 
+protection from nefarious snooping on network traffic.  Tor protects
105 
+users against hazards such as harassment, spam, and identity theft.
106 
+In fact, initial development of Tor, including deployment of a
107 
+public-use Tor network, was a project of the U.S. Naval Research
108 
+Laboratory, with funding from ONR and DARPA. (For more on Tor,
109 
+see <a
110 
+href="https://www.torproject.org/">https://www.torproject.org/</a>.)
111 
+As an organization committed to
112 
+protecting the privacy of its customers, I hope you'll agree that
113 
+this is a valuable technology.
114 
+</p>
115 
+
116 
+<p>
117 
+Thank you for working with me on this matter.  As a loyal subscriber,
118 
+I appreciate your notifying me of this issue and hope that the
119 
+complete protections of DMCA 512 put any concerns you may have at
120 
+rest. If not, please contact me with any further questions.
121 
+</p>
122 
+
123 
+<p>
124 
+Very truly yours,<br />
125 
+Your customer, [User]
126 
+</p>
127 
+
128 
+</div><!-- #main -->
129 
+
130 
+#include <foot.wmi>
eff/en/tor-legal-faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,233 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 13015 $
3 
+
4 
+#include "head.wmi" TITLE="Legal FAQ for Tor Relay Operators"
5 
+
6 
+<div class="main-column">
7 
+
8 
+<!-- PUT CONTENT AFTER THIS TAG -->
9 
+
10 
+<h2>Legal FAQ for Tor Relay Operators</h2>
11 
+<hr />
12 
+<p>FAQ written by the Electronic Frontier
13 
+Foundation (<a href="http://www.eff.org/">EFF</a>). Last updated 25 Apr 2005.</p>
14 
+
15 
+<p><strong>NOTE:</strong> This FAQ is for informational purposes only
16 
+and does not constitute legal advice.  EFF has not analyzed any
17 
+particular factual situation or laws in drafting this FAQ. Our aim is
18 
+to provide a general description of the legal issues surrounding
19 
+Tor in the United States.  Different factual situations and different legal
20 
+jurisdictions will
21 
+result in different answers to a number of questions.  Therefore, please
22 
+do not act on this information alone; if you have any
23 
+specific legal problems, issues, or questions, seek a complete review of
24 
+your situation with a lawyer licensed to practice in your jurisdiction.
25 
+</p>
26 
+
27 
+<p>Also, if you received this document from anywhere besides <a
28 
+href="https://www.torproject.org/eff/tor-legal-faq.html">https://www.torproject.org/eff/tor-legal-faq.html</a>,
29 
+it may be out of date. Follow the link to get the latest version.</p>
30 
+
31 
+<hr />
32 
+
33 
+<a id="Lawsuits"></a>
34 
+<h3><a class="anchor" href="#Lawsuits">Has anyone ever been sued for running Tor?
35 
+</a></h3>
36 
+
37 
+<p><strong>No.</strong> Further, we believe that running a Tor node,
38 
+including a Tor exit node that allows people to anonymously send and
39 
+receive traffic, is lawful under U.S. law.</p>
40 
+
41 
+<a id="IllegalPurposes"></a>
42 
+<h3><a class="anchor" href="#IllegalPurposes">Should I use Tor,
43 
+or encourage the use of Tor, for illegal purposes
44 
+such as spamming, harassment, distribution of child porn, or copyright
45 
+infringement?</a></h3>
46 
+
47 
+<p><strong>No.</strong> Tor has been developed to be a tool for free
48 
+speech, privacy, and human rights.  It is not a tool designed or intended
49 
+to be used to break the law, either by Tor users or Tor relay
50 
+operators.</p>
51 
+
52 
+<p>We further recommend that you not keep any potentially illegal files
53 
+on the same machine you use for Tor, nor use that machine for any illegal
54 
+purpose.  Although no Tor relay in the US has ever been seized, nor any relay
55 
+operator sued, the future possibility cannot be ruled out. If that
56 
+happens, you will want your machine to be clean.</p>
57 
+
58 
+<a id="Promise"></a>
59 
+<h3><a class="anchor" href="#Promise">Can EFF promise that I won't get
60 
+in trouble for running a Tor relay?</a></h3>
61 
+
62 
+<p><strong>No.</strong> All new technologies create legal uncertainties,
63 
+and Tor is no exception to the rule. Presently, no court has ever considered any
64 
+case involving the Tor technology, and we therefore cannot guarantee
65 
+that you will never face any legal liability as a result of running a
66 
+Tor relay. However, EFF believes so strongly that those running Tor
67 
+relays shouldn't be liable for traffic that passes through the relay
68 
+that we're running our own Tor relay.
69 
+</p>
70 
+
71 
+<a id="Represent"></a>
72 
+<h3><a class="anchor" href="#Represent">Will EFF represent me if I get
73 
+in trouble for running a Tor relay?</a></h3>
74 
+
75 
+<p><strong>Maybe.</strong> While EFF cannot promise legal representation
76 
+of all Tor relay operators, it will assist relay operators in
77 
+assessing the situation and will try to locate qualified legal counsel
78 
+when necessary.  Inquiries to EFF for the purpose of securing legal
79 
+representation or referrals should be directed to staff attorney Kevin
80 
+Bankston (bankston at eff.org or US +1 (415) 436-9333 x 126). Such
81 
+inquiries will be kept
82 
+confidential subject to the limits of the attorney/client privilege.
83 
+Note that although EFF cannot practice law outside of the U.S., it will
84 
+still try to assist non-U.S. relay operators in finding local
85 
+representation.</p>
86 
+
87 
+<a id="DevelopersAreNotLawyers"></a>
88 
+<h3><a class="anchor" href="#DevelopersAreNotLawyers">Should I contact
89 
+the Tor developers when I have legal questions about Tor or to inform
90 
+them if I suspect Tor is being used for illegal purposes?</a></h3>
91 
+
92 
+<p><strong>No.</strong> Tor's core developers, Roger Dingledine
93 
+and Nick Mathewson, are available to answer technical questions, but
94 
+they are not lawyers and cannot give legal advice.  Nor do they have any
95 
+ability to prevent illegal activity that may occur through Tor relays.
96 
+Furthermore, your communications with Tor's core developers are
97 
+not protected by any legal privilege, so law enforcement or civil
98 
+litigants could subpoena and obtain any information you give to
99 
+them.</p>
100 
+
101 
+<a id="RequestForLogs"></a>
102 
+<h3><a class="anchor" href="#RequestForLogs">If I receive a request from
103 
+law enforcement or anyone else for my Tor relay's logs, what should
104 
+I do?</a></h3>
105 
+
106 
+<p><strong>Educate them about Tor.</strong> In most instances, properly
107 
+configured Tor relays will have no useful data for inquiring parties,
108 
+and you should feel free to educate them on this point.  To the extent
109 
+you do maintain logs, however, you should not disclose them to any third
110 
+party without first consulting a lawyer.  In the U.S., such a disclosure
111 
+may violate the Electronic Communications Privacy Act, and relay
112 
+operators outside of the U.S. may be subject to similar data protection
113 
+laws.</p>
114 
+
115 
+<p>You may receive legal inquiries where you are prohibited by law from
116 
+telling anyone about the request.  We believe that, at least in the
117 
+U.S., such gag orders do not prevent you from talking to a lawyer,
118 
+including calling a lawyer to find representation.  Inquiries to EFF for
119 
+the purpose of securing legal representation should be directed to staff
120 
+attorney Kevin Bankston (bankston at eff.org or US +1 (415) 436-9333
121 
+x126). Such inquiries
122 
+will be kept confidential subject to the limits of the attorney/client
123 
+privilege.</p>
124 
+
125 
+<p>EFF is currently working on informational materials to help you
126 
+respond to the most likely types of legal requests or notices, so watch
127 
+this space.</p>
128 
+
129 
+<a id="DMCA"></a>
130 
+<h3><a class="anchor" href="#DMCA">My ISP/University/etc just sent me
131 
+a DMCA notice. What should I do?</a></h3>
132 
+
133 
+<p>The EFF has written a <a
134 
+href="tor-dmca-response.html">short template</a>
135 
+to help you write a response to your ISP/University/etc, to let them
136 
+know about the details of DMCA safe harbor, and how Tor fits in. Note
137 
+that this only refers to a U.S. jurisdiction.</p>
138 
+
139 
+<p>If you like, you should consider submitting a copy of your notice
140 
+to <a href="http://www.chillingeffects.org/">Chilling Effects</a>. This
141 
+will help us recognize trends and issues that the lawyers might want to
142 
+focus on. Chilling Effects encourages submissions from people outside
143 
+the United States too.</p>
144 
+
145 
+<p>EFF is actively seeking Tor relay operators willing to stand up
146 
+and help set a clear legal precedent establishing that merely running
147 
+a node does not create copyright liability for either node operators
148 
+or their bandwidth providers. If you want to be the EFF's test case,
149 
+<a href="http://archives.seul.org/or/talk/Oct-2005/msg00208.html">read
150 
+more here</a>.</p>
151 
+
152 
+<a id="ExitSnooping"></a>
153 
+<h3><a class="anchor" href="#ExitSnooping">Should I snoop on the plaintext
154 
+that exits through my Tor relay?</a></h3>
155 
+
156 
+<p><strong>No.</strong> You may be technically capable of modifying
157 
+the Tor source code or installing additional software to monitor
158 
+or log plaintext that exits your node. However,
159 
+Tor relay operators in the U.S. can create legal and possibly even
160 
+criminal liability for themselves under state or federal wiretap laws if
161 
+they affirmatively monitor, log, or disclose Tor users'
162 
+communications, while non-U.S. operators may be subject to similar laws.
163 
+Do not examine the contents of anyone's communications without
164 
+first talking to a lawyer.</p>
165 
+
166 
+<a id="DirectoryWarranty"></a>
167 
+<h3><a class="anchor" href="#DirectoryWarranty">Do Tor's core developers
168 
+make any promises about the trustworthiness or reliability of Tor relays
169 
+that are listed in their directory?</a></h3>
170 
+
171 
+<p><strong>No.</strong> Although the developers attempt to verify that
172 
+Tor relays listed in the directory the core developers maintain are
173 
+stable and have adequate bandwidth, neither they nor EFF can guarantee
174 
+the personal trustworthiness or reliability of the individuals who run
175 
+those relays.  Tor's core developers further reserve the right to
176 
+refuse a Tor relay operator's request to be listed in their
177 
+directory or to remove any relay from their directory for any
178 
+reason.</p>
179 
+
180 
+<a id="License"></a>
181 
+<h3><a class="anchor" href="#License">Is the Tor software subject to
182 
+any license terms?</a></h3>
183 
+
184 
+<p><strong>Yes.</strong> The Tor software is distributed under the
185 
+Modified BSD license, and is reproduced below.  The Vidalia software is distributed under
186 
+the GPL v2.  Privoxy is distributed under the GPL v2.
187 
+"src/common/strlcat.c and src/common/strlcpy.c" by Todd C. Miller are
188 
+licensed under the Modified BSD license. </p>
189 
+
190 
+<p>If you have Tor as a static binary with OpenSSL included, then you
191 
+should know: "This product includes software developed by the OpenSSL Project
192 
+ for use in the OpenSSL Toolkit (http://www.openssl.org/)"</p>
193 
+
194 
+<p>The Tor software license is the Modified BSD, which is as follows:</p>
195 
+<p>Copyright &copy 2001-2004, Roger Dingledine<br />
196 
+Copyright &copy; 2004-2007, Roger Dingledine, Nick Mathewson<br />
197 
+Copyright &copy; 2007-2008 The Tor Project, Inc.</p>
198 
+
199 
+<p>Redistribution and use in source and binary forms, with or without
200 
+modification, are permitted provided that the following conditions are
201 
+met:</p>
202 
+
203 
+<ul>
204 
+
205 
+<li>Redistributions of source code must retain the above copyright
206 
+notice, this list of conditions and the following disclaimer.</li>
207 
+
208 
+<li>Redistributions in binary form must reproduce the above copyright
209 
+notice, this list of conditions and the following disclaimer in the
210 
+documentation and/or other materials provided with the
211 
+distribution.</li>
212 
+
213 
+<li>Neither the names of the copyright owners nor the names of its
214 
+contributors may be used to endorse or promote products derived from
215 
+this software without specific prior written permission.</li>
216 
+
217 
+</ul>
218 
+
219 
+<p>THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
220 
+"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
221 
+BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND
222 
+FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
223 
+COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT,
224 
+INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
225 
+NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
226 
+USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
227 
+ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
228 
+(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
229 
+THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.</p>
230 
+
231 
+</div><!-- #main -->
232 
+
233 
+#include <foot.wmi>
en/._home.wml
Zeige Datei @ 2a9aaa802
en/foot.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,110 @@
1 
+#!/usr/bin/env wml
2 
+    <div id="footer">
3 
+    	<div class="onion"><img src="$(IMGROOT)/onion.jpg" alt="Tor" /></div>
4 
+      <div class="about">
5 
+      	<p>"Tor" and the "Onion Logo" are registered trademarks of <a href="#">The Tor Project, Inc.</a> Content on this site is licensed under a <a href="#">Creative Commons Attribution 3.0 United States License</a>, unless otherwise noted.</p>
6 
+        # This will grab the date from svn info but formatting is tedious
7 
+       	# REQUIRES svn for this to work
8 
+        <:{
9 
+          my $svninfo = `svn info`;
10 
+          if ($svninfo =~ m/Last Changed Date: (\d{4}-\d{2}-\d{2})\s(\d{2}:\d{2}:\d{2})\s(.*)\s\((.*)\)/) {
11 
+            my $modifydate = "$4 $2 $3";
12 
+            # remove commas from date
13 
+            $modifydate =~ s/,//;
14 
+            print 'Last modified: '.$modifydate."\n";
15 
+          }
16 
+        }:>
17 
+        <br />
18 
+        <:{
19 
+          #my $compiledate = `date`;
20 
+          my $compiledate = `date +"%a %b %d %Y %k:%M:%S %z"`;
21 
+          print 'Last compiled: '.$compiledate."\n";
22 
+        }:>
23 
+        </p>
24 
+      </div>
25 
+      <!-- END ABOUT -->
26 
+      <div class="newsletter">
27 
+        <form action="">
28 
+          <input class="textfield" type="text" name="email" value="Sign up for our newsletter! Enter email." onClick="clearDefault(this);" />
29 
+          <input class="signup" type="submit" name="submit" value="Sign Up" />
30 
+        </form>
31 
+      </div>
32 
+      <!-- END NEWSLETTER -->
33 
+      <div class="col first">
34 
+      	<h4>About Tor</h4>
35 
+        <ul>
36 
+          <li><a href="<page about/about>">What Tor Does</a></li>
37 
+          <li><a href="<page about/torusers>">Users of Tor</a></li>
38 
+          <li><a href="<page about/corepeople>">Core Tor People</a></li>
39 
+          <li><a href="<page about/sponsors>">Sponsors</a></li>
40 
+          <li><a href="<page about/contact>">Contact Us</a></li>
41 
+        </ul>
42 
+      </div>
43 
+      <!-- END COL -->
44 
+      <div class="col">
45 
+      	<h4>Get Involved</h4>
46 
+        <ul>
47 
+          <li><a href="<page donate/donate>">Donate</a></li>
48 
+          <li><a href="<page getinvolved/getinvolved>">Mailing List</a></li>
49 
+          <li><a href="#">Relays</a></li>
50 
+          <li><a href="<page docs/running-a-mirror>">Mirrors</a></li>
51 
+          <li><a href="<page docs/hidden-services>">Hidden Services</a></li>
52 
+          <li><a href="<page getinvolved/translation>">Translations</a></li>
53 
+          <li><a href="<page getinvolved/open-positions>">Careers</a></li>
54 
+        </ul>
55 
+      </div>
56 
+      <!-- END COL -->
57 
+      <div class="col">
58 
+      	<h4>Documentation</h4>
59 
+        <ul>
60 
+          <li><a href="<page docs/tor-manual>">Manuals</a></li>
61 
+          <li><a href="<page docs/documentation>">Installation Guides</a></li>
62 
+          <li><a href="<page docs/glossary>">Glossary</a></li>
63 
+          <li><a href="http://wiki.torproject.org">Tor Wiki</a></li>
64 
+          <li><a href="<page docs/faq>">FAQ</a></li>
65 
+        </ul>
66 
+      </div>
67 
+      <!-- END COL -->
68 
+      <div class="col wider">
69 
+      	<h4>Languages</h4>
70 
+        # this is a cgi trampoline to bounce us to the right page
71 
+        # alternately, if the client supports javascript we can redirect that way
72 
+        # noscript does not block onclick but clients may have disabled javascript completely
73 
+        #
74 
+        # for this to work we need to know the relative path from the document root
75 
+        # to the current directory that wml is in.
76 
+        <form action="$(DOCROOT)/cgi-bin/languageswitch.cgi">
77 
+          <select name="Language" id="lang">
78 
+          <:{
79 
+            #import "perl-globals.wmi";
80 
+            use Cwd;
81 
+            use Cwd 'abs_path';
82 
+            use File::Spec;
83 
+            my $urlbase = File::Spec->abs2rel(getcwd(),abs_path("$(DOCROOT)"));
84 
+            my $LANGUAGES;
85 
+            my $page = $WML_SRC_FILENAME;
86 
+            opendir(DIR, getcwd()) or die $!;
87 
+            # take a look and see what language support we have
88 
+            while (my $file = readdir(DIR)) {
89 
+                if (-d $file) {
90 
+                    if (-e "$file/$page") {
91 
+                        my $url = $urlbase.'/'.$WML_SRC_BASENAME.'.html.'.$file;
92 
+                        my $url2js = $WML_SRC_BASENAME.'.html.'.$file;
93 
+                        print '<option value="'.$url.'" onclick="window.location=\''.$url2js.'\'">'.$LANGUAGES{$file}.'</option>'."\n" unless not defined $LANGUAGES{$file};
94 
+                    }
95 
+                }
96 
+            }
97 
+            closedir(DIR);
98 
+          }:>
99 
+          </select>
100 
+          <input class="go" type="submit" name="submit" value="Go" />
101 
+        </form>
102 
+        <p>Questions on this? Visit <a href="http://www.debian.org/intro/cn#howtoset">how to set the default document language</a>.</p>
103 
+      </div>
104 
+    </div>
105 
+    <!-- END FOOTER -->
106 
+
107 
+  </div>
108 
+  <!-- END WRAP -->
109 
+</body>
110 
+</html>
en/home.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,196 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Anonymity Online" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+
7 
+# note, translators will need to translate the javascript below also!
8 
+# also, the script is here so that links are created for the correct language
9 
+<!-- javascript to detect the client and suggest a download link -->
10 
+<script language="javascript" type="text/javascript">
11 
+
12 
+function downloadRedirect() {
13 
+  var destination = "<page download/thankyou>";
14 
+  setTimeout("window.location='"+destination+"'",3000);
15 
+}
16 
+
17 
+function clientSpecificDownload() {
18 
+  document.write('<div id="download" onClick=downloadRedirect()>');
19 
+  var platform = navigator.platform;
20 
+  if (platform === "Win32" || platform === "Win64")
21 
+  {
22 
+    document.write('<a href="<package-win32-bundle-stable>"> \
23 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
24 
+        <span class="version">Version <version-win32-bundle-stable> for Windows</span><br /> \
25 
+        <span class="info">English (US) 24.3MB</span> \
26 
+        </a>');
27 
+  }
28 
+  else if (platform === "MacIntel")
29 
+  {
30 
+    document.write('<a href="<package-osx-bundle-stable>"> \
31 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
32 
+        <span class="version">Version <version-osx-bundle-stable> for Mac OSX</span><br /> \
33 
+        <span class="info">English (US) 24.3MB</span> \
34 
+        </a>');
35 
+  }
36 
+  else if (platform === "MacPPC")
37 
+  {
38 
+    document.write('<a href="<package-oldosx-bundle-stable>"> \
39 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
40 
+        <span class="version">Version <version-oldosx-bundle-stable> for Mac OSX</span><br /> \
41 
+        <span class="info">English (US) 24.3MB</span> \
42 
+        </a>');
43 
+  }
44 
+  else if (platform === "Linux i686" || platform === "Linux x86_64")
45 
+  {
46 
+    document.write('<a href="<package-source-stable>"> \
47 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
48 
+        <span class="version">Version <version-stable> for Linux</span><br /> \
49 
+        <span class="info">English (US) 24.3MB</span> \
50 
+        </a>');
51 
+  }
52 
+  else
53 
+  {
54 
+    document.write('<a href="<page download/download>"> \
55 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
56 
+        <span class="version">Version <version-stable></span><br /> \
57 
+        <span class="info">English (US) 24.3MB</span> \
58 
+        </a>');
59 
+  }
60 
+
61 
+  document.write('</div>');
62 
+  document.write('<div class="incorrect"><a href="<page download/download>">Not what you\'re using?</a></div>');
63 
+}
64 
+</script>
65 
+
66 
+<div id="home">
67 
+    <div id="content" class="clearfix">
68 
+    	<div id="maincol">
69 
+      	<div id="banner">
70 
+        	<ul>
71 
+          	<li>Tor prevents anyone from learning your location or browsing habits.</li>
72 
+            <li>Tor works for web browsers, instant messaging clients, remote logins, and more.</li>
73 
+            <li>Tor is Open Source, so it’s absolutely <u>free</u>, guaranteed.</li>
74 
+          </ul>
75 
+        	<h1 class="headline">Anonymity Online</h1>
76 
+          <p class="desc">Protect your privacy. Defend yourself against network surveillance and traffic analysis.</p>
77 
+
78 
+          <!-- javascript to detect browser -->
79 
+          <script type="text/javascript">
80 
+              clientSpecificDownload();
81 
+          </script>
82 
+
83 
+          <!-- default to download page -->
84 
+          <noscript>
85 
+          <div id="download">
86 
+          <a href="<page download/download>">
87 
+            <span class="download-tor">Download <strong>Tor</strong></span><br />
88 
+            <span class="version">Version <version-stable></span><br />
89 
+            <span class="info">English (US) 24.3MB</span>
90 
+          </a>
91 
+          </div>
92 
+          </noscript>
93 
+
94 
+        </div>
95 
+        <!-- END BANNER -->
96 
+        <div class="subcol-container clearfix">
97 
+          <div class="subcol first">
98 
+            <h2>What is Tor?</h2>
99 
+            <p>Here, you should put an introductory paragraph about the scary things on the web (like how everything you do can be tracked and recorded, or some human rights violations regarding web searches, etc.) what Tor is, what it does, what the Tor mission is, and why you need it. This should be concise and to-the-point. Direct language is a good thing. If they want to learn more about Tor, they can click the continuation link below.<br /><span class="continue"><a href="<page about/about>">Learn more about Tor &raquo;</a></span></p>
100 
+          </div>
101 
+          <!-- END SUBCOL -->
102 
+          <div class="subcol">
103 
+          <h2>Why Anonymity Matters</h2>
104 
+          <p>This is where you can tell your users why they should care about Tor. You can put a concise blurb about your promise and mission. This is reassuring to people who may be on the edge about whether or not to use your product. It will also help spur people on to make a donation, run a relay, or otherwise help your cause. Super cool stuff. Write something catchy and honest-sounding.<br /><span class="continue"><a href="<page about/about>">Get involved with Tor &raquo;</a></span></p>
105 
+          </div>
106 
+        </div>
107 
+        <!-- END SUBCOL -->
108 
+        <div id="home-our-projects" class="clearfix">
109 
+          <h2>Our Projects</h2>
110 
+          <div class="fauxhead"></div>
111 
+          <table>
112 
+            <tr>
113 
+              <td>
114 
+                <img src="images/icon-default.jpg" alt="Default Icon" />
115 
+                <h3><a href="<page projects/torbutton>">TorButton</a></h3>
116 
+                <p>This will be a quick sentence or two summary of the featured project.</p>
117 
+              </td>
118 
+              <td>
119 
+                <img src="images/icon-default.jpg" alt="Default Icon" />
120 
+                <h3><a href="#">TorWeather</a></h3>
121 
+                <p>This will be a quick sentence or two summary of the featured project.</p>
122 
+              </td>
123 
+            </tr>
124 
+            <tr>
125 
+              <td>
126 
+                <img src="images/icon-default.jpg" alt="Default Icon" />
127 
+                <h3><a href="#">PuppeTor</a></h3>
128 
+                <p>This will be a quick sentence or two summary of the featured project.</p>
129 
+              </td>
130 
+              <td>
131 
+                <img src="images/icon-default.jpg" alt="Default Icon" />
132 
+                <h3><a href="http://check.torproject.org">check.torproject.org</a></h3>
133 
+                <p>This will be a quick sentence or two summary of the featured project.</p>
134 
+              </td>
135 
+            </tr>
136 
+          </table>
137 
+      	</div>
138 
+        <!-- END TABLE -->
139 
+      </div>
140 
+      <!-- END MAINCOL -->
141 
+
142 
+      <div id="sidecol">
143 
+      	<div id="torusers">
144 
+          <h2>Who Uses Tor?</h2>
145 
+          <div class="user">
146 
+            <img src="images/family.jpg" alt="Family and Friends" />
147 
+            <h3>Family &amp; Friends</h3>
148 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
149 
+          </div>
150 
+          <div class="user">
151 
+            <img src="images/consumers.jpg" alt="Consumer Advocates" />
152 
+            <h3>Consumer Advocates</h3>
153 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
154 
+          </div>
155 
+          <div class="user">
156 
+            <img src="images/activists.jpg" alt="Human Rights Activists" />
157 
+            <h3>Human Rights Activists</h3>
158 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
159 
+          </div>
160 
+          <div class="user">
161 
+            <img src="images/media.jpg" alt="Media" />
162 
+            <h3>Media</h3>
163 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
164 
+          </div>
165 
+          <div class="user">
166 
+            <img src="images/military.jpg" alt="Military" />
167 
+            <h3>Military</h3>
168 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
169 
+          </div>
170 
+        </div>
171 
+        <div id="home-announcements" class="clearfix">
172 
+        	<h2>Announcements</h2>
173 
+          <div class="fauxhead"></div>
174 
+          <table>
175 
+            <tr>
176 
+              <td>
177 
+                <div class="calendar"><span class="month">May</span><br /><span class="day">05</span></div>
178 
+                <p>The Tor Project has launched a roadmap for dramatically improving the performance of the public Tor network over the next year.<br /><span class="continue"><a href="#">Read the press release &raquo;</a></span></p>
179 
+              </td>
180 
+            </tr>
181 
+            <tr>
182 
+              <td>
183 
+                <div class="calendar"><span class="month">Apr</span><br /><span class="day">27</span></div>
184 
+                <p>Tor 0.2.1.24 released as stable. Fixes compatibility with recent Apple OSX openssl changes and adds some performance enhancements.<br /><span class="continue"><a href="#">Read the full list of changes &raquo;</a></span></p>
185 
+              </td>
186 
+            </tr>
187 
+          </table>
188 
+        </div>
189 
+        <!-- END TABLE -->
190 
+      </div>
191 
+      <!-- END SIDECOL -->
192 
+    </div>
193 
+    <!-- END CONTENT -->
194 
+  </div>
195 
+  <!-- END HOME -->
196 
+#include <foot.wmi>
en/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,196 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Anonymity Online" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+
7 
+# note, translators will need to translate the javascript below also!
8 
+# also, the script is here so that links are created for the correct language
9 
+<!-- javascript to detect the client and suggest a download link -->
10 
+<script language="javascript" type="text/javascript">
11 
+
12 
+function downloadRedirect() {
13 
+  var destination = "<page download/thankyou>";
14 
+  setTimeout("window.location='"+destination+"'",3000);
15 
+}
16 
+
17 
+function clientSpecificDownload() {
18 
+  document.write('<div id="download" onClick=downloadRedirect()>');
19 
+  var platform = navigator.platform;
20 
+  if (platform === "Win32" || platform === "Win64")
21 
+  {
22 
+    document.write('<a href="<package-win32-bundle-stable>"> \
23 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
24 
+        <span class="version">Version <version-win32-bundle-stable> for Windows</span><br /> \
25 
+        <span class="info">English (US) 24.3MB</span> \
26 
+        </a>');
27 
+  }
28 
+  else if (platform === "MacIntel")
29 
+  {
30 
+    document.write('<a href="<package-osx-bundle-stable>"> \
31 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
32 
+        <span class="version">Version <version-osx-bundle-stable> for Mac OSX</span><br /> \
33 
+        <span class="info">English (US) 24.3MB</span> \
34 
+        </a>');
35 
+  }
36 
+  else if (platform === "MacPPC")
37 
+  {
38 
+    document.write('<a href="<package-oldosx-bundle-stable>"> \
39 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
40 
+        <span class="version">Version <version-oldosx-bundle-stable> for Mac OSX</span><br /> \
41 
+        <span class="info">English (US) 24.3MB</span> \
42 
+        </a>');
43 
+  }
44 
+  else if (platform === "Linux i686" || platform === "Linux x86_64")
45 
+  {
46 
+    document.write('<a href="<package-source-stable>"> \
47 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
48 
+        <span class="version">Version <version-stable> for Linux</span><br /> \
49 
+        <span class="info">English (US) 24.3MB</span> \
50 
+        </a>');
51 
+  }
52 
+  else
53 
+  {
54 
+    document.write('<a href="<page download/download>"> \
55 
+        <span class="download-tor">Download <strong>Tor</strong></span><br /> \
56 
+        <span class="version">Version <version-stable></span><br /> \
57 
+        <span class="info">English (US) 24.3MB</span> \
58 
+        </a>');
59 
+  }
60 
+
61 
+  document.write('</div>');
62 
+  document.write('<div class="incorrect"><a href="<page download/download>">Not what you\'re using?</a></div>');
63 
+}
64 
+</script>
65 
+
66 
+<div id="home">
67 
+    <div id="content" class="clearfix">
68 
+    	<div id="maincol">
69 
+      	<div id="banner">
70 
+        	<ul>
71 
+          	<li>Tor prevents anyone from learning your location or browsing habits.</li>
72 
+            <li>Tor works for web browsers, instant messaging clients, remote logins, and more.</li>
73 
+            <li>Tor is Open Source, so it’s absolutely <u>free</u>, guaranteed.</li>
74 
+          </ul>
75 
+        	<h1 class="headline">Anonymity Online</h1>
76 
+          <p class="desc">Protect your privacy. Defend yourself against network surveillance and traffic analysis.</p>
77 
+
78 
+          <!-- javascript to detect browser -->
79 
+          <script type="text/javascript">
80 
+              clientSpecificDownload();
81 
+          </script>
82 
+
83 
+          <!-- default to download page -->
84 
+          <noscript>
85 
+          <div id="download">
86 
+          <a href="<page download/download>">
87 
+            <span class="download-tor">Download <strong>Tor</strong></span><br />
88 
+            <span class="version">Version <version-stable></span><br />
89 
+            <span class="info">English (US) 24.3MB</span>
90 
+          </a>
91 
+          </div>
92 
+          </noscript>
93 
+
94 
+        </div>
95 
+        <!-- END BANNER -->
96 
+        <div class="subcol-container clearfix">
97 
+          <div class="subcol first">
98 
+            <h2>What is Tor?</h2>
99 
+            <p>Here, you should put an introductory paragraph about the scary things on the web (like how everything you do can be tracked and recorded, or some human rights violations regarding web searches, etc.) what Tor is, what it does, what the Tor mission is, and why you need it. This should be concise and to-the-point. Direct language is a good thing. If they want to learn more about Tor, they can click the continuation link below.<br /><span class="continue"><a href="<page about/about>">Learn more about Tor &raquo;</a></span></p>
100 
+          </div>
101 
+          <!-- END SUBCOL -->
102 
+          <div class="subcol">
103 
+          <h2>Why Anonymity Matters</h2>
104 
+          <p>This is where you can tell your users why they should care about Tor. You can put a concise blurb about your promise and mission. This is reassuring to people who may be on the edge about whether or not to use your product. It will also help spur people on to make a donation, run a relay, or otherwise help your cause. Super cool stuff. Write something catchy and honest-sounding.<br /><span class="continue"><a href="<page about/about>">Get involved with Tor &raquo;</a></span></p>
105 
+          </div>
106 
+        </div>
107 
+        <!-- END SUBCOL -->
108 
+        <div id="home-our-projects" class="clearfix">
109 
+          <h2>Our Projects</h2>
110 
+          <div class="fauxhead"></div>
111 
+          <table>
112 
+            <tr>
113 
+              <td>
114 
+                <img src="images/icon-default.jpg" alt="Default Icon" />
115 
+                <h3><a href="<page projects/torbutton>">TorButton</a></h3>
116 
+                <p>This will be a quick sentence or two summary of the featured project.</p>
117 
+              </td>
118 
+              <td>
119 
+                <img src="images/icon-default.jpg" alt="Default Icon" />
120 
+                <h3><a href="#">TorWeather</a></h3>
121 
+                <p>This will be a quick sentence or two summary of the featured project.</p>
122 
+              </td>
123 
+            </tr>
124 
+            <tr>
125 
+              <td>
126 
+                <img src="images/icon-default.jpg" alt="Default Icon" />
127 
+                <h3><a href="#">PuppeTor</a></h3>
128 
+                <p>This will be a quick sentence or two summary of the featured project.</p>
129 
+              </td>
130 
+              <td>
131 
+                <img src="images/icon-default.jpg" alt="Default Icon" />
132 
+                <h3><a href="http://check.torproject.org">check.torproject.org</a></h3>
133 
+                <p>This will be a quick sentence or two summary of the featured project.</p>
134 
+              </td>
135 
+            </tr>
136 
+          </table>
137 
+      	</div>
138 
+        <!-- END TABLE -->
139 
+      </div>
140 
+      <!-- END MAINCOL -->
141 
+
142 
+      <div id="sidecol">
143 
+      	<div id="torusers">
144 
+          <h2>Who Uses Tor?</h2>
145 
+          <div class="user">
146 
+            <img src="images/family.jpg" alt="Family and Friends" />
147 
+            <h3>Family &amp; Friends</h3>
148 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
149 
+          </div>
150 
+          <div class="user">
151 
+            <img src="images/consumers.jpg" alt="Consumer Advocates" />
152 
+            <h3>Consumer Advocates</h3>
153 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
154 
+          </div>
155 
+          <div class="user">
156 
+            <img src="images/activists.jpg" alt="Human Rights Activists" />
157 
+            <h3>Human Rights Activists</h3>
158 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
159 
+          </div>
160 
+          <div class="user">
161 
+            <img src="images/media.jpg" alt="Media" />
162 
+            <h3>Media</h3>
163 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
164 
+          </div>
165 
+          <div class="user">
166 
+            <img src="images/military.jpg" alt="Military" />
167 
+            <h3>Military</h3>
168 
+            <p>Here, you can put a quick sentence about what the featured user or user-group uses Tor for.</p>
169 
+          </div>
170 
+        </div>
171 
+        <div id="home-announcements" class="clearfix">
172 
+        	<h2>Announcements</h2>
173 
+          <div class="fauxhead"></div>
174 
+          <table>
175 
+            <tr>
176 
+              <td>
177 
+                <div class="calendar"><span class="month">May</span><br /><span class="day">05</span></div>
178 
+                <p>The Tor Project has launched a roadmap for dramatically improving the performance of the public Tor network over the next year.<br /><span class="continue"><a href="#">Read the press release &raquo;</a></span></p>
179 
+              </td>
180 
+            </tr>
181 
+            <tr>
182 
+              <td>
183 
+                <div class="calendar"><span class="month">Apr</span><br /><span class="day">27</span></div>
184 
+                <p>Tor 0.2.1.24 released as stable. Fixes compatibility with recent Apple OSX openssl changes and adds some performance enhancements.<br /><span class="continue"><a href="#">Read the full list of changes &raquo;</a></span></p>
185 
+              </td>
186 
+            </tr>
187 
+          </table>
188 
+        </div>
189 
+        <!-- END TABLE -->
190 
+      </div>
191 
+      <!-- END SIDECOL -->
192 
+    </div>
193 
+    <!-- END CONTENT -->
194 
+  </div>
195 
+  <!-- END HOME -->
196 
+#include <foot.wmi>
en/navigation.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,24 @@
1 
+#!/usr/bin/wml
2 
+
3 
+## translation metadata
4 
+# Revision: $Revision: 22069 $
5 
+# Translation-Priority: 1-high
6 
+
7 
+<:
8 
+    # path                              link text
9 
+    my @navigation = (
10 
+        'home'                        , 'Home',
11 
+        'about/about'                 , 'About Tor',
12 
+        'docs/documentation'          , 'Documentation',
13 
+        'projects/clientside'         , 'Projects',
14 
+        'press/press'                 , 'Press',
15 
+        'https://blog.torproject.org' , 'Blog',
16 
+        'http://printfection.com/torprojectstore' , 'Store',
17 
+    );
18 
+    my @calltoaction = (
19 
+        'download/download'                , 'Download',
20 
+        'donate/donate'                    , 'Donate',
21 
+        'getinvolved/getinvolved'          , 'Get Involved',
22 
+    );
23 
+
24 
+:>
fr/contact.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,75 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22359 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Contact" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Contacts</h2>
14 
+
15 
+<div class="underline"></div>
16 
+
17 
+<!-- BEGIN SIDEBAR -->
18 
+<div class="sidebar">
19 
+<h3>Contacts de Presse ou pour d'autres Médias ?</h3>
20 
+<a href="<page press/index>">Voir notre page Presse</a>
21 
+</div>
22 
+
23 
+<p>En premier lieu, si vous avez un problème ou une question à propos de Tor,
24 
+allez voir la <a href="<page documentation>#Support">section Support</a>
25 
+pour comprendre comment procéder. Les développeurs de Tor passent la plus
26 
+grande partie de leur temps à développer Tor et personne n'est dévolu au
27 
+support utilisateur, vous devez donc essayer de vous aider par vous même
28 
+avant <a href="<page faq>#SupportMail">de trouver poliment un
29 
+volontaire</a>.</p>
30 
+
31 
+<p>Si vous avez réellement besoin de nous contacter, il existes plusieurs
32 
+approches. Toutes ces adresses se terminent par @torproject.org. Notez que
33 
+dans la pratique, la plupart d'entre elles redirige vers le même petit
34 
+groupe de personnes, donc soyez patient et <a
35 
+href="http://www.catb.org/~esr/faqs/smart-questions.html">efficace</a>, et
36 
+merci de vérifier que vous avez rédigé votre courriel en anglais.</p>
37 
+
38 
+<ul>
39 
+<li><tt>tor-assistants</tt> est l'adresse "attrape-tout". Si vous voulez poser
40 
+une question orientée, merci de lire les descriptions qui suivent.</li>
41 
+<li><tt>tor-ops</tt> permet de contacter la personne qui gère les autorités
42 
+d'annuaire. Utilisez-la si vous faîtes fonctionner un noeud Tor et que vous
43 
+avez des questions ou des problèmes avec.</li>
44 
+<li><tt>tor-webmaster</tt> can fix typos on the website, change wrong statements
45 
+or directions on the website, and add new sections and paragraphs that you
46 
+send us. You might want to make a draft of your new sections on <a
47 
+href="https://trac.torproject.org/projects/tor/wiki">the Tor wiki</a> first.</li>
48 
+<li><tt>tor-volunteer</tt> est là pour lire vos documents, vos patchs, vos
49 
+tests, vos expériences avec les applications concernées et tout ce qui a été
50 
+inspiré par notre <a href="<page volunteer>">page sur la contribution</a>
51 
+(ou d'autres problèmes que vous avez réglés ou documentés sur l'utilisation
52 
+de Tor). Vous n'avez pas besoin de nous écrire avant de commencer quoi que
53 
+ce soit -- comme tous les projets de contribution sur Internet, nous
54 
+entendons parler de beaucoup de personnes excitées qui s'évanouissent peu
55 
+après, c'est pourquoi nous sommes intéressés par vos progrès récents.</li>
56 
+<li><tt>tor-translation</tt> permet d'ajouter de nouvelles <a href="<page
57 
+translation>">traductions du site web</a> et de répondre aux questions
58 
+relatives aux traductions existantes et en évolution.</li>
59 
+<li><tt>tordnsel</tt> est l'alias pour la personne qui gère la liste de sortie
60 
+tordns.</li>
61 
+<li><tt>donations</tt> est reservée aux questions et commentaires à propos <a
62 
+href="<page donate>">des dons en argent aux développeurs</a>. Plus il y aura
63 
+de dons, plus il y aura de <a href="<page faq>#Funding">Tor</a>. Nous sommes
64 
+à votre écoute si vous avez d'autres moyens plus créatifs sur lesquels vous
65 
+désirez contribuer.</li>
66 
+<li><tt>execdir</tt> est réservé pour la Presse et les Médias, les questions et
67 
+les commentaires à propos de l'association à but non lucratif: marques
68 
+déposées, affiliation et coordination, dons importants, contrats, licences
69 
+et certification, etc.</li>
70 
+</ul>
71 
+
72 
+  </div>
73 
+
74 
+
75 
+#include <foot.wmi>
fr/documentation.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,293 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22359 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor: Documentation" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<a id="RunningTor"></a>
14 
+<h2><a class="anchor" href="#RunningTor">Utiliser Tor</a></h2>
15 
+<ul>
16 
+<li><a href="<page docs/tor-doc-windows>">Installer Tor sur Win32</a></li>
17 
+<li><a href="<page docs/tor-doc-osx>">Installer Tor sur Mac OS X</a></li>
18 
+<li><a href="<page docs/tor-doc-unix>">Installer Tor sur Linux/BSD/Unix</a></li>
19 
+<li><a href="<page torbutton/index>">Installer Torbutton pour Tor</a></li>
20 
+<li><a href="<page docs/tor-doc-relay>">Configurer un relais Tor</a></li>
21 
+<li><a href="<page docs/tor-hidden-service>">Configurer un service caché Tor</a></li>
22 
+</ul>
23 
+
24 
+<a id="Support"></a> <a id="UpToSpeed"></a>
25 
+<h2><a class="anchor" href="#UpToSpeed">Rentrer dans le rythme de Tor, son
26 
+passé, son présent, et son futur</a></h2>
27 
+
28 
+<ol>
29 
+<li>
30 
+D'abord, lisez la <a href="<page overview>">page d'ensemble</a> pour vous
31 
+faire une première idée sur comment Tor fonctionne, sur ce qu'il fait, et
32 
+sur qui l'utilise.
33 
+</li>
34 
+
35 
+<li>
36 
+<a href="<page download>">Installez le Pack Tor</a> et essayez-le.  Assurez
37 
+vous d'avoir installé Firefox auparavant, et soyez sûr d'avoir lu la <a
38 
+href="<page download>#Warning">liste des mises en garde</a> sur les
39 
+possibilités de fuites de votre anonymat.
40 
+</li>
41 
+
42 
+<li>
43 
+Our <a
44 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">FAQ</a>
45 
+covers all sorts of topics, including questions about setting up a client or
46 
+relay, concerns about anonymity attacks, why we didn't build Tor in other
47 
+ways, etc.  There's a separate <a href="<page faq-abuse>">Abuse FAQ</a> to
48 
+answer common questions from or for relay operators.  The <a href="<page
49 
+eff/tor-legal-faq>">Tor Legal FAQ</a> is written by EFF lawyers, and aims to
50 
+give you an overview of some of the legal issues that arise from the Tor
51 
+project in the US.
52 
+</li>
53 
+
54 
+<li>The <a href="<page tor-manual>">manual</a> lists all the possible entries
55 
+you can put in your <a
56 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc
57 
+file</a>. We also provide a <a href="<page tor-manual-dev>">manual for the
58 
+development version of Tor</a>.</li>
59 
+
60 
+<li>If you have questions, we have an IRC channel (for users, relay operators,
61 
+and developers)  at <a href="irc://irc.oftc.net/tor">#tor on
62 
+irc.oftc.net</a>. If you have a bug, especially a crash bug, read <a
63 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#MyTorkeepscrashing.">how
64 
+to report a Tor bug</a> first and then tell us as much information about it
65 
+as you can in <a href="https://bugs.torproject.org/tor">our bugtracker</a>.
66 
+(If your bug is with Polipo, your browser, or some other application, please
67 
+don't put it in our bugtracker.) The <a href="#MailingLists">or-talk mailing
68 
+list</a> can also be useful.
69 
+</li>
70 
+
71 
+<li>
72 
+<a href="https://blog.torproject.org/">Tor a maintenant un blog</a>. Nous
73 
+essayons de le garder à jour toutes les une à deux semaines avec les
74 
+dernières nouvelles.
75 
+</li>
76 
+
77 
+<li>
78 
+Téléchargez et visionnez les présentations au « What The Hack » (<a
79 
+href="http://freehaven.net/~arma/wth-anonymous-communication-58.mp4">vidéo</a>,
80 
+<a href="http://freehaven.net/~arma/wth1.pdf">diapositives</a>, <a
81 
+href="http://wiki.whatthehack.org/index.php/Anonymous_communication_for_the_United_States_Department_of_Defense...and_you">résumé</a>).
82 
+Cette présentation a eu lieu en juillet 2005, à l'époque où nous étions
83 
+financé par l'EFF et où le réseau était encore assez petit, mais il continue
84 
+à offrir une bonne compréhension de la manière dont Tor fonctionne et à quoi
85 
+il sert.
86 
+</li>
87 
+
88 
+<li>
89 
+Jetez un œil sur <a href="#DesignDoc">nos documents de
90 
+spécifications</a>. Notez que nous avons des spécifications dans le style
91 
+RFC pour préciser exactement comment Tor est conçu.
92 
+</li>
93 
+
94 
+<li>
95 
+Il existe une <a
96 
+href="https://svn.torproject.org/svn/projects/roadmaps/2008-12-19-roadmap-full.pdf">liste
97 
+très réduite d'éléments que nous souhaiterions aborder dans le
98 
+futur</a>. Hélas, beaucoup de ces points devraient être approfondis avant
99 
+qu'ils puissent avoir un sens pour des nons dévelopeurs Tor, mais vous
100 
+pouvez tout de même avoir une idée des questions à résoudre prochainement.
101 
+</li>
102 
+
103 
+<li>
104 
+Téléchargez et regardez les présentations de Nick sur les « Changements
105 
+Techniques depuis 2004 » à la Defcon de juillet 2007 (<a
106 
+href="http://freehaven.net/~arma/Defcon15-Mathewson-Technical_Changes_since_you_Last_Heard_about_Tor.mp4">vidéo</a>,
107 
+<a
108 
+href="http://freehaven.net/~nickm/slides/Defcon07/TorChanges.pdf">diaporama</a>),
109 
+La présentation de Roger « Résistance au blocage et contournement » au 23C3
110 
+de décembre 2006 (<a
111 
+href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">vidéo</a>,
112 
+<a href="http://freehaven.net/~arma/slides-23c3.pdf">diaporama</a>, <a
113 
+href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">résumé</a>,
114 
+<a
115 
+href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">document
116 
+de spécifications</a>), et la présentation des « Évènements courant en 2007
117 
+» de Roger au 24C3 en décembre 2007 (<a
118 
+href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">vidéo</a>,
119 
+<a href="http://freehaven.net/~arma/slides-24c3.pdf">diaporama</a>, <a
120 
+href="http://events.ccc.de/congress/2007/Fahrplan/events/2325.en.html">résumé</a>).
121 
+Nous avons également le tutoriel « What The Hack » sur les services cachés
122 
+(<a href="http://freehaven.net/~arma/wth_tor_hidden_services.mp4">vidéo</a>,
123 
+<a href="http://freehaven.net/~arma/wth3.pdf">diaporama</a>).
124 
+</li>
125 
+
126 
+<li>
127 
+Regardez la conférence « Sécuriser le réseau Tor » de Mike au Defcon en
128 
+Juillet 2007 (<a
129 
+href="http://freehaven.net/~arma/Defcon15-Mike_Perry-Securing_the_Tor_Network.mp4">vidéo</a>,
130 
+<a
131 
+href="http://freehaven.net/~arma/SecuringTheTorNetwork.pdf">diapositives</a>).
132 
+Il décrit plusieurs manières d'attaquer les réseaux comme Tor et comment
133 
+nous pouvons essayer de nous défendre contre celles-ci, et il introduit la
134 
+collection de scripts <a
135 
+href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>.
136 
+</li>
137 
+
138 
+<li>
139 
+Étudiez les <a href="<gitblob>doc/spec/proposals/001-process.txt">processus
140 
+Tor proposés à la modifications de nos spécifications</a>, et consultez les
141 
+<a href="<gittree>doc/spec/proposals">propositions existantes</a>.
142 
+</li>
143 
+
144 
+<li>
145 
+Notre <a href="<gitblob>doc/TODO">fichier TODO de développeur</a> commence
146 
+par un calendrier de promesses &mdash; choses que <a href="<page
147 
+sponsors>">nos sponsors</a> ont payé pour voir achevées. Elle liste
148 
+également d'autres tâches et thèmes que nous aimerions attaquer
149 
+prochainement.
150 
+</li>
151 
+
152 
+<li>
153 
+Une fois dans le rythme, les choses continueront de changer rapidement.  La
154 
+<a href="#MailingLists">liste de diffusion or-dev</a> est l'endroit où les
155 
+discussions complexes arrivent, et le canal #tor sur IRC est l'endroit où
156 
+les discussions moins complexes prennent place.
157 
+</li>
158 
+
159 
+</ol>
160 
+
161 
+<a id="MailingLists"></a>
162 
+<h2><a class="anchor" href="#MailingLists">Information sur les listes de
163 
+diffusion</a></h2>
164 
+<ul>
165 
+<li>La <a href="http://archives.seul.org/or/announce/">liste de diffusion
166 
+or-announce</a> est une liste a faible trafic pour les annonces de nouvelles
167 
+versions et les mises à jour de sécurité. Tout le monde devrait souscrire à
168 
+cette liste. Il y a également <a
169 
+href="http://rss.gmane.org/gmane.network.onion-routing.announce">un flux
170 
+RSS</a> de la liste or-announce sur <a
171 
+href="http://gmane.org">gmane.org</a>.</li>
172 
+<li>La <a href="http://archives.seul.org/or/talk/">liste or-talk</a> est
173 
+l'endroit où les discussions se déroulent, et où nous envoyons les
174 
+notifications de pré-versions et les versions candidates.</li>
175 
+<li>La <a href="http://archives.seul.org/tor/relays/">liste de diffusion
176 
+tor-relays</a> est l'endroit désigné pour discuter du fonctionnement, de la
177 
+configuration, de la gestion courante de votre noeud Tor.  Si vous faîtes
178 
+fonctionner actuellement un noeud ou que vous pensez le faire, cette liste
179 
+est pour vous.</li>
180 
+<li>La <a href="http://archives.seul.org/or/dev/">liste or-dev</a> est pour les
181 
+développeurs seulement et a un très faible trafic.</li>
182 
+<li>Une liste de diffusion destinée aux <a
183 
+href="http://archives.seul.org/tor/mirrors/">gestionnaires de miroirs</a>
184 
+pour les nouveaux miroirs de site et le support <a href="<page mirrors>">des
185 
+miroirs de site actuels</a>.</li>
186 
+<li>La liste pour les <a href="http://archives.seul.org/or/cvs/">commits git et
187 
+svn</a> peut-être intéressante pour les développeurs.</li>
188 
+<li>An automated list for <a href="http://archives.seul.org/tor/bugs/">bug
189 
+reports from trac</a> may be interesting for users and developers.</li>
190 
+</ul>
191 
+
192 
+<a id="DesignDoc"></a>
193 
+<h2><a class="anchor" href="#DesignDoc">Documents de spécifications</a></h2>
194 
+<ul>
195 
+<li>Le <b>document de conception</b> (publié lors de Usenix Security en 2004)
196 
+présente notre analyse de sécurité, et notre point de vue sur la conception
197 
+de Tor : disponible en versions <a
198 
+href="https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf">PDF</a>
199 
+et <a
200 
+href="https://svn.torproject.org/svn/projects/design-paper/tor-design.html">HTML</a>.</li>
201 
+<li>Notre publication suivante : <b>les défis de l'anonymat avec un court délai
202 
+de réponse</b> (encore à l'état d'ébauche) expose des expériences et des
203 
+tendances plus récentes : <a
204 
+href="https://svn.torproject.org/svn/projects/design-paper/challenges.pdf">l'ébauche
205 
+au format PDF</a>.</li>
206 
+<li>Notre papier au WEIS 2006 &mdash; <b>L'Anonymat aime les entreprises : De
207 
+l'utilisation et de son effet sur le réseau</b> &mdash; explique en quoi
208 
+l'utilisation des systèmes anonymes est importante pour leur sécurité: <a
209 
+href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
210 
+<li>Nos spécifications préliminaires visant à rendre plus difficile le blocage
211 
+des firewalls pour l'accès au réseau Tor est décrit sur <b>Architecture d'un
212 
+système résistant au blocage</b> : <a
213 
+href="https://svn.torproject.org/svn/projects/design-paper/blocking.pdf">l'ébauche
214 
+au format PDF</a> et <a
215 
+href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">l'ébauche
216 
+au format HTML</a>. Vous êtes intéressé pour <a href="<page
217 
+volunteer>#Coding">nous aider à le coder</a> ?</li>
218 
+<li>Les <b>spécifications</b> visent à donner aux développeurs suffisamment
219 
+d'informations pour créer une version compatible de Tor :
220 
+<ul>
221 
+<li><a href="<gitblob>doc/spec/tor-spec.txt">Spécifications principales de Tor
222 
+</a></li>
223 
+<li><a href="<gitblob>doc/spec/dir-spec.txt">Version 3 des spécifications de
224 
+serveur d'annuaire</a> (anciennement les <a
225 
+href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> et <a
226 
+href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> des spécifications
227 
+d'annuaire)</li>
228 
+<li><a href="<gitblob>doc/spec/control-spec.txt">Spécification du protocole de
229 
+contrôle de Tor</a></li>
230 
+<li><a href="<gitblob>doc/spec/rend-spec.txt">Spécification du « rendezvous »
231 
+Tor</a></li>
232 
+<li><a href="<gitblob>doc/spec/path-spec.txt">Spécification de la sélection de
233 
+chemin de Tor</a></li>
234 
+<li><a href="<gitblob>doc/spec/address-spec.txt">Noms de machines spéciaux dans
235 
+Tor</a></li>
236 
+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Gestion de SOCKS et de ses
237 
+extensions par Tor</a></li>
238 
+<li><a href="<gitblob>doc/spec/version-spec.txt">Comment sont numérotés les
239 
+versions de Tor</a></li>
240 
+<li><a href="<gitblob>doc/spec/proposals">Travail en cours sur les nouvelles
241 
+spécifications et sur les changements proposés</a></li>
242 
+</ul></li>
243 
+
244 
+</ul>
245 
+
246 
+<a id="NeatLinks"></a>
247 
+<h2><a class="anchor" href="#NeatLinks">Liens utiles</a></h2>
248 
+<ul>
249 
+<li>The <a href="https://trac.torproject.org/projects/tor/wiki">Tor wiki</a>
250 
+provides a plethora of helpful contributions from Tor users. Check it out!</li>
251 
+<li><a
252 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">A
253 
+list of supporting programs you might want to use in association with
254 
+Tor</a>.</li>
255 
+<li><a href="https://check.torproject.org/">Le détecteur Tor</a> ou <a
256 
+href="http://torcheck.xenobite.eu/">L'autre Detecteur Tor</a> essaye de
257 
+déterminer si vous utilisez Tor ou non.</li>
258 
+<li>Allez voir l'une des pages sur l'état de Tor comme <a
259 
+href="http://torstatus.blutmagie.de/">celle de blutmagie</a>, ou <a
260 
+href="http://trunk.torstatus.kgprog.com/index.php">celle de kgprog</a>, ou
261 
+encore la page de Xenobite <a href="https://torstat.xenobite.eu/">état du
262 
+noeud Tor</a>.  Souvenez vous que ces listes peuvent ne pas être aussi à
263 
+jour que celles utilisées par votre client Tor, car ce dernier va chercher
264 
+les listes d'annuaires et les combine localement. </li>
265 
+<li>Lisez <a
266 
+href="http://freehaven.net/anonbib/topic.html#Anonymous_20communication">ces
267 
+documents</a> (en particulier ceux mis en valeur) pour des informations sur
268 
+les systèmes de communications anonymes.</li>
269 
+</ul>
270 
+
271 
+<a id="Developers"></a>
272 
+<h2><a class="anchor" href="#Developers">Pour les développeurs</a></h2>
273 
+  Parcourez le <b>dépôt des sources</b> de Tor:
274 
+  <ul>
275 
+    <li><a href="<gitrepo>">Parcourir l'arborescence de répertoire du dépôt des
276 
+sources directement</a></li>
277 
+    <li>Accès à Git et au SVN:
278 
+      <ul>
279 
+        <li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>
280 
+        <li>La branche de développement est nommée <kbd>master</kbd>.  Les branches de
281 
+maintenance sont nommées <kbd>maint-0.2.0</kbd> et <kbd>maint-0.2.1</kbd>.</li>
282 
+        <li><kbd>svn checkout https://svn.torproject.org/svn/website/trunk website</kbd></li>
283 
+      </ul>
284 
+    </li>
285 
+    <li><a
286 
+href="https://gitweb.torproject.org//githax.git?a=blob;f=doc/Howto.txt;hb=HEAD">Instructions
287 
+de base pour l'utilisation de Git en vue de contribuer au logiciel Tor.</a></li>
288 
+  </ul>
289 
+
290 
+  </div>
291 
+
292 
+
293 
+#include <foot.wmi>
fr/faq-abuse.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,449 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22308 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Abuse FAQ" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>FAQ sur l'utilisation abusive</h2>
17 
+
18 
+<!-- BEGIN SIDEBAR -->
19 
+<div class="sidebar-left">
20 
+<h3>Questions</h3>
21 
+<ul>
22 
+<li><a href="<page faq-abuse>#WhatAboutCriminals">Tor permet-il aux criminels
23 
+d'accomplir leurs forfaits ?</a></li>
24 
+<li><a href="<page faq-abuse>#DDoS">Qu'en est-il des attaques par déni de
25 
+service distribué ?</a></li>
26 
+<li><a href="<page faq-abuse>#WhatAboutSpammers">Et les spammeurs ?</a></li>
27 
+<li><a href="<page faq-abuse>#HowMuchAbuse">Y a-t-il beaucoup d'utilisations
28 
+abusives de Tor ?</a></li>
29 
+<li><a href="<page faq-abuse>#TypicalAbuses">Si je mets en place un relais, à
30 
+quoi dois-je m'attendre ?</a></li>
31 
+<li><a href="<page faq-abuse>#IrcBans">Tor est banni du serveur IRC que je veux
32 
+utiliser.</a></li>
33 
+<li><a href="<page faq-abuse>#SMTPBans">Les nœuds de sortie Tor sont bannis du
34 
+serveur de mail que je veux utiliser.</a></li>
35 
+<li><a href="<page faq-abuse>#Bans">Je veux bannir le réseau Tor de mon service
36 
+Internet.</a></li>
37 
+<li><a href="<page faq-abuse>#TracingUsers">J'ai une raison impérieuse de
38 
+retrouver la trace d'un utilisateur de Tor. Pouvez-vous m'aider ?</a></li>
39 
+<li><a href="<page faq-abuse>#RemoveContent">Je veux supprimer un contenu d'une
40 
+adresse-oignon.</a></li>
41 
+<li><a href="<page faq-abuse>#LegalQuestions">J'ai des questions juridiques au
42 
+sujet de l'utilisation malveillante.</a></li>
43 
+</ul>
44 
+</div>
45 
+
46 
+<!-- END SIDEBAR -->
47 
+<hr />
48 
+
49 
+<a id="WhatAboutCriminals"></a>
50 
+<h3><a class="anchor" href="#WhatAboutCriminals">Tor permet-il aux criminels
51 
+d'accomplir leurs forfaits ?</a></h3>
52 
+
53 
+<p>Les criminels peuvent déjà accomplir leurs mauvaises actions. Déterminés à
54 
+briser les lois, ils disposent déjà de nombreuses options qui peuvent leur
55 
+procurer un <em>meilleur</em> anonymat que ne le peut Tor. Ils peuvent voler
56 
+des téléphones portables, les utiliser, puis les jeter dans le caniveau ;
57 
+ils peuvent pirater des ordinateurs en Corée ou au Brésil et les utiliser
58 
+pour lancer leurs attaques. Ils peuvent utiliser des logiciels espions, des
59 
+virus, et d'autres techniques, pour prendre le contrôle, au sens propre, de
60 
+millions de machines Windows dans le monde. </p>
61 
+
62 
+<p>Tor a pour vocation d'apporter la sécurité des communications Internet à des
63 
+gens ordinaires respectueux des lois. Pour le moment, seuls les criminels
64 
+bénéficient de confidentialité, et nous devons corriger cela. </p>
65 
+
66 
+<p>Certains qui militent en faveur de la confidentialité expliquent qu'il
67 
+s'agit juste d'une question d'échange - accepter les mauvais usages pour
68 
+pouvoir avoir les bons -, mais il y a plus que cela.  Les criminels et
69 
+autres personnes mal intentionnées possèdent la motivation d'apprendre à
70 
+obtenir un bon anonymat, et beaucoup sont prêts à payer cher pour
71 
+l'obtenir. Être en mesure de voler et de réutiliser l'identité d'innocentes
72 
+victimes (usurpation d'identité) leur rend la tâche encore plus facile. D'un
73 
+autre côté, les gens ordinaires n'ont ni le temps, ni l'argent, d'investir
74 
+dans l'étude de solutions permettant d'obtenir la sécurité de leurs
75 
+communications sur Internet. C'est le plus mauvais des mondes possibles. </p>
76 
+
77 
+<p>Donc, oui, en théorie, les criminels pourraient utiliser Tor, mais ils ont
78 
+déjà de meilleures solutions. Et il semble improbable qu'éliminer Tor de la
79 
+surface du monde les arrêterait dans leurs entreprises criminelles. En même
80 
+temps, Tor, et d'autres mesures de protection des données privées, peuvent
81 
+<em>combattre</em> l'usurpation d'identité, la traque physique des
82 
+personnes, etc. </p>
83 
+
84 
+
85 
+
86 
+<!--
87 
+<a id="Pervasive">
88 
+</a>
89 
+<h3><a class="anchor" href="#Pervasive">If the whole world starts using
90 
+Tor, won't civilization collapse?</a></h3>
91 
+-->
92 
+<a id="DDoS"></a>
93 
+<h3><a class="anchor" href="#DDoS">Qu'en est-il des attaques par déni de service
94 
+distribué ?</a></h3>
95 
+
96 
+<p>Les attaques par déni de service distribué (ou déni de service réparti, en
97 
+anglais : DDoS - Distributed Denial of Service) supposent, globalement, de
98 
+disposer d'un groupe de milliers d'ordinateurs lançant des requêtes vers une
99 
+machine victime de façon simultanée. Le but étant de saturer la bande
100 
+passante de la machine visée, ces ordinateurs envoient généralement des
101 
+paquets UDP, car ceux-ci ne nécessitent ni procédures d'authentification, ni
102 
+coordination. </p>
103 
+
104 
+<p>Mais, Tor ne transportant que des flux TCP correctement configurés, et non
105 
+des paquets IP, on ne peut pas utiliser Tor pour envoyer des paquets UDP. De
106 
+même, Tor n'autorise pas les attaques par amplification de bande passante :
107 
+vous devez envoyer un octet pour chaque octet que Tor enverra vers la
108 
+destination que vous avez choisie. Donc, d'une façon générale, des
109 
+attaquants qui disposeraient d'une bande passante suffisante pour une
110 
+attaque DDoS efficace peuvent le faire tout aussi bien sans l'aide de Tor. </p>
111 
+
112 
+<a id="WhatAboutSpammers"></a>
113 
+<h3><a class="anchor" href="#WhatAboutSpammers">Et les spammeurs ?</a></h3>
114 
+
115 
+<p>Premier point, les règles par défaut pour les nœuds de sortie de Tor
116 
+rejettent tout trafic sortant du port 25 (SMTP) : envoyer du spam via Tor,
117 
+par défaut, ne va donc pas fonctionner. Il est possible que certains
118 
+opérateurs de relais ouvrent le port 25 sur leur serveur, ce qui
119 
+autoriserait l'envoi de mails. Mais ces opérateurs peuvent tout aussi bien
120 
+installer un serveur relais de mail ouvert, complètement indépendant de
121 
+Tor. En résumé, Tor n'est pas très utile au spammeur, parce que presque tous
122 
+les serveurs Tor refusent d'acheminer les mails sortants. </p>
123 
+
124 
+<p>Bien sûr, il y a plus que l'acheminement des mails. Les spammeurs peuvent
125 
+utiliser Tor pour se connecter à des proxys HTTP ouverts (et de là, à des
126 
+serveurs SMTP) ; pour se connecter à de mauvais scripts CGI envoyant des
127 
+mails, et pour contrôler leur robots - et ainsi, communiquer, de façon
128 
+déguisée, avec des armées de machines compromises qui enverront le spam.
129 
+</p>
130 
+
131 
+<p>
132 
+C'est désolant, mais il faut noter que les spammeurs font déjà ceci très
133 
+bien, sans Tor. Surtout, souvenez-vous que nombre de leurs méthodes
134 
+d'attaque les plus subtiles (comme l'envoi de paquets UDP contrefaits) ne
135 
+peuvent pas être utilisées sur Tor, parce qu'il ne transporte que des
136 
+paquets TCP correctement formés.
137 
+</p>
138 
+
139 
+<a id="ExitPolicies"></a>
140 
+<h3><a class="anchor" href="#ExitPolicies">Quelle est la stratégie pour les
141 
+relais de sortie de Tor ?</a></h3>
142 
+
143 
+<p>
144 
+<a href="<page faq>#ExitPolicies">Déplacé sur la page de la nouvelle FAQ</a>
145 
+</p>
146 
+
147 
+<a id="HowMuchAbuse"></a>
148 
+<h3><a class="anchor" href="#HowMuchAbuse">Y a-t-il beaucoup d'utilisations
149 
+abusives de Tor ?</a></h3>
150 
+
151 
+<p>Pas beaucoup, tout bien considéré. Nous avons mis en place et maintenu le
152 
+réseau depuis octobre 2003, et il n'y a eu qu'une poignée de plaintes. Bien
153 
+entendu, comme tous les réseaux orientés vers la confidentialité des
154 
+communications sur Internet, nous attirons notre lot d'abrutis. Les
155 
+stratégies de sortie pratiquées par Tor aident à bien différencier le rôle
156 
+de "voulant contribuer au réseau par des ressources" de celui de "voulant
157 
+avoir à gérer les plaintes pour utilisations abusives"; nous espérons ainsi
158 
+faire de Tor un réseau plus durable que les essais précédents de réseaux
159 
+anonymes. </p>
160 
+
161 
+<p>Étant donné que Tor a également <a href="<page overview>">un nombre
162 
+important d'utilisateurs légitimes</a>, nous pensons réussir plutôt bien à
163 
+maintenir l'équilibre pour l'instant. </p>
164 
+
165 
+<a id="TypicalAbuses"></a>
166 
+<h3><a class="anchor" href="#TypicalAbuses">Si je mets en place un relais, à
167 
+quoi dois-je m'attendre ?</a></h3>
168 
+
169 
+<p>Si le relais Tor que vous mettez en place autorise les sorties de connexions
170 
+(et ce, avec les stratégies de sortie par défaut), il est bon de dire que
171 
+vous finirez par entendre parler de quelqu'un. Les plaintes pour utilisation
172 
+abusive présentent des formes variées. Par exemple : </p>
173 
+<ul>
174 
+<li>Quelqu'un se connecte à Hotmail, et envoie à une entreprise une demande de
175 
+rançon. Le FBI vous envoie un courriel poli, vous expliquez que vous faites
176 
+tourner un relais Tor, ils disent "Ah, bien..." et vous laissent
177 
+tranquille. [Port 80]</li>
178 
+<li>Quelqu'un essaie de faire fermer votre relais en utilisant Tor pour se
179 
+connecter aux newsgroups Google et envoyer du spam sur Usenet, et ensuite
180 
+cette personne envoie un mail courroucé à votre FAI, pour dire que vous
181 
+détruisez le monde. [Port 80]</li>
182 
+<li>Quelqu'un se connecte à un réseau IRC (Internet Relay Chat) et se comporte
183 
+de façon malfaisante. Votre FAI reçoit un mail poli disant que votre
184 
+ordinateur a été compromis, et/ou votre ordinateur subit une attaque
185 
+DDoS. [Port 6667]</li>
186 
+<li>Quelqu'un utilise Tor pour télécharger un film de Vin Diesel, et votre FAI
187 
+reçoit une plainte des autorités chargées de faire respecter les droits
188 
+s'appliquant sur le matériel téléchargé. Consulter le <a href="<page
189 
+eff/tor-dmca-response>">modèle de réponse Tor DMCA</a> de l'EFF, qui
190 
+explique en quoi votre FAI peut certainement ignorer la plainte sans
191 
+risque. [Ports divers]</li>
192 
+</ul>
193 
+
194 
+<p>Vous pourriez aussi vous apercevoir que l'accès à certains sites Internet ou
195 
+services est bloqué pour l'adresse IP de votre serveur. Ceci pourrait
196 
+arriver quelle que soit la stratégie de sortie de votre relais, parce que
197 
+certains groupes ne semblent pas savoir que Tor a des stratégies de sortie,
198 
+ou ne pas s'en soucier. (Si vous avez une IP de réserve qui n'est pas
199 
+utilisée pour d'autres activités, vous pouvez envisager de faire tourner
200 
+votre serveur avec cette IP). Par exemple, </p>
201 
+
202 
+<ul>
203 
+<li>À cause de quelques cas d'idiots s'amusant à vandaliser ses pages, Wikipédia
204 
+bloque pour l'instant la fonction "écriture" pour beaucoup de relais Tor (la
205 
+lecture des pages marche toujours). Nous discutons actuellement avec
206 
+Wikipédia sur comment ils pourraient limiter les utilisations malveillantes
207 
+tout en maintenant les fonctionnalités d'écriture pour les contributeurs
208 
+anonymes qui ont souvent des scoops ou des informations de première main sur
209 
+un sujet, mais ne souhaitent pas révéler leur identité en les publiant (ou
210 
+ne souhaitent pas révéler à un observateur local qu'ils utilisent
211 
+Wikipédia). Slashdot est dans le même cas de figure.</li>
212 
+
213 
+<li>SORBS a placé les IP de quelques relais Tor sur sa liste noire d'adresses
214 
+email. Ils ont fait cela après avoir détecté, en mode passif, que votre
215 
+relais se connectait à certains réseaux IRC, et ils en ont conclu que votre
216 
+relais était susceptible de spammer. Nous avons essayé de travailler avec
217 
+eux et de leur expliquer que tous les logiciels ne fonctionnaient pas de
218 
+cette façon, mais nous avons renoncé. Nous vous recommandons d'éviter SORBS,
219 
+et d'apprendre à vos amis (s'ils l'utilisent) <a
220 
+href="http://paulgraham.com/spamhausblacklist.html">comment éviter d'être
221 
+sur les listes noires</a>.</li>
222 
+
223 
+</ul>
224 
+
225 
+<a id="IrcBans"></a>
226 
+<h3><a class="anchor" href="#IrcBans">Tor est banni du serveur IRC que je veux
227 
+utiliser.</a></h3>
228 
+
229 
+<p>Il arrive que des idiots se servent de Tor pour "troller" dans des canaux
230 
+IRC. Cette utilisation malveillante peut résulter dans le bannissement
231 
+temporaire d'une IP (dans le jargon IRC, "kline") que l'opérateur du réseau
232 
+IRC met en place pour empêcher le troll d'accéder au réseau. </p>
233 
+
234 
+<p>Ce type de réponse met en évidence une faiblesse essentielle du modèle de
235 
+sécurité d'IRC : les opérateurs de réseau IRC supposent que une adresse IP
236 
+égale un humain, et qu'en bannissant l'adresse IP, ils banniront en même
237 
+temps l'individu. En réalité, ce n'est pas ainsi que cela fonctionne -
238 
+beaucoup de ces trolls prennent soin, généralement, d'utiliser les millions
239 
+de proxys ouverts existants et les ordinateurs dont la sécurité est
240 
+compromise. Les réseaux IRC ont engagé une bataille perdue d'avance à
241 
+essayer de bloquer tous ces nœuds, et toute une industrie d'anti-trolls et
242 
+dresseurs de listes noires a émergé, basée sur cette faille du modèle de
243 
+sécurité (un peu comme l'industrie de l'anti-virus). Tor, ici, n'est qu'une
244 
+goutte d'eau dans la mer. </p>
245 
+
246 
+<p>D'un autre côté, du point de vue des opérateurs de réseau IRC, la sécurité
247 
+n'est pas un "tout ou rien". La rapidité de leur réponse aux trolls ou aux
248 
+autres attaques de ce type peut rendre le scénario d'attaque moins
249 
+intéressant pour le troll. Notons que, sur un réseau donné, à un instant
250 
+donné, une adresse IP particulière correspondra bien à un seul individu.
251 
+Parmi les exceptions, on trouve en particulier les passerelles NAT,
252 
+auxquelles l'accès peut être autorisé. Vouloir stopper l'utilisation de
253 
+proxys ouverts est une bataille perdue d'avance, mais ce n'en est pas une de
254 
+bannir (kline) une adresse IP de façon répétée, jusqu'à ce que l'utilisateur
255 
+au comportement abusif se lasse et s'en aille voir ailleurs. </p>
256 
+
257 
+<p>Mais la bonne réponse serait d'implémenter des applications
258 
+d'authentification, de laisser l'accès au réseau aux utilisateurs qui se
259 
+comportent correctement et d'empêcher les malveillants d'entrer. Ceci doit
260 
+se faire sur la base de quelque chose que l'humain connaît (comme un mot de
261 
+passe, par exemple), et non sur la manière dont les paquets de données sont
262 
+transportés. </p>
263 
+
264 
+<p>Bien entendu, les réseaux IRC n'essayent pas tous de bannir les nœuds
265 
+Tor. Après tout, pas mal de gens utilisent Tor pour avoir, via IRC, des
266 
+discussions confidentielles sans qu'on puisse faire le lien entre leur
267 
+compte dans les canaux IRC et leur vraie identité. Il appartient à chaque
268 
+réseau IRC de décider s'il veut, en bloquant l'accès des IP utilisant Tor -
269 
+une poignée par rapport aux millions d'IP que les personnes malveillantes
270 
+peuvent utiliser - bloquer aussi les contributions des utilisateurs de Tor
271 
+qui se comportent correctement. </p>
272 
+
273 
+<p>Si l'accès à un réseau IRC est bloqué pour vous, ayez une discussion avec
274 
+les opérateurs du réseau, et expliquez-leur les enjeux. Ils peuvent très
275 
+bien ne pas connaître du tout l'existence de Tor, ou bien ne pas savoir que
276 
+les noms d'hôte qu'ils bannissent sont des nœuds de sortie Tor.  Si vous
277 
+expliquez le problème, et qu'ils concluent que Tor doit être bloqué, alors
278 
+vous pouvez peut-être envisager d'aller sur un réseau plus soucieux de la
279 
+liberté d'expression. Les inviter sur le canal #tor sur irc.oftc.net peut
280 
+aussi leur montrer que nous ne sommes pas tous des "méchants". </p>
281 
+
282 
+<p>Enfin, si vous avez connaissance d'un réseau IRC qui semble interdire à Tor
283 
+son accès, ou qui bloque un nœud de sortie Tor, merci de faire figurer cette
284 
+information dans la <a
285 
+href="https://wiki.torproject.org/wiki/TheOnionRouter/BlockingIrc">liste des
286 
+réseaux IRC bloquant Tor</a> afin d'en informer les autres.  Au moins un
287 
+réseau IRC consulte cette page pour débloquer les nœuds Tor qui ont été
288 
+bannis par inadvertance. </p>
289 
+
290 
+<a id="SMTPBans"></a>
291 
+<h3><a class="anchor" href="#SMTPBans">Les nœuds de sortie Tor sont bannis du
292 
+serveur de mail que je veux utiliser.</a></h3>
293 
+
294 
+<p>Même si Tor n'est <a href="#WhatAboutSpammers">pas utile pour faire du
295 
+spam</a>, certains black-listeurs zélés semblent penser que tous les réseaux
296 
+ouverts comme Tor sont le mal - ils donnent à leurs administrateurs réseau
297 
+les moyens d'une opération coup-de-poing sur les problèmes de stratégie de
298 
+réseau, de service, et de routage, puis ils demandent des rançons aux
299 
+victimes. </p>
300 
+
301 
+<p>Au cas où les administrateurs de votre serveur mail décideraient de refuser
302 
+le courrier entrant sur la base de ces listes noires, vous devriez discuter
303 
+de Tor avec eux, et leur expliquer son fonctionnement et ses stratégies de
304 
+sortie. </p>
305 
+
306 
+<a id="Bans"></a>
307 
+<h3><a class="anchor" href="#Bans">Je veux bannir le réseau Tor de mon service
308 
+Internet.</a></h3>
309 
+
310 
+<p>Nous sommes désolés de l'apprendre. Il y a quelques cas qui justifient de
311 
+bloquer l'accès d'un service Internet à des utilisateurs anonymes. Mais,
312 
+dans la plupart des cas, il existe des solutions plus simples pour résoudre
313 
+votre problème tout en continuant à laisser les utilisateurs accéder au
314 
+service de façon sûre.</p>
315 
+
316 
+<p>D'abord, demandez-vous si vous ne pourriez pas différencier les utilisateurs
317 
+légitimes des utilisateurs malveillants par des mesures prises au niveau
318 
+logiciel. Par exemple, vous pourriez n'autoriser l'accès à certaines parties
319 
+du site, ou à certains privilèges comme la fonction de "post", qu'aux
320 
+utilisateurs enregistrés. Il est facile de maintenir une liste à jour des
321 
+adresses IP Tor qui auraient accès au service, vous pourriez mettre ceci en
322 
+place pour les utilisateurs de Tor. De cette façon, vous auriez des accès
323 
+multi-critères, et n'auriez pas à interdire l'accès à la totalité de votre
324 
+service. </p>
325 
+
326 
+<p>À titre d'exemple, le <ahref="http://freenode.net/policy.shtml#tor">réseau
327 
+IRC Freenode</a> a connu un problème avec un groupe organisé d'utilisateurs
328 
+malveillants qui joignaient des canaux de discussion et en prenaient
329 
+subtilement le contrôle. Lorsque Freenode a étiqueté "utilisateur anonyme"
330 
+tous les utilisateurs des relais Tor, empêchant ceux qui commettaient les
331 
+abus de s'immiscer dans les canaux, ceux-ci se sont remis à utiliser leurs
332 
+proxys ouverts et leurs bots. </p>
333 
+
334 
+<p>En second lieu, pensez que des dizaines de milliers de gens utilisent
335 
+quotidiennement Tor simplement comme une mesure de bonne hygiène dans leur
336 
+navigation normale sur Internet - par exemple, pour se protéger contre les
337 
+sites publicitaires qui collectent des données. D'autres se serviront de Tor
338 
+parce que c'est la seule façon pour eux de sortir de pare-feu locaux
339 
+restrictifs. Certains utilisateurs de Tor sont sans doute, en ce moment
340 
+même, connectés à votre service, et y ont des activités tout-à-fait
341 
+banales. Vous devez décider si interdire l'accès à Tor vaut la peine de
342 
+perdre la contribution de ces utilisateurs, ainsi que des éventuels futurs
343 
+utilisateurs légitimes de votre service. Souvent, les gens n'ont même pas
344 
+idée du nombre d'utilisateurs polis de Tor qui sont connectés à leur service
345 
+- ils passent inaperçus jusqu'à ce qu'un impoli se manifeste.</p>
346 
+
347 
+<p>À ce niveau, demandez-vous également quelle doit être votre politique pour
348 
+les autres services qui groupent un grand nombre d'utilisateurs derrière
349 
+quelques adresses IP. Tor, de ce point de vue, n'est pas très différent
350 
+d'AOL.</p>
351 
+
352 
+<p>En dernier lieu, souvenez-vous que les nœuds Tor fonctionnent avec des <a
353 
+href="<page faq>#ExitPolicies">stratégies de sortie
354 
+individuelles</a>. Beaucoup de relais Tor n'autorisent aucune sortie de
355 
+connexion. Parmi ceux qui effectivement autorisent des sorties de connexion,
356 
+beaucoup peuvent déjà ne pas autoriser l'accès à votre service. Lorsque vous
357 
+procédez au bannissement des nœuds, vous devriez sélectionner selon les
358 
+stratégies de sortie et ne bannir que ceux qui autorisent ces connexions. Et
359 
+souvenez-vous que les stratégies de sortie peuvent changer (ainsi que plus
360 
+globalement, la liste des nœuds sur le réseau).</p>
361 
+
362 
+<p>Si vous désirez vraiment bannir des noeuds, nous fournissons une <a
363 
+href="https://check.torproject.org/cgi-bin/TorBulkExitList.py">liste des
364 
+relais Tor existants</a> ou une <a href="<page tordnsel/index>">liste basée
365 
+sur le DNS que vous pouvez interroger</a>.
366 
+</p>
367 
+
368 
+<p>
369 
+(Certains administrateurs système bloquent des plages d'adresses IP en
370 
+raison d'une stratégie officielle ou de motif d'abus mais certains nous ont
371 
+également demandé des informations sur comment mettre en liste blanche les
372 
+noeuds de sortie Tor car ils voulaient mettre en place un accès à leurs
373 
+systèmes uniquement par Tor. Ces scripts sont également utilisables pour
374 
+mettre en liste blanche).
375 
+</p>
376 
+
377 
+<a id="TracingUsers"></a>
378 
+<h3><a class="anchor" href="#TracingUsers">J'ai une raison impérieuse de
379 
+retrouver la trace d'un utilisateur de Tor. Pouvez-vous m'aider ?</a></h3>
380 
+
381 
+<p>
382 
+Les développeurs de Tor ne peuvent rien pour retrouver la trace des
383 
+utilisateurs de Tor. Les mêmes protections qui empêchent les méchants de
384 
+violer l'anonymat apporté par Tor nous empêchent, nous aussi, de voir ce qui
385 
+se passe.
386 
+</p>
387 
+
388 
+<p>
389 
+Certains fans ont suggéré que nous révisions la conception de Tor en y
390 
+incluant une <a href="<page faq>#Backdoor">porte dérobée (backdoor)</a>.
391 
+Nous avons deux problèmes avec cette idée. Premièrement, cela affaiblirait
392 
+bien trop le système. Avoir une façon centralisée de lier les utilisateurs à
393 
+leurs activités serait la porte ouverte à toutes sortes d'attaques, et les
394 
+méthodes nécessaires à la bonne gestion de cette responsabilité sont énormes
395 
+et pour l'instant irrésolues. En second lieu, <a
396 
+href="#WhatAboutCriminals">en aucune façon les criminels ne se feraient
397 
+prendre par cette méthode</a>, puisqu'ils utiliseraient d'autres moyens pour
398 
+se rendre anonymes (usurpation d'identité, effraction dans des ordinateurs
399 
+utilisés ensuite comme rebonds, etc.)
400 
+</p>
401 
+
402 
+<p>
403 
+Ceci ne signifie pas que Tor est invulnérable. Les méthodes traditionnelles
404 
+de police sont toujours efficaces contre Tor, comme l'audition des suspects,
405 
+la surveillance et le monitoring de claviers, la rédaction d'analyses
406 
+stylistiques, les opérations sous couverture, et autres méthodes classiques
407 
+d'investigation.
408 
+</p>
409 
+
410 
+<a id="RemoveContent"></a>
411 
+<h3><a class="anchor" href="#RemoveContent">Je veux supprimer un contenu d'une
412 
+adresse-oignon.</a></h3>
413 
+<p>The Tor Project does not host, control, nor have the ability to discover the
414 
+owner or location of a .onion address.  The .onion address is an address
415 
+from <a href="<page hidden-services>">a hidden service</a>.  The name you
416 
+see ending in .onion is a hidden service descriptor.  It's an automatically
417 
+generated name which can be located on any Tor relay or client anywhere on
418 
+the Internet.  Hidden services are designed to protect both the user and
419 
+service provider from discovering who they are and where they are from.  The
420 
+design of hidden services means the owner and location of the .onion site is
421 
+hidden even from us.</p>
422 
+<p>Mais souvenez-vous que cela ne signifie pas que les services cachés sont
423 
+invulnérables. Les techniques traditionnelles de Police sont toujours très
424 
+efficaces contre elles, telles que l'interrogatoire de suspects, la
425 
+surveillance et le monitoring de claviers, la rédaction d'analyses
426 
+stylistiques, les opérations sous couverture, et autres méthodes classiques
427 
+d'investigation.</p>
428 
+<p>If you have a complaint about child pornography, you may wish to report it
429 
+to the National Center for Missing and Exploited Children, which serves as a
430 
+national coordination point for investigation of child pornography: <a
431 
+href="http://www.missingkids.com/">http://www.missingkids.com/</a>.  We do
432 
+not view links you report.</p>
433 
+
434 
+<a id="LegalQuestions"></a>
435 
+<h3><a class="anchor" href="#LegalQuestions">J'ai des questions juridiques au
436 
+sujet de l'utilisation malveillante.</a></h3>
437 
+
438 
+<p>Nous ne sommes que les développeurs. Nous pouvons répondre aux questions
439 
+d'ordre technique, mais nous ne sommes pas en mesure de répondre aux
440 
+problèmes et aspects légaux. </p>
441 
+
442 
+<p>Veuillez consulter la page des <a href="<page eff/tor-legal-faq>">FAQ
443 
+juridiques</a> et contacter EFF directement si vous avez d'autres questions
444 
+d'ordre juridique. </p>
445 
+
446 
+  </div>
447 
+
448 
+
449 
+#include <foot.wmi>
fr/faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,1262 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22360 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor FAQ" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>FAQ Tor</h2>
17 
+<hr />
18 
+
19 
+<p>Questions générales:</p>
20 
+<ul>
21 
+<li><a href="#WhatIsTor">Qu'est-ce-que Tor?</a></li>
22 
+<li><a href="#Torisdifferent">En quoi Tor est-il différent des autres proxy
23 
+?</a></li>
24 
+<li><a href="#CompatibleApplications">Quels programmes puis-je utiliser avec Tor
25 
+?</a></li>
26 
+<li><a href="#WhyCalledTor">Pourquoi s'appelle-t-il Tor ?</a></li>
27 
+<li><a href="#Backdoor">Y a-t-il une porte dérobée dans Tor ?</a></li>
28 
+<li><a href="#DistributingTor">Puis-je distribuer Tor sur le CD de mon magazine
29 
+?</a></li>
30 
+<li><a href="#SupportMail">Comment puis-je obtenir une réponse à mon email de
31 
+demande de support sur Tor ?</a></li>
32 
+<li><a href="#WhySlow">Pourquoi Tor est-il si lent ?</a></li>
33 
+<li><a href="#Funding">Que pourrait faire le Projet Tor avec davantage de fonds
34 
+?</a></li>
35 
+</ul>
36 
+
37 
+<p>Compilation et Installation:</p>
38 
+<ul>
39 
+<li><a href="#HowUninstallTor">Comment puis-je désinstaller Tor ?</a></li>
40 
+<li><a href="#PGPSigs">Que sont ces fichiers "sig" sur la page de téléchargement
41 
+?</a></li>
42 
+<li><a href="#CompileTorWindows">Comment compiler Tor sous Windows ?</a></li>
43 
+<li><a href="#VirusFalsePositives">Pourquoi mon binaire exécutable de Tor semble
44 
+avoir un virus ou un spyware ?</a></li>
45 
+<li><a href="#LiveCD">Existe-t-il un LiveCD ou un autre pack incluant Tor ?</a></li>
46 
+</ul>
47 
+
48 
+<p>Faire fonctionner Tor:</p>
49 
+
50 
+<p>Utiliser un client Tor:</p>
51 
+<ul>
52 
+<li><a href="#ChooseEntryExit">Puis-je contrôler quels noeuds (ou pays) sont
53 
+utilisés comme point d'entrée ou de sortie ?</a></li>
54 
+</ul>
55 
+
56 
+<p>Faire fonctionner un noeud Tor:</p>
57 
+<ul>
58 
+<li><a href="#RelayFlexible">Quelle stabilité doit avoir mon noeud ?</a></li>
59 
+<li><a href="#ExitPolicies">Je veux faire fonctionner un noeud mais je ne veux
60 
+pas avoir à gérer de problèmes juridiques.</a></li>
61 
+<li><a href="#RelayOrBridge">Devrais-je faire fonctionner un noeud normal ou une
62 
+passerelle ?</a></li>
63 
+<li><a href="#RelayMemory">Pourquoi mon relais Tor consomme autant de mémoire
64 
+?</a></li>
65 
+<li><a href="#WhyNotNamed">Pourquoi mon noeud Tor n'a pas de nom ?</a></li>
66 
+</ul>
67 
+
68 
+<p>Faire fonctionner un service caché par Tor:</p>
69 
+
70 
+<p>Anonymat et Sécurité:</p>
71 
+<ul>
72 
+<li><a href="#KeyManagement">Dites-m'en plus sur les clefs utilisées par
73 
+Tor.</a></li>
74 
+</ul>
75 
+
76 
+<p>Les autres spécifications qui ne sont pas (encore) implémentées:</p>
77 
+<ul>
78 
+<li><a href="#EverybodyARelay">Vous devriez faire que chaque utilisateur de Tor
79 
+soit un noeud.</a></li>
80 
+</ul>
81 
+
82 
+<p>Abus</p>
83 
+<ul>
84 
+<li><a href="#Criminals">Est-ce-que Tor permet aux criminels de faire des choses
85 
+répréhensibles ?</a></li>
86 
+<li><a href="#RespondISP">Comment puis-je répondre à mon FAI à propos de mon
87 
+noeud de sortie ?</a></li>
88 
+</ul>
89 
+
90 
+<p>For other questions not yet on this version of the FAQ, see the <a
91 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">wiki
92 
+FAQ</a> for now.</p>
93 
+
94 
+<hr />
95 
+
96 
+<a id="General"></a> <a id="WhatIsTor"></a>
97 
+<h3><a class="anchor" href="#WhatIsTor">Qu'es-ce-que Tor ?</a></h3>
98 
+
99 
+<p>
100 
+Le nom "Tor" peut faire référence à plusieurs composants distincts.
101 
+</p>
102 
+
103 
+<p>
104 
+Le logiciel Tor est un programme que vous pouvez exécuter sur votre
105 
+ordinateur qui vous aide à être en sécurité sur Internet. Tor vous protège
106 
+en faisant rebondir vos communications sur un réseau distribué de relais
107 
+maintenus par des volontaires partout dans le monde: il empêche qu'une
108 
+tierce personne scrutant votre connexion internet connaisse les sites que
109 
+vous visitez, et empêche également les sites que vous visitez de connaître
110 
+votre position géographique. Cet ensemble de relais bénévoles est appelé le
111 
+réseau Tor. Vous pouvez en apprendre davantage sur la façon dont Tor
112 
+fonctionne en lisant la <a href = "<page overview>">page de
113 
+présentation</a>.
114 
+</p>
115 
+
116 
+<p>
117 
+Le Projet Tor est une association à but non lucratif qui maintient et
118 
+développe le logiciel Tor.
119 
+</p>
120 
+
121 
+<hr />
122 
+
123 
+<a id="Torisdifferent"></a>
124 
+<h3><a class="anchor" href="#Torisdifferent">En quoi Tor est-il différent des
125 
+autres proxy ?</a></h3>
126 
+<p>
127 
+Typiquement, un fournisseur de proxy met en place un serveur quelque part
128 
+sur Internet et vous permet de l'utiliser pour relayer votre trafic.  Cela
129 
+crée une architecture simple et facile à maintenir.  Les utilisateurs
130 
+entrent et sortent tous par le même serveur.  Le fournisseur peut demander
131 
+des frais d'usage pour l'utilisation du proxy, ou finance ses coûts par la
132 
+publicité sur le serveur.  Dans la configuration la plus simple, vous n'avez
133 
+rien à installer. Il vous suffit de pointer votre navigateur vers l'adresse
134 
+du serveur proxy.  Ces fournisseurs de proxy simple sont des solutions
135 
+correctes si vous ne voulez pas de protection pour votre vie privée et
136 
+d'anonymat en ligne et que vous faites confiance au prestataire.  Certains
137 
+fournisseurs de proxy simple utilisent SSL pour sécuriser votre connexion
138 
+entre vous et eux.  Cela peut vous protéger contre des oreilles indiscrètes,
139 
+telles que celles dans les cafés offrant un accès Internet wifi gratuit.
140 
+</p>
141 
+<p>
142 
+Les fournisseurs de proxy simple créent également un point de défaillance
143 
+unique.  Le fournisseur sait qui vous êtes et où vous naviguez sur
144 
+Internet.  Ils peuvent voir tout le trafic qui passe par leur serveur.  Dans
145 
+certains cas, ils peuvent voir votre trafic chiffré car ils le relayent à
146 
+votre site bancaire ou aux sites de vente en lignee.  Vous devez présumer
147 
+que ce fournisseur ne fasse pas n'importe quoi, comme regarder votre trafic
148 
+ou injecter ses propres annonces dans votre flux et également qu'il
149 
+n'enregistre pas vos coordonnées personnelles.
150 
+</p>
151 
+<p>
152 
+Tor envoie votre trafic à travers au moins 3 serveurs différents avant de
153 
+l'envoyer à la destination.  Tor ne modifie pas ni même ne sait ce que vous
154 
+envoyez à travers lui.  Il relaie simplement votre trafic, totalement
155 
+chiffré par le réseau Tor et le fait sortir quelque part ailleurs dans le
156 
+monde, totalement préservé.  Le client Tor est nécessaire parce que nous
157 
+supposons que vous faites confiance à votre ordinateur local.  Le client Tor
158 
+gère le chiffrement et le chemin à travers le réseau.  Les noeuds situés
159 
+partout dans le monde transmettent simplement entre eux des paquets
160 
+chiffrés.</p>
161 
+<p>
162 
+<dl>
163 
+<dt>Le premier serveur ne voit-il pas qui je suis ?</dt><dd>C'est possible. Un mauvais premier serveur peut observer le trafic Tor
164 
+chiffré venant de votre ordinateur.  Il ne sait toutefois pas qui vous êtes
165 
+et ce que vous faîtes sur Tor.  En gros, il voit "Cette adresse IP utilise
166 
+Tor".  L'utilisation de Tor est légale à travers le monde entier, donc
167 
+utiliser Tor en lui-même ne pose pas de problème.  Vous êtes protégé, le
168 
+noeud ne pouvant pas vous identifier et savoir ou vous aller sur l'Internet.</dd>
169 
+<dt>Le troisième serveur ne voit-il pas mon trafic ?</dt><dd>C'est possible. Un mauvais dernier serveur peut voir le trafic que vous avez
170 
+envoyé dans Tor.  Il ne peut savoir qui a émis ce trafic.  Si vous utilisez
171 
+le chiffrement, comme lorsque vous consultez un site web de banque, de
172 
+commerce en ligne ou que vous utilisez des emails chiffrés, il connaîtra
173 
+uniquement la destination.  Il ne sera pas capable de voir les données à
174 
+l'intérieur du flux de trafic.  Vous êtes protégé de ce noeud qui ne peut
175 
+savoir ni qui vous êtes et si vous utilisez le chiffrement,ni quelles sont
176 
+les données que vous envoyez à votre destinataire.</dd>
177 
+</dl>
178 
+</p>
179 
+
180 
+<hr />
181 
+
182 
+<a id="CompatibleApplications"></a>
183 
+<h3><a class="anchor" href="#CompatibleApplications">Quels programmes puis-je
184 
+utiliser avec Tor ?</a></h3>
185 
+
186 
+<p>
187 
+Il y a deux étapes pour "Torifier" un programme: anonymat au niveau de la
188 
+connexion et anonymat au niveau de l'application.  L'anonymat au niveau de
189 
+la connexion fait en sorte que les connexions Internet sont bien envoyées à
190 
+travers Tor.  Cette étape se fait normalement en configurant le programme
191 
+pour qu'il utilise votre client Tor comme proxy "socks", mais existe
192 
+également d'autres manières de le faire.  Pour l'anonymat au niveau
193 
+applicatif, vous devez vous assurer que les informations que l'application
194 
+envoie ne trahissent pas votre vie privée. (Même si les connexions sont
195 
+routées par Tor, vous ne voulez pas inclure d'informations sensibles comme
196 
+votre nom.) Cette deuxième étape doit être réalisée programme par programme,
197 
+ce qui explique pourquoi nous n'avons pas encore recommandé beaucoup de
198 
+programmes qui utilisent Tor correctement.
199 
+</p>
200 
+
201 
+<p>
202 
+Notre travail s'est concentré jusqu'à présent sur le navigateur web
203 
+Firefox.  Les packs sur la <a href="<page download>">page de
204 
+téléchargement</a> installent automatiquement l'<a href="<page
205 
+torbutton/index>">extension Firefox Torbutton</a> si vous avez installé
206 
+Firefox. Depuis la version 1.2.0, Torbutton gère la majorité des problèmes
207 
+au niveau connexion et au niveau applicatif.
208 
+</p>
209 
+
210 
+<p>
211 
+There are plenty of other programs you can use with Tor, but we haven't
212 
+researched the application-level anonymity issues on them well enough to be
213 
+able to recommend a safe configuration. Our wiki has a list of instructions
214 
+for <a
215 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">Torifying
216 
+specific applications</a>. There's also a <a
217 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">list
218 
+of applications that help you direct your traffic through Tor</a>.  Please
219 
+add to these lists and help us keep them accurate!
220 
+</p>
221 
+
222 
+<hr />
223 
+
224 
+<a id="WhyCalledTor"></a>
225 
+<h3><a class="anchor" href="#WhyCalledTor">Pourquoi s'appelle-t-il Tor ?</a></h3>
226 
+
227 
+<p>
228 
+Parce que Tor est le réseau du routage en oignon. Lorsque nous travaillions
229 
+sur les spécifications et l'implémentation de la nouvelle génération de
230 
+routage en oignon en 2001-2002, nous disions aux gens que nous étions en
231 
+train de travailler sur le routage en oignon et ils nous répondaient:
232 
+"Parfait. Lequel ?". Même si le routage en oignon est devenu un terme
233 
+standard, Tor est né du véritable <a
234 
+href="http://www.onion-router.net/">projet de routage en oignon</a> organisé
235 
+par le Naval Research Lab.
236 
+</p>
237 
+
238 
+<p>
239 
+(C'est également une traduction fine de l'Allemand et du Turque)
240 
+</p>
241 
+
242 
+<p>
243 
+Note: même s'il provient à l'origine d'un acronyme, Tor n'est pas épelé
244 
+"TOR". Seule la première lettre est en majuscule. En fait, nous distinguons
245 
+généralement les personnes qui n'ont rien lu de notre site web (et ont
246 
+appris au contraire tout ce qu'il savent de Tor à partir d'articles de news)
247 
+par le fait qu'il l'épellent incorrectement.
248 
+</p>
249 
+
250 
+<hr />
251 
+
252 
+<a id="Backdoor"></a>
253 
+<h3><a class="anchor" href="#Backdoor">Y a-t-il une porte dérobée dans Tor ?</a></h3>
254 
+
255 
+<p>
256 
+Il n'y a absolument aucune porte dérobée dans Tor. Personne ne nous a
257 
+demandé d'en mettre une et nous connaissons des juristes qui affirment qu'il
258 
+est peu probable que quelqu'un nous demande de le faire dans notre
259 
+juridiction (U.S.). Nous combattrons toute demande sur ce sujet et il est
260 
+très probable que nous gagnerions.
261 
+</p>
262 
+
263 
+<p>
264 
+Nous pensons que mettre une porte dérobée dans Tor serait vraiment
265 
+irresponsable pour nos utilisateurs, et constituerait un mauvais précédent
266 
+pour les logiciels de sécurité en général.  Poser une porte dérobée dans
267 
+notre logiciel de sécurité reviendrait à ruiner notre réputation
268 
+professionnelle. Personne ne ferait plus jamais confiance à notre logiciel
269 
+et ce, pour d'excellentes raisons!
270 
+</p>
271 
+
272 
+<p>
273 
+Mais ceci dit, il existe encore de nombreuses attaques subtiles que des
274 
+personnes peuvent essayer. Quelqu'un pourrait se faire passer pour nous ou
275 
+pénétrer dans nos ordinateurs, ou quelque chose comme ça. Tor est open
276 
+source, et vous devriez toujours vérifier le code source (ou au moins les
277 
+diffs depuis la dernière version)  pour trouver des choses suspectes. Si
278 
+nous (ou les distributeurs) ne vous donnons pas le code source, c'est le
279 
+signe que quelque chose de suspect pourrait se dérouler. Vous devriez
280 
+également consulter les <a href="<page verifying-signatures>">signatures
281 
+PGP</a> de versions, pour vous assurer que personne n'a attaqué les sites de
282 
+distribution.
283 
+</p>
284 
+
285 
+<p>
286 
+Toutefois , il est possible que des bugs pouvant affecter votre anonymat
287 
+subsistent accidentellement dans Tor. Nous trouvons et corrigeons
288 
+régulièrement les bugs liés à l'anonymat donc assurez-vous de toujours
289 
+utiliser la dernière version de Tor.
290 
+</p>
291 
+
292 
+<hr />
293 
+
294 
+<a id="DistributingTor"></a>
295 
+<h3><a class="anchor" href="#DistributingTor">Puis-je distribuer Tor sur le CD
296 
+de mon magazine ?</a></h3>
297 
+
298 
+<p>
299 
+Oui.
300 
+</p>
301 
+
302 
+<p>
303 
+Le logiciel Tor est <a href="https://www.fsf.org/">un logiciel
304 
+libre</a>. Cela signifie que nous vous donnons le droit de le redistribuer
305 
+même modifié, gratuitement ou contre redevance. Vous n'avez pas besoin de
306 
+nous demander une autorisation spéciale.
307 
+</p>
308 
+
309 
+<p>
310 
+En revanche, si vous désirez redistribuer le logiciel Tor ,vous devez suivre
311 
+les règles de notre <a href="<gitblob>LICENSE">LICENCE</a>.  Globalement,
312 
+cela signifie que vous devez inclure le fichier de notre LICENCE avec toute
313 
+partie du logiciel Tor que vous distribuez.
314 
+</p>
315 
+
316 
+<p>
317 
+La plupart des gens qui nous posent cette question, ne veulent pas seulement
318 
+distribuer le logiciel Tor. Ils veulent distribuer les Packs Tor qui
319 
+comprennent généralement <a
320 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> et <a
321 
+href="<page vidalia/index>">Vidalia</a>.  Vous devrez également respecter
322 
+les licences de ces programmes. Les deux sont distribués sous la <a
323 
+href="https://www.fsf.org/licensing/licenses/gpl.html">licence GNU General
324 
+Public License</a>. Le moyen le plus simple pour obéir à ces licences est
325 
+d'inclure le code source de ces programmes partout où vous incluez les Pack
326 
+eux-mêmes. Cherchez les paquets "source" sur la <a href="<page
327 
+vidalia/index>">page Vidalia</a> et la <a
328 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/">page de
329 
+téléchargement de Polipo</a>.
330 
+</p>
331 
+
332 
+<p>
333 
+En outre, vous devriez vous assurer de ne pas porter confusion à vos
334 
+lecteurs sur ce que Tor est, qui l'a réalisé et quelles fonctionnalités il
335 
+permet (et celles qu'il ne fournit pas). Voir notre <a href="<page
336 
+trademark-faq>">FAQ sur la marque Tor</a> pour plus de détails.
337 
+</p>
338 
+
339 
+<p>
340 
+Enfin, vous devez réaliser que nous publions fréquemment de nouvelles
341 
+versions du logiciel Tor et parfois il y a des changements incompatibles
342 
+avec les versions précédentes. Donc, si vous distribuez une version
343 
+particulière du logiciel Tor, il ne sera peut-être pas pris en charge
344 
+&mdash; ou même ne fonctionnera pas &mdash; six mois plus tard. Ceci est une
345 
+réalité de la vie de tous les logiciels de sécurité en cours de
346 
+développement important.
347 
+</p>
348 
+
349 
+<hr />
350 
+
351 
+<a id="SupportMail"></a>
352 
+<h3><a class="anchor" href="#SupportMail">Comment puis-je obtenir une réponse à
353 
+mon email de demande de support sur Tor ?</a></h3>
354 
+
355 
+<p>
356 
+Beaucoup de gens envoient des emails en privé aux développeurs de Tor, ou
357 
+envoient un mail sur notre <a href="<page contact>">liste de diffusion
358 
+interne</a>, avec des questions sur leur configuration &mdash; ils ne
359 
+peuvent pas faire fonctionner correctement leur pare-feu, ils ne peuvent pas
360 
+configurer Polipo correctement, et ainsi de suite. Parfois, nos bénévoles
361 
+peuvent répondre à ces emails, mais généralement ils ont besoin de passer la
362 
+majorité de leur temps à des tâches de développement qui profiteront à plus
363 
+de personnes. Cela est particulièrement vrai si votre question est déjà
364 
+couverte dans la <a href="<page documentation>">documentation</a> ou dans
365 
+cette FAQ.
366 
+</p>
367 
+
368 
+<p>
369 
+Donc, si nous ne répondons pas à votre message, vérifiez d'abord la <a
370 
+href="<page documentation>">page de documentation</a>, ainsi que cette FAQ,
371 
+pour vous assurer que votre question n'a pas déjà de réponse. Ensuite, lisez
372 
+<a href="http://www.catb.org/~esr/faqs/smart-questions.html"> "Comment poser
373 
+des questions de manière futée"</a>. Si cela ne vous aide pas, notez que
374 
+nous avons <a href="<page documentation>#Support">un canal IRC</a> où vous
375 
+pouvez poser vos questions (mais si elles sont encore ouvertes, mal formées
376 
+ou sans lien avec Tor, vous n'obtiendrez probablement pas beaucoup d'aide
377 
+là-bas). Enfin, les personnes sur la <a href="<page
378 
+documentation>#MailingLists">liste de diffusion or-talk</a> peuvent vous
379 
+fournir des conseils, si d'autres ont rencontré les mêmes
380 
+problèmes. Assurez-vous d'en consulter <a
381 
+href="http://archives.seul.org/or/talk/">les archives</a>.
382 
+</p>
383 
+
384 
+<p>
385 
+Une autre stratégie consiste à <a href="<page docs/tor-doc-relay>">installer
386 
+un noeud Tor quelques temps</a> et/ou <a href="<page donate>">de donner de
387 
+l'argent</a> ou <a href="<page volunteer>">du temps</a>. Nous sommes plus
388 
+enclins à accorder de l'attention aux personnes qui ont manifesté leur
389 
+intérêt et leur engagement envers la communauté Tor.
390 
+</p>
391 
+
392 
+<p>
393 
+Si vous trouvez votre réponse, merci de la coller sur le canal IRC ou sur la
394 
+liste de diffusion et de répondre aux questions des autres.
395 
+</p>
396 
+
397 
+<hr />
398 
+
399 
+<a id="WhySlow"></a>
400 
+<h3><a class="anchor" href="#WhySlow">Pourquoi Tor est-il si lent ?</a></h3>
401 
+
402 
+<p>
403 
+Il y plusieurs raisons au fait que le réseau Tor soit actuellement lent.
404 
+</p>
405 
+
406 
+<p>
407 
+Avant de répondre, vous devez comprendre que Tor ne deviendra jamais très
408 
+rapide. Votre trafic est partagé à travers les ordinateurs de volontaires
409 
+sur toute la surface de la planète et il y aura toujours des goulots
410 
+d'étranglement et de la latence sur le réseau. Ne vous attendez pas à
411 
+trouver une bande passante comme celle d'une Université à travers Tor.
412 
+</p>
413 
+
414 
+<p>
415 
+Mais cela ne signifie pas que la situation ne puisse être améliorée. Le
416 
+réseau Tor actuel est assez peu étendu comparé au nombre de personnes qui
417 
+tentent de l'utiliser et beaucoup de ces personnes ne comprennent pas ou ne
418 
+font pas attention au fait que Tor ne peut pas gérer une charge réseau de
419 
+partage de fichiers.
420 
+</p>
421 
+
422 
+<p>
423 
+Pour des réponses plus précises, consultez le <a
424 
+href="https://blog.torproject.org/blog/why-tor-is-slow">l'article du blog de
425 
+Roger sur ce sujet</a>. qui inclus un PDF détaillé et une présentation
426 
+vidéo.
427 
+</p>
428 
+
429 
+<p>
430 
+Que pouvez-vous faire pour aider ?
431 
+</p>
432 
+
433 
+<ul>
434 
+
435 
+<li>
436 
+<a href="<page docs/tor-doc-relay>">Configurez votre noeud Tor pour relayer
437 
+du trafic pour les autres</a>. Aidez à l'extension du réseau Tor pour que
438 
+nous puissions gérer tous les utilisateurs qui ont besoin de vie privée et
439 
+de sécurité sur Internet.
440 
+</li>
441 
+
442 
+<li>
443 
+<a href="<page gui/index>">Aidez-nous à rendre Tor plus utilisable</a>. Nous
444 
+avons tout particulièrement besoin de personne qui peuvent simplifier la
445 
+configuration d'un noeud Tor. Nous avons besoin d'une documentation claire
446 
+pour aider les gens tout au long du processus d'installation.
447 
+</li>
448 
+
449 
+<li>
450 
+Il existe des goulots d'étranglement dans le réseau Tor actuel. Aidez-nous à
451 
+expérimenter des moyens de trouver l'origine des problèmes de manière à ce
452 
+que nous puissions nous concentrer dessus.
453 
+</li>
454 
+
455 
+<li>
456 
+There are some steps that individuals can take to improve their Tor
457 
+performance. <a
458 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/FireFoxTorPerf">You
459 
+can configure your Firefox to handle Tor better</a>, <a
460 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
461 
+Polipo with Tor</a>, or you can try <a href="<page download>">upgrading to
462 
+the latest version of Tor</a>.  If this works well, please help by
463 
+documenting what you did, and letting us know about it.
464 
+</li>
465 
+
466 
+<li>
467 
+Tor a également besoin de quelques modifications d'architecture. Un
468 
+changement important est de commencer à fournir <a href="#EverybodyARelay">
469 
+un meilleur service aux personnes qui relaient le trafic</a>. Nous
470 
+travaillons sur ce point, et nous terminerons d'autant plus rapidement que
471 
+nous aurons de temps à passer dessus.
472 
+</li>
473 
+
474 
+<li>
475 
+Aider à faire d'autres choses pour que nous puissions nous concentrer sur le
476 
+travail pénible. Merci de prendre un moment pour faire le point sur vos
477 
+compétences et vos centres d'intérêts, puis de jeter un oeil sur <a
478 
+href="<page volunteer>">notre page de bénévoles</a>.
479 
+</li>
480 
+
481 
+<li>
482 
+Aidez-nous à trouver des sponsors pour Tor. Vous travaillez dans une
483 
+entreprise ou un organisme gouvernemental qui utilise Tor ou qui a un besoin
484 
+dans la protection de la vie privée sur Internet, par exemple parcourir des
485 
+sites Internet concurrents discrètement, ou de se connecter vers un serveur
486 
+à la maison quand vous êtes sur la route sans l'indiquer à vos partenaires ?
487 
+Si votre organisation a un intérêt à rendre le réseau Tor continuellement
488 
+opérable, merci de lui proposer de financer Tor. Sans les sponsors, Tor
489 
+restera toujours aussi lent.
490 
+</li>
491 
+
492 
+<li>
493 
+Si vous ne pouvez pas nous aider tel qu'indiqué ci-dessus, vous pouvez
494 
+toujours <a href="<page donate>">donner un peu d'argent à notre
495 
+cause</a>. C‭a aide vraiment !
496 
+</li>
497 
+
498 
+</ul>
499 
+
500 
+<hr />
501 
+
502 
+<a id="Funding"></a>
503 
+<h3><a class="anchor" href="#Funding">Que pourrait faire le Projet Tor avec
504 
+davantage de fonds ?</a></h3>
505 
+
506 
+<p>
507 
+Nous disposons maintenant d'environ 1800 noeuds qui permettent de
508 
+transmettre un trafic moyen de 150Mo/s. Nous avons plusieurs milliers
509 
+d'utilisateurs actifs. Mais le réseau Tor n'est pas encore autonome.
510 
+</p>
511 
+
512 
+<p>
513 
+Il y a six points de développement ou de maintenance qui requièrent de
514 
+l'attention:
515 
+</p>
516 
+
517 
+<ul>
518 
+
519 
+<li>
520 
+Extensibilité: Nous devons conserver l'extensibilité et la décentralisation
521 
+dans l'architecture de Tor pour qu'il puisse gérer des milliers de relais et
522 
+des millions d'utilisateurs. La version stable à venir constitue une
523 
+amélioration majeure, mais il y a beaucoup à faire pour maintenir Tor rapide
524 
+et stable.
525 
+</li>
526 
+
527 
+<li>
528 
+Assistance aux utilisateurs: Avec autant d'utilisateurs, beaucoup de
529 
+personnes posent souvent des questions et offrent leur aide et ainsi de
530 
+suite. Nous avons besoin d'une documentation propre, et nous avons besoin de
531 
+mettre de l'effort dans la coordination des contributeurs.
532 
+</li>
533 
+
534 
+<li>
535 
+Support des noeuds: le réseau Tor est géré par des contributeurs, mais ils
536 
+ont besoin de rapides corrections de bugs, d'explications lorsque les choses
537 
+tournent mal, de rappels de mise à jour, et ainsi de suite. Le réseau
538 
+lui-même est un bien commun, et il est nécéssaire de dépenser un peu
539 
+d'énergie afin d'être sûr que les opérateurs de noeud restent heureux. Nous
540 
+devons également travailler sur <a href="#RelayOS">la stabilité</a> de
541 
+certaines plates-formes &mdash; par exemple, les noeuds Tor ont actuellement
542 
+des problèmes sur Win XP.
543 
+</li>
544 
+
545 
+<li>
546 
+Convivialité: Au-delà de la documentation, nous avons aussi besoin de
547 
+travailler sur la convivialité du logiciel lui-même. Cela concerne les
548 
+installateurs, les interfaces graphiques conviviales, une configuration
549 
+facile de l'interface avec d'autres applications ainsi que l'automatisation
550 
+de l'ensemble des étapes difficiles et confuses dans Tor. Nous avons lancé
551 
+le sujet avec le <a href="<page gui/index>">concours IHM</a>, mais il reste
552 
+encore beaucoup de travail &mdash; la convivialité des logiciels de
553 
+protection de la vie privée n'a jamais été grande.
554 
+</li>
555 
+
556 
+<li>
557 
+Incitations: Nous devons travailler sur les moyens d'encourager les gens à
558 
+configurer leur noeud Tor comme un noeud de sortie plutôt que de l'utiliser
559 
+comme un simple client. <a href="#EverybodyARelay">Nous avons besoin de
560 
+facliter la démarche pour configurer un noeud, et nous devons inciter les
561 
+gens à le faire</a>.
562 
+</li>
563 
+
564 
+<li>
565 
+Recherche: le monde des communications anonymes est plein de surprises et de
566 
+pièges. Pendant notre temps libre, nous devons également organiser des
567 
+conférences sur l'anonymat et la vie privée comme <a
568 
+href="http://petsymposium.org/">PETS</a>. Nous avons identifié une série de
569 
+<a href="<page volunteer>#Research">questions fondamentales sur la recherche
570 
+autour de Tor</a> qui nous aideront à mieux comprendre comment rendre Tor
571 
+plus sûr contre les diverses attaques existantes. Bien entendu, il y a
572 
+plusieurs questions de recherche en attente derrière elles.
573 
+</li>
574 
+
575 
+</ul>
576 
+
577 
+<p>
578 
+Nous continuons à avancer sur tous ces domaines, mais à ce rythme, <a
579 
+href="#WhySlow">le réseau Tor croît plus vite que peuvent suivre les
580 
+développeurs</a>. Il est maintenant temps de recruter plus de développeurs
581 
+afin que nous puissions continuer à étendre le réseau.
582 
+</p>
583 
+
584 
+<p>
585 
+Nous sommes aussi ravis de faire face aux problèmes connexes, tels que la
586 
+résistance à la censure.
587 
+</p>
588 
+
589 
+<p>
590 
+Nous sommes fiers d'avoir <a href="<page sponsors>">le parrainage et le
591 
+soutien</a> du Réseau Omidyar, de l'International Broadcasting Bureau, de
592 
+Bell Security Solutions, de l'Electronic Frontier Foundation, de plusieurs
593 
+organismes gouvernementaux et de groupes de recherche ainsi que des
594 
+centaines de contributeurs privés.
595 
+</p>
596 
+
597 
+<p>
598 
+Toutefois, ce soutien n'est pas suffisant pour se maintenir Tor au niveau
599 
+des changements dans le monde de la vie privée sur Internet. Merci <a
600 
+href="<page donate>">de faire un don</a> pour le projet, ou de <a
601 
+href="<page contact>">contacter</a> notre directeur exécutif pour plus
602 
+d'informations sur comment verser des subventions ou des dons importants.
603 
+</p>
604 
+
605 
+<hr />
606 
+
607 
+<a id="HowUninstallTor"></a>
608 
+<h3><a class="anchor" href="#HowUninstallTor">Comment puis-je désinstaller Tor
609 
+?</a></h3>
610 
+
611 
+<p>
612 
+Cela dépend entièrement de la manière dont vous l'avez installé et du
613 
+système d'exploitation que vous possédez. Si vous avez installé un paquet,
614 
+alors, votre paquet peut se désinstaller. Les paquets Windows incluent des
615 
+programmes de désinstallation. La bonne façon de supprimer complètement Tor,
616 
+Vidalia, Torbutton pour Firefox, et Polipo sur n'importe quelle version de
617 
+Windows est décrite comme suit:
618 
+</p>
619 
+
620 
+<ol>
621 
+<li>Dans votre barre des tâches, cliquez sur Vidalia (l'oignon vert ou la tête
622 
+noire)  et choisissez sortir.</li>
623 
+<li>Faîtes un clic-droit sur la barre de tâches pour ouvrir le Gestionnaire des
624 
+Tâches. Cherchez tor.exe dans la liste des Processus. S'il tourne, faîtes un
625 
+clic-droit et choisissez Terminer le Processus.</li>
626 
+<li>Cliquez sur le bouton Démarrer, allez dans Programmes, allez dans Vidalia,
627 
+choisissez Désinstaller.  Cela supprimera le pack Vidalia qui contient Tor
628 
+et Polipo.</li>
629 
+<li>Lancez Firefox. Allez dans le menu Outils, choisissez Modules
630 
+complémentaires. Sélectionnez Torbutton.  Cliquez sur le bouton
631 
+Désinstaller.</li>
632 
+</ol>
633 
+
634 
+<p>
635 
+Si vous ne suivez pas ces étapes (par exemple essayer de désinstaller
636 
+Vidalia, Tor et Polipo alors qu'ils sont toujours en fonctionnement), vous
637 
+aurez besoin de redémarrer votre ordinateur et de supprimer à la main le
638 
+répertoire "Program Files\Vidalia Bundle".
639 
+</p>
640 
+
641 
+<p>
642 
+Pour Mac OS X, suivez les <a href="<page
643 
+docs/tor-doc-osx>#uninstall">directives de désinstallation</a>.
644 
+</p>
645 
+
646 
+<p>
647 
+Si vous avez installé à partir des sources, j'ai peur qu'il n'existe aucune
648 
+méthode facile pour désinstaller. Mais, d'un autre côté, l'installation se
649 
+déroule dans /usr/local par défaut et il devrait être assez facile d'y
650 
+trouver des instructions.
651 
+</p>
652 
+
653 
+<hr />
654 
+
655 
+<a id="PGPSigs"></a>
656 
+<h3><a class="anchor" href="#PGPSigs">Que sont ces fichiers "sig" sur la page de
657 
+téléchargement ?</a></h3>
658 
+
659 
+<p>
660 
+Ce sont des signatures PGP qui vous permettent de vérifier que les fichiers
661 
+que vous avez téléchargés sont bien ceux que vous aviez l'intention de
662 
+récupérer.
663 
+</p>
664 
+
665 
+<p>
666 
+Merci de lire la page de <a href="<page verifying-signatures>">verification
667 
+des signatures</a> pour plus de détails.
668 
+</p>
669 
+
670 
+<hr />
671 
+
672 
+<a id="CompileTorWindows"></a>
673 
+<h3><a class="anchor" href="#CompileTorWindows">Comment compiler Tor sous
674 
+Windows ?</a></h3>
675 
+
676 
+<p>
677 
+Vous pouvez essayer de suivre les étapes du fichier <a
678 
+href="<gitblob>doc/tor-win32-mingw-creation.txt">tor-win32-mingw-creation.txt</a>.
679 
+</p>
680 
+
681 
+<p>
682 
+(A noter que vous n'avez pas besoin de compiler Tor vous-même pour
683 
+l'utiliser. La majorité des gens utilisent les paquets disponibles sur <a
684 
+href="<page download>">la page de téléchargement</a>.)
685 
+</p>
686 
+
687 
+<hr />
688 
+
689 
+<a id="VirusFalsePositives"></a>
690 
+<h3><a class="anchor" href="#VirusFalsePositives">Pourquoi mon binaire
691 
+exécutable de Tor semble avoir un virus ou un spyware ?</a></h3>
692 
+
693 
+<p>
694 
+Parfois, les excès de zèle des détecteurs de virus et de spyware sous
695 
+Windows se déclenchent sur certaines parties du binaire Windows Tor. Notre
696 
+meilleure hypothèse est que ce sont des faux positifs &mdash; après tout, le
697 
+business d'anti-virus et d'anti-spyware est juste un jeu de devinettes. Vous
698 
+devriez contacter votre fournisseur et lui expliquer que vous avez un
699 
+programme qui semble avoir déclenché des faux positifs. Ou choisir un
700 
+meilleur fournisseur.
701 
+</p>
702 
+
703 
+<p>
704 
+Dans le même temps, nous vous encourageons à ne pas en rester là. Notre
705 
+travail est de fournir du code source; si vous êtes concernés, merci de <a
706 
+href="#CompileTorWindows">le recompiler vous-même</a>.
707 
+</p>
708 
+
709 
+<hr />
710 
+
711 
+<a id="LiveCD"></a>
712 
+<h3><a class="anchor" href="#LiveCD">Existe-t-il un LiveCD ou un autre pack
713 
+incluant Tor ?</a></h3>
714 
+
715 
+<p>
716 
+Il n'existe pas de LiveCD officiel à ce jour. Nous essayons de trouver de
717 
+bonnes solutions et de comprendre l'implication de nombreuses options dans
718 
+la sécurité et l'anonymat. Toutefois, vous pouvez consulter la liste
719 
+ci-dessous et juger de ce qui sera le plus adapté:
720 
+</p>
721 
+
722 
+<p>
723 
+LiveCDs:
724 
+</p>
725 
+
726 
+<ol>
727 
+<li><a href="https://amnesia.boum.org/">Le système Live Incognito (Amnesic)</a>
728 
+est un système Live destiné à préserver votre vie privée et votre anonymat:
729 
+<ul>
730 
+<li> Toutes les connexions sortantes vers Internet passent forcément à travers le
731 
+réseau Tor.</li>
732 
+<li> Aucune trace n'est laissée sur les périphériques de stockage à moins que la
733 
+question ne vous soit explicitement posée.</li>
734 
+<li> Il inclut Firefox, Tor, Torbutton, le contrôleur graphique de Tor Vidalia,
735 
+le client de messagerie instantanée Pigdin et beaucoup d'autres logiciels.</li>
736 
+<li> Il est basé sur Debian Gnu/linux et fonctionne sous l'environnement de
737 
+bureau GNOME.</li>
738 
+</ul>
739 
+<li><a href="http://tork.sourceforge.net/wiki/index.php/LiveCD">TorK LiveCD</a>
740 
+est basé sur Knoppix et orienté vers la facilité d'utilisation. Vous pouvez
741 
+travailler de manière anonyme ou non tout en étant informé par TorK des
742 
+conséquences de votre activité. Le LiveCD TorK LiveCD est expérimental, et
743 
+l'objectif est de fournir des mises à jour régulières toute l'année 2007 et
744 
+au delà.</li>
745 
+<li><a href="http://mandalka.name/privatix/">Privatix LiveCD/USB</a> est un
746 
+système live debian incluant Tor, Firefox et TorButton qui permet de
747 
+sauvegarder des marques-pages et la configuration ainsi que des données sur
748 
+une clef USB chiffrée.</li>
749 
+</li>
750 
+</ol>
751 
+
752 
+<p>
753 
+Pack Windows:
754 
+</p>
755 
+
756 
+<ol>
757 
+<li><a href="<page torbrowser/index>">Le Pack Tor Navigateur</a> pour Windows
758 
+contient un navigateur web pre-configuré et est entièrement autonome de
759 
+manière à ce que vous puissiez le faire tourner sur une clef USB.</li>
760 
+<li><a href="http://www.janusvm.com/tor_vm/">Tor VM</a> est un successeur de
761 
+JanusVM. Il a besoin de vos tests !</li>
762 
+<li><a href="http://janusvm.com/">JanusVM </a> est un noyau Linux et des
763 
+logiciels s'exécutant dans VMWare qui se trouve entre votre ordinateur
764 
+Windows et l'Internet, en vous assurant que votre trafic Internet est
765 
+nettoyé et anonyme.</li>
766 
+<li><a href="http://www.xerobank.com/xB_browser.html">xB Browser</a>,
767 
+anciennement connu sous le nom de Torpark, est un pack pour Win32 contenant
768 
+Firefox+Tor qui peut être installé sur une clef USB. Il a besoin d'une
769 
+machine avec un système d'exploitation Win32.</li>
770 
+</ol>
771 
+
772 
+<p>
773 
+Non réellement maintenu:
774 
+</p>
775 
+
776 
+<ol>
777 
+<li>Polippix / Privatlivets Fred est un LiveCD basé sur une distribution danoise
778 
+de Knoppix disposant de Tor et d'utilitaires de téléphonie chiffrée sur
779 
+IP. <a href="http://polippix.org/">Information et téléchargement</a>.</li>
780 
+<li>ELE est un LiveCD Linux qui est centré sur les logiciels de protection de la
781 
+vie privée. Il inclus Tor et vous pouvez le télécharger sur <a
782 
+href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity.net/download/ele/</a>.</li>
783 
+<li>Virtual Privacy Machine is a Linux LiveCD that includes Firefox, Privoxy,
784 
+Tor, some IRC and IM applications, and a set of ipchains rules aimed to
785 
+prevent non-Tor traffic from accidentally leaving your computer. More
786 
+information at <a
787 
+href="https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine">https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine</a>.</li>
788 
+<li>Anonym.OS est un LiveCD similaire au précédent, mais est basé sur OpenBSD
789 
+plutôt que Linux pour une sécurité maximale. Il a été conçu pour être
790 
+anonyme et sécurisé à partir de zéro, et possède donc des caractéristiques
791 
+et des limites qu'on ne retrouve pas dans d'autres LiveCD (liées à Tor ou
792 
+non). Vous pouvez obtenir plus d'informations et télécharger Anonym.OS
793 
+depuis <a href="http://theory.kaos.to/projects.html">Kaos.Theory</a>.</li>
794 
+<li>Phantomix est un LiveCD pour le surf anonyme et le chat basé sur la plus
795 
+récente KNOPPIX. Il est livré préconfiguré avec Privoxy, Tor, et
796 
+Polipo. Vous pouvez l'obtenir à partir du <a
797 
+href="http://phantomix.ytternhagen.de/">site web Phantomix</a>.</li>
798 
+</ol>
799 
+
800 
+<p>
801 
+Merci de nous contacter si vous en connaissez d'autres.
802 
+</p>
803 
+
804 
+<hr />
805 
+
806 
+<a id="ChooseEntryExit"></a>
807 
+<h3><a class="anchor" href="#ChooseEntryExit">Puis-je contrôler quels noeuds (ou
808 
+pays) sont utilisés comme point d'entrée ou de sortie ?</a></h3>
809 
+
810 
+<p>
811 
+Oui. Vous pouvez configurer vos noeuds d'entrée et de sortie préférés ainsi
812 
+qu'informer Tor sur les noeuds que vous ne désirez pas utiliser.  Les
813 
+options suivantes doivent être ajoutées à votre fichier de configuration
814 
+'torrc" ou spécifiés à partir de la ligne de commande:
815 
+</p>
816 
+<dl>
817 
+  <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
818 
+    <dd>Une liste de vos noeuds préférés à utiliser pour le premier jalon du
819 
+circuit, si possible.
820 
+    </dd>
821 
+  <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>
822 
+    <dd>Une liste de vos noeuds préférés à utiliser pour le dernier jalon du
823 
+circuit, si possible.
824 
+    </dd>
825 
+  <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>
826 
+    <dd>Une liste de noeuds à ne jamais utiliser pour construire un circuit.
827 
+    </dd>
828 
+  <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>
829 
+    <dd>Une liste de noeuds à ne jamais utiliser lors de la sélection d'une sortie.
830 
+Les noeuds listés dans <tt>ExcludeNodes</tt> sont automatiquement présents
831 
+dans cette liste.
832 
+    </dd>
833 
+</dl>
834 
+<p>
835 
+<em>Nous vous recommandons de ne pas les utiliser</em> &mdash; ils sont
836 
+présents à fin de tests et peuvent disparaître dans les prochaines
837 
+versions.  Vous disposez de la meilleure protection quand vous laissez le
838 
+soin à Tor de choisir sa propre route. Modifier les préférences sur les
839 
+noeuds d'entrée/sortie peut mettre en danger votre anonymat par des moyens
840 
+non encore identifiés à ce jour.
841 
+</p>
842 
+<p>
843 
+Les options de configuration <tt>EntryNodes</tt> et <tt>ExitNodes</tt> sont
844 
+traitées comme une requête, c'est à dire si les noeuds sont en panne ou
845 
+paraissent lents, Tor les évitera.  Vous pouvez rendre l'option obligatoire
846 
+en ajoutant <tt>StrictExitNodes 1</tt> ou <tt>StrictEntryNodes 1</tt>
847 
+&mdash; mais si vous le faites, vos connexions Tor vont cesser de
848 
+fonctionner si tous les nœuds que vous avez spécifié deviennent
849 
+inaccessibles. Consultez les <a
850 
+href="https://www.torproject.org/documentation.html.fr#NeatLinks">pages de
851 
+statut de Tor</a> pour prendre connaissance des nœuds que vous pouvez
852 
+choisir.
853 
+</p>
854 
+<p>
855 
+Au lieu de <tt>$fingerprint</tt>, vous pouvez également spécifier un code de
856 
+pays ISO3166 de 2 lettres dans les accolades (par exemple {de}), ou un motif
857 
+d'adresse IP (par exemple 255.254.0.0/8), ou un surnom de nœud. Assurez-vous
858 
+qu'il n'y a pas d'espace entre les virgules et les éléments de liste.
859 
+</p>
860 
+<p>
861 
+Si vous souhaitez accéder à un service directement par l'interface SOCKS de
862 
+Tor (par exemple en utilisant ssh via connect.c), une autre option consiste
863 
+à mettre en place un mapping interne dans votre fichier de configuration en
864 
+utilisant <tt>MapAddress</tt>. Voir la page de manuel pour plus de détails.
865 
+</p>
866 
+
867 
+<hr />
868 
+
869 
+<a id="RelayFlexible"></a>
870 
+<h3><a class="anchor" href="#RelayFlexible">Quelle stabilité doit avoir mon
871 
+noeud ?</a></h3>
872 
+
873 
+<p>
874 
+Notre objectif est de mettre facilement et correctement en place un noeud
875 
+Tor:
876 
+</p>
877 
+
878 
+<ul>
879 
+<li>Tor has built-in support for <a
880 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#LimitBandwidth">
881 
+rate limiting</a>. Further, if you have a fast link but want to limit the
882 
+number of bytes per day (or week or month) that you donate, check out the <a
883 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Hibernation">hibernation
884 
+feature</a>.
885 
+</li>
886 
+<li>Chaque noeud Tor a une <a href="#ExitPolicies">politique de sortie</a> qui
887 
+spécifie quelles sortes de connexions sont autorisées ou refusées depuis ce
888 
+noeud. Si vous ne souhaitez pas laisser des gens sortir par votre connexion,
889 
+vous pouvez configurer votre noeud pour autoriser uniquement des connexions
890 
+à d'autres relais Tor.
891 
+</li>
892 
+<li>Ce n'est pas grave si le noeud se déconnecte parfois. Les annuaires le note
893 
+rapidement et stoppent la publication d'informations sur ce noeud. Essayez
894 
+seulement de vous assurer qu'il n'est pas trop souvent déconnecté, puisque
895 
+les connexions en cours dans le noeud seront coupées.
896 
+</li>
897 
+<li>Les adresses IP dynamiques sont également bien gérées par Tor, laissez
898 
+simplement l'option de configuration Address vide et Tor tentera de la
899 
+deviner.
900 
+</li>
901 
+<li>If your relay is behind a NAT and it doesn't know its public IP (e.g. it has
902 
+an IP of 192.168.x.y), you'll need to set up port forwarding. Forwarding TCP
903 
+connections is system dependent but <a
904 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this
905 
+FAQ entry</a> offers some examples on how to do this.
906 
+</li>
907 
+<li>Votre noeud va estimer de manière passive sa capacité de bande passante et
908 
+la publier, ainsi un noeud à large bande passante attirera davantage
909 
+d'utilisateurs qu'un autre à faible bande passante. Toutefois, les noeuds à
910 
+faible bande passante sont également utiles.
911 
+</li>
912 
+</ul>
913 
+
914 
+<hr />
915 
+
916 
+<a id="RunARelayBut"></a> <a id="ExitPolicies"></a>
917 
+<h3><a class="anchor" href="#ExitPolicies">Je veux faire fonctionner un noeud
918 
+mais je ne veux pas avoir à gérer de problèmes juridiques.</a></h3>
919 
+
920 
+<p>
921 
+Impeccable, c'est exactement pour ça que nous avons créé les règles de
922 
+sortie.
923 
+</p>
924 
+
925 
+<p>
926 
+Chaque relais Tor a une politique de sortie qui spécifie quelles sont les
927 
+connexions sortantes autorisées ou refusées depuis un relais. Les stratégies
928 
+de sortie sont propagées vers les clients Tor via l'annuaire, de manière à
929 
+ce que les clients évitent automatiquement les relais de sortie qui
930 
+refuseraient d'accéder à la destination voulue. Ainsi, chaque relais peut
931 
+décider des services, hôtes et réseaux vers lesquels il veut autoriser des
932 
+connexions, cette politique est basée sur sa propre situation et sur les
933 
+abus potentiels. Lisez l'article de la FAQ à propos des <a href ="<page
934 
+faq-abuse>#TypicalAbuses"> problèmes que vous pourriez rencontrer si vous
935 
+utilisez la politique par défaut</a>, et lisez ensuite les <a
936 
+href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">
937 
+conseils de Mike Perry pour faire fonctionner un noeud de sortie avec un
938 
+harcèlement minimal</a>.
939 
+</p>
940 
+
941 
+<p>
942 
+The default exit policy allows access to many popular services (e.g. web
943 
+browsing), but <a
944 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
945 
+some due to abuse potential (e.g. mail) and some since the Tor network can't
946 
+handle the load (e.g. default file-sharing ports). You can change your exit
947 
+policy using Vidalia's "Sharing" tab, or by manually editing your <a
948 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc">torrc</a>
949 
+file. If you want to avoid most if not all abuse potential, set it to
950 
+"reject *:*" (or un-check all the boxes in Vidalia). This setting means that
951 
+your relay will be used for relaying traffic inside the Tor network, but not
952 
+for connections to external websites or other services.
953 
+</p>
954 
+
955 
+<p>
956 
+Si vous autorisez n'importe quelle connexion de sortie, assurez-vous que la
957 
+résolutions de noms fonctionne (c'est à dire que votre ordinateur puisse
958 
+résoudre les adresses Internet correctement).  S'il y a des ressources que
959 
+votre ordinateur ne peut pas atteindre (par exemple, vous êtes derrière un
960 
+pare-feu restrictif ou un filtrage de contenu), merci de les rejeter
961 
+explicitement dans votre politique de sortie &mdash; sinon les utilisateurs
962 
+de Tor seront également impactés.
963 
+</p>
964 
+
965 
+<hr />
966 
+
967 
+<a id="RelayOrBridge"></a>
968 
+<h3><a class="anchor" href="#RelayOrBridge">Devrais-je faire fonctionner un
969 
+noeud normal ou une passerelle ?</a></h3>
970 
+
971 
+<p><a href="<page bridges>">Les noeuds-passerelles</a> (or "passerelles" en
972 
+plus court)  sont des <a href="<page docs/tor-doc-relay>">noeuds Tor</a> qui
973 
+ne sont pas listés dans l'annuaire de Tor. Cela signifie que même un FAI ou
974 
+un gouvernement qui tente de filtre les connexions vers Tor ne sera
975 
+probablement pas en mesure de bloquer toutes les passerelles.
976 
+</p>
977 
+
978 
+<p>Etre un noeud ou une passerelle demande quasiment la même configuration:
979 
+c'est juste une question de savoir si votre relais est sur une liste
980 
+publique ou non.
981 
+</p>
982 
+
983 
+<p>À l'heure actuelle, il n'y a pratiquement aucun endroit dans le monde où les
984 
+connexions au réseau Tor sont filtrées. Ainsi, faire fonctionner beaucoup de
985 
+passerelles dès maintenant est essentiellement une mesure de sauvegarde, a)
986 
+dans le cas où le réseau Tor est bloqué quelque-part, et b) pour les
987 
+personnes qui veulent une couche supplémentaire de sécurité car elles
988 
+s'inquiètent que quelqu'un reconnaisse qu'ils contactent un noeud public
989 
+Tor.
990 
+</p>
991 
+
992 
+<p>Alors, faut-il faire tourner un noeud normal ou une passerelle ? Si vous
993 
+avez beaucoup de bande passante, vous devriez installer un noeud normal
994 
+&mdash; une passerelle voyant très peu d'utilisation de nos jours. Si vous
995 
+êtes prêt à <a href="#ExitPolicies">être une sortie</a>, vous devriez
996 
+absolument installer un noeud normal, étant donné que nous avons besoin de
997 
+plus de sorties. Si vous ne pouvez pas être une sortie et avez peu de bande
998 
+passante, alors envoyez nous de l'argent. Merci de votre action !
999 
+</p>
1000 
+
1001 
+<hr />
1002 
+
1003 
+<a id="RelayMemory"></a>
1004 
+<h3><a class="anchor" href="#RelayMemory">Pourquoi mon noeud Tor consomme-t-il
1005 
+autant de mémoire ?</a></h3>
1006 
+
1007 
+<p>Si votre relais Tor consomme plus de mémoire que vous ne le voulez, voici
1008 
+quelques astuces pour réduire son empreinte mémoire!
1009 
+</p>
1010 
+
1011 
+<ol>
1012 
+<li>Si vous êtes sous Linux, vous pouvez rencontrer des bugs de fragmentation
1013 
+mémoire dans les différentes implémentations de la fonction malloc de la
1014 
+glibc. Ainsi, lorsque Tor libère de la mémoire vers le système, les morceaux
1015 
+libérés sont fragmentés ce qui ne facilite pas leur réutilisation. L'archive
1016 
+Tar de Tor utilise l'implémentation OpenBSD de la fonction malloc, qui
1017 
+souffre de moins de problèmes de fragmentation (aux dépends d'une plus
1018 
+grande charge processeur). Vous pouvez indiquer à Tor d'utiliser cette
1019 
+implémentation de la fonction malloc en utilisant à la place:
1020 
+<tt>./configure --enable-openbsd-malloc</tt></li>
1021 
+
1022 
+<li>If you're running a fast relay, meaning you have many TLS connections open,
1023 
+you are probably losing a lot of memory to OpenSSL's internal buffers (38KB+
1024 
+per socket). We've patched OpenSSL to <a
1025 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00001.html">release unused
1026 
+buffer memory more aggressively</a>. If you update to OpenSSL 1.0.0-beta5,
1027 
+Tor's build process will automatically recognize and use this feature.</li>
1028 
+
1029 
+<li>If you're running on Solaris, OpenBSD, NetBSD, or old FreeBSD, Tor is
1030 
+probably forking separate processes rather than using threads. Consider
1031 
+switching to a <a
1032 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayOS">better
1033 
+operating system</a>.</li>
1034 
+
1035 
+<li>Si vous ne pouvez toujours pas gérer la charge mémoire, vous pouvez
1036 
+envisager de réduire la bande passante que votre relais affiche. Afficher
1037 
+moins de bande passante implique que vous allez attirer moins d'utilisateur
1038 
+et ainsi, voter relais ne devrait pas être trop utilisé. Consultez la page
1039 
+de manuel sur l'option <tt>MaxAdvertisedBandwith</tt>.</li>
1040 
+
1041 
+</ol>
1042 
+
1043 
+<p>
1044 
+Toutefois, il faut bien prendre en compte que les relais Tor rapides
1045 
+consomment beaucoup de mémoire. Ainsi, il n'est pas anormal qu'un relais de
1046 
+sortie rapide utilise entre 500 et 1000Mo de mémoire.
1047 
+</p>
1048 
+
1049 
+<hr />
1050 
+
1051 
+<a id="WhyNotNamed"></a>
1052 
+<h3><a class="anchor" href="#WhyNotNamed">Pourquoi mon noeud Tor n'a pas de nom
1053 
+?</a></h3>
1054 
+
1055 
+<p>
1056 
+We currently use these metrics to determine if your relay should be named:<br />
1057 
+</p>
1058 
+<ul>
1059 
+<li>Le nom n'est pas constitué à partir d'une clef différente. Les noms en cours
1060 
+sont supprimés après 6 mois d'inactivité du noeud.</li>
1061 
+<li>Le noeud doit être présent depuis au moins deux semaines.</li>
1062 
+<li>Aucun autre noeud ne doit avoir demandé le même nom au cours le mois
1063 
+précédent</li>
1064 
+</ul>
1065 
+
1066 
+<hr />
1067 
+
1068 
+<a id="KeyManagement"></a>
1069 
+<h3><a class="anchor" href="#KeyManagement">Dites-m'en plus sur les clefs
1070 
+utilisées par Tor.</a></h3>
1071 
+
1072 
+<p>
1073 
+Tor utilise de nombreuses clefs différentes avec trois objectifs en tête: 1)
1074 
+le chiffrement pour assurer le secret des données sur le réseau Tor, 2)
1075 
+l'authentification afin que les clients sachent qu'ils communiquent bien
1076 
+avec les noeuds avec lesquels il doivent communiquer, et 3) des signatures
1077 
+pour s'assurer que tous les clients connaissent le même ensemble de noeuds.
1078 
+</p>
1079 
+
1080 
+<p>
1081 
+<b>Chiffrement</b>: d'abord, toutes les connexions dans Tor utilisent le
1082 
+chiffrement en tunnel TLS afin que des observateurs externes ne puissent
1083 
+lire pour quel circuit une cellule est prévue. Ensuite, le client Tor génère
1084 
+une clef de chiffrement éphémère avec chaque noeud du circuit afin que seul
1085 
+le noeud de sortie puisse lire les cellules. Les deux extrémités suppriment
1086 
+la clef de circuit lorsque le circuit prend fin afin que la collecte de
1087 
+trafic et la pénétration dans le noeud pour découvrir la clef ne puissent
1088 
+pas fonctionner.
1089 
+</p>
1090 
+
1091 
+<p>
1092 
+<b>Authentification</b>: Chaque noeud Tor a une clef de déchiffrement
1093 
+publique appelée "clef oignon".  Lorsque le client met en place des
1094 
+circuits, à chaque étape il <a
1095 
+href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demande que
1096 
+le noeud Tor prouve qu'il connaît sa propre clef oignon</a>. Ainsi, le
1097 
+premier noeud du circuit ne peut usurper le reste du circuit.  Chaque noeud
1098 
+change de clef oignon une fois par semaine.
1099 
+</p>
1100 
+
1101 
+<p>
1102 
+<b>Coordination</b>: Comment les clients font pour savoir qui sont les
1103 
+noeuds et comment savent-ils qu'ils disposent de bonnes clefs ? Chaque
1104 
+relais dispose d'une clef publique de chiffrement avec une grande durée de
1105 
+vie appelée "clef d'identité". Chaque autorité d'annuaire dispose en plus
1106 
+d'une "clef de signature d'annuaire". Les autorités d'annuaire <a
1107 
+href="<gitblob>doc/spec/dir-spec.txt">fournissent une liste signée</a> de
1108 
+tous les noeuds connus ainsi qu'un jeu de certificats pour chaque noeud
1109 
+(signés avec leur propre clef d'identité) spécifiant leurs clefs, leur
1110 
+emplacement, leurs politique de sortie, etc... Donc à moins que votre
1111 
+adversaire contrôle un nombre suffisant d'autorité d'annuaire, il ne peut
1112 
+tromper un client Tor en utilisant d'autres noeuds Tor.
1113 
+</p>
1114 
+
1115 
+<p>
1116 
+Comment les clients connaissent-ils les autorités d'annuaire ? Le logiciel
1117 
+Tor est livré avec une liste "en dur" contenant l'emplacement et la clef
1118 
+publique de chaque autorité d'annuaire. Ainsi, le seul moyen de tromper les
1119 
+utilisateurs en utilisant un faux réseau Tor est de livrer une version
1120 
+spécialement modifée du logiciel.
1121 
+</p>
1122 
+
1123 
+<p>
1124 
+Comment les utilisateurs savent-ils qu'ils ont le bon logiciel ? Lorsque
1125 
+nous distribuons les sources ou un paquet, nous le signons électroniquement
1126 
+avec <a href="http://www.gnupg.org/">GNU Privacy Guard</a>. Consultez <a
1127 
+href="<page verifying-signatures>">les instructions sur comment vérifier les
1128 
+signatures de Tor</a>.
1129 
+</p>
1130 
+
1131 
+<p>
1132 
+Pour être certain qu'il soit signé par nous, vous devez nous rencontrer en
1133 
+personne et récupérer une copie de notre empreinte de clef GPG ou bien
1134 
+connaître quelqu'un qui en dispose. Si vous suspectez une attaque à ce
1135 
+niveau, nous vous recommandons de contacter la communauté sécurité et de
1136 
+rencontrer ces personnes.
1137 
+</p>
1138 
+
1139 
+<hr />
1140 
+
1141 
+<a id="EverybodyARelay"></a>
1142 
+<h3><a class="anchor" href="#EverybodyARelay">Vous devriez faire que chaque
1143 
+utilisateur de Tor soit un noeud.</a></h3>
1144 
+
1145 
+<p>
1146 
+Requiring every Tor user to be a relay would help with scaling the network
1147 
+to handle all our users, and <a
1148 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">running
1149 
+a Tor relay may help your anonymity</a>. However, many Tor users cannot be
1150 
+good relays &mdash; for example, some Tor clients operate from behind
1151 
+restrictive firewalls, connect via modem, or otherwise aren't in a position
1152 
+where they can relay traffic. Providing service to these clients is a
1153 
+critical part of providing effective anonymity for everyone, since many Tor
1154 
+users are subject to these or similar constraints and including these
1155 
+clients increases the size of the anonymity set.
1156 
+</p>
1157 
+
1158 
+<p>
1159 
+Ceci-dit, nous voulons encourager les utilisateurs de Tor à faire
1160 
+fonctionner des noeuds. Ainsi, nous souhaitons véritablement simplifier le
1161 
+processus de configuration et de maintenance d'un noeud. Nous avons réalisé
1162 
+de gros progrès sur le plan de la configuration facile au cours des années
1163 
+précédentes: Vidalia dispose d'une interface de configuration de noeud
1164 
+facile à utiliser et supporte également uPnP. Tor est performant pour
1165 
+déterminer automatiquement s'il est atteignable et combien de bande passante
1166 
+il peut offrir.
1167 
+</p>
1168 
+
1169 
+<p>
1170 
+Il y 5 points que nous devons régler avant de faire cela:
1171 
+</p>
1172 
+
1173 
+<p>
1174 
+D'abord, nous avons besoin de rendre Tor stable en tant que noeud sur tous
1175 
+les systèmes d'exploitation courants. La plateforme principale est Windows
1176 
+et nous devrions régler les problèmes dans le courant de 2009. Consultez la
1177 
+section 4.1. de <a
1178 
+href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#RelayAnonymity">notre
1179 
+feuille de route de développement</a>.
1180 
+</p>
1181 
+
1182 
+<p>
1183 
+Second, we still need to get better at automatically estimating the right
1184 
+amount of bandwidth to allow. See item #7 on the <a href="<page
1185 
+volunteer>#Research">research section of the volunteer page</a>: "Tor
1186 
+doesn't work very well when relays have asymmetric bandwidth (e.g. cable or
1187 
+DSL)". It might be that <a
1188 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching
1189 
+to UDP transport</a> is the simplest answer here &mdash; which alas is not a
1190 
+very simple answer at all.
1191 
+</p>
1192 
+
1193 
+<p>
1194 
+Troisièment, nous avons besoin de travailler sur l'évolutivité du réseau
1195 
+(comment éviter d'imposer que chaque noeud Tor soit capable de se connecter
1196 
+à l'intégralité des noeuds Tor) et de l'annuaire (comment éviter d'imposer
1197 
+que tous les utilisateurs Tor connaissent l'intégralité des noeuds Tor). Les
1198 
+changement à ce niveau peuvent avoir des conséquences sur
1199 
+l'anonymat. Consultez la section 5 de notre article sur <a
1200 
+href="<svnprojects>design-paper/challenges.pdf">nos défis</a> pour plus
1201 
+détails. Encore une fois, le transport par UDP devrait améliorer grandement
1202 
+la situation.
1203 
+</p>
1204 
+
1205 
+<p>
1206 
+Quatrièmement, nous devons mieux comprendre les risques qui existent à
1207 
+laisser l'attaquant envoyer du trafic à travers votre noeud alors que vous
1208 
+êtes également en train d'initialiser votre propre trafic anonymisé. <a
1209 
+href="http://freehaven.net/anonbib/#back01">Trois</a> documents de <a
1210 
+href="http://freehaven.net/anonbib/#torta05">recherche</a> <a
1211 
+href="http://freehaven.net/anonbib/#clog-the-queue">différents</a> décrivent
1212 
+les moyens d'identifier les noeud d'un circuit à travers les noeuds
1213 
+candidats et en observant le traffic alors que le circuit est en
1214 
+activité. Ces attaques par engorgement ne posent pas de problème à Tor tant
1215 
+que les noeuds ne sont pas également des clients. Mais si nous encourageons
1216 
+de plus en plus de clients à devenir des noeuds (soit comme des passerelles,
1217 
+soit comme des noeuds normaux), nous devons comprendre ce problème un peu
1218 
+mieux et apprendre comment le rendre inoffensif.
1219 
+</p>
1220 
+
1221 
+<p>
1222 
+Cinquièmement, nous aurions besoin d'une sorte de système d'incitation pour
1223 
+encourager les gens à relayer le trafic pour les autres, et / ou à devenir
1224 
+des nœuds de sortie. Voici nos <a
1225 
+href="https://blog.torproject.org/blog/two-incentive-designs-tor">réflexions
1226 
+sur les incitation à propos de Tor</a>.
1227 
+</p>
1228 
+
1229 
+<p>
1230 
+Merci de nous aider sur tous ces points.
1231 
+</p>
1232 
+
1233 
+<hr />
1234 
+
1235 
+<a id="Criminals"></a>
1236 
+<h3><a class="anchor" href="#Criminals">Est-ce-que Tor permet aux criminels de
1237 
+faire des choses répréhensibles ?</a></h3>
1238 
+
1239 
+<p>
1240 
+Merci de consultez notre <a href="<page faq-abuse>">Faq sur l'utilisation
1241 
+abusive</a> pour trouver la réponse à cette question et aux autres.
1242 
+</p>
1243 
+
1244 
+<hr />
1245 
+
1246 
+<a id="RespondISP"></a>
1247 
+<h3><a class="anchor" href="#RespondISP">Comment puis-je répondre à mon FAI à
1248 
+propros de mon noeud de sortie ?</a></h3>
1249 
+
1250 
+<p>
1251 
+A collection of templates for successfully responding to ISPs is <a
1252 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates">collected
1253 
+here</a>.
1254 
+</p>
1255 
+
1256 
+<hr />
1257 
+
1258 
+  </div>
1259 
+
1260 
+
1261 
+
1262 
+#include <foot.wmi>
fr/mirrors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,48 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Mirrors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor : Miroirs</h2>
14 
+<hr />
15 
+
16 
+<p>
17 
+L'url canonique de ce site est <a
18 
+href="https://www.torproject.org/">https://www.torproject.org/</a>, mais il
19 
+existe quelques miroirs à d'autres endroits.
20 
+</p>
21 
+
22 
+<p>
23 
+Si vous voulez faire fonctionner un miroir, merci de <a href="<page
24 
+docs/running-a-mirror>">lire nos instructions pour mettre en place un miroir</a>.
25 
+</p>
26 
+
27 
+<table class="mirrors">
28 
+<tr>
29 
+  <th>Pays</th>
30 
+  <th>Organisation</th>
31 
+  <th>Etat</th>
32 
+  <th>ftp</th>
33 
+  <th>http dist/</th>
34 
+  <th>http website</th>
35 
+  <th>https dist/</th>
36 
+  <th>https website</th>
37 
+  <th>rsync dist/</th>
38 
+  <th>rsync website</th>
39 
+</tr>
40 
+
41 
+<!--PO4ASHARPBEGINinclude <mirrors-table.wmi>
42 
+PO4ASHARPEND-->
43 
+</table>
44 
+
45 
+  </div>
46 
+
47 
+
48 
+#include <foot.wmi>
fr/overview.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,268 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22308 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor: Overview" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<a name="overview"></a>
14 
+<h2><a class="anchor" href="#overview">Tor: Vue d'ensemble</a></h2>
15 
+
16 
+<!-- BEGIN SIDEBAR -->
17 
+<div class="sidebar-left">
18 
+<h3>Thèmes</h3>
19 
+<ul>
20 
+<li><a href="<page overview>#overview">Aperçu</a></li>
21 
+<li><a href="<page overview>#whyweneedtor">Pourquoi nous avons besoins de
22 
+Tor</a></li>
23 
+<li><a href="<page overview>#thesolution">La Solution</a></li>
24 
+<li><a href="<page overview>#hiddenservices">Services Cachés</a></li>
25 
+<li><a href="<page overview>#stayinganonymous">Rester anonyme</a></li>
26 
+<li><a href="<page overview>#thefutureoftor">Le futur de Tor</a></li>
27 
+</ul>
28 
+</div>
29 
+
30 
+
31 
+<!-- END SIDEBAR -->
32 
+<hr />
33 
+
34 
+<p>
35 
+Tor est un réseau de tunnels virtuels qui permet d'améliorer la protection
36 
+de la vie privée et la sécurité sur Internet.  Il offre également la
37 
+possibilité aux développeurs de créer de nouveaux outils de communication
38 
+respectueux de la vie privée. Tor fournit les bases grâce auxquelles de
39 
+multiples applications vont permettre à des organisations et à des individus
40 
+d'échanger des informations sur les réseaux publics sans compromettre leur
41 
+intimité.
42 
+</p>
43 
+
44 
+<p>
45 
+Individuals use Tor to keep websites from tracking them and their family
46 
+members, or to connect to news sites, instant messaging services, or the
47 
+like when these are blocked by their local Internet providers.  Tor's <a
48 
+href="<page hidden-services>">hidden services</a> let users publish web
49 
+sites and other services without needing to reveal the location of the
50 
+site. Individuals also use Tor for socially sensitive communication: chat
51 
+rooms and web forums for rape and abuse survivors, or people with illnesses.
52 
+</p>
53 
+
54 
+<p>
55 
+Tor permet à des journalistes de communiquer de manière plus sécurisée avec
56 
+des contacts ou des dissidents. Des organisations non gouvernementales (ONG)
57 
+utilisent Tor pour permettre à leurs membres de se connecter à leur site web
58 
+lorsqu'ils sont dans un pays étranger,sans dévoiler alentour pour qui ils
59 
+travaillent.
60 
+</p>
61 
+
62 
+<p>
63 
+Des groupes comme Indymedia recommandent à leurs membres l'usage de Tor pour
64 
+protéger leur confidentialité et leur sécurité. Des groupes activistes comme
65 
+l'Electronic Frontier Foundation (EFF) recommandent le recours à Tor qu'ils
66 
+voient comme un moyen de préserver les libertés civiles sur Internet. Des
67 
+entreprises utilisent Tor pour étudier leurs concurrents sans être
68 
+surveillées et pour protéger leurs tractations des oreilles
69 
+indiscrètes. Elles l'utilisent aussi pour remplacer les VPNs traditionnels,
70 
+qui ne masquent ni la quantité des données échangées, ni la durée des
71 
+connexions. Dans quelles entreprises les employés travaillent-t-ils tard ?
72 
+Quelles sont les organisations dont les employés consultent des sites
73 
+d'offre d'emploi ? Quels bureaux d'étude ont communiqué avec quels cabinets
74 
+d'avocats d'affaire ?
75 
+</p>
76 
+
77 
+<p>
78 
+Une des divisions de l'US Navy utilise Tor comme outil de renseignement dont
79 
+le code est ouvert. Une de ses équipes s'est également servie de Tor
80 
+récemment lorsqu'elle était déployée au Moyen-Orient. La police utilise Tor
81 
+pour visiter ou surveiller des sites web sans que les adresses IP
82 
+gouvernementales n'apparaissent dans les logs des serveurs, ainsi que lors
83 
+de certaines opérations, pour des raisons de sécurité.
84 
+</p>
85 
+
86 
+<p>
87 
+La diversité des utilisateurs est en fait <a
88 
+href="http://freehaven.net/doc/fc03/econymics.pdf">une composante importante
89 
+de la sécurité de Tor</a>.  Vous êtes mêlés aux autres <a href="<page
90 
+torusers>">utilisateurs de Tor</a>; plus la base d'utilisateurs est peuplée
91 
+et variée, meilleure est la protection de l'anonymat.
92 
+</p>
93 
+
94 
+<a name="whyweneedtor"></a>
95 
+<h3><a class="anchor" href="#whyweneedtor">Pourquoi nous avons besoin de Tor</a></h3>
96 
+
97 
+<p>
98 
+Tor protège de « l'analyse de trafic », une forme courante de surveillance
99 
+sur Internet. L'analyse de trafic peut être utilisée pour découvrir qui
100 
+parle à qui sur un réseau public.  En connaissant la source et la
101 
+destination de votre trafic Internet, on peut découvrir vos habitudes et vos
102 
+centres d'intérêt.  Cela peut avoir des conséquences financières si par
103 
+exemple, un site de commerce en ligne ne propose pas les mêmes prix en
104 
+fonction de votre pays ou institution d'origine.  Il y a même des cas où
105 
+votre emploi ou bien votre sécurité physique peuvent être compromis si vous
106 
+dévoilez qui et où vous êtes. Si par exemple vous voyagez à l'étranger, et
107 
+que vous vous connectez à l'ordinateur de votre employeur pour recevoir ou
108 
+envoyer des emails, vous risquez de révéler votre pays d'origine et votre
109 
+situation professionnelle à quiconque est en train d'observer le réseau, et
110 
+ce même si la communication est chiffrée.
111 
+</p>
112 
+
113 
+<p>
114 
+Comment fonctionne l'analyse de trafic ? Les paquets de données Internet se
115 
+composent de deux parties : une charge utile, et un en-tête utilisé pour le
116 
+routage.  La charge utile correspond aux données que l'on veut effectivement
117 
+envoyer : un email, une page web, un fichier audio, etc. L'en-tête contient
118 
+entre autres l'origine, la destination, la taille des données, des variables
119 
+relatives aux durées de transmission, etc...  Même si vous chiffrez vos
120 
+données, les en-têtes restent visibles, et une analyse du trafic peut
121 
+révéler beaucoup de choses sur ce que vous faites, et peut-être ce que vous
122 
+dites.
123 
+</p>
124 
+
125 
+<p>
126 
+Un problème classique de protection de la vie privée est que les
127 
+destinataires de vos communications peuvent savoir que vous en êtes l'auteur
128 
+en regardant les en-têtes.  Les intermédiaires autorisés, comme les
129 
+fournisseurs d'accès Internet, ainsi que parfois, des intermédiaires non
130 
+autorisés, le peuvent également.  Une forme d'analyse de trafic très simple
131 
+consiste donc par exemple à capturer le trafic entre un expéditeur et un
132 
+destinataire, et à regarder les en-têtes.
133 
+</p>
134 
+
135 
+<p>
136 
+Mais il existe des formes d'analyse de trafic plus poussées.  Certains
137 
+attaquants épient plusieurs endroits de l'Internet, et se servent de
138 
+techniques statistiques sophistiquées pour observer des motifs dans les
139 
+communications. Le chiffrement ne dissimule que le contenu du trafic et pas
140 
+les en-têtes. Il ne protège donc pas contre ces attaques.
141 
+</p>
142 
+
143 
+<a name="thesolution"></a>
144 
+<h3><a class="anchor" href="#thesolution">La solution : un réseau anonyme
145 
+décentralisé</a></h3>
146 
+
147 
+<p>
148 
+Tor réduit les risques d'analyses de trafic simples ou sophistiquées, en
149 
+répartissant vos transactions entre plusieurs endroits de l'Internet. On ne
150 
+peut donc pas, en observant un seul point, vous associer à votre
151 
+destinataire.  C'est comme utiliser un chemin tortueux et difficile à suivre
152 
+pour semer un poursuivant (tout en effaçant de temps en temps ses traces) .
153 
+Au lieu d'emprunter un itinéraire direct entre la source et la destination,
154 
+les paquets de données suivent une trajectoire aléatoire à travers plusieurs
155 
+relais qui font disparaître vos traces. Personne ne peut donc déduire de
156 
+l'observation d'un point unique, d'où viennent, ni où vont les données.
157 
+</p>
158 
+
159 
+<p><img alt="Tor circuit step one" src="$(IMGROOT)/htw1.png" /></p>
160 
+
161 
+<p>
162 
+Pour définir un trajet privé à travers le réseau Tor, le logiciel de
163 
+l'utilisateur détermine au fur et à mesure un circuit de connexions
164 
+chiffrées à travers les relais du réseau. Le circuit est construit étape par
165 
+étape, et chaque relais le long du chemin ne connaît que celui qui lui a
166 
+transmis les données, et celui auquel il va les retransmettre.  Aucun relais
167 
+ne connaît à lui tout seul le chemin complet pris par un paquet de
168 
+données. Le client négocie indépendamment une paire de clé de chiffrement
169 
+avec chaque serveur du circuit. Aucun d'eux ne peut donc intercepter la
170 
+connexion au passage.
171 
+</p>
172 
+
173 
+<p><img alt="Tor circuit step two" src="$(IMGROOT)/htw2.png" /></p>
174 
+
175 
+<p>
176 
+Une fois le circuit établi, différents types de données peuvent être
177 
+échangées, et plusieurs sortes d'applications peuvent être utilisées via le
178 
+réseau Tor. Vu que chaque serveur ne voit pas plus d'une étape dans le
179 
+circuit, ni un éventuel intermédiaire, ni un noeud compromis ne peuvent
180 
+analyser le trafic pour établir une relation entre la source et la
181 
+destination d'une connexion.
182 
+</p>
183 
+
184 
+<p>
185 
+Pour des raisons d'efficacité, le logiciel Tor utilise le même circuit pour
186 
+des connexions qui ont lieu dans un même intervalle de dix minutes.  Les
187 
+requêtes ultérieures utiliseront un nouveau circuit, afin d'éviter que l'on
188 
+puisse faire le lien entre vos actions précédentes, et les nouvelles.
189 
+</p>
190 
+
191 
+<p><img alt="Tor circuit step three" src="$(IMGROOT)/htw3.png" /></p>
192 
+
193 
+
194 
+<a name="hiddenservices"></a>
195 
+<h3><a class="anchor" href="#hiddenservices">Les services cachés</a></h3>
196 
+
197 
+<p>
198 
+Les utilisateurs de Tor ont également la possibilité d'offrir des services,
199 
+comme par exemple la publication d'un site web ou un serveur de messagerie
200 
+instantanée, tout en masquant le lieu géographique de ce service.  Les
201 
+autres utilisateurs de Tor peuvent se connecter à ces services cachés en
202 
+utilisant le système de « points de rendez-vous » de Tor.  Ni le serveur, ni
203 
+l'utilisateur ne peuvent alors découvrir avec qui ils communiquent.  Ces
204 
+services cachés permettent de mettre en place un site web sur lesquels des
205 
+auteurs publieraient sans craindre la censure.  Personne ne pourrait savoir
206 
+qui a mis en place le site, et personne ne pourrait savoir qui a posté sur
207 
+le site, pas même celui qui l'a mis en place.  Plus d'information sur <a
208 
+href="<page docs/tor-hidden-service>">la configuration des services
209 
+cachés</a> et comment le <a href="<page hidden-services>">protocole des
210 
+services cachés</a> fonctionne.
211 
+</p>
212 
+
213 
+<a name="stayinganonymous"></a>
214 
+<h3><a class="anchor" href="#stayinganonymous">Rester anonyme</a></h3>
215 
+
216 
+<p>
217 
+Tor ne résout pas tous les problèmes d'anonymat. Il ne s'occupe que du
218 
+transport des données. Vous devez utiliser des programmes appropriés aux
219 
+différents protocoles si vous voulez éviter que les sites que vous visitez
220 
+puissent vous identifier. Vous pouvez par exemple utiliser un proxy web
221 
+comme Privoxy, pour bloquer les cookies et les informations spécifiques à
222 
+votre navigateur lorsque vous surfez.
223 
+</p>
224 
+
225 
+<p>
226 
+Pour protéger votre anonymat, soyez malin. Ne rentrez pas votre nom ou
227 
+d'autres informations personnelles dans les formulaires web. Soyez
228 
+conscients que, comme tout réseau d'anonymat suffisamment rapide pour du
229 
+surf sur le web, Tor ne protège pas contre certaines attaques temporelles :
230 
+si votre attaquant peut observer à la fois le trafic sortant de votre poste,
231 
+et le trafic arrivant à votre destination, il va pouvoir, grâce à des
232 
+analyses statistiques, établir un lien entre les deux.
233 
+</p>
234 
+
235 
+<a name="thefutureoftor"></a>
236 
+<h3><a class="anchor" href="#thefutureoftor">Le futur de Tor</a></h3>
237 
+
238 
+<p>
239 
+Le pari de mettre en place un réseau d'anonymat utilisable aujourd'hui sur
240 
+l'Internet est aujourd'hui loin d'être gagné. Nous voulons que le logiciel
241 
+corresponde aux besoins des utilisateurs. Nous voulons aussi que le réseau
242 
+reste fiable et puisse supporter le maximum d'usagers possible. Sécurité et
243 
+facilité d'utilisation ne sont pas des notions antagonistes : plus Tor
244 
+deviendra simple à utiliser, plus le nombre d'utilisateurs grandira, plus il
245 
+sera difficile de pister une personne parmi toutes les connexions possibles,
246 
+meilleure sera la sécurité pour tout le monde. Nous progressons, mais nous
247 
+avons besoin de votre aide. Pourquoi ne pas <a href="<page
248 
+docs/tor-doc-relay>">mettre en place un relais</a>, ou <a href="<page
249 
+volunteer>">vous investir</a> dans le <a href="<page
250 
+documentation>#Developers">développement</a>.
251 
+</p>
252 
+
253 
+<p>
254 
+Les tendances législatives et technologiques actuelles menacent de plus en
255 
+plus notre anonymat, restreignant ainsi notre liberté d'expression et
256 
+d'accès à l'information sur l'Internet. Cela fragilise également la sécurité
257 
+nationale et les infrastructures critiques en rendant les communications
258 
+entre les individus, les organisations, les sociétés, et les gouvernements,
259 
+vulnérables à l'analyse de trafic. Chaque utilisateur et chaque relais
260 
+introduit de la diversité, renforçant ainsi la possibilité offerte par Tor
261 
+de nous laisser reprendre le contrôle de notre sécurité et de notre vie
262 
+privée.
263 
+</p>
264 
+
265 
+  </div>
266 
+
267 
+
268 
+#include <foot.wmi>
fr/sponsors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,89 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22225 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Sponsors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Sponsors</h2>
14 
+<div class="underline"></div>
15 
+<p>
16 
+La <a href="<page torusers>">variété des utilisateurs de Tor</a> explique
17 
+assez bien la diversité de nos sources de financements &mdash; que nous
18 
+souhaitons promouvoir encore plus ! Nos sponsors sont divisés en niveaux
19 
+basés sur le total des sommes perçues:
20 
+</p>
21 
+
22 
+<h3><i>Magnoliophyta</i> (jusqu'à 1 million de $)</h3>
23 
+	<ul>
24 
+		<li>Vous ?</li>
25 
+	</ul>
26 
+
27 
+<h3><i>Liliopsida</i> (jusqu'à 750000 $)</h3>
28 
+	<ul>
29 
+		<li>Une ONG anonyme Nord-Américaine (2008-2010)</li>
30 
+	</ul>
31 
+
32 
+<h3><i>Asparagales</i> (jusqu'à 500000 $)</h3>
33 
+	<ul>
34 
+		<li><a href="http://www.ibb.gov/">Bureau de diffusion internationale </a>
35 
+(2006-2010)</li>
36 
+		<li>Une ONG anonyme européenne (2006-2008)</li>
37 
+	</ul>
38 
+
39 
+<h3><i>Alliaceae</i> (jusqu'à 200000 $)</h3>
40 
+	<ul>
41 
+		<li>Vous ?</li>
42 
+	</ul>
43 
+
44 
+<h3><i>Allium</i> (jusqu'à 100000 $)</h3>
45 
+	<ul>
46 
+		<li><a href="http://www.nlnet.nl/">NLnet Foundation</a> (2008-2009)</li>
47 
+		<li><a href="http://chacs.nrl.navy.mil/">Naval Research Laboratory</a>
48 
+(2006-2010)</li>
49 
+		<li>Un FAI Nord-Américain anonyme (2009-2010)</li>
50 
+	</ul>
51 
+
52 
+<h3><i>Allium cepa</i> (jusqu'à 50000 $)</h3>
53 
+	<ul>
54 
+		<li><a href="<page donate>">Plus de 500 dons personnels venant de personnes
55 
+comme vous</a> (2006-2010)</li>
56 
+		<li><a href="http://code.google.com/opensource/">Google</a> (2008-2009)</li>
57 
+		<li><a href="http://code.google.com/soc/">Google Summer of Code</a> (2007-2009)</li>
58 
+		<li><a href="http://www.hrw.org/">Human Rights Watch</a> (2007)</li>
59 
+		<li><a href="http://www.torfox.org/">Torfox</a> (2009)</li>
60 
+    <li><a href="http://www.shinjiru.com/">Shinjiru Technology</a> (2009-2010)</li>
61 
+  </ul>
62 
+
63 
+<h3>Anciens Sponsors</h3>
64 
+<p>We greatly appreciate the support provided by our past sponsors in keeping
65 
+the pre-501(c)(3) Tor Project progressing through our ambitious goals:</p>
66 
+	<ul>
67 
+		<li><a href="https://www.eff.org/">Electronic Frontier Foundation</a>
68 
+(2004-2005)</li>
69 
+		<li><a href="http://chacs.nrl.navy.mil/">DARPA et ONR par Naval Research
70 
+Laboratory</a> (2001-2006)</li>
71 
+		<li><a href="http://www.cyber-ta.org/">projet Cyber-TA</a> (2006-2008)</li>
72 
+		<li>Bell Security Solutions Inc (2006)</li>
73 
+		<li><a href="http://www.omidyar.net/">Omidyar Network Enzyme Grant</a> (2006)</li>
74 
+		<li><a
75 
+href="http://seclab.cs.rice.edu/lab/2005/08/01/seclab-awarded-grant-to-study-security-of-p2p/">NSF
76 
+grâce à l'Université Rice</a> (2006-2007)</li>
77 
+	</ul>
78 
+<p>Merci à toutes les personnes et à tous les groupes qui ont rendu possible le
79 
+projet Tor et merci spécialement aux volontaires individuels qui ont apporté
80 
+les contributions non financières: le code, les tests, la documentation, la
81 
+formation, la recherche et le fonctionnement de relais qui constituent le
82 
+réseau Tor.
83 
+</p>
84 
+
85 
+</div>
86 
+
87 
+
88 
+
89 
+#include <foot.wmi>
fr/torusers.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,445 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22261 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Who uses Tor?" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Pour débuter</h2>
14 
+
15 
+
16 
+<!-- BEGIN SIDEBAR -->
17 
+<div class="sidebar-left">
18 
+<h3>Qui utilise Tor ?</h3>
19 
+<ul>
20 
+<li><a href="<page torusers>#normalusers">Des gens ordinaires utilisent Tor</a></li>
21 
+<li><a href="<page torusers>#military">Des militaires utilisent Tor</a></li>
22 
+<li><a href="<page torusers>#journalist">Des journalistes et leurs lecteurs
23 
+utilisent Tor</a></li>
24 
+<li><a href="<page torusers>#lawenforcement">Des agents de la force publique
25 
+utilisent Tor</a></li>
26 
+<li><a href="<page torusers>#activists">Des Militants &amp; Dénonciateurs
27 
+Anonymes utilisent Tor</a></li>
28 
+<li><a href="<page torusers>#spotlight">Des personnes de toutes conditions
29 
+utilisent Tor</a></li>
30 
+<li><a href="<page torusers>#executives">Des entreprises utilisent Tor</a></li>
31 
+<li><a href="<page torusers>#bloggers">Des Blogueurs utilisent Tor</a></li>
32 
+<li><a href="<page torusers>#itprofessionals">Des professionels de
33 
+l'informatique utilisent Tor</a></li>
34 
+</ul>
35 
+</div>
36 
+
37 
+
38 
+<!-- END SIDEBAR -->
39 
+<hr />
40 
+<p>
41 
+Tor a été initialement conçu, mis en œuvre et déployé comme la troisième
42 
+génération du <a href="http://www.onion-router.net/">projet de routage en
43 
+oignon du Laboratoire de Recherche de la Navale américaine</a>.  Il a été
44 
+développé initialement, avec l'US Navy, dans le but principal de protéger
45 
+les communications gouvernementales. Aujourd'hui, il est utilisé chaque jour
46 
+pour une multitude de besoins par des militaires, des journalistes, des
47 
+agents de la force publique, des militants, et bien d'autres. Voici
48 
+quelques-unes des utilisations spécifiques que nous avons observées ou que
49 
+nous recommandons.
50 
+</p>
51 
+
52 
+<a name="normalusers"></a>
53 
+<h2><a class="anchor" href="#normalusers">Des gens ordinaires utilisent Tor</a></h2>
54 
+<hr />
55 
+<ul>
56 
+<li><strong>Ils protègent leur vie privée des commerçants sans scrupules et des
57 
+voleurs d'identité.</strong> Des Fournisseurs d'Accès Internet (FAI) <a
58 
+href="http://seekingalpha.com/article/29449-compete-ceo-isps-sell-clickstreams-for-5-a-month">vendent
59 
+les enregistrements de vos activités sur Internet</a> à des entreprises de
60 
+marketing ou à quiconque est susceptible de payer pour cela. Les FAI en
61 
+général disent qu'ils anonymisent les données en ne fournissant pas
62 
+d'informations personnelles identifiables, mais <a
63 
+href="http://www.wired.com/politics/security/news/2006/08/71579?currentPage=all">cela
64 
+s'est révélé inexact</a>. Un procès-verbal détaillé de chaque site que vous
65 
+visitez, le texte de toutes les recherches que vous effectuez, et peut-être
66 
+même les comptes d'utilisateur et mots de passe peuvent figurer dans ces
67 
+données.   En plus de votre FAI, les sites (<a
68 
+href="http://www.google.com/privacy_faq.html">les moteurs de recherche</a>)
69 
+que vous visitez ont leurs propres journaux de bord, contenant les mêmes
70 
+informations voire davantage.
71 
+</li>
72 
+<li><strong>Ils protègent leurs communications des entreprises
73 
+irresponsables.</strong> Partout sur Internet, Tor est recommandé aux
74 
+personnes qui se préoccupent depuis peu de leur vie privée face à
75 
+l'augmentation des violations et des diffusions de données privées. De <a
76 
+href="http://www.securityfocus.com/news/11048"> la pertes de données de
77 
+sauvegarde</a>, à la <a
78 
+href="http://www.nytimes.com/2006/08/09/technology/09aol.html?ex=1312776000&amp;en=f6f61949c6da4d38&amp;ei=5090">
79 
+remise d'informations aux chercheurs</a>, vos données ne sont souvent pas
80 
+bien protégées par ceux en qui vous pensez pouvoir avoir confiance pour les
81 
+garder en sécurité.
82 
+</li>
83 
+<li><strong>Ils protègent leurs enfants sur Internet</strong> Vous avez dit à
84 
+vos enfants qu'ils ne devaient pas communiquer des informations personnelles
85 
+en ligne, mais ils peuvent partager leur adresse tout simplement en ne
86 
+dissimulant pas leur adresse IP. De plus en plus, les adresses IP peuvent
87 
+être <a href="http://whatismyipaddress.com/">littéralement mis en
88 
+correspondance avec une même ville ou une rue</a>, et peuvent <a
89 
+href="http://whatsmyip.org/more/">révéler d'autres renseignements</a> sur la
90 
+façon dont vous vous connectez à Internet. Aux États-Unis, le gouvernement
91 
+pousse à rendre cette cartographie de plus en plus précise.
92 
+</li>
93 
+<li><strong>Ils font des recherches sur des sujets sensibles.</strong> Il y a
94 
+une très grande richesse d'informations disponibles sur Internet. Mais
95 
+peut-être dans votre pays, l'accès à l'information sur le SIDA, sur le
96 
+contrôle des naissances, <a
97 
+href="http://www.cbsnews.com/stories/2002/12/03/tech/main531567.shtml">la
98 
+culture tibétaine</a>, ou les religions du monde est cachée derrière un
99 
+pare-feu national.
100 
+</li>
101 
+</ul>
102 
+
103 
+<a name="military"></a>
104 
+<h2><a class="anchor" href="#military">Des militaires utilisent Tor</a></h2>
105 
+<hr />
106 
+<ul>
107 
+
108 
+<li>
109 
+<strong>Les agents secrets :</strong> Il n'est pas difficile pour des
110 
+ennemis de surveiller le trafic Internet et de découvrir dans tous les
111 
+hôtels et autres lieux quelles sont les personnes qui se connectent à des
112 
+serveurs militaires connus. Les agents secrets déployés loin de leur base
113 
+utilisent Tor pour masquer les sites qu'ils visitent, pour protéger les
114 
+intérêts et les opérations militaires, ainsi que pour éviter de se faire
115 
+agresser physiquement.
116 
+</li>
117 
+
118 
+<li><strong>Les services cachés :</strong> Quand Internet a été mis au point par
119 
+le DARPA, son objectif premier était de fournir des moyens de communication
120 
+distribués robustes capables de résister à des attaques locales.  Toutefois,
121 
+certaines fonctions doivent être centralisées, telles que l'administration
122 
+et le contrôle des sites.  C'est la nature des protocoles Internet de
123 
+révéler l'emplacement géographique de tout serveur qui est accessible en
124 
+ligne.  Les fonctionnalités des services cachés de Tor redonnent aux
125 
+militaires à la fois la direction et à la fois le contrôle pour être
126 
+physiquement protégé d'un blocage ou d'une opération de recherche.
127 
+</li>
128 
+<li><strong>La Collecte de renseignements:</strong> Le personnel militaire a
129 
+besoin d'utiliser des ressources électroniques qui peuvent être gérées et
130 
+surveillées par des ennemis. Ils ne veulent pas que le serveur Web de ces
131 
+ennemis enregistre une adresse militaire, révélant ainsi une opération de
132 
+surveillance.
133 
+</li>
134 
+</ul>
135 
+
136 
+<a name="journalist"></a>
137 
+<h2><a class="anchor" href="#journalist">Des journalistes et leurs lecteurs
138 
+utilisent Tor</a></h2>
139 
+<hr />
140 
+<ul>
141 
+<li><strong><a href="http://www.rsf.org/">Reporters sans Frontières</a></strong>
142 
+relie par Internet des prisonniers de droit commun  et  des journalistes
143 
+emprisonnés ou en danger dans le monde entier. Ils conseillent aux
144 
+journalistes, aux sources, aux blogueurs et aux dissidents d'utiliser Tor
145 
+pour assurer leur confidentialité et leur sécurité.
146 
+</li>
147 
+<li>Le <strong><a href="http://www.ibb.gov/">Bureau International de Diffusion
148 
+US</a></strong> (La Voix de l'Amérique/Radio Free Europe/Radio Free Asia)
149 
+soutient le développement de Tor pour  aider les utilisateurs d'Internet
150 
+dans les pays ne disposant pas d'un accès correct aux médias libres.  Tor
151 
+préserve la capacité des personnes qui se cachent derrière des pare-feu
152 
+nationaux, ou celles qui sont sous la surveillance de régimes répressifs, à
153 
+obtenir une vision globale de sujets controversés tels que la démocratie,
154 
+l'économie et la religion.
155 
+</li>
156 
+<li><strong>Des citoyens et des journalistes en Chine</strong> utilisent Tor
157 
+pour écrire des articles sur des évènements locaux afin d'encourager le
158 
+changement social et la réforme politique.
159 
+</li>
160 
+<li><strong>Des citoyens et des journalistes dans <a
161 
+href="http://www.rsf.org/rubrique.php3?id_rubrique=554">les trous noirs
162 
+d'Internet</a></strong> utilisent Tor pour rechercher des informations et
163 
+des points de vue opposés, pour déposer des histoires sur des médias non
164 
+contrôlés par l'État, et pour éviter les conséquences personnelles de leur
165 
+curiosité intellectuelle.
166 
+</li>
167 
+</ul>
168 
+
169 
+<a name="lawenforcement"></a>
170 
+<h2><a class="anchor" href="#lawenforcement">Des agents de la force publique
171 
+utilisent Tor</a></h2>
172 
+<hr />
173 
+<ul>
174 
+<li><strong>Surveillance en ligne:</strong> Tor permet aux autorités de surfer
175 
+sur les sites Web et les services douteux sans laisser de traces.  Si
176 
+l'administrateur système d'un site de jeu illégal, par exemple, venait à
177 
+voir de multiples connexions d'adresses IP provenant du gouvernement ou
178 
+d'agents de la force publique dans ses journaux d'utilisation, des enquêtes
179 
+pourraient être entravées.
180 
+</li>
181 
+<li><strong>Opérations dissimulées:</strong> De la même manière, l'anonymat
182 
+permet aux officiers de la force publique de réaliser en ligne des
183 
+opérations &rdquo;d'infiltration&rdquo;.  Indépendamment de la façon dont un
184 
+bon agent d'infiltration peut se présenter, si les communications
185 
+comprennent les plages d'adresses IP correspondant à celle de la police, la
186 
+couverture est grillée.
187 
+</li>
188 
+<li><strong>Sites web d'indicateurs (ndt de police) vraiment anonymes:</strong>
189 
+Depuis que les sites d'indicateurs en ligne sont populaires, sans un
190 
+logiciel d'anonymat, ils sont beaucoup moins efficaces.  Les sources
191 
+sérieuses ont compris que même si le nom ou l'email n'est pas attaché à
192 
+l'information, l'historique du serveur permet de les identifier très
193 
+rapidement.  Il en résulte que les sites d'indicateurs qui n'encouragent pas
194 
+l'anonymat réduisent le nombre de leurs indices.
195 
+</li>
196 
+</ul>
197 
+
198 
+<a name="activists"></a>
199 
+<h2><a class="anchor" href="#activists">Des Militants &amp; Dénonciateurs
200 
+Anonymes utilisent Tor</a></h2>
201 
+<hr />
202 
+<ul>
203 
+<li><strong>Des militants pour les droits de l'homme utilisent Tor pour signaler
204 
+anonymement les abus à partir dezones dangereuses.</strong> Au niveau
205 
+international, les syndicats utilisent Tor et d'autres formes d'anonymat en
206 
+ligne ou hors ligne pour féderer les travailleurs conformément à la
207 
+Déclaration Universelle des Droits de l'Homme. Même si ces organisations
208 
+sont légales, cela ne signifie pas qu'elles sont hors de danger. Tor permet
209 
+d'éviter la persécution tout en continuant à élever la voix.
210 
+</li>
211 
+<li>Lorsque des groupes tels que le <strong>American Friends Service Committee
212 
+et les groupes environnementaux sont de plus en plus <a
213 
+href="http://www.afsc.org/news/2005/government-spying.htm">mis sous
214 
+surveillance</a> aux États-Unis</strong> en vertu de lois destinées à lutter
215 
+contre le terrorisme, de nombreux agents pacifistes comptent sur Tor pour
216 
+une protection élémentaire de leurs activités légitimes.
217 
+</li>
218 
+<li><strong><a href="http://hrw.org/doc/?t=internet">Human Rights
219 
+Watch</a></strong> recommande Tor dans ses rapports, &ldquo;<a
220 
+href="http://www.hrw.org/reports/2006/china0806/">La course vers le bas:
221 
+complicité des entreprises dans la censure de l'Internet chinois</a>.&rdquo;
222 
+Le co-auteur de l'étude interviewe Roger Dingledine, responsable du projet
223 
+Tor, sur l'utilisation de Tor.  Ils présentent Tor dans la section comment
224 
+outre-passer le
225 
+<ahref="http://www.hrw.org/reports/2006/china0806/3.htm#_Toc142395820">&ldquo;GrandPare-feu
226 
+de la Chine,&rdquo;</a> et recommandent aux militants des droits de l'homme
227 
+globe d'utiliser Tor pour &ldquo;une navigation et des communications
228 
+sûres.&rdquo;
229 
+</li>
230 
+<li> Tor a été consulté et s'est porté volontaire pour aider la récente
231 
+<strong>campagne d'Amnesty International <a
232 
+href="http://irrepressible.info/">contre la répression</a></strong>.Voir
233 
+également leur <a
234 
+href="http://irrepressible.info/static/pdf/FOE-in-china-2006-lores.pdf">rapport
235 
+complet</a> sur les problèmes de l'Internet Chinois.
236 
+</li>
237 
+<li><a href="http://www.globalvoicesonline.org">Global Voices</a>recommande Tor,
238 
+spécialement pour le <strong>blog anonyme</strong>,par le moyen de leur <a
239 
+href="http://advocacy.globalvoicesonline.org/projects/guide/">site web.</a>
240 
+</li>
241 
+<li>Aux États-Unis, la Cour suprême a récemment supprimé la protection juridique
242 
+des indics du gouvernement.  Mais ces personnes qui travaillent pour la
243 
+transparence gouvernementale ou pour la responsabilité d'entreprises peuvent
244 
+utiliser Tor pour réclamer justice sans répercussions personnelles.
245 
+</li>
246 
+<li>Un de nos contacts qui travaille dans une ONG dédiée à la santé en Afrique
247 
+rapporte que son organisation <strong>doit affecter 10% de son budget pour
248 
+payer les différentes sortes de corruption</strong>, pour la majorité des
249 
+pots-de-vin et autres.  Lorsque ce pourcentage augmente fortement,ils n'ont
250 
+ni les moyens de payer, ni les moyens de  se plaindre &mdash; car à tout
251 
+moment faire des objections peut devenir dangereux.  Ainsi, son association
252 
+a commencé à <strong>utiliser Tor pour dénoncer en toute sécurité la
253 
+corruption du gouvernement</strong> afin de pouvoir continuer à travailler.
254 
+</li>
255 
+<li>Lors d'une récente conférence, un membre du personnel Tor s'est heurté à une
256 
+femme qui venait d'une "ville-entreprise" de l'est des États-Unis. Elle a
257 
+tenté en bloguant anonymement de rallier les résidents à <strong>d'urgentes
258 
+réformes dans l'entreprise </strong> qui dominait les affaires économiques
259 
+et municipales de la ville. Elle était pleinement consciente que le type
260 
+d'activité qu'elle avait lancé, pouvait <strong>conduire à des dommages ou
261 
+&ldquo; des accidents fatals&rdquo;.</strong>
262 
+</li>
263 
+<li>En Asie du Sud-Est, certains syndicalistes utilisent l'anonymat pour
264 
+<strong>révéler certaines informations concernant les ateliers
265 
+clandestins</strong>qui produisent des biens pour les pays occidentaux. Ils
266 
+l'utilisent également pour organiser la main-d'oeuvre locale.
267 
+</li>
268 
+<li>
269 
+Tor can help activists avoid government or corporate censorship that hinders
270 
+organization.  In one such case, a <a
271 
+href="http://www.cbc.ca/canada/story/2005/07/24/telus-sites050724.html">Canadian
272 
+ISP blocked access to a union website used by their own employees</a> to
273 
+help organize a strike.
274 
+</li>
275 
+</ul>
276 
+
277 
+<a name="spotlight"></a>
278 
+<h2><a class="anchor" href="#spotlight">Des personnes de toutes conditions
279 
+utilisent Tor</a></h2>
280 
+<hr />
281 
+<ul>
282 
+<li>Est ce qu'être sous le feu des projecteurs doit vous priver pour toujours
283 
+d'avoir une vie privée en ligne ? Par exemple, un avocat en milieu rural
284 
+dans l'état de Nouvelle Angleterre garde son blog anonyme car la diversité
285 
+de la clientèle de son prestigieux cabinet pourrait être <strong>offensée
286 
+par ses convictions politiques</strong>.  Pourtant, il n'en a pas moins
287 
+l'intention de garder le silence sur des questions qui le préoccupent.  Tor
288 
+l'aide à se sentir en sécurité pour exprimer son opinion sans conséquences
289 
+dans son activité publique.
290 
+</li>
291 
+<li>Les personnes vivant dans la pauvreté participent peu à la vie civile -- non
292 
+par ignorance ou apathie, mais à cause de la peur.  Si quelque chose que
293 
+vous avez écrit, revenait aux oreilles de votre patron,  perdriez-vous votre
294 
+emploi ? Si votre assistante sociale lit votre opinion sur le système,
295 
+pourrait-elle vous traiter différemment ? L'anonymat redonne une voix à ceux
296 
+qui n'en n'ont pas. Pour améliorer la situation, <strong>Tor a actuellement
297 
+un poste ouvert disponible par Americorps/VISTA</strong>.  Cette subvention
298 
+gouvernementale couvrira la rémunération à temps plein d'un volontaire pour
299 
+créer des programmes ayant pour objectif de <strong>montrer aux populations
300 
+à faible revenu comment utiliser l'anonymat en ligne en vue d'un engagement
301 
+civique sécurisé</strong>.  Même si l'on dit souvent que les personnes
302 
+pauvres n'utilisent pas Internet pour l'engagement civique, ne pouvant ainsi
303 
+agir pour leur propre cause, notre hypothèse  (basée sur des conversations
304 
+personnelles et des informations reçues) est que c'est précisément le
305 
+&rdquo;flicage en ligne permanent&rdquo; qui empêche ces personnes de
306 
+prendre la parole sur Internet.  Nous espérons montrer aux gens comment
307 
+s'engager de manière sécurisée sur Internet; puis à la fin de l'année, nous
308 
+aimerions évaluer comment à évolué l'engagement civique en ligne et hors
309 
+ligne, et comment la population perçoit cela dans l'avenir.
310 
+</li>
311 
+</ul>
312 
+
313 
+<a name="executives"></a>
314 
+<h2><a class="anchor" href="#executives">Des entreprises utilisent Tor</a></h2>
315 
+<hr />
316 
+<ul>
317 
+<li><strong>Protections des fuites d'informations dans les
318 
+référentiels:</strong> Supposons qu'une institution financière participe à
319 
+un regroupement d'informations sur la sécurité des attaques sur Internet.
320 
+Un tel répertoire exige de ses membres qu'ils retransmettent les infractions
321 
+à une autorité centrale, qui corrèle les attaques coordonnées afin d'en
322 
+détecter les modalités et qui envoie des alertes.  Mais si une banque de
323 
+Saint-Louis en particulier est attaquée, elle ne voudra sans doute pas qu'un
324 
+attaquant qui observerait le trafic arrivant dans ce répertoire, puisse
325 
+tracer l'origine de l'information.  Même si chaque paquet est chiffré,
326 
+l'adresse IP peut trahir la localisation du système compromis.  Tor permet à
327 
+de tels répertoires de résister à ces attaques.
328 
+</li>
329 
+<li><strong>Observer ce que font vos concurrents sur le marché:</strong> Si vous
330 
+essayez de consulter les prix d'un concurrent, il est possible que vous ne
331 
+trouviez aucune information ou alors des informations trompeuses sur leur
332 
+site web. La cause de ce problème est qu'il est techniquement possible de
333 
+configurer un serveur Web pour qu'il détecte les connexions des concurrents,
334 
+et qu'il les bloque ou renvoie des fausses informations à votre personnel.
335 
+Tor permet à une entreprise d'observer leur secteur d'activité de la même
336 
+manière que le grand public peut le percevoir.
337 
+</li>
338 
+<li><strong>Garder confidentielles les stratégies:</strong>Une banque
339 
+d'investissement, par exemple, peut ne pas vouloir que les fureteurs de
340 
+l'industrie soient capables de tracer quels sites ces analystes
341 
+surveillent. L'importance stratégique des analyses de trafic, et la
342 
+vulnérabilité de la surveillance de ces données, commence à être plus
343 
+largement connue dans différents domaines du monde des affaires.
344 
+</li>
345 
+<li><strong>Responsabilisation:</strong> A une époque où, une activité
346 
+irresponsable et cachée dans une entreprise peut compromettre des milliards
347 
+de dollars de recettes, un directeur exécutif peut vouloir vraiment que tout
348 
+son personnel soit libre de rapporter les malversations internes.  Tor
349 
+facilite la responsabilisation interne avant qu'elle ne se transforme en
350 
+dénonciation.
351 
+</li>
352 
+</ul>
353 
+
354 
+<a name="bloggers"></a>
355 
+<h2><a class="anchor" href="#bloggers">Des Blogueurs utilisent Tor</a></h2>
356 
+<hr />
357 
+<ul>
358 
+<li>Nous entendons souvent parler de blogueurs qui sont <a
359 
+href="http://online.wsj.com/public/article/SB112541909221726743-Kl4kLxv0wSbjqrkXg_DieY3c8lg_20050930.html">poursuivis</a>
360 
+ou <a
361 
+href="http://www.usatoday.com/money/workplace/2005-06-14-worker-blogs-usat_x.htm">virés</a>
362 
+pour avoir dit des choses parfaitement légales en ligne, dans leur blog.</li>
363 
+<li>Nous recommandons le <a
364 
+href="http://www.eff.org/issues/blogger/legal/">Guide juridique de l'EFF
365 
+pour les blogueurs</a>.</li>
366 
+<li>Global Voices tient à jour un <a
367 
+href="http://advocacy.globalvoicesonline.org/projects/guide/">Guide du blog
368 
+anonyme avec Wordpress et Tor</a>.</li>
369 
+</ul>
370 
+
371 
+<a name="itprofessionals"></a>
372 
+<h2><a class="anchor" href="#itprofessionals">Des professionels de
373 
+l'informatique utilisent Tor</a></h2>
374 
+<hr />
375 
+<ul>
376 
+<li>Pour vérifier les règles IP des pare-feux: un pare-feux peut avoir plusieurs
377 
+règles qui autorisent seulement certaines adresses ou plages d'adresses
378 
+IP. Tor peut être utilisé pour vérifier cette configuration en utilisant une
379 
+adresse IP située en dehors du bloc d'adresse alloué à l'entreprise.</li>
380 
+<li>Pour échapper à leur propres systèmes de sécurité dans le cadre de leur
381 
+activité professionnelle: Par exemple, une entreprise peut avoir des règles
382 
+strictes en ce qui concerne ce que ses employés peuvent consulter sur
383 
+Internet. Une revue de fichier de log révèle une possible transgression. Tor
384 
+peut être utilisé pour vérifier cette information sans remonter d'alerte
385 
+dans le système de sécurité de l'entreprise.</li>
386 
+<li>Pour se connecter de dehors à des services mis en route: Un ingénieur réseau
387 
+peut utiliser Tor dans son protocole de test pour se connecter à distance à
388 
+ses propres services, sans avoir besoin d'utiliser une machine extérieure ou
389 
+un compte utilisateur différent.</li>
390 
+<li>Pour accéder à des ressources internet: Les règles d'accès à Internet sont
391 
+différentes entre celles du personnel informatique et les autres
392 
+employés. Tor peut permettre un accès sans entrave à Internet tout en
393 
+laissant les règles de sécurité standardes en place.</li>
394 
+<li>Pour passer outre les interruptions de service des FAI: Parfois, quand un
395 
+FAI a des problèmes de routage ou de DNS, Tor permet d'accéder à des
396 
+ressources Internet, alors que le FAI fonctionne mal. C'est particulièrement
397 
+important lors de situations de crise. </li>
398 
+</ul>
399 
+
400 
+<p>
401 
+Merci de nous envoyer vos histoires de réussite. C'est très important car
402 
+Tor préserve l'anonymat.Il est passionnant de spéculer sur les <a
403 
+href="<page faq-abuse>">effets indésirables de Tor</a>, mais quand cela
404 
+fonctionne, personne n'en parle. C'est idéal pour les utilisateurs, mais pas
405 
+très bon pour nous, car la publications d'histoires sur la façon dont les
406 
+personnes ou les  organisations peuvent rester anonymes peut-être contre
407 
+productive. Par exemple, nous avons parlé à un agent du FBI qui a expliqué
408 
+qu'il utilise Tor tous les jours pour son travail &mdash; mais qui a
409 
+rapidement demandé de ne pas fournir des détails ou de mentionner son nom.</p>
410 
+
411 
+<p> Comme toute technologie, du stylo au téléphone portable, l'anonymat peut
412 
+être utilisé, à la fois, pour le bien ou le mal.  Nous avons probablement lu
413 
+beaucoup de vigoureux débats (<a
414 
+href="http://www.wired.com/politics/security/commentary/securitymatters/2006/01/70000">pour</a>,
415 
+<a href="http://www.edge.org/q2006/q06_4.html#kelly">contre</a>, et <a
416 
+href="http://web.mit.edu/gtmarx/www/anon.html">académique</a>) sur
417 
+l'anonymat. Le projet Tor project est basé sur la pensée que l'anonymat
418 
+n'est pas seulement une bonne idée de temps en temps - mais que c'est
419 
+nécessaire pour le fonctionnement d'une société libre. L'<a
420 
+href="http://www.eff.org/issues/anonymity">EFF presente un bon aperçu</a> de
421 
+la manière dont l'anonymat fut essentiel à la fondation des
422 
+États-Unis. L'anonymat est reconnu par les tribunaux américains comme un
423 
+élément fondamental et important. En fait, les gouvernements recommandent
424 
+eux-mêmes l'anonymat dans bien des cas:<a
425 
+href="https://www.crimeline.co.za/default.asp">service d'indicateurs de
426 
+police</a>,<a
427 
+href="http://www.texasbar.com/Content/ContentGroups/Public_Information1/Legal_Resources_Consumer_Information/Family_Law1/Adoption_Options.htm#sect2">services
428 
+d'adoption</a>,<a
429 
+href="http://writ.news.findlaw.com/aronson/20020827.html">identités des
430 
+officiers de Police</a>,et ainsi de suite. Il serait impossible d'abréger
431 
+l'ensemble du débat sur l'anonymat ici - il est trop grand et il y a trop de
432 
+nuances à apporter, et il y a beaucoup d'autres lieux où ces informations
433 
+peuvent être trouvées. Nous avons une page <a href="<page faq-abuse>">Tor
434 
+abus</a> qui décrit quelques uns des abus possibles de Tor, mais il faut
435 
+dire que si vous voulez d'abuser du système, vous trouverez plutôt fermé
436 
+pour vos besoins (par ex. la majorité des relais Tor ne supportent pas le
437 
+SMTP pour prévenir le spam par email anonyme), or et si vous êtes l'un des
438 
+<a
439 
+href="http://www.schneier.com/blog/archives/2005/12/computer_crime_1.html">quatres
440 
+cavaliers de l'Apocalypse de l'Information</a>, vous avez de meilleurs choix
441 
+que Tor. Sans exclure les éventuels abus de Tor, cette page montre
442 
+quelques-unes des nombreuses importantes manières dont l'anonymat en ligne
443 
+est utilisé, de nos jours.</p>
444 
+</div>
445 
+#include <foot.wmi>
fr/trademark-faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,93 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+## translation metadata
7 
+# Revision: $Revision: 22138 $
8 
+# Translation-Priority: 3-low
9 
+#include "head.wmi" TITLE="Tor Trademark FAQ" CHARSET="UTF-8"
10 
+<div class="main-column">
11 
+
12 
+
13 
+<!-- PUT CONTENT AFTER THIS TAG -->
14 
+<h1>Questions Fréquemment Posées sur la marque Tor</h1>
15 
+<hr />
16 
+
17 
+<a id="usage"></a>
18 
+<h2>Comment puis-je utiliser le nom "Tor"?</h2>
19 
+<p>The Tor Project encourages developers to use the name Tor in ways that do
20 
+not confuse the public about the source of anonymity software and services.
21 
+If you are building open-source non-commercial software or services that
22 
+incorporate or work with The Tor Project's code, you may use the name
23 
+“Tor” in an accurate description of your work.  We ask you to include a
24 
+link to the official Tor website <a
25 
+href="https://www.torproject.org/">https://www.torproject.org/</a> so users
26 
+can verify the original source of Tor for themselves, and a note indicating
27 
+that your project is not sponsored by The Tor Project. For example, “This
28 
+product is produced independently from the Tor&#174; anonymity software and
29 
+carries no guarantee from The Tor Project about quality, suitability or
30 
+anything else.”</p>
31 
+
32 
+<a id="onionlogo"></a>
33 
+<h2>Puis-je utiliser le logo oignon de Tor ?</h2>
34 
+<p>Si vous faites un usage non-commercial du logiciel Tor, vous pouvez
35 
+également utiliser le logo en oignon de Tor (à titre d'illustration, et non
36 
+comme une marque pour vos produits). Merci de ne pas modifier la forme ou
37 
+les couleurs du logo.  Vous pouvez utiliser les images qui ressemblent au
38 
+logo en oignon de Tor pour illustrer un point (ex: un éclaté d'oignon avec
39 
+des couches, en l'occurrence), tant qu'ils sont pas utilisés comme des logos
40 
+risquant d'induire en erreur les personnes.</p>
41 
+
42 
+<a id="combining"></a>
43 
+<h2>Puis-je utiliser le mot "Tor" dans le cadre du nom de mon produit ou mon nom
44 
+de domaine?</h2>
45 
+<p>Nous vous recommandons de ne pas le faire, mais plutôt de trouver un nom qui
46 
+permettra d'identifier avec précision <i>vos</i> produits ou services.
47 
+N'oubliez pas que notre objectif est de faire en sorte que personne ne soit
48 
+induit en erreur de savoir si votre produit ou tout autre projet est réalisé
49 
+ou approuvé par le projet Tor. La création d'une nouvelle marque, intégrant
50 
+les marques de Tor, est susceptible de prêter à confusion.</p>
51 
+
52 
+<a id="enforcing"></a>
53 
+<h2>Cela signifie t'il que vous restreignez la marque?</h2>
54 
+<p>Le projet Tor est un organisme à but non lucratif dédié à la recherche et au
55 
+développement du logiciel d'anonymat Tor et du réseau éponyme.  Nous ne
56 
+voulons pas être des tyrans des marques, mais nous voulons utiliser les
57 
+marques pour protéger la capacité du public à reconnaître les logiciels du
58 
+projet Tor.  Une marque commerciale nous aide à assurer que le nom est
59 
+utilisé seulement dans le cadre du véritable logiciel d'anonymat Tor et pour
60 
+un ensemble précis de logiciels et de services.  Après tout, pour protéger
61 
+la sécurité de leur anonymat, les utilisateurs d'ordinateurs doivent être en
62 
+mesure d'identifier les logiciels qu'ils utilisent, afin qu'ils puissent
63 
+correctement identifier leurs forces et leurs faiblesses.  Tor est reconnu
64 
+comme le nom d'un logiciel et des réseaux de relais d'anonymat par routage
65 
+en oignon, avec une documentation en ligne, des instructions pour renforcer
66 
+la protection de l'anonymat, et des rappels car, même à ce stade, il reste
67 
+un logiciel expérimental.  Nous travaillons avec les développeurs afin
68 
+d'améliorer le logiciel et le réseau et nous encourageons activement les
69 
+chercheurs à documenter les attaques pour nous aider à renforcer toujours
70 
+plus la protection de son anonymat.  Nous distribuons librement le logiciel
71 
+complet, mais nous exigeons une présentation correcte des droits. </p>
72 
+
73 
+<a id="commercial"></a>
74 
+<h2>Que faire si je crée des produits commerciaux, non open source, basés sur
75 
+Tor?</h2>
76 
+<p>Contactez-nous, pour en parler.</p>
77 
+
78 
+<a id="licensee"></a>
79 
+<h2>Y a t'il des licences officielles des marques Tor ?</h2>
80 
+<p>Oui.  Quelques projets open source, non-commerciaux utilisent les marques
81 
+Tor sous licence:</p>
82 
+<ul>
83 
+<li><a href="https://amnesia.boum.org/">Le système live (Amnesic) Incognito</a></li>
84 
+<li><a href="http://portabletor.sourceforge.net/">Portable Tor</a></li>
85 
+<li><a href="http://torstatus.kgprog.com/">Kprog Tor Status</a></li>
86 
+<li><a href="http://www.vidalia-project.net/">Vidalia</a></li>
87 
+<li><a href="http://www.anonymityanywhere.com/tork/">TorK</a></li>
88 
+</ul>
89 
+
90 
+</div>
91 
+
92 
+
93 
+#include <foot.wmi>
fr/translation-overview.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,179 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="Tor: Translation Overview" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h1>Tor: Présentation générale des traductions</h1>
14 
+<hr />
15 
+
16 
+<p>
17 
+Le Pack Tor inclut différents types de logiciels, chacun d'eux nécessite un
18 
+travail de traduction. Par ordre d'importance il y a: <a href="<page
19 
+vidalia/index>">Vidalia</a>, <a href="<page torbutton/index>">Torbutton</a>,
20 
+et <a href="https://check.torproject.org/">TorCheck</a>.  Merci de lire les
21 
+paragraphes ci-dessous et d'apporter votre aide. Si vous avez besoin d'aide,
22 
+merci de le demander, nous sommes toujours heureux de donner un coup de
23 
+main.
24 
+</p>
25 
+
26 
+<a id="TTP"></a> <a id="TTPVidalia"></a>
27 
+<h2><a class="anchor" href="#TTP">Utiliser le Portail de Traduction de Tor</a></h2>
28 
+<hr />
29 
+
30 
+<p>
31 
+Le <a href="https://translation.torproject.org/">Portail de Traduction
32 
+Tor</a> est un site web qui permet aux utilisateurs de contribuer aux
33 
+traductions en ligne à l'aide de leur navigateur web. Il répertorie toutes
34 
+les mots ou phrases (appelées "chaines") utilisées dans un projet en
35 
+particulier, et permet aux bénévoles intéressés de traduire individuellement
36 
+les phrases ou les expressions qu'ils peuvent.
37 
+</p>
38 
+
39 
+<p>
40 
+Vous pouvez vérifier l'état de toutes les traductions pour un projet donné
41 
+en visitant chaque page du projet.  Les états suivants sont mis à jour en
42 
+temps réel lorsque de nouvelles traductions sont ajoutées: <a
43 
+href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>, <a
44 
+href="https://translation.torproject.org/projects/torbutton/">Torbutton</a>,
45 
+et <a
46 
+href="https://translation.torproject.org/projects/torcheck/">TorCheck</a>.
47 
+</p>
48 
+
49 
+<p>
50 
+Pour débuter la traduction en utilisant le portail de traduction, vous devez
51 
+y ouvrir un compte. Pour commencer, visitez <a
52 
+href="https://translation.torproject.org/register.html">la page de création
53 
+de compte</a>. Assurez-vous de saisir une adresse e-mail valide et un mot de
54 
+passe robuste. Après avoir rempli le formulaire et utilisé le bouton
55 
+'Register Account', vous devriez voir un texte indiquant que les choses se
56 
+sont bien déroulées:
57 
+</p>
58 
+<pre>
59 
+Account created. You will be emailed login details and an activation code.
60 
+Please enter your activation code on the activation page.
61 
+</pre>
62 
+
63 
+<p>
64 
+Peu de temps après avoir vu ce texte, un email sera envoyé à l'adresse
65 
+électronique que vous avez saisie. L'email doit ressembler à ce qui suit:
66 
+</p><pre>
67 
+A Pootle account has been created for you using this email address.
68 
+Your activation code is:
69 
+36074ec543c1fa23ceeaf8e187dfa43e
70 
+This message is sent to verify that the email address is in fact correct. If
71 
+you did not want to register an account, you may simply ignore the message.
72 
+Your user name is: example_user
73 
+Your password is: example_user
74 
+Your registered email address is: username@example.com
75 
+</pre>
76 
+
77 
+<p>
78 
+Une fois que vous avez reçu l'email, vous devrez visiter <a
79 
+href="https://translation.torproject.org/activate.html">la page
80 
+d'activation</a> afin d'activer votre compte.  Saisissez votre nom
81 
+d'utilisateur et le code d'activation dans le formulaire et validez le
82 
+formulaire en appuyant sur le bouton "Activate Account". Vous verrez un
83 
+message disant:
84 
+</p><pre>
85 
+Redirecting to login Page...
86 
+Your account has been activated! Redirecting to login...
87 
+</pre>
88 
+
89 
+<p>
90 
+Lorsque vous vous connectez à votre nouveau compte, vous serez invité à
91 
+configurer vos préférences linguistiques sur <a
92 
+href="https://translation.torproject.org/home/options.html">la page
93 
+d'options</a>. Tout à la fin, vous devrez sélectionner la langue de
94 
+l'interface utilisateur, sélectionner un des projets dont la traduction vous
95 
+intéresse, et en complément les langues vous désirez traduire. Enregistrez
96 
+vos modifications en cliquant sur le bouton "Save Changes" lorsque vous avez
97 
+terminé.
98 
+</p>
99 
+
100 
+<p>
101 
+Vous êtes prêt à traduire !
102 
+</p>
103 
+
104 
+<p>
105 
+A partir de là, vous pouvez sélectionner un projet, par exemple: <a
106 
+href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>.
107 
+Vous aurez alors une liste de toutes les langues prises en charge ainsi que
108 
+l'état actuel de leur traduction. Sélectionnez une langue,&mdash; dans notre
109 
+exemple, vous cliquerez sur <a
110 
+href="https://translation.torproject.org/fr/vidalia/">Français</a>. La
111 
+prochaine page doit vous montrer une seule ligne de données pour le fichier
112 
+"<a
113 
+href='https://translation.torproject.org/fr/vidalia/vidalia_fr.po?translate=1&amp;view=1'>vidalia_fr.po</a>".
114 
+C'est le fichier, avec toutes les chaînes de caractères traduites en
115 
+français pour Vidalia. Vous aurez besoin de cliquer sur le lien "<a
116 
+href='https://translation.torproject.org/fr/vidalia/index.html?editing=1'>Show
117 
+Editing Functions</a>" au dessus de la ligne 'vidalia_fr.po'. Ensuite, vous
118 
+pouvez cliquez sur le lien "<a
119 
+href='https://translation.torproject.org/fr/vidalia/translate.html?fuzzy=1&amp;editing=1&amp;blank=1'>Quick
120 
+Translate</a>". Ceci vous mènera à la première chaîne non traduite dans la
121 
+langue correspondante du projet en cours.
122 
+</p>
123 
+
124 
+<p>
125 
+Si vous en êtes capable, merci de traduire la chaîne que vous voyez et de
126 
+cliquez sur le bouton 'Submit'. Si vous n'êtes pas sûr, cliquez sur le lien
127 
+'Suggest'. N'hésitez pas à laisser des commentaires pour l'une des
128 
+traductions si vous pensez que cela est important pour clarifier un point
129 
+quelconque.
130 
+</p>
131 
+
132 
+<p>
133 
+Lorsque vous avez terminé, vous validerez vos changements en retournant à la
134 
+page <a
135 
+href="https://translation.torproject.org/fr/vidalia/index.html?editing=1">Editing
136 
+Functions</a>. et en cliquant sur le lien "<a
137 
+href='https://translation.torproject.org/de/vidalia/index.html?editing=1&amp;docommit=1&amp;commitfile=vidalia_de.po'>Commit</a>".
138 
+Cela validera vos changements dans le <a
139 
+href="https://svn.torproject.org/svn/translation/trunk/projects/vidalia/fr/">Module
140 
+subversion de traduction</a> dans la partie spécifique correspondant à vos
141 
+choix de langue et de projet (Vidalia et Français, pour cet example).
142 
+</p>
143 
+
144 
+<p>
145 
+C'est tout ce qu'il y a à faire ! Refaîtes ces étapes et contribuez
146 
+également à Torbutton et à Torcheck.
147 
+</p>
148 
+
149 
+<p>
150 
+Si votre langue n'est pas encore dans la liste des options, envoyez un email
151 
+à <tt>tor-translation AT torproject.org</tt> et nous l'ajouterons pour vous.
152 
+</p>
153 
+
154 
+<p>
155 
+Pour les utilisateurs plus expérimentés qui aiment traduire sans l'aide d'un
156 
+navigateur Web, vous pouvez également télécharger directement le fichier
157 
+.po. Vous trouverez cette option après avoir cliqué sur le lien "<a
158 
+href='https://translation.torproject.org/de/vidalia/index.html?editing=1'>Show
159 
+Editing Functions</a>". Vous devriez voir un lien pour télécharger le "<a
160 
+href="https://translation.torproject.org/de/vidalia/vidalia_de.po">fichier
161 
+PO</a>".  Si cette option correspond à vos habitudes de travail, merci de
162 
+l'utiliser le plus souvent ! Vous pouvez utiliser le logiciel nommé <a
163 
+href="http://www.poedit.net/">Poedit</a> pour rendre plus facile ce travail,
164 
+particulièrement pour les langues s'écrivant de droite à gauche qui ne
165 
+fonctionnent pas aussi bien dans les éditeurs de texte. Si vous utilisez
166 
+Poedit, vous devriez supprimer la compilation des fichiers .mo dans les
167 
+préférences de Poedit (Fichier -&gt; Préférences -&gt; Editeur -&gt;
168 
+Comportement, décocher "Compiler automatiquement les fichiers .mo lors de la
169 
+sauvegarde"). Lorsque vous avez fini la traduction du fichier .po, vous
170 
+pouvez le télécharger en utilisant le formulaire "upload file" dans le coin
171 
+supérieur droit, il suffit de sélectionner le fichier et de cliquez sur le
172 
+bouton"Upload file".
173 
+</p>
174 
+
175 
+  </div>
176 
+
177 
+
178 
+
179 
+#include <foot.wmi>
fr/translation.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,64 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="Tor Website Translation Guidelines" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Conseils aux traducteurs du site web de Tor</h2>
14 
+<hr />
15 
+
16 
+<p>
17 
+Si vous voulez nous aider à traduire le site web de Tor et la documentation,
18 
+voici quelques recommandations qui vous aideront à effectuer cette tâche le
19 
+mieux possible.
20 
+</p>
21 
+
22 
+<p>
23 
+Si vous souhaiter nous aider à traduire les autres projets liés à Tor, merci
24 
+de consulter notre <a href="<page translation-overview>">présentation
25 
+générale des traductions</a> pour comprendre clairement ce qui a besoin
26 
+d'être traduit. Si vous êtes coincé, merci de nous contacter par e-mail:
27 
+<tt>tor-translation AT torproject.org</tt>.
28 
+</p>
29 
+
30 
+<p>
31 
+Pour vous donner une idée de l'avancement de la traduction, nous avons créé
32 
+une page présentant <a href="<page translation-status>">l'état des
33 
+traductions</a>.</p>
34 
+
35 
+<p>
36 
+Notez que si vous ne pouvez pas traduire beaucoup de pages dans votre
37 
+langue, quelques pages seront tout de même appréciées.  De même, plutôt que
38 
+de traduire mot à mot chaque page, merci d'essayer de traduire les idées
39 
+afin que cela ait le plus de sens possible dans votre langue.</p>
40 
+
41 
+<ol>
42 
+<li>Nous aimerions également des traductions des schémas de <a href="<page
43 
+overview>">la page d'aperçu</a>. Vous pouvez nous envoyer juste le texte qui
44 
+doit figurer sur les schémas et nous nous chargerons de créer les nouvelles
45 
+versions des images.</li>
46 
+
47 
+<li>Lorsque vous avez des pages prêtes, envoyez les à l'adresse
48 
+<tt>tor-translation</tt> figurant sur la <a href="<page contact>">page de
49 
+contact</a>.  (Si vous avez juste des changements sur des pages existantes,
50 
+merci d'utiliser l'outil diff pour générer des fichiers patch, si
51 
+possible).  Si vous envisagez de continuer à les maintenir, nous serons
52 
+enchantés de vous donner un compte SVN pour les mettre à jour directement.</li>
53 
+</ol>
54 
+
55 
+<p>Les autres projets liés à Tor ont également besoin de traducteurs. Merci de
56 
+voir notre portail de traduction pour <a href="<page
57 
+translation-overview>">traduire d'autres logiciels utiles et liés à Tor</a>.
58 
+</p>
59 
+
60 
+  </div>
61 
+
62 
+
63 
+
64 
+#include <foot.wmi>
getinvolved/.deps/.stamp
Zeige Datei @ 2a9aaa802
getinvolved/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1 @@
1 
+include $(WMLBASE)/Makefile.common
getinvolved/en/developers.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,23 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Get Involved" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved &raquo; </a>
10 
+    <a href="<page getinvolved/developers>">Developers</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+    <h1>Developers</h1>
14 
+  </div>
15 
+  <!-- END MAINCOL -->
16 
+  <div id = "sidecol">
17 
+#include "side.wmi"
18 
+#include "info.wmi"
19 
+  </div>
20 
+  <!-- END SIDECOL -->
21 
+</div>
22 
+<!-- END CONTENT -->
23 
+#include <foot.wmi>
getinvolved/en/everyone.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,23 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Get Involved" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved &raquo; </a>
10 
+    <a href="<page getinvolved/everyone>">Everyone</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+    <h1>Everyone</h1>
14 
+  </div>
15 
+  <!-- END MAINCOL -->
16 
+  <div id = "sidecol">
17 
+#include "side.wmi"
18 
+#include "info.wmi"
19 
+  </div>
20 
+  <!-- END SIDECOL -->
21 
+</div>
22 
+<!-- END CONTENT -->
23 
+#include <foot.wmi>
getinvolved/en/getinvolved.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,101 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Get Involved with Tor" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+  	<h1>Get Involved</h1>
13 
+    <p class="left forty"><strong>Your support is critical to our success.</strong> Consectetur adipiscing elit. Proin sit amet dolor justo, lacinia dapibus est. Lorem ipsum dolor sit amet, consectetur adipiscing elit. In orci est, pellentesque sit amet consequat eget, venenatis id augue.</p>
14 
+    <div class="focus right fifty">
15 
+    	<img class="icon" src="$(IMGROOT)/icon-relay-lg.jpg" alt="Run a Relay" />
16 
+    	<div class="name">Run a Relay</div>
17 
+      <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
18 
+    </div>
19 
+    <!-- END FOCUS -->
20 
+    <table class="toptwenty">
21 
+    	<tr>
22 
+        <td class="beige">
23 
+    			<img class="icon" src="$(IMGROOT)/icon-donate.jpg" alt="Donate" />
24 
+          <span class="name">Donate</span><span class="meta"><a href="#">Everyone</a></span>
25 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
26 
+					<a href="#">Learn more &raquo;</a></p>
27 
+      	</td>
28 
+        <td>
29 
+    			<img class="icon" src="$(IMGROOT)/icon-translate.jpg" alt="Translate" />
30 
+          <span class="name">Translate</span><span class="meta"><a href="#">Technical</a></span>
31 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
32 
+					<a href="#">Learn more &raquo;</a></p>
33 
+        </td>
34 
+      </tr>
35 
+      <tr>
36 
+        <td>
37 
+    			<img class="icon" src="$(IMGROOT)/icon-development.jpg" alt="Development" />
38 
+          <span class="name">Development</span><span class="meta"><a href="#">Developer</a></span>
39 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
40 
+					<a href="#">Learn more &raquo;</a></p>
41 
+        </td>
42 
+        <td class="beige">
43 
+    			<img class="icon" src="$(IMGROOT)/icon-documentation.jpg" alt="Documentation" />
44 
+          <span class="name">Documentation</span><span class="meta"><a href="#">Technical</a></span>
45 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
46 
+					<a href="#">Learn more &raquo;</a></p>
47 
+        </td>
48 
+      </tr>
49 
+      <tr>
50 
+        <td class="beige">
51 
+    			<img class="icon" src="$(IMGROOT)/icon-design.jpg" alt="Design" />
52 
+          <span class="name">Design</span><span class="meta"><a href="#">Developer</a></span>
53 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
54 
+					<a href="#">Learn more &raquo;</a></p>
55 
+        </td>
56 
+        <td>
57 
+    			<img class="icon" src="$(IMGROOT)/icon-advocacy.jpg" alt="Advocacy" />
58 
+          <span class="name">Advocacy</span><span class="meta"><a href="#">Everyone</a></span>
59 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
60 
+					<a href="#">Learn more &raquo;</a></p>
61 
+        </td>
62 
+      <tr>
63 
+        <td>
64 
+    			<img class="icon" src="$(IMGROOT)/icon-research.jpg" alt="Research" />
65 
+          <span class="name">Research</span><span class="meta"><a href="#">Everyone</a></span>
66 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
67 
+					<a href="#">Learn more &raquo;</a></p>
68 
+        </td>
69 
+        <td class="beige">
70 
+    			<img class="icon" src="$(IMGROOT)/icon-jobs.jpg" alt="Jobs" />
71 
+          <span class="name">Jobs</span><span class="meta"><a href="#">Developer</a></span>
72 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
73 
+          <a href="#">Learn more &raquo;</a></p>
74 
+        </td>
75 
+      </tr>
76 
+      <tr>
77 
+        <td class="beige">
78 
+    			<img class="icon" src="$(IMGROOT)/icon-relay-sm.jpg" alt="Run a Relay" />
79 
+          <span class="name">Run a Relay</span><span class="meta"><a href="#">Everyone</a></span>
80 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
81 
+					<a href="#">Learn more &raquo;</a></p>
82 
+        </td>
83 
+        <td>
84 
+    			<img class="icon" src="$(IMGROOT)/icon-hardware.jpg" alt="Give Hardware" />
85 
+          <span class="name">Give Hardware</span><span class="meta"><a href="#">Everyone</a></span>
86 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.<br />
87 
+					<a href="#">Learn more &raquo;</a></p>
88 
+        </td>
89 
+      </tr>
90 
+      </table>
91 
+    <!-- END FAUXTABLE -->
92 
+  </div>
93 
+  <!-- END MAINCOL -->
94 
+  <div id = "sidecol">
95 
+#include "side.wmi"
96 
+#include "info.wmi"
97 
+  </div>
98 
+  <!-- END SIDECOL -->
99 
+</div>
100 
+<!-- END CONTENT -->
101 
+#include <foot.wmi>
getinvolved/en/mirrors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,49 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Mirrors" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/mirrors>">Mirrors</a>
10 
+  </div>
11 
+  <div id="maincol">
12 
+    <h2>Tor: Mirrors</h2>
13 
+    <hr />
14 
+
15 
+    <p>
16 
+    The canonical URL of this site is <a href="https://www.torproject.org/">https://www.torproject.org/</a>,
17 
+    but there are a few mirrors of this site in other places.
18 
+    </p>
19 
+
20 
+    <p>
21 
+    If you would like to run a mirror, please <a href="<page docs/running-a-mirror>">read
22 
+    our instructions for running a mirror</a>.
23 
+    </p>
24 
+
25 
+    <table class="mirrors">
26 
+    <tr>
27 
+      <th>Country</th>
28 
+      <th>Organisation</th>
29 
+      <th>Status</th>
30 
+      <th>ftp</th>
31 
+      <th>http dist/</th>
32 
+      <th>http website</th>
33 
+      <th>https dist/</th>
34 
+      <th>https website</th>
35 
+      <th>rsync dist/</th>
36 
+      <th>rsync website</th>
37 
+    </tr>
38 
+    #include <mirrors-table.wmi>
39 
+    </table>
40 
+  </div>
41 
+  <!-- END MAINCOL -->
42 
+  <div id = "sidecol">
43 
+#include "side.wmi"
44 
+#include "info.wmi"
45 
+  </div>
46 
+  <!-- END SIDECOL -->
47 
+</div>
48 
+<!-- END CONTENT -->
49 
+#include <foot.wmi>
getinvolved/en/open-positions.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,148 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Open Positions" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved &raquo; </a>
10 
+    <a href="<page getinvolved/open-positions>">Open Positions</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h2>Tor: Open Positions</h2>
14 
+    <hr />
15 
+
16 
+    <p>Tor is hiring!  We're looking for self-motivated individuals who are
17 
+    able to work independently and want to help make Tor better.
18 
+    </p>
19 
+
20 
+    <p>In particular, we're looking for a few people:</p>
21 
+    <ul>
22 
+    <li><a href="#sysdev">Systems Developer</a></li>
23 
+    <li><a href="#windowsdev">Microsoft Windows Developer</a></li>
24 
+    </ul>
25 
+
26 
+    <p>Working on Tor is rewarding because:</p>
27 
+    <ul>
28 
+    <li>You can work your own hours in your own locations. As long as you
29 
+    get the job done, we don't care about the process.</li>
30 
+    <li>We only write free (open source) software. The tools you make won't
31 
+    be locked down or rot on a shelf.</li>
32 
+    <li>You will work with a world-class team of anonymity experts and
33 
+    developers on what is already the largest and most active strong anonymity
34 
+    network ever.</li>
35 
+    </ul>
36 
+
37 
+    <p>
38 
+    We want you to have good communication and writing skills (in particular,
39 
+    you should know how to keep other project members informed of your
40 
+    progress), and we want you to know how to figure out what needs doing and
41 
+    then take the initiative to do it. Most project members play more than
42 
+    one role, so combination developer/activist are very welcome.
43 
+    </p>
44 
+
45 
+    <a id="sysdev"></a>
46 
+    <h3><a class="anchor" href="#sysdev">Systems Developer</a></h3>
47 
+    <ul>
48 
+    <li><strong>New Secure Updater Features</strong>:
49 
+    <br />
50 
+    Additional capabilities are needed for assisted updates of all the Tor
51 
+    related software for Windows and other operating systems. Some of the
52 
+    features to consider include:
53 
+    <ol>
54 
+    <li> Integration of the <a
55 
+    href="http://chandlerproject.org/Projects/MeTooCrypto">MeTooCrypto
56 
+    Python library</a> for authenticated HTTPS downloads.</li>
57 
+    <li> Adding a level of indirection between the timestamp signatures
58 
+    and the package files included in an update. See the "<a
59 
+    href="http://archives.seul.org/or/dev/Dec-2008/msg00010.html">Thandy
60 
+    attacks / suggestions</a>" thread on or-dev.</li>
61 
+    <li> Support locale specific installation and configuration of assisted
62 
+    updates based on preference, host, or user account language settings.
63 
+    Familiarity with Windows codepages, unicode, and other character sets
64 
+    is helpful in addition to general win32 and posix API experience and
65 
+    Python proficiency.</li>
66 
+    </ol>
67 
+    </li>
68 
+
69 
+    <li><strong>Extend the Tor Secure Auto-Update Framework</strong>:
70 
+    <p>We've developed a secure auto-update framework, codenamed <a
71 
+    href="http://gitweb.torproject.org/thandy/thandy.git/tree">Thandy</a>.  It
72 
+    needs some design work to be finished, some security decisions to be
73 
+    made, and then code written to actually get the software and
74 
+    infrastructure running.  The primary goal is to get this working on
75 
+    Microsoft Windows operating systems.  Secondary goal is to have this
76 
+    work with Apple OS X.  The <a
77 
+    href="http://gitweb.torproject.org/thandy/thandy.git/blob/HEAD:/TODO">TODO</a>
78 
+    file explains more of the goals.</p>
79 
+    <p>A person undertaking this project should have good C/C++ development
80 
+    experience. Previous experience with Qt is helpful, but not required. One
81 
+    should also have a good understanding of common security
82 
+    practices, such as package signature verification. Good writing ability
83 
+    is also important for this project, since a vital step of the project
84 
+    will be producing a design document to review and discuss
85 
+    with others prior to implementation.</p>
86 
+    </li>
87 
+    </ul>
88 
+
89 
+    <a id="windowsdev"></a>
90 
+    <h3><a class="anchor" href="#windowsdev">Microsoft Windows Developer</a></h3>
91 
+    This person needs to be very familiar with Windows at a system and
92 
+    network level.  We're looking or someone to do two projects:
93 
+    <ul>
94 
+    <li><strong>Improving Polipo on Windows</strong>:
95 
+    <p>Help port <a
96 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>
97 
+    to Windows. Example topics to tackle include:
98 
+    <ol>
99 
+    <li> the ability to asynchronously query name servers, find the system
100 
+    nameservers, and manage netbios and dns queries.</li>
101 
+    <li> manage events and buffers natively (i.e. in Unix-like OSes, Polipo
102 
+    defaults to 25% of ram, in Windows it's whatever the config
103 
+    specifies).</li>
104 
+    <li> some sort of GUI config and reporting tool, bonus if it has a
105 
+    systray icon with right clickable menu options. Double bonus if it's
106 
+    cross-platform compatible.</li>
107 
+    <li> allow the software to use the Windows Registry and handle proper
108 
+    Windows directory locations, such as "C:\Program Files\Polipo"</li>
109 
+    </ol>
110 
+    </p>
111 
+    </li>
112 
+
113 
+    <li><strong>Intermediate Level Network Device Driver</strong>:
114 
+    <br />
115 
+    The WinPCAP device driver used by Tor VM for bridged networking does
116 
+    not support a number of wireless and non-Ethernet network adapters.
117 
+    Implementation of a intermediate level network device driver for win32
118 
+    and 64bit would provide a way to intercept and route traffic over such
119 
+    networks. This project will require knowledge of and experience with
120 
+    Windows kernel device driver development and testing. Familiarity with
121 
+    Winsock and Qemu would also be helpful.
122 
+    </li>
123 
+    </ul>
124 
+
125 
+    <p>
126 
+    The best way to get noticed as a good developer is to join the community
127 
+    and start helping out. We have a great core group of developers working
128 
+    on the Tor software itself as well as supporting software like Vidalia,
129 
+    Torbutton, etc.
130 
+    </p>
131 
+
132 
+    <p>
133 
+    Periodically we get new funding to work on more development
134 
+    projects.  Your goal should be to get into the list of <a href="<page
135 
+    about/people>#Core">core project members</a> so we think of you when new
136 
+    funding arrives. We're particularly looking for Qt developers and
137 
+    people to help maintain <a href="<page projects/vidalia>">Vidalia</a>.
138 
+    </p>
139 
+  </div>
140 
+  <!-- END MAINCOL -->
141 
+  <div id = "sidecol">
142 
+#include "side.wmi"
143 
+#include "info.wmi"
144 
+  </div>
145 
+  <!-- END SIDECOL -->
146 
+</div>
147 
+<!-- END CONTENT -->
148 
+#include <foot.wmi>
getinvolved/en/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,39 @@
1 
+#!/usr/bin/wml
2 
+
3 
+## translation metadata
4 
+# Revision: $Revision: 0 $
5 
+# Translation-Priority: 2-medium
6 
+
7 
+# this structure defines the side nav bar for the /about pages
8 
+# and is the input for include/side.wmi
9 
+
10 
+# fields:
11 
+#
12 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
13 
+# that links will point to the current language if supported, and alternately
14 
+# the english version
15 
+#
16 
+# txt - the link text to be displayed. Different translations will
17 
+# need to supply alternate txt
18 
+
19 
+<:
20 
+    my $sidenav;
21 
+    $sidenav = [
22 
+        {'url'  => 'getinvolved/getinvolved',
23 
+         'txt'  => 'Get Involved',
24 
+         'subelements' => [
25 
+            {'url'  => 'getinvolved/everyone',
26 
+             'txt'  => 'Everyone',
27 
+            },
28 
+            {'url'  => 'getinvolved/technical',
29 
+             'txt'  => 'Technical Users',
30 
+            },
31 
+            {'url'  => 'getinvolved/developers',
32 
+             'txt'  => 'Developers',
33 
+            }]
34 
+        },
35 
+        {'url'  => 'donate/donate',
36 
+         'txt'  => 'Donate',
37 
+        },
38 
+    ];
39 
+:>
getinvolved/en/technical.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,23 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Get Involved" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved &raquo; </a>
10 
+    <a href="<page getinvolved/technical>">Technical</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+    <h1>Technical</h1>
14 
+  </div>
15 
+  <!-- END MAINCOL -->
16 
+  <div id = "sidecol">
17 
+#include "side.wmi"
18 
+#include "info.wmi"
19 
+  </div>
20 
+  <!-- END SIDECOL -->
21 
+</div>
22 
+<!-- END CONTENT -->
23 
+#include <foot.wmi>
getinvolved/en/translation-overview.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,177 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Translation Overview" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved &raquo; </a>
10 
+    <a href="<page getinvolved/translation-overview>">Translation Overview</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor: Translation Overview</h1>
14 
+    <hr />
15 
+
16 
+    <p>
17 
+    The Tor bundles include several different programs, all of which need
18 
+    translation help. In order of importance they are:
19 
+    <a href="<page projects/vidalia>">Vidalia</a>,
20 
+    <a href="<page projects/torbutton>">Torbutton</a>, and
21 
+    <a href="https://check.torproject.org/">TorCheck</a>.
22 
+    Please read the sections below and help out. If you need help, please
23 
+    ask; we're always happy to lend a hand.
24 
+    </p>
25 
+
26 
+    <a id="TTP"></a>
27 
+    <a id="TTPVidalia"></a>
28 
+    <h2><a class="anchor" href="#TTP">Using The Tor Translation Portal</a></h2>
29 
+    <hr />
30 
+
31 
+    <p>
32 
+    The <a href="https://translation.torproject.org/">Tor Translation Portal</a>
33 
+    is a website that lets users contribute translations online using their
34 
+    web browser. It lists all sentences or phrases (called "strings") used
35 
+    by a particular project, and allows interested volunteers to translate
36 
+    individual sentences or phrases as they are able.
37 
+    </p>
38 
+
39 
+    <p>
40 
+    You can check the status of all translations for a given project by visiting
41 
+    each project page.  The following statuses are updated in real time when new
42 
+    translations are added:
43 
+    <a href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>,
44 
+    <a href="https://translation.torproject.org/projects/torbutton/">Torbutton</a>,
45 
+    and
46 
+    <a href="https://translation.torproject.org/projects/torcheck/">TorCheck</a>.
47 
+    </p>
48 
+
49 
+    <p>
50 
+    To get started using our translation website, you need to sign up for an
51 
+    account. Visit the <a
52 
+    href="https://translation.torproject.org/register.html">account registration
53 
+    page</a> to get started. Be sure to enter a proper email address and a strong
54 
+    password. After you fill in the form and use the 'Register Account' button, you
55 
+    should see some text indicating that things worked out:
56 
+    </p>
57 
+    <pre>
58 
+    Account created. You will be emailed login details and an activation code.
59 
+    Please enter your activation code on the activation page.
60 
+    </pre>
61 
+
62 
+    <p>
63 
+    Shortly after you see this text an email will be sent to the email address you
64 
+    provided. The email should look something like the following:
65 
+    </p><pre>
66 
+    A Pootle account has been created for you using this email address.
67 
+    Your activation code is:
68 
+    36074ec543c1fa23ceeaf8e187dfa43e
69 
+    This message is sent to verify that the email address is in fact correct. If
70 
+    you did not want to register an account, you may simply ignore the message.
71 
+    Your user name is: example_user
72 
+    Your password is: example_user
73 
+    Your registered email address is: username@example.com
74 
+    </pre>
75 
+
76 
+    <p>
77 
+    Once you've received the email, you'll need to activate your account by
78 
+    visiting the <a
79 
+    href="https://translation.torproject.org/activate.html">activation page</a>.
80 
+    Enter your username and activation code into the form and then submit the form
81 
+    by pressing the "Activate Account" button.
82 
+
83 
+    You'll see a message that says:
84 
+    </p><pre>
85 
+    Redirecting to login Page...
86 
+    Your account has been activated! Redirecting to login...
87 
+    </pre>
88 
+
89 
+    <p>
90 
+    When you login to your new account, you'll be prompted to configure your basic
91 
+    language preferences on the <a
92 
+    href="https://translation.torproject.org/home/options.html">options page</a>. At
93 
+    the very least, you'll want to select the user interface language, select any
94 
+    of the projects you're interested in translating, and additionally the languages
95 
+    you wish to translate. Save your changes by clicking the "Save Changes" button
96 
+    when you're finished.
97 
+    </p>
98 
+
99 
+    <p>
100 
+    You're ready to translate!
101 
+    </p>
102 
+
103 
+    <p>
104 
+    At this point, you can select a project, such as <a
105 
+    href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>. You'll
106 
+    see a nice list of all of the currently supported languages along with the
107 
+    current translation progress. Select a language &mdash; in our example,
108 
+    you'll click
109 
+    <a href="https://translation.torproject.org/de/vidalia/">German</a>. The next
110 
+    page should show you a single row of data for the file "<a
111 
+    href='https://translation.torproject.org/de/vidalia/vidalia_de.po?translate=1&amp;view=1'>vidalia_de.po</a>".
112 
+    This is the file with all of the currently translated German strings for
113 
+    Vidalia. You should click on the "<a
114 
+    href='https://translation.torproject.org/de/vidalia/index.html?editing=1'>Show
115 
+    Editing Functions</a>" link above the 'vidalia_de.po' row. Next you should
116 
+    click the "<a
117 
+    href='https://translation.torproject.org/de/vidalia/translate.html?fuzzy=1&amp;editing=1&amp;blank=1'>Quick
118 
+    Translate</a>" link. This will take you to the first untranslated string in the
119 
+    language group for the current project.
120 
+    </p>
121 
+
122 
+    <p>
123 
+    If you're able, please translate the string you see and click the 'Submit'
124 
+    button. If you're unsure, click the 'Suggest' button. Feel free to leave
125 
+    comments for any of the translations if you feel it's important to clarify
126 
+    anything.
127 
+    </p>
128 
+
129 
+    <p>
130 
+    When you're finished, you need to commit your changes. Return to the
131 
+    page with the <a
132 
+    href="https://translation.torproject.org/de/vidalia/index.html?editing=1">Editing
133 
+    Functions</a>, and click on the "<a
134 
+    href='https://translation.torproject.org/de/vidalia/index.html?editing=1&amp;docommit=1&amp;commitfile=vidalia_de.po'>Commit</a>"
135 
+    link. This will commit your changes into the <a
136 
+    href="https://svn.torproject.org/svn/translation/trunk/projects/vidalia/de/">Translation
137 
+    subversion module</a> in the specific area as specified by your choices of
138 
+    language and project (Vidalia and German, for this example).
139 
+    </p>
140 
+
141 
+    <p>
142 
+    That's all there is to it! Be sure to go through the steps again and
143 
+    contribute to Torbutton and Torcheck too.
144 
+    </p>
145 
+
146 
+    <p>
147 
+    If your language isn't in the list of options yet, send mail to
148 
+    <tt>tor-translation AT torproject.org</tt> and we'll add it for you.
149 
+    </p>
150 
+
151 
+    <p>
152 
+    For more advanced users who like to translate without a web browser, you can
153 
+    also download the .po file directly. You'll find this option after clicking on
154 
+    the "<a
155 
+    href='https://translation.torproject.org/de/vidalia/index.html?editing=1'>Show
156 
+    Editing Functions</a>" link. You should see a link to download the "<a
157 
+    href="https://translation.torproject.org/de/vidalia/vidalia_de.po">PO file</a>".
158 
+    If this option fits your working habits, by all means, please use it!
159 
+    You may find a program called <a href="http://www.poedit.net/">Poedit</a>
160 
+    to make the job easier, especially for right-to-left languages that don't
161 
+    work as well in text editors. If you're using Poedit, you should disable
162 
+    compiling .mo files in Poedit's preferences (File -&gt; Preferences -&gt;
163 
+    Editor -&gt; Behavior, uncheck "Automatically compile .mo file on save").
164 
+    When you're finished translating the .po file, you can upload it by
165 
+    using the "upload file" form in the upper right hand corner: simply
166 
+    select the file and click the 'Upload file' button.
167 
+    </p>
168 
+  </div>
169 
+  <!-- END MAINCOL -->
170 
+  <div id = "sidecol">
171 
+#include "side.wmi"
172 
+#include "info.wmi"
173 
+  </div>
174 
+  <!-- END SIDECOL -->
175 
+</div>
176 
+<!-- END CONTENT -->
177 
+#include <foot.wmi>
getinvolved/en/translation-portal.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,7 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 15928 $
3 
+# Status: obsolete
4 
+
5 
+#include "head.wmi" TITLE="Redirecting" REDIRECT="translation-overview"
6 
+
7 
+#include <foot.wmi>
getinvolved/en/translation-status.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,239 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21313 $
3 
+
4 
+# Note to translators:
5 
+# translating this page is probably not a good idea, and it never was intended to be translated.
6 
+# it contains lots of programming logic, which you would have to duplicate, and it's probably
7 
+# useful only to other translators which most likely will know a bit of english.
8 
+#
9 
+# Thanks for your hard work, improve the other pages instead. :)   -- weasel
10 
+
11 
+#include "head.wmi" TITLE="Tor Projecdt: Translation status" CHARSET="UTF-8"
12 
+#use "functions.wmi"
13 
+
14 
+<div id="content" class="clearfix">
15 
+  <div id="breadcrumbs">
16 
+    <a href="<page home>">Home &raquo; </a>
17 
+    <a href="<page getinvolved/getinvolved>">Get Involved &raquo; </a>
18 
+    <a href="<page getinvolved/translation-status>">Translation Status</a>
19 
+  </div>
20 
+  <div id="maincol">
21 
+    <h1>Tor: Translation status</h1>
22 
+    <hr />
23 
+
24 
+    <:
25 
+    sub do_status(\%$$) {
26 
+    	my $dir = $_[1];
27 
+    	my $may_miss_dir = $_[2];
28 
+    	my %files;
29 
+
30 
+    	my @warnings;
31 
+    	for my $lang (@LANGUAGES) {
32 
+    		my $dir_opened = opendir(DIR, "$dir/$lang");
33 
+
34 
+    		if (! $dir_opened) {
35 
+    			$may_miss_dir or die ("Cannot opendir $dir/$lang: $!\n");
36 
+    			next;
37 
+    		}
38 
+
39 
+    		my @files = grep { $_ ne '.' && $_ ne '..' &&
40 
+    			$_ !~ /tor-manual/i && $_ !~ /translation-status/i && $_ =~ m/^[^.]/ && -f "$dir/$lang/$_"} readdir(DIR);
41 
+    		closedir DIR;
42 
+
43 
+    		for my $file (@files) {
44 
+    			$files{$lang}->{$file}->{'all'} = getMetadata("$dir/$lang/$file");
45 
+    			if ($lang eq 'en') {
46 
+    				$files{$lang}->{$file}->{'rev'} = translation_get_masterrevision_file($dir, $file);
47 
+    			} else {
48 
+    				$files{$lang}->{$file}->{'based'} = translation_get_basedonrevision_langfile($dir, $lang, $file);
49 
+    			};
50 
+    		};
51 
+    	};
52 
+    	my %priorities;
53 
+    	for my $file (keys %{$files{'en'}}) {
54 
+    		my $p = $files{'en'}->{$file}->{'all'}->{'Translation-Priority'};
55 
+    		if (defined $p) {
56 
+    			$priorities{$p} = 1;
57 
+    		};
58 
+    	};
59 
+    	my @priorities = sort {$a cmp $b} keys %priorities;
60 
+    	push @priorities, 'none';
61 
+
62 
+    	my $HTMLBASE = (defined $ENV{'HTMLBASE'} ? $ENV{'HTMLBASE'} : 'https://www.torproject.org/') . ($dir eq '.' ? '' : $dir.'/');
63 
+
64 
+    	for my $priority (@priorities) {
65 
+    		for my $file (sort {$a cmp $b} keys %{$files{'en'}}) {
66 
+    			my $file_priority = $files{'en'}->{$file}->{'all'}->{'Translation-Priority'};
67 
+    			next if (defined $file_priority && $priority ne $file_priority);
68 
+    			next if (!defined $file_priority && $priority ne 'none');
69 
+    			my $path = ($dir eq '.' ? '' : $dir.'/') . $file;
70 
+
71 
+    			my $obs = file_is_obsolete($dir, 'en', $file);
72 
+    			my $validatorlink = '';
73 
+    			my $htmlfile = $file;
74 
+    			if ($htmlfile =~ s/\.wml/.html/) {
75 
+    				$validatorlink = sprintf '<br><a href="http://validator.w3.org/check?uri=%s%s.en">validator</a>',
76 
+    					$HTMLBASE, $htmlfile;
77 
+    			};
78 
+
79 
+    			my $cell_path = sprintf '<th>%s</th>', $path;
80 
+    			my $cell_en = sprintf '<td%s>Revision %s%s<br>
81 
+    				<a href="https://svn.torproject.org/cgi-bin/viewvc.cgi/website/trunk/%sen/%s?root=Tor&amp;view=markup">HEAD</a>
82 
+    				%s',
83 
+    				($obs ? ' bgcolor="#D3D3D3"' : ''),
84 
+    				$files{'en'}->{$file}->{'rev'},
85 
+    				($obs ? ' (obsolete)' :''),
86 
+    				($dir eq '.' ? '' : $dir.'/'),
87 
+    				$file,
88 
+    				$validatorlink;
89 
+
90 
+    			${$_[0]}{$priority}->{$path}->{'data'} = $cell_path . $cell_en;
91 
+    			# Assign high urgency if it's *.wmi, else init to 0
92 
+    			if ($file =~ /.wmi$/) {
93 
+    			  ${$_[0]}{$priority}->{$path}->{'urgency'} = 1000;
94 
+    			} else {
95 
+    			  ${$_[0]}{$priority}->{$path}->{'urgency'} = 0;
96 
+    			}
97 
+
98 
+    			for my $lang (@LANGUAGES) {
99 
+    				next if $lang eq 'en';
100 
+    				my $color;
101 
+    				my $status;
102 
+    				#my $path = ($dir eq '.' ? '' : $dir.'/') . $file;
103 
+    				if ($validatorlink) {
104 
+    					$validatorlink = sprintf '<br><a href="http://validator.w3.org/check?uri=%s%s.%s">validator</a>',
105 
+    						$HTMLBASE, $htmlfile, $lang;
106 
+    				};
107 
+    				if (exists $files{$lang}->{$file}) {
108 
+    					my $all_info = '';
109 
+    					for my $key (sort {$a cmp $b} keys %{$files{$lang}->{$file}->{'all'}}) {
110 
+    						next if $key eq 'Translation-Priority';
111 
+    						$all_info .= sprintf "%s: %s<br>", $key, $files{$lang}->{$file}->{'all'}->{$key};
112 
+    					};
113 
+
114 
+    					my $difflink;
115 
+    					if ($files{$lang}->{$file}->{'based'}  eq  $files{'en'}->{$file}->{'rev'}) {
116 
+    						$color='#90EE90';
117 
+    						$status='current';
118 
+    						$difflink='';
119 
+    					} else {
120 
+    						$status='not current';
121 
+    						if ($files{$lang}->{$file}->{'based'} ne 'unknown') {
122 
+    							$difflink=sprintf '<br><a href="https://svn.torproject.org/cgi-bin/viewvc.cgi/website/trunk/%sen/%s?root=Tor&amp;r1=%s&amp;r2=%s">changes in original</a>',
123 
+    								($dir eq '.' ? '' : $dir.'/'), $file, $files{$lang}->{$file}->{'based'}, $files{'en'}->{$file}->{'rev'};
124 
+    							$color='yellow';
125 
+    						} else {
126 
+    							$difflink='';
127 
+    							$color='#FFA500';
128 
+    						};
129 
+
130 
+    						${$_[0]}{$priority}->{$path}->{'urgency'} += 1;
131 
+    					};
132 
+
133 
+    					${$_[0]}{$priority}->{$path}->{'data'} .= sprintf '<td bgcolor="%s">%s<br>
134 
+    						<a href="https://svn.torproject.org/cgi-bin/viewvc.cgi/website/trunk/%s%s/%s?root=Tor&amp;view=markup">HEAD</a><br>
135 
+    						%s
136 
+    						%s
137 
+    						%s</td>',
138 
+    						$color,
139 
+    						$status,
140 
+    						($dir eq '.' ? '' : $dir.'/'),
141 
+    						$lang, $file,
142 
+    						$all_info,
143 
+    						$difflink,
144 
+    						$validatorlink;
145 
+    				} else {
146 
+    					#my $path = ($dir eq '.' ? '' : $dir.'/') . $file;
147 
+    					$color=(($obs or $priority eq 'none') ?
148 
+    						'#90EE90' : 'red');
149 
+    					$status='missing';
150 
+
151 
+    					${$_[0]}{$priority}->{$path}->{'data'} .= sprintf '<td bgcolor="%s">%s</td>', $color, $status;
152 
+    					${$_[0]}{$priority}->{$path}->{'urgency'} += ($obs or $priority eq 'none') ? 0 : 2;
153 
+    				};
154 
+    				delete $files{$lang}->{$file};
155 
+    			};
156 
+
157 
+    			${$_[0]}{$priority}->{$path}->{'data'} .= $cell_en . $cell_path;
158 
+    		};
159 
+    	};
160 
+
161 
+    	for my $lang (@LANGUAGES) {
162 
+    		next if $lang eq 'en';
163 
+    		if (keys %{$files{$lang}} > 0) {
164 
+    #			print "<p>";
165 
+    			print "<br><br>";
166 
+    			printf "<h2>Additional files in %s (%s)</h2>\n", $lang, $LANGUAGES{$lang};
167 
+
168 
+    			print "<table border=1>\n";
169 
+    			print "<tr>\n";
170 
+    			print "<th>File</th>\n";
171 
+    			print "<th>Based on Revision</th>\n";
172 
+    			print "</tr>\n";
173 
+    			for my $file (sort {$a cmp $b} keys %{$files{$lang}}) {
174 
+    				print "<tr>";
175 
+    				printf "<th>%s</th><td>", $file;
176 
+    				for my $key (sort {$a cmp $b} keys %{$files{$lang}->{$file}->{'all'}}) {
177 
+    					printf "%s: %s<br>", $key, $files{$lang}->{$file}->{'all'}->{$key};
178 
+    				};
179 
+    				printf "</td>";
180 
+    				delete $files{$lang}->{$file};
181 
+    				print "</tr>\n";
182 
+    			};
183 
+    			print "</table>\n\n";
184 
+    		};
185 
+    	};
186 
+    };
187 
+
188 
+    sub sort_and_print(\%) {
189 
+    	my %rows = %{$_[0]};
190 
+
191 
+    	for my $priority (sort {$a cmp $b} keys %rows) {
192 
+    		print "<h2>Translation priority: $priority</h2>\n";
193 
+
194 
+    		print "<table border=1>\n";
195 
+    		print "<tr>\n";
196 
+    		print "<th>File</th>\n";
197 
+    		printf("<th>%s (%s)</th>\n", $_, $LANGUAGES{$_}) for ('en', grep({ $_ ne 'en' } @LANGUAGES), 'en');
198 
+    		print "<th>File</th>\n";
199 
+    		print "</tr>\n";
200 
+
201 
+    		for my $row (sort {$rows{$priority}->{$b}->{'urgency'} <=> $rows{$priority}->{$a}->{'urgency'}} keys %{$rows{$priority}}) {
202 
+    			print "<tr>";
203 
+    			print $rows{$priority}->{$row}->{'data'};
204 
+    			delete ${$_[0]}{$priority}->{$row};
205 
+    			print "</tr>\n\n";
206 
+    		};
207 
+
208 
+    		print "</table><br>\n\n\n";
209 
+    	};
210 
+    };
211 
+
212 
+    # accumulate the table rows, then sort and print them
213 
+    my %table_rows;
214 
+    do_status(%table_rows, '.', 0);
215 
+    do_status(%table_rows, 'docs', 1);
216 
+    do_status(%table_rows, 'torbrowser', 1);
217 
+    do_status(%table_rows, 'torbutton', 1);
218 
+    do_status(%table_rows, 'tordnsel', 1);
219 
+    do_status(%table_rows, 'projects', 1);
220 
+    do_status(%table_rows, 'torvm', 1);
221 
+    do_status(%table_rows, 'press', 1);
222 
+    #do_status(%table_rows, 'gettor', 1);
223 
+    do_status(%table_rows, 'vidalia', 1);
224 
+    #do_status(%table_data, 'eff', 1);
225 
+    #do_status(%table_data, 'gui', 1);
226 
+    sort_and_print(%table_rows);
227 
+
228 
+
229 
+    :>
230 
+  </div>
231 
+  <!-- END MAINCOL -->
232 
+  <div id = "sidecol">
233 
+#include "side.wmi"
234 
+#include "info.wmi"
235 
+  </div>
236 
+  <!-- END SIDECOL -->
237 
+</div>
238 
+<!-- END CONTENT -->
239 
+#include <foot.wmi>
getinvolved/en/translation.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,68 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Website Translation Guidelines" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved &raquo; </a>
10 
+    <a href="<page getinvolved/translation>">Translation Guidelines</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor Website Translation Guidelines</h1>
14 
+    <hr />
15 
+
16 
+    <p>
17 
+    If you want to help translate the Tor website and documentation into
18 
+    other languages, here are some guidelines to help you do this as
19 
+    efficiently as possible.
20 
+    </p>
21 
+
22 
+    <p>
23 
+    If you would like to help translate other Tor project related information,
24 
+    please visit our <a href="<page getinvolved/translation-overview>">Translation Overview</a>
25 
+    for a clear overview of what needs translation help. If you're stuck, please
26 
+    contact us via email: <tt>tor-translation AT torproject.org</tt>.
27 
+    </p>
28 
+
29 
+    <p>
30 
+    To get an idea how
31 
+    current our translations are, we have created a page with the current
32 
+    <a href="<page getinvolved/translation-status>">translation status</a>.</p>
33 
+
34 
+    <p>
35 
+    Note that even if you can't translate many pages for your language,
36 
+    a few pages will still be helpful.
37 
+    Also, rather than just translating each page word
38 
+    by word, please try to translate the ideas so they make the most sense
39 
+    in your language.</p>
40 
+
41 
+    <ol>
42 
+    <li>We would also like some translations for the diagrams on
43 
+    <a href="<page about/overview>">the overview page</a>. You can just send us
44 
+    the text that should go in the diagrams, and we'll take care of making
45 
+    new versions of the pictures.</li>
46 
+
47 
+    <li>When you have some pages ready, send them to the
48 
+    <tt>tor-translation</tt> alias on the <a href="<page about/contact>">contact
49 
+    page</a>.  (If you have changes to existing pages, please use the diff
50 
+    tool to generate patch files, if possible.)  If you plan to stick
51 
+    around and keep maintaining them, let us know and we'll
52 
+    be happy to give you an SVN account to manage them directly.</li>
53 
+    </ol>
54 
+
55 
+    <p>Other projects related to Tor also need translators. Please see
56 
+    our translation portal for <a href="<page getinvolved/translation-overview>">translating
57 
+    other useful and related software</a>.
58 
+    </p>
59 
+  </div>
60 
+  <!-- END MAINCOL -->
61 
+  <div id = "sidecol">
62 
+#include "side.wmi"
63 
+#include "info.wmi"
64 
+  </div>
65 
+  <!-- END SIDECOL -->
66 
+</div>
67 
+<!-- END CONTENT -->
68 
+#include <foot.wmi>
getinvolved/en/tshirt.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,62 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22359 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: T-shirt" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved &raquo; </a>
10 
+    <a href="<page getinvolved/tshirt>">Tshirt</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <h1>Tor: T-shirt for Contributing</h1>
14 
+    <hr />
15 
+
16 
+    <p>You can get one of these fine Tor T-shirts for contributing to the
17 
+    Tor project. There are three primary ways of contributing:</p>
18 
+
19 
+    <ol>
20 
+    <li>A large enough ($65+) <a href="<page donate/donate>">donation</a> to the Tor
21 
+    Project.</li>
22 
+    <li>Operate a fast <a href="<page docs/tor-doc-relay>">Tor relay</a>
23 
+    that's been running for the past two months: you are eligible if you
24 
+    allow exits to port 80 and you average 100 KB/s traffic, or if you're
25 
+    not an exit but you average 500 KB/s traffic.</li>
26 
+    <li>Help out in <a href="<page getinvolved/volunteer>">other ways</a>. <a href="<page
27 
+    getinvolved/translation>">Maintain a translation for the website</a>. Write a good <a
28 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">support
29 
+    program and get a lot of people to use it</a>. Do research on Tor
30 
+    and anonymity, solve some of <a href="https://bugs.torproject.org/">our
31 
+    bugs</a>, or establish yourself as a Tor advocate.
32 
+    </li>
33 
+    </ol>
34 
+
35 
+    <p>
36 
+    If you qualify, send mail to donations at torproject dot org with
37 
+    a brief explanation. Be sure to specify a color preference, a size
38 
+    (S/M/L/XL/XXL), a backup size if your first choice isn't available,
39 
+    and a shipping address.
40 
+    </p>
41 
+
42 
+    <p>
43 
+    You can choose between the traditional black and our conversation-starting
44 
+    bright green. You can also see the shirts
45 
+    <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorShirt">in
46 
+    action</a> &mdash; add your own photos there too.
47 
+    </p>
48 
+
49 
+    <div style="text-align: center">
50 
+    <a href="tshirt/black-tor-tshirt.png"><img src="tshirt/black-tor-tshirt.png" /></a>
51 
+    <a href="tshirt/green-tor-tshirt.png"><img src="tshirt/green-tor-tshirt.png" /></a>
52 
+    </div>
53 
+  </div>
54 
+  <!-- END MAINCOL -->
55 
+  <div id = "sidecol">
56 
+#include "side.wmi"
57 
+#include "info.wmi"
58 
+  </div>
59 
+  <!-- END SIDECOL -->
60 
+</div>
61 
+<!-- END CONTENT -->
62 
+#include <foot.wmi>
getinvolved/en/volunteer.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,1070 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22432 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor: Volunteer" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page getinvolved/getinvolved>">Get Involved</a>
10 
+    <a href="<page getinvolved/volunteer>">Volunteer</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+    <h1>A few things everyone can do now:</h1>
15 
+    <ol>
16 
+    <li>Please consider <a href="<page docs/tor-doc-relay>">running
17 
+    a relay</a> to help the Tor network grow.</li>
18 
+    <li>Tell your friends! Get them to run relays. Get them to run hidden
19 
+    services. Get them to tell their friends.</li>
20 
+    <li>If you like Tor's goals, please <a href="<page donate/donate>">take a moment
21 
+    to donate to support further Tor development</a>. We're also looking
22 
+    for more sponsors &mdash; if you know any companies, NGOs, agencies,
23 
+    or other organizations that want anonymity / privacy / communications
24 
+    security, let them know about us.</li>
25 
+    <li>We're looking for more <a href="<page about/torusers>">good examples of Tor
26 
+    users and Tor use cases</a>. If you use Tor for a scenario or purpose not
27 
+    yet described on that page, and you're comfortable sharing it with us,
28 
+    we'd love to hear from you.</li>
29 
+    </ol>
30 
+
31 
+    <p>Tor has <a href="<page getinvolved/open-positions>">two open positions</a>.
32 
+    Please <a href="<page about/contact>">contact us</a> if you are qualified!</p>
33 
+
34 
+    <a id="Documentation"></a>
35 
+    <h2><a class="anchor" href="#Documentation">Documentation</a></h2>
36 
+    <ol>
37 
+    <li>Help translate the web page and documentation into other
38 
+    languages. See the <a href="<page getinvolved/translation>">translation
39 
+    guidelines</a> if you want to help out. We especially need Arabic or
40 
+    Farsi translations, for the many Tor users in censored areas.</li>
41 
+    <li>Evaluate and document
42 
+    <a href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">our
43 
+    list of programs</a> that can be configured to use Tor.</li>
44 
+    <li>We have a huge list of <a
45 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">potentially useful
46 
+    programs that interface to Tor</a>. Which ones are useful in which
47 
+    situations? Please help us test them out and document your results.</li>
48 
+    </ol>
49 
+
50 
+    <a id="Advocacy"></a>
51 
+    <h2><a class="anchor" href="#Advocacy">Advocacy</a></h2>
52 
+    <ol>
53 
+    <li>Create a <a href="https://trac.torproject.org/projects/tor/wiki/CommunityLogos">community logo</a> under a Creative Commons license that all can use and modify</li>
54 
+    <li>Create a presentation that can be used for various user group meetings around the world</li>
55 
+    <li>Create a video about the positive uses of Tor, what Tor is, or how
56 
+    to use it.  Some have already
57 
+    started on <a href="http://media.torproject.org/video/">Tor's Media
58 
+    server</a>, <a
59 
+    href="http://www.howcast.com/videos/90601-How-To-Circumvent-an-Internet-Proxy">Howcast</a>,
60 
+    and <a href="http://www.youtube.com/thetorproject">Youtube</a>.</li>
61 
+    <li>Create a poster, or a set of posters, around a theme,
62 
+    such as "Tor for Freedom!"</li>
63 
+    </ol>
64 
+
65 
+    <a id="Coding"></a>
66 
+    <a id="Summer"></a>
67 
+    <a id="Projects"></a>
68 
+    <h2><a class="anchor" href="#Projects">Good Coding Projects</a></h2>
69 
+
70 
+    <p>
71 
+    You may find some of these projects to be good <a href="<page
72 
+    about/gsoc>">Google Summer of Code 2010</a> ideas. We have labelled each idea
73 
+    with how useful it would be to the overall Tor project (priority), how
74 
+    much work we expect it would be (effort level), how much clue you should
75 
+    start with (skill level), and which of our <a href="<page
76 
+    about/people>#Core">core developers</a> would be good mentors.
77 
+    If one or more of these ideas looks promising to you, please <a
78 
+    href="<page about/contact>">contact us</a> to discuss your plans rather than
79 
+    sending blind applications. You may also want to propose your own project
80 
+    idea &mdash; which often results in the best applications.
81 
+    </p>
82 
+
83 
+    <ol>
84 
+
85 
+    <li>
86 
+    <b>Tor Browser Bundle for Mac OS X</b>
87 
+    <br />
88 
+    Priority: <i>High</i>
89 
+    <br />
90 
+    Effort Level: <i>High</i>
91 
+    <br />
92 
+    Skill Level: <i>Medium</i>
93 
+    <br />
94 
+    Likely Mentors: <i>Steven, Erinn, Jacob, Andrew</i>
95 
+    <br />
96 
+    The Tor Browser Bundle incorporates Tor, Firefox, Polipo, and the Vidalia
97 
+    user interface (and optionally the <a href="http://pidgin.im/">Pidgin</a>
98 
+    Instant Messaging client). Components are pre-configured to operate in a
99 
+    secure way, and it has very few dependencies on the installed operating
100 
+    system. It has therefore become one of the most easy to use, and popular,
101 
+    ways to use Tor on Windows.
102 
+    <br />
103 
+    However, there is currently no released package for Mac OS X, so this project
104 
+    would be to implement Tor Browser Bundle for OS X. This will involve
105 
+    modifications to Vidalia (C++), possibly Firefox (C) then creating and testing
106 
+    the launcher on a range of operating system versions and configurations to
107 
+    verify portability.  Some work on this was completed as part of the Google
108 
+    Summer of Code 2009. Another part of this project is to identify all of the
109 
+    traces left behind by using a Tor Browser Bundle on Mac OS X or Linux.
110 
+    Developing ways to stop, counter, or remove these traces is a final step.
111 
+    <br />
112 
+    Students should be familiar with application development on one or
113 
+    preferably both of Linux and Mac OS X, and be comfortable with C/C++
114 
+    and shell scripting.
115 
+    <br />
116 
+    Part of this project could be usability testing of Tor Browser Bundle,
117 
+    ideally amongst our target demographic.  That would help a lot in knowing
118 
+    what needs to be done in terms of bug fixes or new features. We get this
119 
+    informally at the moment, but a more structured process would be better.
120 
+    <br />
121 
+    A beta version of the Tor Browser Bundle has been released for GNU/Linux, but
122 
+    work is still required for the Tor IM Browser bundle. Work is currently being
123 
+    done on the Mac OS X version as well. If you would like to help extend or do
124 
+    security auditing for either (or both) of these, please contact Erinn.
125 
+    </li>
126 
+
127 
+    <li>
128 
+    <b>Help track the overall Tor Network status</b>
129 
+    <br />
130 
+    Priority: <i>Medium to High</i>
131 
+    <br />
132 
+    Effort Level: <i>Medium</i>
133 
+    <br />
134 
+    Skill Level: <i>Medium</i>
135 
+    <br />
136 
+    Likely Mentors: <i>Karsten, Roger</i>
137 
+    <br />
138 
+    It would be great to set up an automated system for tracking network
139 
+    health over time, graphing it, etc. Part of this project would involve
140 
+    inventing better metrics for assessing network health and growth. Is the
141 
+    average uptime of the network increasing? How many relays are qualifying
142 
+    for Guard status this month compared to last month? What's the turnover
143 
+    in terms of new relays showing up and relays shutting off? Periodically
144 
+    people collect brief snapshots, but where it gets really interesting is
145 
+    when we start tracking data points over time.
146 
+    <br />
147 
+    Data could be collected from the Tor Network Scanners in <a
148 
+    href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>, from
149 
+    the server descriptors that each relay publishes, and from other
150 
+    sources. Results over time could be integrated into one of the <a
151 
+    href="https://torstatus.blutmagie.de/">Tor Status</a> web pages, or be
152 
+    kept separate. Speaking of the Tor Status pages, take a look at Roger's
153 
+    <a href="http://archives.seul.org/or/talk/Jan-2008/msg00300.html">Tor
154 
+    Status wish list</a>.
155 
+    </li>
156 
+
157 
+    <li>
158 
+    <b>Rewrite TorDNSEL, this time with a spec!</b>
159 
+    <br />
160 
+    Priority: <i>High</i>
161 
+    <br />
162 
+    Effort Level: <i>Medium</i>
163 
+    <br />
164 
+    Skill Level: <i>Medium</i>
165 
+    <br />
166 
+    Likely Mentors: <i>Mike, Roger, Sebastian, Damian</i>
167 
+    <br />
168 
+    The <a href="<page projects/tordnsel>">Tor DNS Exit List</a> is an
169 
+    unmaintained Haskell
170 
+    program that serves three purposes. First, it provides an rbl-style DNS
171 
+    interface for people to look up whether a given IP address is (or has
172 
+    recently been) a Tor exit relay. Second, it actively builds circuits over
173 
+    the Tor network and connects back to itself, to learn the actual exit
174 
+    IP address of each relay &mdash; some Tor relays exit from a different
175 
+    address than they advertise in their descriptor. Third, it exports a <a
176 
+    href="http://exitlist.torproject.org/exitAddresses">set of conclusions</a>
177 
+    so that <a href="https://check.torproject.org/">check.torproject.org</a>
178 
+    can guess for you whether your browser is configured to point to Tor.
179 
+    <br />
180 
+    This project would make use of <a
181 
+    href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>,
182 
+    a set of Python scripts to interact with Tor,
183 
+    to figure out how our Tor Exit Checker should actually work, and then
184 
+    build it &mdash; probably in Python since Torflow is in Python. The main
185 
+    goal is to reduce false positives as much as possible, by making sure
186 
+    that it learns about new relays as soon as possible, making sure that
187 
+    the testing phase concludes quickly, and making sure the answers get
188 
+    passed to the Check script quickly. As a bonus, we should standardize
189 
+    (specify) the format of the exitAddresses file, and rewrite the <a
190 
+    href="https://svn.torproject.org/svn/check/trunk/cgi-bin/TorBulkExitList.py">Tor
191 
+    Bulk Exit List</a> script to use that file rather than its current <a
192 
+    href="https://bugs.torproject.org/flyspray/index.php?do=details&id=1019">horrible
193 
+    DNS hacks</a>. As an extra bonus, we should work with Freenode, OFTC,
194 
+    and/or other IRC networks to make sure that the scripts we offer are
195 
+    actually the scripts they want, in terms of accurately identifying which
196 
+    of their users are coming from the Tor network.
197 
+    <br />
198 
+    You can fetch the <a href="git://git.torproject.org/git/tordnsel">latest
199 
+    tordnsel</a> via git.
200 
+    </li>
201 
+
202 
+    <li>
203 
+    <b>Improving Tor's ability to resist censorship</b>
204 
+    <br />
205 
+    Priority: <i>Medium to High</i>
206 
+    <br />
207 
+    Effort Level: <i>Medium to High</i>
208 
+    <br />
209 
+    Skill Level: <i>High</i>
210 
+    <br />
211 
+    Likely Mentors: <i>Roger, Nick, Steven</i>
212 
+    <br />
213 
+    The Tor 0.2.1.x series makes <a
214 
+    href="<svnprojects>design-paper/blocking.html">significant
215 
+    improvements</a> in resisting national and organizational censorship.
216 
+    But Tor still needs better mechanisms for some parts of its
217 
+    anti-censorship design.
218 
+    <br />
219 
+    One huge category of work is adding features to our <a
220 
+    href="http://gitweb.torproject.org//bridgedb.git?a=tree">bridgedb</a>
221 
+    service (Python). Tor aims to give out <a href="<page docs/bridges>">bridge
222 
+    relay addresses</a> to users that can't reach the Tor network
223 
+    directly, but there's an arms race between algorithms for distributing
224 
+    addresses and algorithms for gathering and blocking them. See <a
225 
+    href="https://blog.torproject.org/blog/bridge-distribution-strategies">our
226 
+    blog post on the topic</a> as an overview, and then look at <a
227 
+    href="http://archives.seul.org/or/dev/Dec-2009/msg00000.html">Roger's
228 
+    or-dev post</a> from December for more recent thoughts &mdash; lots of
229 
+    design work remains.
230 
+    <br />
231 
+    If you want to get more into the guts of Tor itself (C), a more minor problem
232 
+    we should address is that current Tors can only listen on a single
233 
+    address/port combination at a time. There's
234 
+    <a href="<gitblob>doc/spec/proposals/118-multiple-orports.txt">a
235 
+    proposal to address this limitation</a> and allow clients to connect
236 
+    to any given Tor on multiple addresses and ports, but it needs more
237 
+    work.
238 
+    <br />
239 
+    This project could involve a lot of research and design. One of the big
240 
+    challenges will be identifying and crafting approaches that can still
241 
+    resist an adversary even after the adversary knows the design, and
242 
+    then trading off censorship resistance with usability and robustness.
243 
+    </li>
244 
+
245 
+    <!--<li>
246 
+    <b>Tuneup Tor!</b>
247 
+    <br />
248 
+    Priority: <i>Medium to High</i>
249 
+    <br />
250 
+    Effort Level: <i>Medium to High</i>
251 
+    <br />
252 
+    Skill Level: <i>High</i>
253 
+    <br />
254 
+    Likely Mentors: <i>Nick, Roger, Mike, Karsten</i>
255 
+    <br />
256 
+    Right now, Tor relays measure and report their own bandwidth, and Tor
257 
+    clients choose which relays to use in part based on that bandwidth.
258 
+    This approach is vulnerable to
259 
+    <a href="http://freehaven.net/anonbib/#bauer:wpes2007">attacks where
260 
+    relays lie about their bandwidth</a>;
261 
+    to address this, Tor currently caps the maximum bandwidth
262 
+    it's willing to believe any relay provides.  This is a limited fix, and
263 
+    a waste of bandwidth capacity to boot.  Instead,
264 
+    Tor should possibly measure bandwidth in a more distributed way, perhaps
265 
+    as described in the
266 
+    <a href="http://freehaven.net/anonbib/author.html#snader08">"A Tune-up for
267 
+    Tor"</a> paper
268 
+    by Snader and Borisov. One could use current testing code to
269 
+    double-check this paper's findings and verify the extent to which they
270 
+    dovetail with Tor as deployed in the wild, and determine good ways to
271 
+    incorporate them into their suggestions Tor network without adding too
272 
+    much communications overhead between relays and directory
273 
+    authorities.
274 
+    </li>-->
275 
+
276 
+    <li>
277 
+    <b>Improving Polipo on Windows</b>
278 
+    <br />
279 
+    Priority: <i>Medium to High</i>
280 
+    <br />
281 
+    Effort Level: <i>Medium</i>
282 
+    <br />
283 
+    Skill Level: <i>Medium</i>
284 
+    <br />
285 
+    Likely Mentors: <i>Chris</i>
286 
+    <br />
287 
+    Help port <a
288 
+    href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> to
289 
+    Windows. Example topics to tackle include:
290 
+    <ol><li> the ability to asynchronously query name servers, find the
291 
+    system nameservers, and manage netbios and dns queries.</li>
292 
+    <li> manage events and buffers natively (i.e. in Unix-like OSes,
293 
+    Polipo defaults to 25% of ram, in Windows it's whatever the config
294 
+    specifies).</li>
295 
+    <li> some sort of GUI config and reporting tool, bonus if it has a
296 
+    systray icon with right clickable menu options. Double bonus if it's
297 
+    cross-platform compatible.</li>
298 
+    <li> allow the software to use the Windows Registry and handle proper
299 
+    Windows directory locations, such as "C:\Program Files\Polipo"</li>
300 
+    </ol>
301 
+    </li>
302 
+
303 
+    <li>
304 
+    <b>Tor Controller Status Event Interface for Vidalia</b>
305 
+    <br />
306 
+    Priority: <i>Medium</i>
307 
+    <br />
308 
+    Effort Level: <i>Medium</i>
309 
+    <br />
310 
+    Skill Level: <i>Low to Medium</i>
311 
+    <br />
312 
+    Likely Mentors: <i>Matt</i>
313 
+    <br />
314 
+    There are a number of status changes inside Tor of which the user may need
315 
+    to be informed. For example, if the user is trying to set up his Tor as a
316 
+    relay and Tor decides that its ports are not reachable from outside
317 
+    the user's network, we should alert the user. Currently, all the user
318 
+    gets is a couple log messages in Vidalia's 'message log' window, which they
319 
+    likely never see since they don't receive a notification that something
320 
+    has gone wrong. Even if the user does actually look at the message log,
321 
+    most of the messages make little sense to the novice user.
322 
+    <br />
323 
+    Tor has the ability to inform Vidalia of many such status changes, and
324 
+    we recently implemented support for a couple of these events. Still,
325 
+    there are many more status events the user should be informed of and we
326 
+    need a better UI for actually displaying them to the user.
327 
+    <br />
328 
+    The goal of this project then is to design and implement a UI for
329 
+    displaying Tor status events to the user. For example, we might put a
330 
+    little badge on Vidalia's tray icon that alerts the user to new status
331 
+    events they should look at. Double-clicking the icon could bring up a
332 
+    dialog that summarizes recent status events in simple terms and maybe
333 
+    suggests a remedy for any negative events if they can be corrected by
334 
+    the user. Of course, this is just an example and one is free to
335 
+    suggest another approach.
336 
+    <br />
337 
+    A person undertaking this project should have good UI design and layout
338 
+    and some C++ development experience. Previous experience with Qt and
339 
+    Qt's Designer will be very helpful, but are not required. Some
340 
+    English writing ability will also be useful, since this project will
341 
+    likely involve writing small amounts of help documentation that should
342 
+    be understandable by non-technical users. Bonus points for some graphic
343 
+    design/Photoshop fu, since we might want/need some shiny new icons too.
344 
+    </li>
345 
+
346 
+    <li>
347 
+    <b>Improve our unit testing process</b>
348 
+    <br />
349 
+    Priority: <i>Medium</i>
350 
+    <br />
351 
+    Effort Level: <i>Medium</i>
352 
+    <br />
353 
+    Skill Level: <i>Medium</i>
354 
+    <br />
355 
+    Likely Mentors: <i>Nick, Erinn</i>
356 
+    <br />
357 
+    Tor needs to be far more tested. This is a multi-part effort. To start
358 
+    with, our unit test coverage should rise substantially, especially in
359 
+    the areas outside the utility functions. This will require significant
360 
+    refactoring of some parts of Tor, in order to dissociate as much logic
361 
+    as possible from globals.
362 
+    <br />
363 
+    Additionally, we need to automate our performance testing. We've got
364 
+    buildbot to automate our regular integration and compile testing already
365 
+    (though we need somebody to set it up on Windows),
366 
+    but we need to get our network simulation tests (as built in <a
367 
+    href="https://svn.torproject.org/svn/torflow/trunk/README">TorFlow</a>)
368 
+    updated for more recent versions of Tor, and designed to launch a test
369 
+    network either on a single machine, or across several, so we can test
370 
+    changes in performance on machines in different roles automatically.
371 
+    </li>
372 
+
373 
+    <li>
374 
+    <b>Help with independent Tor client implementations</b>
375 
+    <br />
376 
+    Priority: <i>Medium</i>
377 
+    <br />
378 
+    Effort Level: <i>High</i>
379 
+    <br />
380 
+    Skill Level: <i>Medium to High</i>
381 
+    <br />
382 
+    Likely Mentors: <i>Bruce, Nathan</i>
383 
+    <br />
384 
+    Others are currently working on Tor clients for Java, Android, and Maemo
385 
+    environments.  The first step is to get a handle on the current state of
386 
+    the project in which you are interested in helping; <a
387 
+    href="http://github.com/brl/JTor">Tor for Java</a>,
388 
+    <a href="https://svn.torproject.org/svn/projects/android/trunk/">Android/Orbot</a>
389 
+    , or <a href="<page docs/N900>">Tor for Maemo</a>. Check out the
390 
+    repository and familiarize yourself
391 
+    with the source code.  Further, support for requesting or even providing
392 
+    Tor hidden services would be neat, but not required.
393 
+    <br />
394 
+    A prospective developer should be able to understand and write new Java
395 
+    code, including a Java cryptography API. Being able to read C code would be helpful,
396 
+    too. One should be willing to read the existing documentation,
397 
+    implement code based on it, and refine the documentation
398 
+    when things are underdocumented. This project is mostly about coding and
399 
+    to a small degree about design.
400 
+    </li>
401 
+    <li>
402 
+    <b>More on Orbot &amp; Android OS-specific development</b>
403 
+    <br/>
404 
+    <br />
405 
+    Priority: <i>Medium</i>
406 
+    <br />
407 
+    Effort Level: <i>High</i>
408 
+    <br />
409 
+    Skill Level: <i>Medium to High</i>
410 
+    <br />
411 
+    Likely Mentors: <i>Nathan</i>
412 
+    <br />
413 
+
414 
+    <b>Android Java UI work:</b> Improved home screen to show better statistics about data transferred (up/down), number of circuits connected, quality of connection and so on. The "Tether Wifi" Android application is a good model to follow in how it shows a realtime count of bytes transferred as well as notifications when wifi client connect. In addition, better display/handling of Tor system/error messages would also be very helpful. Finally, the addition of a wizard or tutorial walkthrough for novice users to explain to them exactly what or what is not anonymized or protected would greatly improve the likelihood they will use Orbot correctly.
415 
+    <br/><br/>
416 
+
417 
+    <b>Android Java OS/Core app work:</b> Better system-wide indicator either via the notification bar, "Toast" pop-up dialogs or some other indicator that an application's traffic is indeed moving through Orbot/Tor. For instance, right now you need to first go to a torcheck web service to ensure your browser is routing via Tor. Orbot should be able to notify you that circuits are being opened, used, etc. The aforementioned data transfer tracker might provide this type of awareness as well.
418 
+
419 
+    <br/><br/>
420 
+    <b>Android Java Library/Community Outreach work:</b> We need to package a simple library for use with third-party application to easily enable them to support "Torification" on non-root devices (aka w/o transparent proxying). This library should include a wrapper for the Apache HTTPClient library, a utility class for detecting the state of Orbot connectivity, and other relevant/useful things an Android app might need to anonymize itself. This work would include the creation of the library, documentation, and sample code. Outreach or effort to implement the library within other open-source apps would follow.
421 
+
422 
+    <br/><br/>
423 
+    <b>Android OS/C/Linux work:</b> The port of Tor to Android is basically a straight cross-compile to Linux ARM. There has been no work done in looking the optimization of Tor within a mobile hardware environment, on the ARM processor or other Android hardware, or on mobile networks. It should be noted, that even without optimization, Tor is handling the mobile network environment very well, automatically detecting change in IP addresses, reconnecting circuits, etc across switching from 2G to 3G to Wifi, and so forth.
424 
+    </li>
425 
+
426 
+    <!--<li>
427 
+    <b>New Torbutton Features</b>
428 
+    <br />
429 
+    Priority: <i>Medium</i>
430 
+    <br />
431 
+    Effort Level: <i>High</i>
432 
+    <br />
433 
+    Skill Level: <i>High</i>
434 
+    <br />
435 
+    Likely Mentors: <i>Mike</i>
436 
+    <br/>
437 
+    There are several <a
438 
+    href="https://bugs.torproject.org/flyspray/index.php?tasks=all&amp;project=5&amp;type=2">good
439 
+    feature requests</a> on the Torbutton Flyspray section. In particular, <a
440 
+    href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=523">Integrating
441 
+    'New Identity' with Vidalia</a>,
442 
+    <a href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=940">ways of
443 
+    managing multiple cookie jars/identities</a>, <a
444 
+    href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=637">preserving
445 
+    specific cookies</a> when cookies are cleared,
446 
+    <a
447 
+    href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=524">better
448 
+    referrer spoofing</a>, <a
449 
+    href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=564">correct
450 
+    Tor status reporting</a>, and <a
451 
+    href="https://bugs.torproject.org/flyspray/index.php?do=details&amp;id=462">"tor://"
452 
+    and "tors://" urls</a> are all interesting
453 
+    features that could be added.
454 
+    <br />
455 
+    This work would be independent coding in Javascript and the fun world of <a
456 
+    href="http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul">XUL</a>,
457 
+    with not too much involvement in the Tor internals.
458 
+    </li>-->
459 
+
460 
+    <!-- <li>
461 
+    <b>New Thandy Features</b>
462 
+    <br />
463 
+    Priority: <i>Medium</i>
464 
+    <br />
465 
+    Effort Level: <i>Medium</i>
466 
+    <br />
467 
+    Skill Level: <i>Medium to High</i>
468 
+    <br />
469 
+    Likely Mentors: <i>Martin</i>
470 
+    <br />
471 
+    Additional capabilities are needed for assisted updates of all the Tor
472 
+    related software for Windows and other operating systems. Some of the
473 
+    features to consider include:
474 
+    <ol>
475 
+    <li> Integration of the <a
476 
+    href="http://chandlerproject.org/Projects/MeTooCrypto">MeTooCrypto
477 
+    Python library</a>
478 
+    for authenticated HTTPS downloads.</li>
479 
+    <li> Adding a level of indirection
480 
+    between the timestamp signatures and the package files included in an
481 
+    update. See the "Thandy attacks / suggestions" thread on or-dev.</li>
482 
+    <li> Support locale specific installation and configuration of assisted
483 
+    updates based on preference, host, or user account language settings.
484 
+    Familiarity with Windows codepages, unicode, and other character sets
485 
+    is helpful in addition to general win32 and posix API experience and
486 
+    Python proficiency.</li>
487 
+    </ol>
488 
+    </li> -->
489 
+
490 
+    <li>
491 
+    <b>Simulator for slow Internet connections</b>
492 
+    <br />
493 
+    Priority: <i>Medium</i>
494 
+    <br />
495 
+    Effort Level: <i>Medium</i>
496 
+    <br />
497 
+    Skill Level: <i>Medium</i>
498 
+    <br />
499 
+    Likely Mentors: <i>Steven</i>
500 
+    <br />
501 
+    Many users of Tor have poor-quality Internet connections, giving low
502 
+    bandwidth, high latency, and high packet loss/re-ordering. User
503 
+    experience is that Tor reacts badly to these conditions, but it is
504 
+    difficult to improve the situation without being able to repeat the
505 
+    problems in the lab.
506 
+    <br />
507 
+    This project would be to build a simulation environment which
508 
+    replicates the poor connectivity so that the effect on Tor performance
509 
+    can be measured. Other components would be a testing utility to
510 
+    establish what are the properties of connections available, and to
511 
+    measure the effect of performance-improving modifications to Tor.
512 
+    <br />
513 
+    The tools used would be up to the student, but dummynet (for FreeBSD)
514 
+    and nistnet (for Linux) are two potential components on which this
515 
+    project could be built. Students should be experienced with network
516 
+    programming/debugging and TCP/IP, and preferably familiar with C and a
517 
+    scripting language.
518 
+    </li>
519 
+
520 
+    <li>
521 
+    <b>An Improved and More Usable Network Map in Vidalia</b>
522 
+    <br />
523 
+    Priority: <i>Low to Medium</i>
524 
+    <br />
525 
+    Effort Level: <i>Medium</i>
526 
+    <br />
527 
+    Skill Level: <i>Medium</i>
528 
+    <br />
529 
+    Likely Mentors: <i>Matt</i>
530 
+    <br />
531 
+    One of Vidalia's existing features is a network map that shows the user
532 
+    the approximate geographic location of relays in the Tor network and
533 
+    plots the paths the user's traffic takes as it is tunneled through the
534 
+    Tor network. The map is currently not very interactive and has rather
535 
+    poor graphics. Instead, we implemented KDE's Marble widget such
536 
+    that it gives us a better quality map and enables improved interactivity,
537 
+    such as allowing the user to click on individual relays or circuits to
538 
+    display additional information. We want to add the ability
539 
+    for users to click on a particular relay or a country containing one or
540 
+    more Tor exit relays and say, "I want my connections to exit
541 
+    from here."
542 
+    <br />
543 
+    This project will first involve getting familiar with Vidalia
544 
+    and the Marble widget's API. One will then integrate the widget
545 
+    into Vidalia and customize Marble to be better suited for our application,
546 
+    such as making circuits clickable, storing cached map data in Vidalia's
547 
+    own data directory, and customizing some of the widget's dialogs.
548 
+    <br />
549 
+    A person undertaking this project should have good C++ development
550 
+    experience. Previous experience with Qt and CMake is helpful, but not
551 
+    required.
552 
+    </li>
553 
+
554 
+    <li>
555 
+    <b>Torbutton equivalent for Thunderbird</b>
556 
+    <br />
557 
+    Priority: <i>Medium</i>
558 
+    <br />
559 
+    Effort Level: <i>High</i>
560 
+    <br />
561 
+    Skill Level: <i>High</i>
562 
+    <br />
563 
+    Likely Mentors: <i>Mike</i>
564 
+    <br />
565 
+    We're hearing from an increasing number of users that they want to use
566 
+    Thunderbird with Tor. However, there are plenty of application-level
567 
+    concerns, for example, by default Thunderbird will put your hostname in
568 
+    the outgoing mail that it sends. At some point we should start a new
569 
+    push to build a Thunderbird extension similar to Torbutton.
570 
+    </li>
571 
+
572 
+    <!--<li>
573 
+    <b>Intermediate Level Network Device Driver</b>
574 
+    <br />
575 
+    Priority: <i>Low</i>
576 
+    <br />
577 
+    Effort Level: <i>High</i>
578 
+    <br />
579 
+    Skill Level: <i>High</i>
580 
+    <br />
581 
+    Likely Mentors: <i>Martin</i>
582 
+    <br />
583 
+    The WinPCAP device driver used by Tor VM for bridged networking does
584 
+    not support a number of wireless and non-Ethernet network adapters.
585 
+    Implementation of a intermediate level network device driver for win32
586 
+    and 64bit would provide a way to intercept and route traffic over such
587 
+    networks. This project will require knowledge of and experience with
588 
+    Windows kernel device driver development and testing. Familiarity with
589 
+    Winsock and Qemu would also be helpful.
590 
+    </li>-->
591 
+
592 
+    <li>
593 
+    <b>Improve Tor Weather</b>
594 
+    <br />
595 
+    Priority: <i>Medium</i>
596 
+    <br />
597 
+    Effort Level: <i>Medium</i>
598 
+    <br />
599 
+    Skill Level: <i>Medium</i>
600 
+    <br />
601 
+    Likely Mentors: <i>Christian, Roger, Damian</i>
602 
+    <br />
603 
+    <a href="https://weather.torproject.org/">Tor weather</a> is a tool
604 
+    that allows signing up to receive notifications via email when the
605 
+    tracked Tor relay is down. Currently, it isn't really useful for
606 
+    people who use the hibernation feature of Tor, or for those who
607 
+    have to shut down their relay regularly. During the project, Tor
608 
+    weather could be extended to allow more flexible configurations.
609 
+    Other enhancements are also possible: Weather could send out warnings
610 
+    when your relay runs an out-of-date version of Tor, or when its
611 
+    observed bandwith drops below a certain value. It might also be a
612 
+    nice tool that allows for checking whether your relay has earned
613 
+    you a <a href="<page getinvolved/tshirt>">T-Shirt</a>, or sending reminders to
614 
+    directory authorities that
615 
+    their keys are about to expire. Be creative, and consider how the
616 
+    above project to track overall network status can help you get your job
617 
+    done more quickly! See also its
618 
+    <a href="https://svn.torproject.org/svn/weather/trunk/README">README</a>
619 
+    and <a href="https://svn.torproject.org/svn/weather/trunk/TODO">TODO</a>.
620 
+    </li>
621 
+
622 
+    <li>
623 
+    <b>Improvements for Tor+Vidalia interaction on Linux/Unix platforms</b>
624 
+    <br />
625 
+    Priority: <i>Medium</i>
626 
+    <br />
627 
+    Effort Level: <i>Medium</i>
628 
+    <br />
629 
+    Skill Level: <i>Medium</i>
630 
+    <br />
631 
+    Likely Mentors: <i>Erinn, Peter</i>
632 
+    <br />
633 
+    Vidalia currently doesn't play nicely with Tor on Linux and Unix platforms.
634 
+    Currently, on Debian and Ubuntu, there is a configuration mechanism which
635 
+    allows Vidalia to override Tor's ability to start on boot (by sourcing
636 
+    <code>/etc/default/tor.vidalia</code> which sets <code>RUN_DAEMON=no</code> at the user's
637 
+    request), but full implementation of <a href="<gitblob>doc/spec/control-spec.txt">ControlPort</a>
638 
+    communication is still required.
639 
+    <br />
640 
+    A better solution on Linux and Unix platforms would be to use Tor's
641 
+    ControlSocket, which allows Vidalia to talk to Tor via a Unix domain socket,
642 
+    and could possibly be enabled by default in Tor's distribution packages.
643 
+    Vidalia can then authenticate to Tor using filesystem-based (cookie)
644 
+    authentication if the user running Vidalia is also in the distribution-specific
645 
+    tor group.
646 
+    <br />
647 
+    This project will first involve adding support for Tor's ControlSocket to
648 
+    Vidalia. The student will then develop and test this support on various
649 
+    distributions to make sure it behaves in a predictable and consistent manner on
650 
+    all of them.
651 
+    <br />
652 
+    The next challenge would be to find an intuitive and usable way for Vidalia to be
653 
+    able to change Tor's configuration (torrc) even though it is located in
654 
+    <code>/etc/tor/torrc</code> and thus immutable. In Debian and Ubuntu we handle
655 
+    this with the aforementioned <code>/etc/default/tor.vidalia</code> but this
656 
+    functionality could (or should) be less distribution-specific.
657 
+    <br />
658 
+    The best idea we've come up with so far is to feed Tor a new configuration via
659 
+    the ControlSocket when Vidalia starts, but that's bad because if the user is not
660 
+    using the latest Debian/Ubuntu packages, they may not have disabled Tor's
661 
+    ability to run on boot and will end up with a configuration that is different
662 
+    from what they want. The second best idea we've come up with is for Vidalia to
663 
+    write out a temporary torrc file and ask the user to manually move it to
664 
+    <code>/etc/tor/torrc</code>, but that's bad because users shouldn't have to
665 
+    mess with files directly.
666 
+    <br />
667 
+    A person undertaking this project should have prior knowledge of various Linux
668 
+    distributions and their packaging mechanisms as well as some C++ development
669 
+    experience. Previous experience with Qt is helpful, but not required.
670 
+    </li>
671 
+
672 
+    <!--<li>
673 
+    <b>Tor/Polipo/Vidalia Auto-Update Framework</b>
674 
+    <br />
675 
+    We're in need of a good authenticated-update framework.
676 
+    Vidalia already has the ability to notice when the user is running an
677 
+    outdated or unrecommended version of Tor, using signed statements inside
678 
+    the Tor directory information. Currently, Vidalia simply pops
679 
+    up a little message box that lets the user know they should manually
680 
+    upgrade. The goal of this project would be to extend Vidalia with the
681 
+    ability to also fetch and install the updated Tor software for the
682 
+    user. We should do the fetches via Tor when possible, but also fall back
683 
+    to direct fetches in a smart way. Time permitting, we would also like
684 
+    to be able to update other
685 
+    applications included in the bundled installers, such as Polipo and
686 
+    Vidalia itself.
687 
+    <br />
688 
+    To complete this project, the student will first need to first investigate
689 
+    the existing auto-update frameworks (e.g., Sparkle on OS X) to evaluate
690 
+    their strengths, weaknesses, security properties, and ability to be
691 
+    integrated into Vidalia. If none are found to be suitable, the student
692 
+    will design their own auto-update framework, document the design, and
693 
+    then discuss the design with other developers to assess any security
694 
+    issues. The student will then implement their framework (or integrate
695 
+    an existing one) and test it.
696 
+    <br />
697 
+    A person undertaking this project should have good C++ development
698 
+    experience. Previous experience with Qt is helpful, but not required. One
699 
+    should also have a good understanding of common security
700 
+    practices, such as package signature verification. Good writing ability
701 
+    is also important for this project, since a vital step of the project
702 
+    will be producing a design document to review and discuss
703 
+    with others prior to implementation.
704 
+    </li>-->
705 
+
706 
+    <li>
707 
+    <b>Improving the Tor QA process: Continuous Integration for builds</b>
708 
+    <br />
709 
+    Priority: <i>Medium</i>
710 
+    <br />
711 
+    Effort Level: <i>Medium</i>
712 
+    <br />
713 
+    Skill Level: <i>Medium</i>
714 
+    <br />
715 
+    Likely Mentors: <i>Erinn</i>
716 
+    <br />
717 
+    It would be useful to have automated build processes for Windows and
718 
+    probably other platforms. The purpose of having a continuous integration
719 
+    build environment is to ensure that Windows isn't left behind for any of
720 
+    the software projects used in the Tor project or its accompanying.<br />
721 
+    Buildbot may be a good choice for this as it appears to support all of
722 
+    the platforms Tor does. See the
723 
+    <a href="http://en.wikipedia.org/wiki/BuildBot">wikipedia entry for
724 
+    buildbot</a>.<br />
725 
+    There may be better options and the person undertaking this task should
726 
+    evaluate other options. Any person working on this automatic build
727 
+    process should have experience or be willing to learn how to build all
728 
+    of the respective Tor related code bases from scratch. Furthermore, the
729 
+    person should have some experience building software in Windows
730 
+    environments as this is the target audience we want to ensure we do not
731 
+    leave behind. It would require close work with the Tor source code but
732 
+    probably only in the form of building, not authoring.<br />
733 
+    Additionally, we need to automate our performance testing for all platforms.
734 
+    We've got buildbot (except on Windows &mdash; as noted above) to automate
735 
+    our regular integration and compile testing already,
736 
+    but we need to get our network simulation tests (as built in torflow)
737 
+    updated for more recent versions of Tor, and designed to launch a test
738 
+    network either on a single machine, or across several, so we can test
739 
+    changes in performance on machines in different roles automatically.
740 
+    </li>
741 
+
742 
+    <!--<li>
743 
+    <b>Usability testing of Tor</b>
744 
+    <br />
745 
+    Priority: <i>Medium</i>
746 
+    <br />
747 
+    Effort Level: <i>Medium</i>
748 
+    <br />
749 
+    Skill Level: <i>Low to Medium</i>
750 
+    <br />
751 
+    Likely Mentors: <i>Andrew</i>
752 
+    <br />
753 
+    Especially the browser bundle, ideally amongst our target demographic.
754 
+    That would help a lot in knowing what needs to be done in terms of bug
755 
+    fixes or new features. We get this informally at the moment, but a more
756 
+    structured process would be better.
757 
+    </li>-->
758 
+
759 
+    <li>
760 
+    <b>An authenticating IRC proxy</b>
761 
+    <br />
762 
+    Priority: <i>Low</i>
763 
+    <br />
764 
+    Effort Level: <i>Medium to High</i>
765 
+    <br />
766 
+    Skill Level: <i>Medium to High</i>
767 
+    <br />
768 
+    Likely Mentors: <i>Sebastian, Weasel, Roger</i>
769 
+    <br />
770 
+    The world needs an authenticating irc proxy. As we're periodically
771 
+    reminded from the Penny Arcade web comic, "Internet user + anonymity =
772 
+    jerk". With respect to websites we're actually doing ok, since websites
773 
+    can make their users log in and use other application-level authentication
774 
+    approaches. But IRC servers are much worse off, because most IRC server
775 
+    code is poorly written: hard to maintain, and harder to modify. Many
776 
+    IRC networks now block connections from Tor, and we're basically down to
777 
+    two holdouts (OFTC and Freenode). This state of affairs means that a lot
778 
+    of people around the world are thinking "I told you so" about anonymity
779 
+    online, when in fact the problem is simply lack of technology to make the
780 
+    problem manageable. We need some way to let the IRC networks distinguish
781 
+    which users have developed a reputation as not being jerks, so they can
782 
+    treat the two groups separately. There are some really cool research
783 
+    designs like <a href="http://www.cs.dartmouth.edu/~nymble/">Nymble</a>,
784 
+    which aim to let websites blacklist users without needing to learn who
785 
+    they are.  But Nymble is designed around web interactions. We need to
786 
+    build the glue around the IRC protocol that would let us plug in a project
787 
+    like Nymble (or a simpler one to start, as a proof-of-concept). One way
788 
+    to do that would be to build an IRC proxy that knows how to hear from
789 
+    IRC clients, knows how to talk to IRC servers, and has an additional
790 
+    layer that requires the users to authenticate.  Some work on this has
791 
+    begun by other volunteers, see their progress at <a
792 
+    href="http://github.com/anonirc/orc">http://github.com/anonirc/orc</a>.
793 
+    </li>
794 
+
795 
+    <li>
796 
+    <b>Make torsocks/dsocks work on OS X</b>
797 
+    <br />
798 
+    Priority: <i>Medium</i>
799 
+    <br />
800 
+    Effort Level: <i>Medium</i>
801 
+    <br />
802 
+    Skill Level: <i>Medium</i>
803 
+    <br />
804 
+    Likely Mentors: <i>?</i>
805 
+    <br />
806 
+    <a href="http://code.google.com/p/torsocks/">Torsocks</a> and <a
807 
+    href="http://code.google.com/p/dsocks/">dsocks</a> are wrappers that will
808 
+    run applications, intercept their outgoing network connections, and push
809 
+    those connections through Tor. The goal is to handle applications that
810 
+    don't support proxies (or don't supporting them well). To get it right,
811 
+    they need to intercept many system calls. The syscalls you need to
812 
+    intercept on Linux differ dramatically from those on BSD. So Torsocks
813 
+    works fine on Linux, dsocks works ok on BSD (though it may be less
814 
+    maintained and thus might miss more syscalls), and nothing works well
815 
+    on both. First, we should patch dsocks to use Tor's <i>mapaddress</i>
816 
+    commands from the controller interface, so we don't waste a whole
817 
+    round-trip inside Tor doing the resolve before connecting. Second,
818 
+    we should make our <i>torify</i> script detect which of torsocks or
819 
+    dsocks is installed, and call them appropriately. This probably means
820 
+    unifying their interfaces, and might involve sharing code between them
821 
+    or discarding one entirely.
822 
+    </li>
823 
+
824 
+    <li>
825 
+    <b>Bring up new ideas!</b>
826 
+    <br />
827 
+    Don't like any of these? Look at the <a
828 
+    href="<gitblob>doc/roadmaps/2008-12-19-roadmap-full.pdf">Tor development
829 
+    roadmap</a> for more ideas, or just try out Tor, Vidalia, and Torbutton,
830 
+    and find out what you think needs fixing.
831 
+    Some of the <a href="<gittree>doc/spec/proposals">current proposals</a>
832 
+    might also be short on developers.
833 
+    </li>
834 
+
835 
+    </ol>
836 
+
837 
+    <a id="OtherCoding"></a>
838 
+    <h2><a class="anchor" href="#OtherCoding">Other Coding and Design related ideas</a></h2>
839 
+    <ol>
840 
+    <li>Tor relays don't work well on Windows XP. On
841 
+    Windows, Tor uses the standard <tt>select()</tt> system
842 
+    call, which uses space in the non-page pool. This means
843 
+    that a medium sized Tor relay will empty the non-page pool, <a
844 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/WindowsBufferProblems">causing
845 
+    havoc and system crashes</a>. We should probably be using overlapped IO
846 
+    instead. One solution would be to teach <a
847 
+    href="http://www.monkey.org/~provos/libevent/">libevent</a> how to use
848 
+    overlapped IO rather than select() on Windows, and then adapt Tor to
849 
+    the new libevent interface. Christian King made a
850 
+    <a href="https://svn.torproject.org/svn/libevent-urz/trunk/">good
851 
+    start</a> on this in the summer of 2007.</li>
852 
+
853 
+    <li>We need to actually start building our <a href="<page
854 
+    docs/documentation>#DesignDoc">blocking-resistance design</a>. This involves
855 
+    fleshing out the design, modifying many different pieces of Tor, adapting
856 
+    <a href="<page projects/vidalia>">Vidalia</a> so it supports the
857 
+    new features, and planning for deployment.</li>
858 
+
859 
+    <li>We need a flexible simulator framework for studying end-to-end
860 
+    traffic confirmation attacks. Many researchers have whipped up ad hoc
861 
+    simulators to support their intuition either that the attacks work
862 
+    really well or that some defense works great. Can we build a simulator
863 
+    that's clearly documented and open enough that everybody knows it's
864 
+    giving a reasonable answer? This will spur a lot of new research.
865 
+    See the entry <a href="#Research">below</a> on confirmation attacks for
866 
+    details on the research side of this task &mdash; who knows, when it's
867 
+    done maybe you can help write a paper or three also.</li>
868 
+
869 
+    <li>Tor 0.1.1.x and later include support for hardware crypto accelerators
870 
+    via OpenSSL. It has been lightly tested and is possibly very buggy.  We're looking for more rigorous testing, performance analysis, and optimally, code fixes to openssl and Tor if needed.</li>
871 
+
872 
+    <li>Perform a security analysis of Tor with <a
873 
+    href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>. Determine
874 
+    if there are good fuzzing libraries out there for what we want. Win fame by
875 
+    getting credit when we put out a new release because of you!</li>
876 
+
877 
+    <li>Tor uses TCP for transport and TLS for link
878 
+    encryption. This is nice and simple, but it means all cells
879 
+    on a link are delayed when a single packet gets dropped, and
880 
+    it means we can only reasonably support TCP streams. We have a <a
881 
+    href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#YoushouldtransportallIPpacketsnotjustTCPpackets.">list
882 
+    of reasons why we haven't shifted to UDP transport</a>, but it would
883 
+    be great to see that list get shorter. We also have a proposed <a
884 
+    href="<gitblob>doc/spec/proposals/100-tor-spec-udp.txt">specification
885 
+    for Tor and
886 
+    UDP</a> &mdash; please let us know what's wrong with it.</li>
887 
+
888 
+    <li>We're not that far from having IPv6 support for destination addresses
889 
+    (at exit nodes). If you care strongly about IPv6, that's probably the
890 
+    first place to start.</li>
891 
+
892 
+    <li>We need a way to generate the website diagrams (for example, the "How
893 
+    Tor Works" pictures on the <a href="<page about/overview>">overview page</a>
894 
+    from source, so we can translate them as UTF-8 text rather than edit
895 
+    them by hand with Gimp. We might want to
896 
+    integrate this as an wml file so translations are easy and images are
897 
+    generated in multiple languages whenever we build the website.</li>
898 
+
899 
+    <li>How can we make the various LiveCD/USB systems easier
900 
+    to maintain, improve, and document?  One example is <a
901 
+    href="https://amnesia.boum.org/">The (Amnesic) Incognito Live
902 
+    System</a>.
903 
+    </li>
904 
+
905 
+    <li>
906 
+    Another anti-censorship project is to try to make Tor
907 
+    more scanning-resistant.  Right now, an adversary can identify <a
908 
+    href="<gitblob>doc/spec/proposals/125-bridges.txt">Tor bridges</a>
909 
+    just by trying to connect to them, following the Tor protocol,
910 
+    and seeing if they respond.  To solve this, bridges could <a
911 
+    href="<svnprojects>design-paper/blocking.html#tth_sEc9.3">act like
912 
+    webservers</a> (HTTP or HTTPS) when contacted by port-scanning tools,
913 
+    and not act like bridges until the user provides a bridge-specific key.
914 
+    To start, check out Shane Pope's <a
915 
+    href="http://dl.dropbox.com/u/37735/index.html">thesis and prototype</a>.
916 
+    </li>
917 
+
918 
+    </ol>
919 
+
920 
+    <a id="Research"></a>
921 
+    <h2><a class="anchor" href="#Research">Research</a></h2>
922 
+    <ol>
923 
+    <li>The "end-to-end traffic confirmation attack":
924 
+    by watching traffic at Alice and at Bob, we can <a
925 
+    href="http://freehaven.net/anonbib/#danezis:pet2004">compare
926 
+    traffic signatures and become convinced that we're watching the same
927 
+    stream</a>. So far Tor accepts this as a fact of life and assumes this
928 
+    attack is trivial in all cases. First of all, is that actually true? How
929 
+    much traffic of what sort of distribution is needed before the adversary
930 
+    is confident he has won? Are there scenarios (e.g. not transmitting much)
931 
+    that slow down the attack? Do some traffic padding or traffic shaping
932 
+    schemes work better than others?</li>
933 
+    <li>A related question is: Does running a relay/bridge provide additional
934 
+    protection against these timing attacks? Can an external adversary that can't
935 
+    see inside TLS links still recognize individual streams reliably?
936 
+    Does the amount of traffic carried degrade this ability any? What if the
937 
+    client-relay deliberately delayed upstream relayed traffic to create a queue
938 
+    that could be used to mimic timings of client downstream traffic to make it
939 
+    look like it was also relayed? This same queue could also be used for masking
940 
+    timings in client upstream traffic with the techniques from <a
941 
+    href="http://www.freehaven.net/anonbib/#ShWa-Timing06">adaptive padding</a>,
942 
+    but without the need for additional traffic. Would such an interleaving of
943 
+    client upstream traffic obscure timings for external adversaries? Would the
944 
+    strategies need to be adjusted for asymmetric links? For example, on
945 
+    asymmetric links, is it actually possible to differentiate client traffic from
946 
+    natural bursts due to their asymmetric capacity? Or is it easier than
947 
+    symmetric links for some other reason?</li>
948 
+    <li>Repeat Murdoch and Danezis's <a
949 
+    href="http://www.cl.cam.ac.uk/~sjm217/projects/anon/#torta">attack from
950 
+    Oakland 05</a> on the current Tor network. See if you can learn why it
951 
+    works well on some nodes and not well on others. (My theory is that the
952 
+    fast nodes with spare capacity resist the attack better.) If that's true,
953 
+    then experiment with the RelayBandwidthRate and RelayBandwidthBurst
954 
+    options to run a relay that is used as a client while relaying the
955 
+    attacker's traffic: as we crank down the RelayBandwidthRate, does the
956 
+    attack get harder? What's the right ratio of RelayBandwidthRate to
957 
+    actually capacity? Or is it a ratio at all? While we're at it, does a
958 
+    much larger set of candidate relays increase the false positive rate
959 
+    or other complexity for the attack? (The Tor network is now almost two
960 
+    orders of magnitude larger than it was when they wrote their paper.) Be
961 
+    sure to read <a href="http://freehaven.net/anonbib/#clog-the-queue">Don't
962 
+    Clog the Queue</a> too.</li>
963 
+    <li>The "routing zones attack": most of the literature thinks of
964 
+    the network path between Alice and her entry node (and between the
965 
+    exit node and Bob) as a single link on some graph. In practice,
966 
+    though, the path traverses many autonomous systems (ASes), and <a
967 
+    href="http://freehaven.net/anonbib/#feamster:wpes2004">it's not uncommon
968 
+    that the same AS appears on both the entry path and the exit path</a>.
969 
+    Unfortunately, to accurately predict whether a given Alice, entry,
970 
+    exit, Bob quad will be dangerous, we need to download an entire Internet
971 
+    routing zone and perform expensive operations on it. Are there practical
972 
+    approximations, such as avoiding IP addresses in the same /8 network?</li>
973 
+    <li>Other research questions regarding geographic diversity consider
974 
+    the tradeoff between choosing an efficient circuit and choosing a random
975 
+    circuit. Look at Stephen Rollyson's <a
976 
+    href="http://swiki.cc.gatech.edu:8080/ugResearch/uploads/7/ImprovingTor.pdf">position
977 
+    paper</a> on how to discard particularly slow choices without hurting
978 
+    anonymity "too much". This line of reasoning needs more work and more
979 
+    thinking, but it looks very promising.</li>
980 
+    <li>Tor doesn't work very well when relays have asymmetric bandwidth
981 
+    (e.g. cable or DSL). Because Tor has separate TCP connections between
982 
+    each hop, if the incoming bytes are arriving just fine and the outgoing
983 
+    bytes are all getting dropped on the floor, the TCP push-back mechanisms
984 
+    don't really transmit this information back to the incoming streams.
985 
+    Perhaps Tor should detect when it's dropping a lot of outgoing packets,
986 
+    and rate-limit incoming streams to regulate this itself? I can imagine
987 
+    a build-up and drop-off scheme where we pick a conservative rate-limit,
988 
+    slowly increase it until we get lost packets, back off, repeat. We
989 
+    need somebody who's good with networks to simulate this and help design
990 
+    solutions; and/or we need to understand the extent of the performance
991 
+    degradation, and use this as motivation to reconsider UDP transport.</li>
992 
+    <li>A related topic is congestion control. Is our
993 
+    current design sufficient once we have heavy use? Maybe
994 
+    we should experiment with variable-sized windows rather
995 
+    than fixed-size windows? That seemed to go well in an <a
996 
+    href="http://www.psc.edu/networking/projects/hpn-ssh/theory.php">ssh
997 
+    throughput experiment</a>. We'll need to measure and tweak, and maybe
998 
+    overhaul if the results are good.</li>
999 
+    <li>Our censorship-resistance goals include preventing
1000 
+    an attacker who's looking at Tor traffic on the wire from <a
1001 
+    href="<svnprojects>design-paper/blocking.html#sec:network-fingerprint">distinguishing
1002 
+    it from normal SSL traffic</a>. Obviously we can't achieve perfect
1003 
+    steganography and still remain usable, but for a first step we'd like to
1004 
+    block any attacks that can win by observing only a few packets. One of
1005 
+    the remaining attacks we haven't examined much is that Tor cells are 512
1006 
+    bytes, so the traffic on the wire may well be a multiple of 512 bytes.
1007 
+    How much does the batching and overhead in TLS records blur this on the
1008 
+    wire? Do different buffer flushing strategies in Tor affect this? Could
1009 
+    a bit of padding help a lot, or is this an attack we must accept?</li>
1010 
+    <li>Tor circuits are built one hop at a time, so in theory we have the
1011 
+    ability to make some streams exit from the second hop, some from the
1012 
+    third, and so on. This seems nice because it breaks up the set of exiting
1013 
+    streams that a given relay can see. But if we want each stream to be safe,
1014 
+    the "shortest" path should be at least 3 hops long by our current logic, so
1015 
+    the rest will be even longer. We need to examine this performance / security
1016 
+    tradeoff.</li>
1017 
+    <li>It's not that hard to DoS Tor relays or directory authorities. Are client
1018 
+    puzzles the right answer? What other practical approaches are there? Bonus
1019 
+    if they're backward-compatible with the current Tor protocol.</li>
1020 
+    <li>Programs like <a
1021 
+    href="<page projects/torbutton>">Torbutton</a> aim to hide
1022 
+    your browser's UserAgent string by replacing it with a uniform answer for
1023 
+    every Tor user. That way the attacker can't splinter Tor's anonymity set
1024 
+    by looking at that header. It tries to pick a string that is commonly used
1025 
+    by non-Tor users too, so it doesn't stand out. Question one: how badly
1026 
+    do we hurt ourselves by periodically updating the version of Firefox
1027 
+    that Torbutton claims to be? If we update it too often, we splinter the
1028 
+    anonymity sets ourselves. If we don't update it often enough, then all the
1029 
+    Tor users stand out because they claim to be running a quite old version
1030 
+    of Firefox. The answer here probably depends on the Firefox versions seen
1031 
+    in the wild. Question two: periodically people ask us to cycle through N
1032 
+    UserAgent strings rather than stick with one. Does this approach help,
1033 
+    hurt, or not matter? Consider: cookies and recognizing Torbutton users
1034 
+    by their rotating UserAgents; malicious websites who only attack certain
1035 
+    browsers; and whether the answers to question one impact this answer.
1036 
+    </li>
1037 
+    <li>Right now Tor clients are willing to reuse a given circuit for ten
1038 
+    minutes after it's first used. The goal is to avoid loading down the
1039 
+    network with too many circuit extend operations, yet to also avoid having
1040 
+    clients use the same circuit for so long that the exit node can build a
1041 
+    useful pseudonymous profile of them. Alas, ten minutes is probably way
1042 
+    too long, especially if connections from multiple protocols (e.g. IM and
1043 
+    web browsing) are put on the same circuit. If we keep fixed the overall
1044 
+    number of circuit extends that the network needs to do, are there more
1045 
+    efficient and/or safer ways for clients to allocate streams to circuits,
1046 
+    or for clients to build preemptive circuits? Perhaps this research item
1047 
+    needs to start with gathering some traces of what connections typical
1048 
+    clients try to launch, so you have something realistic to try to optimize.
1049 
+    </li>
1050 
+    <li>How many bridge relays do you need to know to maintain
1051 
+    reachability? We should measure the churn in our bridges. If there is
1052 
+    lots of churn, are there ways to keep bridge users more likely to stay
1053 
+    connected?
1054 
+    </li>
1055 
+    </ol>
1056 
+
1057 
+    <p>
1058 
+    <a href="<page about/contact>">Let us know</a> if you've made progress on any
1059 
+    of these!
1060 
+    </p>
1061 
+  </div>
1062 
+  <!-- END MAINCOL -->
1063 
+  <div id = "sidecol">
1064 
+#include "side.wmi"
1065 
+#include "info.wmi"
1066 
+  </div>
1067 
+  <!-- END SIDECOL -->
1068 
+</div>
1069 
+<!-- END CONTENT -->
1070 
+#include <foot.wmi>
global.js
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,7 @@
1 
+// JavaScript Document
2 
+
3 
+function clearDefault(el) {
4 
+ if (el.defaultValue == el.value) {
5 
+   el.value = "";
6 
+ }
7 
+}
0 8 
\ No newline at end of file
images/._.DS_Store
Zeige Datei @ 2a9aaa802
images/._activists.jpg
Zeige Datei @ 2a9aaa802
images/._banner-gradient.jpg
Zeige Datei @ 2a9aaa802
images/._bg-banner.jpg
Zeige Datei @ 2a9aaa802
images/._bg-banner.png
Zeige Datei @ 2a9aaa802
images/._bg-nav-hover.jpg
Zeige Datei @ 2a9aaa802
images/._bg-sidenav-active-longtitle.jpg
Zeige Datei @ 2a9aaa802
images/._bg-sidenav-active-longtitle.png
Zeige Datei @ 2a9aaa802
images/._bg-sidenav-active.jpg
Zeige Datei @ 2a9aaa802
images/._bg-sidenav-active.png
Zeige Datei @ 2a9aaa802
images/._button-donate.jpg
Zeige Datei @ 2a9aaa802
images/._button-download-arrow.gif
Zeige Datei @ 2a9aaa802
images/._button-download-arrow.png
Zeige Datei @ 2a9aaa802
images/._button-download.gif
Zeige Datei @ 2a9aaa802
images/._button-download.png
Zeige Datei @ 2a9aaa802
images/._consumers.jpg
Zeige Datei @ 2a9aaa802
images/._donationchart.jpg
Zeige Datei @ 2a9aaa802
images/._family.jpg
Zeige Datei @ 2a9aaa802
images/._icon-advocacy.jpg
Zeige Datei @ 2a9aaa802
images/._icon-advocacy.png
Zeige Datei @ 2a9aaa802
images/._icon-ae.gif
Zeige Datei @ 2a9aaa802
images/._icon-android.gif
Zeige Datei @ 2a9aaa802
images/._icon-calendar.jpg
Zeige Datei @ 2a9aaa802
images/._icon-default.jpg
Zeige Datei @ 2a9aaa802
images/._icon-design.jpg
Zeige Datei @ 2a9aaa802
images/._icon-design.png
Zeige Datei @ 2a9aaa802
images/._icon-development.jpg
Zeige Datei @ 2a9aaa802
images/._icon-development.png
Zeige Datei @ 2a9aaa802
images/._icon-documentation.jpg
Zeige Datei @ 2a9aaa802
images/._icon-documentation.png
Zeige Datei @ 2a9aaa802
images/._icon-donate.jpg
Zeige Datei @ 2a9aaa802
images/._icon-donate.png
Zeige Datei @ 2a9aaa802
images/._icon-hardware.jpg
Zeige Datei @ 2a9aaa802
images/._icon-hardware.png
Zeige Datei @ 2a9aaa802
images/._icon-jobs.jpg
Zeige Datei @ 2a9aaa802
images/._icon-jobs.png
Zeige Datei @ 2a9aaa802
images/._icon-linux.gif
Zeige Datei @ 2a9aaa802
images/._icon-mac.gif
Zeige Datei @ 2a9aaa802
images/._icon-mc.gif
Zeige Datei @ 2a9aaa802
images/._icon-relay-lg.jpg
Zeige Datei @ 2a9aaa802
images/._icon-relay-lg.png
Zeige Datei @ 2a9aaa802
images/._icon-relay-sm.jpg
Zeige Datei @ 2a9aaa802
images/._icon-relay-sm.png
Zeige Datei @ 2a9aaa802
images/._icon-research.jpg
Zeige Datei @ 2a9aaa802
images/._icon-research.png
Zeige Datei @ 2a9aaa802
images/._icon-translate.jpg
Zeige Datei @ 2a9aaa802
images/._icon-translate.png
Zeige Datei @ 2a9aaa802
images/._icon-visa.gif
Zeige Datei @ 2a9aaa802
images/._icon-windows.gif
Zeige Datei @ 2a9aaa802
images/._ie-bg-sidenav-active-longtitle.jpg
Zeige Datei @ 2a9aaa802
images/._ie-bg-sidenav-active.jpg
Zeige Datei @ 2a9aaa802
images/._lightbulb.jpg
Zeige Datei @ 2a9aaa802
images/._media.jpg
Zeige Datei @ 2a9aaa802
images/._military.jpg
Zeige Datei @ 2a9aaa802
images/._onion.jpg
Zeige Datei @ 2a9aaa802
images/._shadow.gif
Zeige Datei @ 2a9aaa802
images/._shadowAlpha.png
Zeige Datei @ 2a9aaa802
images/._sidenav-active.png
Zeige Datei @ 2a9aaa802
images/._sidenav-arrow-active.gif
Zeige Datei @ 2a9aaa802
images/._sidenav-arrow-active.png
Zeige Datei @ 2a9aaa802
images/._sidenav-arrow.gif
Zeige Datei @ 2a9aaa802
images/._sidenav-arrow.png
Zeige Datei @ 2a9aaa802
images/._table-arrow.jpg
Zeige Datei @ 2a9aaa802
images/._table-arrow.png
Zeige Datei @ 2a9aaa802
images/._table-head.jpg
Zeige Datei @ 2a9aaa802
images/._table-title-arrow.jpg
Zeige Datei @ 2a9aaa802
images/._table-title.jpg
Zeige Datei @ 2a9aaa802
images/._tor-logo.jpg
Zeige Datei @ 2a9aaa802
images/._warning.jpg
Zeige Datei @ 2a9aaa802
images/._warning.png
Zeige Datei @ 2a9aaa802
images/._white-bullet.png
Zeige Datei @ 2a9aaa802
images/activists.jpg
Zeige Datei @ 2a9aaa802
images/banner-gradient.jpg
Zeige Datei @ 2a9aaa802
images/bg-banner.jpg
Zeige Datei @ 2a9aaa802
images/bg-banner.png
Zeige Datei @ 2a9aaa802
images/bg-nav-hover.jpg
Zeige Datei @ 2a9aaa802
images/bg-sidenav-active-longtitle.jpg
Zeige Datei @ 2a9aaa802
images/bg-sidenav-active-longtitle.png
Zeige Datei @ 2a9aaa802
images/bg-sidenav-active.jpg
Zeige Datei @ 2a9aaa802
images/bg-sidenav-active.png
Zeige Datei @ 2a9aaa802
images/button-donate.jpg
Zeige Datei @ 2a9aaa802
images/button-download-arrow.gif
Zeige Datei @ 2a9aaa802
images/button-download-arrow.png
Zeige Datei @ 2a9aaa802
images/button-download.gif
Zeige Datei @ 2a9aaa802
images/button-download.jpg
Zeige Datei @ 2a9aaa802
images/button-download.png
Zeige Datei @ 2a9aaa802
images/button-go.jpg
Zeige Datei @ 2a9aaa802
images/button-signup.jpg
Zeige Datei @ 2a9aaa802
images/calltoaction-dl.jpg
Zeige Datei @ 2a9aaa802
images/calltoaction-donate.jpg
Zeige Datei @ 2a9aaa802
images/calltoaction-getinvolved.jpg
Zeige Datei @ 2a9aaa802
images/consumers.jpg
Zeige Datei @ 2a9aaa802
images/donationchart.jpg
Zeige Datei @ 2a9aaa802
images/family.jpg
Zeige Datei @ 2a9aaa802
images/favicon.ico
Zeige Datei @ 2a9aaa802
images/icon-advocacy.jpg
Zeige Datei @ 2a9aaa802
images/icon-advocacy.png
Zeige Datei @ 2a9aaa802
images/icon-ae.gif
Zeige Datei @ 2a9aaa802
images/icon-android.gif
Zeige Datei @ 2a9aaa802
images/icon-calendar.jpg
Zeige Datei @ 2a9aaa802
images/icon-default.jpg
Zeige Datei @ 2a9aaa802
images/icon-design.jpg
Zeige Datei @ 2a9aaa802
images/icon-design.png
Zeige Datei @ 2a9aaa802
images/icon-development.jpg
Zeige Datei @ 2a9aaa802
images/icon-development.png
Zeige Datei @ 2a9aaa802
images/icon-documentation.jpg
Zeige Datei @ 2a9aaa802
images/icon-documentation.png
Zeige Datei @ 2a9aaa802
images/icon-donate.jpg
Zeige Datei @ 2a9aaa802
images/icon-donate.png
Zeige Datei @ 2a9aaa802
images/icon-hardware.jpg
Zeige Datei @ 2a9aaa802
images/icon-hardware.png
Zeige Datei @ 2a9aaa802
images/icon-jobs.jpg
Zeige Datei @ 2a9aaa802
images/icon-jobs.png
Zeige Datei @ 2a9aaa802
images/icon-linux.gif
Zeige Datei @ 2a9aaa802
images/icon-mac.gif
Zeige Datei @ 2a9aaa802
images/icon-mc.gif
Zeige Datei @ 2a9aaa802
images/icon-relay-lg.jpg
Zeige Datei @ 2a9aaa802
images/icon-relay-lg.png
Zeige Datei @ 2a9aaa802
images/icon-relay-sm.jpg
Zeige Datei @ 2a9aaa802
images/icon-relay-sm.png
Zeige Datei @ 2a9aaa802
images/icon-research.jpg
Zeige Datei @ 2a9aaa802
images/icon-research.png
Zeige Datei @ 2a9aaa802
images/icon-translate.jpg
Zeige Datei @ 2a9aaa802
images/icon-translate.png
Zeige Datei @ 2a9aaa802
images/icon-visa.gif
Zeige Datei @ 2a9aaa802
images/icon-windows.gif
Zeige Datei @ 2a9aaa802
images/ie-bg-sidenav-active-longtitle.jpg
Zeige Datei @ 2a9aaa802
images/ie-bg-sidenav-active.jpg
Zeige Datei @ 2a9aaa802
images/lightbulb.jpg
Zeige Datei @ 2a9aaa802
images/media.jpg
Zeige Datei @ 2a9aaa802
images/military.jpg
Zeige Datei @ 2a9aaa802
images/onion.jpg
Zeige Datei @ 2a9aaa802
images/shadow.gif
Zeige Datei @ 2a9aaa802
images/shadowAlpha.png
Zeige Datei @ 2a9aaa802
images/sidenav-active.png
Zeige Datei @ 2a9aaa802
images/sidenav-arrow-active.gif
Zeige Datei @ 2a9aaa802
images/sidenav-arrow-active.png
Zeige Datei @ 2a9aaa802
images/sidenav-arrow.gif
Zeige Datei @ 2a9aaa802
images/sidenav-arrow.png
Zeige Datei @ 2a9aaa802
images/table-arrow.jpg
Zeige Datei @ 2a9aaa802
images/table-arrow.png
Zeige Datei @ 2a9aaa802
images/table-head.jpg
Zeige Datei @ 2a9aaa802
images/table-title-arrow.jpg
Zeige Datei @ 2a9aaa802
images/table-title.jpg
Zeige Datei @ 2a9aaa802
images/tor-logo.jpg
Zeige Datei @ 2a9aaa802
images/warning.jpg
Zeige Datei @ 2a9aaa802
images/warning.png
Zeige Datei @ 2a9aaa802
images/white-bullet.png
Zeige Datei @ 2a9aaa802
include/._.DS_Store
Zeige Datei @ 2a9aaa802
include/README
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,51 @@
1 
+Here's a brief overview of how our wml set-up works.
2 
+----------------------------------------------------
3 
+
4 
+Here's a typical wml file:
5 
+https://svn.torproject.org/svn/website/trunk/en/bridges.wml
6 
+
7 
+The top of the file has:
8 
+
9 
+  ## translation metadata
10 
+  # Revision: $Revision$
11 
+  # Translation-Priority: 1-high
12 
+
13 
+  #include "head.wmi" TITLE="Tor: Bridges"
14 
+
15 
+  <div class="main-column">
16 
+
17 
+and the bottom of the file has:
18 
+
19 
+    </div><!-- #main -->
20 
+
21 
+  #include <foot.wmi>
22 
+
23 
+and the middle is standard html, plus a few extra tags like
24 
+<page> that we've added to automatically link to the translated
25 
+pages when they exist. So that wml page produces this html page:
26 
+https://www.torproject.org/bridges aka
27 
+https://www.torproject.org/bridges.html.en
28 
+
29 
+Then head.wmi and foot.wmi are just other mostly-html files you import
30 
+to handle the repeat parts of each page (well, that plus some embedded
31 
+perl scripts to generate some of the static content).
32 
+https://svn.torproject.org/svn/website/trunk/include/head.wmi
33 
+https://svn.torproject.org/svn/website/trunk/en/foot.wmi
34 
+
35 
+You can basically ignore the wml part of them, and to a first
36 
+approximation just think of them as more html.
37 
+
38 
+So in summary, wml is like html with a bit more markup.
39 
+
40 
+----------------------------------------------------
41 
+
42 
+Where it gets interesting is the download page:
43 
+https://svn.torproject.org/svn/website/trunk/en/easy-download.wml
44 
+
45 
+It has the standard header and footer section, but in the body of the page
46 
+it includes links like <a href="<package-osx-bundle-stable>". Rather than
47 
+putting URLs and Tor versions into every wml page, and then requiring
48 
+the translators to update their page whenever we bump a version number,
49 
+we instead define each URL and version as a new wml element:
50 
+https://svn.torproject.org/svn/website/trunk/include/versions.wmi
51 
+
include/foot.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,111 @@
1 
+#!/usr/bin/env wml
2 
+    <div id="footer">
3 
+    	<div class="onion"><img src="$(IMGROOT)/onion.jpg" alt="Tor" /></div>
4 
+      <div class="about">
5 
+      	<p>"Tor" and the "Onion Logo" are registered trademarks of <a href="#">The Tor Project, Inc.</a> Content on this site is licensed under a <a href="#">Creative Commons Attribution 3.0 United States License</a>, unless otherwise noted.</p>
6 
+        # This will grab the date from svn info but formatting is tedious
7 
+       	# REQUIRES svn for this to work
8 
+        <p>
9 
+        <:{
10 
+          my $svninfo = `svn info`;
11 
+          if ($svninfo =~ m/Last Changed Date: (\d{4}-\d{2}-\d{2})\s(\d{2}:\d{2}:\d{2})\s(.*)\s\((.*)\)/) {
12 
+            my $modifydate = "$4 $2 $3";
13 
+            # remove commas from date
14 
+            $modifydate =~ s/,//;
15 
+            print 'Last modified: '.$modifydate."\n";
16 
+          }
17 
+        }:>
18 
+        <br />
19 
+        <:{
20 
+          #my $compiledate = `date`;
21 
+          my $compiledate = `date +"%a %b %d %Y %k:%M:%S %z"`;
22 
+          print 'Last compiled: '.$compiledate."\n";
23 
+        }:>
24 
+        </p>
25 
+      </div>
26 
+      <!-- END ABOUT -->
27 
+      <div class="newsletter">
28 
+        <form action="">
29 
+          <input class="textfield" type="text" name="email" value="Sign up for our newsletter! Enter email." onClick="clearDefault(this);" />
30 
+          <input class="signup" type="submit" name="submit" value="Sign Up" />
31 
+        </form>
32 
+      </div>
33 
+      <!-- END NEWSLETTER -->
34 
+      <div class="col first">
35 
+      	<h4>About Tor</h4>
36 
+        <ul>
37 
+          <li><a href="<page about/about>">What Tor Does</a></li>
38 
+          <li><a href="<page about/torusers>">Users of Tor</a></li>
39 
+          <li><a href="<page about/corepeople>">Core Tor People</a></li>
40 
+          <li><a href="<page about/sponsors>">Sponsors</a></li>
41 
+          <li><a href="<page about/contact>">Contact Us</a></li>
42 
+        </ul>
43 
+      </div>
44 
+      <!-- END COL -->
45 
+      <div class="col">
46 
+      	<h4>Get Involved</h4>
47 
+        <ul>
48 
+          <li><a href="<page donate/donate>">Donate</a></li>
49 
+          <li><a href="<page getinvolved/getinvolved>">Mailing List</a></li>
50 
+          <li><a href="#">Relays</a></li>
51 
+          <li><a href="<page docs/running-a-mirror>">Mirrors</a></li>
52 
+          <li><a href="<page docs/hidden-services>">Hidden Services</a></li>
53 
+          <li><a href="<page getinvolved/translation>">Translations</a></li>
54 
+          <li><a href="<page getinvolved/open-positions>">Careers</a></li>
55 
+        </ul>
56 
+      </div>
57 
+      <!-- END COL -->
58 
+      <div class="col">
59 
+      	<h4>Documentation</h4>
60 
+        <ul>
61 
+          <li><a href="<page docs/tor-manual>">Manuals</a></li>
62 
+          <li><a href="<page docs/documentation>">Installation Guides</a></li>
63 
+          <li><a href="<page docs/glossary>">Glossary</a></li>
64 
+          <li><a href="http://wiki.torproject.org">Tor Wiki</a></li>
65 
+          <li><a href="<page docs/faq>">FAQ</a></li>
66 
+        </ul>
67 
+      </div>
68 
+      <!-- END COL -->
69 
+      <div class="col wider">
70 
+      	<h4>Languages</h4>
71 
+        # this is a cgi trampoline to bounce us to the right page
72 
+        # alternately, if the client supports javascript we can redirect that way
73 
+        # noscript does not block onclick but clients may have disabled javascript completely
74 
+        #
75 
+        # for this to work we need to know the relative path from the document root
76 
+        # to the current directory that wml is in.
77 
+        <form action="$(DOCROOT)/cgi-bin/languageswitch.cgi">
78 
+          <select name="Language" id="lang">
79 
+          <:{
80 
+            #import "perl-globals.wmi";
81 
+            use Cwd;
82 
+            use Cwd 'abs_path';
83 
+            use File::Spec;
84 
+            my $urlbase = File::Spec->abs2rel(getcwd(),abs_path("$(DOCROOT)"));
85 
+            my $LANGUAGES;
86 
+            my $page = $WML_SRC_FILENAME;
87 
+            opendir(DIR, getcwd()) or die $!;
88 
+            # take a look and see what language support we have
89 
+            while (my $file = readdir(DIR)) {
90 
+                if (-d $file) {
91 
+                    if (-e "$file/$page") {
92 
+                        my $url = $urlbase.'/'.$WML_SRC_BASENAME.'.html.'.$file;
93 
+                        my $url2js = $WML_SRC_BASENAME.'.html.'.$file;
94 
+                        print '<option value="'.$url.'" onclick="window.location=\''.$url2js.'\'">'.$LANGUAGES{$file}.'</option>'."\n" unless not defined $LANGUAGES{$file};
95 
+                    }
96 
+                }
97 
+            }
98 
+            closedir(DIR);
99 
+          }:>
100 
+          </select>
101 
+          <input class="go" type="submit" name="submit" value="Go" />
102 
+        </form>
103 
+        <p>Questions on this? Visit <a href="http://www.debian.org/intro/cn#howtoset">how to set the default document language</a>.</p>
104 
+      </div>
105 
+    </div>
106 
+    <!-- END FOOTER -->
107 
+
108 
+  </div>
109 
+  <!-- END WRAP -->
110 
+</body>
111 
+</html>
include/functions.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,92 @@
1 
+#!/usr/bin/wml
2 
+
3 
+<:
4 
+
5 
+sub getMetadata($) {
6 
+	my ($file) = @_;
7 
+
8 
+	die ("File $file is not a regular file") unless (-f $file);
9 
+
10 
+	open(F, "$file") or die ("Cannot open $file: $!\n");
11 
+	my $found_metadata = 0;
12 
+	while (<F>) {
13 
+		chomp;
14 
+		s/\r$//;
15 
+		if ($_ eq '## translation metadata') {
16 
+			$found_metadata = 1;
17 
+			last;
18 
+		};
19 
+	};
20 
+	die ("Did not find translation metadata in $file") unless $found_metadata;
21 
+	my %data;
22 
+	while (<F>) {
23 
+		chomp;
24 
+		s/\r$//;
25 
+		if (/^#\s*(\S*):\s*(.*?)\s*$/) {
26 
+			$data{$1} = $2;
27 
+		} else {
28 
+			last;
29 
+		};
30 
+	};
31 
+	return \%data;
32 
+};
33 
+
34 
+sub translation_get_masterrevision_file($$) {
35 
+	my ($dir, $page) = @_;
36 
+	my $master = getMetadata("$dir/en/$page");
37 
+
38 
+	die ("Cannot find 'Revision' header in master's translation metadata of en/$page") unless exists $master->{'Revision'};
39 
+
40 
+	my ($rev) = $master->{'Revision'} =~ m/([0-9.]+)/;
41 
+	if ($rev eq '') { $rev = '(Revision not a valid number)'; };
42 
+
43 
+	return $rev;
44 
+};
45 
+sub translation_get_masterrevision() {
46 
+	translation_get_masterrevision_file('.', $WML_SRC_FILENAME);
47 
+};
48 
+
49 
+sub translation_get_basedonrevision_langfile($$$) {
50 
+	my ($dir, $lang, $page) = @_;
51 
+	my $translation = getMetadata("$dir/$lang/$page");
52 
+
53 
+	if (exists $translation->{'Based-On-Revision'}) {
54 
+		return $translation->{'Based-On-Revision'};
55 
+	} else {
56 
+		 return '(unknown)';
57 
+	}
58 
+};
59 
+sub translation_get_basedonrevision() {
60 
+	translation_get_basedonrevision_langfile(".", "$(LANG)", $WML_SRC_FILENAME);
61 
+};
62 
+
63 
+
64 
+sub translation_current() {
65 
+	return (translation_get_masterrevision() eq translation_get_basedonrevision());
66 
+};
67 
+
68 
+sub file_is_obsolete($$$) {
69 
+	my ($dir, $lang, $page) = @_;
70 
+	my $translation = getMetadata("$dir/$lang/$page");
71 
+	return (exists $translation->{'Status'} && ($translation->{'Status'} eq 'obsolete'))
72 
+};
73 
+
74 
+sub list_translations() {
75 
+  my @links = ();
76 
+  my $page = $WML_SRC_FILENAME;
77 
+  $page =~ s/\.wml//;
78 
+  for my $dir (@LANGUAGES) {
79 
+    if (-e "$dir/$WML_SRC_FILENAME") {
80 
+      if ($dir ne '$(LANG)') {
81 
+        push @links, sprintf('<a href="%s.html.%s">%s</a>', $page, $dir, $LANGUAGES{$dir});
82 
+      };
83 
+    };
84 
+  };
85 
+  return join(', ', @links);
86 
+};
87 
+
88 
+sub has_translations() {
89 
+  return list_translations() ne '';
90 
+};
91 
+
92 
+:>
include/head.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,141 @@
1 
+#! /usr/bin/wml
2 
+<: use strict; :>
3 
+<: use warnings; :>
4 
+#use "perl-globals.wmi"
5 
+#use "links.wmi"
6 
+#use "versions.wmi"
7 
+#use "navigation.wmi"
8 
+
9 
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
10 
+<html xmlns="http://www.w3.org/1999/xhtml">
11 
+<head>
12 
+  <title>$(TITLE)</title>
13 
+  <link rel="shortcut icon" type="image/x-icon" href="$(IMGROOT)/favicon.ico" />
14 
+  <ifneq "$(REDIRECT)" "" "<meta http-equiv="refresh" content="0;url=$(DOCROOT)/$(REDIRECT)" />">
15 
+  <ifneq "$(REDIRECT_GLOBAL)" "" "<meta http-equiv="refresh" content="0;url=$(REDIRECT_GLOBAL)" />">
16 
+  <ifeq "$(ANNOUNCE_RSS)" "yes" "<link rel="alternate" title="Tor Project OR-announce" href="http://rss.gmane.org/gmane.network.onion-routing.announce" type="application/rss+xml" />">
17 
+
18 
+  # begin WML to generate css/js paths
19 
+  <ifneq "$(STYLESHEET)" "" "<link rel="stylesheet" type="text/css" href="$(DOCROOT)/$(STYLESHEET)" />">
20 
+  <ifeq "$(STYLESHEET)" "" "<link rel="stylesheet" type="text/css" href="$(DOCROOT)/css/master.css" />">
21 
+
22 
+  #<link href="css/master.css" rel="stylesheet" type="text/css" />
23 
+  <!--[if lte IE 7]>
24 
+  <link rel="stylesheet" type="text/css" href="$(DOCROOT)/css/ie7-and-down.css" />
25 
+  <![endif]-->
26 
+  <!--[if IE 6]>
27 
+  <link rel="stylesheet" type="text/css" href="$(DOCROOT)/css/ie6.css" />
28 
+  <![endif]-->
29 
+  <script language="javascript" type="text/javascript" src="$(DOCROOT)/global.js"></script>
30 
+  # end WML to generate css/js paths
31 
+
32 
+  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
33 
+  <meta name="author" content="" />
34 
+  <meta name="keywords" content="" />
35 
+  <meta name="description" content="" />
36 
+</head>
37 
+<body>
38 
+<div id="wrap">
39 
+  <div id="header">
40 
+    <h1 id="logo"><a href="<page home>">Tor</a></h1>
41 
+      # navigation menu generation
42 
+      <div id="nav">
43 
+        <ul>
44 
+        <:{
45 
+            # create a hash and maintain order of keys
46 
+            my %navigation;
47 
+            my @keys;
48 
+            while (@navigation) {
49 
+              my $key = shift @navigation;
50 
+              my $val = shift @navigation;
51 
+              push @keys, $key;
52 
+              $navigation{$key} = $val;
53 
+            }
54 
+
55 
+            my $page = $WML_SRC_BASENAME;
56 
+            my $lang = "$(LANG)";
57 
+
58 
+            for my $key (@keys) {
59 
+              my ($dir, $base) = $key =~ m,^(?:(.*)/)?(.*?)$,;
60 
+
61 
+              # in directory of active link, set class active
62 
+              my $class;
63 
+              if ((defined $dir) and ($WML_SRC_DIRNAME =~/$dir/) or ($WML_SRC_BASENAME eq $base)) {
64 
+                $class = 'class="active"';
65 
+              } else {
66 
+                $class = '';
67 
+              }
68 
+
69 
+	            $dir = '.' unless defined $dir;
70 
+
71 
+              # translated version
72 
+              if (-e "$(DOCROOT)/$dir/$lang/$base.wml") {
73 
+                  printf '<li><a '.$class.' href="%s">%s</a></li>'."\n",
74 
+                         stripDotSlashs("$(DOCROOT)/$dir/$base.html.$(LANG)"),$navigation{$key};
75 
+              }
76 
+              # english version
77 
+              elsif (-e "$(DOCROOT)/$dir/en/$base.wml") {
78 
+              	printf '<li><a '.$class.' href="%s">%s</a></li>'."\n",
79 
+                  stripDotSlashs("$(DOCROOT)/$dir/$base.html"), $navigation{$key};
80 
+              }
81 
+              # full url
82 
+              elsif ($key =~/^http/) {
83 
+                printf '<li><a href="%s">%s</a></li>'."\n", $key, $navigation{$key};
84 
+              } else {
85 
+                warn "$WML_SRC_FILENAME has a [page $key] (parses to docdir: $(DOCROOT)/; dir: $dir; base: $base -> $(DOCROOT)/$dir/$lang/$base.wml), but that doesn't exist.";
86 
+              }
87 
+            }
88 
+        }:>
89 
+        </ul>
90 
+      </div>
91 
+      <!-- END NAV -->
92 
+     # end navigation generation
93 
+      <div id="calltoaction">
94 
+        <ul>
95 
+          <:{
96 
+            my %calltoaction;
97 
+            my @keys;
98 
+            while (@calltoaction) {
99 
+              my $key = shift @calltoaction;
100 
+              my $val = shift @calltoaction;
101 
+              push @keys, $key;
102 
+              $calltoaction{$key} = $val;
103 
+            }
104 
+
105 
+            my $page = $WML_SRC_BASENAME;
106 
+            my $lang = "$(LANG)";
107 
+            for my $key (@keys) {
108 
+              my ($dir, $base) = $key =~ m,^(?:(.*)/)?(.*?)$,;
109 
+
110 
+              # in directory, set active
111 
+              my $class;
112 
+              if ((defined $dir) and ($WML_SRC_DIRNAME =~/$dir/) or ($WML_SRC_BASENAME eq $base)) {
113 
+              #if ($WML_SRC_BASENAME eq $base) {
114 
+                $class = 'class="active"';
115 
+              } else {
116 
+                $class = '';
117 
+              }
118 
+
119 
+	          $dir = '.' unless defined $dir;
120 
+              # try to use a translated version
121 
+              if (-e "$(DOCROOT)/$dir/$lang/$base.wml") {
122 
+                  printf '<li class="donate"><a '.$class.' href="%s">%s</a></li>'."\n",
123 
+                         stripDotSlashs("$(DOCROOT)/$dir/$base.html.$(LANG)"),$calltoaction{$key};
124 
+              }
125 
+              # default to english version
126 
+              elsif (-e "$(DOCROOT)/$dir/en/$base.wml") {
127 
+              	printf '<li class="donate"><a '.$class.' href="%s">%s</a></li>'."\n",
128 
+                  stripDotSlashs("$(DOCROOT)/$dir/$base.html"), $calltoaction{$key};
129 
+              } else {
130 
+                warn "$WML_SRC_FILENAME has a [page $key] (parses to docdir: $(DOCROOT)/; dir: $dir; base: $base -> $(DOCROOT)/$dir/$lang/$base.wml), but that doesn't exist.";
131 
+              }
132 
+            }
133 
+          }:>
134 
+        </ul>
135 
+      </div>
136 
+      <!-- END CALLTOACTION -->
137 
+  </div>
138 
+  <!-- END HEADER -->
139 
+
140 
+#<ifneq "$(REDIRECT)" "" "Redirecting to <a href="$(DOCROOT)/$(REDIRECT)">$(DOCROOT)/$(REDIRECT)</a>.">
141 
+#<ifneq "$(REDIRECT_GLOBAL)" "" "Redirecting to <a href="$(REDIRECT_GLOBAL)">$(REDIRECT_GLOBAL)</a>.">
include/info.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,9 @@
1 
+#!/usr/bin/env wml
2 
+<div class="img-shadow">
3 
+  <div class="infoblock">
4 
+    <h2 class="bulb">Tor Tip</h2>
5 
+    <p>If you take a step towards online privacy by downloading Tor, that’s great, but remember that Tor can only be effective if you use the programs it’s developed for!</p>
6 
+  </div>
7 
+  <!-- END INFOBLOCK -->
8 
+</div>
9 
+<!-- END IMG-SHADOW -->
include/links.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,52 @@
1 
+#!wml
2 
+
3 
+<define-tag gitblob whitespace=delete>http://gitweb.torproject.org/tor.git?a=blob_plain;hb=HEAD;f=</define-tag>
4 
+<define-tag gitblobstable whitespace=delete>http://gitweb.torproject.org/tor.git?a=blob_plain;hb=release-0.2.1;f=</define-tag>
5 
+<define-tag gittree whitespace=delete>http://gitweb.torproject.org/tor.git?a=tree;hb=HEAD;f=</define-tag>
6 
+<define-tag gitrepo whitespace=delete>http://gitweb.torproject.org/tor.git?a=tree;hb=HEAD</define-tag>
7 
+<define-tag svnwebsite whitespace=delete>https://svn.torproject.org/svn/website/trunk/</define-tag>
8 
+<define-tag svnprojects whitespace=delete>https://svn.torproject.org/svn/projects/</define-tag>
9 
+
10 
+#  Xinclude "locallinks.wmi"
11 
+#  Xinclude "langlocallinks.$(LANG).wmi"
12 
+
13 
+<:
14 
+	sub stripDotSlashs($) {
15 
+		my ($s) = @_;
16 
+		1 while ($s =~ s|/\./|/|);
17 
+		1 while ($s =~ s|^\./||);
18 
+		return $s;
19 
+	};
20 
+:>
21 
+
22 
+<:  sub pageToURL($$) {
23 
+ 	    my ($page, $lang) = @_;
24 
+	    my ($dir, $base) = $page =~ m,^(?:(.*)/)?(.*?)$,;
25 
+	    $dir = '.' unless defined $dir;
26 
+	    if (-e "$(DOCROOT)/$dir/$lang/$base.wml") {
27 
+	    	return stripDotSlashs("$(DOCROOT)/$dir/$base.html.$lang");
28 
+	    } elsif (-e "$(DOCROOT)/$dir/en/$base.wml") {
29 
+	    	return stripDotSlashs("$(DOCROOT)/$dir/$base.html");
30 
+        } elsif ($page =~ /^http/) {
31 
+          return $page;
32 
+	    } else {
33 
+	    	warn "$WML_SRC_FILENAME has a [page $page] (parses to docdir: $(DOCROOT)/; dir: $dir; base: $base -> $(DOCROOT)/$dir/$lang/$base.wml), but that doesn't exist.";
34 
+	    };
35 
+    }
36 
+:>
37 
+
38 
+<define-tag page whitespace=delete>
39 
+<:{
40 
+	my $page="%0";
41 
+	my $lang="$(LANG)";
42 
+	my ($dir, $base) = $page =~ m,^(?:(.*)/)?(.*?)$,;
43 
+	$dir = '.' unless defined $dir;
44 
+	if (-e "$(DOCROOT)/$dir/$lang/$base.wml") {
45 
+		print stripDotSlashs("$(DOCROOT)/$dir/$base.html.$lang");
46 
+	} elsif (-e "$(DOCROOT)/$dir/en/$base.wml") {
47 
+		print stripDotSlashs("$(DOCROOT)/$dir/$base.html");
48 
+	} else {
49 
+		warn "$WML_SRC_FILENAME has a [page $page] (parses to docdir: $(DOCROOT)/; dir: $dir; base: $base -> $(DOCROOT)/$dir/$lang/$base.wml), but that doesn't exist.";
50 
+	};
51 
+}:>
52 
+</define-tag>
include/mirrors-table.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,731 @@
1 
+
2 
+<tr>
3 
+
4 
+         <td>UK</td>
5 
+
6 
+         <td>tomyn</td>
7 
+
8 
+         <td>Up to date</td>
9 
+
10 
+    <td><a href="ftp://tor.tomyn.com">ftp</a></td>
11 
+    <td><a href="http://tor.tomyn.com/dist">http</a></td>
12 
+    <td><a href="http://tor.tomyn.com">http</a></td>
13 
+    <td><a href="https://tor.tomyn.com/dist">https</a></td>
14 
+    <td><a href="https://tor.tomyn.com">https</a></td>
15 
+    <td> - </td>
16 
+    <td> - </td>
17 
+</tr>
18 
+
19 
+<tr>
20 
+
21 
+         <td>EE</td>
22 
+
23 
+         <td>CyberSIDE</td>
24 
+
25 
+         <td>Up to date</td>
26 
+
27 
+    <td> - </td>
28 
+    <td><a href="http://freedos.pri.ee/tor/">http</a></td>
29 
+    <td><a href="http://cyberside.planet.ee/tor/">http</a></td>
30 
+    <td> - </td>
31 
+    <td> - </td>
32 
+    <td> - </td>
33 
+    <td> - </td>
34 
+</tr>
35 
+
36 
+<tr>
37 
+
38 
+         <td> </td>
39 
+
40 
+         <td> spacecowboy </td>
41 
+
42 
+         <td>Up to date</td>
43 
+
44 
+    <td> - </td>
45 
+    <td><a href="http://tor-proxy.de/tor-mirror/dist/">http</a></td>
46 
+    <td><a href="http://tor-proxy.de/tor-mirror/">http</a></td>
47 
+    <td><a href="https://tor-proxy.de/tor-mirror/dist/">https</a></td>
48 
+    <td><a href="https://tor-proxy.de/tor-mirror/">https</a></td>
49 
+    <td> - </td>
50 
+    <td> - </td>
51 
+</tr>
52 
+
53 
+<tr>
54 
+
55 
+         <td>US</td>
56 
+
57 
+         <td>BarkerJr</td>
58 
+
59 
+         <td>Up to date</td>
60 
+
61 
+    <td> - </td>
62 
+    <td><a href="http://www.torproject.us/dist/">http</a></td>
63 
+    <td><a href="http://www.torproject.us/">http</a></td>
64 
+    <td><a href="https://www.torproject.us/dist/">https</a></td>
65 
+    <td><a href="https://www.torproject.us/">https</a></td>
66 
+    <td> - </td>
67 
+    <td><a href="rsync://rsync.torproject.us/tor">rsync</a></td>
68 
+</tr>
69 
+
70 
+<tr>
71 
+
72 
+         <td>US</td>
73 
+
74 
+         <td>TheOnionRouter</td>
75 
+
76 
+         <td>Up to date</td>
77 
+
78 
+    <td> - </td>
79 
+    <td><a href="http://www.theonionrouter.com/dist/">http</a></td>
80 
+    <td><a href="http://www.theonionrouter.com/">http</a></td>
81 
+    <td> - </td>
82 
+    <td> - </td>
83 
+    <td> - </td>
84 
+    <td> - </td>
85 
+</tr>
86 
+
87 
+<tr>
88 
+
89 
+         <td>DE</td>
90 
+
91 
+         <td>beme it</td>
92 
+
93 
+         <td>Up to date</td>
94 
+
95 
+    <td> - </td>
96 
+    <td><a href="http://tor.beme-it.de/dist/">http</a></td>
97 
+    <td><a href="http://tor.beme-it.de/">http</a></td>
98 
+    <td> - </td>
99 
+    <td> - </td>
100 
+    <td> - </td>
101 
+    <td><a href="rsync://tor.beme-it.de/tor">rsync</a></td>
102 
+</tr>
103 
+
104 
+<tr>
105 
+
106 
+         <td>AT</td>
107 
+
108 
+         <td></td>
109 
+
110 
+         <td>Up to date</td>
111 
+
112 
+    <td> - </td>
113 
+    <td><a href="http://tor.idnr.at/dist/">http</a></td>
114 
+    <td><a href="http://tor.idnr.at/">http</a></td>
115 
+    <td> - </td>
116 
+    <td> - </td>
117 
+    <td> - </td>
118 
+    <td> - </td>
119 
+</tr>
120 
+
121 
+<tr>
122 
+
123 
+         <td>NL</td>
124 
+
125 
+         <td>CCC</td>
126 
+
127 
+         <td>Up to date</td>
128 
+
129 
+    <td> - </td>
130 
+    <td><a href="http://tor.ccc.de/dist/">http</a></td>
131 
+    <td><a href="http://tor.ccc.de/">http</a></td>
132 
+    <td> - </td>
133 
+    <td> - </td>
134 
+    <td> - </td>
135 
+    <td> - </td>
136 
+</tr>
137 
+
138 
+<tr>
139 
+
140 
+         <td>RU</td>
141 
+
142 
+         <td></td>
143 
+
144 
+         <td>Up to date</td>
145 
+
146 
+    <td> - </td>
147 
+    <td><a href="http://www.tor.myeveryday.ru/dist/">http</a></td>
148 
+    <td><a href="http://www.tor.myeveryday.ru/">http</a></td>
149 
+    <td> - </td>
150 
+    <td> - </td>
151 
+    <td> - </td>
152 
+    <td> - </td>
153 
+</tr>
154 
+
155 
+<tr>
156 
+
157 
+         <td>FR</td>
158 
+
159 
+         <td>BarkerJr</td>
160 
+
161 
+         <td>Up to date</td>
162 
+
163 
+    <td> - </td>
164 
+    <td><a href="http://www.oignon.net/dist/">http</a></td>
165 
+    <td><a href="http://www.oignon.net/">http</a></td>
166 
+    <td><a href="https://oignon.net/dist/">https</a></td>
167 
+    <td><a href="https://oignon.net/">https</a></td>
168 
+    <td> - </td>
169 
+    <td> - </td>
170 
+</tr>
171 
+
172 
+<tr>
173 
+
174 
+         <td>DK</td>
175 
+
176 
+         <td>Zentrum der Gesundheit</td>
177 
+
178 
+         <td>Up to date</td>
179 
+
180 
+    <td> - </td>
181 
+    <td><a href="http://tor.idnr.ws/dist/">http</a></td>
182 
+    <td><a href="http://tor.idnr.ws/">http</a></td>
183 
+    <td> - </td>
184 
+    <td> - </td>
185 
+    <td> - </td>
186 
+    <td> - </td>
187 
+</tr>
188 
+
189 
+<tr>
190 
+
191 
+         <td>US</td>
192 
+
193 
+         <td>AskApache</td>
194 
+
195 
+         <td>Up to date</td>
196 
+
197 
+    <td> - </td>
198 
+    <td><a href="http://tor.askapache.com/dist/">http</a></td>
199 
+    <td><a href="http://tor.askapache.com/">http</a></td>
200 
+    <td> - </td>
201 
+    <td> - </td>
202 
+    <td> - </td>
203 
+    <td> - </td>
204 
+</tr>
205 
+
206 
+<tr>
207 
+
208 
+         <td>DE</td>
209 
+
210 
+         <td>chaos darmstadt</td>
211 
+
212 
+         <td>Up to date</td>
213 
+
214 
+    <td> - </td>
215 
+    <td><a href="http://mirrors.chaos-darmstadt.de/tor-mirror/dist/">http</a></td>
216 
+    <td><a href="http://mirrors.chaos-darmstadt.de/tor-mirror/">http</a></td>
217 
+    <td> - </td>
218 
+    <td> - </td>
219 
+    <td> - </td>
220 
+    <td> - </td>
221 
+</tr>
222 
+
223 
+<tr>
224 
+
225 
+         <td>SE</td>
226 
+
227 
+         <td></td>
228 
+
229 
+         <td>Up to date</td>
230 
+
231 
+    <td> - </td>
232 
+    <td><a href="http://tor.homosu.net/dist">http</a></td>
233 
+    <td><a href="http://tor.homosu.net/">http</a></td>
234 
+    <td> - </td>
235 
+    <td> - </td>
236 
+    <td> - </td>
237 
+    <td> - </td>
238 
+</tr>
239 
+
240 
+<tr>
241 
+
242 
+         <td>HU</td>
243 
+
244 
+         <td>NIIF Institute</td>
245 
+
246 
+         <td>Up to date</td>
247 
+
248 
+    <td> - </td>
249 
+    <td><a href="http://trak.tor.hu/dist/">http</a></td>
250 
+    <td><a href="http://trak.tor.hu/">http</a></td>
251 
+    <td> - </td>
252 
+    <td> - </td>
253 
+    <td> - </td>
254 
+    <td> - </td>
255 
+</tr>
256 
+
257 
+<tr>
258 
+
259 
+         <td>HU</td>
260 
+
261 
+         <td>Unknown</td>
262 
+
263 
+         <td>Up to date</td>
264 
+
265 
+    <td> - </td>
266 
+    <td> - </td>
267 
+    <td><a href="http://tor.hu/">http</a></td>
268 
+    <td> - </td>
269 
+    <td> - </td>
270 
+    <td> - </td>
271 
+    <td> - </td>
272 
+</tr>
273 
+
274 
+<tr>
275 
+
276 
+         <td>IR</td>
277 
+
278 
+         <td>Access</td>
279 
+
280 
+         <td>Up to date</td>
281 
+
282 
+    <td> - </td>
283 
+    <td><a href="http://irani-tor.ath.cx/dist/">http</a></td>
284 
+    <td><a href="http://irani-tor.ath.cx/">http</a></td>
285 
+    <td> - </td>
286 
+    <td> - </td>
287 
+    <td> - </td>
288 
+    <td> - </td>
289 
+</tr>
290 
+
291 
+<tr>
292 
+
293 
+         <td>CN</td>
294 
+
295 
+         <td>zuola</td>
296 
+
297 
+         <td>Out of date</td>
298 
+
299 
+    <td> - </td>
300 
+    <td><a href="http://tor.zuo.la/dist/">http</a></td>
301 
+    <td><a href="http://tor.zuo.la/">http</a></td>
302 
+    <td> - </td>
303 
+    <td> - </td>
304 
+    <td> - </td>
305 
+    <td> - </td>
306 
+</tr>
307 
+
308 
+<tr>
309 
+
310 
+         <td>CN</td>
311 
+
312 
+         <td>shizhao</td>
313 
+
314 
+         <td>Out of date</td>
315 
+
316 
+    <td> - </td>
317 
+    <td><a href="http://tor.shizhao.org/dist/">http</a></td>
318 
+    <td><a href="http://tor.shizhao.org/">http</a></td>
319 
+    <td> - </td>
320 
+    <td> - </td>
321 
+    <td> - </td>
322 
+    <td> - </td>
323 
+</tr>
324 
+
325 
+<tr>
326 
+
327 
+         <td>CN</td>
328 
+
329 
+         <td>bullog</td>
330 
+
331 
+         <td>Out of date</td>
332 
+
333 
+    <td> - </td>
334 
+    <td><a href="http://tor.bullog.org/dist/">http</a></td>
335 
+    <td><a href="http://tor.bullog.org/">http</a></td>
336 
+    <td> - </td>
337 
+    <td> - </td>
338 
+    <td> - </td>
339 
+    <td> - </td>
340 
+</tr>
341 
+
342 
+<tr>
343 
+
344 
+         <td>CN</td>
345 
+
346 
+         <td>ranyunfei</td>
347 
+
348 
+         <td>Out of date</td>
349 
+
350 
+    <td> - </td>
351 
+    <td><a href="http://tor.ranyunfei.com/dist/">http</a></td>
352 
+    <td><a href="http://tor.ranyunfei.com/">http</a></td>
353 
+    <td> - </td>
354 
+    <td> - </td>
355 
+    <td> - </td>
356 
+    <td> - </td>
357 
+</tr>
358 
+
359 
+<tr>
360 
+
361 
+         <td>NL</td>
362 
+
363 
+         <td>Amorphis</td>
364 
+
365 
+         <td>Out of date</td>
366 
+
367 
+    <td> - </td>
368 
+    <td><a href="http://tor.amorphis.eu/dist/">http</a></td>
369 
+    <td><a href="http://tor.amorphis.eu/">http</a></td>
370 
+    <td> - </td>
371 
+    <td> - </td>
372 
+    <td> - </td>
373 
+    <td> - </td>
374 
+</tr>
375 
+
376 
+<tr>
377 
+
378 
+         <td>CN</td>
379 
+
380 
+         <td>wuerkaixi</td>
381 
+
382 
+         <td>Out of date</td>
383 
+
384 
+    <td> - </td>
385 
+    <td><a href="http://tor.wuerkaixi.com/dist/">http</a></td>
386 
+    <td><a href="http://tor.wuerkaixi.com/">http</a></td>
387 
+    <td> - </td>
388 
+    <td> - </td>
389 
+    <td> - </td>
390 
+    <td> - </td>
391 
+</tr>
392 
+
393 
+<tr>
394 
+
395 
+         <td> </td>
396 
+
397 
+         <td> cybervalley </td>
398 
+
399 
+         <td>Out of date</td>
400 
+
401 
+    <td> - </td>
402 
+    <td> - </td>
403 
+    <td><a href="http://torproject.cybervalley.org/">http</a></td>
404 
+    <td> - </td>
405 
+    <td> - </td>
406 
+    <td> - </td>
407 
+    <td> - </td>
408 
+</tr>
409 
+
410 
+<tr>
411 
+
412 
+         <td>CA</td>
413 
+
414 
+         <td>Hermetix</td>
415 
+
416 
+         <td>Out of date</td>
417 
+
418 
+    <td> - </td>
419 
+    <td> - </td>
420 
+    <td><a href="http://tor.hermetix.org/">http</a></td>
421 
+    <td> - </td>
422 
+    <td> - </td>
423 
+    <td> - </td>
424 
+    <td> - </td>
425 
+</tr>
426 
+
427 
+<tr>
428 
+
429 
+         <td>DE</td>
430 
+
431 
+         <td>Bbs</td>
432 
+
433 
+         <td>Out of date</td>
434 
+
435 
+    <td> - </td>
436 
+    <td> - </td>
437 
+    <td><a href="http://tor.blingblingsquad.net/">http</a></td>
438 
+    <td> - </td>
439 
+    <td> - </td>
440 
+    <td> - </td>
441 
+    <td> - </td>
442 
+</tr>
443 
+
444 
+<tr>
445 
+
446 
+         <td>DE</td>
447 
+
448 
+         <td>Spline</td>
449 
+
450 
+         <td>Unknown</td>
451 
+
452 
+    <td> - </td>
453 
+    <td><a href="http://rem.spline.de/tor/">http</a></td>
454 
+    <td> - </td>
455 
+    <td> - </td>
456 
+    <td> - </td>
457 
+    <td> - </td>
458 
+    <td> - </td>
459 
+</tr>
460 
+
461 
+<tr>
462 
+
463 
+         <td>US</td>
464 
+
465 
+         <td>Xpdm</td>
466 
+
467 
+         <td>Unknown</td>
468 
+
469 
+    <td> - </td>
470 
+    <td><a href="http://torproj.xpdm.us/dist/">http</a></td>
471 
+    <td><a href="http://torproj.xpdm.us/">http</a></td>
472 
+    <td><a href="https://torproj.xpdm.us/dist/">https</a></td>
473 
+    <td><a href="https://torproj.xpdm.us/">https</a></td>
474 
+    <td> - </td>
475 
+    <td> - </td>
476 
+</tr>
477 
+
478 
+<tr>
479 
+
480 
+         <td>DE</td>
481 
+
482 
+         <td>Cybermirror</td>
483 
+
484 
+         <td>Unknown</td>
485 
+
486 
+    <td> - </td>
487 
+    <td><a href="http://tor.cybermirror.org/dist/">http</a></td>
488 
+    <td><a href="http://tor.cybermirror.org/">http</a></td>
489 
+    <td> - </td>
490 
+    <td> - </td>
491 
+    <td> - </td>
492 
+    <td> - </td>
493 
+</tr>
494 
+
495 
+<tr>
496 
+
497 
+         <td>AU</td>
498 
+
499 
+         <td>Wiretapped</td>
500 
+
501 
+         <td>Unknown</td>
502 
+
503 
+    <td><a href="ftp://ftp.mirrors.wiretapped.net/pub/security/cryptography/network/tor/">ftp</a></td>
504 
+    <td><a href="http://www.mirrors.wiretapped.net/security/cryptography/network/tor/">http</a></td>
505 
+    <td> - </td>
506 
+    <td> - </td>
507 
+    <td> - </td>
508 
+    <td> - </td>
509 
+    <td> - </td>
510 
+</tr>
511 
+
512 
+<tr>
513 
+
514 
+         <td>US</td>
515 
+
516 
+         <td>I'm on the roof</td>
517 
+
518 
+         <td>Unknown</td>
519 
+
520 
+    <td> - </td>
521 
+    <td><a href="http://mirror.imontheroof.com/tor-mirror/dist/">http</a></td>
522 
+    <td><a href="http://mirror.imontheroof.com/tor-mirror/">http</a></td>
523 
+    <td> - </td>
524 
+    <td> - </td>
525 
+    <td> - </td>
526 
+    <td> - </td>
527 
+</tr>
528 
+
529 
+<tr>
530 
+
531 
+         <td>CH</td>
532 
+
533 
+         <td>Sixx</td>
534 
+
535 
+         <td>Unknown</td>
536 
+
537 
+    <td> - </td>
538 
+    <td><a href="http://tor.sixxs.net/dist/">http</a></td>
539 
+    <td><a href="http://tor.sixxs.net/">http</a></td>
540 
+    <td> - </td>
541 
+    <td> - </td>
542 
+    <td> - </td>
543 
+    <td> - </td>
544 
+</tr>
545 
+
546 
+<tr>
547 
+
548 
+         <td>CH</td>
549 
+
550 
+         <td>Unfix</td>
551 
+
552 
+         <td>Unknown</td>
553 
+
554 
+    <td> - </td>
555 
+    <td><a href="http://tor.unfix.org/dist/">http</a></td>
556 
+    <td><a href="http://tor.unfix.org/">http</a></td>
557 
+    <td> - </td>
558 
+    <td> - </td>
559 
+    <td> - </td>
560 
+    <td> - </td>
561 
+</tr>
562 
+
563 
+<tr>
564 
+
565 
+         <td>IN</td>
566 
+
567 
+         <td></td>
568 
+
569 
+         <td>Unknown</td>
570 
+
571 
+    <td> - </td>
572 
+    <td><a href="http://www.torproject.org.in/dist/">http</a></td>
573 
+    <td><a href="http://www.torproject.org.in/">http</a></td>
574 
+    <td> - </td>
575 
+    <td> - </td>
576 
+    <td> - </td>
577 
+    <td> - </td>
578 
+</tr>
579 
+
580 
+<tr>
581 
+
582 
+         <td>FR</td>
583 
+
584 
+         <td>CRAN</td>
585 
+
586 
+         <td>Unknown</td>
587 
+
588 
+    <td><a href="ftp://miroir-francais.fr/pub/tor/">ftp</a></td>
589 
+    <td><a href="http://tor.miroir-francais.fr/">http</a></td>
590 
+    <td> - </td>
591 
+    <td> - </td>
592 
+    <td> - </td>
593 
+    <td> - </td>
594 
+    <td><a href="rsync://miroir-francais.fr::tor">rsync</a></td>
595 
+</tr>
596 
+
597 
+<tr>
598 
+
599 
+         <td>NO</td>
600 
+
601 
+         <td>Meulie</td>
602 
+
603 
+         <td>Unknown</td>
604 
+
605 
+    <td> - </td>
606 
+    <td><a href="http://tor.meulie.net/">http</a></td>
607 
+    <td> - </td>
608 
+    <td> - </td>
609 
+    <td> - </td>
610 
+    <td> - </td>
611 
+    <td> - </td>
612 
+</tr>
613 
+
614 
+<tr>
615 
+
616 
+         <td>NL</td>
617 
+
618 
+         <td>Kamagurka</td>
619 
+
620 
+         <td>Unknown</td>
621 
+
622 
+    <td> - </td>
623 
+    <td><a href="http://tor.kamagurka.org/dist/">http</a></td>
624 
+    <td><a href="http://tor.kamagurka.org/">http</a></td>
625 
+    <td> - </td>
626 
+    <td> - </td>
627 
+    <td> - </td>
628 
+    <td> - </td>
629 
+</tr>
630 
+
631 
+<tr>
632 
+
633 
+         <td>HU</td>
634 
+
635 
+         <td>ax</td>
636 
+
637 
+         <td>Unknown</td>
638 
+
639 
+    <td> - </td>
640 
+    <td><a href="http://tor.initrd.net/dist/">http</a></td>
641 
+    <td> - </td>
642 
+    <td> - </td>
643 
+    <td> - </td>
644 
+    <td> - </td>
645 
+    <td> - </td>
646 
+</tr>
647 
+
648 
+<tr>
649 
+
650 
+         <td>NL</td>
651 
+
652 
+         <td>BIT BV</td>
653 
+
654 
+         <td>Unknown</td>
655 
+
656 
+    <td><a href="ftp://ftp.bit.nl/mirror/tor/">ftp</a></td>
657 
+    <td><a href="http://ftp.bit.nl/mirror/tor/">http</a></td>
658 
+    <td> - </td>
659 
+    <td> - </td>
660 
+    <td> - </td>
661 
+    <td> - </td>
662 
+    <td> - </td>
663 
+</tr>
664 
+
665 
+<tr>
666 
+
667 
+         <td>UK</td>
668 
+
669 
+         <td>Ghirai</td>
670 
+
671 
+         <td>Unknown</td>
672 
+
673 
+    <td> - </td>
674 
+    <td><a href="http://www.ghirai.com/tor/">http</a></td>
675 
+    <td> - </td>
676 
+    <td> - </td>
677 
+    <td> - </td>
678 
+    <td> - </td>
679 
+    <td> - </td>
680 
+</tr>
681 
+
682 
+<tr>
683 
+
684 
+         <td>UA</td>
685 
+
686 
+         <td>Technica-03</td>
687 
+
688 
+         <td>Unknown</td>
689 
+
690 
+    <td> - </td>
691 
+    <td><a href="http://tordistua.reactor-xg.kiev.ua/">http</a></td>
692 
+    <td><a href="http://torua.reactor-xg.kiev.ua/">http</a></td>
693 
+    <td> - </td>
694 
+    <td> - </td>
695 
+    <td> - </td>
696 
+    <td> - </td>
697 
+</tr>
698 
+
699 
+<tr>
700 
+
701 
+         <td></td>
702 
+
703 
+         <td>StrangeCharm</td>
704 
+
705 
+         <td>Unknown</td>
706 
+
707 
+    <td> - </td>
708 
+    <td><a href="http://torproject.the-onion-router.net/dist/">http</a></td>
709 
+    <td><a href="http://torproject.the-onion-router.net/">http</a></td>
710 
+    <td> - </td>
711 
+    <td> - </td>
712 
+    <td> - </td>
713 
+    <td> - </td>
714 
+</tr>
715 
+
716 
+<tr>
717 
+
718 
+         <td>CH</td>
719 
+
720 
+         <td>Boinc</td>
721 
+
722 
+         <td>Unknown</td>
723 
+
724 
+    <td> - </td>
725 
+    <td><a href="http://tor.boinc.ch/dist/">http</a></td>
726 
+    <td><a href="http://tor.boinc.ch/">http</a></td>
727 
+    <td> - </td>
728 
+    <td> - </td>
729 
+    <td> - </td>
730 
+    <td> - </td>
731 
+</tr>
include/navigation.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,24 @@
1 
+#!/usr/bin/wml
2 
+
3 
+## translation metadata
4 
+# Revision: $Revision: 22069 $
5 
+# Translation-Priority: 1-high
6 
+
7 
+<:
8 
+    # path                              link text
9 
+    my @navigation = (
10 
+        'home'                        , 'Home',
11 
+        'about/about'                 , 'About Tor',
12 
+        'docs/documentation'          , 'Documentation',
13 
+        'projects/projects'           , 'Projects',
14 
+        'press/press'                 , 'Press',
15 
+        'https://blog.torproject.org' , 'Blog',
16 
+        'http://printfection.com/torprojectstore' , 'Store',
17 
+    );
18 
+    my @calltoaction = (
19 
+        'download/download'                , 'Download',
20 
+        'donate/donate'                    , 'Donate',
21 
+        'getinvolved/getinvolved'          , 'Get Involved',
22 
+    );
23 
+
24 
+:>
include/perl-globals.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,40 @@
1 
+#!wml
2 
+<:
3 
+	# Change both.  The array is ordered (for pages like translation status, order of flags, etc).
4 
+
5 
+	my @LANGUAGES = qw{ar bms de en es et fa fi fr it ja ko nl no pl pt ru se tr zh-cn};
6 
+	my %LANGUAGES = (
7 
+		'ar' => "&#1593;&#1585;&#1576;&#1610;&#1577;&nbsp;(Arabiya)",
8 
+		'bms' => "Burmese",
9 
+		'de' => "Deutsch",
10 
+		'en' => "English",
11 
+		'es' => "espa&ntilde;ol",
12 
+		'et' => "Estonian",
13 
+		'fa' => "&#1601;&#1575;&#1585;&#1587;&#1740; (F&#257;rs&#299;)",
14 
+		'fi' => "suomi",
15 
+		'fr' => "fran&ccedil;ais",
16 
+		'it' => "Italiano",
17 
+		'ja' => "&#26085;&#26412;&#35486;&nbsp;(Nihongo)",
18 
+		'ko' => "&#54620;&#44397;&#50612;&nbsp;(Hangul)",
19 
+		'nl' => "Nederlands",
20 
+		'no' => "norsk",
21 
+		'pl' => "polski",
22 
+		'pt' => "Portugu&ecirc;s",
23 
+		'ru' => "&#1056;&#1091;&#1089;&#1089;&#1082;&#1080;&#1081;&nbsp;(Russkij)",
24 
+		'se' => "svenska",
25 
+		'tr' => "T&uuml;rk&ccedil;e",
26 
+		'zh-cn' => "&#20013;&#25991;(&#31616;) (Simplified Chinese)",
27 
+
28 
+		);
29 
+	our $WML_SRC_FILENAME;
30 
+	our $WML_SRC_BASENAME;
31 
+	our $WML_SRC_DIRNAME;
32 
+
33 
+	# sanity check.
34 
+	for my $lang (@LANGUAGES) {
35 
+		die "Language $lang defined in \@LANGUAGES but not in \%LANGUAGES in perl-globals"
36 
+			unless exists $LANGUAGES{$lang};
37 
+	};
38 
+	die "\@LANGUAGES and \%LANGUAGES have a different number of elements in perl-globals"
39 
+		unless (scalar @LANGUAGES == scalar keys %LANGUAGES);
40 
+:>
include/side.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,91 @@
1 
+#! /usr/bin/wml
2 
+<: use strict; :>
3 
+<: use warnings; :>
4 
+#use "perl-globals.wmi"
5 
+#use "links.wmi"
6 
+#use "versions.wmi"
7 
+#use "sidenav.wmi"
8 
+<div class="img-shadow">
9 
+  <div id="sidenav">
10 
+    <:
11 
+      # recursively search menu structure to see if it contains a given page
12 
+      sub containsSub($$);
13 
+      sub containsSub($$) {
14 
+          my ($elements, $page) = @_;
15 
+          for my $ele (@{$elements}) {
16 
+              if (containsSub($ele->{'subelements'},$page)){
17 
+                  return 1;
18 
+              } elsif ($page eq $ele->{'url'}) {
19 
+                  return 1;
20 
+              }
21 
+
22 
+          }
23 
+          return 0;
24 
+      }
25 
+
26 
+      # generate navigation menu
27 
+      sub printNavMenu($$$);
28 
+      sub printNavMenu($$$) {
29 
+          my ($navmenu, $page, $lang) = @_;
30 
+          print '<ul>'."\n";
31 
+          for my $navmenu (@{$navmenu}) {
32 
+              # this menu entry is the current (active) page
33 
+              if ($navmenu->{'url'} eq $page) {
34 
+
35 
+                  # the current page has nested menu elements
36 
+                  if ($navmenu->{'subelements'}) { # menu has dropdown
37 
+                      printf '<li class="dropdown active"><a class="active" href="%s">%s</a></li>'."\n",
38 
+                             pageToURL($navmenu->{'url'}, $lang), $navmenu->{'txt'};
39 
+
40 
+                      print '<li>'."\n";
41 
+                      printNavMenu($navmenu->{'subelements'},$page,$lang);
42 
+                      print '</li>'."\n";
43 
+
44 
+                  # the current (active) page does not have sub elements
45 
+                  } else {
46 
+                      printf '<li class="active"><a class="active" href="%s">%s</a></li>'."\n",
47 
+                             pageToURL($navmenu->{'url'}, $lang), $navmenu->{'txt'};
48 
+                  }
49 
+
50 
+              # a subelement of this menu item is the current (active) page
51 
+              } elsif (containsSub($navmenu->{'subelements'}, $page)) {
52 
+                  printf '<li class="dropdown"><a class="active" href="%s">%s</a></li>'."\n",
53 
+                         pageToURL($navmenu->{'url'}, $lang), $navmenu->{'txt'};
54 
+
55 
+                  print '<li>'."\n"; #encapsulate subelements
56 
+                  # recurse to generate the expanded menu
57 
+                  printNavMenu($navmenu->{'subelements'},$page,$lang);
58 
+                  print '</li>'."\n"; #encapsulate subelements
59 
+
60 
+              # the menu entry is not active and does not enclose the active page
61 
+              } else {
62 
+
63 
+                  # if there are subelements, set collapsed style
64 
+                  if ($navmenu->{'subelements'}) {
65 
+                      printf '<li class="dropdown"><a href="%s">%s</a></li>'."\n",
66 
+                             pageToURL($navmenu->{'url'}, $lang), $navmenu->{'txt'};
67 
+                  # regular menu entry
68 
+                  } else {
69 
+                      printf '<li><a href="%s">%s</a></li>'."\n",
70 
+                             pageToURL($navmenu->{'url'}, $lang), $navmenu->{'txt'};
71 
+                  }
72 
+              }
73 
+          }
74 
+          print '</ul>'."\n";
75 
+      }
76 
+
77 
+      my $lang = "$(LANG)";
78 
+
79 
+      use Cwd;
80 
+      use Cwd 'abs_path';
81 
+      use File::Spec;
82 
+
83 
+      # get document path from site root
84 
+      my $path = File::Spec->abs2rel(getcwd(),abs_path("$(DOCROOT)"));
85 
+      my $page = $WML_SRC_BASENAME;
86 
+      printNavMenu($sidenav, $path.'/'.$page, $lang);
87 
+    :>
88 
+  </div>
89 
+  <!-- END SIDENAV -->
90 
+</div>
91 
+<!-- END IMG-SHADOW -->
include/versions.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,96 @@
1 
+<define-tag version-stable whitespace=delete>0.2.1.26</define-tag>
2 
+<define-tag version-alpha whitespace=delete>0.2.2.13-alpha</define-tag>
3 
+
4 
+<define-tag version-win32-stable whitespace=delete>0.2.1.26</define-tag>
5 
+<define-tag version-win32-alpha whitespace=delete>0.2.2.13-alpha</define-tag>
6 
+
7 
+<define-tag version-win32-bundle-stable whitespace=delete>0.2.1.26</define-tag>
8 
+<define-tag version-win32-bundle-alpha whitespace=delete>0.2.2.13-alpha</define-tag>
9 
+
10 
+<define-tag version-osx-bundle-stable whitespace=delete>0.2.1.26</define-tag>
11 
+<define-tag version-osx-bundle-alpha whitespace=delete>0.2.2.13-alpha</define-tag>
12 
+
13 
+<define-tag version-oldosx-bundle-stable whitespace=delete>0.2.1.26</define-tag>
14 
+<define-tag version-oldosx-bundle-alpha whitespace=delete>0.2.2.13-alpha</define-tag>
15 
+
16 
+<define-tag version-osx-stable whitespace=delete>0.2.1.26</define-tag>
17 
+<define-tag version-osx-alpha whitespace=delete>0.2.2.13-alpha</define-tag>
18 
+
19 
+<define-tag version-oldosx-stable whitespace=delete>0.2.1.26</define-tag>
20 
+<define-tag version-oldosx-alpha whitespace=delete>0.2.2.13-alpha</define-tag>
21 
+
22 
+<define-tag version-torbrowserbundle whitespace=delete>1.3.6</define-tag>
23 
+<define-tag version-torbrowser-tor whitespace=delete>0.2.1.26</define-tag>
24 
+<define-tag version-torbrowser-tor-components whitespace=delete>libevent-1.4.13, zlib-1.2.3, openssl-0.9.8l</define-tag>
25 
+<define-tag version-torbrowser-firefox whitespace=delete>3.5.9</define-tag>
26 
+<define-tag version-torbrowser-torbutton whitespace=delete>1.2.5</define-tag>
27 
+<define-tag version-torbrowser-polipo whitespace=delete>1.0.4.1</define-tag>
28 
+<define-tag version-torbrowser-pidgin whitespace=delete>2.6.6</define-tag>
29 
+<define-tag version-torbrowser-otr whitespace=delete>3.2</define-tag>
30 
+<define-tag version-torbrowser-vidalia whitespace=delete>0.2.9</define-tag>
31 
+<define-tag version-torimbrowserbundle whitespace=delete>1.3.6</define-tag>
32 
+
33 
+<define-tag version-torbrowserbundlelinux whitespace=delete>1.0.7</define-tag>
34 
+<define-tag version-gnu-torbrowser-tor whitespace=delete>0.2.2.13-alpha</define-tag>
35 
+<define-tag version-gnu-torbrowser-tor-components whitespace=delete>libevent-1.4.13, zlib-1.2.3, openssl-0.9.8l</define-tag>
36 
+<define-tag version-gnu-torbrowser-firefox whitespace=delete>3.5.8</define-tag>
37 
+<define-tag version-gnu-torbrowser-torbutton whitespace=delete>1.2.5</define-tag>
38 
+<define-tag version-gnu-torbrowser-polipo whitespace=delete>1.0.4.1</define-tag>
39 
+<define-tag version-gnu-torbrowser-vidalia whitespace=delete>0.2.9</define-tag>
40 
+
41 
+<define-tag version-androidbundle-tor whitespace=delete>0.2.2.13-alpha</define-tag>
42 
+<define-tag version-androidbundle-orbot whitespace=delete>0.0.7</define-tag>
43 
+<define-tag version-androidbundle-privoxy whitespace=delete>privoxy-3.0.12-stable</define-tag>
44 
+<define-tag version-androidbundle-libevent whitespace=delete>libevent-1.4.12-stable</define-tag>
45 
+<define-tag package-androidbundle-alpha whitespace=delete>dist/android/<version-androidbundle-tor>-orbot-<version-androidbundle-orbot>.apk</define-tag>
46 
+<define-tag package-androidbundle-alpha-sig whitespace=delete><package-androidbundle-alpha>.asc</define-tag>
47 
+
48 
+<define-tag package-win32-stable whitespace=delete>dist/win32/tor-<version-win32-stable>-win32.exe</define-tag>
49 
+<define-tag package-win32-alpha whitespace=delete>dist/win32/tor-<version-win32-alpha>-win32.exe</define-tag>
50 
+
51 
+<define-tag local-win32-bundle-stable whitespace=delete>dist/vidalia-bundles/vidalia-bundle-<version-win32-bundle-stable>-0.2.9.exe</define-tag>
52 
+<define-tag local-win32-bundle-alpha whitespace=delete>dist/vidalia-bundles/vidalia-bundle-<version-win32-bundle-alpha>-0.2.9.exe</define-tag>
53 
+<define-tag package-win32-bundle-stable whitespace=delete><local-win32-bundle-stable></define-tag>
54 
+<define-tag package-win32-bundle-alpha whitespace=delete><local-win32-bundle-alpha></define-tag>
55 
+
56 
+<define-tag package-osx-bundle-stable whitespace=delete>dist/vidalia-bundles/vidalia-bundle-<version-osx-bundle-stable>-0.2.9-i386.dmg</define-tag>
57 
+<define-tag package-osx-bundle-alpha whitespace=delete>dist/vidalia-bundles/vidalia-bundle-<version-osx-bundle-alpha>-0.2.9-i386.dmg</define-tag>
58 
+
59 
+<define-tag package-oldosx-bundle-stable whitespace=delete>dist/vidalia-bundles/vidalia-bundle-<version-oldosx-bundle-stable>-0.2.8-ppc.dmg</define-tag>
60 
+<define-tag package-oldosx-bundle-alpha whitespace=delete>dist/vidalia-bundles/vidalia-bundle-<version-oldosx-bundle-alpha>-0.2.8-ppc.dmg</define-tag>
61 
+
62 
+<define-tag package-osx-stable whitespace=delete>dist/osx/Tor-<version-osx-stable>-i386-Bundle.dmg</define-tag>
63 
+<define-tag package-osx-alpha whitespace=delete>dist/osx/Tor-<version-osx-alpha>-i386-Bundle.dmg</define-tag>
64 
+
65 
+<define-tag package-oldosx-stable whitespace=delete>dist/osx-old/Tor-<version-oldosx-stable>-ppc-Bundle.dmg</define-tag>
66 
+<define-tag package-oldosx-alpha whitespace=delete>dist/osx-old/Tor-<version-oldosx-alpha>-ppc-Bundle.dmg</define-tag>
67 
+
68 
+<define-tag package-source-stable whitespace=delete>dist/tor-<version-stable>.tar.gz</define-tag>
69 
+<define-tag package-source-alpha whitespace=delete>dist/tor-<version-alpha>.tar.gz</define-tag>
70 
+
71 
+<define-tag package-win32-stable-sig whitespace=delete><package-win32-stable>.asc</define-tag>
72 
+<define-tag package-win32-alpha-sig whitespace=delete><package-win32-alpha>.asc</define-tag>
73 
+
74 
+<define-tag package-win32-bundle-stable-sig whitespace=delete><package-win32-bundle-stable>.asc</define-tag>
75 
+<define-tag package-win32-bundle-alpha-sig whitespace=delete><package-win32-bundle-alpha>.asc</define-tag>
76 
+
77 
+<define-tag local-win32-bundle-stable-sig whitespace=delete><local-win32-bundle-stable>.asc</define-tag>
78 
+<define-tag local-win32-bundle-alpha-sig whitespace=delete><local-win32-bundle-alpha>.asc</define-tag>
79 
+
80 
+<define-tag package-osx-bundle-stable-sig whitespace=delete><package-osx-bundle-stable>.asc</define-tag>
81 
+<define-tag package-osx-bundle-alpha-sig whitespace=delete><package-osx-bundle-alpha>.asc</define-tag>
82 
+
83 
+<define-tag package-oldosx-bundle-stable-sig whitespace=delete><package-oldosx-bundle-stable>.asc</define-tag>
84 
+<define-tag package-oldosx-bundle-alpha-sig whitespace=delete><package-oldosx-bundle-alpha>.asc</define-tag>
85 
+
86 
+<define-tag package-osx-stable-sig whitespace=delete><package-osx-stable>.asc</define-tag>
87 
+<define-tag package-osx-alpha-sig whitespace=delete><package-osx-alpha>.asc</define-tag>
88 
+
89 
+<define-tag package-oldosx-stable-sig whitespace=delete><package-oldosx-stable>.asc</define-tag>
90 
+<define-tag package-oldosx-alpha-sig whitespace=delete><package-oldosx-alpha>.asc</define-tag>
91 
+
92 
+<define-tag package-source-stable-sig whitespace=delete><package-source-stable>.asc</define-tag>
93 
+<define-tag package-source-alpha-sig whitespace=delete><package-source-alpha>.asc</define-tag>
94 
+
95 
+<define-tag version-torbutton whitespace=delete>1.2.5 (08 April 2010)</define-tag>
96 
+<define-tag version-hash-torbutton whitespace=delete>sha1:e84592877593ad6119e829ac7199fd19333e101e</define-tag>
nl/mirrors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,49 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Mirrors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Spiegelservers</h2>
14 
+<hr />
15 
+
16 
+<p>
17 
+De canonical URL van deze site is <a
18 
+href="https://www.torproject.org/">https://www.torproject.org/</a>, maar er
19 
+zijn een paar spiegelsites van deze site op andere plekken.
20 
+</p>
21 
+
22 
+<p>
23 
+Als u een spiegelserver zou willen draaien, lees dan alstublieft <a
24 
+href="<page docs/running-a-mirror>">onze instructies voor het draaien van een
25 
+spiegelserver</a>.
26 
+</p>
27 
+
28 
+<table class="mirrors">
29 
+<tr>
30 
+  <th>Land</th>
31 
+  <th>Organisatie</th>
32 
+  <th>Status</th>
33 
+  <th>ftp</th>
34 
+  <th>http dist/</th>
35 
+  <th>http website</th>
36 
+  <th>https dist/</th>
37 
+  <th>https website</th>
38 
+  <th>rsync dist/</th>
39 
+  <th>rsync website</th>
40 
+</tr>
41 
+
42 
+<!--PO4ASHARPBEGINinclude <mirrors-table.wmi>
43 
+PO4ASHARPEND-->
44 
+</table>
45 
+
46 
+  </div>
47 
+
48 
+
49 
+#include <foot.wmi>
no/documentation.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,278 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22359 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor: Documentation" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<a id="RunningTor"></a>
14 
+<h2><a class="anchor" href="#RunningTor">Kjøre Tor</a></h2>
15 
+<ul>
16 
+<li><a href="<page docs/tor-doc-windows>">Installere Tor på Win32</a></li>
17 
+<li><a href="<page docs/tor-doc-osx>">Installere Tor på Mac OS X</a></li>
18 
+<li><a href="<page docs/tor-doc-unix>">Installere Tor på Linux/BSD/Unix</a></li>
19 
+<li><a href="<page torbutton/index>">Installere Torbutton for Tor</a></li>
20 
+<li><a href="<page docs/tor-doc-relay>">Konfigurere en Tor-relè</a></li>
21 
+<li><a href="<page docs/tor-hidden-service>">Konfigurere en skjult tjeneste med
22 
+Tor</a></li>
23 
+</ul>
24 
+
25 
+<a id="Support"></a> <a id="UpToSpeed"></a>
26 
+<h2><a class="anchor" href="#UpToSpeed">Kjapp gjennomgang av Tor sin fortid,
27 
+fremtid og nåværende</a></h2>
28 
+
29 
+<ol>
30 
+<li>
31 
+Først les <a href="<page overview>">oversiktssiden</a> for å lære generelt
32 
+om hvordan Tor fungerer, hva formålet er og hvem som bruker det.
33 
+</li>
34 
+
35 
+<li>
36 
+<a href="<page download>">Installer Tor-pakken</a> for å teste det ut. Vær
37 
+sikker på at du har Firefox installert først, og vær sikker på å les <a
38 
+href="<page download>#Warning">om advarslene</a> som kan ødelegge
39 
+anonymiteten din.
40 
+</li>
41 
+
42 
+<li>
43 
+Our <a
44 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">FAQ</a>
45 
+covers all sorts of topics, including questions about setting up a client or
46 
+relay, concerns about anonymity attacks, why we didn't build Tor in other
47 
+ways, etc.  There's a separate <a href="<page faq-abuse>">Abuse FAQ</a> to
48 
+answer common questions from or for relay operators.  The <a href="<page
49 
+eff/tor-legal-faq>">Tor Legal FAQ</a> is written by EFF lawyers, and aims to
50 
+give you an overview of some of the legal issues that arise from the Tor
51 
+project in the US.
52 
+</li>
53 
+
54 
+<li>The <a href="<page tor-manual>">manual</a> lists all the possible entries
55 
+you can put in your <a
56 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc
57 
+file</a>. We also provide a <a href="<page tor-manual-dev>">manual for the
58 
+development version of Tor</a>.</li>
59 
+
60 
+<li>If you have questions, we have an IRC channel (for users, relay operators,
61 
+and developers)  at <a href="irc://irc.oftc.net/tor">#tor on
62 
+irc.oftc.net</a>. If you have a bug, especially a crash bug, read <a
63 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#MyTorkeepscrashing.">how
64 
+to report a Tor bug</a> first and then tell us as much information about it
65 
+as you can in <a href="https://bugs.torproject.org/tor">our bugtracker</a>.
66 
+(If your bug is with Polipo, your browser, or some other application, please
67 
+don't put it in our bugtracker.) The <a href="#MailingLists">or-talk mailing
68 
+list</a> can also be useful.
69 
+</li>
70 
+
71 
+<li>
72 
+<a href="https://blog.torproject.org/">Tor har en blogg nå</a>. Vi prøver å
73 
+holde den oppdatert noen ganger i uken med det av nyheter som måtte være.
74 
+</li>
75 
+
76 
+<li>
77 
+Last ned og se Roger sin frem oversiktstale fra What The Hack (<a
78 
+href="http://freehaven.net/~arma/wth-anonymous-communication-58.mp4">video</a>,
79 
+<a href="http://freehaven.net/~arma/wth1.pdf">lysbilder</a>, <a
80 
+href="http://wiki.whatthehack.org/index.php/Anonymous_communication_for_the_United_States_Department_of_Defense...and_you">abstrakt</a>).
81 
+Denne talen ble gitt i Juli 2005 når vi ble sponset av EFF og når vårt
82 
+nettverk fortsatt var nokså lite, men den gir fortsatt god innsikt i hvordan
83 
+Tor fungerer og hva det er godt for.
84 
+</li>
85 
+
86 
+<li>
87 
+Se gjennom våre <a href="#DesignDoc">designdokumenter</a>. Legg også merke
88 
+til at vi har RFC-stylet spesifikasjoner som kan fortelle deg nøyaktig
89 
+hvordan Tor er bygget.
90 
+</li>
91 
+
92 
+<li>
93 
+Det finnes en <a
94 
+href="https://svn.torproject.org/svn/projects/roadmaps/2008-12-19-roadmap-full.pdf">hel
95 
+liste over ting vil takle i fremtiden</a>. Desverre må mange av de tingene
96 
+få konsistens før de gir mening til folk som ikke er Tor-utviklere, men du
97 
+kan fortsatt få en liten idè om hvilke ting som vil bli løst i nærmeste
98 
+fremtid.
99 
+</li>
100 
+
101 
+<li>
102 
+Last ned og se Nick sin "Technical changes since 2004" tale fra Defcon i
103 
+juli 2007 (<a
104 
+href="http://freehaven.net/~arma/Defcon15-Mathewson-Technical_Changes_since_you_Last_Heard_about_Tor.mp4">video</a>,
105 
+<a
106 
+href="http://freehaven.net/~nickm/slides/Defcon07/TorChanges.pdf">lysbilder</a>),
107 
+Roger sin "blocking-resistance and circumvention" tale fra 23C3 i desember
108 
+2006 (<a
109 
+href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">video</a>,
110 
+<a href="http://freehaven.net/~arma/slides-23c3.pdf">lysbilder</a>, <a
111 
+href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">abstrakt</a>,
112 
+<a
113 
+href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">designpapirer</a>,
114 
+og Roger sin "Current events in 2007" tale fra 24C3 fra desember 2007 (<a
115 
+href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">video</a>,
116 
+<a href="http://freehaven.net/~arma/slides-24c3.pdf">lysbilder</a>, <a
117 
+href="http://events.ccc.de/congress/2007/Fahrplan/events/2325.en.html">abstrakt</a>).
118 
+Vi har også en What The Hack innføring om skjulte tjenester (<a
119 
+href="http://freehaven.net/~arma/wth_tor_hidden_services.mp4">video</a>, <a
120 
+href="http://freehaven.net/~arma/wth3.pdf">lysbilder</a>).
121 
+</li>
122 
+
123 
+<li>
124 
+Se Mike sin "Securing the Tor network" tale fra Defcon i juli 2007 (<a
125 
+href="http://freehaven.net/~arma/Defcon15-Mike_Perry-Securing_the_Tor_Network.mp4">video</a>,
126 
+<a
127 
+href="http://freehaven.net/~arma/SecuringTheTorNetwork.pdf">lysbilder</a>).
128 
+Den forklarer vanlige måter å angripe nettverk som Tor og viser hvordan vi
129 
+prøver å forsvare oss mot dem, og introduserer <a
130 
+href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>-samlingen
131 
+av script.
132 
+</li>
133 
+
134 
+<li>
135 
+Les mer om <a href="<gitblob>doc/spec/proposals/001-process.txt">Tor sin
136 
+forslagsprosess for endringer av vårt design</a>, og se over <a
137 
+href="<gittree>doc/spec/proposals">eksisterende forslag</a>.
138 
+</li>
139 
+
140 
+<li>
141 
+Vår <a href="<gitblob>doc/TODO">utvikler TODO-fil</a> starter med et tidsrom
142 
+for eksterne ønsker; ting som <a href="<page sponsors>">våre sponsorer</a>
143 
+har betalt for å se gjort. Den lister også opp mange andre oppgaver og tema
144 
+vi ønsker å takle etterpå.
145 
+</li>
146 
+
147 
+<li>
148 
+Når du så er oppdatert på alt, vil ting begynne å forandre seg overraskende
149 
+fort. Vi har <a href="#MailingLists">or-dev mailing liste</a> hvor relativt
150 
+komplekse diskusjoner skjer, og #tor sin IRC-kanal hvor mindre komplekse
151 
+diskusjoner skjer.
152 
+</li>
153 
+
154 
+</ol>
155 
+
156 
+<a id="MailingLists"></a>
157 
+<h2><a class="anchor" href="#MailingLists">Informasjon om maillistene</a></h2>
158 
+<ul>
159 
+<li><a href="http://archives.seul.org/or/announce/">or-announce mailing
160 
+liste</a> er en mailing liste med primæroppgave å annonsere nye utgivelser
161 
+og kritiske sikkerhetsoppdateringer. Alle burde være på denne listen. Det er
162 
+også en <a
163 
+href="http://rss.gmane.org/gmane.network.onion-routing.announce">RSS-feed</a>
164 
+av or-announce hos <a href="http://gmane.org">gmane.org</a>.</li>
165 
+<li><a href="http://archives.seul.org/or/talk/">or-talk listen</a> er hvor en
166 
+god del diskusjoner skjer, og hvor vi sender ut beskjer om nye ustabile
167 
+versjoner og kandidater til utgivelse i stabile versjoner.</li>
168 
+<li><a href="http://archives.seul.org/tor/relays/">tor-relays listen</a> er hvor
169 
+diskusjoner om å kjøre, konfigurere og håndtere din Tor-relé foregår. Hvis
170 
+du kjører en relé eller vurderer å gjøre det så er dette listen for deg.</li>
171 
+<li><a href="http://archives.seul.org/or/dev/">or-dev listen</a> er kun for
172 
+utviklere og har lite trafikk.</li>
173 
+<li>En liste av <a href="http://archives.seul.org/tor/mirrors/">nettside
174 
+operatører (de som kjører kopier av denne)</a> for nye nettside operatører,
175 
+og støttede <a href="<page mirrors>">nåværende nettside kopier</a>.</li>
176 
+<li>En liste over <a href="http://archives.seul.org/or/cvs/">svn og git
177 
+innlegg</a> kan være interessant for utviklere.</li>
178 
+<li>An automated list for <a href="http://archives.seul.org/tor/bugs/">bug
179 
+reports from trac</a> may be interesting for users and developers.</li>
180 
+</ul>
181 
+
182 
+<a id="DesignDoc"></a>
183 
+<h2><a class="anchor" href="#DesignDoc">Designdokumenter</a></h2>
184 
+<ul>
185 
+<li><b>designdokumentet</a> (publisert på Usenix Security 2004) utgir våre
186 
+rettferdiggjøringer og sikkerhetsanalyser av Tor-designet: <a
187 
+href="https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf">PDF</a>
188 
+og <a
189 
+href="https://svn.torproject.org/svn/projects/design-paper/tor-design.html">HTML</a>
190 
+versjoner er tilgjengelig.</li>
191 
+<li>Vår oppfølgende om <b>utfordringer vedrørende lav-latens anonymitet</b>
192 
+(fortsatt i form av et utkast) detaljerer mer nylige erfaringer og
193 
+retninger: <a
194 
+href="https://svn.torproject.org/svn/projects/design-paper/challenges.pdf">PDF-utkast</a>.</li>
195 
+<li>Vårt dokument hos WEIS 2006;  <b>Anonymitet elsker selskap: Brukbarhet og
196 
+nettverkseffekt</b>; forklarer hvorfor brukbarheten i anonymitetsystemer
197 
+betyr mye for deres sikkerhet: <a
198 
+href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
199 
+<li>Vårt forberedende design for å gjøre det vanskeligere for store brannmurer å
200 
+hindre tilgang til Tor-nettverket er beskrevet i <b>design av det
201 
+blokkeringsavstøtende anonymitetsystem</b>: <a
202 
+href="https://svn.torproject.org/svn/projects/design-paper/blocking.pdf">PDF-utkast</a>
203 
+og <a
204 
+href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">HTML-utkast</a>.
205 
+Vil du <a href="<page volunteer>#Coding">hjelpe oss med å bygge det</a>?</li>
206 
+<li><b>Spesifikasjonene</b> sikter på å gi utviklere nok informasjon til å bygge
207 
+en kompatibel versjon av Tor:
208 
+<ul>
209 
+<li><a href="<gitblob>doc/spec/tor-spec.txt">Tor sine hovedspesifikasjoner</a></li>
210 
+<li><a href="<gitblob>doc/spec/dir-spec.txt">Tor version 3 katalogserver
211 
+spesifikasjoner</a> (og eldre <a
212 
+href="<gitblob>doc/spec/dir-spec-v1.txt">version 1</a> og <a
213 
+href="<gitblob>doc/spec/dir-spec-v2.txt">version 2</a> katalog
214 
+spesifikasjoner)</li>
215 
+<li><a href="<gitblob>doc/spec/control-spec.txt">Tor kontrollprotokoll sine
216 
+spesifikasjoner</a></li>
217 
+<li><a href="<gitblob>doc/spec/rend-spec.txt">Tor spesifikasjoner for
218 
+samlepunkt</a></li>
219 
+<li><a href="<gitblob>doc/spec/path-spec.txt">Tor sine spesifikasjoner for
220 
+stivalg</a></li>
221 
+<li><a href="<gitblob>doc/spec/address-spec.txt">Spesielle vertsnavn i Tor</a></li>
222 
+<li><a href="<gitblob>doc/spec/socks-extensions.txt">Tor sin SOCKS støtte og
223 
+utvidelser</a></li>
224 
+<li><a href="<gitblob>doc/spec/version-spec.txt">Hvordan Tor numererer
225 
+versjonene</a></li>
226 
+<li><a href="<gitblob>doc/spec/proposals">Utkast av nye spesifikasjoner og
227 
+forslag til endringer som fortsatt er aktiv</a></li>
228 
+</ul></li>
229 
+
230 
+</ul>
231 
+
232 
+<a id="NeatLinks"></a>
233 
+<h2><a class="anchor" href="#NeatLinks">Fine lenker</a></h2>
234 
+<ul>
235 
+<li>The <a href="https://trac.torproject.org/projects/tor/wiki">Tor wiki</a>
236 
+provides a plethora of helpful contributions from Tor users. Check it out!</li>
237 
+<li><a
238 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">A
239 
+list of supporting programs you might want to use in association with
240 
+Tor</a>.</li>
241 
+<li><a href="https://check.torproject.org/">Tor detector</a> eller <a
242 
+href="http://torcheck.xenobite.eu/">den andre Tor detector</a> prøver å
243 
+gjette om du bruker Tor eller ikke.</li>
244 
+<li>Sjekk ut en av Tor statussidene, som a
245 
+href="http://torstatus.blutmagie.de/">blutmagie</a>, <a
246 
+href="http://trunk.torstatus.kgprog.com/index.php">kgprog</a> eller Xenobite
247 
+sin <a href="https://torstat.xenobite.eu/">Tor node status</a> sider. Husk
248 
+at disse listene er ikke nødvendigvis like nøyaktig som det din Tor klient
249 
+bruker fordi din client henter sin egen kataloginformasjon og undersøker det
250 
+lokalt.</li>
251 
+<li>Les <a
252 
+href="http://freehaven.net/anonbib/topic.html#Anonymous_20communication">disse
253 
+dokumentene</a> (spesielt de i boksene) for å bli oppdatert med det som
254 
+skjer i verden av anonyme kommunikasjonsystemer.</li>
255 
+</ul>
256 
+
257 
+<a id="Developers"></a>
258 
+<h2><a class="anchor" href="#Developers">For utviklere</a></h2>
259 
+  Bla gjennom Tor <b>kildekodemagasin</b>:
260 
+  <ul>
261 
+    <li><a href="<gitrepo>">Bla hierarkisk i magasinets kildekode direkte</a></li>
262 
+    <li>Tilgang til Git og SVN:
263 
+      <ul>
264 
+        <li><kbd>git clone git://git.torproject.org/git/tor</kbd></li>
265 
+        <li>Utviklingsdelen er <kbd>master</kbd>. Den aktive vedlikeholdsdelene er
266 
+<kbd>maint-0.2.0</kbd> og <kbd>maint-0.2.1</kbd>.</li>
267 
+        <li><kbd>svn checkout https://svn.torproject.org/svn/website/trunk website</kbd></li>
268 
+      </ul>
269 
+    </li>
270 
+    <li><a
271 
+href="https://gitweb.torproject.org//githax.git?a=blob;f=doc/Howto.txt;hb=HEAD">Basic
272 
+instructions for using Git to contribute to Tor software.</a></li>
273 
+  </ul>
274 
+
275 
+  </div>
276 
+
277 
+
278 
+#include <foot.wmi>
no/mirrors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,48 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Mirrors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Speil</h2>
14 
+<hr />
15 
+
16 
+<p>
17 
+Hoved-URLen til denne siden er <a
18 
+href="https://www.torproject.org/">https://www.torproject.org/</a>, men det
19 
+finnes enkelte andre speilinger av denne siden andre plasser.
20 
+</p>
21 
+
22 
+<p>
23 
+Hvis du har lyst til å sette opp et speil for våre nettsider, vær vennlig og
24 
+les <a href="<page docs/running-a-mirror>">instruksjonene</a> først.
25 
+</p>
26 
+
27 
+<table class="mirrors">
28 
+<tr>
29 
+  <th>Land</th>
30 
+  <th>Organisasjon</th>
31 
+  <th>Status</th>
32 
+  <th>ftp</th>
33 
+  <th>http dist/</th>
34 
+  <th>http nettsted</th>
35 
+  <th>https dist/</th>
36 
+  <th>https nettsted</th>
37 
+  <th>rsync dist/</th>
38 
+  <th>rsync nettsted</th>
39 
+</tr>
40 
+
41 
+<!--PO4ASHARPBEGINinclude <mirrors-table.wmi>
42 
+PO4ASHARPEND-->
43 
+</table>
44 
+
45 
+  </div>
46 
+
47 
+
48 
+#include <foot.wmi>
pl/bridges.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,206 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22432 $
9 
+# Translation-Priority: 1-high
10 
+#include "head.wmi" TITLE="Tor: Bridges" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<a id="BridgeIntroduction"></a>
14 
+<h2><a class="anchor" href="#BridgeIntroduction">Tor: Mostki</a></h2>
15 
+<hr />
16 
+
17 
+<p>
18 
+Mostkowe przekaźniki sieci (lub po prostu "mostki") to węzły sieci Tora,
19 
+które niesą wpisane do głównego katalogu. Jako że nie ma pełnej publicznej
20 
+listy mostków, to nawet jeśli Twój dostawca internetu blokuje połączenia do
21 
+wszystkich znanychwęzłów Tora, prawdopodobnie nie będzie mógł zablokować
22 
+wszystkich mostków. Jeśli podejrzewasz, że masz zablokowany dostęp do sieci
23 
+Tor, możesz skorzystaćz mostków Tora.
24 
+</p>
25 
+
26 
+<p>
27 
+Dodanie mostków do Tora jest krokiem naprzód w opieraniu się
28 
+blokowaniu. Jest całkiem możliwe, że nie musisz mieć mostka, by używać
29 
+Tora. Spróbuj najpierw poużywać Tora, a jeśli masz kłopoty, to możliwe, że
30 
+potrzebujesz mostka, by obejść blokadę. Wiele programów filtrujących szuka
31 
+nieszyfrowanych żądań pobrania katalogu Tora, bypoznać, że używasz Tora, ale
32 
+od wersji 0.2.0.23-rc Tor wysyła szyfrowane zapytania do katalogu. Ta zmiana
33 
+oznacza, że wiele programów filtrujących nie potrafi rozpoznać połączenia
34 
+Tora. Powinieneś/aś więc najpierw spróbować użyć Tora bez mostków, gdyżjest
35 
+możliwe, że będzie działał.
36 
+</p>
37 
+
38 
+<p>
39 
+Note that it's also possible that Tor is non-functional for other
40 
+reasons. The latest version of <a href="<page torbrowser/index>">The Tor
41 
+Browser Bundle</a> on Windows tries to give you better hints about why Tor
42 
+is having problems connecting. You should also read <a
43 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#IinstalledTorandPolipobutitsnotworking.">the
44 
+FAQ about problems with running Tor properly</a> when you have issues.  If
45 
+you feel that the issue is clearly blocking, or you'd simply like to try
46 
+because you're unsure or feeling adventurous, please read on. Ensure that
47 
+you're using the <a href="<page download>#Dev">latest 0.2.1.x or 0.2.2.x
48 
+bundle for your platform</a>.
49 
+</p>
50 
+
51 
+<p>
52 
+By korzystać z mostka, musisz najpierw jakiś znaleźć. Ponadto, będziesz
53 
+musiał/a skonfigurować Tora, podając adres mostka, którego zamierzasz
54 
+używać. Robi się tow kontrolerze Tora - programie Vidalia. Jeśli Twoje
55 
+połączenie z Internetem wymaga serwera pośredniczącego (proxy), musisz od
56 
+tego zacząć konfigurację Vidalii. Jeśli uważasz, że nie musisz konfigurować
57 
+serwera pośredniczącego do swojego połączenia, to pewnie nie
58 
+musisz. Spróbuj, a w razie problemów poproś nas o pomoc.
59 
+</p>
60 
+
61 
+<p>Freedom House has produced a video on how to get and use Tor bridges.  If
62 
+you don't see a video below, view it at <a
63 
+href="http://www.youtube.com/thetorproject">Youtube: Freedom4Internet</a>
64 
+Know of a better video, or one translated into your language? Let us know!</p>
65 
+
66 
+<div class="center">
67 
+<p><video id="v1" src="http://media.torproject.org/video/2009-using-a-bridge-relay-to-access-tor.ogv" autobuffer="true" controls="controls"></video></p>
68 
+</div>
69 
+
70 
+<p>
71 
+W chwili obecnej, możesz dostać mostek, odwiedzając <a
72 
+href="https://bridges.torproject.org/">https://bridges.torproject.org/</a>
73 
+swoją przeglądarką. Jeśli ta strona jest filtrowana i nie masz żadnych
74 
+innych serwerów proxy, by się do niej dostać, są <a href="#FindingMore">inne
75 
+sposoby naznalezienie mostka</a>.
76 
+</p>
77 
+
78 
+<a id="Understanding"></a>
79 
+<h2><a class="anchor" href="#Understanding">Zrozumienie jak działają mostki</a></h2>
80 
+<hr />
81 
+
82 
+<p>
83 
+Przykładowo, możesz dostać informacje o mostku wyglądające tak:
84 
+</p>
85 
+<pre><samp>
86 
+bridge 141.201.27.48:443 4352e58420e68f5e40bf7c74faddccd9d1349413
87 
+</samp>
88 
+</pre>
89 
+
90 
+<p>
91 
+Zrozumienie składników linii z mostkiem nie jest wymagane, lecz może się
92 
+przydać. Jeśli chcesz, możesz ominąć tę sekcję.<br />
93 
+Pierwszy element to adres IP: <tt>'141.201.27.48'</tt><br />
94 
+Drugi element to port: <tt>'443'</tt><br />
95 
+Trzeci element, odcisk palca, jest opcjonalny:
96 
+<tt>'4352e58420e68f5e40bf7c74faddccd9d1349413'</tt><br />
97 
+</p>
98 
+
99 
+<a id="UsingBridges"></a>
100 
+<h2><a class="anchor" href="#UsingBridges">Korzystanie z mostków w Torze i
101 
+Vidalii</a></h2>
102 
+<hr />
103 
+
104 
+<p>
105 
+By skorzystać z powyższego przykładowego adresu mostka, wejdź do ustawień
106 
+sieciowych programu Vidalia i kliknij "Mój dostawca blokuje połączenia do
107 
+sieci Tor" ("My ISP blocks connections to the Tor network"). Dodawaj adresy
108 
+mostków jeden po drugim na stronie ustawień sieciowych Vidalii, wklejając je
109 
+do okienka "Dodaj mostek" ("Add a Bridge") i klikając znak .Wszystko to
110 
+ujęte jest na obrazku:
111 
+</p>
112 
+
113 
+<br /><br />
114 
+<img src="$(IMGROOT)/vidalia-bridges.png" alt="strona ustawień sieci w programie Vidalia" />
115 
+<br /><br />
116 
+
117 
+<p>
118 
+Powinieneś dodać tyle adresów mostków, ile znasz, gdyż zwiększy to
119 
+niezawodność. Do połączenia z siecią Tora wystarczy jeden mostek, ale po
120 
+jego wyłączeniu tracisz połączenie z siecią.
121 
+</p>
122 
+
123 
+<a id="FindingMore"></a>
124 
+<h2><h2><a class= href=>Znajdowanie dalszych mostków</a></h2></h2>
125 
+<hr />
126 
+
127 
+<p>
128 
+Innym sposobem na znalezienie publicznych adresów mostków jest wysłanie
129 
+listue-mail na adres bridges@torproject.org o treści zawierającej tylko
130 
+jedną linię mówiącą "get bridges". Musisz jednak wysłać swój list z konta
131 
+gmail&mdash; w innym przypadku zbyt łatwo byłoby napastnikom utworzyć wiele
132 
+adresów e-maili poznać wszystkie mostki.Prawie natychmiast otrzymasz
133 
+odpowiedź zawierającą:
134 
+</p>
135 
+<pre>
136 
+Here are your bridge relays:
137 
+
138 
+ bridge 60.16.182.53:9001 c9111bd74a710c0d25dda6b35e181f1aa7911133
139 
+ bridge 87.237.118.139:444 c18dde4804e8fcb48464341ca1375eb130453a39
140 
+ bridge 60.63.97.221:443 ab5c849ed5896d53052e43966ee9aba2ff92fb82
141 
+
142 
+</pre>
143 
+<p>
144 
+Po otrzymaniu takiego listu z informacją o mostkach, możesz dalej
145 
+konfigurować Vidalię według <a href="#UsingBridges">powyższych</a> kroków.
146 
+</p>
147 
+
148 
+<a id="RunningABridge"></a>
149 
+<h2><h2><a class= href=>Prowadzenie Mostka Tor</a></h2></h2>
150 
+<hr />
151 
+
152 
+<p>
153 
+Jeśli chcesz pomóc, a nie możesz prowadzić <a
154 
+href="<pagedocs/tor-doc-relay>">normalnego przekaźnika Tora</a>,
155 
+powinieneś/aś prowadzić przekaźnik mostkowy. Możesz skonfigurować go na dwa
156 
+sposoby:
157 
+<ul>
158 
+<li> manually <a
159 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">edit
160 
+your torrc file</a> to be just these four lines:<br />
161 
+<pre><code>
162 
+SocksPort 0
163 
+ORPort 443
164 
+BridgeRelay 1
165 
+Exitpolicy reject *:*
166 
+</code></pre></li>
167 
+<li><a href="<page docs/tor-doc-relay>">lub korzystając z Vidalii</a>:<br />
168 
+<img src="$(IMGROOT)/vidalia-bridges-setup.png" alt="strona ustawień współdzielenia w programie Vidalia" /></li>
169 
+</ul>
170 
+</p>
171 
+
172 
+<p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors on
173 
+startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
174 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Myfirewallonlyallowsafewoutgoingports.">some
175 
+complex port forwarding</a>.
176 
+</p>
177 
+
178 
+<p>
179 
+Gdy skonfigurowany jako mostek, Twój serwer <b>nie</b> będzie widoczny w
180 
+publicznej sieci Tora.
181 
+</p>
182 
+
183 
+<p>
184 
+Twój przekaźnik mostkowy automatycznie opublikuje swój adres do katalogu
185 
+mostków, który będzie go podawał przez https lub e-mail, jak powyżej. Możesz
186 
+też bezpośrednio powiedzieć użytkownikowi o swoim mostku: jeśli używasz
187 
+Vidalii, możesz skopiować i wkleić adres mostku z okna ustawień. Jeśli
188 
+jesteś na Linuksie lub BSD, możesz ręcznie skonstruować adres, korzystając z
189 
+<a href="#Understanding">powyższego formatu</a>(odcisk palca możesz znaleźć
190 
+w logach Tora lub w <tt>/var/lib/tor/fingerprint</tt>,w zależności od Twojej
191 
+platformy).
192 
+</p>
193 
+
194 
+<p>
195 
+Jeśli chcesz się dowiedzieć więcej o projekcie mostka z technicznego punktu
196 
+widzenia,przeczytaj <a
197 
+href="<gitblob>doc/spec/bridges-spec.txt">specyfikację mostków
198 
+Tora</a>. Jeśli interesuje Cię prowadzenie niepublicznego mostka lub inne
199 
+niestandardowe wykorzystania, prosimy przeczytać specyfikację.
200 
+</p>
201 
+
202 
+  </div>
203 
+
204 
+
205 
+
206 
+#include <foot.wmi>
pl/faq-abuse.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,409 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22308 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Abuse FAQ" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>FAQ o nadużyciach</h2>
17 
+
18 
+<!-- BEGIN SIDEBAR -->
19 
+<div class="sidebar-left">
20 
+<h3>Pytania</h3>
21 
+<ul>
22 
+<li><a href="<page faq-abuse>#WhatAboutCriminals">Czy Tor nie umożliwia
23 
+przestępcom robienia złych rzeczy?</a></li>
24 
+<li><a href="<page faq-abuse>#DDoS">A co z atakami typu "distributed denial of
25 
+service" (DDoS)?</a></li>
26 
+<li><a href="<page faq-abuse>#WhatAboutSpammers">A co ze spamerami?</a></li>
27 
+<li><a href="<page faq-abuse>#HowMuchAbuse">Czy Tor jest bardzo nadużywany?</a></li>
28 
+<li><a href="<page faq-abuse>#TypicalAbuses">Więc czego mam oczekiwać, jeśli
29 
+uruchomię przekaźnik z możliwością wyjścia z sieci Tor?</a></li>
30 
+<li><a href="<page faq-abuse>#IrcBans">Tor jest zablokowany na sieci IRC, której
31 
+chciałbym używać.</a></li>
32 
+<li><a href="<page faq-abuse>#SMTPBans">Wasze węzły są zablokowane na serwerze
33 
+pocztowym, którego chcę używać.</a></li>
34 
+<li><a href="<page faq-abuse>#Bans">Chcę zablokować sieci Tor dostęp do mojej
35 
+usługi.</a></li>
36 
+<li><a href="<page faq-abuse>#TracingUsers">Mam dobry powód, by śledzić
37 
+użytkownika Tora. Możecie pomóc?</a></li>
38 
+<li><a href="<page faq-abuse>#RemoveContent">Chcę, aby usunięto jakąś treść z
39 
+adresu .onion.</a></li>
40 
+<li><a href="<page faq-abuse>#LegalQuestions">Mam pytania prawne dotyczące
41 
+nadużyć Tora.</a></li>
42 
+</ul>
43 
+</div>
44 
+
45 
+<!-- END SIDEBAR -->
46 
+<hr />
47 
+
48 
+<a id="WhatAboutCriminals"></a>
49 
+<h3><a class="anchor" href="#WhatAboutCriminals">Czy Tor nie umożliwia
50 
+przestępcom robienia złych rzeczy?</a></h3>
51 
+
52 
+<p>Przestępcy już i tak mogą robić złe rzeczy. Skoro chcą łamać prawo, już i
53 
+tak mają wiele możliwości, które dają <em>lepsze</em> zabezpieczenie
54 
+prywatności niż Tor.  Mogą kraść telefony komórkowe, używać ich, a potem
55 
+wyrzucać; mogą włamywać się do komputerów w Korei czy Brazylii i używać ich
56 
+do różnych działań; mogą używać oprogramowania szpiegowskiego, wirusów i
57 
+innych technik, by przejąć kontrolę nad dosłownie milionami komputerów z
58 
+Windowsem na całym świecie. </p>
59 
+
60 
+<p>Celem Tora jest dawanie ochrony zwykłym ludziom, którzy chcą działać zgodnie
61 
+z prawem.  W dzisiejszych czasach tylko przestępcy mają prywatność i musimy
62 
+to naprawić. </p>
63 
+
64 
+<p>Niektórzy zwolennicy prywatności tłumaczą, że to jest kompromis &mdash;
65 
+przyjmowanie złych sposobów użycia na rzecz tych dobrych &mdash; ale chodzi
66 
+o coś więcej niż tylko to.  Przestępcy i inni źli ludzie mają motywację by
67 
+uczyć się, jak osiągać dobrą anonimowość, i wielu ma motywację, by dobrze za
68 
+to zapłacić. Możliwość kradzieży i używania tożsamości niewinnych ofiar
69 
+(kradzież tożsamości) czyni to jeszcze łatwiejszym. Zaś normalni ludzie nie
70 
+mają czasu lub pieniędzy do wydania na zastanawianie się, jak zachować
71 
+prywatność będąc on-line. To jest najgorszy ze wszystkich możliwych światów. </p>
72 
+
73 
+<p>Więc tak, przestępcy mogą teoretycznie używać Tora, ale oni już mają lepsze
74 
+rozwiązania i wydaje się mało prawdopodobnym, żeby odebranie Tora światu
75 
+powstrzymało ich od robienia swych złych rzeczy. Jednocześnie, Tor i inne
76 
+środki ochrony prywatności mogą <em>zwalczać</em> kradzież tożsamości,
77 
+przestępstwa fizyczne, jak śledzenie, itd. </p>
78 
+
79 
+
80 
+
81 
+<!--
82 
+<a id="Pervasive">
83 
+</a>
84 
+<h3><a class="anchor" href="#Pervasive">If the whole world starts using
85 
+Tor, won't civilization collapse?</a></h3>
86 
+-->
87 
+<a id="DDoS"></a>
88 
+<h3><a class="anchor" href="#DDoS">A co z atakami typu "distributed denial of
89 
+service" (DDoS)?</a></h3>
90 
+
91 
+<p>Ataki DDoS zwykle polegają na posiadaniu grupy tysięcy komputerów
92 
+wysyłających dużo danych do ofiary. Skoro celem jest zapchanie łącza ofiary,
93 
+ataki te zwykle wysyłają pakiety UDP, gdyż nie wymagają one uzgodnień
94 
+połączenia ani koordynacji transmisji. </p>
95 
+
96 
+<p>Ale skoro Tor transportuje wyłącznie prawidłowo utworzone strumienie TCP, a
97 
+nie wszystkie pakiety IP, nie można wysyłać pakietów UDP przez Tora. (Nie
98 
+można też wykonać specjalnej formy tego ataku, jak SYN flooding.) Tak więc,
99 
+zwykłe ataki DDoS nie są możliwe do przeprowadzenia przez Tora. Tor
100 
+uniemożliwia też ataki polegające na narastaniu objętości danych wysyłanych
101 
+do zewnętrznych serwerów: musisz wysłać jeden bajt na każdy bajt, który Tor
102 
+wyśle do odbiorcy. Ogólnie więc ci, którzy mają dość szerokie łącze by
103 
+wykonać skuteczny atak DDoS, mogą to równie dobrze zrobić bez Tora. </p>
104 
+
105 
+<a id="WhatAboutSpammers"></a>
106 
+<h3><a class="anchor" href="#WhatAboutSpammers">A co ze spamerami?</a></h3>
107 
+
108 
+<p>Po pierwsze, domyślna polityka wyjścia z Tora odrzuca cały ruch wychodzący
109 
+na port 25 (SMTP). Dlatego wysyłanie spamu przez Tora nie będzie działać w
110 
+domyślnej konfiguracji. Jest możliwe, że niektórzy operatorzy przekaźników
111 
+sieci Tor włączą port 25 na swoim punkcie wyjścia, wtedy taki komputer
112 
+pozwoli na wysyłanie poczty; ale ta osoba mogłaby równie dobrze uruchomić
113 
+otwarty serwer pocztowy przekazujący pocztę, niezależnie od Tora. Krótko
114 
+mówiąc, Tor nie jest użyteczny do spamowania, gdyż prawie wszystkie
115 
+przekaźniki sieci Tora odmawiają wysłania poczty. </p>
116 
+
117 
+<p>Ale oczywiście, nie chodzi tylko o dostarczanie poczty. Spamerzy mogą
118 
+wykorzystywać Tora, by łączyć się z otwartymi serwerami Proxy HTTP (a z nich
119 
+do serwerów SMTP); by łączyć się ze źle napisanymi skryptami CGI
120 
+wysyłającymi pocztę; oraz by kontrolować swoje botnety &mdash; tzn. w sposób
121 
+ukryty łączyć się z armiami przejętych komputerów, które dostarczają spam.
122 
+</p>
123 
+
124 
+<p>
125 
+To wstyd, ale zauważ, że spamerzy już i tak sobie świetnie radzą bez
126 
+Tora. Pamiętaj też, że wiele z ich bardziej subtelnych mechanizmów
127 
+komunikacji (jak sfałszowane pakietu UDP) nie może być używanych z Torem,
128 
+gdyż ten transportuje tylko prawidłowo uformowane połączenia TCP.
129 
+</p>
130 
+
131 
+<a id="ExitPolicies"></a>
132 
+<h3><a class="anchor" href="#ExitPolicies">Jak działają polityki wyjścia
133 
+Tora?</a></h3>
134 
+
135 
+<p>
136 
+<a href="<page faq>#ExitPolicies">Przeniesione na nową stronę FAQ</a>
137 
+</p>
138 
+
139 
+<a id="HowMuchAbuse"></a>
140 
+<h3><a class="anchor" href="#HowMuchAbuse">Czy Tor jest bardzo nadużywany?</a></h3>
141 
+
142 
+<p>Nie bardzo, patrząc po całości. Sieć działa od października 2003, a
143 
+dostaliśmy tylko garść skarg. Oczywiście, jak każda sieć nastawiona na
144 
+prywatność, przyciągamy trochę pacanów. Polityki wyjścia Tora pozwalają
145 
+oddzielić rolę "dostarczycieli zasobów do sieci" od roli "chcących stawiać
146 
+czoła skargom o nadużyciach na punktach wyjścia", więc mamy nadzieję, że
147 
+nasza sieć jest bardziej podtrzymywalna od wcześniejszych prób z sieciami
148 
+anonimowymi. </p>
149 
+
150 
+<p>Jako że Tor posiada także <a href="<page overview>">wiele dobrych
151 
+zastosowań</a>, czujemy, że w tej chwili całkiem nieźle nam idzie ustalanie
152 
+równowagi. </p>
153 
+
154 
+<a id="TypicalAbuses"></a>
155 
+<h3><a class="anchor" href="#TypicalAbuses">Więc czego mam oczekiwać, jeśli
156 
+uruchomię przekaźnik z możliwością wyjścia z sieci Tor?</a></h3>
157 
+
158 
+<p>Jeśli masz przekaźnik sieci Tora, który umożliwia połączenia wychodzące (tak
159 
+jak polityka domyślna), można prawie na pewno powiedzieć, że wcześniej czy
160 
+później dostaniesz od kogoś wiadomość. Skargi o nadużycia mają wiele
161 
+postaci. Na przykład: </p>
162 
+<ul>
163 
+<li>Ktoś podłącza się do systemu Hotmail i wysyła żądanie okupu jakiejś firmie.
164 
+FBI przysyła Ci uprzejmy list, ty tłumaczysz, że masz przekaźnik sieci Tora,
165 
+a oni odpowiadają "no trudno" i zostawiają Cię w spokoju. [Port 80]</li>
166 
+<li>Ktoś stara się zmusić Cię do wyłączenia, używając Tora do połączenia się z
167 
+Google Groups i wysyłania spamu do Usenetu, a potem wysyła nieuprzejmy list
168 
+do twojego dostawcy internetu (ISP) o tym, jak psujesz świat. [Port 80]</li>
169 
+<li>Ktoś łączy się z siecią IRC i staje się nieznośny. Twój dostawca dostaje
170 
+uprzejmy list o tym, jak włamano się do Twojego komputera lub Twój komputer
171 
+zostaje zaatakowany atakiem typu DDoS. [Port 6667]</li>
172 
+<li>Ktoś używa Tora do pobrania filmu Vina Diesela, a Twój dostawca dostaje
173 
+informację o naruszeniu praw autorskich. Zobacz <a href="<page
174 
+eff/tor-dmca-response>">Szablon odpowiedzi na taką informację</a>, który
175 
+wytłumaczy, czemu Rwój dostawca może prawdopodobnie zignorować taką
176 
+wiadomość bez żadnych skutków prawnych. [Różne porty]</li>
177 
+</ul>
178 
+
179 
+<p>Możesz także dowiedzieć się, że IP Twojego przekaźnika sieci Tor jest
180 
+blokowane przy próbie dostępu do pewnych stron lub usług internetowych. To
181 
+może się zdarzyć niezależnie od polityki wyjścia, gdyż niektóre grupy nie
182 
+wiedzą, że Tor ma polityki wyjścia lub ich to nie obchodzi. (Jeśli masz
183 
+wolny adres IP nieużywany do innych działań, możesz rozważyć uruchomienie
184 
+przekaźnika sieci Tora na tym właśnie adresie.) Na przykład, </p>
185 
+
186 
+<ul>
187 
+<li>Z powodu paru przypadków anonimowych pacanów, bawiących się jej stronami,
188 
+Wikipedia aktualnie blokuje wiele IP serwerów Tora od zapisu (czytanie nadal
189 
+działa). Rozmawiamy z Wikipedią o tym, jak mogą zapobiegać nadużyciom, w
190 
+dalszym ciągu dając dostęp anonimowym pomocnikom, którzy często mają
191 
+najnowsze wiadomości lub wewnętrzne informacje na jakiś temat, ale nie chcą
192 
+ryzykować odkrycia ich tożsamości, gdy będą te informacje publikować (lub
193 
+nie chcę odkrywać przed lokalnymi obserwatorami, że korzystają z
194 
+Wikipedii). Podobna sprawa jest z serwisem Slashdot.</li>
195 
+
196 
+<li>SORBS umieszcza adresy IP niektórych przekaźników sieci Tora na swojej
197 
+czarnej liście dotyczące e-maili. Robią to, gdyż pasywnie sprawdzają, czy
198 
+twój przekaźnik łączy się z pewnymi sieciami IRC, i w oparciu o to
199 
+wnioskują, że jest on zdolny do spamowania. Próbowaliśmy z nimi
200 
+współpracować, by im wytłumaczyć, że nie każdy program działa w ten sposób,
201 
+ale poddaliśmy się. Zalecamy, byście ich unikali i <a
202 
+href="http://paulgraham.com/spamhausblacklist.html">nauczyli swoich
203 
+przyjaciół (jeśli też ich używają), żeby również unikali nadużywających
204 
+czarnych list</a>.</li>
205 
+
206 
+</ul>
207 
+
208 
+<a id="IrcBans"></a>
209 
+<h3><a class="anchor" href="#IrcBans">Tor jest zablokowany na sieci IRC, której
210 
+chciałbym używać.</a></h3>
211 
+
212 
+<p>Czasami różne ćwoki używają Tora, by trollować kanały IRC. Takie nadużycia
213 
+skutkują w tymczasowym blokowaniu według IP ("klines" w slangu IRC), gdyż
214 
+operatorzy sieci próbują trzymać troli z dala od swojej sieci. </p>
215 
+
216 
+<p>Tego typu odpowiedź podkreśla fundamentalny błąd w modelu bezpieczeństwa
217 
+sieci IRC: wydaje im się, że adresy IP odpowiadają ludziom i że poprzez
218 
+blokowanie adresu IP, blokują właściwego człowieka. W rzeczywistości tak nie
219 
+jest &mdash; wielu takich troli normalnie korzysta z dosłownie milionów
220 
+otwartych serwerów proxy i komputerów w całym internecie, do których się
221 
+włamano. Sieci IRC przegrywają walkę, próbując zablokować te wszystkie
222 
+węzły, powstało wiele czarnych list i kontra-troli w oparciu o ten
223 
+nieprawidłowy model (podobnie jak to jest w antywirusach). Sieć Tora jest tu
224 
+tylko kroplą w morzu. </p>
225 
+
226 
+<p>Z drugiej strony, z punktu widzenia operatorów serwerów IRC, bezpieczeństwo
227 
+nie jest sprawą typu wszystko albo nic. Poprzez szybkie reagowanie na troli
228 
+i każdy inny atak społeczny, możliwe jest uczynienie ataku mniej atrakcyjnym
229 
+dla napastnika. Zaś większość indywidualnych adresów odpowiada pojedynczym
230 
+osobom na każdej sieci IRC o każdej porze. Do wyjątków należą bramki NAT,
231 
+które można traktować jako osobny przypadek. Próba powstrzymania używania
232 
+otwartych proxy może i jest przegrywaną walką, ale nie jest nią kline'owanie
233 
+pojedynczych źle zachowujących się użytkowników IRCa, dopóki się nie znudzą
234 
+i nie pójdą sobie gdzieś indziej. </p>
235 
+
236 
+<p>Ale prawdziwą odpowiedzią jest implementacja systemów uwierzytelniania na
237 
+poziomie aplikacji, żeby dobrze zachowujący się użytkownicy mogli trzymać z
238 
+dala tych źle zachowujących się. To musi być oparte na pewnych cechach
239 
+człowieka (np. hasło, które zna), a nie na cechach sposobu, w jaki
240 
+transportowany są jego pakiety. </p>
241 
+
242 
+<p>Oczywiście, nie wszystkie sieci IRC próbują blokować węzły Tora. W końcu,
243 
+całkiem niemało ludzi używa Tora, by w prywatności poużywać IRCa w celu
244 
+nawiązania dobrej, legalnej komunikacji bez przywiązywania tych ludzi do ich
245 
+rzeczywistej tożsamości. Każda sieć IRC musi zdecydować, czy blokowanie
246 
+kilku więcej z tych milionów adresów IP, których mogą używać źli ludzie,
247 
+jest warte utraty wkładu od dobrze zachowujących się użytkowników Tora. </p>
248 
+
249 
+<p>Jeśli jesteś blokowany, porozmawiaj z operatorami sieci i wyjaśnij im
250 
+sytuację.  Mogą oni w ogóle nie zdawać sobie sprawy z istnienia Tora lub
251 
+mogą być nieświadomi tego, że adresy, które blokują są punktami wyjścia
252 
+sieci Tor. Jeśli po wyjaśnieniu problemy dojdą do wniosku, że Tor powinien
253 
+być blokowany, rozważ korzystanie z sieci, która daje większą swobodę
254 
+wypowiedzi. Może zaproszenie ich na kanał #tor na irc.oftc.net pomoże im
255 
+pokazać, że nie wszyscy jesteśmy złymi ludźmi. </p>
256 
+
257 
+<p>Ostatecznie, jeśli odkryjesz sieć IRC, która zdaje się blokować Tora lub
258 
+jeden z jego punktów wyjścia, podaj tę informację na <a
259 
+href="https://wiki.torproject.org/wiki/TheOnionRouter/BlockingIrc">stronie
260 
+śledzenia blokad Tora przez IRC</a>, żeby podzielić się tym z innymi. Co
261 
+najmniej jedna sieć IRC sprawdza tę stronę, żeby odblokowywać punkty
262 
+wyjścia, które zostały niesłusznie zablokowane. </p>
263 
+
264 
+<a id="SMTPBans"></a>
265 
+<h3><a class="anchor" href="#SMTPBans">Wasze węzły są zablokowane na serwerze
266 
+pocztowym, którego chcę używać.</a></h3>
267 
+
268 
+<p>Mimo że <a href="#WhatAboutSpammers">Tor nie jest przydatny do
269 
+spamowania</a>, niektórym zbyt zagorzałym twórcom czarnych list wydaje się,
270 
+że wszystkie otwarte sieci są złe &mdash; próbują przymusić administratorów
271 
+sieci odnośnie spraw polityki, usług i trasowania, a potem wyciągać opłaty
272 
+od ofiar. </p>
273 
+
274 
+<p>Jeśli administratorzy twojego serwera zdecydują się takich czarnych list, by
275 
+odrzucać pocztę przychodzącą, porozmawiaj z nimi i opowiedz im o Torze i
276 
+jego politykach wyjścia. </p>
277 
+
278 
+<a id="Bans"></a>
279 
+<h3><a class="anchor" href="#Bans">Chcę zablokować sieci Tor dostęp do mojej
280 
+usługi.</a></h3>
281 
+
282 
+<p>Przykro nam to słyszeć. Są sytuacje, gdzie blokowanie anonimowego dostępu do
283 
+usługi ma sens. Ale w wielu przypadkach, są prostsze rozwiązania twojego
284 
+problemu, które w dalszym ciągu pozwolą użytkownikom bezpiecznie łączyć się
285 
+z Twoim serwisem.</p>
286 
+
287 
+<p>Po pierwsze, zadaj sobie pytanie, czy można oddzielić właściwych
288 
+użytkowników od pacanów na poziomie aplikacji. Na przykład, mógłbyś mieć
289 
+pewne obszary strony lub pewne przywileje jak wysyłanie wiadomości, dostępne
290 
+tylko dla użytkowników zarejestrowanych. Łatwo jest stworzyć aktualną listę
291 
+adresów IP Tora, które pozwalają na łączenie się z Twoją stroną, więc
292 
+mógłbyś to rozróżnienie zrobić tylko dla użytkowników Tora. W ten sposób
293 
+dostajesz ochronę dostępu i nie musisz blokować całego serwisu. </p>
294 
+
295 
+<p>Na przykład, sieć <a href="http://freenode.net/policy.shtml#tor">Freenode
296 
+IRC</a> miała problem ze skoordynowaną grupą osób nadużywających, które
297 
+przyłączały się do kanałów i subtelnie przejmowały rozmowy; ale kiedy
298 
+oznaczyli wszystkich użytkowników łączących się z Tora jako "anonimowych",
299 
+pozbawiając ich możliwości wtopienia się w kanał, te osoby wyniosły się z
300 
+powrotem do używania swoich anonimowych serwerów proxy i sieci botów. </p>
301 
+
302 
+<p>Po drugie pomyśl, że setki tysięcy ludzi używają Tora codziennie po prostu
303 
+do "dobrej higieny danych" &mdash; na przykład, by chronić się przed
304 
+zbierającymi informacje firmami reklamowymi, w czasie swoich normalnych
305 
+czynności. Inni używają Tora, gdyż jest to ich jedyny sposób na przejście
306 
+przez restrykcyjne lokalne zapory ogniowe. Niektórzy użytkownicy Tora mogą
307 
+właśnie teraz legalnie łączyć się z Twoim serwisem, by wykonywać swoje
308 
+normalne czynności. Musisz zdecydować, czy blokowanie sieci Tora jest warte
309 
+utraty wkładu tych użytkowników, jak również potencjalnych przyszłych
310 
+legalnych użytkowników. (Często ludzie nie wiedzą, ilu dobrych użytkowników
311 
+Tora łączy się z ich serwisem &mdash; tego się nie zauważa, dopóki nie
312 
+pojawi się jakiś nieuprzejmy.)</p>
313 
+
314 
+<p>Teraz powinieneś się zapytać samego siebie, co zrobić z usługami grupującymi
315 
+wielu użytkowników za kilkoma adresami IP. Tor w tej kwestii nie różni się
316 
+za bardzo od AOL.</p>
317 
+
318 
+<p>Ostatecznie, proszę pamiętać, że przekaźniki sieci Tora mają <a href="<page
319 
+faq>#ExitPolicies">indywidualne polityki wyjścia</a>. Wiele przekaźników
320 
+Tora w ogóle nie zezwala na połączenia wychodzące. Wiele z tych, które
321 
+zezwalają na pewne połączenia wychodzące może już blokować połączenia z
322 
+Twoim serwisem.  Jeśli chcesz blokować węzły Tora, przejrzyj ich polityki
323 
+wyjścia i blokuj tylko te, które pozwalają na połączenia z Twoją stroną;
324 
+pamiętaj, że polityki wyjścia mogą się zmieniać (podobnie jak lista węzłów w
325 
+sieci).</p>
326 
+
327 
+<p>Jeśli naprawdę chcesz to zrobić, mamy <a
328 
+href="https://check.torproject.org/cgi-bin/TorBulkExitList.py">listę punktów
329 
+wyjściowych Tora</a> i <a href="<page tordnsel/index>">opartą na DNS listę,
330 
+do której można wysyłać zapytania</a>.
331 
+</p>
332 
+
333 
+<p>
334 
+(Niektórzy administratorzy blokują zakresy adresów IP z przyczyn oficjalnej
335 
+polityki lub pewnych wzorców nadużyć, ale niektórzy pytali o możliwość
336 
+znalezienia węzłów wyjściowych Tora w celu ich odblokowania, gdyż chcą dać
337 
+dostęp do swoich systemów wykorzystując tylko Tora. Te skrypty są przydatne
338 
+także do tworzenia "białych list".)
339 
+</p>
340 
+
341 
+<a id="TracingUsers"></a>
342 
+<h3><a class="anchor" href="#TracingUsers">Mam dobry powód, by śledzić
343 
+użytkownika Tora. Możecie mi pomóc?</a></h3>
344 
+
345 
+<p>
346 
+Deweloperzy Tora nie mogą nic zrobić, by wyśledzić użytkowników Tora. Te
347 
+same mechanizmy ochrony, które uniemożliwiają złym ludziom złamanie
348 
+anonimowości Tora również uniemożliwiają nam dowiedzieć się, co się dzieje.
349 
+</p>
350 
+
351 
+<p>
352 
+Niektórzy z fanów sugerowali, byśmy przeprojektowali Tora, tak by zawierał
353 
+<a href="<page faq>#Backdoor">tylne drzwi</a>.  Z tym pomysłem wiążą się dwa
354 
+problemy. Po pierwsze, to zbytnio osłabia system ze strony
355 
+technicznej. Posiadanie zcentralizowanego sposobu na połączenie użytkowników
356 
+z ich działaniami jest otwartą dziurą dla napastników wszelkiego typu; a
357 
+mechanizmy polityki potrzebne do poprawnej obsługi tej odpowiedzialności są
358 
+ogromne i nierozwiązane. Po drugie, źli ludzie <a
359 
+href="#WhatAboutCriminals">i tak się w to nie złapią</a>, gdyż użyją innych
360 
+środków by zapewnić sobie anonimowość (kradzież tożsamości, włamywanie się
361 
+do komputerów i używanie ich do przekierowania swojego ruchu itd.).
362 
+</p>
363 
+
364 
+<p>
365 
+Pamiętać należy jednak, że to nie znaczy, że Tor jest nie
366 
+narażony. Tradycyjne techniki policyjne w dalszym ciągu mogą być efektywne
367 
+względem Tora, jak np. przesłuchiwanie podejrzanych, pluskwy podsłuchowe i
368 
+na klawiaturę, analiza charakteru pisma, operacje specjalne i inne fizyczne
369 
+środki śledcze.
370 
+</p>
371 
+
372 
+<a id="RemoveContent"></a>
373 
+<h3><a class="anchor" href="#RemoveContent">Chcę, aby usunięto jakąś treść z
374 
+adresu .onion.</a></h3>
375 
+<p>Projekt Tor nie hostuje, nie kontroluje ani nie ma możliwości odkrycia
376 
+właściciela lub lokalizacji adresu .onion. Adres .onion jest adresem <a
377 
+href="<page docs/tor-hidden-service>">usługi ukrytej</a>. Nazwa zakończona
378 
+na .onion, którą widzisz, jest deskryptorem usługi ukrytej. Jest to
379 
+generowana automatycznie nazwa, która może znajdować się na każdym
380 
+przekaźniku lub kliencie Tora w dowolnym miejscu Internetu. Usługi ukryte są
381 
+zaprojektowane tak, by chronić zarówno użytkownika, jak i dostawcę usługi,
382 
+przed odkryciem, kim są i skąd pochodzą. Projekt usług ukrytych oznacza, że
383 
+właściciel i lokalizacja strony .onion jest ukryta nawet przed nami.</p>
384 
+<p>Ale pamiętaj, że to nie oznacza, że usługi ukryte nie są podatne na
385 
+ataki. Tradycyjne techniki policyjne mogą nadal być przeciwko nim efektywne,
386 
+jak na przykład przesłuchania podejrzanych, pluskwy podsłuchowe i na
387 
+klawiaturę, analiza charakteru pisma, operacje specjalne i inne fizyczne
388 
+środki śledcze.</p>
389 
+<p>Jeśli otrzymałeś/aś skargę o dziecięcej pornografii, zgłoś ją do National
390 
+Center for Missing and Exploited Children, który jest narodowym punktem
391 
+koordynacji działań odnośnie dziecięcej pornografii: <a
392 
+href="http://www.missingkids.com/">http://www.missingkids.com/</a>. Nie
393 
+oglądamy linków, które zgłaszasz.</p>
394 
+
395 
+<a id="LegalQuestions"></a>
396 
+<h3><a class="anchor" href="#LegalQuestions">Mam pytania prawne dotyczące
397 
+nadużyć Tora.</a></h3>
398 
+
399 
+<p>My jesteśmy tylko deweloperami. Możemy odpowiadać na pytania techniczne, ale
400 
+to nie z nami należy rozmawiać o sprawach prawnych. </p>
401 
+
402 
+<p>Spójrz na <a href="<page eff/tor-legal-faq>">Prawne FAQ Tora</a>, i
403 
+skontaktuj się bezpośrednio z EFF, jeśli będziesz miał jakiekolwiek dalsze
404 
+pytania prawne. </p>
405 
+
406 
+  </div>
407 
+
408 
+
409 
+#include <foot.wmi>
pl/faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,1207 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22360 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor FAQ" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>FAQ Tora</h2>
17 
+<hr />
18 
+
19 
+<p>Pytania ogólne:</p>
20 
+<ul>
21 
+<li><a href="#WhatIsTor">Czym jest Tor?</a></li>
22 
+<li><a href="#Torisdifferent">Czym różni się Tor od innych serwerów proxy?</a></li>
23 
+<li><a href="#CompatibleApplications">Jakich programów mogę używać z Torem?</a></li>
24 
+<li><a href="#WhyCalledTor">Czemu się to nazywa Tor?</a></li>
25 
+<li><a href="#Backdoor">Czy jest tylna furtka w Torze?</a></li>
26 
+<li><a href="#DistributingTor">Czy mogę rozprowadzać Tora na płycie CD mojego
27 
+magazynu?</a></li>
28 
+<li><a href="#SupportMail">Jak mogę dostać odpowiedź na mój list o Torze?</a></li>
29 
+<li><a href="#WhySlow">Czemu Tor jest taki powolny?</a></li>
30 
+<li><a href="#Funding">Co Projekt Tor zrobiłby z większymi funduszami?</a></li>
31 
+</ul>
32 
+
33 
+<p>Kompilacja i instalacja:</p>
34 
+<ul>
35 
+<li><a href="#HowUninstallTor">Jak odinstalować Tora?</a></li>
36 
+<li><a href="#PGPSigs">Czym są te pliki "sig" na stronie pobierania?</a></li>
37 
+<li><a href="#CompileTorWindows">Jak skompilować Tora pod Windows?</a></li>
38 
+<li><a href="#VirusFalsePositives">Czemu mój program Tor zdaje się mieć wirusa
39 
+lub oprogramowanie szpiegujące?</a></li>
40 
+<li><a href="#LiveCD">Czy jest LiveCD lub inna dystrybucja/paczka zawierająca
41 
+Tora?</a></li>
42 
+</ul>
43 
+
44 
+<p>Uruchamianie Tora:</p>
45 
+
46 
+<p>Uruchamianie klienta Tora:</p>
47 
+<ul>
48 
+<li><a href="#ChooseEntryExit">Czy mogę kontrolować, które węzły (lub kraje) są
49 
+używane do wchodzenia/wychodzenia?</a></li>
50 
+</ul>
51 
+
52 
+<p>Uruchamianie przekaźnika sieci Tora:</p>
53 
+<ul>
54 
+<li><a href="#RelayFlexible">Jak stabilny musi być mój przekaźnik?</a></li>
55 
+<li><a href="#ExitPolicies">Prowadziłbym/prowadziłabym przekaźnik, ale nie chcę
56 
+mieć do czynienia z przypadkami nadużyć.</a></li>
57 
+<li><a href="#RelayOrBridge">Czy powinienem/am prowadzić normalny przekaźnik,
58 
+czy przekaźnik mostkowy?</a></li>
59 
+<li><a href="#RelayMemory">Czemu mój przekaźnik Tora zużywa tyle pamięci?</a></li>
60 
+<li><a href="#WhyNotNamed">Czemu mój przekaźnik Tora nie ma nazwy?</a></li>
61 
+</ul>
62 
+
63 
+<p>Uruchamianie usługi ukrytej Tora:</p>
64 
+
65 
+<p>Anonimowość i bezpieczeństwo:</p>
66 
+<ul>
67 
+<li><a href="#KeyManagement">Opowiedzcie mi o wszystkich kluczach używanych
68 
+przez Tora.</a></li>
69 
+</ul>
70 
+
71 
+<p>Alternatywne projeky, których nie robimy (jeszcze):</p>
72 
+<ul>
73 
+<li><a href="#EverybodyARelay">Powinno się sprawić, by każdy użytkownik Tora był
74 
+przekaźnikiem.</a></li>
75 
+</ul>
76 
+
77 
+<p>Nadużycie</p>
78 
+<ul>
79 
+<li><a href="#Criminals">Czy Tor nie umożliwia przestępcom robienia złych
80 
+rzeczy?</a></li>
81 
+<li><a href="#RespondISP">Jak odpowiadać mojemu dostawcy internetu o moim
82 
+przekaźniku wyjściowym?</a></li>
83 
+</ul>
84 
+
85 
+<p>For other questions not yet on this version of the FAQ, see the <a
86 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">wiki
87 
+FAQ</a> for now.</p>
88 
+
89 
+<hr />
90 
+
91 
+<a id="General"></a> <a id="WhatIsTor"></a>
92 
+<h3><a class="anchor" href="#WhatIsTor">Czym jest Tor?</a></h3>
93 
+
94 
+<p>
95 
+Nazwa "Tor" może odnosić się do kilku różnych komponentów.
96 
+</p>
97 
+
98 
+<p>
99 
+Oprogramowanie Tor to program, który możesz uruchomić na swoim komputerze i
100 
+który pomaga w zachowaniu bezpieczeństwa w Internecie. Tor chroni Cię,
101 
+przekazując Twój ruch sieciowy poprzez rozproszoną sieć przekaźników
102 
+uruchamianych przez wolontariuszy na całym świecie: zapobiega podglądaniu
103 
+Twojego łącza internetowego w celu poznania listy stron, które odwiedzasz, i
104 
+zapobiega poznaniu Twojej fizycznej lokalizacji przez strony, które
105 
+odwiedzasz. Ten zestaw przekaźników jest nazywany siecią Tora. Możesz
106 
+dowiedzieć się więcej o tym, jak działa Tor na <a href="<page
107 
+overview>">stronie wprowadzenia</a>.
108 
+</p>
109 
+
110 
+<p>
111 
+Projekt Tor jest organizacją non-profit (dobroczynną), która zajmuje się i
112 
+rozwija oprogramowanie Tor.
113 
+</p>
114 
+
115 
+<hr />
116 
+
117 
+<a id="Torisdifferent"></a>
118 
+<h3><a class="anchor" href="#Torisdifferent">Czym różni się Tor od innych
119 
+serwerów proxy?</a></h3>
120 
+<p>
121 
+Typowi dostawcy proxy uruchamiają serwer gdzieś w Internecie i umożliwiają
122 
+Ci korzystanie z niego do przekierowywania swojego ruchu. To stwarza prostą,
123 
+łatwą do utrzymania architekturę. Wszyscy użytkownicy wchodzą i wychodzą
124 
+przez ten sam serwer. Dostawca może pobierać opłaty za korzystanie z proxy
125 
+lub pokrywać koszty z reklam na serwerze. W najprostszej konfiguracji nie
126 
+musisz nic instalować. Wystarczy, że skierujesz swoją przeglądarkę na ich
127 
+serwer proxy. Dostawcy prostych proxy są dobrym rozwiązaniem, jeśli nie
128 
+chcesz chronić swojej prywatności i anonimowości on-line i ufasz, że
129 
+dostawca nie robi nic złego. Niektórzy dostawcy prostych proxy używają SSL,
130 
+by zabezpieczyć Twoje połączenia do nich. Może Cię to ochronić przed
131 
+lokalnymi podsłuchiwaczami, jak na przykład w kawiarence z darmowym
132 
+internetem wifi.
133 
+</p>
134 
+<p>
135 
+Dostawcy prostych proxy dają też pojedynczy niedobry punkt. Wiedzą, kim
136 
+jesteś i co oglądasz w Internecie. Mogą obserwować Twój ruch, jak przechodzi
137 
+przez ich serwer. W niektórych przypadkach mogą obserwować Twój zaszyfrowany
138 
+ruch, gdy przekierowują go do strony Twojego banku lub sklepów
139 
+internetowych. Musisz im ufać, że nie robią żadnej z takich rzeczy jak
140 
+obserwacja ruchu, wstrzykiwanie własnych reklam w Twój ruch czy zapisywanie
141 
+szczegółów o Tobie.
142 
+</p>
143 
+<p>
144 
+Tor przekazuje Twój ruch przez co najmniej 3 różne serwery, zanim wyśle go
145 
+do miejsca przeznaczenia. Tor nie zmienia ani nawet nie wie, co przez niego
146 
+wysyłasz. Tylko przekierowuje Twój ruch, całkowicie zaszyfrowany, przez sieć
147 
+Tora i sprawia, że wyskakuje gdzieś indziej na świecie, całkowicie
148 
+nienaruszony. Klient Tora jest wymagany, gdyż zakładamy, że masz zaufanie do
149 
+swojego komputera. Klient Tora zarządza szyfrowaniem i wybraną ścieżką przez
150 
+sieć Tora. Przekaźniki rozmieszczone na całym świecie tylko przekazują
151 
+zaszyfrowane pakiety między sobą.</p>
152 
+<p>
153 
+<dl>
154 
+<dt>Czy pierwszy serwer nie widzi, kim jestem?</dt><dd>Być może. Zły pierwszy z trzech serwerów może widzieć zaszyfrowany ruch Tora
155 
+pochodzący z Twojego komputera. Ale ciągle nie wie, kim jesteś i co robisz
156 
+przez Tora. Po prostu widzi "Ten adres IP używa Tora". Tor nie jest nigdzie
157 
+nielegalny, więc korzystanie z samego Tora jest w porządku. Jesteś ciągle
158 
+chroniony/a przed tym, by ten węzeł odkrył, kim jesteś i dokąd idziesz w
159 
+Internecie.</dd>
160 
+<dt>Czy trzeci serwer nie widzi mojego ruchu?</dt><dd>Być może. Zły trzeci z trzech serwerów może widzieć ruch, który wysłałeś do
161 
+Tora. Nie będzie wiedział, kto wysłał te dane. Jeśli używasz szyfrowania,
162 
+jak przy odwiedzaniu stron banków czy e-sklepów lub szyfrowanych połączeń do
163 
+poczty itd., będzie tylko znał przeznaczenie. Nie będzie widział danych w
164 
+strumieniu ruchu.  Jesteś ciągle chroniony/a przed tym, by ten węzeł odkrył,
165 
+kim jesteś, a jeśli używasz szyfrowania - także przed zobaczeniem Twoich
166 
+danych wysyłanych do ich miejsca przeznaczenia.</dd>
167 
+</dl>
168 
+</p>
169 
+
170 
+<hr />
171 
+
172 
+<a id="CompatibleApplications"></a>
173 
+<h3><a class="anchor" href="#CompatibleApplications">Jakich programów mogę
174 
+używać z Torem?</a></h3>
175 
+
176 
+<p>
177 
+Są dwa elementy "toryfikacji" programu: anonimowość na poziomie połączenia i
178 
+anonimowość na poziomie aplikacji. Anonimowość na poziomie połączenia skupia
179 
+się na zapewnianiu tego, by ruch sieciowy aplikacji był wysyłany przez
180 
+Tora. Jest to zazwyczaj robione tak, że program jest konfigurowany do
181 
+używania Twojego klienta Tora jako serwer pośredniczący (proxy) typu
182 
+"socks", ale są też inne sposoby. Jeśli chodzi o anonimowość na poziomie
183 
+aplikacji, musisz upewnić się, że informacje wysyłane przez aplikację nie
184 
+szkodzą Twojej prywatności. (Nawet jeśli połączenia są przekierowywane przez
185 
+Tora, nie jest wskazane przekazywanie takich informacji jak nazwisko.) Ten
186 
+drugi krok musi być robiony w każdym programie inaczej, co jest powodem
187 
+tego, że nie polecamy jeszcze wielu programów do bezpiecznego używania z
188 
+Torem.
189 
+</p>
190 
+
191 
+<p>
192 
+Większość naszej dotychczasowej pracy skupiła się na przeglądarce
193 
+internetowej Firefox. Paczki na <a href="<page download>">stronie
194 
+pobierania</a> automatycznie instalują <a href="<page
195 
+torbutton/index>">rozszerzenie Torbutton do Firefoksa</a>, jeśli masz
196 
+zainstalowanego Firefoksa. Od wersji 1.2.0 Torbutton usuwa wiele problemów
197 
+poziomów połączenia i aplikacji.
198 
+</p>
199 
+
200 
+<p>
201 
+There are plenty of other programs you can use with Tor, but we haven't
202 
+researched the application-level anonymity issues on them well enough to be
203 
+able to recommend a safe configuration. Our wiki has a list of instructions
204 
+for <a
205 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">Torifying
206 
+specific applications</a>. There's also a <a
207 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">list
208 
+of applications that help you direct your traffic through Tor</a>.  Please
209 
+add to these lists and help us keep them accurate!
210 
+</p>
211 
+
212 
+<hr />
213 
+
214 
+<a id="WhyCalledTor"></a>
215 
+<h3><a class="anchor" href="#WhyCalledTor">Czemu się to nazywa Tor?</a></h3>
216 
+
217 
+<p>
218 
+Gdyż Tor jest siecią trasowania cebulowego (ang. The Onion Routing). Gdy
219 
+zaczynaliśmy nowy projekt kolejnej generacji i implementację trasowania
220 
+cebulowego w 2001-2002, mówiliśmy ludziom, że pracujemy nad trasowaniem
221 
+cebulowym, a oni odpowiadali "Fajnie. Ale nad którym?". Nawet jeśli
222 
+trasowanie cebulowe stało się terminem powszechnym, Tor narodził się z tego
223 
+właściwego <a href="http://www.onion-router.net/">projektu trasowania
224 
+cebulowego</a>, prowadzonego przez Laboratorium Badawcze Marynarki Wojennej.
225 
+</p>
226 
+
227 
+<p>
228 
+(Ma też niezłe tłumaczenie z niemieckiego i tureckiego.)
229 
+</p>
230 
+
231 
+<p>
232 
+Uwaga: mimo iż pochodzi od skrótu, słowa Tor nie pisze się "TOR". Tylko
233 
+pierwsza litera jest wielka. W zasadzie zauważamy kogoś, kto nie przeczytał
234 
+naszej strony (i dowiedział się wszystkiego o Torze z artykułów), po tym, że
235 
+źle literuje nazwę.
236 
+</p>
237 
+
238 
+<hr />
239 
+
240 
+<a id="Backdoor"></a>
241 
+<h3><a class="anchor" href="#Backdoor">Czy jest tylna furtka w Torze?</a></h3>
242 
+
243 
+<p>
244 
+Nie ma absolutnie żadnego tylnego wejścia do Tora. Nikt nie prosił nas,
245 
+abyśmy takie zrobili, a znamy kilku mądrych prawników, którzy mówią, że mało
246 
+prawdopodobne jest, by ktoś zmusił nas do zrobienia czegoś takiego w naszej
247 
+jurysdykcji (Stany Zjednoczone). Jeśli nas o to poproszą, będziemy z nimi
248 
+walczyć, i (jak mówią prawnicy) prawdopodobnie wygramy.
249 
+</p>
250 
+
251 
+<p>
252 
+Naszym zdaniem umieszczenie tylnego wejścia do systemu Tor byłoby
253 
+niesamowicie nieodpowiedzialne względem naszych użytkowników i złym
254 
+precedensem w ogóle w dziedzinie oprogramowania do bezpieczeństwa. Jeśli
255 
+kiedykolwiek umieścilibyśmy celowe tylne wejście w naszym oprogramowaniu do
256 
+bezpieczeństwa, zrujnowałoby to nasze zawodowe reputacje. Nikt już by nigdy
257 
+nie zaufał naszym programom &mdash; z doskonałego powodu!
258 
+</p>
259 
+
260 
+<p>
261 
+Ale to rzekłszy, jest jeszcze sporo subtelnych ataków, których różni ludzie
262 
+mogą próbować. Ktoś mógłby podszywać się pod nas, włamać się na nasze
263 
+komputery lub coś w tym stylu. Tor jest programem o otwartym kodzie i zawsze
264 
+powinieneś/aś sprawdzać kod (lub chociaż pliki różnic od ostatniego
265 
+wydania), czy nie ma tam czegoś podejrzanego. Jeśli my (lub inni
266 
+dystrybutorzy) nie damy Ci kodu, jest to pewny znak, że dzieje się coś
267 
+dziwnego. Powinieneś/aś też sprawdzać <a href="<page
268 
+verifying-signatures>">sygnatury PGP</a>, by upewnić się, że nikt nie
269 
+grzebał w miejscach dystrybucji.
270 
+</p>
271 
+
272 
+<p>
273 
+Ponadto, w Torze mogą znaleźć się przypadkowe błędy, które mogłyby wpłynąć
274 
+na Twoją anonimowość. Okresowo szukamy i usuwamy błędy związane z
275 
+anonimowością, więc zawsze używaj najnowszej wersji Tora.
276 
+</p>
277 
+
278 
+<hr />
279 
+
280 
+<a id="DistributingTor"></a>
281 
+<h3><a class="anchor" href="#DistributingTor">Czy mogę rozprowadzać Tora na
282 
+płycie CD mojego magazynu?</a></h3>
283 
+
284 
+<p>
285 
+Tak.
286 
+</p>
287 
+
288 
+<p>
289 
+Oprogramowanie Tor jest <a href="https://www.fsf.org/">Wolnym
290 
+Oprogramowaniem (Free Software)</a>. To znaczy, że dajemy Ci prawo do
291 
+rozpowszechniania programu Tor, ze zmianami lub bez, za opłatą lub za
292 
+darmo. Nie musisz nas pytać o szczególne pozwolenie.
293 
+</p>
294 
+
295 
+<p>
296 
+Lecz jeśli planujesz rozpowszechniać program Tor, musisz trzymać się naszej
297 
+<a href="<gitblob>LICENSE">licencji</a>. W skrócie znaczy to tyle, że musisz
298 
+dołączyć nasz plik LICENSE z jakąkolwiek częścią programu Tor, którą
299 
+rozpowszechniasz.
300 
+</p>
301 
+
302 
+<p>
303 
+Większość ludzi zadająca nam to pytanie nie chce rozpowszechniać tylko
304 
+programu Tor. Chcą dystrybuować paczki z Torem, które zazwyczaj zawierają
305 
+programy <a
306 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> i <a
307 
+href="<page vidalia/index>">Vidalia</a>. Musisz się wtedy trzymać też
308 
+licencji tych programów. Oba są pod licencją <a
309 
+href="https://www.fsf.org/licensing/licenses/gpl.html">GNU General Public
310 
+License</a>. Najprostszym sposobem na spełnienie licencji jest dołączenie
311 
+kodu źródłowego tych programów gdziekolwiek, gdzie umieszczasz
312 
+paczki. Szukaj paczek "source" ("kod źródłowy") na <a href="<page
313 
+vidalia/index>">stronie Vidalii</a> i <a
314 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/">stronie pobierania
315 
+Polipo</a>.
316 
+</p>
317 
+
318 
+<p>
319 
+Ponadto, powinieneś/aś uważać, by nie wprowadzać w błąd swoich czytelników
320 
+odnośnie tego, czym jest Tor, kto go robi i co on daje (a czego
321 
+nie). Przeczytaj nasze <a href="<page trademark-faq>">FAQ o znaku
322 
+handlowym</a> po więcej szczegółów.
323 
+</p>
324 
+
325 
+<p>
326 
+I na koniec, powinieneś/aś zdawać sobie sprawę z tego, że nowe wersje
327 
+programu Tor wydajemy często i czasem dokonujemy zmian niezgodnych
328 
+wstecz. Więc jeśli rozprowadzasz konkretną wersję programu Tor, może ona nie
329 
+być obsługiwana &mdash; ani nawet działać &mdash; już sześć miesięcy
330 
+później. Tak jest z każdym oprogramowaniem dotyczącym bezpieczeństwa, które
331 
+jest aktywnie rozwijane.
332 
+</p>
333 
+
334 
+<hr />
335 
+
336 
+<a id="SupportMail"></a>
337 
+<h3><a class="anchor" href="#SupportMail">Jak mogę dostać odpowiedź na mój list
338 
+o Torze?</a></h3>
339 
+
340 
+<p>
341 
+Wiele osób wysyła listy do deweloperów Tora prywatnie lub na nasze
342 
+wewnętrzne <a href="<page contact>">listy mailingowe</a>, z pytaniami
343 
+dotyczącymi swojej konfiguracji &mdash; nie mogą sprawić, by firewall
344 
+działał, nie mogą skonfigurować Polipo itd. Czasem nasi ochotnicy mogą
345 
+odpowiedzieć na te pytania, ale zazwyczaj muszą spędzać większość czasu na
346 
+zadaniach programistycznych, dzięki którym zyskamy więcej ludzi. Jest to
347 
+zwłaszcza prawdą, gdy na Twoje pytanie jest już odpowiedź w <a href="<page
348 
+documentation>">dokumentacji</a> lub w tym FAQ.
349 
+</p>
350 
+
351 
+<p>
352 
+Tak więc, jeśli nie odpowiadamy na Twój list, najpierw sprawdź stronę z <a
353 
+href="<page documentation>">dokumentacją</a>, oraz to FAQ, by sprawdzić, czy
354 
+na Twoje pytanie nie ma już gotowej odpowiedzi. Potem przeczytaj <a
355 
+href="http://www.catb.org/~esr/faqs/smart-questions.html">"Jak mądrze
356 
+zadawać mądre pytania"</a>. Jeśli to nie pomoże, mamy <a href="<page
357 
+documentation>#Support">kanał IRC</a>, gdzie możesz zadawać pytania (ale
358 
+jeśli ciagle będą źle sformułowane lub nie o Torze, tam też pewnie nie
359 
+dostaniesz wielu odpowiedzi). W ostateczności, ludzie na <a href="<page
360 
+documentation>#MailingLists" >liście mailingowej or-talk</a> mogą Ci dać
361 
+parę wskazówek, jeśli inni doznali tych samych problemów, co Ty. Najpierw
362 
+jednak przejrzyj <a href="http://archives.seul.org/or/talk/">archiwa</a>.
363 
+</p>
364 
+
365 
+<p>
366 
+Inną strategią jest <a href="<page docs/tor-doc-relay>">prowadzenie
367 
+przekaźnika sieci Tor przez jakiś czas</a>, lub <a href="<page
368 
+donate>">dotacja pieniędzy</a> <a href="<page volunteer>">albo czasu</a> na
369 
+naszą sprawę. Chętniej zwrócimy uwagę na pytania osób, które pokazały
370 
+zainteresowanie i poświęcenie, by dać coś społeczności Tora.
371 
+</p>
372 
+
373 
+<p>
374 
+Jeśli znajdziesz swoją odpowiedź, zostań na kanale IRC lub liście
375 
+mailingowej i odpowiadaj na pytania od innych.
376 
+</p>
377 
+
378 
+<hr />
379 
+
380 
+<a id="WhySlow"></a>
381 
+<h3><a class="anchor" href="#WhySlow">Czemu Tor jest taki powolny?</a></h3>
382 
+
383 
+<p>
384 
+Jest wiele powodów, dlaczego sieć Tora jest w tej chwili powolna.
385 
+</p>
386 
+
387 
+<p>
388 
+Zanim odpowiemy na to pytanie, powinieneś/aś zdać sobie sprawę, że Tor nigdy
389 
+nie będzie działał błyskawicznie. Twój ruch sieciowy jest przekierowywany
390 
+przez komputery ochotników z różnych części świata i pewne wąskie gardła i
391 
+przestoje zawsze będą obecne. Nie oczekuj, że przez Tora osiągniesz
392 
+przepustowość w stylu uczelni.
393 
+</p>
394 
+
395 
+<p>
396 
+Ale to wszystko nie znaczy, że nie można polepszyć stanu rzeczy. Aktualna
397 
+sieć Tora jest dość mała w porównaniu z liczbą ludzi, którzy próbują jej
398 
+używać, a wielu z tych ludzi nie rozumie lub nie obchodzi ich, że Tor nie
399 
+może teraz dać sobie rady z obciążeniem powodowanym przez współdzielenie
400 
+plików.
401 
+</p>
402 
+
403 
+<p>
404 
+Jeśli chcesz bardziej wyczerpującą odpowiedź, przeczytaj <a
405 
+href="https://blog.torproject.org/blog/why-tor-is-slow">wiadomość na blogu
406 
+Rogera o tym temacie</a>, która zawiera zarówno szczegółowy PDF, jak i
407 
+towarzyszące wideo.
408 
+</p>
409 
+
410 
+<p>
411 
+Jak możesz pomóć?
412 
+</p>
413 
+
414 
+<ul>
415 
+
416 
+<li>
417 
+<a href="<page docs/tor-doc-relay>">Skonfiguruj swojego Tora, by przekazywał
418 
+ruch innych</a>. Pomóż uczynić sieć Tora dość dużą, byśmy mogli obsłużyć
419 
+wszystkich ludzi, którzy chcą prywatności i bezpieczeństwa w Internecie.
420 
+</li>
421 
+
422 
+<li>
423 
+<a href="<page gui/index>">Pomóż uczynić Tora łatwiejszym w
424 
+użyciu</a>. Potrzebujemy zwłaszcza ludzi, którzy pomogą ułatwić konfigurację
425 
+Tora jako przekaźnika sieci. Ponadto, potrzebujemy pomocy w stworzeniu
426 
+jasnej, prostej dokumentacji, która poprowadzi ludzi w procesie
427 
+konfiguracji.
428 
+</li>
429 
+
430 
+<li>
431 
+Są pewne wąskie gardła w aktualnej sieci Tora. Pomóż nam zaprojektować
432 
+eksperymenty, które pozwolą na wyśledzenie i zademonstrowanie, gdzie są
433 
+problemy, a wtedy my będziemy mogli bardziej skupić się na ich naprawieniu.
434 
+</li>
435 
+
436 
+<li>
437 
+There are some steps that individuals can take to improve their Tor
438 
+performance. <a
439 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/FireFoxTorPerf">You
440 
+can configure your Firefox to handle Tor better</a>, <a
441 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
442 
+Polipo with Tor</a>, or you can try <a href="<page download>">upgrading to
443 
+the latest version of Tor</a>.  If this works well, please help by
444 
+documenting what you did, and letting us know about it.
445 
+</li>
446 
+
447 
+<li>
448 
+Tor wymaga też trochę zmian architektury. Jedną z ważnych zmian jest
449 
+rozpoczęcie dostarczania <a href="#EverybodyARelay">lepszej obsługi ludziom,
450 
+którzy prowadzą przekaźniki sieci</a>. Pracujemy nad tym, a skończymy
451 
+szybciej, jeśli uda nam się spędzić przy tym więcej czasu.
452 
+</li>
453 
+
454 
+<li>
455 
+Pomóż robić inne rzeczy, abyśmy my mogli się zająć tym, co trudne. Zastanów
456 
+się chwilę nad swoimi umiejętnościami i zainteresowaniami, po czym <a
457 
+href="<page volunteer>">zajrzyj na naszą stronę dla ochotników</a>.
458 
+</li>
459 
+
460 
+<li>
461 
+Pomóż znaleźć sponsorów dla Tora. Czy pracujesz dla firmy lub agencji
462 
+rządowej, która używa Tora lub korzysta z anonimowości w Internecie, np. by
463 
+dyskretnie przeglądać strony internetowe konkurencji, lub łączyć się z
464 
+serwerami w czasie podróży bez odkrywania swoich powiązań? Jeśli Twoja
465 
+organizacja ma interes w tym, by sieć Tora działała, prosimy skontaktuj się
466 
+z nimi odnośnie wspierania Tora. Bez sponsorów, Tor stanie się jeszcze
467 
+wolniejszy.
468 
+</li>
469 
+
470 
+<li>
471 
+Jeśli nie możesz pomóc na żaden z powyższych sposobów, możesz pomóc
472 
+indywidualnie, poprzez <a href="<page donate>">złożenie skromnej dotacji dla
473 
+naszej sprawy</a>. To się przydaje!
474 
+</li>
475 
+
476 
+</ul>
477 
+
478 
+<hr />
479 
+
480 
+<a id="Funding"></a>
481 
+<h3><a class="anchor" href="#Funding">Co Projekt Tor zrobiłby z większymi
482 
+funduszami?</a></h3>
483 
+
484 
+<p>
485 
+W tej chwili mamy około 1800 przekaźników sieci, ze średnim ruchem 150
486 
+MB/s. Mamy kilkaset tysięcy aktywnych użytkowników. Ale sieć Tora nie jest
487 
+jeszcze samopodtrzymująca się.
488 
+</p>
489 
+
490 
+<p>
491 
+Jest sześć głównych spraw programistycznych i związanych z utrzymaniem,
492 
+które wymagają uwagi:
493 
+</p>
494 
+
495 
+<ul>
496 
+
497 
+<li>
498 
+Skalowalność: musimy ciągle skalować i decentralizować architekturę Tora, by
499 
+mógł obsłużyć tysiące przekaźników i miliony użytkowników. Zbliżająca się
500 
+wersja stabilna jest ważnym krokiem ku lepszemu, ale jest jeszcze wiele do
501 
+zrobienia w następnej kolejności, by utrzymać Tora szybkiego i stabilnego.
502 
+</li>
503 
+
504 
+<li>
505 
+Wsparcie użytkowników: Z taką liczbą użytkowników, wiele osób ciągle zadaje
506 
+pytania, oferuje pomoc w innych sprawach itd. Potrzebujemy dobrej, jasnej
507 
+dokumentacji i musimy poświęcić trochę wysiłku na koordynację wolontariuszy.
508 
+</li>
509 
+
510 
+<li>
511 
+Obsługa przekaźników sieci: sieć Tora jest prowadzona przez wolontariuszy,
512 
+ale oni wymagają uwagi z usuwaniem błędów, tłumaczeniem, czemu coś nie
513 
+działa, przypominaniem o aktualizacjach itd. Sama sieć jest czymś wspólnym i
514 
+ktoś musi poświęcić trochę energii, by operatorzy przekaźników byli
515 
+zadowoleni. Musimy też popracować nad <a href="#RelayOS">stabilnością</a> na
516 
+niektórych systemach &mdash; np. przekaźniki Tora mają aktualnie problemy na
517 
+Win XP.
518 
+</li>
519 
+
520 
+<li>
521 
+Łatwość obsługi: Poza dokumentacją, musimy też popracować nad użytecznością
522 
+samego oprogramowania. W skład tego punktu wchodzą: instalatory, przejrzyste
523 
+GUI, łatwa konfiguracja do współpracy z innymi aplikacjami, i generalnie
524 
+zautomatyzowanie wszystkich trudnych i mylących kroków w Torze. Zaczęliśmy
525 
+już pracę nad tym poprzez <a href="<page gui/index>">konkurs na GUI</a>, ale
526 
+znacznie więcej pracy pozostało &mdash; użyteczność oprogramowania do
527 
+prywatności nigdy nie była łatwa.
528 
+</li>
529 
+
530 
+<li>
531 
+Bodźce: Musimy popracować nad sposobami zachęcania ludzi do konfigurowania
532 
+swoich Torów jako przekaźników sieci i węzłów wyjściowych, zamiast tylko
533 
+jako klientów. <a href="#EverybodyARelay">Musimy sprawić, by łatwo było stać
534 
+się przekaźnikiem i musimy dać ludziom bodźce, by to robili.</a>
535 
+</li>
536 
+
537 
+<li>
538 
+Badania: Obszar komunikacji anonimowej jest pełen niespodzianek i pułapek. W
539 
+naszym wolnym czasie pomagamy prowadzić najważniejsze konferencje o
540 
+anonimowości i prywatności, jak <a
541 
+href="http://petsymposium.org/">PETS</a>. Zidentyfikowaliśmy zestaw
542 
+kluczowych <a href="<page volunteer>#Research">pytań badawczych do Tora</a>,
543 
+które pomogą nam dowiedzieć się, jak zabezpieczyć Tora przed różnymi
544 
+istniejącymi atakami. Oczywiście, za tymi pytaniami kryją się dalsze.
545 
+</li>
546 
+
547 
+</ul>
548 
+
549 
+<p>
550 
+Robimy postępy w każdej z tych rzeczy, ale w tym tempie <a
551 
+href="#WhySlow">sieć Tora rośnie szybciej niż deweloperzy mogą
552 
+nadążyć</a>. Teraz jest idealny moment na dodanie kilku deweloperów do
553 
+sprawy, byśmy mogli kontynuować wzrost sieci.
554 
+</p>
555 
+
556 
+<p>
557 
+Jesteśmy także zainteresowani wzięciem się za problemy powiązane, jak
558 
+ochrona przed cenzurą.
559 
+</p>
560 
+
561 
+<p>
562 
+Jesteśmy dumni z bycia <a href="<page sponsors>">sponsorowanymi i
563 
+wspieranymi</a> przez Omidyar Network, International Broadcasting Bureau,
564 
+Bell Security Solutions, Electronic Frontier Foundation, kilka agencji
565 
+rządowych i grup badawczych, i setki prywatnych osób, które włożyły swój
566 
+wkład w projekt.
567 
+</p>
568 
+
569 
+<p>
570 
+Jednak, to wsparcie jest niewystarczające, by Tor był na bieżąco ze zmianami
571 
+w obszarze prywatności w Internecie. Prosimy <a href="<page donate>">złóż
572 
+dotację</a> do projektu lub <a href="<page contact>">skontaktuj się</a> z
573 
+naszym dyrektorem wykonawczym, by dowiedzieć się, jak dokonywać większych
574 
+wpłat lub grantów.
575 
+</p>
576 
+
577 
+<hr />
578 
+
579 
+<a id="HowUninstallTor"></a>
580 
+<h3><a class="anchor" href="#HowUninstallTor">Jak odinstaloawć Tora?</a></h3>
581 
+
582 
+<p>
583 
+To zależy całkowicie od tego, jak go zainstalowano i jaki posiadasz system
584 
+operacyjny. Jeśli zainstalowałeś/aś paczkę, to ta paczka zna sposób, by się
585 
+odinstalować. Paczki dla Windows zawierają programy
586 
+odinstalowujące. Prawidłowy sposób na całkowite usunięcie Tora, Vidalii,
587 
+Torbuttona dla Firefoksa i Polipo na dowolnym systemie Windows jest
588 
+następujący:
589 
+</p>
590 
+
591 
+<ol>
592 
+<li>Na pasku zadań kliknij prawym klawiszem na Vidalię (zielona cebula lub
593 
+czarna głowa) i wybierz wyjście.</li>
594 
+<li>Kliknij prawym klawiszem na pasek zadań i uruchom Menadżera Zadań. Szukaj
595 
+tor.exe na liście procesów. Jeśli działa, kliknij go prawym klawiszem i
596 
+wybierz Zakończ Proces.</li>
597 
+<li>Kliknij przycisk Start, przejdź do Programy, Vidalia, wybierz Odinstaluj
598 
+(Uninstall). To usunie dystrybucję Vidalii, która zawiera Tora i Polipo.</li>
599 
+<li>Uruchom Firefoksa. Przejdź do menu Narzędzia, wybierz Dodatki. Wybierz
600 
+Torbutton. Kliknij przycisk Odinstaluj.</li>
601 
+</ol>
602 
+
603 
+<p>
604 
+Jeśli nie będziesz trzymać tych kroków (na przykład próbując odinstalować
605 
+Vidalia, Tor i Polipo gdy jeszcze działają), będziesz musiał/a ponownie
606 
+uruchomić komputer i ręcznie usunąć katalog "Program Files\Vidalia Bundle".
607 
+</p>
608 
+
609 
+<p>
610 
+Na systemie Mac OS X, trzymaj się <a href="<page
611 
+docs/tor-doc-osx>#uninstall">instrukcji odinstalowania</a>.
612 
+</p>
613 
+
614 
+<p>
615 
+Jeśli instalowałeś/aś ze źródła, obawiam się, że może nie być łatwego
616 
+sposobu na odinstalowanie. Ale patrząc z jasnej strony, domyślnie wszystko
617 
+instaluję się do /usr/local/, a tam powinno łatwo być zauważyć nowe rzeczy.
618 
+</p>
619 
+
620 
+<hr />
621 
+
622 
+<a id="PGPSigs"></a>
623 
+<h3><a class="anchor" href="#PGPSigs">Czym są te pliki "sig" na stronie
624 
+pobierania?</a></h3>
625 
+
626 
+<p>
627 
+To są podpisy PGP, byście mogli zweryfikować, że plik, który pobraliście,
628 
+jest dokładnie tym, który daliśmy do ściągnięcia.
629 
+</p>
630 
+
631 
+<p>
632 
+Proszę przeczytać stronę o <a href="<page verifying-signatures>">weryfikacji
633 
+podpisów</a>, by dowiedzieć się więcej.
634 
+</p>
635 
+
636 
+<hr />
637 
+
638 
+<a id="CompileTorWindows"></a>
639 
+<h3><a class="anchor" href="#CompileTorWindows">Jak skompilować Tora pod
640 
+Windows?</a></h3>
641 
+
642 
+<p>
643 
+Spróbuj wykonać kroki podane w <a
644 
+href="<gitblob>doc/tor-win32-mingw-creation.txt">
645 
+tor-win32-mingw-creation.txt</a>.
646 
+</p>
647 
+
648 
+<p>
649 
+(Ale zauważ, że nie musisz własnoręcznie kompilować Tora, by go
650 
+używać. Większość ludzi po prostu używa paczek dostępnych na <a href="<page
651 
+download>">stronie pobierania</a>.)
652 
+</p>
653 
+
654 
+<hr />
655 
+
656 
+<a id="VirusFalsePositives"></a>
657 
+<h3><a class="anchor" href="#VirusFalsePositives">Czemu mój program Tor zdaje
658 
+się mieć wirusa lub oprogramowanie szpiegujące?</a></h3>
659 
+
660 
+<p>
661 
+Czasami przesadnie czułe wykrywacze wirusów i programów szpiegujących pod
662 
+Windows podnoszą alarm na niektórych częściach binarki Tora dla
663 
+Windows. Według nas to są prawdopodobnie fałszywe pozytywne wyniki &mdash; w
664 
+końcu rynek antywirusowy i antyszpiegowski to i tak gra w
665 
+zgadywanie. Skontaktuj się z producentem swojego oprogramowania i wytłumacz,
666 
+że masz program, która daje fałszywe pozytywne wyniki. Albo wybierz lepszego
667 
+producenta.
668 
+</p>
669 
+
670 
+<p>
671 
+W międzyczasie, zachęcamy nie brać tego tylko na nasze słowo. Naszym
672 
+zadaniem jest dawanie kodu źródłowego; jeśli jesteś zaniepokojony/a, proszę
673 
+<a href="#CompileTorWindows">skompiluj program własnoręcznie</a>.
674 
+</p>
675 
+
676 
+<hr />
677 
+
678 
+<a id="LiveCD"></a>
679 
+<h3><a class="anchor" href="#LiveCD">Czy jest LiveCD lub inna dystrybucja/paczka
680 
+zawierająca Tora?</a></h3>
681 
+
682 
+<p>
683 
+W chwili obecnej nie ma żadnego oficjalnego LiveCD. Ciągle szukamy dobrych
684 
+rozwiązań i próbujemy zrozumieć implikacje różnych rozwiązań na
685 
+bezpieczeństwo i anonimowość. W międzyczasie przejrzyj poniższą listę i
686 
+wybierz według własnego uznania:
687 
+</p>
688 
+
689 
+<p>
690 
+LiveCD:
691 
+</p>
692 
+
693 
+<ol>
694 
+<li><a href="https://amnesia.boum.org/">The (Amnesic) Incognito Live System</a>
695 
+is a Live System aimed at preserving your privacy and anonymity:
696 
+<ul>
697 
+<li> Wszystkie wychodzące połączenia do Internetu są zmuszane do przechodzenia
698 
+przez sieć Tora.</li>
699 
+<li> Na lokalnych urządzeniach przechowywania danych nie jest zostawiany żaden
700 
+ślad, chyba że jawnie o to poproszono.</li>
701 
+<li> Zawiera programy Firefox, Tor, Torbutton, graficzny kontroler Tora Vidalia,
702 
+program do rozmów Pidgin i mnóstwo innego oprogramowania.</li>
703 
+<li> Opiera się na systemie Debian GNU/Linux i zawiera środowisko pulpitu GNOME.</li>
704 
+</ul>
705 
+<li><a href="http://tork.sourceforge.net/wiki/index.php/LiveCD">TorK LiveCD</a>
706 
+jest oparta na Knoppiksie z naciskiem na przyjazność dla użytkownika. Możesz
707 
+pracować anonimowo lub nie-anonimowo, podczas gdy TorK próbuje ciągle Cię
708 
+informować o konsekwencjach Twoich działań. TorK LiveCD jest
709 
+eksperymentalne, więc celem jest dostarczanie regularnie kolejnych wersji
710 
+przez rok 2007 i później.</li>
711 
+<li><a href="http://mandalka.name/privatix/">Privatix LiveCD/USB</a> jest
712 
+opartym na Debianie systemem zawierającym Tora, Firefoksa i Torbuttona,
713 
+które mogą zapisywać zakładki i inne ustawienia lub dane na zaszyfrowanym
714 
+kluczu USB</li>
715 
+</li>
716 
+</ol>
717 
+
718 
+<p>
719 
+Paczki dla Windows:
720 
+</p>
721 
+
722 
+<ol>
723 
+<li><a href="<page torbrowser/index>">Paczka Tora z przeglądarką</a> dla Windows
724 
+zawiera prekonfigurowaną przeglądarkę internetową i zawiera wszystkie
725 
+niezbędne elementy, więc możesz jej używać z dysku USB.</li>
726 
+<li><a href="http://www.janusvm.com/tor_vm/">Tor VM</a> jest następcą
727 
+JanusVM. Wymaga twojego testowania!</li>
728 
+<li><a href="http://janusvm.com/">JanusVM</a> to jądro Linuksa i oprogramowanie
729 
+działającej w VMWare, które siedzi między Twoim komputerem z Windowsem a
730 
+Internetem, upewniając się, że Twój ruch internetowy jest wymazywany i
731 
+anonimizowany.</li>
732 
+<li><a href="http://www.xerobank.com/xB_browser.html">xB Browser</a>, znane
733 
+dawniej jako Torpark jest paczką Firefox+Tor dla Win32, którą można
734 
+zainstalować na dysku USB. Wymaga systemu Win32, na którym będzie działać.</li>
735 
+</ol>
736 
+
737 
+<p>
738 
+Aktualnie nieutrzymywane, według naszej wiedzy:
739 
+</p>
740 
+
741 
+<ol>
742 
+<li>Polippix / Privatlivets Fred jest duńskim, opartym na Knoppiksie LiveCD z
743 
+Torem i programami do szyfrowania telefonii IP. <a
744 
+href="http://polippix.org/">Informacje i pobieranie</a>.</li>
745 
+<li>ELE to Linux LiveCD skupione na oprogramowaniu związanym z
746 
+prywatnością. Zawiera Tora, a możesz go pobrać z <a
747 
+href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity.net/download/ele/</a>.</li>
748 
+<li>Virtual Privacy Machine is a Linux LiveCD that includes Firefox, Privoxy,
749 
+Tor, some IRC and IM applications, and a set of ipchains rules aimed to
750 
+prevent non-Tor traffic from accidentally leaving your computer. More
751 
+information at <a
752 
+href="https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine">https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine</a>.</li>
753 
+<li>Anonym.OS to LiveCD podobne do powyższych, ale oparte na OpenBSD zamiast na
754 
+Linuksie, by zapewnić maksymalne bezpieczeństwo. Zostało zaprojektowane od
755 
+podstaw, by zapewniać anonimowość i bezpieczeństwo, ma więc kilka cech i
756 
+ograniczeń niespotykanych w innych LiveCD (związanych z Torem lub
757 
+nie). Więcej informacji i pobieranie Anonym.OS jest na stronie <a
758 
+href="http://theory.kaos.to/projects.html">Kaos.Theory</a>.</li>
759 
+<li>Phantomix to LiveCD do anonimowego surfowania i czatowania, oparte na
760 
+najnowszej wersji systemu KNOPPIX. Zawiera prekonfigurowane Provoxy, Tora i
761 
+Polipo. Można je pobrać ze <a href="http://phantomix.ytternhagen.de/">strony
762 
+Phantomix</a>.</li>
763 
+</ol>
764 
+
765 
+<p>
766 
+Proszę się z nami skontaktować, jeśli znacie jakieś inne.
767 
+</p>
768 
+
769 
+<hr />
770 
+
771 
+<a id="ChooseEntryExit"></a>
772 
+<h3><a class="anchor" href="#ChooseEntryExit">Czy mogę kontrolować, które węzły
773 
+(lub kraje) są używane do wchodzenia/wychodzenia?</a></h3>
774 
+
775 
+<p>
776 
+Tak. Możesz ustawić preferowane węzły wejściowe i wyjściowe, jak również
777 
+poinformować Tora, których węzłów nie chcesz używać. Następujące opcje mogą
778 
+być dodane do Twojego pliku konfiguracyjnego "torrc" lub podane na linii
779 
+poleceń:
780 
+</p>
781 
+<dl>
782 
+  <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
783 
+    <dd>Lista preferowanych węzłów do używania przy pierwszym skoku w obwodzie,
784 
+jeśli możliwe.
785 
+    </dd>
786 
+  <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>
787 
+    <dd>Lista preferowanych węzłów do używania przy ostatnim skoku w obwodzie, jeśli
788 
+możliwe.
789 
+    </dd>
790 
+  <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>
791 
+    <dd>Lista węzłów, których nigdy nie używać do budowania obwodu.
792 
+    </dd>
793 
+  <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>
794 
+    <dd>Lista węzłów, których nigdy nie wybierać do wyjścia. Węzły podane w
795 
+<tt>ExcludeNodes</tt> są automatycznie na tej liście.
796 
+    </dd>
797 
+</dl>
798 
+<p>
799 
+<em>Nie zalecamy używania tych opcji</em> &mdash; są przeznaczone do testów
800 
+i mogą zniknąć w przyszłych wersjach. Najlepsze bezpieczeństwo, jakie może
801 
+dać Tor, dostajesz gdy zostawisz Torowi wybór ścieżki; zmiana węzłów
802 
+wejściowych / wyjściowych może zepsuć Twoją anonimowość na sposoby, których
803 
+nie rozumiemy.
804 
+</p>
805 
+<p>
806 
+Opcje <tt>EntryNodes</tt> i <tt>ExitNodes</tt> są traktowane jako prośba, co
807 
+znaczy, że jeśli te węzły są wyłączone lub wydają się działać wolno, Tor
808 
+dalej będzie ich unikał. Możesz sprawić, że te opcje będą obowiązkowe
809 
+ustawiając <tt>StrictExitNodes 1</tt> lub <tt>StrictEntryNodes 1</tt>
810 
+&mdash; ale jeśli tak zrobisz, Twoje połączenia przez Tora przestaną
811 
+działać, jeśli wszystkie podane przez Ciebie węzły staną się
812 
+nieosiągalne. Zobacz <a
813 
+href="https://www.torproject.org/documentation.html.en#NeatLinks">strony
814 
+statusu Tora</a>, by znaleźć węzły, które można wybrać.
815 
+</p>
816 
+<p>
817 
+Zamiast <tt>$fingerprint</tt> możesz podać też 2-literowy kod kraju według
818 
+ISO3166 w nawiasach klamrowych (na przykład {de}) lub wzorzec adresów IP (na
819 
+przykład 255.254.0.0/8) lub nazwę węzła. Upewnij się, że nie ma spacji
820 
+między przecinkami a elementami list.
821 
+</p>
822 
+<p>
823 
+Jeśli chcesz się dostać do usługi bezpośrednio przez interfejs SOCKS Tora
824 
+(np. używając SSH przez connect.c), innym rozwiązaniem jest ustawienie
825 
+wewnętrznego odwzorowania w pliku konfiguracyjnym, korzystając z
826 
+<tt>MapAddress</tt>. Przeczytaj stronę podręcznika, by poznać szczegóły.
827 
+</p>
828 
+
829 
+<hr />
830 
+
831 
+<a id="RelayFlexible"></a>
832 
+<h3><a class="anchor" href="#RelayFlexible">Jak stabilny musi być mój
833 
+przekaźnik?</a></h3>
834 
+
835 
+<p>
836 
+Naszym celem jest uczynienie uruchomienia przekaźnika Tora czynnością łatwą
837 
+i wygodną:
838 
+</p>
839 
+
840 
+<ul>
841 
+<li>Tor has built-in support for <a
842 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#LimitBandwidth">
843 
+rate limiting</a>. Further, if you have a fast link but want to limit the
844 
+number of bytes per day (or week or month) that you donate, check out the <a
845 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Hibernation">hibernation
846 
+feature</a>.
847 
+</li>
848 
+<li>Każdy przekaźnik Tora ma <a href="#ExitPolicies">politykę wyjścia</a>, która
849 
+określa, jakie rodzaje połączeń wychodzących są dozwolone lub zabronione z
850 
+danego przekaźnika. Jeśli nie chcesz pozwalać ludziom na wychodzenie z
851 
+Twojego przekaźnika, możesz skonfigurować go tak, by pozwalał na połączenia
852 
+tylko do innych przekaźników Tora.
853 
+</li>
854 
+<li>Jeśli przekaźnik czasem będzie offline, to w porządku. Serwery katalogowe
855 
+szybko to zauważają i przestają ogłaszać dany przekaźnik. Postaraj się
856 
+jednak, by nie zdarzało się to zbyt często, gdyż przerwie to połączenia
857 
+korzystające z przekaźnika w chwili jego rozłączenia.
858 
+</li>
859 
+<li>Dobrze radzimy sobie z przekaźnikami mającymi dynamiczne adresy IP &mdash;
860 
+po prostu zostaw opcję konfiguracji adresu pustą, a Tor spróbuje zgadnąć.
861 
+</li>
862 
+<li>If your relay is behind a NAT and it doesn't know its public IP (e.g. it has
863 
+an IP of 192.168.x.y), you'll need to set up port forwarding. Forwarding TCP
864 
+connections is system dependent but <a
865 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this
866 
+FAQ entry</a> offers some examples on how to do this.
867 
+</li>
868 
+<li>Twój przekaźnik pasywnie oszacuje i ogłosi swoją ostatnią przepustowość
869 
+łącza, by przekaźniki o szerszym łączu przyciągały więcej użytkowników, niż
870 
+te o wąskim łączu. Zatem posiadanie przekaźnika z wolnym łączem też jest
871 
+przydatne.
872 
+</li>
873 
+</ul>
874 
+
875 
+<hr />
876 
+
877 
+<a id="RunARelayBut"></a> <a id="ExitPolicies"></a>
878 
+<h3><a class="anchor" href="#ExitPolicies">Prowadziłbym/prowadziłabym
879 
+przekaźnik, ale nie chcę mieć do czynienia z przypadkami nadużyć.</a></h3>
880 
+
881 
+<p>
882 
+Wspaniale. To właśnie po to zaimplementowaliśmy polityki wyjścia.
883 
+</p>
884 
+
885 
+<p>
886 
+Każdy przekaźnik Tora ma politykę wyjścia, która określa, jakie rodzaje
887 
+połączeń wychodzących są dozwolone lub zabronione z danego
888 
+przekaźnika. Polityki wyjścia są rozprowadzane do klientów Tora poprzez
889 
+katalog, więc klienci automatycznie unikną wybierania przekaźników, które
890 
+odmówiłyby wyjścia do ich zamierzonych miejsc. W ten sposób każdy przekaźnik
891 
+może decydować o usługach, hostach i sieciach, do których chce zezwalać na
892 
+połączenia, w oparciu o możliwości nadużyć i własną sytuację. Przeczytaj
893 
+wpis do FAQ o <a href="<page faq-abuse>#TypicalAbuses">sprawach, które można
894 
+napotkać w razie używania domyślnej polityki wyjścia</a>, po czym przeczytaj
895 
+<a
896 
+href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">wskazówki
897 
+prowadzenia węzła wyjściowego z minimalnym narażeniem</a> Mike'a Perry'ego.
898 
+</p>
899 
+
900 
+<p>
901 
+The default exit policy allows access to many popular services (e.g. web
902 
+browsing), but <a
903 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
904 
+some due to abuse potential (e.g. mail) and some since the Tor network can't
905 
+handle the load (e.g. default file-sharing ports). You can change your exit
906 
+policy using Vidalia's "Sharing" tab, or by manually editing your <a
907 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc">torrc</a>
908 
+file. If you want to avoid most if not all abuse potential, set it to
909 
+"reject *:*" (or un-check all the boxes in Vidalia). This setting means that
910 
+your relay will be used for relaying traffic inside the Tor network, but not
911 
+for connections to external websites or other services.
912 
+</p>
913 
+
914 
+<p>
915 
+Jeśli zezwolisz na połączenia wychodzące, upewnij się, że działa
916 
+rozwiązywanie nazw (czyli Twój komputer jest w stanie poprawnie rozwiązywać
917 
+adresy internetowe). Jeśli są jakieś zasoby, do których Twój komputer nie
918 
+może dotrzeć (na przykład, jesteś za restrykcyjną zaporą ogniową lub filtrem
919 
+zawartości), prosimy o jawne wykluczenie ich w Twojej polityce wyjścia
920 
+&mdash; w innym przypadku miałoby to wpływ też na użytkowników Tora.
921 
+</p>
922 
+
923 
+<hr />
924 
+
925 
+<a id="RelayOrBridge"></a>
926 
+<h3><a class="anchor" href="#RelayOrBridge">Czy powinienem/powinnam prowadzić
927 
+normalny przekaźnik, czy przekaźnik mostkowy?</a></h3>
928 
+
929 
+<p><a href="<page bridges>">Przekaźniki mostkowe</a> (lub w skrócie "mostki")
930 
+są <a href="<page docs/tor-doc-relay>">przekaźnikami Tora</a>, które nie są
931 
+umieszczane na listach w głównym katalogu Tora. To znaczy, że nawet jeśli
932 
+dostawca Internetu lub rząd próbujący filtrować połączenia do sieci Tora
933 
+prawdopodobnie nie będzie mógł zablokować wszystkich mostków.
934 
+</p>
935 
+
936 
+<p>Bycie normalnym przekaźnikiem a mostkiem to prawie ta sama konfiguracja:
937 
+jest to tylko kwestia tego, czy Twój przekaźnik jest umieszczany na
938 
+publicznych listach, czy nie.
939 
+</p>
940 
+
941 
+<p>W tej chwili na świecie jest około zera miejsc, które filtrują połączenia do
942 
+sieci Tora. Dlatego posiadanie dużej liczby mostków obecnie jest tylko
943 
+środkiem zapasowym a) w przypadku, gdy sieć Tora faktycznie jest gdzieś
944 
+blokowana, i b) dla ludzi chcących dodatkowej warstwy zabezpieczenia, gdyż
945 
+martwią się tym, że ktoś pozna, że adres, z którym się kontaktują, jest
946 
+adresem IP publicznego przekaźnika Tora.
947 
+</p>
948 
+
949 
+<p>Masz więc prowadzić normalny przekaźnik, czy mostek? Jeśli masz szybkie
950 
+łącze, zdecydowanie normalny przekaźnik &mdash; przekaźniki mostkowe nie są
951 
+bardzo wykorzystywane obecnie. Jeśli chcesz <a href="#ExitPolicies">być
952 
+wyjściem</a>, powinieneś/aś prowadzić normalny przekaźnik, gdyż potrzebujemy
953 
+więcej wyjść. Jeśli nie możesz być wyjściem i masz niską przepustowość
954 
+łącza, rzuć monetą. Dziękujemy za zgłoszenie!
955 
+</p>
956 
+
957 
+<hr />
958 
+
959 
+<a id="RelayMemory"></a>
960 
+<h3><a class="anchor" href="#RelayMemory">Czemu mój przekaźnik Tora zużywa tyle
961 
+pamięci?</a></h3>
962 
+
963 
+<p>Jeśli Twój przekaźnik zużywa więcej pamięci niż być chciał/a, oto kilka
964 
+wskazówek, jak zmniejszyć tę ilość:
965 
+</p>
966 
+
967 
+<ol>
968 
+<li>Jeśli jesteś na Linuksie, może napotykasz błędy z fragmentacją pamięci w
969 
+implementacji malloc w glibc. To znaczy, że jeśli Tor zwalnia pamięć z
970 
+powrotem do systemu, części pamięci są pofragmentowane, więc ciężko ich użyć
971 
+ponownie. Paczka Tora jest wydawana z implementacją malloc z OpenBSD, która
972 
+nie ma aż tylu błędów związanych z fragmentacją (ale ceną jest większe
973 
+użycie procesora). Możesz powiedzieć Torowi, by używał tej implementacji
974 
+malloc: <tt>./configure --enable-openbsd-malloc</tt></li>
975 
+
976 
+<li>If you're running a fast relay, meaning you have many TLS connections open,
977 
+you are probably losing a lot of memory to OpenSSL's internal buffers (38KB+
978 
+per socket). We've patched OpenSSL to <a
979 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00001.html">release unused
980 
+buffer memory more aggressively</a>. If you update to OpenSSL 1.0.0-beta5,
981 
+Tor's build process will automatically recognize and use this feature.</li>
982 
+
983 
+<li>If you're running on Solaris, OpenBSD, NetBSD, or old FreeBSD, Tor is
984 
+probably forking separate processes rather than using threads. Consider
985 
+switching to a <a
986 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayOS">better
987 
+operating system</a>.</li>
988 
+
989 
+<li>Jeśli dalej nie możesz sobie poradzić z wykorzystaniem pamięci, rozważ
990 
+zmniejszenie przepustowości łącza, którą zgłasza Twój przekaźnik. Zgłaszanie
991 
+mniejszej przepustowości oznacza, że będziesz przyciągać mniej użytkowników,
992 
+więc Twój przekaźnik nie powinien urosnąć aż tak bardzo. Spójrz na opcję
993 
+<tt>MaxAdvertisedBandwidth</tt> na stronie podręcznika.</li>
994 
+
995 
+</ol>
996 
+
997 
+<p>
998 
+Powiedziawszy to wszystko, szybkie przekaźniki Tora używają dużo
999 
+RAMu. Nierzadko szybkie przekaźniki używają 500-1000 MB pamięci.
1000 
+</p>
1001 
+
1002 
+<hr />
1003 
+
1004 
+<a id="WhyNotNamed"></a>
1005 
+<h3><a class="anchor" href="#WhyNotNamed">Czemu mój przekaźnik Tora nie ma
1006 
+nazwy?</a></h3>
1007 
+
1008 
+<p>
1009 
+We currently use these metrics to determine if your relay should be named:<br />
1010 
+</p>
1011 
+<ul>
1012 
+<li>Nazwa nie jest przypisana do innego klucza. Istniejące przypisania są
1013 
+usuwane po 6 miesiącach nieaktywności przekaźnika.</li>
1014 
+<li>Przekaźnik musi działać przez co najmniej 2 tygodnie.</li>
1015 
+<li>Żaden inny router nie chciał tej nazwy w poprzednim miesiącu.</li>
1016 
+</ul>
1017 
+
1018 
+<hr />
1019 
+
1020 
+<a id="KeyManagement"></a>
1021 
+<h3><a class="anchor" href="#KeyManagement">Opowiedzcie mi o kluczach używanych
1022 
+przez Tora.</a></h3>
1023 
+
1024 
+<p>
1025 
+Tor używa wielu różnych kluczy, mając na uwadze trzy cele: 1) szyfrowanie w
1026 
+celu zapewnienia prywatności danych wewnątrz sieci Tora, 2) autentykacja
1027 
+(weryfikacja tożsamości), by klienci wiedzieli, że przesyłają dane do tych
1028 
+przekaźników, do których chcieli, 3) podpisy, by wszyscy klienci posiadali
1029 
+ten sam zestaw przekaźników sieci.
1030 
+</p>
1031 
+
1032 
+<p>
1033 
+<b>Szyfrowanie</b>: po pierwsze, wszystkie połączenia w sieci Tor korzystają
1034 
+z szyfrowania TLS, więc obserwatorzy zewnętrzni nie mogą dowiedzieć się, dla
1035 
+którego obwodu dana komórka jest przeznaczona. Ponadto, klient Tora uzgadnia
1036 
+efemeryczny klucz szyfrujący z każdym przekaźnikiem w obwodzie, by tylko
1037 
+węzeł wyjściowy mógł przeczytać komórki. Obie strony wyrzucają klucz obwodu,
1038 
+gdy ulega on zamknięciu, więc logowanie ruchu i włamanie się do przekaźnika
1039 
+w celu odkrycia klucza nie podziała.
1040 
+</p>
1041 
+
1042 
+<p>
1043 
+<b>Authentication</b>: Every Tor relay has a public decryption key called
1044 
+the "onion key".  When the Tor client establishes circuits, at each step it
1045 
+<a href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demands
1046 
+that the Tor relay prove knowledge of its onion key</a>. That way the first
1047 
+node in the path can't just spoof the rest of the path.  Each relay rotates
1048 
+its onion key once a week.
1049 
+</p>
1050 
+
1051 
+<p>
1052 
+<b>Koordynacja</b>: Skąd klienci wiedzą, jakie są przekaźniki i skąd wiedzą,
1053 
+że mają do nich właściwe klucze? Każdy przekaźnik ma "długoterminowy"
1054 
+publiczny klucz podpisujący, zwany "kluczem tożsamości". Każde centrum
1055 
+katalogowe ponadto ma "katalogowy klucz podpisujący". Centra katalogowe <a
1056 
+href="<gitblob>doc/spec/dir-spec.txt">dostarczają podpisane listy</a>
1057 
+wszystkich znanych przekaźników sieci, a w tej liście jest zestaw
1058 
+certyfikatów od każdego przekaźnika (samopodpisanych ich kluczem
1059 
+tożsamości), określających ich klucze, położenia, polityki wyjścia itd. Więc
1060 
+jeśli atakujący nie kontroluje serwerów katalogowych, nie może oszukać
1061 
+klientów, by używali innych przekaźników sieci.
1062 
+</p>
1063 
+
1064 
+<p>
1065 
+Skąd klienci wiedzą, jakie są centra katalogowe? Oprogramowanie Tor zawiera
1066 
+wbudowaną listę położeń i kluczy publicznych każdego centrum
1067 
+katalogowego. Więc jedynym sposobem na oszukanie użytkowników, by korzystali
1068 
+z fałszywej sieci Tora jest danie im specjalnie zmodyfikowanej wersji
1069 
+programu.
1070 
+</p>
1071 
+
1072 
+<p>
1073 
+Skąd użytkownicy wiedzą, że dostali właściwy program? Gdy wydajemy kod
1074 
+źródłowy lub paczkę, podpisujemy ją cyfrowo, używając <a
1075 
+href="http://www.gnupg.org/">GNU Privacy Guard</a>. Przeczytaj <a
1076 
+href="<page verifying-signatures>">instrukcje odnośnie weryfikacji podpisów
1077 
+Tora</a>.
1078 
+</p>
1079 
+
1080 
+<p>
1081 
+Aby być pewnym, że coś naprawdę jest podpisane przez nas, powinieneś/aś
1082 
+spotkać się z nami osobiście i otrzymać kopię odcisku palca naszego klucza
1083 
+GPG, lub powinieneś/aś znać kogoś, kto tak zrobił. Jeśli martwisz się
1084 
+atakiem na tym poziomie, zalecamy zaangażować się ze społecznością związaną
1085 
+z bezpieczeństwem i zacząć poznawać ludzi.
1086 
+</p>
1087 
+
1088 
+<hr />
1089 
+
1090 
+<a id="EverybodyARelay"></a>
1091 
+<h3><a class="anchor" href="#EverybodyARelay">Powinno się sprawić, by każdy
1092 
+użytkownik Tora był przekaźnikiem.</a></h3>
1093 
+
1094 
+<p>
1095 
+Requiring every Tor user to be a relay would help with scaling the network
1096 
+to handle all our users, and <a
1097 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">running
1098 
+a Tor relay may help your anonymity</a>. However, many Tor users cannot be
1099 
+good relays &mdash; for example, some Tor clients operate from behind
1100 
+restrictive firewalls, connect via modem, or otherwise aren't in a position
1101 
+where they can relay traffic. Providing service to these clients is a
1102 
+critical part of providing effective anonymity for everyone, since many Tor
1103 
+users are subject to these or similar constraints and including these
1104 
+clients increases the size of the anonymity set.
1105 
+</p>
1106 
+
1107 
+<p>
1108 
+To rzekłszy, chcemy zachęcać użytkowników do prowadzenia przekaźników, więc
1109 
+to, czego naprawdę chcemy, to uproszczenie procesu uruchamiania i
1110 
+utrzymywania przekaźnika. Poczyniliśmy duży postęp z łatwą konfiguracją w
1111 
+ciągu ostatnich kilku lat: Vidalia ma łatwy interfejs konfiguracji
1112 
+przekaźnika i obsługuje też uPnP. Tor jest dobry w automatycznym
1113 
+sprawdzaniu, czy jest dostępny i jak dużą przepustowość łącza może
1114 
+zaoferować.
1115 
+</p>
1116 
+
1117 
+<p>
1118 
+Jest jednak pięć kroków, którymi musimy się najpierw zająć:
1119 
+</p>
1120 
+
1121 
+<p>
1122 
+Po pierwsze, musimy ustabilizować pracę Tora jako przekaźnika na wszystkich
1123 
+popularnych systemach. Główną platformą pozostającą do zrobienia jest
1124 
+Windows, planujemy zająć się tym ostatecznie w 2009. Przeczytaj sekcję 4.1
1125 
+<a
1126 
+href="https://www.torproject.org/press/2008-12-19-roadmap-press-release">naszego
1127 
+planu rozwojowego</a>.
1128 
+</p>
1129 
+
1130 
+<p>
1131 
+Second, we still need to get better at automatically estimating the right
1132 
+amount of bandwidth to allow. See item #7 on the <a href="<page
1133 
+volunteer>#Research">research section of the volunteer page</a>: "Tor
1134 
+doesn't work very well when relays have asymmetric bandwidth (e.g. cable or
1135 
+DSL)". It might be that <a
1136 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching
1137 
+to UDP transport</a> is the simplest answer here &mdash; which alas is not a
1138 
+very simple answer at all.
1139 
+</p>
1140 
+
1141 
+<p>
1142 
+Third, we need to work on scalability, both of the network (how to stop
1143 
+requiring that all Tor relays be able to connect to all Tor relays) and of
1144 
+the directory (how to stop requiring that all Tor users know about all Tor
1145 
+relays). Changes like this can have large impact on potential and actual
1146 
+anonymity. See Section 5 of the <a
1147 
+href="<svnprojects>design-paper/challenges.pdf">Challenges</a> paper for
1148 
+details. Again, UDP transport would help here.
1149 
+</p>
1150 
+
1151 
+<p>
1152 
+Po czwarte, musimy lepiej zrozumieć ryzyka płynące z umożliwienia
1153 
+napastnikowi wysyłania ruchu przez Twój przekaźnik, gdy Ty zaczynasz swój
1154 
+własny ruch anonimowy. <a
1155 
+href="http://freehaven.net/anonbib/#back01">Trzy</a> <a
1156 
+href="http://freehaven.net/anonbib/#clog-the-queue">różne</a> dokumenty <a
1157 
+href="http://freehaven.net/anonbib/#torta05">badawcze</a> opisują sposoby na
1158 
+identyfikację przekaźników w obwodzie poprzez kierowanie ruchu przez
1159 
+węzły-kandydatów i szukanie obniżania w ruchu w czasie, gdy obwód jest
1160 
+aktywny. Te ataki zatykające nie są tak straszne w kontekście Tora, dopóki
1161 
+przekaźniki nie są klientami. Ale jeśli próbujemy zachęcić więcej klientów
1162 
+do bycia przekaźnikami (czy jako <a href="<page bridges>">przekaźniki
1163 
+mostkowe</a>, czy zwykłe przekaźniki), to musimy lepiej zrozumieć to
1164 
+zagrożenie i nauczyć się je łagodzić.
1165 
+</p>
1166 
+
1167 
+<p>
1168 
+Po piąte, możemy potrzebować jakiegoś schematu bodźców do zachęcana ludzi,
1169 
+by przekierowywali ruch innych lub zostali węzłami wyjściowymi. Tu są nasze
1170 
+<a href="https://blog.torproject.org/blog/two-incentive-designs-tor">bieżące
1171 
+pomysły na bodźce Tora</a>.
1172 
+</p>
1173 
+
1174 
+<p>
1175 
+Prosimy o pomoc przy każdym z tych punktów!
1176 
+</p>
1177 
+
1178 
+<hr />
1179 
+
1180 
+<a id="Criminals"></a>
1181 
+<h3><a class="anchor" href="#Criminals">Czy Tor nie umożliwia przestępcom
1182 
+robienia złych rzeczy?</a></h3>
1183 
+
1184 
+<p>
1185 
+By poznać odpowiedź na to i inne pytania, odwiedź nasze <a href="<page
1186 
+faq-abuse>">FAQ o nadużyciach Tora</a>.
1187 
+</p>
1188 
+
1189 
+<hr />
1190 
+
1191 
+<a id="RespondISP"></a>
1192 
+<h3><a class="anchor" href="#RespondISP">Jak odpowiadać mojemu dostawcy
1193 
+Internetu o moim przekaźniku wyjściowym?</a></h3>
1194 
+
1195 
+<p>
1196 
+A collection of templates for successfully responding to ISPs is <a
1197 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates">collected
1198 
+here</a>.
1199 
+</p>
1200 
+
1201 
+<hr />
1202 
+
1203 
+  </div>
1204 
+
1205 
+
1206 
+
1207 
+#include <foot.wmi>
pl/mirrors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,49 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Mirrors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Mirrory</h2>
14 
+<hr />
15 
+
16 
+<p>
17 
+Adres kanoniczny tej strony to <a
18 
+href="https://www.torproject.org/">https://www.torproject.org/</a>, ale w
19 
+innych miejscach znajduje się kilka mirrorów tej strony.
20 
+</p>
21 
+
22 
+<p>
23 
+Jeśli chcielibyście poprowadzić mirror, prosimy <a href="<page
24 
+docs/running-a-mirror>">przeczytać nasze instrukcje odnośnie prowadzenia
25 
+mirrora</a>.
26 
+</p>
27 
+
28 
+<table class="mirrors">
29 
+<tr>
30 
+  <th>Kraj</th>
31 
+  <th>Organizacja</th>
32 
+  <th>Status</th>
33 
+  <th>ftp</th>
34 
+  <th>http - katalog dist/</th>
35 
+  <th>http - strona</th>
36 
+  <th>https - katalog dist/</th>
37 
+  <th>https - strona</th>
38 
+  <th>rsync - katalog dist/</th>
39 
+  <th>rsync - strona</th>
40 
+</tr>
41 
+
42 
+<!--PO4ASHARPBEGINinclude <mirrors-table.wmi>
43 
+PO4ASHARPEND-->
44 
+</table>
45 
+
46 
+  </div>
47 
+
48 
+
49 
+#include <foot.wmi>
pl/torusers.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,416 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22261 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Who uses Tor?" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Początek</h2>
14 
+
15 
+
16 
+<!-- BEGIN SIDEBAR -->
17 
+<div class="sidebar-left">
18 
+<h3>Kto używa Tora?</h3>
19 
+<ul>
20 
+<li><a href="<page torusers>#normalusers">Normalni ludzie używają Tora</a></li>
21 
+<li><a href="<page torusers>#military">Wojskowi używają Tora</a></li>
22 
+<li><a href="<page torusers>#journalist">Dziennikarze i ich widownia używają
23 
+Tora</a></li>
24 
+<li><a href="<page torusers>#lawenforcement">Stróże prawa używają Tora</a></li>
25 
+<li><a href="<page torusers>#activists">Aktywiści używają Tora</a></li>
26 
+<li><a href="<page torusers>#spotlight">Osoby publiczne i niepubliczne używają
27 
+Tora</a></li>
28 
+<li><a href="<page torusers>#executives">Kierownicy używają Tora</a></li>
29 
+<li><a href="<page torusers>#bloggers">Blogerzy używają Tora</a></li>
30 
+<li><a href="<page torusers>#itprofessionals">Profesjonaliści IT używają
31 
+Tora</a></li>
32 
+</ul>
33 
+</div>
34 
+
35 
+
36 
+<!-- END SIDEBAR -->
37 
+<hr />
38 
+<p>
39 
+Tor był początkowo zaprojektowany, zaimplementowany i wydany jako <a
40 
+href="http://www.onion-router.net/">projekt trasowania cebulowego trzeciej
41 
+generacji Laboratotium Marynarki Wojennej (Naval Research Laboratory)</a>.
42 
+Był początkowo rozwijany z myślą o Marynarce Wojennej USA, przede wszystkim
43 
+w celu ochrony łączności rządowej. Dziś jest używany na co dzień do różnych
44 
+celów przez wojskowych, dziennikarzy, stróżów prawa, aktywistów i wielu
45 
+innych ludzi.  Poniżej przedstawiamy kilka specyficznych zastosowań, o
46 
+których wiemy lub które polecamy.
47 
+</p>
48 
+
49 
+<a name="normalusers"></a>
50 
+<h2><a class="anchor" href="#normalusers">Normalni ludzie używają Tora</a></h2>
51 
+<hr />
52 
+<ul>
53 
+<li><strong>Bronią swojej prywatności przed pozbawionymi skrupułów ludźmi od
54 
+marketingu i złodziejami tożsamości.</strong> Firmy dostarczające łącza
55 
+internetowe (ISPs) <a
56 
+href="http://seekingalpha.com/article/29449-compete-ceo-isps-sell-clickstreams-for-5-a-month"
57 
+>sprzedają zapisy z twojego przeglądania sieci</a> ludziom od marketingu lub
58 
+komukolwiek, kto zechce za to zapłacić. Firmy te zazwyczaj mówią, że
59 
+anonimizują te dane poprzez nie podawanie informacji umożliwiających
60 
+identyfikację, ale <a
61 
+href="http://www.wired.com/politics/security/news/2006/08/71579?currentPage=all">udowodniono,
62 
+że to nieprawda</a>. Pełny zapis stron, które odwiedzasz, tekst każdego
63 
+wykonanego wyszukiwania, i potencjalnie każdy login, a nawet hasło mogą być
64 
+częścią tych danych. Ponadto, strony (<a
65 
+href="http://www.google.com/privacy_faq.html">i wyszukiwarki</a>), które
66 
+odwiedzasz, mają swoje własne zapisy zawierające tę samą ilość lub nawet
67 
+więcej informacji.
68 
+</li>
69 
+<li><strong>Chronią swoją łączność przed nieodpowiedzialnymi
70 
+korporacjami.</strong> W całym Internecie Tor jest zalecany ludziom, którzy
71 
+właśnie zaniepokoili się o swoją prywatność w obliczu wzrastającej liczby
72 
+włamań i zdrady prywatnych danych.  Od <a
73 
+href="http://www.securityfocus.com/news/11048">zagubionych taśm kopii
74 
+zapasowych</a>, do <a
75 
+href="http://www.nytimes.com/2006/08/09/technology/09aol.html?ex=1312776000&amp;en=f6f61949c6da4d38&amp;ei=5090"
76 
+>oddawania danych badaczom</a>, twoje dane są często niedostatecznie
77 
+chronione przez tych, którym powinieneś ufać w tych sprawach.
78 
+</li>
79 
+<li><strong>Chronią swoje dzieci w sieci.</strong> Powiedziałeś/aś swoim
80 
+dzieciom, że nie powinny podawać danych osobowych w sieci, ale mogą one
81 
+zdradzać miejsce swojego pobytu poprzez nie ukrywanie swojego adresu IP
82 
+Ponadto, adresy IP mogą być <a href="http://whatismyipaddress.com/" >użyte
83 
+do odkrycia miasta, a nawet ulicy</a> i mogą też <a
84 
+href="http://whatsmyip.org/more/">zdradzić inne informacje</a> o tym, jak
85 
+łączysz się z Internetem. W Stanach Zjednoczonych rząd naciska, by to
86 
+odwzorowanie IP-adres było coraz bardziej precyzyjne.
87 
+</li>
88 
+<li><strong>Badają wrażliwe tematy.</strong> W sieci dostępne jest bogactwo
89 
+informacji. Ale może w twoim kraju dostęp do informacji na temat AIDS,
90 
+kontroli narodzin, <a
91 
+href="http://www.cbsnews.com/stories/2002/12/03/tech/main531567.shtml">kultury
92 
+Tybetańskiej</a>, lub religii światowych jest za krajową zaporą ogniową
93 
+(firewallem).
94 
+</li>
95 
+</ul>
96 
+
97 
+<a name="military"></a>
98 
+<h2><a class="anchor" href="#military">Wojskowi używają Tora</a></h2>
99 
+<hr />
100 
+<ul>
101 
+
102 
+<li>
103 
+<strong>Agenci w terenie:</strong> Rebeliantom nie jest trudno monitorować
104 
+ruch w Internecie i odkryć wszystkie hotele i inne miejsca, z których inni
105 
+ludzie łączą się ze znanymi serwerami wojskowymi.  Agenci wojskowi w terenie
106 
+daleko od domu używają Tora do maskowania stron, które odwiedzają, do
107 
+ochrony interesów i operacji wojskowych, a także do ochrony siebie od
108 
+niebezpieczeństwa.
109 
+</li>
110 
+
111 
+<li><strong>Usługi ukryte:</strong> Gdy Internet by projektowany przez DARPA,
112 
+jego głównym celem było ułatwienie wykonywania rozproszonej, sprawnej
113 
+łączności w wypadku ataków lokalnych.  Jednakże, część funkcji musi być
114 
+scentralizowana, jak na przykład miejsca kontroli i dowodzenia. Odkrywanie
115 
+geograficznej lokalizacji dowolnego dostępnego serwera jest w naturze
116 
+protokołów internetowych. Usługi ukryte Tora pozwalają punktom kontroli i
117 
+dowodzenia fizyczne zabezpieczenie przed wykryciem i zniszczeniem.
118 
+</li>
119 
+<li><strong>Zbieranie danych wywiadowczych:</strong> Personel wojskowy musi
120 
+używać elektronicznych zasobów prowadzonych i monitorowanych przez
121 
+rebeliantów. Nie chcą zapisów wojskowych adresów IP na serwerach, gdyż to
122 
+odkryłoby fakt prowadzenia wywiadu.
123 
+</li>
124 
+</ul>
125 
+
126 
+<a name="journalist"></a>
127 
+<h2><a class="anchor" href="#journalist">Dziennikarze i ich widownia używają
128 
+Tora</a></h2>
129 
+<hr />
130 
+<ul>
131 
+<li><strong><a href="http://www.rsf.org/">Reporterzy bez Granic</a></strong>
132 
+znajdują internetowych więźniów sumienia i zamkniętych w więzieniach lub
133 
+krzywdzonych dziennikarzy na całym świecie. Zalecają dziennikarzom, ich
134 
+źródłom, blogerom i dysydentom używanie Tora do zapewnienia sobie
135 
+prywatności i bezpieczeństwa.
136 
+</li>
137 
+<li><strong>Amerykańskie <a href="http://www.ibb.gov/">International
138 
+Broadcasting Bureau</a></strong> (Głos Ameryki/Radio Wolna Europa/Radio
139 
+Wolna Azja) wspiera rozwój Tora, by pomóc użytkownikom Internetu w krajach
140 
+bez bezpiecznego dostępu do wolnych mediów. Tor daje ludziom za krajowymi
141 
+zaporami ogniowymi lub pod nadzorem represyjnych reżimów możliwość uzyskania
142 
+globalnej perspektywy na kontrowersyjne tematy jak demokracja, ekonomia i
143 
+religia.
144 
+</li>
145 
+<li><strong>Dziennikarze obywatelscy w Chinach</strong> używają Tora do pisania
146 
+o lokalnych zdarzeniach, by zachęcić zmiany społeczne i reformy polityczne.
147 
+</li>
148 
+<li><strong>Obywatele i dziennikarze w <a
149 
+href="http://www.rsf.org/rubrique.php3?id_rubrique=554">internetowych
150 
+czarnych dziurach</a></strong> używają Tora, by badać propagandę krajową i
151 
+opozycyjne punkty widzenia, by pisać artykuły w mediach nie kontrolowanych
152 
+przez państwo i aby uniknąć ryzyka osobistych konsekwencji intelektualnej
153 
+ciekawości.
154 
+</li>
155 
+</ul>
156 
+
157 
+<a name="lawenforcement"></a>
158 
+<h2><a class="anchor" href="#lawenforcement">Stróże prawa używają Tora</a></h2>
159 
+<hr />
160 
+<ul>
161 
+<li><strong>Inwigilacja on-line:</strong> Tor pozwala na odwiedzanie wątpliwych
162 
+stron i serwisów internetowych bez pozostawiania zdradzających śladów. Jeśli
163 
+administrator nielegalnej strony hazardowej zobaczyłby w logach wielokrotne
164 
+połączenia z adresów IP należących do rządu lub organów ochrony prawa,
165 
+śledztwo mogłoby ucierpieć.
166 
+</li>
167 
+<li><strong>Operacje wykiwania:</strong> Podobnie, anonimowość pozwala stróżom
168 
+prawa brać udział w &ldquo;tajnych&rdquo; operacjach w sieci. Nieważne, jak
169 
+dobra jest &ldquo;uliczna wiarygodność&rdquo; danego oficera.  Jeśli w
170 
+łączności biorą udział zakresy adresów IP policji, operacja wychodzi na jaw.
171 
+</li>
172 
+<li><strong>Prawdziwie anonimowe serwisy ze wskazówkami:</strong> Mimo iż
173 
+anonimowe serwisy ze wskazówkami są popularne, bez oprogramowania do
174 
+anonimowości są znacznie mniej użyteczne. Wyspecjalizowane źródła wiedzą, że
175 
+mimo iż imię czy adres e-mail nie są częścią informacji, logi serwera mogą
176 
+zidentyfikować ich bardzo szybko. W wyniku tego, serwisy ze wskazówkami,
177 
+które nie zachęcają do anonimowości, same sobie ograniczają liczbę źródeł
178 
+wskazówek.
179 
+</li>
180 
+</ul>
181 
+
182 
+<a name="activists"></a>
183 
+<h2><a class="anchor" href="#activists">Aktywiści używają Tora</a></h2>
184 
+<hr />
185 
+<ul>
186 
+<li><strong>Aktywiści w sprawach praw człowieka używają Tora w strefach
187 
+zagrożenia do anonimowego zgłaszania nadużyć.</strong> W wielu krajach
188 
+ludzie działający na rzecz prawa pracowników używają Tora i innych form
189 
+anonimowości off-line i on-line, by organizować pracowników zgodnie z
190 
+Powszechną Deklaracją Praw Człowieka. Mimo iż działają zgodnie z prawem, nie
191 
+znaczy to, że są bezpieczni. Tor umożliwia uniknięcie oskarżenia i
192 
+jednoczesne głośne mówienie.
193 
+</li>
194 
+<li>Gdy grupy takie jak <strong>Friends Service Committee i grupy środowiskowe
195 
+są coraz <a href="http://www.afsc.org/news/2005/government-spying.htm"
196 
+>częściej inwigilowane</a> w Stanach Zjednoczonych</strong> w związku z
197 
+prawem mającym chronić przed terroryzmem, wielu pokojowych agentów zmiany
198 
+polega na Torze w celu zachowania prywatności w trakcie wykonywania zgodnych
199 
+z prawem czynności
200 
+</li>
201 
+<li><strong><a href="http://hrw.org/doc/?t=internet">Human Rights
202 
+Watch</a></strong> zaleca Tora w swoim raporcie, &ldquo; <a
203 
+href="http://www.hrw.org/reports/2006/china0806/">Race to the Bottom:
204 
+Corporate Complicity in Chinese Internet Censorship</a>&rdquo;
205 
+(&ldquo;Wyścig na dno: Korporacyjny współudział w chińskim cenzurowaniu
206 
+Internetu&rdquo;). Współautor dokumentu przeprowadził wywiad z Rogerem
207 
+Dingledinem, liderem projektu Tor, na temat używania Tora. Tor opisany jest
208 
+w sekcji mówiącej, jak przełamać <a
209 
+href="http://www.hrw.org/reports/2006/china0806/3.htm#_Toc142395820">&ldquo;Chiński
210 
+Wielki Mur Ognisty&rdquo;</a> (firewall). Dokument zaleca ludziom pracującym
211 
+na rzecz praw człowieka na całym świecie używanie Tora do
212 
+&ldquo;bezpiecznego przeglądania Internetu i bezpiecznej łączności.&rdquo;
213 
+</li>
214 
+<li> Projekt Tor skonsultował się i zgłosił chęć pomocy do nowej kampanii
215 
+<strong>Amnesty International - <a
216 
+href="http://irrepressible.info/">kampanii o odpowiedzialności
217 
+korporacji</a></strong>.  Przeczytaj także ich <a
218 
+href="http://irrepressible.info/static/pdf/FOE-in-china-2006-lores.pdf">pełny
219 
+raport</a> dotyczący spraw Internetu w Chinach.
220 
+</li>
221 
+<li><a href="http://www.globalvoicesonline.org">Global Voices</a> poleca Tora,
222 
+zwłaszcza do <strong>anonimowego blogowania</strong>, poprzez ich <a
223 
+href="http://advocacy.globalvoicesonline.org/projects/guide/">stronę.</a>
224 
+</li>
225 
+<li>Sąd Najwyższy USA ostatnio zdjął prawne ochrony z rządowych aktywistów.  Ale
226 
+aktywiści pracujący na rzecz przejrzystości rządu lub odpowiedzialności
227 
+korporacji mogą używać Tora, by szukać sprawiedliwości bez reperkusji.
228 
+</li>
229 
+<li>Jedna z naszych osób kontaktowych, która pracuje w ochronie zdrowia
230 
+nonprofit w Afryce, zgłasza że jego organizacja <strong>przeznacza 10%
231 
+budżetu na pokrycie różnych rodzajów korupcji</strong>, głównie łapówki
232 
+itp. Gdy ta ilość szybko rośnie, nie tylko nie stać ich na pieniądze, nie
233 
+stać ich też na skarżenie się &mdash; jest to punkt, w którym otwarty
234 
+sprzeciw może być niebezpieczny. Dlatego jego organizacja pracowała nad
235 
+<strong>wykorzystaniem Tora do bezpiecznego ujawniania korupcji w
236 
+rządzie</strong>, by mogli kontynuować pracę.
237 
+</li>
238 
+<li>Na niedawnej konferencji pracownik Tora wpadł na kobietę pochodzącą z
239 
+&ldquo;firmowego miasteczka&rdquo; we wschodnich Stanach. Próbowała ona
240 
+blogować anonimowo, by pozyskać lokalnych mieszkańców do <strong>pilnej
241 
+reformy w firmie</strong>, która zdominowała miejską ekonomię i sprawy
242 
+rządowe. Jest ona w pełni powiadomiona, że rodzaj organizacji, który
243 
+wykonuje, <strong>mógł prowadzić do krzywdy lub &ldquo;śmiertelnych
244 
+wypadków.&rdquo;</strong>
245 
+</li>
246 
+<li>We wschodniej Azji niektóre organizacje pracownicze używają anonimowości, by
247 
+<strong>ujawniać informacje dotyczące firm</strong>, które produkują wyroby
248 
+dla zachodnich krajów, i by organizować lokalną pracę.
249 
+</li>
250 
+<li>
251 
+Tor can help activists avoid government or corporate censorship that hinders
252 
+organization.  In one such case, a <a
253 
+href="http://www.cbc.ca/canada/story/2005/07/24/telus-sites050724.html">Canadian
254 
+ISP blocked access to a union website used by their own employees</a> to
255 
+help organize a strike.
256 
+</li>
257 
+</ul>
258 
+
259 
+<a name="spotlight"></a>
260 
+<h2><a class="anchor" href="#spotlight">Osoby publiczne i niepubliczne używają
261 
+Tora</a></h2>
262 
+<hr />
263 
+<ul>
264 
+<li>Czy bycie w świetle reflektorów na zawsze uniemożliwia posiadanie prywatnego
265 
+życia w sieci? Rolniczy prawnik w Nowej Anglii prowadzi anonimowy blog,
266 
+gdyż, ze względu na zróżnicowaną klientelę jego prestiżowej firmy
267 
+prawniczej, <strong>jego przekonania polityczne na pewno kogoś
268 
+urażą</strong>.  Jednak nie chce on siedzieć cicho w sprawach, na których mu
269 
+zależy. Tor pomaga mu pozostać anonimowym tak, by mógł wyrażać swoje opinie
270 
+bez konsekwencji dla jego publicznej roli.
271 
+</li>
272 
+<li>Ludzie żyjący w ubóstwie często nie biorą pełnego udziału w społeczeństwie
273 
+obywatelskim -- nie z ignorancji czy apatii, lecz ze strachu. Jeśli coś, co
274 
+napisałeś, miałoby trafić do twojego szefa, straciłbyś pracę? Jeśli twój
275 
+pracownik socjalny przeczytałby twoją opinię o systemie, traktowałby cię
276 
+inaczej? Anonimowość gaje głos bezgłośnym. By to wspierać, <strong>Tor ma w
277 
+tej chwili otwartą pozycję Americorps/VISTA</strong>.  Ten rządowy grant
278 
+pokryje pełnoetatowe stypendium dla ochotnika, by stworzył szkolenia, by
279 
+<strong>pokazać ludności o niskich dochodach, jak używać anonimowości w
280 
+sieci dla bezpieczniejszego zaangażowania społecznego</strong>.  Mimo iż
281 
+często się mówi, że ludzie biedni nie używają sieci do spraw obywatelskich,
282 
+nie dbając o swoje interesy, naszą hipotezą (opartą na osobistych rozmowach
283 
+i anegdotach) jest to, że to dokładnie ta &ldquo;utrwalona opinia&rdquo;
284 
+zapisana w sieci jest tym, co powstrzymuje wielu biednych przed
285 
+wypowiadaniem się w Internecie. Mamy nadzieję pokazać ludziom, jak angażować
286 
+się bezpieczniej w sieci, a pod koniec roku zbadać, jak zmieniło się
287 
+obywatelskie zaangażowanie on-line i off-line i jak społeczeństwo widzi
288 
+kontynuację tego w przyszłości.
289 
+</li>
290 
+</ul>
291 
+
292 
+<a name="executives"></a>
293 
+<h2><a class="anchor" href="#executives">Kierownicy używają Tora</a></h2>
294 
+<hr />
295 
+<ul>
296 
+<li><strong>Spotkania na temat zagrożeń bezpieczeństwa:</strong> Powiedzmy, że
297 
+pewna instytucja finansowa bierze udział w spotkaniu na temat bezpieczeństwa
298 
+o atakach internetowych. Takie repozytorium wymaga od członków zgłaszania
299 
+włamań do jakiejś centralnej grupy, która koreluje ataki, by wykryć
300 
+powtarzające się wzorce i wysłać zawiadomienia. Ale jeśli jakiś konkretny
301 
+bank w St. Louis padł ofiarą włamania, nie chcą, by atakujący obserwujący
302 
+ruch przychodzący do repozytorium wyśledził, skąd pochodzi dana
303 
+informacja. Nawet jeśli każdy pakiet byłby zaszyfrowany, adres IP zdradziłby
304 
+pochodzenie złamanego systemu. Tor pozwala takim repozytoriom poufnych
305 
+danych na unikanie włamania.
306 
+</li>
307 
+<li><strong>Patrzenie na konkurencję tak, jak widzi ją rynek:</strong> Jeśli
308 
+spróbujesz sprawdzić ceny konkurencji, możesz na ich stronie wcale nie
309 
+znaleźć informacji lub znaleźć zwodzące informacje.  Może tak być dlatego,
310 
+że ich serwer może być ustawiony tak, by wykrywać połączenia od konkurencji
311 
+i blokować lub szerzyć dezinformacje wśród twojego personelu. Tor pozwala
312 
+firmom oglądać swój sektor tak, jak widzi go cała reszta.
313 
+</li>
314 
+<li><strong>Utrzymywanie strategii w tajemnicy:</strong> Inwestujący bank, na
315 
+przykład, mógłby nie zechcieć, by wyszukiwacze informacji gospodarczych
316 
+mogli śledzić, jakie strony oglądają ich analitycy.  Strategiczna ważność
317 
+wzorców ruchu sieciowego i podatność takich danych na inwigilację zaczyna
318 
+być coraz bardziej dostrzegana w kilku obszarach świata biznesu.
319 
+</li>
320 
+<li><strong>Odpowiedzialność:</strong> W czasach, gdy nieodpowiedzialna i
321 
+niezgłaszana działalność korporacji umniejszyła interesy za wiele miliardów
322 
+dolarów, dyrektor wprowadzający prawdziwe zarządzanie chciałby, by wszyscy
323 
+pracownicy mogli swobodnie ujawniać wewnętrzne problemy. Tor ułatwia
324 
+wewnętrzną zdawanie relacji, zanim niedobre dla firmy sprawy będą
325 
+nagłaśniane na zewnątrz.
326 
+</li>
327 
+</ul>
328 
+
329 
+<a name="bloggers"></a>
330 
+<h2><a class="anchor" href="#bloggers">Blogerzy używają Tora</a></h2>
331 
+<hr />
332 
+<ul>
333 
+<li>Często słyszymy o blogerach, którzy zostają <a
334 
+href="http://online.wsj.com/public/article/SB112541909221726743-Kl4kLxv0wSbjqrkXg_DieY3c8lg_20050930.html"
335 
+>pozwani do sądu</a> lub <a
336 
+href="http://www.usatoday.com/money/workplace/2005-06-14-worker-blogs-usat_x.htm"
337 
+>wyrzuceni z pracy</a> za mówienie całkowicie legalnych rzeczy w sieci, w
338 
+swoich blogach.</li>
339 
+<li>Polecamy <a href="http://w2.eff.org/bloggers/lg/">prawny przewodnik EFF dla
340 
+Blogerów</a>.</li>
341 
+<li>Global Voices utrzymuje <a
342 
+href="http://advocacy.globalvoicesonline.org/projects/guide/" >przewodnik po
343 
+anonimowym blogowaniu z Wordpress i Torem</a>.</li>
344 
+</ul>
345 
+
346 
+<a name="itprofessionals"></a>
347 
+<h2><a class="anchor" href="#itprofessionals">Profesjonaliści IT używają
348 
+Tora</a></h2>
349 
+<hr />
350 
+<ul>
351 
+<li>Aby weryfikować reguły zapory ogniowej opartej na adresach IP: Zapora
352 
+ogniowa może mieć jakieś polityki, które pozwalają tylko na pewne adres IP
353 
+lub ich zakresy. Tor może być używany do weryfikacji tych konfiguracji
354 
+poprzez używanie adresu IP spoza bloku IP przydzielonego dla danej firmy.</li>
355 
+<li>By omijać własne systemy zabezpieczeń dla ważnych działań zawodowych: Na
356 
+przykład, firma może mieć ścisłą politykę odnośnie materiałów, które
357 
+pracownicy mogą oglądać w Internecie. Przegląd logów odkrywa możliwe
358 
+naruszenia. Tor może być używany do weryfikacji informacji bez umieszczania
359 
+wyjątków w korporacyjnych systemach bezpieczeństwa.</li>
360 
+<li>By łączyć się z powrotem do rozmieszczonych usług: Inżynier sieciowy może
361 
+używać Tora do łączenia się z usługami bez potrzeby używania zewnętrznych
362 
+maszyn i kont użytkownika, jako część testów działania.</li>
363 
+<li>Do dostępu do zasobów Internetu: Akceptowalna polityka korzystania dla
364 
+personelu IT i normalnych pracowników jest zazwyczaj inna. Tor pozwala na
365 
+nieskrępowany dostęp do Internetu, pozostawiając na miejscu standardowe
366 
+polityki bezpieczeństwa.</li>
367 
+<li>By omijać problemy z siecią dostawcy Internetu (ISP): Czasami gdy ISP ma
368 
+problemy z trasowaniem lub DNS, Tor może uczynić zasoby Internetu
369 
+dostępnymi, podczas gdy sam ISP źle działa. To może być nieocenione w
370 
+sytuacjach kryzysowych. </li>
371 
+</ul>
372 
+
373 
+<p>
374 
+Prosimy przysyłać nam swoje opowiadania o sukcesach. Są bardzo ważne, gdyż
375 
+Tor daje anonimowość. Podczas, gdy spekulowanie o <a href="<page faq-abuse>"
376 
+>niepożądanych efektach Tora</a> wzbudza dreszcze, to kiedy wszystko działa,
377 
+nikt tego nie zauważa. To jest dobre dla użytkowników, ale nie tak dobre dla
378 
+nas, gdyż publikowanie historii o sukcesach w tym, jak ludzie i organizacje
379 
+pozostają anonimowi, może przynieś odwrotny efekt. Na przykład,
380 
+rozmawialiśmy z oficerem FBI, który powiedział, że używa Tora codziennie w
381 
+pracy &mdash; ale szybko dopisał prośbę, byśmy nie podawali szczegółów lub
382 
+jego nazwiska.</p>
383 
+
384 
+<p> Jak każda technologia, od ołówków to telefonów komórkowych, anonimowość może
385 
+być używana zarówno w dobrych, jak i złych celach. Widzieliście pewnie część
386 
+żywiołowej debaty (<a
387 
+href="http://www.wired.com/politics/security/commentary/securitymatters/2006/01/70000">za</a>,
388 
+<a href="http://www.edge.org/q2006/q06_4.html#kelly">przeciw</a> i <a
389 
+href="http://web.mit.edu/gtmarx/www/anon.html">akademickiej</a>) dotyczącej
390 
+anonimowości.  Projekt Tor jest oparty na wierze, że anonimowość nie jest
391 
+tylko dobrym pomysłem raz na jakiś czas - jest wymaganiem wolnego i
392 
+funkcjonującego społeczeństwa.  <a
393 
+href="http://www.eff.org/issues/anonymity">EFF ma dobry przegląd</a> na
394 
+temat jak istotna anonimowość była dla tworzenia Stanów
395 
+Zjednoczonych. Anonimowość jest postrzegana przez amerykańskie sądy jako
396 
+fundamentalne i ważne prawo.  Rządy same popierają anonimowość w wielu
397 
+przypadkach: <a href="https://www.crimeline.co.za/default.asp">policyjne
398 
+kanały informacyjne</a>, <a
399 
+href="http://www.texasbar.com/Content/ContentGroups/Public_Information1/Legal_Resources_Consumer_Information/Family_Law1/Adoption_Options.htm#sect2"
400 
+>serwisy adopcyjne</a>, <a
401 
+href="http://writ.news.findlaw.com/aronson/20020827.html">tożsamość oficerów
402 
+policji</a>, itd. Niemożliwe jest skrócenie tu całej debaty o anonimowości -
403 
+jest zbyt długa ze zbyt dużą liczbą niuansów, a jest wiele innych miejsc,
404 
+gdzie można znaleźć te informacje. Mamy stronę <a href="<page faq-abuse>">o
405 
+nadużyciach Tora</a> opisującą możliwe przypadki nadużyć Tora, ale wystarczy
406 
+powiedzieć, że jeśli chcesz nadużyć ten system, to albo będzie on w
407 
+większości zamknięty dla twoich celów (np. większość przekaźników sieci Tora
408 
+nie obsługuje SMTP w celu zapobiegania anonimowemu spamowaniu e-mail), albo
409 
+jeśli jesteś jednym z <a
410 
+href="http://www.schneier.com/blog/archives/2005/12/computer_crime_1.html">Czterech
411 
+Jeźdźców Informacyjnej Apokalipsy</a>, to masz lepsze środki niż Tor. Nie
412 
+odrzucając potencjalnych możliwości nadużyć Tora, ta strona kilka z wielu
413 
+ważnych sposobów wykorzystywania anonimowości on-line w dzisiejszych
414 
+czasach.</p>
415 
+</div>
416 
+#include <foot.wmi>
pl/trademark-faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,86 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+## translation metadata
7 
+# Revision: $Revision: 22138 $
8 
+# Translation-Priority: 3-low
9 
+#include "head.wmi" TITLE="Tor Trademark FAQ" CHARSET="UTF-8"
10 
+<div class="main-column">
11 
+
12 
+
13 
+<!-- PUT CONTENT AFTER THIS TAG -->
14 
+<h1>Najczęściej zadawane pytania o znaku handlowym Tora</h1>
15 
+<hr />
16 
+
17 
+<a id="usage"></a>
18 
+<h2>Jak mogę używać nazwy "Tor"?</h2>
19 
+<p>The Tor Project encourages developers to use the name Tor in ways that do
20 
+not confuse the public about the source of anonymity software and services.
21 
+If you are building open-source non-commercial software or services that
22 
+incorporate or work with The Tor Project's code, you may use the name
23 
+“Tor” in an accurate description of your work.  We ask you to include a
24 
+link to the official Tor website <a
25 
+href="https://www.torproject.org/">https://www.torproject.org/</a> so users
26 
+can verify the original source of Tor for themselves, and a note indicating
27 
+that your project is not sponsored by The Tor Project. For example, “This
28 
+product is produced independently from the Tor&#174; anonymity software and
29 
+carries no guarantee from The Tor Project about quality, suitability or
30 
+anything else.”</p>
31 
+
32 
+<a id="onionlogo"></a>
33 
+<h2>Czy mogę używać logo cebuli?</h2>
34 
+<p>If you're making non-commercial use of Tor software, you may also use the
35 
+Tor onion logo (as an illustration, not as a brand for your products).
36 
+Please don't modify the design or colors of the logo.  You can use items
37 
+that look like the Tor onion logo to illustrate a point (e.g. an exploded
38 
+onion with layers, for instance), so long as they're not used as logos in
39 
+ways that would confuse people.</p>
40 
+
41 
+<a id="combining"></a>
42 
+<h2>Czy mogę używać słowa "Tor" jako część nazwy mojego produktu lub domeny?</h2>
43 
+<p>We recommend that you don't do this, but rather find a name that will
44 
+accurately identify <i>your</i> products or services.  Remember that our
45 
+goal is to make sure that people aren't confused about whether your product
46 
+or project is made or endorsed by The Tor Project. Creating a new brand that
47 
+incorporates the Tor brand is likely to lead to confusion.</p>
48 
+
49 
+<a id="enforcing"></a>
50 
+<h2>Czy to oznacza, że wprowadzacie w życie prawa związane ze znakiem handlowym?</h2>
51 
+<p>Projekt Tor jest organizacją non-profit stworzoną, by badać i rozwijać
52 
+oprogramowanie anonimizujące i sieć Tor. Nie mamy zamiaru używać naszego
53 
+znaku do walki z innymi, lecz po to, by dać ludziom możliwość rozpoznawania
54 
+oprogramowania Projektu Tor. Prawo handlowe pozwala nam upewnić się, że
55 
+nasza nazwa używana jest wyłącznie z oryginalnym oprogramowaniem Tor i do
56 
+dokładnego opisu oprogramowania i usług. W końcu, by dobrze chronić
57 
+anonimowość użytkowników, muszą oni być w stanie zidentyfikować
58 
+oprogramowanie, którego używają, by znali jego siły i słabości. Tor stał się
59 
+znany jako pakiet oprogramowania i połączona z nim sieć anonimizujących
60 
+ruterów pośredniczących z dokumentacją on-line, instrukcjami odnośnie
61 
+zwiększania swojej anonimowości i ostrzeżeniami, że nawet na tym etapie jest
62 
+to oprogramowanie eksperymentalne.  Pracujemy z programistami, by poprawić
63 
+oprogramowanie i sieć oraz by zachęcać badaczy do dokumentowania ataków, co
64 
+pomoże nam jeszcze bardziej wzmocnić anonimowość. Samo oprogramowanie
65 
+rozpowszechniamy za darmo, lecz wymagamy, by było ono nam przypisywane. </p>
66 
+
67 
+<a id="commercial"></a>
68 
+<h2>A co, jeśli wytwarzam zamknięte, komercyjne produkty oparte na Torze?</h2>
69 
+<p>Skontaktuj się z nami i porozmawiajmy.</p>
70 
+
71 
+<a id="licensee"></a>
72 
+<h2>Czy są jacyś oficjalni licencjobiorcy znaku Tora?</h2>
73 
+<p>Tak. Kilka projektów otwartego, niekomercyjnego oprogramowania jest
74 
+oficjalnymi licencjobiorcami znaku Tora:</p>
75 
+<ul>
76 
+<li><a href="https://amnesia.boum.org/">The (Amnesic) Incognito Live System</a></li>
77 
+<li><a href="http://portabletor.sourceforge.net/">Portable Tor</a></li>
78 
+<li><a href="http://torstatus.kgprog.com/">Kprog Tor Status</a></li>
79 
+<li><a href="<page vidalia/index>">Vidalia</a></li>
80 
+<li><a href="http://www.anonymityanywhere.com/tork/">TorK</a></li>
81 
+</ul>
82 
+
83 
+</div>
84 
+
85 
+
86 
+#include <foot.wmi>
pl/translation-overview.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,186 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="Tor: Translation Overview" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h1>Tor: Strona Tłumaczeń</h1>
14 
+<hr />
15 
+
16 
+<p>
17 
+Paczki z Torem zawierają kilka różnych programów i wszystkie potrzebują
18 
+pomocy z tłumaczeniem.  Według ważności, są to: <a href="<page
19 
+vidalia/index>">Vidalia</a>, <a href="<page torbutton/index>">Torbutton</a>,
20 
+i <a href="https://check.torproject.org/">TorCheck</a>.  Proszę przeczytać
21 
+poniższe sekcje i pomóc. Jeśli potrzebujesz pomocy, to o nią poproś; zawsze
22 
+chętnie podamy pomocną dłoń.
23 
+</p>
24 
+
25 
+<a id="TTP"></a> <a id="TTPVidalia"></a>
26 
+<h2><a class="anchor" href="#TTP">Korzystanie z Portalu Tłumaczeń Tora</a></h2>
27 
+<hr />
28 
+
29 
+<p>
30 
+<a href="https://translation.torproject.org/">Portal Tłumaczeń Tora</a> jest
31 
+stroną pozwalającą użytkownikom na dodanie swoich tłumaczeń on-line,
32 
+używając ich przeglądarki internetowej. Zawiera listę wszystkich zdań lub
33 
+wyrażeń (nazywanych "łańcuchami znaków" - "string") używanych przez dany
34 
+projekt i pozwala zainteresowanym wolontariuszom na tłumaczenie kolejnych
35 
+zdań lub wyrażeń na miarę ich umiejętności.
36 
+</p>
37 
+
38 
+<p>
39 
+Można sprawdzić stan wszystkich tłumaczeń dla danego projektu odwiedzając
40 
+jego stronę.  Następujące statusy są aktualizowane w czasie rzeczywistym,
41 
+gdy dodawane są nowe tłumaczenia: <a
42 
+href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>, <a
43 
+href="https://translation.torproject.org/projects/torbutton/">Torbutton</a>,
44 
+i <a
45 
+href="https://translation.torproject.org/projects/torcheck/">TorCheck</a>.
46 
+</p>
47 
+
48 
+<p>
49 
+To get started using our translation website, you need to sign up for an
50 
+account. Visit the <a
51 
+href="https://translation.torproject.org/register.html">account registration
52 
+page</a> to get started. Be sure to enter a proper email address and a
53 
+strong password. After you fill in the form and use the 'Register Account'
54 
+button, you should see some text indicating that things worked out:
55 
+</p>
56 
+<pre>
57 
+Account created. You will be emailed login details and an activation code.
58 
+Please enter your activation code on the activation page.
59 
+
60 
+(Konto utworzone. Informacje o loginie i kod aktywacyjny zostaną wysłane e-mailem.
61 
+Proszę wprowadzić kod aktywacji na stronie aktywacji.)
62 
+</pre>
63 
+
64 
+<p>
65 
+Wkrótce po tym, jak zobaczysz ten tekst, na podany przez Ciebie adres
66 
+zostanie wysłany e-mail. Powinien on wyglądać następująco:
67 
+</p><pre>
68 
+A Pootle account has been created for you using this email address.
69 
+Your activation code is:
70 
+36074ec543c1fa23ceeaf8e187dfa43e
71 
+This message is sent to verify that the email address is in fact correct. If
72 
+you did not want to register an account, you may simply ignore the message.
73 
+Your user name is: example_user
74 
+Your password is: example_user
75 
+Your registered email address is: username@example.com
76 
+
77 
+(Zostało utworzone konto Pootle dla Ciebie, korzystając z tego adresu.
78 
+Twój kod aktywacyjny:
79 
+36074ec543c1fa23ceeaf8e187dfa43e
80 
+Ta wiadomość jest wysłana, by zweryfikować, że adres e-mail jest poprawny.
81 
+Jeśli nie chciałeś/aś rejestrować konta, możesz po prosu zignorować tę wiadomość.
82 
+Twoja nazwa użytkownika: example_user
83 
+Twoje hasło: example_user
84 
+Twój zarejestrowany adres e-mail: username@example.com
85 
+</pre>
86 
+
87 
+<p>
88 
+Once you've received the email, you'll need to activate your account by
89 
+visiting the <a
90 
+href="https://translation.torproject.org/activate.html">activation
91 
+page</a>.  Enter your username and activation code into the form and then
92 
+submit the form by pressing the "Activate Account" button.  You'll see a
93 
+message that says:
94 
+</p><pre>
95 
+Redirecting to login Page...
96 
+Your account has been activated! Redirecting to login...
97 
+
98 
+(Przekierowywanie na stronę logowania...
99 
+Twoje konto zostało aktywowane! Przekierowywanie do logowania...)
100 
+</pre>
101 
+
102 
+<p>
103 
+Gdy zalogujesz się na swoje nowe konto, zostaniesz poproszony o
104 
+skonfigurowanie swoich podstawowych preferencji językowych na <a
105 
+href="https://translation.torproject.org/home/options.html">stronie
106 
+opcji</a>.  Powinieneś/Powinnaś przynajmniej ustawić język interfejsu
107 
+użytkownika, wybrać projekty, których tłumaczeniem jesteś zainteresowany/a i
108 
+w końcu języki, na które chcesz tłumaczyć.  Po zakończeniu zachowaj zmiany
109 
+klikając "Zapisz zmiany" ("Save Changes").
110 
+</p>
111 
+
112 
+<p>
113 
+Teraz możesz zacząć tłumaczyć!
114 
+</p>
115 
+
116 
+<p>
117 
+At this point, you can select a project, such as <a
118 
+href="https://translation.torproject.org/projects/vidalia/">Vidalia</a>.
119 
+You'll see a nice list of all of the currently supported languages along
120 
+with the current translation progress. Select a language &mdash; in our
121 
+example, you'll click <a
122 
+href="https://translation.torproject.org/de/vidalia/">German</a>. The next
123 
+page should show you a single row of data for the file "<a
124 
+href='https://translation.torproject.org/de/vidalia/vidalia_de.po?translate=1&amp;view=1'>vidalia_de.po</a>".
125 
+This is the file with all of the currently translated German strings for
126 
+Vidalia. You should click on the "<a
127 
+href='https://translation.torproject.org/de/vidalia/index.html?editing=1'>Show
128 
+Editing Functions</a>" link above the 'vidalia_de.po' row. Next you should
129 
+click the "<a
130 
+href='https://translation.torproject.org/de/vidalia/translate.html?fuzzy=1&amp;editing=1&amp;blank=1'>Quick
131 
+Translate</a>" link. This will take you to the first untranslated string in
132 
+the language group for the current project.
133 
+</p>
134 
+
135 
+<p>
136 
+Jeśli jesteś w stanie, przetłumacz dane wyrażenie i kliknij 'Submit'
137 
+("Wyślij").  Jeśli nie masz pewności, kliknij 'Suggest'
138 
+("Zasugeruj"). Możesz dodawać komentarze do tłumaczeń, jeśli Twoim zdaniem
139 
+trzeba coś lepiej wyjaśnić.
140 
+</p>
141 
+
142 
+<p>
143 
+Gdy skończyłeś/aś, musisz wysłać swoje zmiany. Wróć na stronę z <a
144 
+href="https://translation.torproject.org/de/vidalia/index.html?editing=1">funkcjami
145 
+edycji</a>, i kliknij link "<a
146 
+href='https://translation.torproject.org/de/vidalia/index.html?editing=1&amp;docommit=1&amp;commitfile=vidalia_de.po'>Commit</a>".
147 
+To wyśle Twoje zmiany do <a
148 
+href="https://svn.torproject.org/svn/translation/trunk/projects/vidalia/de/">Modułu
149 
+subversion do tłumaczeń</a> do właściwego miejsca względem języka i projektu
150 
+(Vidalia i niemiecki w tym przypadku).
151 
+</p>
152 
+
153 
+<p>
154 
+To wszystko, czego potrzeba! Wykonaj ponownie wszystkie kroki i pomóż też
155 
+projektom Torbutton i Torcheck.
156 
+</p>
157 
+
158 
+<p>
159 
+Jeśli Twojego języka nie ma jeszcze na liście, wyślij list do
160 
+<tt>tor-translation AT torproject.org</tt>, a my go dodamy.
161 
+</p>
162 
+
163 
+<p>
164 
+For more advanced users who like to translate without a web browser, you can
165 
+also download the .po file directly. You'll find this option after clicking
166 
+on the "<a
167 
+href='https://translation.torproject.org/de/vidalia/index.html?editing=1'>Show
168 
+Editing Functions</a>" link. You should see a link to download the "<a
169 
+href="https://translation.torproject.org/de/vidalia/vidalia_de.po">PO
170 
+file</a>".  If this option fits your working habits, by all means, please
171 
+use it! You may find a program called <a
172 
+href="http://www.poedit.net/">Poedit</a> to make the job easier, especially
173 
+for right-to-left languages that don't work as well in text editors. If
174 
+you're using Poedit, you should disable compiling .mo files in Poedit's
175 
+preferences (File -&gt; Preferences -&gt; Editor -&gt; Behavior, uncheck
176 
+"Automatically compile .mo file on save").  When you're finished translating
177 
+the .po file, you can upload it by using the "upload file" form in the upper
178 
+right hand corner: simply select the file and click the 'Upload file'
179 
+button.
180 
+</p>
181 
+
182 
+  </div>
183 
+
184 
+
185 
+
186 
+#include <foot.wmi>
po2wml.sh
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,194 @@
1 
+#!/bin/bash
2 
+#
3 
+# Author: Runa Sandvik, <runa.sandvik@gmail.com>
4 
+# Google Summer of Code 2009
5 
+#
6 
+# This is Free Software (GPLv3)
7 
+# http://www.gnu.org/licenses/gpl-3.0.txt
8 
+#
9 
+# This script will convert all the translated po files back to wml
10 
+# files.
11 
+#
12 
+# For more information, see the HOWTO and README in
13 
+# translation/tools/gsoc09.
14 
+#
15 
+
16 
+### start config ###
17 
+
18 
+# Location of the wml files
19 
+wmldir="$PWD"
20 
+
21 
+# Location of the po files,
22 
+podir="`dirname $wmldir`/translation/projects/website"
23 
+
24 
+# A lot of the wml files have custom tags. These tags have been defined
25 
+# in website/include/versions.wmi. Tags that people usually forget to close,
26 
+# as well as tags that are not defined in versions.wmi have been added.
27 
+# See: https://svn.torproject.org/svn/website/trunk/include/versions.wmi
28 
+customtag=`echo $(cat "$wmldir/include/versions.wmi" | awk '{ printf "<%s> " , $2 }' | sed 's/<>//g') "<svnsandbox> <svnwebsite> <svnprojects> <input> <hr> <br> <img> <gitblob>"`
29 
+
30 
+# We also need to use the nodefault option of po4a; space separated list
31 
+# of tags that the module should not try to set by default in any
32 
+# category. For now, we only need the input tag.
33 
+nodefault='<input>'
34 
+
35 
+### end config ###
36 
+
37 
+# Create a lockfile to make sure that only one instance of the script
38 
+# can run at any time.
39 
+LOCKFILE=po2wml.lock
40 
+
41 
+if lockfile -! -l 60 -r 3 "$LOCKFILE";
42 
+then
43 
+	echo "unable to acquire lock" >2
44 
+	exit 1
45 
+fi
46 
+
47 
+trap "rm -f '$PWD/$LOCKFILE'" exit
48 
+
49 
+# Check if translation/projects/website exist, i.e. has been checked out
50 
+if [ ! -d $podir ]
51 
+then
52 
+	echo "Have you remembered to check out translation/projects/website?"
53 
+	exit 1
54 
+fi
55 
+
56 
+# cd to the right directory so we can commit the files later
57 
+cd "$wmldir"
58 
+
59 
+# We need to find the po files
60 
+po=`find $podir -regex '^'$podir'/.*/.*\.po' -type f`
61 
+
62 
+# For every wml, update po
63 
+for file in $po ; do
64 
+
65 
+	# Get the basename of the file we are dealing with
66 
+	pofile=`basename $file`
67 
+
68 
+	# Strip the file for its original extension and the translation
69 
+	# priority, and add .wml
70 
+	wmlfile="`echo $pofile | cut -d . -f 2`.wml"
71 
+
72 
+	# Find out what directory the file is in.
73 
+	indir=`dirname $file`
74 
+
75 
+	# We also need to know what one directory up is
76 
+	onedirup=`dirname $indir`
77 
+
78 
+	# We need to find out what subdirectory we are in
79 
+	subdir=`dirname $file | sed "s#$onedirup/##"`
80 
+
81 
+	# And which language we are dealing with
82 
+	lang=`dirname $indir | sed "s#$podir/##"`
83 
+
84 
+	# Time to write the translated wml file.
85 
+	# The translated document is written if 80% or more of the po
86 
+	# file has been translated. Example: Use '-k 21' to set this
87 
+	# number down to 21%. Also, po4a-translate will only write the
88 
+	# translated document if 80% or more has been translated.
89 
+	# However, it will delete the wml if less than 80% has been
90 
+	# translated. To avoid having our current, translated wml files
91 
+	# deleted, convert the po to a temp wml first. If this file was
92 
+	# actually written, rename it to wml.
93 
+
94 
+	# Convert translations to directories such as website/nb/.
95 
+	function nosubdir {
96 
+		# The location of the english wml file
97 
+		english="$wmldir/en/$wmlfile"
98 
+
99 
+		# Convert the files
100 
+		po4a-translate -f wml -m "$english" -p "$file" -l "$wmldir/$subdir/tmp-$wmlfile" --master-charset utf-8 -L utf-8 -o customtag="$customtag" -o nodefault="$nodefault"
101 
+
102 
+		# Check to see if the file was written
103 
+                if [ -e "$wmldir/$subdir/tmp-$wmlfile" ]
104 
+		then
105 
+			mv "$wmldir/$subdir/tmp-$wmlfile" "$wmldir/$subdir/$wmlfile"
106 
+
107 
+                        # Remove last three lines in file
108 
+			sed -i -e :a -e '$d;N;2,3ba' -e 'P;D' "$wmldir/$subdir/$wmlfile"
109 
+
110 
+			# Include foot.wmi
111 
+			echo "#include <foot.wmi>" >> "$wmldir/$subdir/$wmlfile"
112 
+		fi
113 
+	}
114 
+
115 
+	# Convert translations to directories such as website/torbrowser/nb/.
116 
+	function subdir {
117 
+		# The location of the english wml file
118 
+                english="$wmldir/$subdir/en/$wmlfile"
119 
+
120 
+		# Convert the files
121 
+		po4a-translate -f wml -m "$english" -p "$file" -l "$wmldir/$subdir/$lang/tmp-$wmlfile" --master-charset utf-8 -L utf-8 -o customtag="$customtag" -o nodefault="$nodefault"
122 
+
123 
+		# Check to see if the file was written
124 
+		if [ -e "$wmldir/$subdir/$lang/tmp-$wmlfile" ]
125 
+		then
126 
+			mv "$wmldir/$subdir/$lang/tmp-$wmlfile" "$wmldir/$subdir/$lang/$wmlfile"
127 
+
128 
+			# Remove last three lines in file
129 
+			sed -i -e :a -e '$d;N;2,3ba' -e 'P;D' "$wmldir/$subdir/$lang/$wmlfile"
130 
+
131 
+			# Include foot.wmi
132 
+			echo "#include <foot.wmi>" >> "$wmldir/$subdir/$lang/$wmlfile"
133 
+		fi
134 
+	}
135 
+
136 
+	# If $onedirup is equal to $lang, that means we do not have a
137 
+	# subdirectory.
138 
+	if [ $onedirup == $lang ]
139 
+	then
140 
+		# If the current subdirectory is "zh_CN" use "zh-cn" instead
141 
+		if [ $subdir = "zh_CN" ]
142 
+		then
143 
+			subdir="zh-cn"
144 
+			nosubdir
145 
+		fi
146 
+
147 
+		# If the current directory is "nb" use "no" instead
148 
+		if [ $subdir = "nb" ]
149 
+		then
150 
+			subdir="no"
151 
+			nosubdir
152 
+		fi
153 
+
154 
+		# If the current directory is "sv" use "se" instead
155 
+		if [ $subdir = "sv" ]
156 
+		then
157 
+			subdir="se"
158 
+			nosubdir
159 
+		fi
160 
+
161 
+		# Convert everything else
162 
+		if [[ $subdir != "en" && $subdir != "zh_CN" && $subdir != "nb" && $subdir != "sv" ]]
163 
+		then
164 
+			nosubdir
165 
+		fi
166 
+	else
167 
+		# If the current language is "zh_CN" use "zh-cn" instead
168 
+		if [ $lang = "zh_CN" ]
169 
+		then
170 
+			lang="zh-cn"
171 
+			subdir
172 
+		fi
173 
+
174 
+		# If the current language is "nb" use "no" instead
175 
+		if [ $lang = "nb" ]
176 
+		then
177 
+			lang="no"
178 
+			subdir
179 
+		fi
180 
+
181 
+		# If the current language is "sv" use "se" instead
182 
+		if [ $lang = "sv" ]
183 
+		then
184 
+			lang="se"
185 
+			subdir
186 
+		fi
187 
+
188 
+		# Convert everything else
189 
+		if [[ $lang != "en" && $lang != "zh_CN" && $lang != "nb" && $lang != "sv" ]]
190 
+		then
191 
+			subdir
192 
+		fi
193 
+	fi
194 
+done
press/.deps/.stamp
Zeige Datei @ 2a9aaa802
press/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1 @@
1 
+include $(WMLBASE)/Makefile.common
press/de/2008-12-19-roadmap-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,90 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22077 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="THE TOR PROJECT ANNOUNCES THREE-YEAR DEVELOPMENT ROADMAP" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Zur sofortigen Veröffentlichung</h2>
17 
+
18 
+<h2><strong>Das Tor Projekt veröffentlicht 3-Jahres-Entwicklungsplan</strong></h2>
19 
+
20 
+<p><strong>DEDHAM, MA, USA</strong> - Das Tor Projekt hat seinen 3-Jahres
21 
+Entwicklungsplan <a href="/press/presskit/2008-12-19-roadmap-full.pdf">
22 
+3-Jahres Entwicklungsplan</a> veröffentlicht, welcher den Fokus insbesondere
23 
+auf die Verbreitung von Anti-Zensur Werkzeugen und Diensten für die Stärkung
24 
+der Freiheit des Internets in geschlossenen Gesellschaften richtet.</p>
25 
+
26 
+<p>Tor's tools and technologies are already used by hundreds of thousands of
27 
+people to protect their activities online.  These users include journalists
28 
+and human rights workers in politically rigid countries communicating with
29 
+whistleblowers and dissidents.  Law enforcement officers on Internet sting
30 
+operations stay anonymous with Tor, as do people wanting to post socially
31 
+sensitive information in chat rooms, like rape or abuse survivors and those
32 
+with illnesses.  The Tor network also provides protection for people
33 
+looking for another layer of privacy from the millions of websites and ISPs
34 
+bent on collecting private information and tracking their moves online.</p>
35 
+
36 
+<p>While Tor's original goal was to provide this important anonymity, many
37 
+people around the world use Tor to get around Internet censorship, as
38 
+well.  <a href="http://www.hrw.org/">Human Rights Watch</a> and <a
39 
+href="http://globalvoicesonline.org/">Global Voices Online</a> have both
40 
+recommended Tor as a tool to circumvent censorship regimes in oppressive
41 
+nations. The roadmap is focused on providing anti-censorship tools and
42 
+services for the advancement of Internet freedom in closed societies.</p>
43 
+
44 
+<p>"If your Internet provider can't see what sites you're looking at, that also
45 
+means they can't prevent you from reaching sites they don't want you to
46 
+see," said Roger Dingledine, Tor Project Leader.  "This new roadmap with
47 
+support from the larger community will let us make Tor even better at
48 
+fighting censorship.  With three years of funding, we can tackle larger
49 
+problems than before, and we can focus on making sure that Tor can grow to
50 
+handle all the people who want to use it."</p>
51 
+
52 
+<p>Tor lädt zusätzliche Unterstützer ein, sich den <a
53 
+href="https://www.torproject.org/sponsors">aktuellen Sponsoren</a>, wie dem
54 
+Broadcasting Board of Governors, der NLnet Stiftung und hunderten
55 
+Einzelspendern, anzuschliessen. Zwar reichen existierende Spenden aus, den
56 
+Entwicklungsplan zu beginnen; damit aus dem Plan allerdings konkrete
57 
+Werkzeuge werden können, fehlen noch zusätzliche 2,1 Millionen Dollar
58 
+innerhalb der nächsten drei Jahre.</p>
59 
+
60 
+<h2>Über das Tor Projekt</h2>
61 
+
62 
+<p>Das Tor Projekt mit offiziellem Sitz in Dedham, Massachusetts, USA
63 
+entwickelt freie und quelloffene Software für den normalen
64 
+Internetnutzer. Tor entstand aus einer Zusammenarbeit mit dem
65 
+Marineforschungslabor der Vereinigten Staaten im Jahr 2001 und wurde im Jahr
66 
+2006 offiziell als gemeinnützig annerkant. Das Tor Projekt arbeitet heute
67 
+mit vielen Individuen, Nichtregierungsorganisationen, Strafverfolgern und
68 
+Firmen weltweit zusammen und hilft ihnen, ihre Anonymität online zu wahren.</p>
69 
+
70 
+<p>Zusätzlich zu den Anstrengungen, die Tor Software zu entwickeln und zu
71 
+betreuen, hilft das Tor Projekt auch der wissenschaftlichen Gemeinschaft zu
72 
+verstehen, wie man skalierbare und sichere anonyme Netze aufbaut und
73 
+vermisst.  Die Tor Entwickler veröffentlichen jedes Jahr mehrere
74 
+Forschungsergebnisse auf grossen IT-Sicherheitskonferenzen und nahezu auf
75 
+jeder grossen Sicherheitskonferenz heutzutage gibt es einen Vortrag über
76 
+Themen aus dem Tor-Umfeld.</p>
77 
+
78 
+<p>Das "Onion Logo" und "Tor" sind eingetragene Warenzeichen der The Tor
79 
+Project, Inc.</p>
80 
+
81 
+<p>Kontakt: Andrew Lewman</p>
82 
+<p>Tel: +1-781-424-9877</p>
83 
+<p>Email: execdir@torproject.org</p>
84 
+<p><a href="https://www.torproject.org/">Webseite: Tor Projet</a></p>
85 
+<div align=center>###</div>
86 
+
87 
+</div>
88 
+
89 
+
90 
+#include <foot.wmi>
press/de/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,60 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22070 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor Press Page"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Tor Presse und Medien Information</h2>
17 
+<div class="underline"></div>
18 
+
19 
+
20 
+<!-- BEGIN SIDEBAR -->
21 
+<div class="sidebar">
22 
+<h3>Pressekontakt</h3>
23 
+<address>
24 
+Andrew Lewman execdir@torproject.org +1-781-424-9877
25 
+</address>
26 
+</div>
27 
+
28 
+
29 
+<!-- END SIDEBAR -->
30 
+<h3>Pressemitteilungen</h3>
31 
+<ul>
32 
+<li>25 March 2010. Tor and Printfection launch <a href="<page
33 
+press/2010-03-25-tor-store-press-release>">The Tor Store</a>.</li>
34 
+<li>12 March 2009.  Tor veröffentlicht einen neuen <a href="<page
35 
+press/2009-03-12-performance-roadmap-press-release>">Plan zur
36 
+Leistungssteigerung</a> und eine Kampagne.</li>
37 
+<li>19 December 2008.  Tor veröffentlicht den <a href="<page
38 
+press/2008-12-19-roadmap-press-release>">Entwicklungsplan</a> für die
39 
+nächsten drei Jahre.</li>
40 
+</ul>
41 
+<br />
42 
+<div class="nb">
43 
+<h3>Kurzlinks für ein besseres Kennenlernen von Tor</h3>
44 
+<ol>
45 
+<li>Inwiefern unterscheidet sich Tor von <a href="<page
46 
+docs/faq>#Torisdifferent">anderen Proxy Lösungen</a>?</li>
47 
+<li><a href="/press/presskit/2009-General-Online-Anonymity-with-Tor.pdf">Wozu
48 
+Anonymität und Online Privatsphäre</a>?</li>
49 
+<li><a href="/press/presskit/2009-General-Background-on-Tor-Project-Inc.pdf">Wer
50 
+ist Tor Project, Inc.</a>?</li>
51 
+<li><a
52 
+href="https://blog.torproject.org/blog/circumvention-and-anonymity">Weshalb
53 
+Anonymität wichtig für Umgehung ist</a>.</li>
54 
+</ol>
55 
+</div>
56 
+</div>
57 
+
58 
+
59 
+
60 
+#include <foot.wmi>
press/en/2008-12-19-roadmap-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,97 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22077 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: THE TOR PROJECT ANNOUNCES THREE-YEAR DEVELOPMENT ROADMAP" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page press/press>">Press &raquo; </a>
10 
+    <a href="<page press/2008-12-19-roadmap-press-release>">Tor Project Announces Three-Year Development Roadmap</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h2>FOR IMMEDIATE RELEASE</h2>
16 
+
17 
+    <h2><strong>THE TOR PROJECT ANNOUNCES THREE-YEAR DEVELOPMENT ROADMAP</strong></h2>
18 
+
19 
+    <p><strong>DEDHAM, MA</strong> - The Tor Project has published its <a
20 
+    href="/press/presskit/2008-12-19-roadmap-full.pdf">three year
21 
+    development roadmap</a>, focused on providing anti-censorship tools and
22 
+    services for the advancement of Internet freedom in closed
23 
+    societies.</p>
24 
+
25 
+    <p>Tor's tools and technologies are already used by hundreds of
26 
+    thousands of people to protect their activities online.  These
27 
+    users include journalists and human rights workers in politically
28 
+    rigid countries communicating with whistleblowers and dissidents.
29 
+    Law enforcement officers on Internet sting operations stay
30 
+    anonymous with Tor, as do people wanting to post socially
31 
+    sensitive information in chat rooms, like rape or abuse survivors
32 
+    and those with illnesses.  The Tor network also provides
33 
+    protection for people looking for another layer of privacy from
34 
+    the millions of websites and ISPs bent on collecting private
35 
+    information and tracking their moves online.</p>
36 
+
37 
+    <p>While Tor's original goal was to provide this important
38 
+    anonymity, many people around the world use Tor to get around
39 
+    Internet censorship, as well.  <a href="http://www.hrw.org/">Human
40 
+    Rights Watch</a> and <a href="http://globalvoicesonline.org/">Global
41 
+    Voices Online</a> have both recommended Tor as a tool to circumvent
42 
+    censorship regimes in oppressive nations. The roadmap is focused
43 
+    on providing anti-censorship tools and services for the
44 
+    advancement of Internet freedom in closed societies.</p>
45 
+
46 
+    <p>"If your Internet provider can't see what sites you're looking
47 
+    at, that also means they can't prevent you from reaching sites
48 
+    they don't want you to see," said Roger Dingledine, Tor Project
49 
+    Leader.  "This new roadmap with support from the larger community
50 
+    will let us make Tor even better at fighting censorship.  With
51 
+    three years of funding, we can tackle larger problems than
52 
+    before, and we can focus on making sure that Tor can grow to
53 
+    handle all the people who want to use it."</p>
54 
+
55 
+    <p>Tor welcomes additional sponsors to join <a
56 
+    href="https://www.torproject.org/sponsors">current sponsors</a>;
57 
+    such as the Broadcasting Board of Governors, the NLnet Foundation,
58 
+    and hundreds of individual donors. While existing funders are enough to
59 
+    get the items on the roadmap started, an additional $2.1 million over the
60 
+    next three years will turn the roadmap into usable tools.</p>
61 
+
62 
+    <h2>ABOUT THE TOR PROJECT</h2>
63 
+
64 
+    <p>Based in Dedham, MA, The Tor Project
65 
+    develops free and open-source software that provides online
66 
+    anonymity to the everyday Internet user. Tor was born out of a
67 
+    collaboration with the U.S. Naval Research Lab starting in 2001,
68 
+    and it became an official U.S. 501(c)(3) non-profit in 2006. The
69 
+    Tor Project now works with many individuals, NGOs, law
70 
+    enforcement agencies, and businesses globally to help them
71 
+    protect their anonymity online.</p>
72 
+
73 
+    <p>In addition to its efforts developing and maintaining the Tor
74 
+    anonymity software and the Tor network, The Tor Project also
75 
+    helps to lead the research community in understanding how to
76 
+    build and measure scalable and secure anonymity networks. The Tor
77 
+    developers publish several new research papers each year in major
78 
+    academic security conferences, and just about every major
79 
+    security conference these days includes a Tor-related paper.</p>
80 
+
81 
+    <p>The "Onion Logo" and "Tor" wordmark are registered trademarks
82 
+    of The Tor Project, Inc.</p>
83 
+
84 
+    <p>Contact: Andrew Lewman</p>
85 
+    <p>Tel: +1-781-424-9877</p>
86 
+    <p>Email: execdir@torproject.org</p>
87 
+    <p><a href="https://www.torproject.org/">Website: Tor Project</a></p>
88 
+  </div>
89 
+  <!-- END MAINCOL -->
90 
+  <div id = "sidecol">
91 
+#include "side.wmi"
92 
+#include "info.wmi"
93 
+  </div>
94 
+  <!-- END SIDECOL -->
95 
+</div>
96 
+<!-- END CONTENT -->
97 
+#include <foot.wmi>
press/en/2009-03-12-performance-roadmap-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,80 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22077 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="TOR PROJECT LAUNCHES PERFORMANCE ROADMAP AND CAMPAIGN" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page press/press>">Press &raquo; </a>
10 
+    <a href="<page press/2009-03-12-performance-roadmap-press-release>">Tor Project Launches Performance Roadmap and Campaign</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h2>FOR IMMEDIATE RELEASE</h2>
16 
+
17 
+    <h2><strong>TOR PROJECT LAUNCHES PERFORMANCE ROADMAP AND CAMPAIGN</strong></h2>
18 
+
19 
+    <p><strong>DEDHAM, MA</strong> -The Tor Project has <a href="/press/presskit/2009-03-11-performance.pdf">launched a roadmap</a> for dramatically improving the performance of the public Tor network over the next year.  A combination of existing funding and a needed $1 million over the next 12 months will ensure success.  This campaign is a direct result of the recently published <a href="<page press/2008-12-19-roadmap-press-release>">3-Year Development Roadmap</a>.  The roadmap incorporates research and actions from a number of sources which define the next steps for improving performance of the public Tor network.  The most requested feature by users of the public Tor network is to increase performance while keeping strong anonymity intact.</p>
20 
+
21 
+    <p>As Tor's user base has grown, the performance of the Tor network has suffered.  Over the past few years, Tor's funding (and thus the development effort) has focused on usability and blocking-resistance.  We've come up with a portable self-contained Windows bundle; deployed tools to handle the upcoming censorship arms race; further
22 
+    developed supporting applications like Vidalia, Torbutton, and Thandy; made it easier for users to be relays by adding better rate limiting and an easy graphical interface with uPnP support; developed an effective
23 
+    translation and localization team and infrastructure; and spread understanding of Tor in a safe word-of-mouth way that stayed mostly under the radar of censors.  All of these successess have contributed to the growing user base and increased stress on the public Tor network.</p>
24 
+
25 
+    <p>Tor's tools and technologies are already used by hundreds of
26 
+    thousands of people to protect their activities online.  These
27 
+    users include journalists and human rights workers in politically
28 
+    rigid countries communicating with whistleblowers and dissidents.
29 
+    Law enforcement officers on Internet sting operations stay
30 
+    anonymous with Tor, as do people wanting to post socially
31 
+    sensitive information in chat rooms, like rape or abuse survivors
32 
+    and those with illnesses.  The Tor network also provides
33 
+    protection for people looking for another layer of privacy from
34 
+    the millions of websites and ISPs bent on collecting private
35 
+    information and tracking their moves online.</p>
36 
+
37 
+    <p>Tor welcomes additional sponsors to join our <a
38 
+    href="<page about/sponsors>">current sponsors</a>;
39 
+    such as the Broadcasting Board of Governors, the NLnet Foundation,
40 
+    and hundreds of individual donors. While existing funders are enough to
41 
+    get the items on the roadmap started, an additional $1 million over the
42 
+    next year will dramatically increase the performance of the public Tor network.</p>
43 
+
44 
+    <h2>ABOUT THE TOR PROJECT</h2>
45 
+
46 
+    <p>Based in Dedham, MA, The Tor Project
47 
+    develops free and open-source software that provides online
48 
+    anonymity to the everyday Internet user. Tor was born out of a
49 
+    collaboration with the U.S. Naval Research Lab starting in 2001,
50 
+    and it became an official U.S. 501(c)(3) non-profit in 2006. The
51 
+    Tor Project now works with many individuals, NGOs, law
52 
+    enforcement agencies, and businesses globally to help them
53 
+    protect their anonymity online.</p>
54 
+
55 
+    <p>In addition to its efforts developing and maintaining the Tor
56 
+    anonymity software and the Tor network, The Tor Project also
57 
+    helps to lead the research community in understanding how to
58 
+    build and measure scalable and secure anonymity networks. The Tor
59 
+    developers publish several new research papers each year in major
60 
+    academic security conferences, and just about every major
61 
+    security conference these days includes a Tor-related paper.  Tor is a
62 
+    project-funded organization with eight full-time staff.</p>
63 
+
64 
+    <p>The "Onion Logo" and "Tor" wordmark are registered trademarks
65 
+    of The Tor Project, Inc.</p>
66 
+
67 
+    <p>Contact: Andrew Lewman</p>
68 
+    <p>Tel: +1-781-424-9877</p>
69 
+    <p>Email: execdir@torproject.org</p>
70 
+    <p><a href="https://www.torproject.org/">Website: Tor Project</a></p>
71 
+  </div>
72 
+  <!-- END MAINCOL -->
73 
+  <div id = "sidecol">
74 
+#include "side.wmi"
75 
+#include "info.wmi"
76 
+  </div>
77 
+  <!-- END SIDECOL -->
78 
+</div>
79 
+<!-- END CONTENT -->
80 
+#include <foot.wmi>
press/en/2010-03-25-tor-store-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,97 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22100 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="TOR PROJECT AND PRINTFECTION ANNOUNCE THE TOR STORE" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page press/press>">Press &raquo; </a>
10 
+    <a href="<page press/2010-03-25-tor-store-press-release>">Tor Project And Printfection Announce the Tor Store</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h2>FOR IMMEDIATE RELEASE</h2>
16 
+
17 
+    <h2><strong>TOR PROJECT AND PRINTFECTION ANNOUNCE THE TOR STORE</strong></h2>
18 
+
19 
+    <p><strong>WALPOLE, MA</strong> The Tor Project and Printfection launch
20 
+    <a href="http://printfection.com/torprojectstore">The Tor Store</a> for
21 
+    all your Tor fan needs. The Tor Store offers a range of t-shirts for
22 
+    men and women, mugs, and sweatshirts emblazed with everyones favorite
23 
+    techno-onion logo. Community feedback shapes the product selection.
24 
+    This first release of the store contains some of the most requested
25 
+    Tor-logo enabled items.</p>
26 
+
27 
+    <p> <blockquote>"The Tor Project is leveraging Printfection's on-demand
28 
+    merchandise fulfillment technology to engage their supporters and generate
29 
+    additional revenue to help protect anonymity online.  We're proud to be
30 
+    associated with such an important project."
31 
+    </blockquote>
32 
+     -- Casey Shorr, CEO of Printfection</p>
33 
+
34 
+    <p>Tor's tools and technologies are already used by millions
35 
+    of people to protect their activities online.  These
36 
+    users include journalists and human rights workers in politically
37 
+    rigid countries communicating with whistleblowers and dissidents.
38 
+    Law enforcement officers on Internet sting operations stay
39 
+    anonymous with Tor, as do people wanting to post socially
40 
+    sensitive information in chat rooms, like rape or abuse survivors
41 
+    and those with illnesses.  The Tor network also provides
42 
+    protection for people looking for another layer of privacy from
43 
+    the millions of websites and ISPs bent on collecting private
44 
+    information and tracking their moves online.</p>
45 
+
46 
+    <p>Tor welcomes your support through purchasing of Tor branded items and
47 
+    through the consistent donations of thousands of individuals through our
48 
+    <a href="<page donate/donate>">various methods of donation</a>.  </p>
49 
+
50 
+    <h2>ABOUT THE TOR PROJECT</h2>
51 
+
52 
+    <p>Based in Walpole, MA, The Tor Project
53 
+    develops free and open-source software that provides online
54 
+    anonymity to the everyday Internet user. Tor was born out of a
55 
+    collaboration with the U.S. Naval Research Lab starting in 2001,
56 
+    and it became an official U.S. 501(c)(3) non-profit in 2006. The
57 
+    Tor Project now works with many individuals, NGOs, law
58 
+    enforcement agencies, and businesses globally to help them
59 
+    protect their anonymity online.</p>
60 
+
61 
+    <p>In addition to its efforts developing and maintaining the Tor
62 
+    anonymity software and the Tor network, The Tor Project also
63 
+    helps to lead the research community in understanding how to
64 
+    build and measure scalable and secure anonymity networks. The Tor
65 
+    developers publish several new research papers each year in major
66 
+    academic security conferences, and just about every major
67 
+    security conference these days includes a Tor-related paper.  Tor is a
68 
+    project-funded organization with eight full-time staff.</p>
69 
+
70 
+    <h2>ABOUT PRINTFECTION</h2>
71 
+
72 
+    <p>Printfection is the leading all-in-one merchandise fulfillment
73 
+    service. Tens of thousands of businesses use our technologies and
74 
+    services to power their merchandising programs. We make it easy for any
75 
+    sized organization to sell t-shirts, mugs, totes, and other promotional
76 
+    merchandise online.  Launched in 2004, Printfection now hosts over
77 
+    20,000 online merchandise stores fulfilling orders from three locations
78 
+    nationwide. The company is based in Denver, Colorado. Learn more about
79 
+    Printfection at www.Printfection.com.</p>
80 
+
81 
+    <p>The "Onion Logo" and "Tor" wordmark are registered trademarks
82 
+    of The Tor Project, Inc.</p>
83 
+
84 
+    <p>Contact: Andrew Lewman</p>
85 
+    <p>Tel: +1-781-424-9877</p>
86 
+    <p>Email: execdir@torproject.org</p>
87 
+    <p><a href="https://www.torproject.org/">Website: Tor Project</a></p>
88 
+  </div>
89 
+  <!-- END MAINCOL -->
90 
+  <div id = "sidecol">
91 
+#include "side.wmi"
92 
+#include "info.wmi"
93 
+  </div>
94 
+  <!-- END SIDECOL -->
95 
+</div>
96 
+<!-- END CONTENT -->
97 
+#include <foot.wmi>
press/en/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,42 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22070 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Press Page"
6 
+<!-- PUT CONTENT AFTER THIS TAG -->
7 
+
8 
+<h2>Tor Press and Media Information</h2>
9 
+<div class="underline"></div>
10 
+
11 
+<!-- BEGIN SIDEBAR -->
12 
+<div class="sidebar">
13 
+<h3>Press Contact</h3>
14 
+<address>
15 
+Andrew Lewman
16 
+execdir@torproject.org
17 
++1-781-424-9877
18 
+</address>
19 
+</div>
20 
+<!-- END SIDEBAR -->
21 
+
22 
+<h3>Press Releases</h3>
23 
+<ul>
24 
+<li>25 March 2010. Tor and Printfection launch <a href="<page press/2010-03-25-tor-store-press-release>">The Tor Store</a>.</li>
25 
+<li>12 March 2009.  Tor launches a <a href="<page press/2009-03-12-performance-roadmap-press-release>">performance roadmap</a> and campaign.</li>
26 
+<li>19 December 2008.  Tor announces 3-year <a href="<page
27 
+press/2008-12-19-roadmap-press-release>">development roadmap</a>.</li>
28 
+</ul>
29 
+<br />
30 
+<div class="nb">
31 
+<h3>Quick links to better understand Tor</h3>
32 
+<ol>
33 
+<li>How is Tor <a href="<page docs/faq>#Torisdifferent">different than other proxy solutions</a>?</li>
34 
+<li><a href="/press/presskit/2009-General-Online-Anonymity-with-Tor.pdf">Why Online Privacy and Anonymity</a>?</li>
35 
+<li><a href="/press/presskit/2009-General-Background-on-Tor-Project-Inc.pdf">Who is the Tor Project, Inc.</a>?</li>
36 
+<li><a href="https://blog.torproject.org/blog/circumvention-and-anonymity">Why anonymity matters for circumvention</a>.</li>
37 
+</ol>
38 
+</div>
39 
+</div><!-- #main -->
40 
+
41 
+#include <foot.wmi>
42 
+
press/en/info.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,17 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 2-medium
4 
+#!/usr/bin/env wml
5 
+<div class="img-shadow">
6 
+  <div class="infoblock">
7 
+  	<h2 class="media">Press Contact</h2>
8 
+    <p>
9 
+    <b>Andrew Lewman</b><br>
10 
+    Executive Director<br>
11 
+    execdir@torproject.org<br>
12 
+    +1-781-424-9877<br>
13 
+    </p>
14 
+   </div>
15 
+   <!-- END INFOBLOCK -->
16 
+</div>
17 
+<!-- END IMG-SHADOW -->
press/en/inthemedia.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,25 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22070 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor in the Media"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page press/press>">Press &raquo; </a>
10 
+    <a href="<page press/inthemedia>">Tor in the Media</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h1>Tor in the Media</h1>
16 
+  </div>
17 
+  <!-- END MAINCOL -->
18 
+  <div id = "sidecol">
19 
+#include "side.wmi"
20 
+#include "info.wmi"
21 
+  </div>
22 
+  <!-- END SIDECOL -->
23 
+</div>
24 
+<!-- END CONTENT -->
25 
+#include <foot.wmi>
press/en/press.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,47 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22070 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Press Page"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page press/press>">Press</a>
10 
+  </div>
11 
+  <div id="maincol">
12 
+    <!-- PUT CONTENT AFTER THIS TAG -->
13 
+    <h1>Latest Announcements</h1>
14 
+    <table class="topforty">
15 
+      <tr>
16 
+        <td class="beige">
17 
+          <div class="name">Title of Press Release</div>
18 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.</p>
19 
+          <div class="right"><a href="<page projects/tordnsel>">Read more &raquo;</a></div>
20 
+        </td>
21 
+      </tr>
22 
+      <tr>
23 
+        <td>
24 
+          <div class="name">Title of Press Release</div>
25 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.</p>
26 
+          <div class="right"><a href="<page projects/tordnsel>">Read more &raquo;</a></div>
27 
+        </td>
28 
+      </tr>
29 
+      <tr>
30 
+        <td class="beige">
31 
+          <div class="name">Title of Press Release</div>
32 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis.</p>
33 
+          <div class="right"><a href="<page projects/tordnsel>">Read more &raquo;</a></div>
34 
+        </td>
35 
+      </tr>
36 
+    </table>
37 
+    <h2><div class="left"><a href="<page projects/tordnsel>">&laquo; Archive</a></div></h2>
38 
+  </div>
39 
+  <!-- END MAINCOL -->
40 
+  <div id = "sidecol">
41 
+#include "side.wmi"
42 
+#include "info.wmi"
43 
+  </div>
44 
+  <!-- END SIDECOL -->
45 
+</div>
46 
+<!-- END CONTENT -->
47 
+#include <foot.wmi>
press/en/pressreleases.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,55 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22070 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Press Releases"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page press/press>">Press &raquo; </a>
10 
+    <a href="<page press/pressreleases>">Press Releases</a>
11 
+  </div>
12 
+  <div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h1>Press Releases</h1>
16 
+    <table class="topforty">
17 
+    <tr>
18 
+    <td class="beige">
19 
+    <div class="name">Tor and Printfection launch</div>
20 
+    <p>
21 
+    WALPOLE, MA The Tor Project and Printfection launch The Tor Store for all your Tor fan needs. The Tor Store offers a range of t-shirts for men and women, mugs, and sweatshirts emblazed with everyones favorite techno-onion logo.
22 
+    </p>
23 
+    <div class="right"><a href="<page press/2010-03-25-tor-store-press-release>">Read more &raquo;</a></div>
24 
+    </td>
25 
+    </tr>
26 
+    <tr>
27 
+    <td>
28 
+    <div class="name">Tor launches a performance roadmap and campaign</div>
29 
+    <p>
30 
+    DEDHAM, MA -The Tor Project has launched a roadmap for dramatically improving the performance of the public Tor network over the next year. A combination of existing funding and a needed $1 million over the next 12 months will ensure success
31 
+    </p>
32 
+    <div class="right"><a href="<page press/2009-03-12-performance-roadmap-press-release>">Read more &raquo;</a></div>
33 
+    </td>
34 
+    </tr>
35 
+    <tr>
36 
+    <td class="beige">
37 
+    <div class="name">Tor announces 3-year development roadmap</div>
38 
+    <p>
39 
+    DEDHAM, MA - The Tor Project has published its three year development roadmap, focused on providing anti-censorship tools and services for the advancement of Internet freedom in closed societies.
40 
+    </p>
41 
+    <div class="right"><a href="<page press/2008-12-19-roadmap-press-release>">Read more &raquo;</a></div>
42 
+    </td>
43 
+    </tr>
44 
+    </table>
45 
+    <h2><div class="left"><a href="<page press/pressreleases>">&laquo; Archive</a></div></h2>
46 
+  </div>
47 
+  <!-- END MAINCOL -->
48 
+  <div id = "sidecol">
49 
+#include "side.wmi"
50 
+#include "info.wmi"
51 
+  </div>
52 
+  <!-- END SIDECOL -->
53 
+</div>
54 
+<!-- END CONTENT -->
55 
+#include <foot.wmi>
press/en/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,35 @@
1 
+#!/usr/bin/wml
2 
+
3 
+## translation metadata
4 
+# Revision: $Revision: 0 $
5 
+# Translation-Priority: 2-medium
6 
+
7 
+# this structure defines the side nav bar for the /about pages
8 
+# and is the input for include/side.wmi
9 
+
10 
+# fields:
11 
+#
12 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
13 
+# that links will point to the current language if supported, and alternately
14 
+# the english version
15 
+#
16 
+# txt - the link text to be displayed. Different translations will
17 
+# need to supply alternate txt
18 
+
19 
+<:
20 
+  my $sidenav;
21 
+  $sidenav = [
22 
+      {'url'  => 'press/press',
23 
+       'txt'  => 'Announcements',
24 
+      },
25 
+      {'url'  => 'press/pressreleases',
26 
+       'txt'  => 'Press Releases',
27 
+      },
28 
+      {'url'  => 'press/inthemedia',
29 
+       'txt'  => 'Tor in the Media',
30 
+      },
31 
+      {'url'  => 'https://blog.torproject.org',
32 
+       'txt'  => 'Tor Blog',
33 
+      },
34 
+  ];
35 
+:>
press/fr/2008-12-19-roadmap-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,90 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22077 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="THE TOR PROJECT ANNOUNCES THREE-YEAR DEVELOPMENT ROADMAP" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>POUR PUBLICATION IMMEDIATE</h2>
17 
+
18 
+<h2><strong>LE PROJET TOR ANNONCE SA FEUILLE DE ROUTE POUR LES TROIS ANNEES A
19 
+VENIR</strong></h2>
20 
+
21 
+<p><strong>DEDHAM, MA</strong> - Le Projet Tor a publié sa <a
22 
+href="/press/presskit/2008-12-19-roadmap-full.pdf">feuille de route de
23 
+développement pour les 3 années à venir</a>, focalisée sur la livraison
24 
+d'outils et de services contre la censure, pour la progression de la liberté
25 
+sur Internet dans les sociétés cloisonnées.</p>
26 
+
27 
+<p>Tor's tools and technologies are already used by hundreds of thousands of
28 
+people to protect their activities online.  These users include journalists
29 
+and human rights workers in politically rigid countries communicating with
30 
+whistleblowers and dissidents.  Law enforcement officers on Internet sting
31 
+operations stay anonymous with Tor, as do people wanting to post socially
32 
+sensitive information in chat rooms, like rape or abuse survivors and those
33 
+with illnesses.  The Tor network also provides protection for people
34 
+looking for another layer of privacy from the millions of websites and ISPs
35 
+bent on collecting private information and tracking their moves online.</p>
36 
+
37 
+<p>While Tor's original goal was to provide this important anonymity, many
38 
+people around the world use Tor to get around Internet censorship, as
39 
+well.  <a href="http://www.hrw.org/">Human Rights Watch</a> and <a
40 
+href="http://globalvoicesonline.org/">Global Voices Online</a> have both
41 
+recommended Tor as a tool to circumvent censorship regimes in oppressive
42 
+nations. The roadmap is focused on providing anti-censorship tools and
43 
+services for the advancement of Internet freedom in closed societies.</p>
44 
+
45 
+<p>"If your Internet provider can't see what sites you're looking at, that also
46 
+means they can't prevent you from reaching sites they don't want you to
47 
+see," said Roger Dingledine, Tor Project Leader.  "This new roadmap with
48 
+support from the larger community will let us make Tor even better at
49 
+fighting censorship.  With three years of funding, we can tackle larger
50 
+problems than before, and we can focus on making sure that Tor can grow to
51 
+handle all the people who want to use it."</p>
52 
+
53 
+<p>Tor encourage la venue de nouveaux sponsors en plus <a
54 
+href="https://www.torproject.org/sponsors">des actuels</a> tels que
55 
+Broadcasting Board of Governors, la Fondation NLnet ainsi que des centaines
56 
+de donneurs individuels. Alors que les fonds déjà versés suffisent à
57 
+démarrer la feuille de route, un ajout supplémentaire de 2.1 millions de $
58 
+sur 3 ans transformera cette feuille de route en outils pratiques.</p>
59 
+
60 
+<h2>A PROPOS DU PROJET TOR</h2>
61 
+
62 
+<p>Basé à Dedham, MA, Le Projet Tor développe des logiciels libres qui rendent
63 
+possible l'anonymat en ligne pour l'utilisateur Internet de tous les
64 
+jours. Tor est né d'une collaboration avec le laboratoire de recherche
65 
+Navale US (U.S. Naval Research Lab) en 2001 et est devenu officiellement une
66 
+association à but non lucratif (US 501(c)(3)) en 2006. Le Projet Tor
67 
+fonctionne maintenant avec de nombreuses personnes, d'ONG, d'agences de
68 
+police et de société privées dans le but de les aider à protéger leur
69 
+anonymat en ligne.</p>
70 
+
71 
+<p>En plus de ses efforts dans le développement et la maintenance des logiciels
72 
+d'anonymat Tor et du réseau Tor, le Projet Tor fournit également de l'aide
73 
+dans la recherche pour comprendre comment mettre en place et mesurer
74 
+l'activité de réseaux anonymes sécurisés. Les développeurs Tor publient
75 
+plusieurs documents de recherche chaque année lors des conférences les plus
76 
+prestigieuses sur la sécurité et chaque conférence d'importance sur ce sujet
77 
+inclut un document lié à Tor.</p>
78 
+
79 
+<p>"Tor " et le "Logo oignon" sont des marques enregistrées du Projet Tor Inc.</p>
80 
+
81 
+<p>Contact: Andrew Lewman</p>
82 
+<p>Tel: +1-781-424-9877</p>
83 
+<p>Courriel: execdir@torproject.org</p>
84 
+<p><a href="https://www.torproject.org/">Sit Web du Projet Tor</a></p>
85 
+<div align=center>###</div>
86 
+
87 
+</div>
88 
+
89 
+
90 
+#include <foot.wmi>
press/fr/2009-03-12-performance-roadmap-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,97 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22077 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="TOR PROJECT LAUNCHES PERFORMANCE ROADMAP AND CAMPAIGN" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>POUR PUBLICATION IMMEDIATE</h2>
17 
+
18 
+<h2><strong>LE PROJET TOR LANCE SA CAMPAGNE ET SA FEUILLE DE ROUTE SUR LA
19 
+PERFORMANCE</strong></h2>
20 
+
21 
+<p><strong>DEDHAM, MA</strong> - Le Projet Tor vient de <a
22 
+href="/press/presskit/2009-03-11-performance.pdf">lancer sa feuille de
23 
+route</a> pour améliorer sensiblement les performances du réseau public Tor
24 
+tout au long de l'année à venir.  Une combinaison des fonds déjà récupérés
25 
+et une levée de 1 million de $ pour les prochains mois permettront d'assurer
26 
+la réussite.  Cette campagne est le résultat direct de la récente
27 
+publication de <a href="<page press/2008-12-19-roadmap-press-release>">la
28 
+feuille de route de développement sur 3 ans</a>.  La feuille de route
29 
+mentionne de la recherche et des actions d'un certain nombres de sources qui
30 
+définissent les étapes permettant d'améliorer les performances du réseau
31 
+public Tor.  La fonctionnalité la plus demandée par les utilisateurs du
32 
+réseau Tor est l'amélioration des performances tout en maintenant un
33 
+anonymat robuste.</p>
34 
+
35 
+<p>Etant donné que la base des utilisateurs de Tor s'accroît, le réseau Tor
36 
+souffre de problèmes de performances.  Au cours des quelques années
37 
+antérieures, les fonds de Tor (et l'effort de développement) ont mis
38 
+l'accent sur la résistance au bloquage et sur une utilisation plus facile.
39 
+Ainsi, nous avons réussi à élaborer un Pack complet pour Windows, déployé
40 
+des outils utiles dans le combat contre la censure, amélioré les outils
41 
+existants tels que Vidalia, Torbutton et Thandy, rendu plus facile la mise
42 
+en place de relais en ajoutant de meilleures règles de gestion de flux ainsi
43 
+qu'une interface graphique supportant uPnP, développé une équipe et une
44 
+infrastructure solide pour la traduction et la régionalisation et contribué
45 
+à répandre de manière positive la connaissance autour de Tor tout en évitant
46 
+la censure.  Tous ces succès ont contribué à élargir le nombre
47 
+d'utilisateurs et de fait, à stresser davantage le réseau public Tor.</p>
48 
+
49 
+<p>Tor's tools and technologies are already used by hundreds of thousands of
50 
+people to protect their activities online.  These users include journalists
51 
+and human rights workers in politically rigid countries communicating with
52 
+whistleblowers and dissidents.  Law enforcement officers on Internet sting
53 
+operations stay anonymous with Tor, as do people wanting to post socially
54 
+sensitive information in chat rooms, like rape or abuse survivors and those
55 
+with illnesses.  The Tor network also provides protection for people
56 
+looking for another layer of privacy from the millions of websites and ISPs
57 
+bent on collecting private information and tracking their moves online.</p>
58 
+
59 
+<p>Tor encourage la venue de nouveaux sponsors en plus <a href="<page
60 
+sponsors>">des actuels</a> tels que Broadcasting Board of Governors, la
61 
+Fondation NLnet ainsi que des centaines de donneurs individuels. Alors que
62 
+les fonds déjà versés suffisent à démarrer la feuille de route, un ajout
63 
+supplémentaire d'1 million de $ l'année prochaine permettra d'augmenter
64 
+sensiblement les performances du réseau public Tor.</p>
65 
+
66 
+<h2>A PROPOS DU PROJET TOR</h2>
67 
+
68 
+<p>Basé à Dedham, MA, Le Projet Tor développe des logiciels libres qui rendent
69 
+possible l'anonymat en ligne pour l'utilisateur Internet de tous les
70 
+jours. Tor est né d'une collaboration avec le laboratoire de recherche
71 
+Navale US (U.S. Naval Research Lab) en 2001 et est devenu officiellement une
72 
+association à but non lucratif (US 501(c)(3)) en 2006. Le Projet Tor
73 
+fonctionne maintenant avec de nombreuses personnes, d'ONG, d'agences de
74 
+police et de société privées dans le but de les aider à protéger leur
75 
+anonymat en ligne.</p>
76 
+
77 
+<p>En plus de ses efforts dans le développement et la maintenance des logiciels
78 
+d'anonymat Tor et du réseau Tor, le Projet Tor fournit également de l'aide
79 
+dans la recherche pour comprendre comment mettre en place et mesurer
80 
+l'activité de réseaux anonymes sécurisés. Les développeurs Tor publient
81 
+plusieurs documents de recherche chaque année lors des conférences les plus
82 
+prestigieuses sur la sécurité et chaque conférence d'importance sur ce sujet
83 
+inclut un document lié à Tor. Tor est une organisation de projet financée et
84 
+dispose d'une équipe de huit personnes à temps complet.</p>
85 
+
86 
+<p>"Tor " et le "Logo oignon" sont des marques enregistrées du Projet Tor Inc.</p>
87 
+
88 
+<p>Contact: Andrew Lewman</p>
89 
+<p>Tel: +1-781-424-9877</p>
90 
+<p>Email: execdir@torproject.org</p>
91 
+<p><a href="https://www.torproject.org/">Site Web: Projet Tor</a></p>
92 
+<div align=center>###</div>
93 
+
94 
+</div>
95 
+
96 
+
97 
+#include <foot.wmi>
press/fr/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,64 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22070 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor Press Page"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Information sur Tor pour la Presse et les Médias</h2>
17 
+<div class="underline"></div>
18 
+
19 
+
20 
+<!-- BEGIN SIDEBAR -->
21 
+<div class="sidebar">
22 
+<h3>Contact de presse</h3>
23 
+<address>
24 
+Andrew Lewman execdir@torproject.org +1-781-424-9877
25 
+</address>
26 
+</div>
27 
+
28 
+
29 
+<!-- END SIDEBAR -->
30 
+<h3>Communiqués de presse</h3>
31 
+<ul>
32 
+<li>25 mars 2010.  Tor et Printfection lancent <a href="<page
33 
+press/2010-03-25-tor-store-press-release>">la Boutique Tor</a>.</li>
34 
+<li>12 mars 2009.  Tor lance une feuille de route et une campagne pour améliorer
35 
+<a href="<page press/2009-03-12-performance-roadmap-press-release>">ses
36 
+performances</a>.</li>
37 
+<li>19 décembre 2008.  Tor annonce sa <a href="<page
38 
+press/2008-12-19-roadmap-press-release>">feuille de route pour les 3 années
39 
+à venir</a>.</li>
40 
+</ul>
41 
+<br />
42 
+<div class="nb">
43 
+<h3>Quelques liens pour mieux comprendre Tor</h3>
44 
+<ol>
45 
+<li>En quoi Tor est <a href="<page docs/faq>#Torisdifferent">différent des autres
46 
+solutions de proxy</a>?</li>
47 
+<li><a
48 
+href="/press/presskit/2009-General-Online-Anonymity-with-Tor.pdf">Pourquoi
49 
+respecter la vie privée et l'anonymat sur Internet (Why Online Privacy and
50 
+Anonymity)</a>?</li>
51 
+<li><a
52 
+href="/press/presskit/2009-General-Background-on-Tor-Project-Inc.pdf">Qu'est-ce-que
53 
+le projet Tor (Who is the Tor Project, Inc.)</a>?</li>
54 
+<li><a
55 
+href="https://blog.torproject.org/blog/circumvention-and-anonymity">Pourquoi
56 
+l'anonymat compte en matière de contournement (Why anonymity matters for
57 
+circumvention)</a>.</li>
58 
+</ol>
59 
+</div>
60 
+</div>
61 
+
62 
+
63 
+
64 
+#include <foot.wmi>
press/nl/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,59 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22070 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor Press Page"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Tor Pers en Media informatie</h2>
17 
+<div class="underline"></div>
18 
+
19 
+
20 
+<!-- BEGIN SIDEBAR -->
21 
+<div class="sidebar">
22 
+<h3>Pers contact</h3>
23 
+<address>
24 
+Andrew Lewman execdir@torproject.org +1-781-424-9877
25 
+</address>
26 
+</div>
27 
+
28 
+
29 
+<!-- END SIDEBAR -->
30 
+<h3>Persberichten</h3>
31 
+<ul>
32 
+<li>25 March 2010. Tor and Printfection launch <a href="<page
33 
+press/2010-03-25-tor-store-press-release>">The Tor Store</a>.</li>
34 
+<li>12 maart 2009. Tor lanceert een <a href="<page
35 
+press/2009-03-12-performance-roadmap-press-release>">prestatieplan</a> en
36 
+campagne.</li>
37 
+<li>19 december 2008: Tor brengt haar 3-jarige <a href="<page
38 
+press/2008-12-19-roadmap-press-release>">ontwikkelingsplan</a> uit.</li>
39 
+</ul>
40 
+<br />
41 
+<div class="nb">
42 
+<h3>Snelle links om Tor beter te begrijpen</h3>
43 
+<ol>
44 
+<li>Hoe is Tor <a href="<page docs/faq>#Torisdifferent">anders dan andere proxy
45 
+oplossingen</a>?</li>
46 
+<li><a href="/press/presskit/2009-General-Online-Anonymity-with-Tor.pdf">Waarom
47 
+Online Privacy en Anonimiteit</a>?</li>
48 
+<li><a href="/press/presskit/2009-General-Background-on-Tor-Project-Inc.pdf">Wie
49 
+is het Tor Project, Inc.</a>?</li>
50 
+<li><a
51 
+href="https://blog.torproject.org/blog/circumvention-and-anonymity">Waarom
52 
+anonimiteit belangrijk is voor omzeiling</a>.</li>
53 
+</ol>
54 
+</div>
55 
+</div>
56 
+
57 
+
58 
+
59 
+#include <foot.wmi>
press/pl/2008-12-19-roadmap-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,91 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22196 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="THE TOR PROJECT ANNOUNCES THREE-YEAR DEVELOPMENT ROADMAP" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>DO NATYCHMIASTOWEGO OGŁOSZENIA</h2>
17 
+
18 
+<h2><strong>PROJEKT TOR OGŁASZA TRZYLETNI PLAN ROZWOJOWY</strong></h2>
19 
+
20 
+<p><strong>DEDHAM, MA</strong> - Projekt Tor wydał swój <a
21 
+href="/press/presskit/2008-12-19-roadmap-full.pdf">trzyletni plan
22 
+rozwojowy</a>, skupiający się na dostarczeniu narzędzi przeciwdziałających
23 
+cenzurze i usług polepszających wolność Internetu w zamkniętych
24 
+społeczeństwach.</p>
25 
+
26 
+<p>Narzędzia i technologie Tora już są używane przez setki tysięcy ludzi, by
27 
+chronić ich działalność online. Do tych użytkowników zaliczają się
28 
+dziennikarze i działacze na rzecz praw człowieka w surowych politycznie
29 
+krajach, komunikujący się z nagłaśniaczami i dysydentami. Stróże prawa
30 
+pozostają anonimowi w czasie operacji internetowych, tak samo jak ludzie
31 
+chcący w pokojach rozmów publikować delikatne towarzysko informacje, jak
32 
+osoby, które przeżyły gwałt lub molestowanie czy ludzie z chorobami. Sieć
33 
+Tora dostarcza też ochrony ludziom szukającym kolejnej warstwy prywatności
34 
+do ochrony przed milionami stron i dostawców usług internetowych
35 
+nastawionych na zbieranie prywatnych danych i śledzenie ruchów w sieci.</p>
36 
+
37 
+<p>Podczas gdy pierwotnym celem Tora było dostarczenie tej ważnej anonimowości,
38 
+wielu ludzi na całym świecie używa Tora także po ty, by obejść cenzurę.  <a
39 
+href="http://www.hrw.org/">Human Rights Watch</a> i <a
40 
+href="http://globalvoicesonline.org/">Global Voices Online</a> zaleciły Tora
41 
+jako narzędzie do obchodzenia cenzurujących reżimów w uciskających
42 
+krajach. Plan rozwojowy skupia się na dostarczeniu narzędzi
43 
+przeciwdziałających cenzurze i usług polepszających wolność Internetu w
44 
+zamkniętych społeczeństwach.</p>
45 
+
46 
+<p>"Jeśli Twój dostawca usług internetowych nie widzi, jakie strony oglądasz,
47 
+znaczy to też, że nie może uniemożliwić Tobie dotarcia do stron, których nie
48 
+chcą, byś oglądał" powiedział Roger Dingledine, Lider Projektu Tor.  "Ten
49 
+nowy plan rozwojowy ze wsparciem od większej społeczności pozwoli nam
50 
+uczynić Tora jeszcze lepszym w walce z cenzurą. Z funduszami na trzy lata
51 
+możemy zająć się problemami większymi niż dotychczas i możemy skupić się nad
52 
+sprawianiem, by Tor mógł rosnąć tak, by mógł obsłużyć wszystkich, którzy
53 
+chcą go używać."</p>
54 
+
55 
+<p>Tor zachęca dodatkowych sponsorów do przyłączenia się do <a
56 
+href="https://www.torproject.org/sponsors">aktualnych sponsorów</a> takich
57 
+jak Broadcasting Board of Governors, Fundacja NLnet i setki indywidualnych
58 
+darczyńców. Podczas gdy istniejące fundusze są wystarczające, by zacząć
59 
+punkty z planu rozwoju, dodatkowe 2,1 miliona dolarów przez trzy kolejne
60 
+lata zmienią ten plan w użyteczne narzędzia.</p>
61 
+
62 
+<h2>O PROJEKCIE TOR</h2>
63 
+
64 
+<p>Mieszcząc się w Dedham, MA, Projekt Tor rozwija darmowe i otwarte
65 
+oprogramowanie, które daje anonimowość online zwykłym użytkownikom
66 
+Internetu. Tor narodził się ze współpracy z Laboratorium Marynarki Wojennej
67 
+USA, która zaczęła się w roku 2001, a organizacją non-profit U.S. 501(c)(3)
68 
+stał się w roku 2006. Projekt Tor pracuje teraz z wieloma osobami,
69 
+organizacjami pozarządowymi, agencjami ochrony prawa i firmami na całym
70 
+świecie, by pomagać im chronić ich anonimowość online.</p>
71 
+
72 
+<p>In addition to its efforts developing and maintaining the Tor anonymity
73 
+software and the Tor network, The Tor Project also helps to lead the
74 
+research community in understanding how to build and measure scalable and
75 
+secure anonymity networks. The Tor developers publish several new research
76 
+papers each year in major academic security conferences, and just about
77 
+every major security conference these days includes a Tor-related paper.</p>
78 
+
79 
+<p>"Logo cebulowe" i słowo-znak "Tor" są zastrzeżonymi znakami handlowymi
80 
+Projektu Tor (The Tor Project, Inc.)</p>
81 
+
82 
+<p>Kontakt: Andrew Lewman</p>
83 
+<p>Tel: +1-781-424-9877</p>
84 
+<p>Email: execdir@torproject.org</p>
85 
+<p><a href="https://www.torproject.org/">Strona WWW: Projekt Tor</a></p>
86 
+<div align=center>###</div>
87 
+
88 
+</div>
89 
+
90 
+
91 
+#include <foot.wmi>
press/pl/2009-03-12-performance-roadmap-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,93 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22077 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="TOR PROJECT LAUNCHES PERFORMANCE ROADMAP AND CAMPAIGN" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>DO NATYCHMIASTOWEGO OGŁOSZENIA</h2>
17 
+
18 
+<h2><strong>PROJEKT TOR PRZEDSTAWIA PLAN I KAMPANIĘ ROZWOJU WYDAJNOŚCI</strong></h2>
19 
+
20 
+<p><strong>DEDHAM, MA</strong> - Projekt Tor <a
21 
+href="https://svn.torproject.org/svn/tor/trunk/doc/roadmaps/2009-03-11-performance.pdf"
22 
+>wydał plan rozwojowy</a>, celem którego jest znaczna poprawa wydajności
23 
+publicznej sieci Tora w ciągu następnego roku. Połączenie istniejących
24 
+funduszy i potrzebnego 1 miliona dolarów w przeciągu następnych 12 miesięcy
25 
+zapewni sukces. Ta kampania jest bezpośrednim wynikiem niedawno ogłoszonego
26 
+<a href="<page press/2008-12-19-roadmap-press-release>">3-letniego planu
27 
+rozwojowego</a>. Plan ten łączy badania i działania pochodzące z wielu
28 
+źródeł, które określają następne kroki do polepszenia wydajności publicznej
29 
+sieci Tora. Najbardziej pożądaną przez użytkowników funkcjonalnością jest
30 
+zwiększenie wydajności z jednoczesnym zachowaniem mocnej anonimowości.</p>
31 
+
32 
+<p>W miarę wzrostu liczby użytkowników Tora, wydajność sieci Tora ucierpiała. W
33 
+przeciągu kilku ostatnich lat fundusze Tora (a więc i prace rozwojowe)
34 
+skupiły się na użyteczności i opieraniu się blokowaniu. Otrzymaliśmy
35 
+przenośną, zawierającą wszystko czego potrzeba, paczkę dla Windows;
36 
+wydaliśmy narzędzia do walki ze zbliżającym się wyścigiem z cenzurą;
37 
+bardziej rozwinęliśmy aplikacje wspierające jak Vidalia, Torbutton i Thandy;
38 
+uprościliśmy uruchamianie przekaźników poprzez dodanie lepszego ograniczania
39 
+łącza i łatwy w użyciu interfejs graficzny z obsługą uPnP; stworzyliśmy
40 
+efektywną ekipę i infrastrukturę do tłumaczeń i lokalizacji oraz
41 
+rozgłosiliśmy informacje o Torze w bezpieczny sposób, który nie został
42 
+wykryty przez cenzorów. Wszystkie te sukcesy złożyły się na wzrost liczby
43 
+użytkowników i zwiększyły nacisk na publiczną sieć Tora.</p>
44 
+
45 
+<p>Tor's tools and technologies are already used by hundreds of thousands of
46 
+people to protect their activities online.  These users include journalists
47 
+and human rights workers in politically rigid countries communicating with
48 
+whistleblowers and dissidents.  Law enforcement officers on Internet sting
49 
+operations stay anonymous with Tor, as do people wanting to post socially
50 
+sensitive information in chat rooms, like rape or abuse survivors and those
51 
+with illnesses.  The Tor network also provides protection for people
52 
+looking for another layer of privacy from the millions of websites and ISPs
53 
+bent on collecting private information and tracking their moves online.</p>
54 
+
55 
+<p>Tor zachęca dodatkowych sponsorów do przyłączenia się do <a
56 
+href="https://www.torproject.org/sponsors">aktualnych sponsorów</a> takich
57 
+jak Broadcasting Board of Governors, Fundacja NLnet i setki indywidualnych
58 
+darczyńców. Podczas gdy istniejące fundusze są wystarczające, by zacząć
59 
+punkty z planu rozwoju, dodatkowy 1 milion dolarów przez kolejny rok
60 
+znacznie poprawi wydajność publicznej sieci Tora.</p>
61 
+
62 
+<h2>O PROJEKCIE TOR</h2>
63 
+
64 
+<p>Mieszcząc się w Dedham, MA, Projekt Tor rozwija darmowe i otwarte
65 
+oprogramowanie, które daje anonimowość online zwykłym użytkownikom
66 
+Internetu. Tor narodził się ze współpracy z Laboratorium Marynarki Wojennej
67 
+USA, która zaczęła się w roku 2001, a organizacją non-profit U.S. 501(c)(3)
68 
+stał się w roku 2006. Projekt Tor pracuje teraz z wieloma osobami,
69 
+organizacjami pozarządowymi, agencjami ochrony prawa i firmami na całym
70 
+świecie, by pomagać im chronić ich anonimowość online.</p>
71 
+
72 
+<p>Oprócz prac związanych z rozwojem i utrzymaniem oprogramowania anonimowości
73 
+Tor i sieci Tora, Projekt Tor pomaga też prowadzić społeczność badawczą w
74 
+zrozumieniu, jak budować i mierzyć skalowalne i bezpieczne sieci
75 
+anonimowości. Deweloperzy Tora publikują kilka nowy dokumentów badawczych
76 
+każdego roku na większych konferencjach akademickich dotyczących
77 
+anonimowości, a prawie każda większa konferencja o bezpieczeństwie zawiera
78 
+dokument dotyczący Tora. Tor jest organizacją finansowaną z projektów z
79 
+ośmioma pełnoetatowymi członkami.</p>
80 
+
81 
+<p>"Logo cebulowe" i słowo-znak "Tor" są zastrzeżonymi znakami handlowymi
82 
+Projektu Tor (The Tor Project, Inc.)</p>
83 
+
84 
+<p>Kontakt: Andrew Lewman</p>
85 
+<p>Tel: +1-781-424-9877</p>
86 
+<p>Email: execdir@torproject.org</p>
87 
+<p><a href="https://www.torproject.org/">Strona WWW: Projekt Tor</a></p>
88 
+<div align=center>###</div>
89 
+
90 
+</div>
91 
+
92 
+
93 
+#include <foot.wmi>
press/pl/2010-03-25-tor-store-press-release.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,90 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22100 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="TOR PROJECT AND PRINTFECTION ANNOUNCE THE TOR STORE" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>DO NATYCHMIASTOWEGO OGŁOSZENIA</h2>
17 
+
18 
+<h2><strong>PROJEKT TOR I PRINTFECTION OGŁASZAJĄ SKLEP TORA</strong></h2>
19 
+
20 
+<p><strong>WALPOLE, MA</strong> The Tor Project i Printfection uruchamiają <a
21 
+href="http://printfection.com/torprojectstore">Sklep Tora</a> dla wszelkich
22 
+potrzeb fanów Tora. Sklep Tora oferuje gamę koszulek dla mężczyzn i kobiet,
23 
+kubki i bluzy ozdobione z ulubionym logo techno-cebuli. Informacje od
24 
+społeczeństwa kształtują wybór produktów. Pierwsze otwarcie sklepu zawiera
25 
+część najbardziej pożądanych przedmiotów z logo Tora.</p>
26 
+
27 
+<p> <blockquote>"Projekt Tor stawia na technologię Printfection spełnienia handlu na
28 
+żądanie, by zaangażować ludzi go wspierających i wytworzyć dodatkowy dochód,
29 
+który pomoże chronić anonimowość on-line. Jesteśmy dumni, że jesteśmy
30 
+związani z tak ważnym projektem.
31 
+</blockquote>
32 
+ -- Casey Shorr, Prezes Printfection</p>
33 
+
34 
+<p>Tor's tools and technologies are already used by millions of people to
35 
+protect their activities online.  These users include journalists and human
36 
+rights workers in politically rigid countries communicating with
37 
+whistleblowers and dissidents.  Law enforcement officers on Internet sting
38 
+operations stay anonymous with Tor, as do people wanting to post socially
39 
+sensitive information in chat rooms, like rape or abuse survivors and those
40 
+with illnesses.  The Tor network also provides protection for people
41 
+looking for another layer of privacy from the millions of websites and ISPs
42 
+bent on collecting private information and tracking their moves online.</p>
43 
+
44 
+<p>Twoje wsparcie dla Tora poprzez kupowanie przedmiotów z marką Tora i poprzez
45 
+stałe dotacje tysięcy osób przez nasze <a href="<page donate/donate>">różne sposoby
46 
+dotowania</a> są mile widziane.  </p>
47 
+
48 
+<h2>O PROJEKCIE TOR</h2>
49 
+
50 
+<p>Mieszcząc się w Walpole, MA, Projekt Tor rozwija darmowe i otwarte
51 
+oprogramowanie, które daje anonimowość online zwykłym użytkownikom
52 
+Internetu. Tor narodził się ze współpracy z Laboratorium Marynarki Wojennej
53 
+USA, która zaczęła się w roku 2001, a organizacją non-profit U.S. 501(c)(3)
54 
+stał się w roku 2006. Projekt Tor pracuje teraz z wieloma osobami,
55 
+organizacjami pozarządowymi, agencjami ochrony prawa i firmami na całym
56 
+świecie, by pomagać im chronić ich anonimowość online.</p>
57 
+
58 
+<p>Oprócz prac związanych z rozwojem i utrzymaniem oprogramowania anonimowości
59 
+Tor i sieci Tora, Projekt Tor pomaga też prowadzić społeczność badawczą w
60 
+zrozumieniu, jak budować i mierzyć skalowalne i bezpieczne sieci
61 
+anonimowości. Deweloperzy Tora publikują kilka nowy dokumentów badawczych
62 
+każdego roku na większych konferencjach akademickich dotyczących
63 
+anonimowości, a prawie każda większa konferencja o bezpieczeństwie zawiera
64 
+dokument dotyczący Tora. Tor jest organizacją finansowaną z projektów z
65 
+ośmioma pełnoetatowymi członkami.</p>
66 
+
67 
+<h2>O PRINTFECTION</h2>
68 
+
69 
+<p>Printfection jest wiodącą usługą wszystko-w-jednym spełnienia handlu na
70 
+żądanie. Dziesiątki tysięcy firm używają naszych technologii i usług, by
71 
+obsługiwać swoje programy handlowe. Ułatwiamy firmom o dowolnym rozmiarze
72 
+sprzedawanie koszulek, kubków, rzeczy do noszenia i innych towarów
73 
+promocyjnych on-line. Uruchomiony w 2004, Printfection hostuje teraz ponad
74 
+20000 sklepów z towarem on-line, wypełaniając zamówienia z trzech miejsc w
75 
+skali kraju. Firma ma siedzibę w Denver, Colorado. Dowiedz się więcej o
76 
+Printfection pod adresem www.Printfection.com.</p>
77 
+
78 
+<p>"Logo cebulowe" i słowo-znak "Tor" są zastrzeżonymi znakami handlowymi
79 
+Projektu Tor (The Tor Project, Inc.)</p>
80 
+
81 
+<p>Kontakt: Andrew Lewman</p>
82 
+<p>Tel: +1-781-424-9877</p>
83 
+<p>Email: execdir@torproject.org</p>
84 
+<p><a href="https://www.torproject.org/">Strona WWW: Projekt Tor</a></p>
85 
+<div align=center>###</div>
86 
+
87 
+</div>
88 
+
89 
+
90 
+#include <foot.wmi>
press/pl/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,58 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22070 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor Press Page"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Informacje o Torze dla prasy i mediów</h2>
17 
+<div class="underline"></div>
18 
+
19 
+
20 
+<!-- BEGIN SIDEBAR -->
21 
+<div class="sidebar">
22 
+<h3>Kontakt prasowy</h3>
23 
+<address>
24 
+Andrew Lewman execdir@torproject.org +1-781-424-9877
25 
+</address>
26 
+</div>
27 
+
28 
+
29 
+<!-- END SIDEBAR -->
30 
+<h3>Informacje prasowe</h3>
31 
+<ul>
32 
+<li>25 March 2010. Tor and Printfection launch <a href="<page
33 
+press/2010-03-25-tor-store-press-release>">The Tor Store</a>.</li>
34 
+<li>12 Marca 2009. Tor przedstawia <a href="<page
35 
+press/2009-03-12-performance-roadmap-press-release>" >plan rozwoju
36 
+wydajności</a> i kampanię.</li>
37 
+<li>19 Grudnia 2008.  Tor ogłasza 3-letni <a href="<page
38 
+press/2008-12-19-roadmap-press-release>">plan rozwojowy</a>.</li>
39 
+</ul>
40 
+<br />
41 
+<div class="nb">
42 
+<h3>Szybkie linki w celu lepszego poznania Tora</h3>
43 
+<ol>
44 
+<li>Czym Tor <a href="<page docs/faq>#Torisdifferent">różni się od innych rozwiązań
45 
+typu proxy</a>?</li>
46 
+<li><a href="/press/presskit/2009-General-Online-Anonymity-with-Tor.pdf">Po co
47 
+prywatność anonimowość on-line</a>?</li>
48 
+<li><a href="/press/presskit/2009-General-Background-on-Tor-Project-Inc.pdf">Kto
49 
+to jest Projekt Tor</a>?</li>
50 
+<li><a href="https://blog.torproject.org/blog/circumvention-and-anonymity">Czemu
51 
+anonimowość jest ważna w unikaniu</a>.</li>
52 
+</ol>
53 
+</div>
54 
+</div>
55 
+
56 
+
57 
+
58 
+#include <foot.wmi>
press/presskit/2008-12-19-roadmap-full.pdf
Zeige Datei @ 2a9aaa802
press/presskit/2009-03-11-performance.pdf
Zeige Datei @ 2a9aaa802
press/presskit/2009-General-Background-on-Tor-Project-Inc.odp
Zeige Datei @ 2a9aaa802
press/presskit/2009-General-Background-on-Tor-Project-Inc.pdf
Zeige Datei @ 2a9aaa802
press/presskit/2009-General-Online-Anonymity-with-Tor.odp
Zeige Datei @ 2a9aaa802
press/presskit/2009-General-Online-Anonymity-with-Tor.pdf
Zeige Datei @ 2a9aaa802
press/presskit/2010-FOSDEM-torproject-freespeech-onlineprivacy.pdf
Zeige Datei @ 2a9aaa802
press/zh-cn/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,56 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22070 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor Press Page"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Tor 新闻和媒体信息</h2>
17 
+<div class="underline"></div>
18 
+
19 
+
20 
+<!-- BEGIN SIDEBAR -->
21 
+<div class="sidebar">
22 
+<h3>媒体联系</h3>
23 
+<address>
24 
+Andrew Lewman execdir@torproject.org +1-781-424-9877
25 
+</address>
26 
+</div>
27 
+
28 
+
29 
+<!-- END SIDEBAR -->
30 
+<h3>新闻稿</h3>
31 
+<ul>
32 
+<li>25 March 2010. Tor and Printfection launch <a href="<page
33 
+press/2010-03-25-tor-store-press-release>">The Tor Store</a>.</li>
34 
+<li>2009 年 3 月 12 日。Tor 推出了 <a href="<page
35 
+press/2009-03-12-performance-roadmap-press-release>">高性能路线图</a> 和行动计划。</li>
36 
+<li>2008 年 12 月 19 号。Tor 公布了未来三年的 <a href="<page
37 
+press/2008-12-19-roadmap-press-release>">开发路线图</a>。</li>
38 
+</ul>
39 
+<br />
40 
+<div class="nb">
41 
+<h3>快速链接，以更好的了解 Tor</h3>
42 
+<ol>
43 
+<li>Tor 是如何 <a href="<page docs/faq>#Torisdifferent">不同于其他代理解决方案</a>？</li>
44 
+<li><a
45 
+href="/press/presskit/2009-General-Online-Anonymity-with-Tor.pdf">为什么要在线隐私和匿名</a>？</li>
46 
+<li><a href="/press/presskit/2009-General-Background-on-Tor-Project-Inc.pdf">什么是
47 
+Tor 项目、公司</a>？</li>
48 
+<li><a href="https://blog.torproject.org/blog/circumvention-and-anonymity">Why
49 
+anonymity matters for circumvention</a>.</li>
50 
+</ol>
51 
+</div>
52 
+</div>
53 
+
54 
+
55 
+
56 
+#include <foot.wmi>
projects/.deps/.stamp
Zeige Datei @ 2a9aaa802
projects/Makefile
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1 @@
1 
+include $(WMLBASE)/Makefile.common
projects/ar/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/bms/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/de/google.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,87 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21953 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="Google Project: Secure Upgrade of Tor" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Google-Projekt: Eine sichere Aktualisierung von Tor</h2>
17 
+
18 
+<hr />
19 
+
20 
+<p>
21 
+
22 
+
23 
+</p>
24 
+
25 
+<p>
26 
+Dieses Projekt wird grosszügigerweise von <a
27 
+href="http://www.google.com">Google</a> finanziert.
28 
+</p>
29 
+
30 
+<a id="Zeitplan"></a>
31 
+<h2><a class="anchor" href="#Timetable">Zeitplan</a></h2>
32 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
33 
+
34 
+
35 
+<!-- <thead>
36 
+
37 
+<tr bgcolor="#e5e5e5">
38 
+<th>Deliverable</th>
39 
+<th>Due Date</th>
40 
+</tr>
41 
+</thead> -->
42 
+<tr bgcolor="#e5e5e5">
43 
+  <td>
44 
+    <b>Etappe 1:</b> Vidalia merkt, wenn Tor aktualisiert werden müsste, findet
45 
+die passende neue Version heraus und schaut, wo es diese gibt.<br />
46 
+<small><em>Dazu schaut Vidalia in den von einer Mehrheit der Authorities
47 
+unterschriebenen Netzwerkstatus (Tor listet bereits in jedem Netzwerkstatus
48 
+auf, welche Versionen als sicher gelten)</em></small>
49 
+  </td>
50 
+  <td>
51 
+    15. November 2008
52 
+  </td>
53 
+</tr>
54 
+
55 
+<tr>
56 
+  <td>
57 
+    <b>Etappe 2:</b>Vidalia kann eine neue Version von Tor von der Tor-Webseite
58 
+beziehen und ihre Signatur prüfen.<br /> <small><em>Das Update soll entweder
59 
+via Tor oder mittels des "Directory Mirror Update Protocol" (Vorschlag 127)
60 
+für zusätzliche Anonymität erfolgen. Die Paketsignaturen müssen überprüft
61 
+werden, um die Korrektheit der Pakte sicherzustellen.</em> </small>
62 
+  </td>
63 
+  <td>
64 
+    15. November 2008
65 
+  </td>
66 
+</tr>
67 
+
68 
+<tr bgcolor="#e5e5e5">
69 
+  <td>
70 
+    <b>Etappe 3:</b> Vidalia hat ein Interface um den Nutzer über
71 
+Aktualisierungen zu informieren und ihm dabei zu helfen. <br />
72 
+<small><em>Gibt dem Nutzer ein Interface für die Updates und die Möglichkeit
73 
+auf die nächste Hauptversion von Tor zu aktualisieren. </em></small>
74 
+  </td>
75 
+  <td>
76 
+    15. November 2008
77 
+  </td>
78 
+</tr>
79 
+</table>
80 
+
81 
+<br />
82 
+
83 
+</div>
84 
+
85 
+
86 
+
87 
+#include <foot.wmi>
projects/de/hidserv.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,476 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 18524
3 
+# Last-Translator: mail (a/t) oliverknapp .de
4 
+
5 
+#include "head.wmi" TITLE="Das NLnet Projekt: Versteckte Dienste beschleunigen" CHARSET="UTF-8"
6 
+
7 
+<div class="main-column">
8 
+
9 
+<!-- PUT CONTENT AFTER THIS TAG -->
10 
+
11 
+<h2>Das NLnet Projekt: Versteckte Dienste beschleunigen</h2>
12 
+<hr />
13 
+
14 
+<p> Versteckte Dienste bei Tor erlauben dem Nutzer anonyme Informationsdienste
15 
+wie Webseiten zu erstellen, welche nur über das Tor-Netzwerk erreichbar sind
16 
+und deren Aufenthaltsort geheim bleibt. Die kritischsten Einschränkungen von
17 
+versteckten Diensten sind momentan die Zeit, die es dauert, bis ein versteckter
18 
+Dienst im Netzwerk registriert ist und die Zeit die es dauert, bis eine
19 
+Verbindung zum versteckten Dienst hergestellt ist, wenn ein Nutzer auf den
20 
+Dienst zugreifen möchte.
21 
+
22 
+Auf Grund von Designproblemen im originalen Tor Protokoll kann eine Verbindung
23 
+zu einem versteckten Dienst mehrere Minuten dauern, was dafür sorgt, dass die
24 
+meisten Nutzer den Verbindungsversuch aufgeben, bevor die Verbindung
25 
+hergestellt wurde. Versteckte Dienste für eine direkte, interaktive
26 
+Kommunikation zwischen Nutzern zu verwenden (z.B. für Instant Messenger) ist
27 
+auf Grund der hohen Latenz für den Verbindungsaufbau daher momentan nahezu
28 
+unmöglich.</p>
29 
+
30 
+<p>Das Ziel dieses Projektes ist es, versteckte Dienste zu beschleunigen, in
31 
+dem sowohl die Methode, mit der Verbindungen zwischen den Nutzern und den
32 
+versteckten Diensten hergestellt werden, als auch die Methode für die
33 
+Registrierung von versteckten Diensten im Netzwerk, verbessert werden. In einem
34 
+ersten Schritt wird eine präzise Diagnose von versteckten Diensten unter
35 
+Labor- als auch unter Realbedingungen durchgeführt, um den Hauptgrund für die
36 
+schlechte Performanz zu finden. Basierend auf diesen Diagnosen werden
37 
+Optimierungsstrategien erarbeitet und auf mögliche unerwünschte Effekte für
38 
+die Sicherheit und Anonymität des Tor-Netzwerks untersucht. Die
39 
+vielversprechensten Lösungen werden dann implementiert, um eine Verbesserung
40 
+für den Nutzer zu erreichen. In der Diagnosephase, sobald bekannt ist wo Zeit
41 
+verloren geht und was für Verbesserungen wahrscheinlich sind, werden auch
42 
+genaue Erfolgsmaßstäbe entwickelt. Das Ziel ist es, die Veränderungen am
43 
+Protokoll von versteckten Diensten innerhalb von 12 Monaten entwickelt und in
44 
+Tor integriert zu haben.</p>
45 
+
46 
+<p>
47 
+Dieses Projekt wird großzügigerweise gesponsert von:
48 
+</p>
49 
+
50 
+<p>
51 
+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html">
52 
+<img src="$(IMGROOT)/nlnet-160x60.png" alt="Der NLnet Stiftung" /></a>
53 
+</p>
54 
+
55 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
56 
+<thead>
57 
+<tr>
58 
+<th><big>Projekt</big></th>
59 
+<th><big>Fälligkeit</big></th>
60 
+</tr>
61 
+</thead>
62 
+
63 
+<tr bgcolor="#e5e5e5">
64 
+  <td>
65 
+    <b>Etappe A:</b> Analyse, Messungen und Problem eingrenzen<br />
66 
+
67 
+<small><em>Da das Protokoll von versteckten Diensten in den letzten Jahren
68 
+nicht aktiv weiterentwickelt wurde, sind bestimmte Teilaspekte des Problems
69 
+nicht ausreichend erforscht. Um die genaue Quelle für die Latenz und den
70 
+Zeitverlust zu finden, muss eine ausführliche Analyse der Hintergründe
71 
+durchgeführt werden. Etappe A wird ungefähr einen Monat benötigen. Die
72 
+Ergebnisse der Analyse werden die Designentscheidungen von Etappe B
73 
+beeinflussen.</em></small>
74 
+
75 
+  </td>
76 
+  <td>
77 
+    15. Juni 2008
78 
+  </td>
79 
+</tr>
80 
+
81 
+<tr>
82 
+  <td>
83 
+    <b>Etappe B:</b> Design und Bewertung der nötigen Veränderungen<br />
84 
+
85 
+<small><em>Die Veränderungen an den versteckten Diensten werden Kernfunktionen
86 
+des Tor Protokolls berühren und müssen daher genau auf mögliche Gefahren für
87 
+die Sicherheit und Anonymität untersucht werden. Für die Design- und
88 
+Überprüfungsphase, welche mit einer ausführlichen, externen Prüfung endet,
89 
+sind 2 Monate vorgesehen</em></small>
90 
+
91 
+  </td>
92 
+  <td>
93 
+    15. August 2008
94 
+  </td>
95 
+</tr>
96 
+
97 
+<tr bgcolor="#e5e5e5">
98 
+  <td>
99 
+    <b>Etappe C:</b> Implementation<br />
100 
+
101 
+<small><em>Nach Design, Folgeabschätzung und externer Prüfung müssen die
102 
+Veränderungen umgesetzt und in die aktuellen Torquellen eingepflegt werden.
103 
+Die eigentliche Umsetzung der Veränderungenn wird etwa 2 Monate dauern.</em>
104 
+</small>
105 
+
106 
+  </td>
107 
+  <td>
108 
+    15. Oktober 2008
109 
+  </td>
110 
+</tr>
111 
+
112 
+<tr>
113 
+  <td>
114 
+    <b>Etappe D:</b> Implementation und Evaluation der Änderungen bis zur Veröffentlichung<br />
115 
+
116 
+<small><em>Die Veränderung ist sehr kritisch für die Sicherheit und Anonymität
117 
+des Tor-Netzwerks. Sie benötigt daher intensive Tests und Fehlersuche sowohl
118 
+im Labor als auch unter realen Bedingungen. Wir planen für diese Phase 3
119 
+Monate ein, wobei der verantwortliche Entwickler 1/3 seine Zeit mit den Test
120 
+verbringt. Ein Teil der Testphase wird eine öffentliche Betaphase
121 
+beinhalten.</em></small>
122 
+
123 
+  </td>
124 
+  <td>
125 
+    15. Januar 2009
126 
+  </td>
127 
+</tr>
128 
+
129 
+<tr bgcolor="#e5e5e5">
130 
+  <td>
131 
+    <b>Etappe E:</b> Veröffentlichung<br />
132 
+
133 
+<small><em>Die eigentliche Veröffentlichung für das Tor-Server-Netzwerk wird
134 
+mit dem regulären Veröffentlichungsplan von Tor abgestimmt. Da dieser Plan von
135 
+mehreren externen Faktoren, wie zum Beispiel der Vervollständigung andere
136 
+Softwareprojekte die in die gleiche Version einfließen sollen, abhängt, kann
137 
+die Zeit zwischen Veröffentlichung und Installation auf den meisten Tor
138 
+Servern variieren. Aus Erfahrung kann ein Zeitraum von 3 bis 4 Monaten
139 
+angenommen werden.</em></small>
140 
+
141 
+  </td>
142 
+  <td>
143 
+    15. Mai 2009
144 
+  </td>
145 
+</tr>
146 
+</table>
147 
+
148 
+<br />
149 
+
150 
+<a id="Reports"></a>
151 
+<h2><a class="anchor" href="#Reports">Monatliche Statusberichte</a></h2>
152 
+
153 
+<p>Es wird insgesamt acht monatliche Statusberichte geben. Der Erste wird mit
154 
+dem Abschluss der ersten Etappe am 15. Juni 2008 erscheinen, der Letzte mit
155 
+dem Abschluss der Tests und der Implementation am 15. Januar 2009. </p>
156 
+
157 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
158 
+<thead>
159 
+<tr>
160 
+<th><big>Monat,</big></th>
161 
+<th><big>Statusbericht</big></th>
162 
+</tr>
163 
+</thead>
164 
+
165 
+<tr bgcolor="#e5e5e5">
166 
+  <td>
167 
+    <a id="Jun08"></a>
168 
+    <a class="anchor" href="#Jun08">Juni 08</a>
169 
+  </td>
170 
+  <td>
171 
+
172 
+<small><em>Das ursprüngliche Ziel, das Problem, welches die versteckten
173 
+Dienste verlangsamt, zu finden, wurde erreicht. Ein Teil dieser Analyse war es,
174 
+ die Verzögerung zu messen, die ein Nutzer erlebt, wenn er auf einen
175 
+versteckten Dienst zugreifen möchte. Messdaten aus dem April 08 konnten dafür
176 
+genutzt werden, zu erforschen welche internen Schritte wie lange dauern, wenn
177 
+ein Nutzer sich zu einem versteckten Dienst verbinden möchte. Die Ergebnisse
178 
+dieser Analyse sind in einem 22-seitigen
179 
+<a href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">
180 
+Bericht (engl.)</a> enthalten, der auf der
181 
+<a href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">Entwickler
182 
+Mailingliste</a> veröffentlicht wurde.</em></small>
183 
+
184 
+<br/> <small><em>Die Analyse hat ausserdem ein paar Fehler ans Licht gebracht,
185 
+die für einen Teil der Verzögerung verantwortlich waren. Ein paar Fehler
186 
+wurden direkt nach der Analyse behoben, andere werden bald behoben sein. Die
187 
+Untersuchung hat ausserdem mehrere mögliche Performanzverbesserungsansätze
188 
+gebracht. Mehrere der Ansätze können direkt umgesetzt werden, andere benötigen
189 
+intensivere Untersuchungen und neue Messungen. Im Zuge der Analyse fanden wir
190 
+auch heraus, dass einigen der Ansätze tiefgreifende Änderungen an Tor
191 
+benötigen, die nicht direkt mit versteckten Diensten zusammenhängen. Diese
192 
+Veränderungen können innerhalb der Zeitplanungen dieses Projektes nicht
193 
+umgesetzt werden.</em></small>
194 
+
195 
+  </td>
196 
+</tr>
197 
+
198 
+<tr>
199 
+  <td>
200 
+    <a id="Jul08"></a>
201 
+    <a class="anchor" href="#Jul08">Juli 08</a>
202 
+  </td>
203 
+  <td>
204 
+
205 
+<small><em>Alle in der Analyse gefundenen Fehler wurden behoben. Dies
206 
+beinhaltet 2 Fehler die schon während der Analyse behoben wurden sowie 4
207 
+weitere Fehler, die in den letzten 30 Tagen entfernt wurden. Während die
208 
+Fehlerbehebungen nur ungewollte Performanzprobleme auf Grund von
209 
+Programmierfehlern behoben haben, werden einige der in der Analyse entdeckten
210 
+Designveränderungen einen Einfluss auf Anonymität oder die generelle
211 
+Netzwerklast im Tor-Netzwerk haben. Diese Einflüsse müssen gegen die
212 
+individuellen Performanzsteigerungen evaluiert werden. Ein <a
213 
+href="http://freehaven.net/~karsten/hidserv/discussion-2008-07-15.pdf">
214 
+Bericht</a> mit 7 möglichen Designveränderungen die diskutiert werden müssen,
215 
+wurde auf der <a href="http://archives.seul.org/or/dev/Jul-2008/msg00034.html">
216 
+Entwicklermailingliste</a> veröffentlicht. Bei mehreren Überprüfungen (genauer
217 
+die Messungen bei niedrigen Bandbreiten und der "Grand Scaling Plan") hat sich
218 
+herausgestellt, dass sie mehr Zeit als erwartet benötigen und sie wurden daher
219 
+für eine spätere Etappe eingeplant. Der aktuelle Plan ist, diese Überprüfungen
220 
+innerhalb eines Zeitraums bis zum 15. Januar 2009 zu erledigen und bis dahin
221 
+mit Abschätzungen zu arbeiten.</em></small>
222 
+
223 
+  </td>
224 
+</tr>
225 
+
226 
+<tr bgcolor="#e5e5e5">
227 
+  <td>
228 
+    <a id="Aug08"></a>
229 
+    <a class="anchor" href="#Aug08">Aug. 08</a>
230 
+  </td>
231 
+  <td>
232 
+
233 
+<small><em>Während der letzen 30 Tage wurden 7 der vorgeschlagenen Designs
234 
+weiter untersucht und diskutiert. Vier davon wurden im Hinblick auf die zu
235 
+erwartenden Codeänderungen und Auswirkungen auf die Anonymität als machbar
236 
+eingeschätzt. Eines wurde eher als Fehler als als Designveränderung gesehen.
237 
+Zwei wurden auf Grund von unvorhersehbaren Sicherheitsauswirkungen oder
238 
+unklarer Performanzgewinne ausgeschlossen.</em></small>
239 
+
240 
+<br/> <small><em>Zusammen mit den Ergebnissen vom 15. Juli wurde die
241 
+Designphase beendet. Die Aufgaben für die kommende Umsetzung sind jetz klar:
242 
+Ein Fehler muss behoben und 4 Designveränderungen müssen implementiert werden.
243 
+Ausserdem müssen Untersuchungen des veränderten Designs zeigen, ob diese
244 
+sinnvoll sind. Ein <a
245 
+href="http://freehaven.net/~karsten/hidserv/design-2008-08-15.pdf">Bericht</a>
246 
+mit den Ergebnissen der Designphase wurde auf der <a
247 
+href="http://archives.seul.org/or/dev/Aug-2008/msg00025.html">Entwickler
248 
+Mailingliste</a> veröffentlicht.</em></small> </td> </tr>
249 
+
250 
+<tr>
251 
+  <td>
252 
+    <a id="Sep08"></a>
253 
+    <a class="anchor" href="#Sep08">Sep. 08</a>
254 
+  </td>
255 
+  <td>
256 
+
257 
+<small><em>Während der ersten Hälfte der Umsetzungsphase konnten 2 Fehler
258 
+behoben werden, die mit versteckten Diessnten zusammenhingen: der <a
259 
+href="http://bugs.noreply.org/flyspray/index.php?do=details&amp;id=767">erste
260 
+Fehler</a> wurde bereits in der Designphase entdeckt und war für eine
261 
+außergewöhnliche Fehlerrate beim Verfügbarmachen von versteckten Diensten
262 
+verantwortlich; der <a
263 
+href="http://bugs.noreply.org/flyspray/index.php?id=814&amp;do=details">zweite
264 
+Fehler</a> wurde in der Umsetzungsphase gefunden und war dafür verantwortlich,
265 
+dass Verbindungen zu aktiven, versteckten Diensten fehlschlagen konnten. Beide
266 
+Fehlerbehebungen werden in der nächsten unstable Version enthalten sein und
267 
+werden wahrscheinlich auch in eine der nächsten stable Veröffentlichungen
268 
+zurückportiert werden.</em></small> <br/>
269 
+
270 
+<small><em>Die vier Designveränderungen die in der Designphase überlegt wurden,
271 
+ wurden in einen <a
272 
+href="https://tor-svn.freehaven.net/svn/tor/branches/hidserv-design-changes/">
273 
+experimentellen Zweig</a> des unstable Entwicklungspfads eingebaut.Erste
274 
+Funktionstests zeigen, dass diese Veränderungen funktionieren und bessere
275 
+(gefühlte) Performanz bieten. Dies muss über die nächsten 4 Wochen in internen
276 
+Tests überprüft werden. Das nächste Ziel ist es eine Version dieses
277 
+experimentellen Zweigs für Betatester zu Beginn der folgenden Testphase zu
278 
+veröffentlichen.</em></small> </td> </tr>
279 
+
280 
+<tr bgcolor="#e5e5e5">
281 
+  <td>
282 
+    <a id="Oct08"></a>
283 
+    <a class="anchor" href="#Oct08">Okt. 08</a>
284 
+  </td>
285 
+  <td>
286 
+
287 
+<small><em>Die Umsetzungsphase wurde beendet. Die Fehler die in den letzten 30
288 
+Tagen gefunden wurden, sind in der Entwicklerversion <a
289 
+href="http://archives.seul.org/or/talk/Oct-2008/msg00093.html">
290 
+0.2.1.6-alpha</a> veröffentlicht worden. Die vier Designänderungen die
291 
+identifiziert werden konnten, wurden in <a
292 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/155-four-hidden-service-improvements.txt">
293 
+Vorschlag 155</a> spezifiziert. Drei Desiggnveränderungen wurden bereits in
294 
+die Entwicklungscodebasis übernommen und werden in der nächsten
295 
+Entwicklerversion automatisch enthalten sein. Die ersten beiden
296 
+Designveränderungen verbessern die Verbindungsherstellung zu versteckten
297 
+Diensten, in dem sie den die maximale Wartezeit von 60 auf 30 Sekunden
298 
+reduzieren und parallel einen zweiten Verbindungsversuch nach 15 Sekunden
299 
+starten. Die dritte Designveränderung beeinflusst die Veröffentlichung eines
300 
+versteckten Dienstes im Netzwerk, in dem er gleichzeitig an 5 anstelle von 3
301 
+Stellen bekanntgemacht wird und sobald 3 Stellen etabliert sind, aufhört. Die
302 
+vierte Veränderung hat sich als eher ineffektiv herausgestellt, würde
303 
+allerdings erhebliche Codekomplexität hinzufügen und wurde daher abgelehnt.
304 
+Aktuell gibt es keine weiteren Fehlerbehebungen und Designveränderungen die
305 
+noch umgesetzt werden können. Alle Veränderungen sind in der
306 
+Entwicklungsquellcodebasis und können in der nächsten Etappe getestet
307 
+werden.</em></small> </td> </tr>
308 
+
309 
+<tr>
310 
+  <td>
311 
+    <a id="Nov08"></a>
312 
+    <a class="anchor" href="#Nov08">Nov. 08</a>
313 
+  </td>
314 
+  <td>
315 
+
316 
+<small><em>Die Geschwindigkeitsverbesserungen wurden in der Tor-Version
317 
+0.2.1.7-alpha veröffentlicht. Benutzer können diese Entwicklungsversion direkt
318 
+von der Tor Homepage runterladen und die Verbesserungen mit minimalem Aufwand
319 
+testen. Ausserdem wurden 2 Fehler (<a
320 
+href="http://bugs.noreply.org/flyspray/index.php?id=767&amp;do=details">1</a>,
321 
+<a href="http://bugs.noreply.org/flyspray/index.php?id=814&amp;do=details">
322 
+2</a>) die während diesem Projekt gefunden wurden, in den stabilen Zweig
323 
+übernommen und werden in der nächsten stable Version 0.2.0.32 enthalten
324 
+sein.</em></small>
325 
+
326 
+<br/> <small><em>Die Hauptaufgabe der letzten 31 Tage war es, neue Messungen
327 
+durchzuführen, ob die Verbesserungen effektiv sind oder nicht. Die Messungen
328 
+wurden zwei Tage lang voom 6. bis zum 7. November durchgeführt. Dummerweise
329 
+hatte das Tor-Netzwerk in dieser Zeit ein massives Problem: Ein abgelaufenes
330 
+Zertifikat einer Verzeichnissauthorität hat hohe Last im Tor-Netz erzeugt, was
331 
+<a href="http://archives.seul.org/or/talk/Nov-2008/msg00053.html">viele
332 
+Serbverbetreiber gezwungen hat, ihre Server abzuschalten</a>. Eine zweite
333 
+Messung wurde zwischen dem 13. und 15. November durchgeführt. Die Rohdaten
334 
+sind <a
335 
+href="http://freehaven.net/~karsten/hidserv/perfdata-2008-11-13.tar.gz">hier
336 
+zu bekommen</a> (40 MB). Leider zeigen die Ergebnisse, dass die
337 
+Gesamtperformanz des Tor-Netzwerks immer noch schlechter ist als im Juni 2008,
338 
+als die erste Messung bezüglich versteckter Dienste durchgeführt wurde. Die
339 
+zeigt sich vor allem bei Anfragen an Verzeichnissserver, die noch nicht von
340 
+den Verbesserungen profitieren und die eine deutlich schlechtere Performanz
341 
+als damals zeigen. Die Effekte der Verbesserungen sind sichtbar, aber absolute
342 
+Zahlen sind noch nicht vergleichbar. Neue Messungen werden im Dezember
343 
+durchgeführt, mit der Hoffnung, dass die Auswirkungen dieses Problems bis
344 
+dahin verschwunden sind.</em></small> <br/>
345 
+
346 
+<small><em>Zusätzlich wurde noch ein möglicher <a
347 
+href="http://bugs.noreply.org/flyspray/index.php?id=847&amp;do=details">
348 
+Fehler</a> in der Art, wie Tor Verzeichnissinformationen beim Starten bezieht,
349 
+gefunden. Auch wenn dieser Fehler nicht direkt mit versteckten Diensten
350 
+zusammenhängt, würde die Veröffentlichung von versteckten Diensten von einer
351 
+Fehlerbehebung profitieren. Ein Teil der Aufgaben der nächsten 30 Tagen wir es
352 
+sein diesen Fehler zu untersuchen. </em></small> </td> </tr>
353 
+
354 
+<tr bgcolor="#e5e5e5">
355 
+  <td>
356 
+    <a id="Dec08"></a>
357 
+    <a class="anchor" href="#Dec08">Dez. 08</a>
358 
+  </td>
359 
+  <td>
360 
+
361 
+<small><em>Ein Teil der letzten 30 Tagen wurde dafür genutzt, Fehler zu
362 
+beheben, die die Messungen negativ beeinflusst haben. Die erste <a
363 
+href="http://archives.seul.org/or/cvs/Nov-2008/msg00100.html">
364 
+Fehlerbehebung</a> behebt einen möglichen Speicherzugriffsfehler, der
365 
+wahrscheinlich für eine Menge an fehlgeschlagenen Messreihen verantwortlich
366 
+war. Ein anderer <a
367 
+href="https://bugs.torproject.org/flyspray/index.php?id=847&amp;do=details">
368 
+Fehler</a> konnte erklärt werden, der zu massiven Verzögerungen beim Verbinden
369 
+mit dem Tor-Netzwerk führte: Sehr langsame Verzeichnissauthoritäten haben
370 
+startende Nutzer für lange Zeit beschäftigt, bis der Nutzer endlich aufgegeben
371 
+hat und seine Daten von einer anderen Authorität bezogen hat. Ein Ergebniss
372 
+war, dass die langsamsten 2 Verzeichnissauthoritäten ihren Rechnern mehr
373 
+Bandbreite spendiert haben, so dass der Effekt abgemindert wurde. Ein dritter
374 
+<a href="https://bugs.torproject.org/flyspray/index.php?id=874&amp;do=details">
375 
+Fehler</a> wurde mit den Performanzverbesserungen für versteckte Dienste im
376 
+November eingeführt. Der Effekt war, dass Torprozesse, die versteckte Dienste
377 
+angeboten haben, diese nicht mehr veröffentlichten, nachdem sie ihre
378 
+Konfiguration neuluden. Ausserdem zeigte dieser Fehler, dass Tor seine
379 
+Introduction Points neu aufbaute, wenn es neugeladen wurde. Dies könnte die
380 
+Stabilität von versteckten Diensten beeinflusst haben. Der Fehler wurde
381 
+behoben und wird in der folgenden Version 0.2.1.9-alpha enthalten sein.</em>
382 
+</small> <br/>
383 
+
384 
+<small><em>Neben der Fehlerbehebung wurden neue Messungen zwischen dem 8. und
385 
+10. Dezember durchgeführt. Dies werden wahrscheinlich die letzen Messungen
386 
+sein, um die Performanz von versteckten Diensten jetzt mit dem Anfang des
387 
+Projektes zu vergleichen. Die Daten wurden noch nicht komplett ausgewertet,
388 
+daher ist es aktuell schwer eine Aussage über Verbesserungen zu machen. jedoch
389 
+zeigt eine <a
390 
+href="http://freehaven.net/~karsten/hidserv/prelimreport-2008-12-15.pdf">
391 
+vorläufige Auswertung</a>, dass die Veröffentlichungszeit eines versteckten
392 
+Dienstes deutlich verbessert wurde. Dieser Erfolg kommt von der deutlich
393 
+verbesserten Startzeit für Tornutzer und den Verbesserungen die im November
394 
+eingebaut wurden. Im Gegensatz dazu sind die Ergebnisse der
395 
+Verbindungsherstellung zu versteckten Diensten deutlich schlechter. Obwohl die
396 
+Verbesserungen aus dem November einen positiven Effekt zu haben scheinen,
397 
+zeigen einige interne Schritte eine deutlich schlechtere Performanz als
398 
+vorher. Ein Beispiel dafür ist das Beziehen von Beschreibungsdateien
399 
+versteckter Dienste um eine Verbindung mit diesen herstellen zu können. Eine
400 
+mögliche Erklärung dafür ist dass der plötzliche Anstieg an Verzeichnissen für
401 
+versteckte Dienste einen negativen Einfluss auf die Leistungsfähigkeit hatte.
402 
+Ein Teil der Arbeit der letzten 31 Tage wird es sein, diese Daten genauer
403 
+auszuwerten und finale Schlüsse über die erreichten Ziele dieses Projektes zu
404 
+ziehen.</em></small> </td> </tr>
405 
+
406 
+<tr>
407 
+  <td>
408 
+    <a id="Jan09"></a>
409 
+    <a class="anchor" href="#Jan09">Jan. 09</a>
410 
+  </td>
411 
+  <td>
412 
+
413 
+<small><em>Die Testphase ist zu Ende. Die Tests wurden in einer öffentlichen
414 
+Betaphase mit den gesamten Änderungen im 0.2.1.x-alpha Zweig von Tor
415 
+durchgeführt. Ein Ergebniss der öffentlichen Betaphase sind ein paar gefundene
416 
+Fehler, die bereits behoben werden konnten.</em></small> <br/>
417 
+
418 
+<small><em>Ein weiterer Teil des Testens war eine zweite Messreihe, die im
419 
+Dezember durchgeführt wurde. Ein <a
420 
+href="http://freehaven.net/~karsten/hidserv/comparison-2009-01-15.pdf">
421 
+Vergleich</a> der durchgeführten Messungen im Juni und im Dezember hat uns
422 
+gezeigt, dass die Veränderungen dieses Projektes effektiv sind. Die
423 
+Veröffentlichungszeit für versteckte Dienste konnte von im Mittel 2:12 Minuten
424 
+auf 58 Sekunden mehr als halbiert werden. Diese Verbesserung ist deutlich
425 
+besser als erwartet. Mit dieser Verbesserung könnte es sogar interessant sein,
426 
+über eine Reduzierung der Stabilisierungszeit von 30 Sekunden auf einen
427 
+niedrigeren Wert nachzudenken. Leider ist die Zeit die es dauert, zwischen der
428 
+Anforderung eines versteckten Dienstes und der Verbindungsherstellung zu
429 
+diesem, bei etwa 56 Sekunden geblieben. Der Hauptgrund für die fehlende
430 
+Verbesserung ist der Wechsel von einer zentralen, hin zu einer dezentralen
431 
+Speicherung der Beschreibungsdateien von versteckten Diensten. Dieser negative
432 
+Effekt durch die Verteilung des Verzeichnisses der versteckten Dienste wurde
433 
+nicht vorhergesehen. In Zukunft sollte daher an der Beschleunigung des
434 
+Herunterladens von Beschreibungsdateien aus dem verteilten Verzeichniss
435 
+gearbeitet werden. Zum Beispiel durch die Parallelisierung dieser
436 
+Anfragen.</em></small> <br/>
437 
+
438 
+<small><em>Dieser Report beendet die monatlichen Statusupdates. Die Verteilung
439 
+der 0.2.1.x Versionen mit den Verbesserungen für versteckte Dienste wird in
440 
+den nächsten Wochen und Monaten geschehen.</em></small>
441 
+
442 
+  </td>
443 
+</tr>
444 
+</table>
445 
+
446 
+<br />
447 
+
448 
+<!-- Do we want a people section? If so, would it make sense to write what
449 
+these people will be doing? And what exactly are these people going to
450 
+do? :)
451 
+<a id="People"></a>
452 
+<h2><a class="anchor" href="#People">Leute</a></h2>
453 
+<ul>
454 
+<li><a href="<page about/people>#Core">Karsten Loesing</a></li>
455 
+<li><a href="<page about/people>#Core">Steven Murdoch</a></li>
456 
+</ul>
457 
+-->
458 
+
459 
+<a id="Links"></a>
460 
+<h2><a class="anchor" href="#Links">Links</a></h2>
461 
+<ul>
462 
+<li>Forschungsbericht über <b>Performance Measurements and Statistics of Tor
463 
+Hidden Services</b>
464 
+(<a href="http://www.uni-bamberg.de/fileadmin/uni/fakultaeten/wiai_lehrstuehle/praktische_informatik/Dateien/Publikationen/loesing2008performance.pdf">PDF</a>)
465 
+von Karsten Loesing, Werner Sandmann, Christian Wilms und Guido Wirtz. In
466 
+den Proceedings des 2008 International Symposium on Applications and the
467 
+Internet (SAINT), Turku, Finnland, Juli 2008.</li>
468 
+
469 
+<!-- In the future, put links to proposal, preliminary results, etc. here -->
470 
+
471 
+</ul>
472 
+
473 
+</div><!-- #main -->
474 
+
475 
+#include <foot.wmi>
476 
+
projects/de/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,24 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 20047
3 
+#Last-Translator: jens§kubieziel.de, mail?oliverknapp.de
4 
+
5 
+#include "head.wmi" TITLE="Projektseite von Tor" CHARSET="UTF-8"
6 
+
7 
+<div class="main-column">
8 
+
9 
+<!-- PUT CONTENT AFTER THIS TAG -->
10 
+
11 
+<h2>Liste der Projekte von Tor</h2>
12 
+<hr/>
13 
+
14 
+<ul>
15 
+<li>NLnet <a href="<page projects/hidserv>">Beschleunigung der
16 
+  versteckten Dienste</a></li>
17 
+<li>NLnet <a href="<page projects/lowbandwidth>">Tor für Programme mit niedriger Bandbreite</a></li>
18 
+<li>Google <a href="<page projects/google>">Auto-update für Tor</a></li>
19 
+<li><a href="http://metrics.torproject.org/">Das Projekt zum Finden von Maßstäben: Ausmessen des Tor Netzwerks</a></li>
20 
+</ul>
21 
+
22 
+</div><!-- #main -->
23 
+
24 
+#include <foot.wmi>
projects/de/lowbandwidth.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,325 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 18524
3 
+# Last-Translator: mail %a_t% oliverknapp.de
4 
+
5 
+#include "head.wmi" TITLE="NLnet Projekt: Tor für Clients mit wenig Bandbreite" CHARSET="UTF-8"
6 
+
7 
+<div class="main-column">
8 
+
9 
+<!-- PUT CONTENT AFTER THIS TAG -->
10 
+
11 
+<h2>NLnet Projekt: Tor für Clients mit wenig Bandbreite</h2>
12 
+<hr />
13 
+
14 
+<p>Tor ist momentan nur von Benutzern mit einer breitbandigen
15 
+Internetverbindung nutzbar. Beim Start von Tor wird eine große Datei mit
16 
+Informationen über alle Server heruntergeladen. Diese Datei ist das sogenannte
17 
+Tor-Verzeichnis und ermöglicht dem Client Tor-Server für eine Route durch das
18 
+Netzwerk auszuwählen. Das aktuelle Tor-Protokoll benötigt dafür das gesamte
19 
+Verzeichnis. Die Datei ist allerdings viel zu groß für Nutzer mit Modem oder
20 
+mobilen Datendiensten wie GPRS, da dieser initiale Download der bei jedem
21 
+Torstart nötig ist, bei solch einer langsamen Leitung zwischen 10 und 30
22 
+Minuten dauert. Daraus folgt, dass Tor für Benutzer die mit Modem oder via
23 
+GPRS surfen, nicht benutzbar ist. Eines der Hauptziele von Tor ist es, Menschen
24 
+in Diktaturen oder repressiven Staaten einen sicheren, anonymen Internetzugang
25 
+zu bieten. Diese Menschen haben aber oft eine sehr langsame Internetverbindung,
26 
+ sei es, weil sie ein Modem nutzen müssen, oder weil die Länder nur
27 
+schmalbandig an das Internet angeschlossen sind. Wenn man diesen Menschen den
28 
+Zugang zu Tor ermöglicht, ist dies ein großer Fortschritt für die Freiheit
29 
+dieser Länder./p>
30 
+
31 
+<p>Um Tor auch für Nutzer mit schmalbandigen Verbindungen benutzbar zu machen,
32 
+benötigen wir eine neue Version des Torprotokolls, was die anfängliche
33 
+Downloadmenge reduziert. Diese neue Protokollversion soll die Art und Weise
34 
+verändern, in der ein Client die Informationen für die initiale
35 
+Verbindungsherstellung empfängt, damit der Download auch über ein 14,4 kbps
36 
+Modem innerhalb von 3 Minuten geschieht. Die Arbeit, die an diesem Vorschlag
37 
+gemacht wird, hat als Endziel, dass diese Protokollveränderung innerhalb von
38 
+12 Monaten umgesetzt ist und an die Endnutzer verteilt werden kann. Die aus
39 
+dem Projekt entstehende Software wird unter der 3-Clause BSD Lizenz
40 
+veröffentlicht, wie auch der Rest des Tor Codes. Alle Zwischenstände werden
41 
+öffentlich sein.</p>
42 
+
43 
+<p>
44 
+Dieses Projekt wird großzügigerweise gesponsert von:
45 
+</p>
46 
+
47 
+<p>
48 
+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html">
49 
+<img src="$(IMGROOT)/nlnet-160x60.png" alt="Der NLnet Stiftung" /></a>
50 
+</p>
51 
+
52 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
53 
+<thead>
54 
+<tr>
55 
+<th><big>Projekt</big></th>
56 
+<th><big>Fälligkeit</big></th>
57 
+</tr>
58 
+</thead>
59 
+
60 
+<tr bgcolor="#e5e5e5"> <td> <b>Etappe A:</b> Design und Überprüfung der
61 
+Protokollveränderung.<br /> <small><em>Diese Etappe enthält das detaillierte
62 
+Design und eine simulationsbasierte Überprüfung der notwendigen Veränderungen
63 
+und Modifikationen am aktuellen Torprotokoll. Die Veränderungen am Protokoll
64 
+sind recht tiefgehend und müssen daher genaustens auf mögliche Gefahren für
65 
+die Sicherheit und Anonymität des Tor-Netzes überprüft werden. Für diese
66 
+Etappe sind 2 Monate eingeplant, die von einem intensiven, externen
67 
+Überprüfung abgeschlossenn wird. Ein Teil von Etappe A wird es auch sein, eine
68 
+Zielsetzung für die Geschwindigkeitssteigerung in der Implementierungsphase zu
69 
+definieren. Das Designziel ist es, dass Tor-Verzeichnis welches initial
70 
+runtergeladen werden muss auf etwa 300 Kilobytes zu verkleinern, was einem
71 
+User mit einer 14,4 Kbps Leitung erlauben würde, es in etwa 3 Minuten
72 
+runterzuladen. Sollte es für die Sicherheit oder Anonymität notwendig sein,
73 
+können von diesem Ziel Abstriche gemacht werden, allerdings ist es das Ziel,
74 
+auf das wir hinarbeiten. </em></small> </td> <td> 15. Juli 2008 </td> </tr>
75 
+
76 
+<tr> <td> <b>Etappe B:</b>Umsetzung der Protokollveränderung<br /> <small><em>
77 
+Nach Design, Überprüfung und externer Kontrolle müssen die Veränderungen
78 
+umgesetzt und in die aktuelle Torcodebasis eingepflegt werden. Die eigentliche
79 
+Umsetzung der Veränderungen wird etwa 3 Monate dauern. </em> </small> </td>
80 
+<td> 15. Oktober 2008 </td> </tr>
81 
+
82 
+<tr bgcolor="#e5e5e5"> <td> <b>Etappe C:</b>Tests<br /> <small><em>Da die
83 
+Veränderung hochkritisch für die Sicherheit und Anonymität des Tornetzwerks
84 
+ist, erfordert sie umfangreiche Überprüfung und Fehlersuche unter Labor- und
85 
+Realbedingungen. Eine Dauer von 3 Monaten ist für die Tesphase vorgesehen, in
86 
+der der verantwortliche Entwickler einen Drittel seiner Zeit mit Testen
87 
+verbringt. Ein Teil der Testphase wird auch ein öffentlicher Betatest sein.
88 
+</em></small> </td> <td> 15. Januar 2009 </td> </tr>
89 
+
90 
+<tr> <td> <b>Etappe D:</b>Veröffentlichung<br /> <small><em>Die eigentliche
91 
+Veröffentlichung wird mit dem normalen Veröffentlichungsplan von Tor
92 
+abgestimmt. Da dieses Projekt von mehreren externen Faktoren, wie der
93 
+Fertigstellung anderer Softwareprojekten, die in die gleiche Version eingebaut
94 
+werden sollen, abhängt, kann die Zeit zwischen Veröffentlichung und die Zeit
95 
+bis die Veränderung von den meisten Serverbetreibern installiert wurde,
96 
+abweichen. Die Veröffentlichung wird innerhalb des normalern
97 
+Veröffentlichungsplans von Tor stattfinden. Dabei handelt es sich um eine
98 
+stetige Arbeit, die von vielen Freiwilligen und Personal das von anderen
99 
+Sponsoren bezahlt wird, durchgeführt wird. </em></small> </td> <td> 15. April
100 
+2009 </td> </tr> </table>
101 
+
102 
+<br />
103 
+
104 
+<a id="Reports"></a> < h2><a class="anchor" href="#Reports">Monatliche
105 
+Statusberichte</a></h2> <p>Es wird insgesamt 8 monatliche Statusberichte
106 
+geben. Beginnend mit der ersten Etappe am 15. Juli 2008, endend mit dem
107 
+Abschluss der Umsetzung und der Tests am 15. Januar 2009. </p>
108 
+
109 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
110 
+<thead>
111 
+<tr>
112 
+<th><big>Monat,</big></th>
113 
+<th><big>Statusbericht</big></th>
114 
+</tr>
115 
+</thead>
116 
+
117 
+<tr bgcolor="#e5e5e5">
118 
+  <td>
119 
+    <a id="Jun08"></a>
120 
+    <a class="anchor" href="#Jun08">Juni 08</a>
121 
+  </td>
122 
+
123 
+<td> <small><em>Wir haben einige anfängliche Messungen von Tor-Clients beim
124 
+Starten gemacht. Die Ergebnisse sind nicht unbedingt überraschend: Ein Client
125 
+holt sich etwa 10 KB Zertifikate, einen unterschriebenen Netzwerkstatuss mit
126 
+140 KB (jetzt nur noch 90 KB, siehe nächster Abschnitt) und etwa 1,5 MB
127 
+Serverbeschreibungen (nach der Hälfte davon beginnt er mit dem
128 
+Pfadaufbau).</em></small> <br />
129 
+
130 
+<small><em><a
131 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/138-remove-down-routers-from-consensus.txt">
132 
+Vorschlag 138</a> verkleinert den Netzwerkstatus um etwa 30-40% und wurde bereits
133 
+umgesetzt und in die Spezifikationen übernommen. Die Umsetzung ist Teil der
134 
+0.2.1.x-alpha Versionen und wird Effekt zeigen, sobald mehr als zwei Drittel
135 
+der Verzeichnisauthoritäten (also 5 von 6) auf diese Version gewechselt
136 
+haben.</em></small> <br />
137 
+
138 
+<small><em><a
139 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">
140 
+Vorschlag 140</a> hängt nicht direkt mit der anfänglich zu downloadenden Menge
141 
+zusammen, sondern versucht die folgenden Downloads für weitere
142 
+Netzwerkstatusdokumente ein paar Byte kleiner zu machen. Der Vorschlag wurde
143 
+bereits aufgeschrieben und an <a
144 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00013.html">or-dev
145 
+geschickt</a>. Es gibt ein paar Fragen, die erst von anderen Torentwicklern
146 
+beantwortet werden müssen, aber ich denke der Vorschlag könnte umgesetzt
147 
+werden.</em></small> <br />
148 
+
149 
+<small><em>Der interessante Punkt wäre aber, dass die Clients nicht mehr 1,5
150 
+MB an Serverbeschreibungen runterladen. <a
151 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">
152 
+Vorschlag 141</a> wurde an <a
153 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00017.html">or-dev
154 
+geschickt</a>. Es gibt vor allem 3 Sachen zu machen, so weit ich momentan
155 
+sehen kann: wir brauchen Lastverteilungsinformationen im Netzwerkstatus
156 
+(sollte nicht so schwer sein), wir müssen etwas einbauen, damit Tor-Clients
157 
+Serverbeschreibungen bei Bedarf von den Servern im Pfad beziehen können,
158 
+während Sie diesen aufbauen und wir müssen uns um die Wahl des Exits kümmern.
159 
+Wir entwickeln immer noch Ideen für den letzten Teil; ein paar Vorschläge
160 
+stehen bereits im Vorschlag.</em></small> </td> </tr>
161 
+
162 
+<tr>
163 
+  <td>
164 
+    <a id="Jul08"></a>
165 
+    <a class="anchor" href="#Jul08">Juli 08</a>
166 
+  </td>
167 
+
168 
+<td> <small><em>Die Arbeit an <a
169 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">
170 
+Vorschlag 141</a> geht weiter: Es gibt 2 grundlegende Ideen, wie man
171 
+Lastverteilungsinformationen in den Netzwerkstatus reinbekommt: Die eine ist,
172 
+dass die Authoritäten die Gewichte generieren, die die Clients benutzen sollen
173 
+und das in den Status reinpacken, der andere Ansatz ist, einfach nur
174 
+Bandbreiteninformationen aus den Serverbeschreibungen dort reinzutun. Der
175 
+zweite Ansatz ist wahrscheinlich besser, wenn man auch <a
176 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">
177 
+Vorschlag 140</a> mitbetrachtet, da es verhindern würde, dass sich die Nummern
178 
+im Netzwerkstatus sehr oft ändern.</em></small> <br />
179 
+
180 
+<small><em>Für den Umgang mit Exitregeln schlägt <a
181 
+href="http://archives.seul.org/or/dev/Jul-2008/msg00022.html">eine Nachricht
182 
+auf der or-dev Mailingliste</a> vor, dass ein Hash der die Exitregeln eines
183 
+Servers beschreibt zum Netzwerkstatus hinzugefügt wird. Das Einfügen von
184 
+weiteren, unvorhersehbaren 160 Bits pro Knoten in den Netzwerkstatus könnte
185 
+problematisch sein, aber da viele Exitregeln ähnlich sind, denken wir, dass
186 
+der Status gut komprimiert werden kann. Messungen müssen noch durchgeführt
187 
+werden.</em></small> </td> </tr>
188 
+
189 
+<tr bgcolor="#e5e5e5">
190 
+  <td>
191 
+    <a id="Aug08"></a>
192 
+    <a class="anchor" href="#Aug08">Aug. 08</a>
193 
+  </td>
194 
+
195 
+<td> <small><em>Die Daten der Verzeichnisautoritäten und der Algorithmus wie
196 
+daraus der Netzwerkstatus gebildet wird, wurden dahingehend geändert, dass sie
197 
+Bandbreiteninformationen und Exitregeln beinhalten, wie das in Vorschlag 141
198 
+dokumentiert ist. Sobald 5 von 6 Authoritäten auf eine Version die dies
199 
+enthält (ab Revision 16554) geupgraded haben, wird der Netzwerkstatus diese
200 
+Informationen enthalten. </em></small> </td> </tr>
201 
+
202 
+<tr>
203 
+  <td>
204 
+    <a id="Sep08"></a>
205 
+    <a class="anchor" href="#Sep08">Sept. 08</a>
206 
+  </td>
207 
+  <td>
208 
+<small><em>Leider keine neuen Informationen im September</em></small>
209 
+  </td>
210 
+</tr>
211 
+
212 
+<tr bgcolor="#e5e5e5">
213 
+  <td>
214 
+    <a id="Oct08"></a>
215 
+    <a class="anchor" href="#Oct08">Okt. 08</a>
216 
+  </td>
217 
+
218 
+<td> <small><em><p>Wir haben unseren "Fertig mit der Umsetzung" Meilenstein
219 
+diesen Monat nicht erreicht, da der Entwickler der dieses Projekt leitet, zu
220 
+viel um die Ohren hat. Die gute Nachricht ist, dass wir einen großen Teil der
221 
+Umsetzungsarbeit fertig haben und dieser Teil schon seit mehreren Monaten
222 
+(genauer seit August) in Tor ist und daher schon intensiv getestet wurde. Die
223 
+noch fehlenden Schritte sind, dass wir Clients beibringen müssen, mit Anfragen
224 
+nach Serverbeschreibungsdateien innerhalb eines Pfades umzugehen (wofür wir
225 
+wahrscheinlich einen neuen Zellentyp nutzen wollen, um einen ganzen Roundtrip
226 
+zu sparen) und dann den Clients beizubringen, das auch zu machen, wenn der
227 
+Server den sie nutzen eine Version verwendet, die aktuell genug ist. Diese
228 
+beiden Schritte sind etwas detaillierter unter <a
229 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">
230 
+Abschnitt 3.2 von Vorschlag 141</a> beschrieben.</p>
231 
+
232 
+<p>Unser neues Ziel ist es, diese beiden Teile bis Mitte November fertig zu
233 
+haben, wenn das nicht mehr wahrscheinlich ist, werden wir unseren Zeitplan
234 
+komplett überarbeiten und vielleicht unser Design überdenken.</p>
235 
+
236 
+<p>Es gibt noch viele weitere Komponenten, um die wir uns nach diesem kümmern
237 
+wollen -- eine, über die wir uns aktuelle viele Gedanken machen, ist das
238 
+Herunterladen von "Unterschieden" zum letzten Netzwerkstatus: <a
239 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">
240 
+140-consensus-diffs.txt</a>. Dies könnte zum Einen Bandbreite sparen, was
241 
+immer schön ist, wenn man das mit der Anzahl der Nutzer multipliziert, aber es
242 
+bedeutet auch, dass wir diese eingesparte Bandbreite nutzen können, diese
243 
+Unterschiede öfter als "alle 3 bis 4 Stunden" zu laden. Wenn die Nutzer öfter
244 
+als jetzt aktuelle Verzeichnisinformationen haben, können sie schnellere Pfade
245 
+bauen, da sie bessere Informationen über die Bandbreite der Server haben (was
246 
+mit dem ersten NLnet Projekt weiter oben zusammenhängt), aber die neue
247 
+Hauptidee ist, dass wir Server die nur kurz online sind besser nutzen können:
248 
+Momentan muss ein Server mindestens 3 bis 4 Stunden online sein, bis er
249 
+irgendwelche Nutzer bekommt, was eine Menge Freiwillige ausschliest, die einen
250 
+Server betrieben wollen, aber diesen nur wenige Stunden am Stück betrieben
251 
+können.</p>
252 
+
253 
+<p>Der nächste Schritt ist, dass wir die Umsetzung von Vorschlag 141 fertig
254 
+bekommen, so dass wir ihn schnell an die Nutzer zum Testen geben können. Wir
255 
+hoffen, das passiert bald!</p></em></small> </td> </tr>
256 
+
257 
+<tr>
258 
+  <td>
259 
+    <a id="Nov08"></a>
260 
+    <a class="anchor" href="#Nov08">Nov. 08</a>
261 
+  </td>
262 
+
263 
+<td> <small><em><p>Es scheint, als ob unser ursprüngliche Plan für das letzte
264 
+Entwicklungsstück sowohl a) deutlich schwerer war als wir gehofft hatten und b)
265 
+ hoffentlich viel zu viel war für das was wir eigentlich brauchen.</p>
266 
+
267 
+<p> Roger hat die Designdiskussion auf or-dev neugestartet: <a
268 
+href="http://archives.seul.org/or/dev/Nov-2008/threads.html">
269 
+http://archives.seul.org/or/dev/Nov-2008/threads.html</a>.</p>
270 
+
271 
+<p>Ich glaube wir haben jetzt einen besseren Zugang zu den Optionen und
272 
+Einschränkungen: <a
273 
+href="http://archives.seul.org/or/dev/Nov-2008/msg00007.html">
274 
+http://archives.seul.org/or/dev/Nov-2008/msg00007.html</a>.</p>
275 
+
276 
+<p>Nick wurde mit anderen Entwicklungsprojekten begraben (hoffentlich beginnt
277 
+er damit, dass monatlich zusammenzufassen) und ich will seine Meinung über das
278 
+weitere Vorgehen; Ich hoffe, wir suchen uns eine der einfacheren
279 
+Vorgehensweise aus..</p>
280 
+
281 
+<p>Wie auch immer, die wirklich einfachen Ideen können nicht so gut skaliert
282 
+werden. Aber ich denke sie sind gute Lückenfüller bis später -- und wer weiß.
283 
+was sich alles bis "später" noch geändert hat.</p></em></small> </td> </tr>
284 
+
285 
+<tr bgcolor="#e5e5e5">
286 
+<td>
287 
+<a id="Jan09">
288 
+</a>
289 
+<a class="anchor" href="#Jan09">Jan 09</a>
290 
+</td>
291 
+<td>
292 
+
293 
+<small><em><p> Ich habe eine etwas genauere Version von unserer neuen
294 
+Designidee als <a
295 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/158-microdescriptors.txt">
296 
+ Vorschlag #158</a> aufgeschrieben und die Diskussion ist bereits losgegangen:
297 
+<a href="http://archives.seul.org/or/dev/Jan-2009/msg00010.html">
298 
+http://archives.seul.org/or/dev/Jan-2009/msg00010.html</a>.</p>
299 
+
300 
+<p> Ich denke das ist endlich die Idee! (Also wenn ich alle Kommentare
301 
+eingebaut habe.) </p>
302 
+
303 
+<p>Einer der Gründe, warum dieses Projekt nicht mehr im Zeitplan ist, ist das
304 
+wir durch das <a href="<page projects/hidserv>">NLnet Projekt über die
305 
+Geschwindigkeit versteckter Dienste von Karsten</a> wissen, dass die
306 
+Pfadverlängerung das Hauptproblem ist. Dieses Projekt würde deutlich mehr
307 
+Komplexität in genau diesen Schritt bringen. Daher brauchen wir einen besseren
308 
+Plan um das eigentliche Ziel zu erreichen ohne die Leistung noch mehr
309 
+einzuschränken.</p>
310 
+
311 
+<p>Wir haben die vorgeschlagene Designänderung in den letzten Wochen nochmal
312 
+betrachtet und Ich denke wir können bald mit der Umsetzung beginnen. Da wir
313 
+bereits eine Menge von Entwicklungsprojekten Mitte Februar fertig haben wollen,
314 
+ ist es sehr wahrscheinlich, dass die Umsetzung erst Ende Februar oder im März
315 
+was wird. Diesmal aber sicher!</p></em></small>
316 
+
317 
+  <td>
318 
+  </td>
319 
+</tr>
320 
+</table>
321 
+
322 
+<br />
323 
+</div><!-- #main -->
324 
+
325 
+#include <foot.wmi>
0 326 
\ No newline at end of file
projects/de/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/en/clientside.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,107 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Client-side Projects" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/clientside>">Client-side Projects</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+  	<h1>Client-side Projects</h1>
14 
+    <p>Consectetur adipiscing elit. Proin sit amet dolor justo, lacinia dapibus est. Lorem ipsum dolor sit amet, consectetur adipiscing elit. In orci est, pellentesque sit amet consequat eget, venenatis id augue. Quisque arcu velit, ultricies non porta a, dictum in lorem. Quisque pulvinar laoreet fermentum. Quisque mauris nulla, lobortis non facilisis at, lacinia in diam. Sed at enim tortor, vitae consequat elit.</p>
15 
+    <div class="featured-project focus left first">
16 
+			<img class="project-icon" src="$(IMGROOT)/icon-default.jpg" alt="Default Icon" />
17 
+      <div class="name">Torbrowser</div>
18 
+      <div class="caps">By Author</div>
19 
+      <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
20 
+    </div>
21 
+    <div class="featured-project focus left">
22 
+			<img class="project-icon" src="$(IMGROOT)/icon-default.jpg" alt="Default Icon" />
23 
+      <div class="name">Torbutton</div>
24 
+      <div class="caps">By Author</div>
25 
+      <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/torbutton>">Learn more &raquo;</a></p>
26 
+    </div>
27 
+    <table class="topforty">
28 
+    	<tr>
29 
+        <td class="beige">
30 
+          <div class="name">Tordnsel</div>
31 
+          <div class="caps">By Author</div>
32 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/tordnsel>">Learn more &raquo;</a></p>
33 
+        </td>
34 
+        <td>
35 
+          <div class="name">Vidalia</div>
36 
+          <div class="caps">By Author</div>
37 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/vidalia>">Learn more &raquo;</a></p>
38 
+        </td>
39 
+        <td class="beige">
40 
+          <div class="name">Project Name</div>
41 
+          <div class="caps">By Author</div>
42 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
43 
+        </td>
44 
+      </tr>
45 
+      <tr>
46 
+        <td>
47 
+          <div class="name">Project Name</div>
48 
+          <div class="caps">By Author</div>
49 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
50 
+        </td>
51 
+        <td class="beige">
52 
+          <div class="name">Project Name</div>
53 
+          <div class="caps">By Author</div>
54 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
55 
+        </td>
56 
+        <td>
57 
+          <div class="name">Project Name</div>
58 
+          <div class="caps">By Author</div>
59 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
60 
+        </td>
61 
+      </tr>
62 
+      <tr>
63 
+        <td class="beige">
64 
+          <div class="name">Project Name</div>
65 
+          <div class="caps">By Author</div>
66 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
67 
+        </td>
68 
+        <td>
69 
+          <div class="name">Project Name</div>
70 
+          <div class="caps">By Author</div>
71 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
72 
+        </td>
73 
+        <td class="beige">
74 
+          <div class="name">Project Name</div>
75 
+          <div class="caps">By Author</div>
76 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
77 
+        </td>
78 
+      </tr>
79 
+      <tr>
80 
+        <td>
81 
+          <div class="name">Project Name</div>
82 
+          <div class="caps">By Author</div>
83 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
84 
+        </td>
85 
+        <td class="beige">
86 
+          <div class="name">Project Name</div>
87 
+          <div class="caps">By Author</div>
88 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
89 
+        </td>
90 
+        <td>
91 
+          <div class="name">Project Name</div>
92 
+          <div class="caps">By Author</div>
93 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
94 
+        </td>
95 
+      </tr>
96 
+    </table>
97 
+    <!-- END TABLE -->
98 
+  </div>
99 
+  <!-- END MAINCOL -->
100 
+  <div id = "sidecol">
101 
+#include "side.wmi"
102 
+#include "info.wmi"
103 
+  </div>
104 
+  <!-- END SIDECOL -->
105 
+</div>
106 
+<!-- END CONTENT -->
107 
+#include <foot.wmi>
projects/en/google.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,89 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Google Project: Secure Upgrade of Tor" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/google>">Google Project</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h2>Google Project:  Secure Upgrade of Tor</h2>
16 
+
17 
+    <hr />
18 
+
19 
+    <p>
20 
+
21 
+
22 
+    </p>
23 
+
24 
+    <p>
25 
+    This project is generously funded by <a href="http://www.google.com">Google</a>.
26 
+    </p>
27 
+
28 
+    <a id="Timetable"></a>
29 
+    <h2><a class="anchor" href="#Timetable">Timetable</a></h2>
30 
+    <table width="100%" border="0" cellspacing="0" cellpadding="3">
31 
+    <!-- <thead>
32 
+    <tr bgcolor="#e5e5e5">
33 
+    <th>Deliverable</th>
34 
+    <th>Due Date</th>
35 
+    </tr>
36 
+    </thead> -->
37 
+
38 
+    <tr bgcolor="#e5e5e5">
39 
+      <td>
40 
+        <b>Milestone 1:</b> Vidalia recognizes when Tor needs to upgrade,
41 
+    and learns the most suitable new version and where to find it.<br />
42 
+        <small><em>Looking at the majority-signed network status consensus
43 
+    to decide when to update and to what version (Tor already lists what
44 
+    versions are considered safe, in each network status
45 
+    document)</em></small>
46 
+      </td>
47 
+      <td>
48 
+        November 15, 2008
49 
+      </td>
50 
+    </tr>
51 
+
52 
+    <tr>
53 
+      <td>
54 
+        <b>Milestone 2:</b>Vidalia can fetch a new version of Tor from the
55 
+    Tor website and check its signature.<br />
56 
+        <small><em>Update either via Tor or via the directory
57 
+    mirror update protocol (proposal 127) when possible, for additional
58 
+    privacy.   Check package signatures to ensure package validity.</em></small>
59 
+      </td>
60 
+      <td>
61 
+        November 15, 2008
62 
+      </td>
63 
+    </tr>
64 
+
65 
+    <tr bgcolor="#e5e5e5">
66 
+      <td>
67 
+        <b>Milestone 3:</b> Vidalia has an interface for notifying the user
68 
+    about upgrades and helping them upgrade. <br />
69 
+        <small><em>Give the user an interface for these updates, including
70 
+    letting her opt to migrate from one major Tor version to the next.
71 
+        </em></small>
72 
+      </td>
73 
+      <td>
74 
+        November 15, 2008
75 
+      </td>
76 
+    </tr>
77 
+    </table>
78 
+
79 
+    <br />
80 
+  </div>
81 
+  <!-- END MAINCOL -->
82 
+  <div id = "sidecol">
83 
+#include "side.wmi"
84 
+#include "info.wmi"
85 
+  </div>
86 
+  <!-- END SIDECOL -->
87 
+</div>
88 
+<!-- END CONTENT -->
89 
+#include <foot.wmi>
projects/en/gui-categories.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,133 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 12809 $
3 
+
4 
+#include "head.wmi" TITLE="Tor Project: GUI Competition" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+<div id="content" class="clearfix">
6 
+	<div id="breadcrumbs">
7 
+    <a href="<page home>">Home &raquo; </a>
8 
+    <a href="<page projects/projects>">Projects &raquo; </a>
9 
+    <a href="<page projects/projects>">Gui Competition</a>
10 
+  </div>
11 
+
12 
+    <!-- LEFT HAND MENU FOR GUI CONTEST PAGES -->
13 
+    <div class="guileft">
14 
+    <div class="guimenu">
15 
+
16 
+      <div class="curveleft">
17 
+      <div class="curveright">
18 
+      &nbsp;
19 
+      </div>
20 
+      </div>
21 
+
22 
+    <div class="guimenuinner">
23 
+    <h1>Tor GUI Competition</h1>
24 
+
25 
+    <a href="index.html">Overview &amp; Goals</a>
26 
+    <a class="on" href="categories.html">What to Submit</a>
27 
+    <a href="submit.html">How to Submit</a>
28 
+    <a href="criteria.html">Judging &amp; Timeline</a>
29 
+    <a href="technotes.html">Technical Notes</a>
30 
+    <a href="legal.html">Licensing</a>
31 
+    <h1>&nbsp;</h1>
32 
+    <a class="wiki" href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ">Wiki/FAQ</a>
33 
+    </div>
34 
+
35 
+      <div class="curvebottomleft">
36 
+      <div class="curvebottomright">
37 
+      &nbsp;
38 
+      </div>
39 
+      </div>
40 
+
41 
+    </div>
42 
+    </div>
43 
+
44 
+    <h2>Categories</h2>
45 
+    <p>
46 
+    The design competition will proceed in two phases: first sketches and then
47 
+    working code. You are invited to submit to either phase, or both phases.
48 
+    For each phase, our panel of judges will recognize the
49 
+    best submissions.
50 
+    </p>
51 
+
52 
+    <p>
53 
+    All qualifying entries will receive an <a
54 
+    href="https://www.torproject.org/tshirt.html">EFF Tor T-shirt</a>
55 
+    (subject to availability). The best sketches and working implementations
56 
+    will be published on the Tor website.
57 
+    </p>
58 
+
59 
+    <p><b>Sketches:</b>
60 
+    the goal of this phase is to produce a mock-up of a functioning interface.
61 
+    This should include design documents describing how the interface should
62 
+    function. If you want, it should also include graphical elements that
63 
+    can be used by programmers.
64 
+    </p>
65 
+
66 
+    <p>
67 
+    A qualifying sketch will present an informal specification for a
68 
+    design. That is, it will present with some degree of thoroughness all
69 
+    of the major interfaces that we might expect to encounter, all of the
70 
+    major functionality for the interface, and a reasonable story about
71 
+    how it would be integrated into currently-existing tools (if, indeed,
72 
+    it would be). One example, with more detail than we would require, is
73 
+    <a href="http://ui.netbeans.org/docs/ui/junits/promo_f.html">the NetBeans
74 
+    UI for JUnit</a>. Note that it walks through multiple interfaces,
75 
+    highlighting the features and functions of the various buttons.
76 
+    </p>
77 
+
78 
+    <ul>
79 
+    <li><b>Most featureful interface</b> will be awarded to the graphic design
80 
+    that would provide usable, clear access to the most aspects of the Tor
81 
+    system, covering many or most of the categories on the "useful features"
82 
+    list.</li>
83 
+    <li><b>Most usable experience</b> will be awarded to the graphic
84 
+    design that would provide the most unobtrusive Tor experience while still
85 
+    covering all criteria (working, perhaps, on the "no news is good news"
86 
+    theory).</li>
87 
+    <li><b>Clearest implementation guidance</b> will be awarded to the
88 
+    graphic design that provides the cleanest package of graphic elements
89 
+    and design documentation to aid would-be implementers.</li>
90 
+    </ul>
91 
+
92 
+    <p><b>Code:</b> the goal of this phase is to produce a working
93 
+    implementation. You may use any of the sketches, graphics, or ideas from
94 
+    the <a
95 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestEntries">first
96 
+    phase</a> (with appropriate credit to their authors), or you can make
97 
+    your own. See the <a
98 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestSamples">Competition
99 
+    Samples</a> wiki page for some other images you can reuse.
100 
+    </p>
101 
+
102 
+    <p>
103 
+    An acceptable entry will be a package of free software that builds and
104 
+    runs. It can be a stand-alone application, or it can act as an extension
105 
+    or plugin to other broadly-available free software. The entry will
106 
+    demonstrate the points in the Goals section: that is, it will be able
107 
+    to control, display, and maintain awareness as discussed above.
108 
+    </p>
109 
+
110 
+    <ul>
111 
+    <li><b>Most featureful interface</b> will be awarded to the application
112 
+    that provides usable, clear access to the most aspects of the Tor system,
113 
+    covering many or most of the categories on the "additional" list.</li>
114 
+    <li><b>Most usable experience</b> will be awarded to the
115 
+    application that provides the most unobtrusive Tor experience while
116 
+    still covering all criteria (working, perhaps, on the "no news is good
117 
+    news" theory).</li>
118 
+    <li><b>Most flexible</b> will be awarded to the best system that runs
119 
+    smoothly on all three of Windows, Linux, and OS&nbsp;X; extra points will be
120 
+    awarded for additional systems.</li>
121 
+    </ul>
122 
+
123 
+    <p>We reserve the right to award other awards as the entries deserve.</p>
124 
+  </div>
125 
+  <!-- END MAINCOL -->
126 
+  <div id = "sidecol">
127 
+#include "side.wmi"
128 
+#include "info.wmi"
129 
+  </div>
130 
+  <!-- END SIDECOL -->
131 
+</div>
132 
+<!-- END CONTENT -->
133 
+#include <foot.wmi>
projects/en/gui-criteria.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,99 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 12809 $
3 
+
4 
+#include "head.wmi" TITLE="Tor Project: GUI Competition" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+<div id="content" class="clearfix">
6 
+	<div id="breadcrumbs">
7 
+    <a href="<page home>">Home &raquo; </a>
8 
+    <a href="<page projects/projects>">Projects &raquo; </a>
9 
+    <a href="<page projects/gui-criteria>">GUI Criteria</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+
13 
+    <!-- LEFT HAND MENU FOR GUI CONTEST PAGES -->
14 
+    <div class="guileft">
15 
+    <div class="guimenu">
16 
+
17 
+      <div class="curveleft">
18 
+      <div class="curveright">
19 
+      &nbsp;
20 
+      </div>
21 
+      </div>
22 
+
23 
+    <div class="guimenuinner">
24 
+    <h1>Tor GUI Competition</h1>
25 
+
26 
+    <a href="index.html">Overview &amp; Goals</a>
27 
+    <a href="categories.html">What to Submit</a>
28 
+    <a href="submit.html">How to Submit</a>
29 
+    <a class="on" href="criteria.html">Judging &amp; Timeline</a>
30 
+    <a href="technotes.html">Technical Notes</a>
31 
+    <a href="legal.html">Licensing</a>
32 
+    <h1>&nbsp;</h1>
33 
+    <a class="wiki" href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ">Wiki/FAQ</a>
34 
+    </div>
35 
+
36 
+      <div class="curvebottomleft">
37 
+      <div class="curvebottomright">
38 
+      &nbsp;
39 
+      </div>
40 
+      </div>
41 
+
42 
+    </div>
43 
+    </div>
44 
+
45 
+    <h2>Criteria</h2>
46 
+
47 
+    <p>Awards will be granted on the basis of (in rough preference order):</p>
48 
+
49 
+    <ul>
50 
+    <li>Usability (<a
51 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ#DefineUsable">what
52 
+    does this mean?</a>)</li>
53 
+    <li>Informativeness: can the user learn what they need to know, both in terms
54 
+    of using the network and also in terms of security decisions?</li>
55 
+    <li>Total user experience</li>
56 
+    <li>Aesthetics</li>
57 
+    <li>Responsiveness</li>
58 
+    <li>Stability and robustness</li>
59 
+    <li>Internationalization (multiple language support)</li>
60 
+    <li>Installation experience</li>
61 
+    </ul>
62 
+    <br />
63 
+    <h2>Judges</h2>
64 
+
65 
+    <p>Judging will be led by a panel of prominent specialists in usability
66 
+    and security, including:</p>
67 
+    <ul>
68 
+    <li>Patrick Ball, Director, Human Rights Program, The Benetech
69 
+    Initiative</li>
70 
+    <li>Ren Bucholz, EFF</li>
71 
+    <!--<li>Simson Garfinkel, Center for Research on Computation and Society,
72 
+    Harvard University</li>-->
73 
+    <li>Bruce Schneier, Counterpane Internet Security</li>
74 
+    <li>Adam Shostack, Informed Security</li>
75 
+    <li>Edward Tufte</li>
76 
+    <li>Ka-Ping Yee, University of California, Berkeley</li>
77 
+    </ul>
78 
+
79 
+    <h2>Timeline</h2>
80 
+
81 
+    <ul>
82 
+    <li>Phase 1 deadline (sketches): November 30, 2005.</li>
83 
+    <li>Phase 2 deadline (code): May 31, 2006.</li>
84 
+    </ul>
85 
+
86 
+    <p>Winners will be announced on the webpage and also at the SOUPS 2006
87 
+    conference. (Here's a suggestion on one approach to <a
88 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ#AcademicResearch">academic
89 
+    usability research on Tor</a>.)</p>
90 
+  </div>
91 
+  <!-- END MAINCOL -->
92 
+  <div id = "sidecol">
93 
+#include "side.wmi"
94 
+#include "info.wmi"
95 
+  </div>
96 
+  <!-- END SIDECOL -->
97 
+</div>
98 
+<!-- END CONTENT -->
99 
+#include <foot.wmi>
projects/en/gui-legal.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,80 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 12809 $
3 
+
4 
+#include "head.wmi" TITLE="Tor Project: GUI Competition" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+<div id="content" class="clearfix">
6 
+	<div id="breadcrumbs">
7 
+    <a href="<page home>">Home &raquo; </a>
8 
+    <a href="<page projects/projects>">Projects &raquo; </a>
9 
+    <a href="<page projects/gui-legal>">GUI Legal</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+
13 
+    <!-- LEFT HAND MENU FOR GUI CONTEST PAGES -->
14 
+    <div class="guileft">
15 
+    <div class="guimenu">
16 
+
17 
+      <div class="curveleft">
18 
+      <div class="curveright">
19 
+      &nbsp;
20 
+      </div>
21 
+      </div>
22 
+
23 
+    <div class="guimenuinner">
24 
+    <h1>Tor GUI Competition</h1>
25 
+
26 
+
27 
+    <a href="index.html">Overview &amp; Goals</a>
28 
+    <a href="categories.html">What to Submit</a>
29 
+    <a href="submit.html">How to Submit</a>
30 
+    <a href="criteria.html">Judging &amp; Timeline</a>
31 
+    <a href="technotes.html">Technical Notes</a>
32 
+    <a class="on" href="legal.html">Licensing</a>
33 
+    <h1>&nbsp;</h1>
34 
+    <a class="wiki" href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ">Wiki/FAQ</a>
35 
+    </div>
36 
+
37 
+      <div class="curvebottomleft">
38 
+      <div class="curvebottomright">
39 
+      &nbsp;
40 
+      </div>
41 
+      </div>
42 
+
43 
+    </div>
44 
+    </div>
45 
+
46 
+    <h2>Legal Notes</h2>
47 
+
48 
+    <p>By submitting your entry to be considered in the Tor GUI competition, you
49 
+    hereby:</p>
50 
+    <p>
51 
+    <b>(A)</b> represent and warrant that (1) the entry was created by you and
52 
+    that you own all rights to the entry or have the authorized rights to
53 
+    submit such entry and grant the licenses below; and (2) that the
54 
+    entry does not infringe on any third party copyright or other
55 
+    intellectual property rights; AND
56 
+    </p><p>
57 
+    <b>(B)</b> EITHER (1) grant us a worldwide, royalty-free, non-exclusive,
58 
+    perpetual license to reproduce, edit, perform, display, publish, make
59 
+    derivative works, and otherwise use the entry as we see fit,
60 
+    including without limitation, incorporating (in whole or in part)
61 
+    into the Tor software, and to sublicense such rights; OR, (2)
62 
+    provide the entry pursuant to a license that complies with the
63 
+    <a href="http://www.opensource.org/docs/definition.php">Open
64 
+    Source Definition</a>, such as the 3-clause BSD, MIT, or
65 
+    GPL licenses, or (where applicable) provide the entry licensed under
66 
+    the <a href="http://creativecommons.org/licenses/by/2.5/">Creative
67 
+    Commons Attribution</a> license. If you provide the entry pursuant to
68 
+    such a license, you must include the applicable information in your
69 
+    submission.
70 
+    </p>
71 
+  </div>
72 
+  <!-- END MAINCOL -->
73 
+  <div id = "sidecol">
74 
+#include "side.wmi"
75 
+#include "info.wmi"
76 
+  </div>
77 
+  <!-- END SIDECOL -->
78 
+</div>
79 
+<!-- END CONTENT -->
80 
+#include <foot.wmi>
projects/en/gui-submit.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,91 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 12809 $
3 
+
4 
+#include "head.wmi" TITLE="Tor Project: GUI Competition" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+<div id="content" class="clearfix">
6 
+	<div id="breadcrumbs">
7 
+    <a href="<page home>">Home &raquo; </a>
8 
+    <a href="<page projects/projects>">Projects &raquo; </a>
9 
+    <a href="<page projects/projects>">GUI Submit</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+
13 
+    <!-- LEFT HAND MENU FOR GUI CONTEST PAGES -->
14 
+    <div class="guileft">
15 
+    <div class="guimenu">
16 
+
17 
+      <div class="curveleft">
18 
+      <div class="curveright">
19 
+      &nbsp;
20 
+      </div>
21 
+      </div>
22 
+
23 
+    <div class="guimenuinner">
24 
+    <h1>Tor GUI Competition</h1>
25 
+
26 
+
27 
+    <a href="index.html">Overview &amp; Goals</a>
28 
+    <a href="categories.html">What to Submit</a>
29 
+    <a class="on" href="submit.html">How to Submit</a>
30 
+    <a href="criteria.html">Judging &amp; Timeline</a>
31 
+    <a href="technotes.html">Technical Notes</a>
32 
+    <a href="legal.html">Licensing</a>
33 
+    <h1>&nbsp;</h1>
34 
+    <a class="wiki" href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ">Wiki/FAQ</a>
35 
+    </div>
36 
+
37 
+      <div class="curvebottomleft">
38 
+      <div class="curvebottomright">
39 
+      &nbsp;
40 
+      </div>
41 
+      </div>
42 
+
43 
+    </div>
44 
+    </div>
45 
+
46 
+    <h2>How to Submit an Entry</h2>
47 
+
48 
+    <p>Submissions for phase one (sketches) should come as:</p>
49 
+    <ul>
50 
+    <li>Images in an html page. The images must be able to be viewed on an
51 
+    ordinary browser, e.g. Firefox. (You can submit proprietary formats too,
52 
+    but if you do then you need to also export them to something we can
53 
+    all read.) Must be licensed under a <a href="legal.html">free license</a>.</li>
54 
+    <li>A design document (txt, html, pdf, or ps) as described in the
55 
+    <a href="categories.html">Submission Categories</a> section.</li>
56 
+    </ul>
57 
+
58 
+    <p>Submissions for phase two (code) should come as:</p>
59 
+
60 
+    <ul>
61 
+    <li>Source code, with appropriate makefiles or documentation explaining
62 
+    how to build it. Must be licensed under a free/open source license, as
63 
+    defined by <a href="http://www.opensource.org/licenses/">OSI</a>. See <a
64 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ#DefineFree">this
65 
+    FAQ entry</a> for clarification.</li>
66 
+    <li>Compiled binaries or bytecodes for at least one platform of choice.</li>
67 
+    <li>A design document (txt, html, pdf, or ps) providing an overview of
68 
+    what major functions to look for and what functions are implemented.</li>
69 
+    </ul>
70 
+
71 
+    <p>To submit your entry, make a web page with
72 
+    all your materials on it, then add a line to <a
73 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestEntries">The
74 
+    GUI Competition Entries Wiki</a>. (If you don't have a web page of
75 
+    your own to put your entry on, find a friend who does, or mail <a
76 
+    href="mailto:tor-gui@freehaven.net">tor-gui@freehaven.net</a> and we'll
77 
+    put it up on a temporary page.</p>
78 
+
79 
+    <p>If you put it up on your own site, you can continue to update and
80 
+    modify it. Remember that submitting early means you can get feedback
81 
+    from Tor users and make it into a better submission!</p>
82 
+  </div>
83 
+  <!-- END MAINCOL -->
84 
+  <div id = "sidecol">
85 
+#include "side.wmi"
86 
+#include "info.wmi"
87 
+  </div>
88 
+  <!-- END SIDECOL -->
89 
+</div>
90 
+<!-- END CONTENT -->
91 
+#include <foot.wmi>
projects/en/gui-technotes.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,78 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21421 $
3 
+
4 
+#include "head.wmi" TITLE="Tor Project: GUI Competition" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+<div id="content" class="clearfix">
6 
+	<div id="breadcrumbs">
7 
+    <a href="<page home>">Home &raquo; </a>
8 
+    <a href="<page projects/projects>">Projects &raquo; </a>
9 
+    <a href="<page projects/gui-technotes>">GUI Technical Notes</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+
13 
+    <!-- LEFT HAND MENU FOR GUI CONTEST PAGES -->
14 
+    <div class="guileft">
15 
+    <div class="guimenu">
16 
+
17 
+      <div class="curveleft">
18 
+      <div class="curveright">
19 
+      &nbsp;
20 
+      </div>
21 
+      </div>
22 
+
23 
+    <div class="guimenuinner">
24 
+    <h1>Tor GUI Competition</h1>
25 
+
26 
+
27 
+    <a href="index.html">Overview &amp; Goals</a>
28 
+    <a href="categories.html">What to Submit</a>
29 
+    <a href="submit.html">How to Submit</a>
30 
+    <a href="criteria.html">Judging &amp; Timeline</a>
31 
+    <a class="on" href="technotes.html">Technical Notes</a>
32 
+    <a href="legal.html">Licensing</a>
33 
+    <h1>&nbsp;</h1>
34 
+    <a class="wiki" href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ">Wiki/FAQ</a>
35 
+    </div>
36 
+
37 
+      <div class="curvebottomleft">
38 
+      <div class="curvebottomright">
39 
+      &nbsp;
40 
+      </div>
41 
+      </div>
42 
+
43 
+    </div>
44 
+    </div>
45 
+
46 
+    <h2>Technical Notes</h2>
47 
+
48 
+
49 
+    <p>For phase two, the canonical version of Tor is going to be the
50 
+    upcoming 0.1.1.x release. This is the version that will be used for
51 
+    judging the competition; please ensure that you use this version. Bugfixes
52 
+    to this version of Tor will be announced on the
53 
+    <a href="<page download/download>">Tor download page</a>.
54 
+    Let us know if you find bugs!
55 
+    </p>
56 
+
57 
+    <p>You may find the <a href="<gitblob>doc/control-spec.txt">Tor controller
58 
+    specification</a> or the <a
59 
+    href="https://svn.torproject.org/svn/torctl/trunk/doc/howto.txt">Tor
60 
+    controller howto</a> helpful.
61 
+    </p>
62 
+
63 
+    <p>The Tor developers will also release test rigs (libraries) in both Java
64 
+    and Python that demonstrate Tor's controller protocol. Code submissions
65 
+    may be able to save a lot of time by using this code as a skeleton. You
66 
+    can check out the <a href="https://svn.torproject.org/svn/torctl/trunk/">development
67 
+    versions of these libraries</a> now. Let us know if you find bugs!
68 
+    </p>
69 
+  </div>
70 
+  <!-- END MAINCOL -->
71 
+  <div id = "sidecol">
72 
+#include "side.wmi"
73 
+#include "info.wmi"
74 
+  </div>
75 
+  <!-- END SIDECOL -->
76 
+</div>
77 
+<!-- END CONTENT -->
78 
+#include <foot.wmi>
projects/en/gui.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,181 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 12809 $
3 
+
4 
+#include "head.wmi" TITLE="Tor Project: GUI Competition" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
5 
+<div id="content" class="clearfix">
6 
+	<div id="breadcrumbs">
7 
+    <a href="<page home>">Home &raquo; </a>
8 
+    <a href="<page projects/projects>">Projects &raquo; </a>
9 
+    <a href="<page projects/gui>">GUI Competition</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+    <!-- LEFT HAND MENU FOR GUI CONTEST PAGES -->
13 
+    <div class="guileft">
14 
+    <div class="guimenu">
15 
+
16 
+      <div class="curveleft">
17 
+      <div class="curveright">
18 
+      &nbsp;
19 
+      </div>
20 
+      </div>
21 
+
22 
+    <div class="guimenuinner">
23 
+    <h1>Tor GUI Competition</h1>
24 
+
25 
+    <a class="on" href="index.html">Overview &amp; Goals</a>
26 
+    <a href="categories.html">What to Submit</a>
27 
+    <a href="submit.html">How to Submit</a>
28 
+    <a href="criteria.html">Judging &amp; Timeline</a>
29 
+    <a href="technotes.html">Technical Notes</a>
30 
+    <a href="legal.html">Licensing</a>
31 
+    <h1>&nbsp;</h1>
32 
+    <a class="wiki" href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestFAQ">Wiki/FAQ</a>
33 
+    </div>
34 
+
35 
+      <div class="curvebottomleft">
36 
+      <div class="curvebottomright">
37 
+      &nbsp;
38 
+      </div>
39 
+      </div>
40 
+
41 
+    </div>
42 
+    </div>
43 
+
44 
+    <h2>News:</h2>
45 
+
46 
+    <p>
47 
+    Jul 2006: Phase two is over, and brought us three fine interface
48 
+    projects: <a href="http://vidalia-project.net/">Vidalia</a>,
49 
+    <a href="http://freehaven.net/~squires/torbutton/">Torbutton</a>, and
50 
+    <a href="http://tork.sf.net/">TorK</a>. Thank you to each of you who
51 
+    participated. The GUI competition is now ended &mdash; but don't let that
52 
+    stop you from <a href="<page getinvolved/volunteer>">helping out</a>!
53 
+    </p>
54 
+
55 
+    <p>
56 
+    Feb 2006: The <a
57 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/ContestEntries">first
58 
+    design phase</a> is over, and we have two winners. The <a
59 
+    href="http://cups.cs.cmu.edu/pubs/TorGUIContest113005.pdf">CMU
60 
+    Usable Privacy and Security Laboratory</a> won "Best Overall,"
61 
+    and <a href="http://www.april3rd.com/tor/">the April3rd team</a> won
62 
+    "Most Aesthetically Pleasing." Feel free to use their ideas if you
63 
+    like them.</p>
64 
+
65 
+    <p>
66 
+    Dec 2005: We're excited to have just added <a href="criteria.html">Edward Tufte
67 
+    and Bruce Schneier</a> to our already impressive list of judges. And don't
68 
+    forget the free <a href="https://www.torproject.org/tshirt.html">Tor T-shirt</a>
69 
+    for every submission!
70 
+    </p>
71 
+
72 
+    <h2>Tor: GUI Competition Overview</h2>
73 
+
74 
+    <p>
75 
+    Tor is a decentralized network of computers on the Internet that increases
76 
+    privacy in Web browsing, instant messaging, and other applications. We
77 
+    estimate there are some 200,000 Tor users currently, routing their traffic
78 
+    through about 500 volunteer Tor servers on six continents. However, Tor's
79 
+    current user interface approach &mdash; running as a service in the background
80 
+    &mdash; does a poor job of communicating network status and security levels
81 
+    to the user.
82 
+    </p>
83 
+
84 
+    <p>
85 
+    The Tor project, affiliated with the
86 
+    <a href="http://www.eff.org/">Electronic Frontier Foundation</a>, is
87 
+    running a <b>GUI competition</b> to develop a vision of how Tor can
88 
+    work in a user's everyday anonymous browsing experience. Some of the
89 
+    challenges include how to make alerts and error conditions visible on
90 
+    screen; how to let the user configure Tor to use or avoid certain routes
91 
+    or nodes; how to learn about the current state of a Tor connection,
92 
+    including which servers it uses; and how to find out whether (and which)
93 
+    applications are using Tor safely.
94 
+    </p>
95 
+    <br />
96 
+
97 
+    <h2>Goals</h2>
98 
+    <p>Submitters for phase two will produce a work of <a
99 
+    href="http://www.opensource.org/">Open Source Software</a>
100 
+    that will provide a user interface to the Tor system, perhaps by way of the
101 
+    <a href="/svn/torctl/doc/howto.txt">Tor Controller Protocol</a>.</p>
102 
+
103 
+    <p>We are looking for a vision of how Tor can work in a user's everyday
104 
+    anonymous browsing experience.</p>
105 
+
106 
+    <p>Entries may:</p>
107 
+    <ul>
108 
+    <li>Allow the user to fully configure Tor rather than manually searching
109 
+    for and opening text files.</li>
110 
+    <li>Let users learn about the current state of their Tor connection
111 
+    (for example, how well the current Tor connection is working),
112 
+    and configure or find out whether any of their applications are using it.</li>
113 
+    <li>Make alerts and error conditions visible to the user.</li>
114 
+    <li>Run on at least one of Windows, Linux, and OS&nbsp;X, on a
115 
+    not-unusually-configured consumer-level machine.</li>
116 
+    </ul>
117 
+
118 
+    <p>Other ideas include:</p>
119 
+    <ul>
120 
+    <li>Provide detailed information about which
121 
+    applications, ports, or packets are (or are not!) passing through Tor,
122 
+    including accounting for both Tor- and non-Tor traffic.</li>
123 
+    <li>Provide
124 
+    additional statistics about the Tor connection.</li>
125 
+    <li>Give users more control over how their Tor behaves at certain times
126 
+    of day or in other contexts (like operating as a server).</li>
127 
+    </ul>
128 
+
129 
+    <p>More examples of useful features include:</p>
130 
+    <ul>
131 
+    <li>How much bandwidth is Tor using? How does this compare
132 
+    to the overall network traffic to/from the computer?</li>
133 
+    <li>Is there network traffic from ports or applications that the user
134 
+    intended to be anonymized?</li>
135 
+    <li>What Tor servers does the user know about on the network? Where are
136 
+    they? How available are they?</li>
137 
+    <li>An interface for displaying or controlling Tor paths:
138 
+    "show me the network from Africa by way of Asia". Think of the global
139 
+    satellite map from the movie <i>Sneakers</i>.</li>
140 
+    <li>Configure other running applications to use Tor (for example,
141 
+    by modifying or working through the network stack, and/or by altering
142 
+    application configurations).</li>
143 
+    <li>Provide an elegant installer for Tor, your GUI submission, and
144 
+    other supporting applications.</li>
145 
+    <li>Make your GUI manage the Tor process and other supporting applications
146 
+    -- start them, stop them, realize when they've died.</li>
147 
+    <li>Provide meaningful defaults for a good Tor experience.</li>
148 
+    <li>Provide application-level anonymity -- that is, not just paying
149 
+    attention to transport anonymity on the level of Tor, but also paying
150 
+    attention to the anonymity of the http headers, cookies, etc.</li>
151 
+    <li>Let the user specify different Tor config option sets depending on
152 
+    time of day (e.g. daytime vs. nighttime).</li>
153 
+    <li>Provide useful controller functions for Tor servers too --
154 
+    for example, walk the user through recommended bandwidth configurations
155 
+    and exit policies.</li>
156 
+    <li>Have a "minimized view" of your GUI for common use, and then a more
157 
+    detailed view or set of windows when the user wants more detail.</li>
158 
+    <li>Provide a button or some automatically updating interface to let
159 
+    the user learn whether Tor is working currently, perhaps by accessing an
160 
+    external what's-my-IP site and seeing if it thinks you're a Tor server;
161 
+    and give useful messages and recommendations if it doesn't seem to
162 
+    be working.</li>
163 
+    <li>Provide a way to automatically configure local firewalls (ipchains,
164 
+    Windows firewalls, etc) to let Tor traffic out (and in, for Tor
165 
+    servers). As a bonus, configure it to prevent non-Tor traffic from
166 
+    leaving (and notify when it tries).</li>
167 
+    </ul>
168 
+
169 
+    <p>We're interested to see submissions that don't achieve all of the
170 
+    above goals -- if it's useful to Tor or Tor users in any way, please
171 
+    submit it!</p>
172 
+  </div>
173 
+  <!-- END MAINCOL -->
174 
+  <div id = "sidecol">
175 
+#include "side.wmi"
176 
+#include "info.wmi"
177 
+  </div>
178 
+  <!-- END SIDECOL -->
179 
+</div>
180 
+<!-- END CONTENT -->
181 
+#include <foot.wmi>
projects/en/hidserv.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,475 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: NLnet Project: Speed Up Tor Hidden Services" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/hidserv>">NLnet Project</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h2>NLnet Project: Speed Up Tor Hidden Services</h2>
16 
+    <hr />
17 
+
18 
+    <p>
19 
+    Tor Hidden Services allow users to set up anonymous information services,
20 
+    like websites, that can only be accessed through the Tor network and are
21 
+    protected against identification of the host that runs the services.
22 
+    The most critical limitations of Tor Hidden Services are the time it takes
23 
+    until a Hidden Service is registered in the network and the latency of
24 
+    contact establishment when accessed by a user.
25 
+    Due to design issues in the original Tor protocol,
26 
+    the connection to a new Hidden Service can take several minutes, which
27 
+    leads most users to give up before the connection has been established.
28 
+    Using Tor Hidden Services for direct interactive user-to-user
29 
+    communication (e.g. messaging) is nearly impossible due to the high latency
30 
+    of Hidden Service circuit setup.
31 
+    </p>
32 
+
33 
+    <p>
34 
+    This project aims at speeding up Tor Hidden Services by improving the way
35 
+    Tor circuits are set up between the user and the Hidden Service as well as
36 
+    the way a Hidden Service is registered in the Tor network.
37 
+    In a first step precise diagnostics of the behavior of the Hidden Services
38 
+    in lab setups and real world situations will be conducted to find the
39 
+    root causes of the bad timing effects.
40 
+    Based on these diagnostics, optimization strategies will be designed and
41 
+    verified for unwanted implications for the security and anonymity of the
42 
+    Tor network.
43 
+    The most promising optimizations will then be implemented to achieve a
44 
+    notable improvement for the users. Precise success metrics will be
45 
+    developed in the diagnostics phase, after it becomes clear where the time
46 
+    is lost and what improvements are realistic.
47 
+    The ultimate goal is to have the Hidden Services protocol change production
48 
+    ready and propagated to the Tor users within a timeframe of less than
49 
+    12 months.
50 
+    </p>
51 
+
52 
+    <p>
53 
+    This project is generously funded by:
54 
+    </p>
55 
+
56 
+    <p>
57 
+    <a href="http://www.nlnet.nl/news/2008/20080514-awards.html">
58 
+    <img src="$(IMGROOT)/nlnet-160x60.png" alt="The NLnet foundation" /></a>
59 
+    </p>
60 
+
61 
+    <table width="100%" border="0" cellspacing="0" cellpadding="3">
62 
+    <thead>
63 
+    <tr>
64 
+    <th><big>Project</big></th>
65 
+    <th><big>Due Date</big></th>
66 
+    </tr>
67 
+    </thead>
68 
+
69 
+    <tr bgcolor="#e5e5e5">
70 
+      <td>
71 
+        <b>Deliverable A:</b> Analysis, measurements and problem
72 
+        clarification<br />
73 
+        <small><em>As Tor Hidden Services have not been actively developed
74 
+        further in the last year or so of Tor development, certain aspects of
75 
+        the problems are under-diagnosed. To identify the precise sources of
76 
+        latency and time loss, an extensive analysis of the deeper reasons for
77 
+        them needs to be conducted. Deliverable A will require about one month
78 
+        of work. The results of the analysis will influence the design
79 
+        decisions to be taken in Deliverable B.</em></small>
80 
+      </td>
81 
+      <td>
82 
+        June 15, 2008
83 
+      </td>
84 
+    </tr>
85 
+
86 
+    <tr>
87 
+      <td>
88 
+        <b>Deliverable B:</b> Design and evaluation of the necessary
89 
+        changes<br />
90 
+        <small><em>The changes to Tor Hidden Services will affect core
91 
+        functionality of the protocol and therefore require a careful
92 
+        evaluation of possible repercussions for the security and anonymity. A
93 
+        two-month period is planned for the design and evaluation phase, which
94 
+        concludes with an extensive peer review.</em></small>
95 
+      </td>
96 
+      <td>
97 
+        August 15, 2008
98 
+      </td>
99 
+    </tr>
100 
+
101 
+    <tr bgcolor="#e5e5e5">
102 
+      <td>
103 
+        <b>Deliverable C:</b> Implementation<br />
104 
+        <small><em>After design, evaluation and peer review the modifications
105 
+        need to be implemented and integrated with the current Tor code base.
106 
+        The actual implementation of the necessary changes will take
107 
+        approximately two months.</em></small>
108 
+      </td>
109 
+      <td>
110 
+        October 15, 2008
111 
+      </td>
112 
+    </tr>
113 
+
114 
+    <tr>
115 
+      <td>
116 
+        <b>Deliverable D:</b> Implementation and test of the change up to
117 
+        release state<br />
118 
+        <small><em>The modification is highly critical to the security and
119 
+        anonymity of the Tor network, it requires extensive testing and
120 
+        debugging in laboratory and real life conditions. A period of three
121 
+        months is projected for testing and debugging, where the responsible
122 
+        developer is committed to the testing effort with 1/3 of its time. Part
123 
+        of the testing phase will be a public beta period.</em></small>
124 
+      </td>
125 
+      <td>
126 
+        January 15, 2009
127 
+      </td>
128 
+    </tr>
129 
+
130 
+    <tr bgcolor="#e5e5e5">
131 
+      <td>
132 
+        <b>Deliverable E:</b> Rollout<br />
133 
+        <small><em>The actual rollout to the Tor server network will be
134 
+        conducted in sync with the regular Tor release schedule. As this
135 
+        schedule is dependent on a number of external factors, like the
136 
+        completion of other software projects that should go into the same
137 
+        release, the actual release time and the time until this release has
138 
+        been accepted and installed by most Tor server operators can vary. From
139 
+        experience a period of three to four months can be
140 
+        expected.</em></small>
141 
+      </td>
142 
+      <td>
143 
+        May 15, 2009
144 
+      </td>
145 
+    </tr>
146 
+    </table>
147 
+
148 
+    <br />
149 
+
150 
+    <a id="Reports"></a>
151 
+    <h2><a class="anchor" href="#Reports">Monthly Status Reports</a></h2>
152 
+    <p>
153 
+    There will be in total eight monthly status reports beginning with the
154 
+    first deliverable on June 15, 2008 and ending with completion of
155 
+    implementation and testing work on January 15, 2009.
156 
+    </p>
157 
+
158 
+    <table width="100%" border="0" cellspacing="0" cellpadding="3">
159 
+    <thead>
160 
+    <tr>
161 
+    <th><big>Month,</big></th>
162 
+    <th><big>Status Report</big></th>
163 
+    </tr>
164 
+    </thead>
165 
+
166 
+    <tr bgcolor="#e5e5e5">
167 
+      <td>
168 
+        <a id="Jun08"></a>
169 
+        <a class="anchor" href="#Jun08">Jun 08</a>
170 
+      </td>
171 
+      <td>
172 
+        <small><em>The original goal of analyzing the problems that lead to
173 
+        slowdown of Tor Hidden Services has been accomplished. Part of this
174 
+        analysis was measuring the delay that a user experiences when
175 
+        setting up or accessing a hidden service. Furthermore, measurement data
176 
+        from April 2008 could be leveraged to explore timings of internal
177 
+        substeps of establishing a connection to a hidden service. The results
178 
+        of this analysis are contained in a 22-page
179 
+        <a href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">report</a>
180 
+        that has been made public on the Tor
181 
+        <a href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">developer
182 
+        mailing list</a>.</em></small>
183 
+        <br/>
184 
+        <small><em>The analysis also unveiled a few bugs which were responsible
185 
+        for part of the delay in making a hidden service available for
186 
+        clients. Some bugs have been fixed subsequent to the analysis, others
187 
+        will be fixed soon. The evaluation has further brought up several
188 
+        possible approaches to improve Tor Hidden Service performance. Some of
189 
+        these ideas can be applied immediately, while others require deeper
190 
+        analysis and new measurements. Finally, in the course of the analysis,
191 
+        we discovered that some improvements require more in-depth
192 
+        changes to Tor which are not directly related to hidden services. These
193 
+        changes cannot be achieved in the time frame of this
194 
+        project.</em></small>
195 
+      </td>
196 
+    </tr>
197 
+
198 
+    <tr>
199 
+      <td>
200 
+        <a id="Jul08"></a>
201 
+        <a class="anchor" href="#Jul08">Jul 08</a>
202 
+      </td>
203 
+      <td>
204 
+        <small><em>All bugs that have been found in the analysis have been
205 
+        fixed. This includes the 2 bugs that have already been fixed during the
206 
+        analysis and 4 more bugs that were fixed within the past 30 days. While
207 
+        the bugfixes remove unintended performance bottlenecks due to
208 
+        programming errors, some of the design changes that have been spotted
209 
+        in the previous analysis have side-effects on anonymity or overall
210 
+        network load which need to be evaluated against individual performance
211 
+        gains. A <a href="http://freehaven.net/~karsten/hidserv/discussion-2008-07-15.pdf">report</a>
212 
+        has been published to the
213 
+        <a href="http://archives.seul.org/or/dev/Jul-2008/msg00034.html">developer
214 
+        mailing list</a> including 7 possible design changes that need to be
215 
+        discussed. Some evaluations (namely Low-Bandwidth Measurements and the
216 
+        Grand Scaling Plan) have turned out to require more time than expected
217 
+        and had to be scheduled for a later time in the project than
218 
+        deliverable B. The current plan is to perform these evaluations within
219 
+        the timeframe until January 15 and work with assumptions until final
220 
+        results are available.</em></small>
221 
+      </td>
222 
+    </tr>
223 
+
224 
+    <tr bgcolor="#e5e5e5">
225 
+      <td>
226 
+        <a id="Aug08"></a>
227 
+        <a class="anchor" href="#Aug08">Aug 08</a>
228 
+      </td>
229 
+      <td>
230 
+        <small><em>During the past 30 days the 7 proposed designs have been
231 
+        further evaluated and discussed. Four of them have proven to be
232 
+        applicable in terms of the required changes to the code and possible
233 
+        anonymity implications. One has been classified as bug rather than
234 
+        design change. Two had to be excluded for either unforeseeable security
235 
+        problems, or uncertainty of actual performance
236 
+        improvements.</em></small>
237 
+        <br/>
238 
+        <small><em>Together with the results from July 15, the design phase has
239 
+        been concluded. The tasks for the upcoming implementation phase are now
240 
+        quite clear: One bug needs to be fixed and four design changes need to
241 
+        be implemented. Further, evaluations of the changed design need to be
242 
+        performed in order to verify their usefulness. A
243 
+        <a href="http://freehaven.net/~karsten/hidserv/design-2008-08-15.pdf">report</a>
244 
+        with the results of the design phase has been published to the
245 
+        <a href="http://archives.seul.org/or/dev/Aug-2008/msg00025.html">developer
246 
+        mailing list</a>.</em></small>
247 
+      </td>
248 
+    </tr>
249 
+
250 
+    <tr>
251 
+      <td>
252 
+        <a id="Sep08"></a>
253 
+        <a class="anchor" href="#Sep08">Sep 08</a>
254 
+      </td>
255 
+      <td>
256 
+        <small><em>During the first half of the implementation phase two bugs
257 
+        could be fixed that were related to hidden services: the
258 
+        <a href="http://bugs.noreply.org/flyspray/index.php?do=details&amp;id=767">first
259 
+        bug</a> has already been identified in the design phase and was
260 
+        responsible for an unusual high failure rate when making a hidden
261 
+        service available in the system; the
262 
+        <a href="http://bugs.noreply.org/flyspray/index.php?id=814&amp;do=details">second
263 
+        bug</a> was found during the implementation phase and was responsible
264 
+        for failure to connect to a working hidden service. Both bugfixes will
265 
+        be included in the next unstable version and likely be backported to
266 
+        one of the next stable releases.</em></small>
267 
+        <br/>
268 
+        <small><em>The four design changes that were proposed as result of the
269 
+        design phase have been implemented in an
270 
+        <a href="https://tor-svn.freehaven.net/svn/tor/branches/hidserv-design-changes/">experimental
271 
+        branch</a> of the unstable development tree. Early function tests have
272 
+        shown that these changes work and provide better (perceived)
273 
+        performance. This needs to be confirmed throughout the next four weeks
274 
+        in internal tests. The next goal is to prepare a release of this
275 
+        experimental branch that can be given out to beta testers at the
276 
+        beginning of the upcoming testing phase.</em></small>
277 
+      </td>
278 
+    </tr>
279 
+
280 
+    <tr bgcolor="#e5e5e5">
281 
+      <td>
282 
+        <a id="Oct08"></a>
283 
+        <a class="anchor" href="#Oct08">Oct 08</a>
284 
+      </td>
285 
+      <td>
286 
+        <small><em>The implementation phase has been concluded. The bugfixes
287 
+        that were found in the past 30 days have been released in developer
288 
+        version <a href="http://archives.seul.org/or/talk/Oct-2008/msg00093.html">0.2.1.6-alpha</a>.
289 
+        The four design changes that were identified in the design phase have
290 
+        been specified in
291 
+        <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/155-four-hidden-service-improvements.txt">proposal 155</a>.
292 
+        Three design changes have been included in the development codebase and
293 
+        will automatically be included in the next development version. The
294 
+        first two design changes improve connection establishment to a hidden
295 
+        service by reducing a timeout from 60 to 30 seconds and by making a
296 
+        second attempt in parallel after a delay of 15 seconds. The third
297 
+        design change affects publication of a hidden service in the network by
298 
+        advertising the service at 5 rather than 3 points in the network in
299 
+        parallel and succeeding as soon as 3 points are established. The fourth
300 
+        design change has turned out to be rather ineffective, but would add
301 
+        considerable code complexity and was therefore dismissed. By now there
302 
+        are no more open bugfixes or new designs. All changes are in the
303 
+        development codebase and can be tested in the next phase.</em></small>
304 
+      </td>
305 
+    </tr>
306 
+
307 
+    <tr>
308 
+      <td>
309 
+        <a id="Nov08"></a>
310 
+        <a class="anchor" href="#Nov08">Nov 08</a>
311 
+      </td>
312 
+      <td>
313 
+        <small><em>The performance improvements that were implemented in the
314 
+        last phase have been released in Tor version 0.2.1.7-alpha. Users can
315 
+        download this development version from the Tor homepage and test the
316 
+        improvements with minimal effort. Further, two bugfixes (<a
317 
+        href="http://bugs.noreply.org/flyspray/index.php?id=767&amp;do=details">1</a>,
318 
+        <a href="http://bugs.noreply.org/flyspray/index.php?id=814&amp;do=details">2</a>)
319 
+        that were found in the course of this project have been backported to
320 
+        the stable branch and will be included with the next stable version
321 
+        0.2.0.32.</em></small>
322 
+        <br/>
323 
+        <small><em>The main focus of the past 31 days was to perform new
324 
+        measurements to see whether the improvements are effective or not.
325 
+        Measurements were conducted for two days in the time of November 6th to
326 
+        8th. Unfortunately, the Tor network suffered a serious problem in this
327 
+        time: An expired directory authority certificate produced huge amounts
328 
+        of traffic within the Tor network which <a
329 
+        href="http://archives.seul.org/or/talk/Nov-2008/msg00053.html">forced
330 
+        many operators to shut down their relays</a>. A second measurement was
331 
+        performed between 13th and 15th. The raw data are available <a
332 
+        href="http://freehaven.net/~karsten/hidserv/perfdata-2008-11-13.tar.gz">here</a>
333 
+        (40 MB). But results show that the overall
334 
+        network performance is still worse than in June 2008 when the first
335 
+        hidden service measurements have been performed. This becomes visible
336 
+        when comparing requests to the Tor directories which have not been
337 
+        affected by the performance improvements and which exhibit
338 
+        significantly worse performance than before. The effects of performance
339 
+        improvements are visible, but absolute values are not comparable at
340 
+        this time. New measurements will be conducted in December in the hope
341 
+        that the effects of this problem have mitigated.</em></small>
342 
+        <br/>
343 
+        <small><em>Further, there might be a <a
344 
+        href="http://bugs.noreply.org/flyspray/index.php?id=847&amp;do=details">bug</a>
345 
+        in the way how Tor downloads directory information during
346 
+        bootstrapping. Even though this is not related to hidden services, an
347 
+        improvement would benefit hidden service publication, too. Part of the
348 
+        work during the upcoming 30 days will be to investigate this bug.
349 
+        </em></small>
350 
+      </td>
351 
+    </tr>
352 
+
353 
+    <tr bgcolor="#e5e5e5">
354 
+      <td>
355 
+        <a id="Dec08"></a>
356 
+        <a class="anchor" href="#Dec08">Dec 08</a>
357 
+      </td>
358 
+      <td>
359 
+        <small><em>Part of the last 30 days has been used to fix bugs that have
360 
+        influenced the previous hidden service measurements. The first <a
361 
+        href="http://archives.seul.org/or/cvs/Nov-2008/msg00100.html">bugfix</a>
362 
+        corrects a possible segmentation fault that was very likely responsible
363 
+        for a number of failed measurement runs. Another <a
364 
+        href="https://bugs.torproject.org/flyspray/index.php?id=847&amp;do=details">bug</a>
365 
+        could be explained that lead to significant delays in bootstrapping:
366 
+        Very slow directory authorities occupied bootstrapping clients for
367 
+        a long time before clients finally gave up and bootstrapped using
368 
+        another authority. As a result, the slowest two directory authorities
369 
+        have dedicated more bandwidth to their nodes, so that the effect is
370 
+        mitigated. A third <a
371 
+        href="https://bugs.torproject.org/flyspray/index.php?id=874&amp;do=details">bug</a>
372 
+        has been introduced with the hidden service performance improvements in
373 
+        November; the effect was that Tor processes running hidden services
374 
+        would stop advertising their service upon reloading their
375 
+        configuration. Further, this bug has uncovered that Tor has
376 
+        re-established its introduction points upon reloading, which might have
377 
+        affected hidden service stability. This bug has been fixed and will be
378 
+        included in the upcoming version 0.2.1.9-alpha.</em></small>
379 
+        <br/>
380 
+        <small><em>Apart from fixing bugs, new measurements have been performed
381 
+        between December 8 and 10. These will very likely be the final
382 
+        measurements to compare hidden service performance now with the
383 
+        beginning of the project. The data have not been completely evaluated,
384 
+        so it is difficult to make a statement about improvements at this
385 
+        point. However, a <a
386 
+        href="http://freehaven.net/~karsten/hidserv/prelimreport-2008-12-15.pdf">preliminary
387 
+        evaluation</a> shows that service publication times have improved
388 
+        significantly. This is a result of Tor clients bootstrapping faster and
389 
+        of the performance improvements added in November. In contrast to this,
390 
+        the results for establishing a connection to a hidden service are less
391 
+        promising. While the improvements added in November seem to have a
392 
+        positive effect on performance, some substeps exhibit significantly
393 
+        worse performance. One example is fetching hidden service descriptors
394 
+        in order to contact a hidden service. A possible explanation is that
395 
+        the sudden increase in the number of hidden service directory nodes in
396 
+        September has had a negative effect on performance. Part of the work in
397 
+        the final 31 days will be to evaluate these data in more detail and
398 
+        make a final conclusion on the achievements of this
399 
+        project.</em></small>
400 
+      </td>
401 
+    </tr>
402 
+
403 
+    <tr>
404 
+      <td>
405 
+        <a id="Jan09"></a>
406 
+        <a class="anchor" href="#Jan09">Jan 09</a>
407 
+      </td>
408 
+      <td>
409 
+        <small><em>The testing phase has been concluded. Testing was performed
410 
+        in a public beta phase with all changes to hidden services being part
411 
+        of the 0.2.1.x-alpha series. The result of the public beta phase is a
412 
+        couple of identified bugs that could already be fixed.</em></small>
413 
+        <br/>
414 
+        <small><em>Another part of testing was a second set of measurements
415 
+        that was performed in December. A
416 
+        <a href="http://freehaven.net/~karsten/hidserv/comparison-2009-01-15.pdf">comparison</a>
417 
+        of measurements performed in June and December has revealed that the
418 
+        changes of this project are effective. Service publication times could
419 
+        be more than halved from 2:12 minutes to 58 seconds in the mean. This
420 
+        improvement is far better than expected. With this improvement it might
421 
+        even be worthwile to think about reducing stabilization time from 30
422 
+        seconds to a lower value in the future. However, connection
423 
+        establishment remains at approximately 56 seconds between requesting a
424 
+        hidden service to having established a connection to the hidden server.
425 
+        The main reason for missing improvements is the switch from the
426 
+        centralized to a decentralized storage for hidden service descriptors.
427 
+        This deteriorating effect of distributing the hidden service directory
428 
+        has not been expected before. Future work should focus on improving
429 
+        downloads from the distributed hidden service directory, for example by
430 
+        parallelizing requests.</em></small>
431 
+        <br/>
432 
+        <small><em>This report concludes the series of monthly status updates.
433 
+        The rollout of the 0.2.1.x series including the hidden service
434 
+        performance improvements is going to take place within the next weeks
435 
+        to months.</em></small>
436 
+      </td>
437 
+    </tr>
438 
+    </table>
439 
+
440 
+    <br />
441 
+
442 
+    <!-- Do we want a people section? If so, would it make sense to write what
443 
+    these people will be doing? And what exactly are these people going to
444 
+    do? :)
445 
+    <a id="People"></a>
446 
+    <h2><a class="anchor" href="#People">People</a></h2>
447 
+    <ul>
448 
+    <li><a href="<page about/people>#Core">Karsten Loesing</a></li>
449 
+    <li><a href="<page about/people>#Core">Steven Murdoch</a></li>
450 
+    </ul>
451 
+    -->
452 
+
453 
+    <a id="Links"></a>
454 
+    <h2><a class="anchor" href="#Links">Links</a></h2>
455 
+    <ul>
456 
+    <li>Research paper on <b>Performance Measurements and Statistics of Tor
457 
+    Hidden Services</b>
458 
+    (<a href="http://www.uni-bamberg.de/fileadmin/uni/fakultaeten/wiai_lehrstuehle/praktische_informatik/Dateien/Publikationen/loesing2008performance.pdf">PDF</a>)
459 
+    by Karsten Loesing, Werner Sandmann, Christian Wilms, and Guido Wirtz. In
460 
+    the Proceedings of the 2008 International Symposium on Applications and the
461 
+    Internet (SAINT), Turku, Finland, July 2008.</li>
462 
+
463 
+    <!-- In the future, put links to proposal, preliminary results, etc. here -->
464 
+
465 
+    </ul>
466 
+  </div>
467 
+  <!-- END MAINCOL -->
468 
+  <div id = "sidecol">
469 
+#include "side.wmi"
470 
+#include "info.wmi"
471 
+  </div>
472 
+  <!-- END SIDECOL -->
473 
+</div>
474 
+<!-- END CONTENT -->
475 
+#include <foot.wmi>
projects/en/lowbandwidth.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,360 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: NLnet Project: Tor for Low Bandwidth Clients" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/lowbandwidth>">NLnet Project: Tor for Low Bandwidth Clients</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h2>NLnet Project: Tor for Low Bandwidth Clients</h2>
16 
+    <hr />
17 
+
18 
+    <p>
19 
+    The Tor anonymity system is currently only usable by internet users who
20 
+    have high-bandwidth connections. Upon the start of the Tor client, a large file
21 
+    with all Tor server descriptions is being downloaded. This file is the so-called Tor
22 
+    Directory and enables the client to choose from the available mix-servers in the Tor network. The
23 
+    download of the full Tor Directory is required by the current Tor protocol. This directory
24 
+    file is too large for users on modem lines or on mobile data networks like GPRS as the initial
25 
+    download that is triggered every time an user logs in takes 10 to 30 minutes over a slow
26 
+    line. As a result, Tor is not usable by modem and mobile users. One of the major goals of
27 
+    the Tor project is to provide secure anonymous internet access to users in dictatorships
28 
+    and repressive states. These locations often have very slow internet connections,
29 
+    either by modem or due to low-bandwidth links to the outside world. By enabling these users to
30 
+    use the Tor network, significant progress can be made towards free communication and
31 
+    information in these countries.
32 
+    </p>
33 
+
34 
+    <p>
35 
+    To make Tor usable also for users on low-bandwidth connections, an
36 
+    evolution of the Tor protocol is needed to reduce the initial download size. This new Tor
37 
+    protocol version should change the way a client receives the information for its Tor
38 
+    circuit setup in a way, that the initial download can be performed over a 14.4 kbps modem line
39 
+    in about three minutes. The work to be conducted under the proposal has the ultimate
40 
+    goal of getting the protocol change production ready and propagated to the Tor users
41 
+    within a timeframe of less then 12 months. The resulting software will be published under
42 
+    the 3-Clause BSD license, as all of the Tor code. All deliverables will be fully public.
43 
+    </p>
44 
+
45 
+    <p>
46 
+    This project is generously funded by:
47 
+    </p>
48 
+
49 
+    <p>
50 
+    <a href="http://www.nlnet.nl/news/2008/20080514-awards.html">
51 
+    <img src="$(IMGROOT)/nlnet-160x60.png" alt="The NLnet foundation" /></a>
52 
+    </p>
53 
+
54 
+    <table width="100%" border="0" cellspacing="0" cellpadding="3">
55 
+    <thead>
56 
+    <tr>
57 
+    <th><big>Project</big></th>
58 
+    <th><big>Due Date</big></th>
59 
+    </tr>
60 
+    </thead>
61 
+
62 
+    <tr bgcolor="#e5e5e5">
63 
+      <td>
64 
+        <b>Deliverable A:</b> Design and evaluation of the protocol change<br />
65 
+        <small><em>This deliverable covers the detailed design and
66 
+        simulation-based evaluation of the necessary changes and design
67 
+        modifications to the current Tor protocol.
68 
+        The changes in protocol will be relatively substantial, so it requires a careful
69 
+        evaluation of possible repercussions for the security and anonymity of the Tor network. A
70 
+        two-month period is planned for this design and evaluation phase, which concludes with an
71 
+        extensive peer review. Part of Deliverable A will be a goal definition for performance
72 
+        for the implementation phase. The design goal is to shrink the Tor Directory
73 
+        size that needs to be downloaded to about 300 Kilobytes, which would enable an user on a 14.4
74 
+        kbps line to download it in roughly three minutes. There may be deviations from this
75 
+        design goal if required to maintain anonymity and security, but this is the figure to aim for.
76 
+        </em></small>
77 
+      </td>
78 
+      <td>
79 
+        July 15, 2008
80 
+      </td>
81 
+    </tr>
82 
+
83 
+    <tr>
84 
+      <td>
85 
+        <b>Deliverable B:</b>Implementation of protocol change<br />
86 
+        <small><em>After design, evaluation and peer review the modifications
87 
+        need to be implemented and integrated with the current Tor code base. The actual implementation of
88 
+        the necessary changes will take approximately three months.
89 
+        </em></small>
90 
+      </td>
91 
+      <td>
92 
+        October 15, 2008
93 
+      </td>
94 
+    </tr>
95 
+
96 
+    <tr bgcolor="#e5e5e5">
97 
+      <td>
98 
+        <b>Deliverable C:</b>Testing<br />
99 
+        <small><em>Since the modification is highly critical to the security
100 
+        and anonymity of the Tor network, it requires extensive testing and debugging in laboratory and real life
101 
+        conditions. A period of three months is projected for testing and debugging, where the
102 
+        responsible developer is committed to the testing effort with 1/3 of its time. Part of the
103 
+        testing phase will be a public beta period.
104 
+        </em></small>
105 
+      </td>
106 
+      <td>
107 
+        January 15, 2009
108 
+      </td>
109 
+    </tr>
110 
+
111 
+    <tr>
112 
+      <td>
113 
+        <b>Deliverable D:</b>Rollout<br />
114 
+        <small><em>The actual rollout to the Tor server network will be
115 
+          conducted in sync with the regular Tor
116 
+          release schedule. As this schedule is dependent on a number of external
117 
+          factors, like the completion of other software projects that should go into the same
118 
+          release, the actual release time and the time until this release has been accepted and
119 
+          installed by most Tor server operators can vary. From experience a period of three to four
120 
+          months can be expected. The rollout will be conducted as part of the regular Tor
121 
+          release process that is a persistent activity done by volunteers and by personal paid through
122 
+          other grants to the Tor project.
123 
+        </em></small>
124 
+      </td>
125 
+      <td>
126 
+        April 15, 2009
127 
+      </td>
128 
+    </tr>
129 
+    </table>
130 
+
131 
+    <br />
132 
+
133 
+    <a id="Reports"></a>
134 
+    <h2><a class="anchor" href="#Reports">Monthly Status Reports</a></h2>
135 
+    <p>
136 
+    There will be in total eight monthly status reports beginning with the
137 
+    first deliverable on July 15, 2008 and ending with completion of
138 
+    implementation and testing work on January 15, 2009.
139 
+    </p>
140 
+
141 
+    <table width="100%" border="0" cellspacing="0" cellpadding="3">
142 
+    <thead>
143 
+    <tr>
144 
+    <th><big>Month,</big></th>
145 
+    <th><big>Status Report</big></th>
146 
+    </tr>
147 
+    </thead>
148 
+
149 
+    <tr bgcolor="#e5e5e5">
150 
+      <td>
151 
+        <a id="Jun08"></a>
152 
+        <a class="anchor" href="#Jun08">Jun 08</a>
153 
+      </td>
154 
+      <td>
155 
+        <small><em>We did some initial measuring of Tor clients
156 
+        bootstrapping. The results are not very surprising: a client
157 
+        fetches about 10KB of certs, one consensus for 140KB (now 90KB, see
158 
+        next paragraph), and about 1.5 megs of Server Descriptors (after
159 
+        half of which it starts building circuits).</em></small>
160 
+        <br />
161 
+        <small><em><a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/138-remove-down-routers-from-consensus.txt">Proposal
162 
+        138</a> shrinks consensus documents by 30% to
163 
+        40% and has already been implemented and merged into the spec.
164 
+        Implementation is part of the 0.2.1.x-alpha tree and the code will
165 
+        take effect once over two-thirds of the directory authorities
166 
+        (i.e. 5 out of 6) have upgraded.</em></small>
167 
+        <br />
168 
+        <small><em><a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">Proposal
169 
+        140</a> does not directly relate to reducing initial download size,
170 
+        but instead tries to make subsequent downloads of new consensus
171 
+        documents use fewer bytes has also been written up and <a
172 
+        href="http://archives.seul.org/or/dev/Jun-2008/msg00013.html">sent to
173 
+        or-dev</a>. There are some questions to be answered from other Tor
174 
+        developers first, but other than that I think it's fine and could
175 
+        be implemented.</em></small>
176 
+        <br />
177 
+        <small><em>The Big Thing is making clients not download all 1.5 megs
178 
+        of server descriptors. <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Proposal
179 
+        141</a> has been <a
180 
+        href="http://archives.seul.org/or/dev/Jun-2008/msg00017.html">sent
181 
+        to or-dev</a>. There are basically 3 things to it, as
182 
+        far as I can see at the moment: move load balancing info into the
183 
+        consensus (should not be hard), implement something so that Tor
184 
+        clients can fetch SDs on demand from routers along their circuit
185 
+        while they are building it (described in the draft), and deal with
186 
+        exit selection. We're still developing ideas for the last part;
187 
+        some possibilities are mentioned in the draft.</em></small>
188 
+      </td>
189 
+    </tr>
190 
+
191 
+    <tr>
192 
+      <td>
193 
+        <a id="Jul08"></a>
194 
+        <a class="anchor" href="#Jul08">Jul 08</a>
195 
+      </td>
196 
+      <td>
197 
+        <small><em>Work on <a
198 
+        href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Proposal
199 
+        141</a> is continuing:  There are two basic ideas for how to move
200 
+        load balancing information into the consensus: One is the
201 
+        authorities generate the weights that clients should use and put
202 
+        that in the consensus, the other approach is to just put bandwidth
203 
+        information from the server descriptor there.  The latter option
204 
+        is probably friendlier when one also considers <a
205 
+        href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">Proposal
206 
+        140</a> since it avoids a having number of highly fluctuating
207 
+        numbers in the consensus.</em></small>
208 
+        <br />
209 
+        <small><em>For handling exit policies <a
210 
+        href="http://archives.seul.org/or/dev/Jul-2008/msg00022.html">a
211 
+        post on the or-dev mailinglist</a> suggests that a hash identifying a
212 
+        node's exit policy be added to the consensus document.  The addition
213 
+        of another 160 high-entropy bits per node to the consensus might
214 
+        be a cause for concern but we think that since a lot of the exit
215 
+        policies are the same the consensus document will compress nicely.
216 
+        Measurements pending.</em></small>
217 
+      </td>
218 
+    </tr>
219 
+
220 
+    <tr bgcolor="#e5e5e5">
221 
+      <td>
222 
+        <a id="Aug08"></a>
223 
+        <a class="anchor" href="#Aug08">Aug 08</a>
224 
+      </td>
225 
+      <td>
226 
+        <small><em>Directory authority voting documents, and their consensus
227 
+        forming algorithm have been changed to include bandwidth information
228 
+        and policy summaries as documented in Proposal 141.  Once five of
229 
+        the six running authorities have upgraded to trunk at at least
230 
+        revision 16554 the consensus will start to include that
231 
+        information.</em></small>
232 
+      </td>
233 
+    </tr>
234 
+
235 
+    <tr>
236 
+      <td>
237 
+        <a id="Sep08"></a>
238 
+        <a class="anchor" href="#Sep08">Sep 08</a>
239 
+      </td>
240 
+      <td>
241 
+    <small><em>No updates for September.</em></small>
242 
+      </td>
243 
+    </tr>
244 
+
245 
+    <tr bgcolor="#e5e5e5">
246 
+      <td>
247 
+        <a id="Oct08"></a>
248 
+        <a class="anchor" href="#Oct08">Oct 08</a>
249 
+      </td>
250 
+      <td><p>
251 
+    <small><em>We didn't hit our "finish
252 
+    the implementation" milestone for this month since the developer leading
253 
+    the project has too much on his plate. The good news there is that we've
254 
+    gotten quite a bit of the implementation work done, and it's been in for
255 
+    several months now (since the August milestone) so it's seen a lot of
256 
+    testing already. The remaining implementation steps are to teach relays
257 
+    how to receive requests for fetching a relay descriptor from inside a
258 
+    circuit (we probably want to use a new cell type specifically for this,
259 
+    so we cut out a round-trip), and then teach clients to do that when the
260 
+    relay they're using is running a recent enough version. These two steps
261 
+    are written in more detail in
262 
+    <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Section 3.2 of proposal 141</a></em></small></p>
263 
+
264 
+    <p><small><em>Our new timing plan is to have both of these pieces in place by mid Nov,
265 
+    and if that starts looking less likely then we're going to do a more
266 
+    radical overhaul of our timing plan and maybe also the design.</em></small></p>
267 
+
268 
+    <p><small><em>There are several other components we'd like to get
269 
+    to after this piece of it -- one we've been thinking about a lot lately
270 
+    is downloading "diffs" of the latest consensus:
271 
+    <a href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">140-consensus-diffs.txt</a>.
272 
+    First this could save bandwidth, which is always nice when multiplied
273 
+    by the total number of clients, but it also means that we can use this
274 
+    saved bandwidth to fetch the diffs more often than the current "every
275 
+    3 to 4 hours". If clients learn more up-to-date directory information,
276 
+    then they can build faster paths because they have better information for
277 
+    each relay's bandwidth (which ties into the first NLnet project above),
278 
+    but the key new idea is that it also means that we're better at taking
279 
+    advantage of transient relays: right now a relay needs to be up for 3 or
280 
+    4 hours before it sees any users, and that rules out a lot of volunteers
281 
+    who want to run a relay but only want to be up a few hours at a time.</em></small></p>
282 
+    <p><small><em>The next step is to get the
283 
+    implementation for proposal 141 finished so we can start putting it in
284 
+    front of users for testing. Soon, we hope!</em></small></p>
285 
+      </td>
286 
+    </tr>
287 
+
288 
+    <tr>
289 
+      <td>
290 
+        <a id="Nov08"></a>
291 
+        <a class="anchor" href="#Nov08">Nov 08</a>
292 
+      </td>
293 
+      <td>
294 
+    <p><small><em>It looks like the
295 
+    original plan we had for the last development piece was both a) way
296 
+    harder than we hoped, and b) hopefully overkill compared to what we need.</em></small></p>
297 
+
298 
+    <p><small><em> Roger restarted the design discussion on or-dev:
299 
+    <a href="http://archives.seul.org/or/dev/Nov-2008/threads.html">http://archives.seul.org/or/dev/Nov-2008/threads.html</a>.</em></small></p>
300 
+
301 
+    <p><small><em>I think we now have a better handle on the options and tradeoffs:
302 
+    <a href="http://archives.seul.org/or/dev/Nov-2008/msg00007.html">http://archives.seul.org/or/dev/Nov-2008/msg00007.html</a>.</em></small></p>
303 
+
304 
+    <p><small><em>Nick has been buried in other development projects (hopefully starting to
305 
+    wrap up this month-ish), and I want to get his opinion on how to proceed;
306 
+    I am hoping we'll pick one of the more simple approaches.</em></small></p>
307 
+
308 
+    <p><small><em>Alas, the really simple approaches provide less scalability. But I think
309 
+    they will be good stopgaps until later -- and when 'later' arrives, who
310 
+    knows what else will have changed.</em></small></p>
311 
+      </td>
312 
+    </tr>
313 
+
314 
+    <tr bgcolor="#e5e5e5">
315 
+      <td>
316 
+        <a id="Jan09"></a>
317 
+        <a class="anchor" href="#Jan09">Jan 09</a>
318 
+      </td>
319 
+      <td>
320 
+    <p><small><em>
321 
+    I wrote up the more detailed version of our new design idea, as <a
322 
+    href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/158-microdescriptors.txt">Tor
323 
+    proposal #158</a>, and discussion has started at <a
324 
+    href="http://archives.seul.org/or/dev/Jan-2009/msg00010.html">http://archives.seul.org/or/dev/Jan-2009/msg00010.html</a>.</em></small></p>
325 
+
326 
+    <p><small><em>
327 
+    I think this is finally the one! (Well, once I finish folding in all
328 
+    the comments.)
329 
+    </em></small></p>
330 
+
331 
+    <p><small><em>
332 
+    One of the big reasons why the project isn't on its original schedule is
333 
+    that a main conclusion from <a href="<page projects/hidserv>">Karsten's
334 
+    NLnet project on hidden service performance</a> was that it's the circuit
335 
+    extension that's the main killer. Yet this project had proposed to add
336 
+    more round-trips and complexity into exactly that step. So we needed
337 
+    to build a better plan to achieve the original goal without screwing up
338 
+    performance even more.
339 
+    </em></small></p>
340 
+
341 
+    <p><small><em>We've been revising the design proposal over the past weeks, and
342 
+    I think we'll be ready soon to start implementing. Note that since
343 
+    we have a bunch of development items we're hoping to land in mid Feb
344 
+    already, it's likely that this implementation won't land until late Feb
345 
+    or March. This time for sure!</em></small></p>
346 
+      </td>
347 
+    </tr>
348 
+    </table>
349 
+
350 
+    <br />
351 
+  </div>
352 
+  <!-- END MAINCOL -->
353 
+  <div id = "sidecol">
354 
+#include "side.wmi"
355 
+#include "info.wmi"
356 
+  </div>
357 
+  <!-- END SIDECOL -->
358 
+</div>
359 
+<!-- END CONTENT -->
360 
+#include <foot.wmi>
projects/en/projects.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,106 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Projects Overview" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects Overview</a>
10 
+  </div>
11 
+	<div id="maincol">
12 
+  	<h1>Client-side Projects</h1>
13 
+    <p>Consectetur adipiscing elit. Proin sit amet dolor justo, lacinia dapibus est. Lorem ipsum dolor sit amet, consectetur adipiscing elit. In orci est, pellentesque sit amet consequat eget, venenatis id augue. Quisque arcu velit, ultricies non porta a, dictum in lorem. Quisque pulvinar laoreet fermentum. Quisque mauris nulla, lobortis non facilisis at, lacinia in diam. Sed at enim tortor, vitae consequat elit.</p>
14 
+    <div class="featured-project focus left first">
15 
+			<img class="project-icon" src="$(IMGROOT)/icon-default.jpg" alt="Default Icon" />
16 
+      <div class="name">Torbrowser</div>
17 
+      <div class="caps">By Author</div>
18 
+      <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
19 
+    </div>
20 
+    <div class="featured-project focus left">
21 
+			<img class="project-icon" src="$(IMGROOT)/icon-default.jpg" alt="Default Icon" />
22 
+      <div class="name">Torbutton</div>
23 
+      <div class="caps">By Author</div>
24 
+      <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/torbutton>">Learn more &raquo;</a></p>
25 
+    </div>
26 
+    <table class="topforty">
27 
+    	<tr>
28 
+        <td class="beige">
29 
+          <div class="name">Tordnsel</div>
30 
+          <div class="caps">By Author</div>
31 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/tordnsel>">Learn more &raquo;</a></p>
32 
+        </td>
33 
+        <td>
34 
+          <div class="name">Vidalia</div>
35 
+          <div class="caps">By Author</div>
36 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/vidalia>">Learn more &raquo;</a></p>
37 
+        </td>
38 
+        <td class="beige">
39 
+          <div class="name">Project Name</div>
40 
+          <div class="caps">By Author</div>
41 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
42 
+        </td>
43 
+      </tr>
44 
+      <tr>
45 
+        <td>
46 
+          <div class="name">Project Name</div>
47 
+          <div class="caps">By Author</div>
48 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
49 
+        </td>
50 
+        <td class="beige">
51 
+          <div class="name">Project Name</div>
52 
+          <div class="caps">By Author</div>
53 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
54 
+        </td>
55 
+        <td>
56 
+          <div class="name">Project Name</div>
57 
+          <div class="caps">By Author</div>
58 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
59 
+        </td>
60 
+      </tr>
61 
+      <tr>
62 
+        <td class="beige">
63 
+          <div class="name">Project Name</div>
64 
+          <div class="caps">By Author</div>
65 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
66 
+        </td>
67 
+        <td>
68 
+          <div class="name">Project Name</div>
69 
+          <div class="caps">By Author</div>
70 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
71 
+        </td>
72 
+        <td class="beige">
73 
+          <div class="name">Project Name</div>
74 
+          <div class="caps">By Author</div>
75 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
76 
+        </td>
77 
+      </tr>
78 
+      <tr>
79 
+        <td>
80 
+          <div class="name">Project Name</div>
81 
+          <div class="caps">By Author</div>
82 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
83 
+        </td>
84 
+        <td class="beige">
85 
+          <div class="name">Project Name</div>
86 
+          <div class="caps">By Author</div>
87 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
88 
+        </td>
89 
+        <td>
90 
+          <div class="name">Project Name</div>
91 
+          <div class="caps">By Author</div>
92 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
93 
+        </td>
94 
+      </tr>
95 
+    </table>
96 
+    <!-- END TABLE -->
97 
+  </div>
98 
+  <!-- END MAINCOL -->
99 
+  <div id = "sidecol">
100 
+#include "side.wmi"
101 
+#include "info.wmi"
102 
+  </div>
103 
+  <!-- END SIDECOL -->
104 
+</div>
105 
+<!-- END CONTENT -->
106 
+#include <foot.wmi>
projects/en/sampleproject.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,26 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Projects Overview" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/projects>">Sample Project</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+
14 
+    <h1>Sample Tor Project</h1>
15 
+    Here is some information
16 
+
17 
+  </div>
18 
+  <!-- END MAINCOL -->
19 
+  <div id = "sidecol">
20 
+#include "side.wmi"
21 
+#include "info.wmi"
22 
+  </div>
23 
+  <!-- END SIDECOL -->
24 
+</div>
25 
+<!-- END CONTENT -->
26 
+#include <foot.wmi>
projects/en/serverside.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,107 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Server-side Projects" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+  <div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/serverside>">Server-side Projects</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+  	<h1>Server-side Projects</h1>
14 
+    <p>Consectetur adipiscing elit. Proin sit amet dolor justo, lacinia dapibus est. Lorem ipsum dolor sit amet, consectetur adipiscing elit. In orci est, pellentesque sit amet consequat eget, venenatis id augue. Quisque arcu velit, ultricies non porta a, dictum in lorem. Quisque pulvinar laoreet fermentum. Quisque mauris nulla, lobortis non facilisis at, lacinia in diam. Sed at enim tortor, vitae consequat elit.</p>
15 
+    <div class="featured-project focus left first">
16 
+			<img class="project-icon" src="$(IMGROOT)/icon-default.jpg" alt="Default Icon" />
17 
+      <div class="name">Torbrowser</div>
18 
+      <div class="caps">By Author</div>
19 
+      <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
20 
+    </div>
21 
+    <div class="featured-project focus left">
22 
+			<img class="project-icon" src="$(IMGROOT)/icon-default.jpg" alt="Default Icon" />
23 
+      <div class="name">Torbutton</div>
24 
+      <div class="caps">By Author</div>
25 
+      <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/torbutton>">Learn more &raquo;</a></p>
26 
+    </div>
27 
+    <table class="topforty">
28 
+    	<tr>
29 
+        <td class="beige">
30 
+          <div class="name">Tordnsel</div>
31 
+          <div class="caps">By Author</div>
32 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/tordnsel>">Learn more &raquo;</a></p>
33 
+        </td>
34 
+        <td>
35 
+          <div class="name">Vidalia</div>
36 
+          <div class="caps">By Author</div>
37 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="<page projects/vidalia>">Learn more &raquo;</a></p>
38 
+        </td>
39 
+        <td class="beige">
40 
+          <div class="name">Project Name</div>
41 
+          <div class="caps">By Author</div>
42 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
43 
+        </td>
44 
+      </tr>
45 
+      <tr>
46 
+        <td>
47 
+          <div class="name">Project Name</div>
48 
+          <div class="caps">By Author</div>
49 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
50 
+        </td>
51 
+        <td class="beige">
52 
+          <div class="name">Project Name</div>
53 
+          <div class="caps">By Author</div>
54 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
55 
+        </td>
56 
+        <td>
57 
+          <div class="name">Project Name</div>
58 
+          <div class="caps">By Author</div>
59 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
60 
+        </td>
61 
+      </tr>
62 
+      <tr>
63 
+        <td class="beige">
64 
+          <div class="name">Project Name</div>
65 
+          <div class="caps">By Author</div>
66 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
67 
+        </td>
68 
+        <td>
69 
+          <div class="name">Project Name</div>
70 
+          <div class="caps">By Author</div>
71 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
72 
+        </td>
73 
+        <td class="beige">
74 
+          <div class="name">Project Name</div>
75 
+          <div class="caps">By Author</div>
76 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
77 
+        </td>
78 
+      </tr>
79 
+      <tr>
80 
+        <td>
81 
+          <div class="name">Project Name</div>
82 
+          <div class="caps">By Author</div>
83 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
84 
+        </td>
85 
+        <td class="beige">
86 
+          <div class="name">Project Name</div>
87 
+          <div class="caps">By Author</div>
88 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
89 
+        </td>
90 
+        <td>
91 
+          <div class="name">Project Name</div>
92 
+          <div class="caps">By Author</div>
93 
+          <p>Lorem ipsum dolor sit amet, consectetur adipiscing elit. Integer semper justo mattis. <a href="#">Learn more &raquo;</a></p>
94 
+        </td>
95 
+      </tr>
96 
+    </table>
97 
+    <!-- END TABLE -->
98 
+  </div>
99 
+  <!-- END MAINCOL -->
100 
+  <div id = "sidecol">
101 
+#include "side.wmi"
102 
+#include "info.wmi"
103 
+  </div>
104 
+  <!-- END SIDECOL -->
105 
+</div>
106 
+<!-- END CONTENT -->
107 
+#include <foot.wmi>
projects/en/sidenav.wmi
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,90 @@
1 
+#!/usr/bin/wml
2 
+
3 
+## translation metadata
4 
+# Revision: $Revision: 0 $
5 
+# Translation-Priority: 2-medium
6 
+
7 
+# this structure defines the side nav bar for the /about pages
8 
+# and is the input for include/side.wmi
9 
+
10 
+# fields:
11 
+#
12 
+# name - the $WML_SRC_BASENAME of the file. It should uniquely identify the
13 
+# page because at build-time it is used to determine what view of the
14 
+# navigation menu to generate
15 
+#
16 
+# url - the path to the wml page, as used the the <page> tag. This tag ensures
17 
+# that links will point to the current language if supported, and alternately
18 
+# the english version
19 
+#
20 
+# txt - the link text to be displayed. Different translations will
21 
+# need to supply alternate txt
22 
+
23 
+<:
24 
+  my $sidenav;
25 
+  $sidenav = [
26 
+      {'url'  => 'projects/clientside',
27 
+       'txt'  => 'Client-side Projects',
28 
+       'subelements' => [
29 
+          {'url'  => 'projects/torbutton',
30 
+           'txt'  => 'TorButton',
31 
+           'subelements' => [
32 
+              {'url' => 'projects/torbutton-options',
33 
+               'txt' => 'TorButton Options',
34 
+              },
35 
+              {'url' => 'projects/torbutton-faq',
36 
+               'txt' => 'TorButton FAQ',
37 
+              },
38 
+          ]},
39 
+          {'url'  => 'http://check.torproject.org',
40 
+           'txt'  => 'TorCheck',
41 
+          },
42 
+          {'url'  => 'projects/sampleproject',
43 
+           'txt'  => 'SampleProject',
44 
+          }],
45 
+#          {'url'  => 'projects/sampleproject',
46 
+#           'txt'  => 'TorWeather',
47 
+#          },
48 
+#          {'url'  => 'projects/sampleproject',
49 
+#           'txt'  => 'TorWall',
50 
+#          },
51 
+#          {'url'  => 'projects/sampleproject',
52 
+#           'txt'  => 'PuppeTor',
53 
+#          },
54 
+#          {'url'  => 'projects/sampleproject',
55 
+#           'txt'  => 'TorDNSEL',
56 
+#          },
57 
+#          {'url'  => 'projects/sampleproject',
58 
+#           'txt'  => 'Pootle',
59 
+#          },
60 
+#          {'url'  => 'projects/sampleproject',
61 
+#           'txt'  => 'LNET',
62 
+#          },
63 
+#          {'url'  => 'projects/sampleproject',
64 
+#           'txt'  => 'TorStatus',
65 
+#          },
66 
+#          {'url'  => 'projects/sampleproject',
67 
+#           'txt'  => 'BridgeDB',
68 
+#          },
69 
+#          {'url'  => 'projects/sampleproject',
70 
+#           'txt'  => 'TorPerf',
71 
+#          },
72 
+#          {'url'  => 'projects/sampleproject',
73 
+#           'txt'  => 'BWAuthority',
74 
+#          },
75 
+#          {'url'  => 'projects/sampleproject',
76 
+#           'txt'  => 'TBB Builds',
77 
+#          }],
78 
+      },
79 
+      {'url'  => 'projects/serverside',
80 
+       'txt'  => 'Server-side Projects',
81 
+       'subelements' => [
82 
+          {'url'  => 'http://metrics.torproject.org',
83 
+           'txt'  => 'http://metrics.torproject.org',
84 
+          }],
85 
+       #   {'url'  => '',
86 
+       #    'txt'  => '',
87 
+       #   }],
88 
+      },
89 
+  ];
90 
+:>
projects/en/torbrowser-details.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,50 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Browser Bundle: Details" CHARSET="UTF-8"
6 
+
7 
+<div id="content" class="clearfix">
8 
+	<div id="breadcrumbs">
9 
+    <a href="<page home>">Home &raquo; </a>
10 
+    <a href="<page projects/projects>">Projects &raquo; </a>
11 
+    <a href="<page projects/torbrowser>">TorBrowser</a>
12 
+  </div>
13 
+	<div id="maincol">
14 
+
15 
+    <!-- PUT CONTENT AFTER THIS TAG -->
16 
+
17 
+    <h2>Tor Browser Bundle: Details</h2>
18 
+    <hr>
19 
+
20 
+    <h3 id="contents">Bundle contents</h3>
21 
+
22 
+    <ul>
23 
+    <li>Vidalia <version-torbrowser-vidalia></li>
24 
+    <li>Tor <version-torbrowser-tor> (with <version-torbrowser-tor-components>)</li>
25 
+    <li>FirefoxPortable <version-torbrowser-firefox> (includes Firefox
26 
+    <version-torbrowser-firefox> and Torbutton <version-torbrowser-torbutton>)</li>
27 
+    <li>Polipo <version-torbrowser-polipo></li>
28 
+    <li>Pidgin <version-torbrowser-pidgin> and OTR <version-torbrowser-otr> (only in Tor IM Browser Bundle)</li>
29 
+    </ul>
30 
+
31 
+    <h3 id="build">Building the bundle</h3>
32 
+
33 
+    <p>To re-build the bundle, download the <a
34 
+    href="dist/tor-browser-<version-torbrowserbundle>-src.tar.gz">source
35 
+    distribution</a> (<a
36 
+    href="dist/tor-browser-<version-torbrowserbundle>-src.tar.gz.asc">signature</a>).
37 
+    See <a
38 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/README">README</a> for
39 
+    the directory layout and changelog. Build instructions can be found in <a
40 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/INSTALL">build-scripts/INSTALL</a>.</p>
41 
+  </div>
42 
+  <!-- END MAINCOL -->
43 
+  <div id = "sidecol">
44 
+#include "side.wmi"
45 
+#include "info.wmi"
46 
+  </div>
47 
+  <!-- END SIDECOL -->
48 
+</div>
49 
+<!-- END CONTENT -->
50 
+#include <foot.wmi>
projects/en/torbrowser-split.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,127 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22082 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Browser Bundle (split edition)" CHARSET="UTF-8"
6 
+
7 
+<div id="content" class="clearfix">
8 
+	<div id="breadcrumbs">
9 
+    <a href="<page home>">Home &raquo; </a>
10 
+    <a href="<page projects/projects>">Projects &raquo; </a>
11 
+    <a href="<page projects/torbrowser>">TorBrowser &raquo; </a>
12 
+    <a href="<page projects/torbrowser>">TorBrowser-Split</a>
13 
+  </div>
14 
+	<div id="maincol">
15 
+
16 
+    <!-- PUT CONTENT AFTER THIS TAG -->
17 
+
18 
+    <h2>Tor Browser Bundle (split edition)</h2>
19 
+    <hr>
20 
+
21 
+    <h3><a class="anchor" href="#Download">Download Tor Browser Bundle and Tor IM Browser Bundle</a></h3>
22 
+
23 
+    <p>If you have a reliable Internet connection, you can download the <a href="<page projects/torbrowser>">single-file edition</a> of Tor Browser Bundle. Alternatively, follow the instructions on this page to download and install the split-file edition.</p>
24 
+
25 
+    <p>Choose the language you would like, and whether you also need the
26 
+    Pidgin instant messaging client, then click on the link corresponding to
27 
+    your choice. Download all the files shown in the folder (the single file
28 
+    ending in <code>.exe</code> and all the files ending in
29 
+    <code>.rar</code>). The files in <code>signatures</code> allow you to
30 
+    check that you've downloaded the file we intended you to get. See our
31 
+    instructions on <a href="<page docs/verifying-signatures>">how to verify
32 
+    package signatures</a>.</p>
33 
+
34 
+    <p id="Download-torbrowserbundle" style="font-size: 120%; margin: 5mm">Tor Browser Bundle for Windows with Firefox (version <version-torbrowserbundle>, split edition, 15 MB total)</p>
35 
+
36 
+    <ul>
37 
+
38 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_en-US_split">English (en-US)</a></li>
39 
+
40 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_ar_split">&#x0627;&#x0644;&#x0639;&#x0631;&#x0628;&#x064a;&#x0629; (ar)</a></li>
41 
+
42 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_de_split">Deutsch (de)</a></li>
43 
+
44 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_es-ES_split">&#x0045;&#x0073;&#x0070;&#x0061;&#x00f1;&#x006f;&#x006c; (es-ES)</a></li>
45 
+
46 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_fa_split">&#x0641;&#x0627;&#x0631;&#x0633;&#x06cc; (fa)</a></li>
47 
+
48 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_fr_split">&#x0046;&#x0072;&#x0061;&#x006e;&#x00e7;&#x0061;&#x0069;&#x0073; (fr)</a></li>
49 
+
50 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_it_split">Italiano (it)</a></li>
51 
+
52 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_nl_split">Nederlands (nl)</a></li>
53 
+
54 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_pt-PT_split">&#x0050;&#x006f;&#x0072;&#x0074;&#x0075;&#x0067;&#x0075;&#x00ea;&#x0073; (pt-PT)</a></li>
55 
+
56 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_ru_split">&#x0420;&#x0443;&#x0441;&#x0441;&#x043a;&#x0438;&#x0439; (ru)</a></li>
57 
+
58 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_zh-CN_split">&#x7b80;&#x4f53;&#x5b57; (zh-CN)</a></li>
59 
+
60 
+    </ul>
61 
+
62 
+    <p id="Download-torimbrowserbundle" style="font-size: 120%; margin: 5mm">Tor IM Browser Bundle for Windows with Firefox and Pidgin (version <version-torimbrowserbundle>, split edition, 24 MB total)</p>
63 
+
64 
+    <ul>
65 
+
66 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_en-US_split">English (en-US)</a></li>
67 
+
68 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_ar_split">&#x0627;&#x0644;&#x0639;&#x0631;&#x0628;&#x064a;&#x0629; (ar)</a></li>
69 
+
70 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_de_split">Deutsch (de)</a></li>
71 
+
72 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_es-ES_split">&#x0045;&#x0073;&#x0070;&#x0061;&#x00f1;&#x006f;&#x006c; (es-ES)</a></li>
73 
+
74 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_fa_split">&#x0641;&#x0627;&#x0631;&#x0633;&#x06cc; (fa)</a></li>
75 
+
76 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_fr_split">&#x0046;&#x0072;&#x0061;&#x006e;&#x00e7;&#x0061;&#x0069;&#x0073; (fr)</a></li>
77 
+
78 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_it_split">Italiano (it)</a></li>
79 
+
80 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_nl_split">Nederlands (nl)</a></li>
81 
+
82 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_pt-PT_split">&#x0050;&#x006f;&#x0072;&#x0074;&#x0075;&#x0067;&#x0075;&#x00ea;&#x0073; (pt-PT)</a></li>
83 
+
84 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_ru_split">&#x0420;&#x0443;&#x0441;&#x0441;&#x043a;&#x0438;&#x0439; (ru)</a></li>
85 
+
86 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_zh-CN_split">&#x7b80;&#x4f53;&#x5b57; (zh-CN)</a></li>
87 
+
88 
+    </ul>
89 
+
90 
+
91 
+    <p>Note that the Firefox in our bundle is <a
92 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/">modified</a>
93 
+    from the <a href="http://www.mozilla.com/firefox/">default Firefox</a>;
94 
+    we're currently working with Mozilla to see if they want
95 
+    us to change the name to make this clearer.
96 
+    </p>
97 
+
98 
+    <a id="Extraction"></a>
99 
+    <h3><a class="anchor" href="#Extraction">Extraction</a></h3>
100 
+
101 
+    <p>After you have downloaded all the files above, double click on the file with the icon of a box (1).</p>
102 
+
103 
+    <p><img src="img/split-screenshot1.png" alt="Screenshot of starting extraction process" /></p>
104 
+
105 
+    <p>Click on the button labelled <strong>Browse...</strong> (2) and select where you want
106 
+    to save the bundle then click <strong>OK</strong> (3). At least 50&nbsp;MB free
107 
+    space must be available in the location you select. If you want to leave the
108 
+    bundle on the computer, saving it to the Desktop is a good choice. If you want
109 
+    to move it to a different computer or limit the traces you leave behind, save
110 
+    it to a USB disk.</p>
111 
+
112 
+    <p>Click <strong>Install</strong> (4) to begin extraction. This may take a
113 
+    few minutes to complete.</p>
114 
+
115 
+    <p><img src="img/split-screenshot2.png" alt="Screenshot of extraction process" /></p>
116 
+
117 
+    <p>Once the extraction has completed, see the <a href="<page projects/torbrowser>#Usage">usage instructions</a> for how to start Tor.</p>
118 
+  </div>
119 
+  <!-- END MAINCOL -->
120 
+  <div id = "sidecol">
121 
+#include "side.wmi"
122 
+#include "info.wmi"
123 
+  </div>
124 
+  <!-- END SIDECOL -->
125 
+</div>
126 
+<!-- END CONTENT -->
127 
+#include <foot.wmi>
projects/en/torbrowser.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,272 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22450 $
3 
+# Translation-Priority: 1-high
4 
+
5 
+#include "head.wmi" TITLE="Tor Browser Bundle" CHARSET="UTF-8"
6 
+
7 
+<div id="content" class="clearfix">
8 
+	<div id="breadcrumbs">
9 
+    <a href="<page home>">Home &raquo; </a>
10 
+    <a href="<page projects/projects>">Projects &raquo; </a>
11 
+    <a href="<page projects/torbrowser>">TorBrowser</a>
12 
+  </div>
13 
+	<div id="maincol">
14 
+
15 
+    <!-- PUT CONTENT AFTER THIS TAG -->
16 
+
17 
+    <h2>Tor Browser Bundle</h2>
18 
+    <hr/>
19 
+
20 
+    <p>The <strong>Tor</strong> software protects you by bouncing
21 
+    your communications around a distributed network of relays run by volunteers
22 
+    all around the world: it prevents somebody watching your Internet connection
23 
+    from learning what sites you visit, it prevents the sites you visit from
24 
+    learning your physical location, and it lets you access sites which are
25 
+    blocked.</p>
26 
+
27 
+    <p>The <strong>Tor Browser Bundle</strong> lets you use Tor on Windows
28 
+    or Linux without needing to
29 
+    install any software.  It can run off a USB flash drive, comes with a
30 
+    pre-configured web browser and is self-contained.
31 
+
32 
+    The <strong>Tor IM Browser Bundle</strong> additionally allows instant
33 
+    messaging and chat over Tor.
34 
+
35 
+    If you would prefer to use your existing web browser, install Tor
36 
+    permanently, or if you don't use Windows, see the other ways to <a
37 
+    href="<page download/download>">download Tor</a>.</p>
38 
+
39 
+    <p>Freedom House has produced a video on how to find and use the Tor
40 
+    Browser Bundle.  If you don't see a video below, view it at <a
41 
+    href="http://www.youtube.com/thetorproject">Youtube
42 
+    </a>.  Know of a better video or one translated into your
43 
+    language?  Let us know!</p>
44 
+
45 
+    <div class="center">
46 
+    <p><video id="v1" src="http://media.torproject.org/video/2009-install-and-use-tor-browser-bundle.ogv" autobuffer="true" controls="controls"></video></p>
47 
+    </div>
48 
+
49 
+    <a id="Download"></a>
50 
+    <h3><a class="anchor" href="#Download">Download Tor Browser Bundle and Tor IM Browser Bundle</a></h3>
51 
+
52 
+    <p>To start using the Tor Browser Bundle or Tor IM Browser Bundle, download the file for your preferred
53 
+    language. This file can be saved wherever is convenient, e.g. the Desktop or a
54 
+    USB flash drive.</p>
55 
+
56 
+    <p>If you have an unreliable Internet connection, it may be easier for you to download the bundle edition which is <a href="<page projects/torbrowser-split>">split up</a> into smaller parts.</p>
57 
+
58 
+    <p id="Download-torbrowserbundle" style="font-size: 120%; margin: 5mm">Tor Browser Bundle for Windows with Firefox (version <version-torbrowserbundle>, 16 MB)</p>
59 
+
60 
+    <ul>
61 
+
62 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_en-US.exe">English (en-US)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_en-US.exe.asc" style="font-size: 90%;">signature</a>)</li>
63 
+
64 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_ar.exe">&#x0627;&#x0644;&#x0639;&#x0631;&#x0628;&#x064a;&#x0629; (ar)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_ar.exe.asc" style="font-size: 90%;">signature</a>)</li>
65 
+
66 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_de.exe">Deutsch (de)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_de.exe.asc" style="font-size: 90%;">signature</a>)</li>
67 
+
68 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_es-ES.exe">&#x0045;&#x0073;&#x0070;&#x0061;&#x00f1;&#x006f;&#x006c; (es-ES)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_es-ES.exe.asc" style="font-size: 90%;">signature</a>)</li>
69 
+
70 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_fa.exe">&#x0641;&#x0627;&#x0631;&#x0633;&#x06cc; (fa)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_fa.exe.asc" style="font-size: 90%;">signature</a>)</li>
71 
+
72 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_fr.exe">&#x0046;&#x0072;&#x0061;&#x006e;&#x00e7;&#x0061;&#x0069;&#x0073; (fr)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_fr.exe.asc" style="font-size: 90%;">signature</a>)</li>
73 
+
74 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_it.exe">Italiano (it)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_it.exe.asc" style="font-size: 90%;">signature</a>)</li>
75 
+
76 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_nl.exe">Nederlands (nl)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_nl.exe.asc" style="font-size: 90%;">signature</a>)</li>
77 
+
78 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_pl.exe">Polish (pl)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_pl.exe.asc" style="font-size: 90%;">signature</a>)</li>
79 
+
80 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_pt-PT.exe">&#x0050;&#x006f;&#x0072;&#x0074;&#x0075;&#x0067;&#x0075;&#x00ea;&#x0073; (pt-PT)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_pt-PT.exe.asc" style="font-size: 90%;">signature</a>)</li>
81 
+
82 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_ru.exe">&#x0420;&#x0443;&#x0441;&#x0441;&#x043a;&#x0438;&#x0439; (ru)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_ru.exe.asc" style="font-size: 90%;">signature</a>)</li>
83 
+
84 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_vi.exe">Vietnamese (vi)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_vi.exe.asc" style="font-size: 90%;">signature</a>)</li>
85 
+
86 
+    <li><a href="dist/tor-browser-<version-torbrowserbundle>_zh-CN.exe">&#x7b80;&#x4f53;&#x5b57; (zh-CN)</a> (<a href="dist/tor-browser-<version-torbrowserbundle>_zh-CN.exe.asc" style="font-size: 90%;">signature</a>)</li>
87 
+
88 
+    </ul>
89 
+
90 
+    <p id="Download-torimbrowserbundle" style="font-size: 120%; margin: 5mm">Tor IM Browser Bundle for Windows with Firefox and Pidgin (version <version-torimbrowserbundle>, 25 MB)</p>
91 
+
92 
+    <ul>
93 
+
94 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_en-US.exe">English (en-US)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_en-US.exe.asc" style="font-size: 90%;">signature</a>)</li>
95 
+
96 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_ar.exe">&#x0627;&#x0644;&#x0639;&#x0631;&#x0628;&#x064a;&#x0629; (ar)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_ar.exe.asc" style="font-size: 90%;">signature</a>)</li>
97 
+
98 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_de.exe">Deutsch (de)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_de.exe.asc" style="font-size: 90%;">signature</a>)</li>
99 
+
100 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_es-ES.exe">&#x0045;&#x0073;&#x0070;&#x0061;&#x00f1;&#x006f;&#x006c; (es-ES)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_es-ES.exe.asc" style="font-size: 90%;">signature</a>)</li>
101 
+
102 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_fa.exe">&#x0641;&#x0627;&#x0631;&#x0633;&#x06cc; (fa)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_fa.exe.asc" style="font-size: 90%;">signature</a>)</li>
103 
+
104 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_fr.exe">&#x0046;&#x0072;&#x0061;&#x006e;&#x00e7;&#x0061;&#x0069;&#x0073; (fr)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_fr.exe.asc" style="font-size: 90%;">signature</a>)</li>
105 
+
106 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_it.exe">Italiano (it)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_it.exe.asc" style="font-size: 90%;">signature</a>)</li>
107 
+
108 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_nl.exe">Nederlands (nl)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_nl.exe.asc" style="font-size: 90%;">signature</a>)</li>
109 
+
110 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_pl.exe">Polish (pl)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_pl.exe.asc" style="font-size: 90%;">signature</a>)</li>
111 
+
112 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_pt-PT.exe">&#x0050;&#x006f;&#x0072;&#x0074;&#x0075;&#x0067;&#x0075;&#x00ea;&#x0073; (pt-PT)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_pt-PT.exe.asc" style="font-size: 90%;">signature</a>)</li>
113 
+
114 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_ru.exe">&#x0420;&#x0443;&#x0441;&#x0441;&#x043a;&#x0438;&#x0439; (ru)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_ru.exe.asc" style="font-size: 90%;">signature</a>)</li>
115 
+
116 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_vi.exe">Vietnamese (vi)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_vi.exe.asc" style="font-size: 90%;">signature</a>)</li>
117 
+
118 
+    <li><a href="dist/tor-im-browser-<version-torimbrowserbundle>_zh-CN.exe">&#x7b80;&#x4f53;&#x5b57; (zh-CN)</a> (<a href="dist/tor-im-browser-<version-torimbrowserbundle>_zh-CN.exe.asc" style="font-size: 90%;">signature</a>)</li>
119 
+
120 
+    </ul>
121 
+
122 
+    <p id="Download-torbrowserbundlelinux" style="font-size: 120%; margin: 5mm">BETA: Tor Browser Bundle for Linux with Firefox (version <version-torbrowserbundlelinux>, 22 MB)</p>
123 
+
124 
+    <ul>
125 
+    <li>English (en-US): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-en-US.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-en-US.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-en-US.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-en-US.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
126 
+
127 
+    <li>&#x0627;&#x0644;&#x0639;&#x0631;&#x0628;&#x064a;&#x0629; (ar): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-ar.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-ar.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-ar.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-ar.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
128 
+
129 
+    <li>Deutsch (de): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-de.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-de.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-de.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-de.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
130 
+
131 
+    <li>&#x0045;&#x0073;&#x0070;&#x0061;&#x00f1;&#x006f;&#x006c; (es-ES): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-es-ES.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-es-ES.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-es-ES.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-es-ES.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
132 
+
133 
+    <li>&#x0641;&#x0627;&#x0631;&#x0633;&#x06cc; (fa): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-fa.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-fa.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-fa.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-fa.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
134 
+
135 
+    <li>&#x0046;&#x0072;&#x0061;&#x006e;&#x00e7;&#x0061;&#x0069;&#x0073; (fr): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-fr.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-fr.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-fr.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-fr.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
136 
+
137 
+    <li>Italiano (it): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-it.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-it.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-it.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-it.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
138 
+
139 
+    <li>Nederlands (nl): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-nl.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-nl.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-nl.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-nl.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
140 
+
141 
+    <li>Polish (pl): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-pl.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-pl.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-pl.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-pl.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
142 
+
143 
+    <li>&#x0050;&#x006f;&#x0072;&#x0074;&#x0075;&#x0067;&#x0075;&#x00ea;&#x0073; (pt-PT): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-pt-PT.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-pt-PT.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-pt-PT.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-pt-PT.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
144 
+
145 
+    <li>&#x0420;&#x0443;&#x0441;&#x0441;&#x043a;&#x0438;&#x0439; (ru): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-ru.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-ru.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-ru.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-ru.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
146 
+
147 
+    <li>&#x7b80;&#x4f53;&#x5b57; (zh-CN): <a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-zh-CN.tar.gz">i386</a> (<a href="dist/linux/tor-browser-gnu-linux-i686-<version-torbrowserbundlelinux>-dev-zh-CN.tar.gz.asc" style="font-size: 90%;">sig</a>) | <a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-zh-CN.tar.gz">x86_64</a> (<a href="dist/linux/tor-browser-gnu-linux-x86_64-<version-torbrowserbundlelinux>-dev-zh-CN.tar.gz.asc" style="font-size: 90%;">sig</a>)</li>
148 
+
149 
+    </ul>
150 
+
151 
+
152 
+
153 
+    <p>See our instructions on <a href="<page docs/verifying-signatures>">how
154 
+    to verify package signatures</a>, which allows you to make sure you've
155 
+    downloaded the file we intended you to get.
156 
+    Also, note that the Firefox in our bundles is <a
157 
+    href="https://svn.torproject.org/svn/torbrowser/trunk/build-scripts/config/">modified</a>
158 
+    from the <a href="http://www.mozilla.com/firefox/">default Firefox</a>;
159 
+    we're currently working with Mozilla to see if they want
160 
+    us to change the name to make this clearer.
161 
+    </p>
162 
+
163 
+    <a id="Linux"></a>
164 
+    <h3><a class="anchor" href="#Linux">Linux instructions</a></h3>
165 
+    <p>Download the architecture-appropriate file above, save it somewhere, then
166 
+    run:<br /> tar -xvzf
167 
+    tor-browser-gnu-linux-<version-torbrowserbundlelinux>-dev-LANG.tar.gz (where
168 
+    LANG is the language listed in the filename), and either double click on the
169 
+    directory or cd into it, then execute the <strong>start-tor-browser</strong>
170 
+    script. This will launch Vidalia and once that connects to Tor, it will launch
171 
+    Firefox.</p>
172 
+
173 
+    <a id="Extraction"></a>
174 
+    <h3><a class="anchor" href="#Extraction">Extraction</a></h3>
175 
+
176 
+    <p>Download the file above, and save it somewhere, then double click on it.
177 
+    Click on the button labelled <strong>"..."</strong> (1) and select where you want
178 
+    to save the bundle then click <strong>OK</strong> (2). At least 50&nbsp;MB free
179 
+    space must be available in the location you select. If you want to leave the
180 
+    bundle on the computer, saving it to the Desktop is a good choice. If you want
181 
+    to move it to a different computer or limit the traces you leave behind, save
182 
+    it to a USB disk.</p>
183 
+
184 
+    <p>Click <strong>Extract</strong> (3) to begin extraction. This may take a
185 
+    few minutes to complete.</p>
186 
+
187 
+    <p><img src="img/screenshot1.png" alt="Screenshot of extraction process" /></p>
188 
+
189 
+    <a id="Usage"></a>
190 
+    <h3><a class="anchor" href="#Usage">Usage</a></h3>
191 
+
192 
+    <p>Once extraction is complete, open the folder <strong>Tor Browser</strong> from the location you saved the bundle.</p>
193 
+
194 
+    <p>Double click on the <strong>Start Tor Browser</strong> (4) application (it may be called
195 
+    <strong>Start Tor Browser.exe</strong> on some systems.)</p>
196 
+
197 
+    <p>The Vidalia window will shortly appear.</p>
198 
+
199 
+    <p><img src="img/screenshot2.png" alt="Screenshot of bundle startup" /></p>
200 
+
201 
+    <p>Once Tor is ready, Firefox will automatically be opened. Only web pages
202 
+    visited through the included Firefox browser will be sent via Tor. Other web
203 
+    browsers such as Internet Explorer are not affected. Make sure that it says
204 
+    <span style="color: #0a0">"Tor Enabled"</span> (5) in the bottom right corner
205 
+    before using it. To reduce the risk of confusion, don't run Firefox while using
206 
+    the Tor Browser Bundle, and close existing Firefox windows before starting.</p>
207 
+
208 
+    <p>If you installed the Tor IM Browser Bundle, the Pidgin instant messaging client will also be automatically opened.</p>
209 
+
210 
+    <p>Once you are finished browsing, close any open Firefox windows by clicking
211 
+    on the <img src="img/close-button.png" alt="Close button (&times;)" /> (6).
212 
+    For privacy reasons, the list of
213 
+    webpages you visited and any cookies will be deleted.</p>
214 
+
215 
+    <p><img src="img/screenshot3a.png" alt="Screenshot of Firefox" /></p>
216 
+
217 
+    <p>With the Tor Browser Bundle, Vidalia and Tor will automatically close. With the Tor IM Browser Bundle you need to also close Pidgin by right-clicking on the Pidgin icon (7), and choosing Quit (8).</p>
218 
+
219 
+    <p><img src="img/screenshot3b.png" alt="Screenshot of Pidgin" /></p>
220 
+
221 
+    <p>To use the Tor Browser Bundle or Tor IM Browser Bundle again, repeat the steps in <a href="#Usage">"Usage"</a>.</p>
222 
+
223 
+    <p>Remember that Tor anonymizes the origin of your traffic, and it
224 
+    encrypts everything inside the Tor network, but <a
225 
+    href="https://wiki.torproject.org/noreply/TheOnionRouter/TorFAQ#ExitEavesdroppers">it
226 
+    can't encrypt your traffic between the Tor network and its final
227 
+    destination.</a> If you are communicating sensitive information, you
228 
+    should use as much care as you would on the normal scary Internet &mdash;
229 
+    use HTTPS or other end-to-end encryption and authentication.
230 
+    </p>
231 
+
232 
+    <a id="Feedback"></a>
233 
+    <h3><a class="anchor" href="#Feedback">Comments and suggestions</a></h3>
234 
+
235 
+    <p>The Tor Browser Bundle is under development and not yet complete.
236 
+    To discuss improvements and submit comments, please use the <a
237 
+    href="http://archives.seul.org/or/talk/">or-talk</a> mailing list.</p>
238 
+
239 
+    <a id="More"></a>
240 
+    <h3><a class="anchor" href="#More">More information</a></h3>
241 
+
242 
+    <p><strong>What is Tor and why do I need it?</strong> To learn more about Tor, visit the <a
243 
+    href="<page home>">Tor Project
244 
+    website</a>.</p>
245 
+
246 
+    <p><strong>What is in the Tor Browser Bundle?</strong> It
247 
+    contains Tor, Vidalia, Polipo, Firefox, and Torbutton (<a
248 
+    href="<page projects/torbrowser-details>#contents">learn more</a>).</p>
249 
+
250 
+    <p><strong>What is in the Tor IM Browser Bundle?</strong> It
251 
+    contains Tor, Vidalia, Polipo, Firefox, Torbutton, Pidgin and OTR (<a
252 
+    href="<page projects/torbrowser-details>#contents">learn more</a>).</p>
253 
+
254 
+    <p><strong>How can I make my own bundle?</strong> To download
255 
+    the source code and learn how to build the bundle yourself, read the
256 
+    <a href="<page projects/torbrowser-details>#build">build instructions</a>.</p>
257 
+
258 
+    <p>Tor Browser Bundle is partially based on <a
259 
+    href="http://portableapps.com/apps/internet/firefox_portable">Mozilla
260 
+    Firefox, Portable Edition</a> and <a
261 
+    href="http://portableapps.com/apps/internet/pidgin_portable">Pidgin
262 
+    Portable</a> from <a href="http://portableapps.com/">PortableApps.com</a>.</p>
263 
+  </div>
264 
+  <!-- END MAINCOL -->
265 
+  <div id = "sidecol">
266 
+#include "side.wmi"
267 
+#include "info.wmi"
268 
+  </div>
269 
+  <!-- END SIDECOL -->
270 
+</div>
271 
+<!-- END CONTENT -->
272 
+#include <foot.wmi>
projects/en/torbutton-faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,356 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Projects Overview" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/torbutton>">TorButton &raquo; </a>
11 
+    <a href="<page projects/torbutton-faq>">TorButton FAQ</a>
12 
+  </div>
13 
+	<div id="maincol">
14 
+    <!-- PUT CONTENT AFTER THIS TAG -->
15 
+
16 
+    <h2>Torbutton FAQ</h2>
17 
+    <hr />
18 
+
19 
+    <h3>Questions</h3>
20 
+    <br />
21 
+    <ul>
22 
+    <li><a href="<page projects/torbutton-faq>#nojavascript">When I toggle Tor, my sites that use javascript stop working. Why?</a></li>
23 
+    <li><a href="<page projects/torbutton-faq>#noreloads">I can't click on links or hit reload after I toggle Tor! Why?</a></li>
24 
+    <li><a href="<page projects/torbutton-faq>#noflash">I can't view videos on YouTube and other flash-based sites. Why?</a></li>
25 
+    <li><a href="<page projects/torbutton-faq>#oldtorbutton">Torbutton sure seems to do a lot of things, some of which I find annoying. Can't I just use the old version?</a></li>
26 
+    <li><a href="<page projects/torbutton-faq>#weirdstate">My browser is in some weird state where nothing works right!</a></li>
27 
+    <li><a href="<page projects/torbutton-faq>#noautocomplete">When I use Tor, Firefox is no longer filling in logins/search boxes for me. Why?</a></li>
28 
+    <li><a href="<page projects/torbutton-faq>#thunderbird">What about Thunderbird support? I see a page, but it is the wrong version?</a></li>
29 
+    <li><a href="<page projects/torbutton-faq>#extensionconflicts">Which Firefox extensions should I avoid using?</a></li>
30 
+    <li><a href="<page projects/torbutton-faq>#recommendedextensions">Which Firefox extensions do you recommend?</a></li>
31 
+    <li><a href="<page projects/torbutton-faq>#securityissues">Are there any other issues I should be concerned about?</a></li>
32 
+    </ul>
33 
+    <br />
34 
+
35 
+    <a id="nojavascript"></a>
36 
+    <strong><a class="anchor" href="#nojavascript">When I toggle Tor, my sites that use javascript stop working. Why?</a></strong>
37 
+
38 
+    <p>
39 
+    Javascript can do things like wait until you have disabled Tor before trying
40 
+    to contact its source site, thus revealing your IP address. As such, Torbutton
41 
+    must disable Javascript, Meta-Refresh tags, and certain CSS behavior when Tor
42 
+    state changes from the state that was used to load a given page. These features
43 
+    are re-enabled when Torbutton goes back into the state that was used to load
44 
+    the page, but in some cases (particularly with Javascript and CSS) it is
45 
+    sometimes not possible to fully recover from the resulting errors, and the
46 
+    page is broken. Unfortunately, the only thing you can do (and still remain
47 
+    safe from having your IP address leak) is to reload the page when you toggle
48 
+    Tor, or just ensure you do all your work in a page before switching tor state.
49 
+    </p>
50 
+
51 
+    <a id="noreloads"></a>
52 
+    <strong><a class="anchor" href="#noreloads">I can't click on links or hit reload after I toggle Tor! Why?</a></strong>
53 
+
54 
+    <p>
55 
+    Due to <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=409737">Firefox
56 
+    Bug 409737</a>, pages can still open popups and perform Javascript redirects
57 
+    and history access after Tor has been toggled. These popups and redirects can
58 
+    be blocked, but unfortunately they are indistinguishable from normal user
59 
+    interactions with the page (such as clicking on links, opening them in new
60 
+    tabs/windows, or using the history buttons), and so those are blocked as a
61 
+    side effect. Once that Firefox bug is fixed, this degree of isolation will
62 
+    become optional (for people who do not want to accidentally click on links and
63 
+    give away information via referrers). A workaround is to right click on the
64 
+    link, and open it in a new tab or window. The tab or window won't load
65 
+    automatically, but you can hit enter in the URL bar, and it will begin
66 
+    loading. Hitting enter in the URL bar will also reload the page without
67 
+    clicking the reload button.
68 
+    </p>
69 
+
70 
+    <a id="noflash"></a>
71 
+    <strong><a class="anchor" href="#noflash">I can't view videos on YouTube and
72 
+    other Flash-based sites. Why?</a></strong>
73 
+
74 
+    <p>
75 
+
76 
+    YouTube and similar sites require third party browser plugins such as Flash.
77 
+    Plugins operate independently from Firefox and can perform
78 
+    activity on your computer that ruins your anonymity. This includes
79 
+    but is not limited to: <a href="http://decloak.net">completely disregarding
80 
+    proxy settings</a>, querying your <a
81 
+    href="http://forums.sun.com/thread.jspa?threadID=5162138&amp;messageID=9618376">local
82 
+    IP address</a>, and <a
83 
+    href="http://epic.org/privacy/cookies/flash.html">storing their own
84 
+    cookies</a>. It is possible to use a LiveCD or VMWare-based solution such as
85 
+    <a href="<page projects/torvm>">Tor VM</a> or <a
86 
+    href="https://amnesia.boum.org/">The (Amnesic) Incognito Live System</a> that creates a
87 
+    secure, transparent proxy to protect you from proxy bypass, however issues
88 
+    with local IP address discovery and Flash cookies still remain.  </p>
89 
+
90 
+    <p>
91 
+
92 
+    If you are not concerned about being tracked by these sites (and sites that
93 
+    try to unmask you by pretending to be them), and are unconcerned about your
94 
+    local censors potentially noticing you visit them, you can enable plugins by
95 
+    going into the Torbutton Preferences-&gt;Security Settings-&gt;Dynamic Content
96 
+    tab and unchecking "Disable plugins during Tor usage" box. If you do this
97 
+    without Tor VM, The (Amnesic) Incognito Live System or appropriate
98 
+    firewall rules, we strongly suggest you at least use <a
99 
+    href="https://addons.mozilla.org/en-US/firefox/addon/722">NoScript</a> to <a
100 
+    href="http://noscript.net/features#contentblocking">block plugins</a>. You do
101 
+    not need to use the NoScript per-domain permissions if you check the <b>Apply
102 
+    these restrictions to trusted sites too</b> option under the NoScript Plugins
103 
+    preference tab. In fact, with this setting you can even have NoScript allow
104 
+    Javascript globally, but still block all plugins until you click on their
105 
+    placeholders in a page. We also recommend <a
106 
+    href="https://addons.mozilla.org/en-US/firefox/addon/6623">Better Privacy</a>
107 
+    in this case to help you clear your Flash cookies.
108 
+
109 
+    </p>
110 
+
111 
+    <a id="oldtorbutton"></a>
112 
+    <strong><a class="anchor" href="#oldtorbutton">Torbutton sure seems to do a lot of things, some of which I find
113 
+    annoying. Can't I just use the old version?</a></strong>
114 
+
115 
+    <p>
116 
+
117 
+    <b>No.</b> Use of the old version, or any other vanilla proxy changer
118 
+    (including FoxyProxy -- see below) without Torbutton is actively discouraged.
119 
+    Seriously. Using a vanilla proxy switcher by itself is so insecure that you are
120 
+    not only just wasting your time, you are also actually endangering yourself.
121 
+    <b>Simply do not use Tor</b> and you will have the same (and in some cases,
122 
+    better) security.  For more information on the types of attacks you are exposed
123 
+    to with a "homegrown" solution, please see <a
124 
+    href="design/index.html#adversary">The Torbutton
125 
+    Adversary Model</a>, in particular the <a
126 
+    href="design/index.html#attacks">Adversary
127 
+    Capabilities - Attacks</a> subsection. If there are any specific Torbutton
128 
+    behaviors that you do not like, please file a bug on <a
129 
+    href="https://bugs.torproject.org/flyspray/index.php?tasks=all&amp;project=5">the
130 
+    bug tracker.</a> Most of Torbutton's security features can also be disabled via
131 
+    its preferences, if you think you have your own protection for those specific
132 
+    cases.
133 
+
134 
+    </p>
135 
+
136 
+    <a id="weirdstate"></a>
137 
+    <strong><a class="anchor" href="#weirdstate">My browser is in some weird state where nothing works right!</a></strong>
138 
+
139 
+    <p>
140 
+    Try to disable Tor by clicking on the button, and then open a new window. If
141 
+    that doesn't fix the issue, go to the preferences page and hit 'Restore
142 
+    Defaults'. This should reset the extension and Firefox to a known good
143 
+    configuration.  If you can manage to reproduce whatever issue gets your
144 
+    Firefox wedged, please file details at <a
145 
+    href="https://bugs.torproject.org/flyspray/index.php?tasks=all&amp;project=5">the
146 
+    bug tracker</a>.
147 
+    </p>
148 
+
149 
+    <a id="noautocomplete"></a>
150 
+    <strong><a class="anchor" href="#noautocomplete">When I use Tor, Firefox is no longer filling in logins/search boxes
151 
+    for me. Why?</a></strong>
152 
+
153 
+    <p>
154 
+    Currently, this is tied to the "<b>Block history writes during Tor</b>"
155 
+    setting. If you have enabled that setting, all formfill functionality (both
156 
+    saving and reading) is disabled. If this bothers you, you can uncheck that
157 
+    option, but both history and forms will be saved. To prevent history
158 
+    disclosure attacks via Non-Tor usage, it is recommended you disable Non-Tor
159 
+    history reads if you allow history writing during Tor.
160 
+    </p>
161 
+
162 
+    <a id="thunderbird"></a>
163 
+    <strong><a class="anchor" href="#thunderbird">What about Thunderbird support? I see a page, but it is the wrong
164 
+    version?</a></strong>
165 
+
166 
+    <p>
167 
+    Torbutton used to support basic proxy switching on Thunderbird back in the 1.0
168 
+    days, but that support has been removed because it has not been analyzed for
169 
+    security. My developer tools page on addons.mozilla.org clearly lists Firefox
170 
+    support only, so I don't know why they didn't delete that Thunderbird listing.
171 
+    I am not a Thunderbird user and unfortunately, I don't have time to analyze
172 
+    the security issues involved with toggling proxy settings in that app. It
173 
+    likely suffers from similar (but not identical) state and proxy leak issues
174 
+    with html mail, embedded images, javascript, plugins and automatic network
175 
+    access. My recommendation is to create a completely separate Thunderbird
176 
+    profile for your Tor accounts and use that instead of trying to toggle proxy
177 
+    settings. But if you really like to roll fast and loose with your IP, you
178 
+    could try another proxy switcher like ProxyButton, SwitchProxy or FoxyProxy
179 
+    (if any of those happen to support thunderbird).
180 
+    </p>
181 
+
182 
+    <a id="extensionconflicts"></a>
183 
+    <strong><a class="anchor" href="#extensionconflicts">Which Firefox extensions should I avoid using?</a></strong>
184 
+
185 
+    <p>
186 
+    This is a tough one. There are thousands of Firefox extensions: making a
187 
+    complete list of ones that are bad for anonymity is near impossible. However,
188 
+    here are a few examples that should get you started as to what sorts of
189 
+    behavior are dangerous.
190 
+    </p>
191 
+
192 
+    <ol>
193 
+     <li>StumbleUpon, et al
194 
+     <p>
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 
+     </p></li>
202 
+     <li>FoxyProxy
203 
+    <p>
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, with Torbutton installed in tandem
212 
+    and always enabled, it is possible to configure FoxyProxy securely (though it
213 
+    is tricky). Since FoxyProxy's 'Patterns' mode only applies to specific urls,
214 
+    and not to an entire tab, setting FoxyProxy to only send specific sites
215 
+    through Tor will still allow adservers (whose hosts don't match your filters) to learn your real IP. Worse, when
216 
+    sites use offsite logging services such as Google Analytics, you will
217 
+    still end up in their logs with your real IP. Malicious exit nodes can also
218 
+    cooperate with sites to inject images into pages that bypass your filters.
219 
+    Setting FoxyProxy to only send certain URLs via Non-Tor is much more secure in
220 
+    this regard, but be very careful with the filters you allow. For example,
221 
+    something as simple as allowing *google* to go via Non-Tor will still cause you to end up
222 
+    in all the logs of all websites that use Google Analytics!  See
223 
+    <a href="http://foxyproxy.mozdev.org/faq.html#privacy-01">this question</a> on
224 
+    the FoxyProxy FAQ for more information.
225 
+     </p></li>
226 
+    </ol>
227 
+
228 
+    <a id="recommendedextensions"></a>
229 
+    <strong><a class="anchor" href="#recommendedextensions">Which Firefox extensions do you recommend?</a></strong>
230 
+    <ol>
231 
+     <li><a href="https://addons.mozilla.org/firefox/addon/953">RefControl</a>
232 
+    	<p>
233 
+    Mentioned above, this extension allows more fine-grained referrer spoofing
234 
+    than Torbutton currently provides. It should break less sites than Torbutton's
235 
+    referrer spoofing option.</p></li>
236 
+
237 
+     <li><a href="https://addons.mozilla.org/firefox/addon/1474">SafeCache</a>
238 
+    <p>
239 
+    If you use Tor excessively, and rarely disable it, you probably want to
240 
+    install this extension to minimize the ability of sites to store long term
241 
+    identifiers in your cache. This extension applies same origin policy to the
242 
+    cache, so that elements are retrieved from the cache only if they are fetched
243 
+    from a document in the same origin domain as the cached element.
244 
+    </p></li>
245 
+
246 
+     <li><a href="https://addons.mozilla.org/en-US/firefox/addon/6623">Better
247 
+    Privacy</a>
248 
+     <p>
249 
+
250 
+    Better Privacy is an excellent extension that protects you from cookies used
251 
+    by Flash applications, which often persist forever and are not clearable via
252 
+    normal Firefox "Private Data" clearing. Flash and all other plugins are
253 
+    disabled by Torbutton by default, but if you are interested in privacy, you
254 
+    may want this extension to allow you to inspect and automatically clear your
255 
+    Flash cookies for your Non-Tor usage.
256 
+
257 
+     </p>
258 
+     </li>
259 
+     <li><a href="https://addons.mozilla.org/firefox/addon/1865">AdBlock Plus</a>
260 
+     <p>
261 
+
262 
+    AdBlock Plus is an excellent addon for removing annoying, privacy-invading,
263 
+    and <a
264 
+    href="http://www.wired.com/techbiz/media/news/2007/11/doubleclick">malware-distributing</a>
265 
+    advertisements from the web. It provides
266 
+    <a href="http://adblockplus.org/en/subscriptions">subscriptions</a> that are
267 
+    continually updated to catch the latest efforts of ad networks to circumvent
268 
+    these filters. I recommend the EasyPrivacy+EasyList combination filter
269 
+    subscription in the Miscellaneous section of the subscriptions page.
270 
+
271 
+     </p>
272 
+    </li>
273 
+    <li><a href="https://addons.mozilla.org/firefox/addon/82">Cookie Culler</a>
274 
+     <p>
275 
+
276 
+    Cookie Culler is a handy extension to give quick access to the cookie manager
277 
+    in Firefox. It also provides the ability to protect certain cookies from
278 
+    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.
279 
+
280 
+     </p>
281 
+     </li>
282 
+
283 
+     <li><a href="https://addons.mozilla.org/en-US/firefox/addon/722">NoScript</a>
284 
+     <p>
285 
+     Torbutton currently mitigates all known anonymity issues with Javascript.
286 
+     However, if you are concerned about Javascript exploits against your browser
287 
+     or against websites you are logged in to, you may want to use NoScript. It
288 
+     provides the ability to allow Javascript only for particular websites
289 
+     and also provides mechanisms to force HTTPS urls for sites with
290 
+    <a href="http://fscked.org/category/tags/insecurecookies">insecure
291 
+     cookies</a>.<br>
292 
+
293 
+     It can be difficult to configure such that the most sites will work
294 
+     properly though. In particular, you want to make sure you do not remove
295 
+     the Javascript whitelist for
296 
+     addons.mozilla.org, as extensions are downloaded via http and verified by
297 
+     javascript from the https page.
298 
+
299 
+     </p></li>
300 
+     <li><a href="https://addons.mozilla.org/en-US/firefox/addon/9727/">Request
301 
+    Policy</a>
302 
+     <p>
303 
+
304 
+    Request Policy is similar to NoScript in that it requires that you configure
305 
+    which sites are allowed to load content from other domains. It can be very
306 
+    difficult for novice users to configure properly, but it does provide a good
307 
+    deal of protection against ads, injected content, and cross-site request
308 
+    forgery attacks.
309 
+
310 
+     </p>
311 
+     </li>
312 
+
313 
+    </ol>
314 
+
315 
+    <a id="securityissues"></a>
316 
+    <strong><a class="anchor" href="#securityissues">Are there any other issues I should be concerned about?</a></strong>
317 
+
318 
+    <p>
319 
+    There are a few known security issues with Torbutton (all of which are due to
320 
+    <a href="design/index.html#FirefoxBugs">unfixed
321 
+    Firefox security bugs</a>). The most important for anonymity is that it is
322 
+    possible to unmask the javascript hooks that wrap the Date object to conceal
323 
+    your timezone in Firefox 2, and the timezone masking code does not work at all
324 
+    on Firefox 3. We are working with the Firefox team to fix one of <a
325 
+    href="https://bugzilla.mozilla.org/show_bug.cgi?id=392274">Bug 399274</a> or
326 
+    <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=419598">Bug 419598</a>
327 
+    to address this. In the meantime, it is possible to set the <b>TZ</b>
328 
+    environment variable to <b>UTC</b> to cause the browser to use UTC as your
329 
+    timezone. Under Linux, you can add an <b>export TZ=UTC</b> to the
330 
+    /usr/bin/firefox script, or edit your system bashrc to do the same. Under
331 
+    Windows, you can set either a <a
332 
+    href="http://support.microsoft.com/kb/310519">User or System Environment
333 
+    Variable</a> for TZ via My Computer's properties. In MacOS, the situation is
334 
+    <a
335 
+    href="http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/Articles/EnvironmentVars.html#//apple_ref/doc/uid/20002093-BCIJIJBH">a
336 
+    lot more complicated</a>, unfortunately.
337 
+    </p>
338 
+
339 
+    <p>
340 
+    In addition, RSS readers such as Firefox Livemarks can perform
341 
+    periodic fetches. Due to <a
342 
+    href="https://bugzilla.mozilla.org/show_bug.cgi?id=436250">Firefox Bug
343 
+    436250</a>, there is no way to disable Livemark fetches during Tor. This can
344 
+    be a problem if you have a lot of custom Livemark urls that can give away
345 
+    information about your identity.
346 
+    </p>
347 
+  </div>
348 
+  <!-- END MAINCOL -->
349 
+  <div id = "sidecol">
350 
+#include "side.wmi"
351 
+#include "info.wmi"
352 
+  </div>
353 
+  <!-- END SIDECOL -->
354 
+</div>
355 
+<!-- END CONTENT -->
356 
+#include <foot.wmi>
projects/en/torbutton-options.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,274 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Projects Overview" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/torbutton>">TorButton &raquo; </a>
11 
+    <a href="<page projects/torbutton-options>">TorButton Options</a>
12 
+  </div>
13 
+	<div id="maincol">
14 
+    <!-- PUT CONTENT AFTER THIS TAG -->
15 
+
16 
+    <h2>Torbutton Options</h2>
17 
+    <hr />
18 
+
19 
+    <p>Torbutton 1.2.0 adds several new security features to protect your
20 
+    anonymity from all the major threats we know about. The defaults should be
21 
+    fine (and safest!) for most people, but in case you are the tweaker type,
22 
+    or if you prefer to try to outsource some options to more flexible extensions,
23 
+    here is the complete list. (In an ideal world, these descriptions should all be
24 
+    tooltips in the extension itself, but Firefox bugs <a
25 
+    href="https://bugzilla.mozilla.org/show_bug.cgi?id=45375">45375</a> and <a
26 
+    href="https://bugzilla.mozilla.org/show_bug.cgi?id=218223">218223</a> currently
27 
+    prevent this.)</p>
28 
+
29 
+    <ul>
30 
+     <li>Disable plugins on Tor Usage (crucial)<p>
31 
+
32 
+      This option is key to Tor security. Plugins perform their own networking
33 
+    independent of the browser, and many plugins only partially obey even their own
34 
+    proxy settings.
35 
+    </p></li>
36 
+      <li>Isolate Dynamic Content to Tor State (crucial)<p>
37 
+
38 
+      Another crucial option, this setting causes the plugin to disable Javascript
39 
+      on tabs that are loaded during a Tor state different than the current one,
40 
+      to prevent delayed fetches of injected URLs that contain unique identifiers,
41 
+      and to prevent meta-refresh tags from revealing your IP when you turn off
42 
+      Tor. It also prevents all fetches from tabs loaded with an opposite Tor
43 
+      state. This serves to block non-Javascript dynamic content such as CSS
44 
+      popups from revealing your IP address if you disable Tor.
45 
+    </p></li>
46 
+      <li>Hook Dangerous Javascript (crucial)<p>
47 
+
48 
+    This setting enables the Javascript hooking code. Javascript is injected into
49 
+    pages to hook the Date object to mask your timezone, and to hook the navigator
50 
+    object to mask OS and user agent properties not handled by the standard
51 
+    Firefox user agent override settings.
52 
+    </p></li>
53 
+      <li>Resize window dimensions to multiples of 50px on toggle (recommended)<p>
54 
+
55 
+    To cut down on the amount of state available to fingerprint users uniquely,
56 
+    this pref causes windows to be resized to a multiple of 50 pixels on each
57 
+    side when Tor is enabled and pages are loaded.
58 
+    </p></li>
59 
+      <li>Disable Updates During Tor (recommended)<p>
60 
+
61 
+    Under Firefox 2, many extension authors did not update their extensions from
62 
+    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
63 
+    existing extensions. Since Firefox 3 now enforces encrypted and/or
64 
+    authenticated updates, this setting is no longer as important as it once
65 
+    was (though updates do leak information about which extensions you have, it is
66 
+    fairly infrequent).
67 
+    </p></li>
68 
+      <li>Disable Search Suggestions during Tor (optional)<p>
69 
+
70 
+    This optional setting governs if you get Google search suggestions during Tor
71 
+    usage. Since no cookie is transmitted during search suggestions, this is a
72 
+    relatively benign behavior.
73 
+    </p></li>
74 
+      <li>Block Livemarks updates during Tor usage (recommended)<p>
75 
+
76 
+    This setting causes Torbutton to disable your <a
77 
+    href="http://www.mozilla.com/firefox/livebookmarks.html">Live bookmark</a>
78 
+    updates. Since most people use Live bookmarks for RSS feeds from their blog,
79 
+    their friends' blogs, the wikipedia page they edit, and other such things,
80 
+    these updates probably should not happen over Tor. This feature takes effect
81 
+    in Firefox 3.5 and above only.
82 
+
83 
+    </p></li>
84 
+      <li>Block Tor/Non-Tor access to network from file:// urls (recommended)<p>
85 
+
86 
+    These settings prevent local html documents from transmitting local files to
87 
+    arbitrary websites <a href="http://www.gnucitizen.org/blog/content-disposition-hacking/">under Firefox 2</a>. Since exit nodes can insert headers that
88 
+    force the browser to save arbitrary pages locally (and also inject script into
89 
+    arbitrary html files you save to disk via Tor), it is probably a good idea to
90 
+    leave this setting on.
91 
+    </p></li>
92 
+      <li>Close all Non-Tor/Tor windows and tabs on toggle (optional)<p>
93 
+
94 
+    These two settings allow you to obtain a greater degree of assurance that
95 
+    after you toggle out of Tor, the pages are really gone and can't perform any
96 
+    extra network activity. Currently, there is no known way that pages can still
97 
+    perform activity after toggle, but these options exist as a backup measure
98 
+    just in case a flaw is discovered. They can also serve as a handy 'Boss
99 
+    Button' feature for clearing all Tor browsing off your screen in a hurry.
100 
+    </p></li>
101 
+      <li>Isolate access to history navigation to Tor state (crucial)<p>
102 
+
103 
+    This setting prevents both Javascript and accidental user clicks from causing
104 
+    the session history to load pages that were fetched in a different Tor state
105 
+    than the current one. Since this can be used to correlate Tor and Non-Tor
106 
+    activity and thus determine your IP address, it is marked as a crucial
107 
+    setting.
108 
+    </p></li>
109 
+      <li>Block History Reads during Tor (crucial)<p>
110 
+
111 
+      Based on code contributed by <a href="http://www.collinjackson.com/">Collin
112 
+      Jackson</a>, when enabled and Tor is enabled, this setting prevents the
113 
+    rendering engine from knowing if certain links were visited.  This mechanism
114 
+    defeats all document-based history disclosure attacks, including CSS-only
115 
+    attacks.
116 
+    </p></li>
117 
+      <li>Block History Reads during Non-Tor (recommended)<p>
118 
+
119 
+      This setting accomplishes the same but for your Non-Tor activity.
120 
+    </p></li>
121 
+      <li>Block History Writes during Tor (recommended)<p>
122 
+
123 
+      This setting prevents the rendering engine from recording visited URLs, and
124 
+    also disables download manager history. Note that if you allow writing of Tor history,
125 
+    it is recommended that you disable non-Tor history reads, since malicious
126 
+    websites you visit without Tor can query your history for .onion sites and
127 
+    other history recorded during Tor usage (such as Google queries).
128 
+    </p></li>
129 
+      <li>Block History Writes during Non-Tor (optional)<p>
130 
+
131 
+    This setting also disables recording any history information during Non-Tor
132 
+    usage.
133 
+    </p></li>
134 
+    <li>Clear History During Tor Toggle (optional)<p>
135 
+
136 
+      This is an alternate setting to use instead of (or in addition to) blocking
137 
+    history reads or writes.
138 
+    </p></li>
139 
+      <li>Block Password+Form saving during Tor/Non-Tor<p>
140 
+
141 
+      These options govern if the browser writes your passwords and search
142 
+      submissions to disk for the given state.
143 
+    </p></li>
144 
+      <li>Block Tor disk cache and clear all cache on Tor Toggle<p>
145 
+
146 
+      Since the browser cache can be leveraged to store unique identifiers, cache
147 
+    must not persist across Tor sessions. This option keeps the memory cache active
148 
+    during Tor usage for performance, but blocks disk access for caching.
149 
+    </p></li>
150 
+      <li>Block disk and memory cache during Tor<p>
151 
+
152 
+      This setting entirely blocks the cache during Tor, but preserves it for
153 
+    Non-Tor usage.
154 
+    </p></li>
155 
+      <li>Clear Cookies on Tor Toggle<p>
156 
+
157 
+      Fully clears all cookies on Tor toggle.
158 
+    </p></li>
159 
+      <li>Store Non-Tor cookies in a protected jar<p>
160 
+
161 
+      This option stores your persistent Non-Tor cookies in a special cookie jar
162 
+      file, in case you wish to preserve some cookies. Based on code contributed
163 
+      by <a href="http://www.collinjackson.com/">Collin Jackson</a>. It is
164 
+      compatible with third party extensions that you use to manage your Non-Tor
165 
+      cookies. Your Tor cookies will be cleared on toggle, of course.
166 
+    </p></li>
167 
+      <li>Store both Non-Tor and Tor cookies in a protected jar (dangerous)<p>
168 
+
169 
+      This option stores your persistent Tor and Non-Tor cookies
170 
+      separate cookie jar files. Note that it is a bad idea to keep Tor
171 
+      cookies around for any length of time, as they can be retrieved by exit
172 
+      nodes that inject spoofed forms into plaintext pages you fetch.
173 
+    </p></li>
174 
+      <li>Manage My Own Cookies (dangerous)<p>
175 
+
176 
+      This setting allows you to manage your own cookies with an alternate
177 
+    extension, such as <a href="https://addons.mozilla.org/firefox/addon/82">CookieCuller</a>. Note that this is particularly dangerous,
178 
+    since malicious exit nodes can spoof document elements that appear to be from
179 
+    sites you have preserved cookies for (and can then do things like fetch your
180 
+    entire gmail inbox, even if you were not using gmail or visiting any google
181 
+    pages at the time!).
182 
+    </p></li>
183 
+      <li>Do not write Tor/Non-Tor cookies to disk<p>
184 
+
185 
+      These settings prevent Firefox from writing any cookies to disk during the
186 
+      corresponding Tor state. If cookie jars are enabled, those jars will
187 
+      exist in memory only, and will be cleared when Firefox exits.
188 
+    </p></li>
189 
+      <li>Disable DOM Storage during Tor usage (crucial)<p>
190 
+
191 
+      Firefox has recently added the ability to store additional state and
192 
+      identifiers in persistent tables, called <a
193 
+      href="http://developer.mozilla.org/docs/DOM:Storage">DOM Storage</a>.
194 
+      Obviously this can compromise your anonymity if stored content can be
195 
+      fetched across Tor-state.
196 
+    </p></li>
197 
+      <li>Clear HTTP auth sessions (recommended)<p>
198 
+
199 
+      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.
200 
+    </p></li>
201 
+      <li>Clear cookies on Tor/Non-Tor shutdown<p>
202 
+
203 
+      These settings install a shutdown handler to clear cookies on Tor
204 
+    and/or Non-Tor browser shutdown. It is independent of your Clear Private Data
205 
+    settings, and does in fact clear the corresponding cookie jars.
206 
+    </p></li>
207 
+      <li>Prevent session store from saving Tor-loaded tabs (recommended)<p>
208 
+
209 
+      This option augments the session store to prevent it from writing out
210 
+      Tor-loaded tabs to disk. Unfortunately, this also disables your ability to
211 
+      undo closed tabs. The reason why this setting is recommended is because
212 
+      after a session crash, your browser will be in an undefined Tor state, and
213 
+      can potentially load a bunch of Tor tabs without Tor. The following option
214 
+      is another alternative to protect against this.
215 
+    </p></li>
216 
+      <li>On normal startup, set state to: Tor, Non-Tor, Shutdown State<p>
217 
+
218 
+      This setting allows you to choose which Tor state you want the browser to
219 
+      start in normally: Tor, Non-Tor, or whatever state the browser shut down in.
220 
+    </p></li>
221 
+      <li>On crash recovery or session restored startup, restore via: Tor, Non-Tor<p>
222 
+
223 
+      When Firefox crashes, the Tor state upon restart usually is completely
224 
+      random, and depending on your choice for the above option, may load
225 
+      a bunch of tabs in the wrong state. This setting allows you to choose
226 
+      which state the crashed session should always be restored in to.
227 
+    </p></li>
228 
+      <li>Prevent session store from saving Non-Tor/Tor-loaded tabs<p>
229 
+
230 
+      These two settings allow you to control what the Firefox Session Store
231 
+      writes to disk. Since the session store state is used to automatically
232 
+      load websites after a crash or upgrade, it is advisable not to allow
233 
+      Tor tabs to be written to disk, or they may get loaded in Non-Tor
234 
+      after a crash (or the reverse, depending upon the crash recovery setting,
235 
+      of course).
236 
+    </p></li>
237 
+      <li>Set user agent during Tor usage (crucial)<p>
238 
+
239 
+      User agent masking is done with the idea of making all Tor users appear
240 
+    uniform. A recent Firefox 2.0.0.4 Windows build was chosen to mimic for this
241 
+    string and supporting navigator.* properties, and this version will remain the
242 
+    same for all TorButton versions until such time as specific incompatibility
243 
+    issues are demonstrated. Uniformity of this value is obviously very important
244 
+    to anonymity. Note that for this option to have full effectiveness, the user
245 
+    must also allow Hook Dangerous Javascript ensure that the navigator.*
246 
+    properties are reset correctly.  The browser does not set some of them via the
247 
+    exposed user agent override preferences.
248 
+    </p></li>
249 
+      <li>Spoof US English Browser<p>
250 
+
251 
+    This option causes Firefox to send http headers as if it were an English
252 
+    browser. Useful for internationalized users.
253 
+    </p></li>
254 
+      <li>Don't send referrer during Tor Usage<p>
255 
+
256 
+    This option disables the referrer header, preventing sites from determining
257 
+    where you came from to visit them. This can break some sites, however. <a
258 
+    href="http://www.digg.com">Digg</a> in particular seemed to be broken by this.
259 
+    A more streamlined, less intrusive version of this option should be available
260 
+    eventually. In the meantime, <a
261 
+    href="https://addons.mozilla.org/firefox/addon/953">RefControl</a> can
262 
+    provide this functionality via a default option of <b>Forge</b>.
263 
+    </p></li>
264 
+    </ul>
265 
+  </div>
266 
+  <!-- END MAINCOL -->
267 
+  <div id = "sidecol">
268 
+#include "side.wmi"
269 
+#include "info.wmi"
270 
+  </div>
271 
+  <!-- END SIDECOL -->
272 
+</div>
273 
+<!-- END CONTENT -->
274 
+#include <foot.wmi>
projects/en/torbutton.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,156 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 0 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Projects Overview" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/torbutton>">TorButton</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <link rel="search" type="application/opensearchdescription+xml" title="Google Canada" href="search/google-ca.xml"/>
16 
+    <link rel="search" type="application/opensearchdescription+xml" title="Google UK" href="search/google-uk.xml" />
17 
+    <link rel="search" type="application/opensearchdescription+xml" title="Google USA" href="search/google-us.xml"/>
18 
+    <script type="text/javascript">
19 
+
20 
+    function addSearchProvider(prov) {
21 
+
22 
+    try {
23 
+    window.external.AddSearchProvider(prov);
24 
+    }
25 
+
26 
+    catch (e) {
27 
+    alert("Search plugins require Firefox 2");
28 
+    return;
29 
+    }
30 
+    }
31 
+
32 
+    function addEngine(name,ext,cat,pid)
33 
+    {
34 
+      if ((typeof window.sidebar == "object") && (typeof window.sidebar.addSearchEngine == "function")) {
35 
+        window.sidebar.addSearchEngine(
36 
+          "http://mycroft.mozdev.org/install.php/" + pid + "/" + name + ".src",
37 
+          "http://mycroft.mozdev.org/install.php/" + pid + "/" + name + "."+ ext, name, cat );
38 
+      } else {
39 
+        alert("You will need a browser which supports Sherlock to install this plugin.");
40 
+      }
41 
+    }
42 
+
43 
+    function addOpenSearch(name,ext,cat,pid,meth)
44 
+    {
45 
+      if ((typeof window.external == "object") && ((typeof window.external.AddSearchProvider == "unknown") || (typeof window.external.AddSearchProvider == "function"))) {
46 
+        if ((typeof window.external.AddSearchProvider == "unknown") && meth == "p") {
47 
+          alert("This plugin uses POST which is not currently supported by Internet Explorer's implementation of OpenSearch.");
48 
+        } else {
49 
+          window.external.AddSearchProvider(
50 
+            "http://mycroft.mozdev.org/installos.php/" + pid + "/" + name + ".xml");
51 
+        }
52 
+      } else {
53 
+        alert("You will need a browser which supports OpenSearch to install this plugin.");
54 
+      }
55 
+    }
56 
+
57 
+    function addOpenSearch2(name,ext,cat,pid,meth)
58 
+    {
59 
+      if ((typeof window.external == "object") && ((typeof window.external.AddSearchProvider == "unknown") || (typeof window.external.AddSearchProvider == "function"))) {
60 
+        if ((typeof window.external.AddSearchProvider == "unknown") && meth == "p") {
61 
+          alert("This plugin uses POST which is not currently supported by Internet Explorer's implementation of OpenSearch.");
62 
+        } else {
63 
+          window.external.AddSearchProvider(
64 
+            "http://torbutton.torproject.org/dev/search/" + name + ".xml");
65 
+        }
66 
+      } else {
67 
+        alert("You will need a browser which supports OpenSearch to install this plugin.");
68 
+      }
69 
+    }
70 
+
71 
+    function install (aEvent)
72 
+    {
73 
+      var params = {
74 
+        "Torbutton": { URL: aEvent.target.href,
75 
+                 Hash: aEvent.target.getAttribute("hash"),
76 
+                 toString: function () { return this.URL; }
77 
+        }
78 
+      };
79 
+      InstallTrigger.install(params);
80 
+
81 
+      return false;
82 
+    }
83 
+
84 
+
85 
+    </script>
86 
+
87 
+    <h2>Torbutton</h2>
88 
+    <hr />
89 
+
90 
+    <strong>Current version:</strong><version-torbutton><br/>
91 
+    <br/>
92 
+    <strong>Authors:</strong> Mike Perry &amp; Scott Squires<br/>
93 
+    <br/>
94 
+    <strong>Install:</strong> Click to
95 
+    <a href="http://www.torproject.org/torbutton/torbutton-current.xpi"
96 
+      hash="<version-hash-torbutton>"
97 
+      onclick="return install(event);">install from this website</a> or
98 
+    <a href="https://addons.mozilla.org/en-US/firefox/downloads/latest/2275/addon-2275-latest.xpi?src=addondetail">install from Mozilla's Add-On site</a><br/>
99 
+    <strong>Past Releases:</strong> <a href="releases/">Local</a><br/>
100 
+    <strong>Developer Documentation:</strong> <a href="design/">Torbutton Design Document</a> and <a href="design/MozillaBrownBag.pdf">Slides (Not actively updated)</a><br/>
101 
+    <strong>Extras:</strong>
102 
+
103 
+    Google search plugins for
104 
+
105 
+    <a href="/jsreq.html" title="Ref: 14938 (googleCA)"
106 
+     onClick="addOpenSearch('GoogleCanada','ico','General','14937','g');return false">Google CA</a>, and
107 
+
108 
+    <a href="/jsreq.html" title="Ref: 14938 (googleCA)"
109 
+     onClick="addOpenSearch('googleuk_web','png','General','14445','g');return false">Google UK</a>.
110 
+    <br/>
111 
+    <strong>Source:</strong> You can <a
112 
+    href="https://gitweb.torproject.org/torbutton.git">browse the
113 
+    repository</a> or simply unzip the xpi.
114 
+    <br/>
115 
+    <strong>Bug Reports:</strong> <a href="https://bugs.torproject.org/flyspray/index.php?tasks=all&amp;project=5">Torproject flyspray</a><br/>
116 
+    <strong>Documents:</strong> <b>[</b> <a href="<page projects/torbutton-faq>">FAQ</a> <b>|</b>
117 
+    <a href="https://git.torproject.org/checkout/torbutton/master/src/CHANGELOG">changelog</a> <b>|</b>
118 
+    <a href="https://git.torproject.org/checkout/torbutton/master/src/LICENSE">license</a> <b>|</b>
119 
+    <a href="https://git.torproject.org/checkout/torbutton/master/src/CREDITS">credits</a> <b>]</b><br/>
120 
+
121 
+    <br/>
122 
+
123 
+    <p>
124 
+    Torbutton is a 1-click way for Firefox users to enable or disable
125 
+    the browser's use of <a href="<page index>">Tor</a>.
126 
+    It adds a panel to the statusbar that says "Tor Enabled" (in green) or
127 
+    "Tor Disabled" (in red).  The user may click on the panel to toggle
128 
+    the status.  If the user (or some other extension) changes the proxy
129 
+    settings, the change is automatically reflected in the statusbar.
130 
+    </p>
131 
+
132 
+    <p>
133 
+    To keep you safe, Torbutton disables many types of active content. You
134 
+    can learn more from the <a href="<page projects/torbutton-faq>">Torbutton FAQ</a>,
135 
+    or read more details in the <a href="<page projects/torbutton-options>">Torbutton
136 
+    options</a> list.
137 
+    </p>
138 
+
139 
+    <p>
140 
+    Some users may prefer a toolbar button instead of a statusbar panel.
141 
+    Torbutton lets you add a toolbar button by right-clicking
142 
+    on the desired toolbar, selecting "Customize...", and then dragging the
143 
+    Torbutton icon onto the toolbar.  There is an option in the preferences
144 
+    to hide the statusbar panel (Tools-&gt;Extensions, select Torbutton,
145 
+    and click on Preferences).
146 
+    </p>
147 
+  </div>
148 
+  <!-- END MAINCOL -->
149 
+  <div id = "sidecol">
150 
+#include "side.wmi"
151 
+#include "info.wmi"
152 
+  </div>
153 
+  <!-- END SIDECOL -->
154 
+</div>
155 
+<!-- END CONTENT -->
156 
+#include <foot.wmi>
projects/en/tordnsel.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,97 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 3-low
4 
+
5 
+#include "head.wmi" TITLE="A public TorDNSEL service" CHARSET="UTF-8"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/tordnsel>">TorDNSEL</a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+
14 
+    <!-- PUT CONTENT AFTER THIS TAG -->
15 
+    <h1>The public TorDNSEL service</h1>
16 
+
17 
+    <h2>What is the TorDNSEL?</h2>
18 
+
19 
+    <p>TorDNSEL is an active testing, DNS-based list of Tor exit nodes. Since Tor
20 
+    supports exit policies, a network service's Tor exit list is a function of its
21 
+    IP address and port. Unlike with traditional DNSxLs, services need to provide
22 
+    that information in their queries.</p>
23 
+
24 
+    <p>Previous DNSELs scraped Tor's network directory for exit node IP addresses,
25 
+    but this method fails to list nodes that don't advertise their exit address in
26 
+    the directory. TorDNSEL actively tests through these nodes to provide a more
27 
+    accurate list.</p>
28 
+
29 
+    <p>The full background and rationale for TorDNSEL is described in the official
30 
+    <a href="<gitblob>doc/contrib/torel-design.txt">design
31 
+    document</a>. The current service only supports the first query type mentioned
32 
+    in that document.</p>
33 
+
34 
+    <h2>How can I query the public TorDNSEL service?</h2>
35 
+
36 
+    <p>Using the command line tool dig, users can ask type 1 queries like so:</p>
37 
+
38 
+    <pre>dig 209.137.169.81.6667.4.3.2.1.ip-port.exitlist.torproject.org</pre>
39 
+
40 
+    <h2>What do the received answers mean?</h2>
41 
+
42 
+    <p>A request for the A record
43 
+    "209.137.169.81.6667.4.3.2.1.ip-port.exitlist.torproject.org" would return
44 
+    127.0.0.2 if there's a Tor node that can exit through 81.169.137.209 to port
45 
+    6667 at 1.2.3.4. If there isn't such an exit node, the DNSEL returns
46 
+    NXDOMAIN.</p>
47 
+
48 
+    <p>Other A records inside net 127/8, except 127.0.0.1, are reserved for future
49 
+    use and should be interpreted by clients as indicating an exit node. Queries
50 
+    outside the DNSEL's zone of authority result in REFUSED. Ill-formed queries
51 
+    inside its zone of authority result in NXDOMAIN.</p>
52 
+
53 
+    <h2>How do I configure software with DNSBL support?</h2>
54 
+
55 
+    <p>Users of software with built-in support for DNSBLs can configure the
56 
+    following zone as a DNSBL:</p>
57 
+
58 
+    <pre>[service port].[reversed service
59 
+    address].ip-port.exitlist.torproject.org</pre>
60 
+
61 
+    <p>An example for an IRC server running on port 6667 at IP address 1.2.3.4:</p>
62 
+    <pre>6667.4.3.2.1.ip-port.exitlist.torproject.org</pre>
63 
+
64 
+    <h2>How reliable are the answers returned by TorDNSEL?</h2>
65 
+
66 
+    <p>The current public service is operating on an experimental basis and hasn't
67 
+    been well tested by real services. Reports of erroneous answers or service
68 
+    interruption would be appreciated. Future plans include building a fault
69 
+    tolerant pool of DNSEL servers. TorDNSEL is currently under active
70 
+    development.</p>
71 
+
72 
+    <h2>How can I run my own private TorDNSEL?</h2>
73 
+
74 
+    <p>You can learn all about the code for TorDNSEL by visiting the <a
75 
+    href="http://p56soo2ibjkx23xo.onion/">official hidden service</a> through
76 
+    Tor.</p>
77 
+
78 
+    <p>You can download the latest source release from the <a
79 
+    href="http://p56soo2ibjkx23xo.onion/dist/tordnsel-0.0.6.tar.gz">hidden
80 
+    service</a> or from a
81 
+    <a href="https://www.torproject.org/tordnsel/dist/tordnsel-0.0.6.tar.gz">
82 
+    local mirror</a>. It's
83 
+    probably wise to check out the current revision from the darcs repository
84 
+    hosted on the aforementioned hidden service.</p>
85 
+
86 
+    <p>For more information or to report something useful, please email the
87 
+    <tt>tordnsel</tt> alias on our <a href="<page about/contact>">contact page</a>.</p>
88 
+  </div>
89 
+  <!-- END MAINCOL -->
90 
+  <div id = "sidecol">
91 
+#include "side.wmi"
92 
+#include "info.wmi"
93 
+  </div>
94 
+  <!-- END SIDECOL -->
95 
+</div>
96 
+<!-- END CONTENT -->
97 
+#include <foot.wmi>
projects/en/torvm.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,174 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 21511 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor VM" CHARSET="UTF-8"
6 
+
7 
+<div id="content" class="clearfix">
8 
+	<div id="breadcrumbs">
9 
+    <a href="<page home>">Home &raquo; </a>
10 
+    <a href="<page projects/projects>">Projects &raquo; </a>
11 
+    <a href="<page projects/torvm>">Tor VM</a>
12 
+  </div>
13 
+	<div id="maincol">
14 
+
15 
+    <!-- PUT CONTENT AFTER THIS TAG -->
16 
+
17 
+    <h1>Tor VM</h1>
18 
+
19 
+    <!-- BEGIN SIDEBAR -->
20 
+    <div class="sidebar-left">
21 
+    <h3>Using Tor VM</h3>
22 
+    <ul>
23 
+    <li><a href="#Download">Download</a></li>
24 
+    <li><a href="#Install">Install</a></li>
25 
+    <li><a href="#Run">Run VM</a></li>
26 
+    <li><a href="#RecommendedUse">Use Torbutton</a></li>
27 
+    <li><a href="#Shutdown">Shutdown</a></li>
28 
+    </ul>
29 
+    </div>
30 
+    <!-- END SIDEBAR -->
31 
+
32 
+    <h2>What Is It?</h2>
33 
+    <p>Tor VM is a transparent Tor proxy for Windows built with
34 
+    <a href="http://www.qemu.org/">Qemu</a> virtualization technology for more
35 
+    resilient clients and relays.
36 
+    </p>
37 
+    <p>You can think of Tor VM like a Tor virtual network card that routes all of the traffic
38 
+     from your machine transparently over the Tor network without application proxy settings or other configuration.
39 
+    </p>
40 
+    <p>The <a href="https://svn.torproject.org/svn/torvm/trunk/doc/design.html">Tor
41 
+    VM design document</a> contains additional detail about this work in progress.</p>
42 
+
43 
+    <hr />
44 
+    <a id="Download"></a>
45 
+    <h2><a class="anchor" href="#Download">Step One: Download Tor VM Software</a></h2>
46 
+
47 
+    <ul>
48 
+    <li><a href="dist/TorVM-0.0.2-Bundle.exe">Tor VM Bundle Installer</a>
49 
+    (<a href="dist/TorVM-0.0.2-Bundle.exe.asc" style="font-size: 90%;">sig</a>)</li>
50 
+
51 
+    <li><a href="dist/TorVM-0.0.2-NetInstaller.exe">Tor VM Network Installer</a>
52 
+    (<a href="dist/TorVM-0.0.2-NetInstaller.exe.asc" style="font-size: 90%;">sig</a>)</li>
53 
+    </ul>
54 
+
55 
+    <hr />
56 
+    <a id="Install"></a>
57 
+    <h2><a class="anchor" href="#Install">Step Two: Install Tor VM</a></h2>
58 
+
59 
+    <p>Double click on the Bundle or Network Installer EXE to begin installation to the
60 
+    current system.</p>
61 
+
62 
+    <p><img src="img/bundle02.png" alt="Click to Run Bundle Installer" /></p>
63 
+
64 
+    <p>The network installer contains the secure Tor updater software that is used
65 
+    to reliably download all of the latest bundle application packages on demand.</p>
66 
+
67 
+    <p><img src="img/netinst02.png" alt="Network Installer downloads bundle software on demand" /></p>
68 
+
69 
+
70 
+    <hr />
71 
+    <a id="Run"></a>
72 
+    <h2><a class="anchor" href="#Run">Step Three: Run Tor VM</a></h2>
73 
+
74 
+    <p>When installation is complete a Tor VM controller is started in
75 
+    the background. The installer program has finished and can be closed.</p>
76 
+
77 
+    <p><img src="img/run01.png" alt="Tor VM controller will start at end of install" /></p>
78 
+
79 
+    <p>After preparing network devices a Qemu virtual machine running the
80 
+    Tor VM kernel is launched with the Vidalia controller. It may take a
81 
+    few minutes to bootstrap into the Tor network. Please be patient.</p>
82 
+
83 
+    <p><img src="img/run02.png" alt="Bootstrap not complete until circuit created" /></p>
84 
+
85 
+    <hr />
86 
+    <a id="RecommendedUse"></a>
87 
+    <h2><a class="anchor" href="#RecommendedUse">Step Four: Using Firefox and Torbutton</a></h2>
88 
+
89 
+    <p>Once Tor has successfully built a circuit the Switch User menu is presented.
90 
+    Firefox and other Tor applications must be run with the "Tor" restricted user account.</p>
91 
+
92 
+    <p><img src="img/tor-user-switch.png" alt="Switch to Tor restricted user account" /></p>
93 
+
94 
+    <p>Start Firefox and click on the Torbutton status icon in the lower right to enable Tor.</p>
95 
+
96 
+    <p><img src="img/torbutton04.png" alt="Click on Torbutton status icon to toggle ON" /></p>
97 
+
98 
+    <p>Verify that you are using Tor via
99 
+    <a href="https://check.torproject.org/">https://check.torproject.org/</a></p>
100 
+
101 
+    <p><img src="img/torbutton05.png" alt="Verify Tor use at check.torproject.org" /></p>
102 
+
103 
+
104 
+    <hr />
105 
+    <a id="ExperimentalUse"></a>
106 
+    <h2><a class="anchor" href="#ExperimentalUse">Experimental: Using Flash</a></h2>
107 
+
108 
+    <p><strong>IMPORTANT: This is not a recommended use of Tor.</strong></p>
109 
+
110 
+    <p>Right click on Torbutton icon at lower right for menu. Select "Preferences..."
111 
+    option.</p>
112 
+
113 
+    <p><img src="img/tbprefs.png" alt="Select Torbutton Preferences menu option" /></p>
114 
+
115 
+    <p>Toggle the "Disable plugins..." dynamic content security setting.</p>
116 
+
117 
+    <p><img src="img/tbcontent.png" alt="Toggle disable plugins dynamic content security setting" /></p>
118 
+
119 
+    <p>Connections made from the Browser and Flash Player plugin will now
120 
+    be transparently proxied through the Tor network when viewing content.</p>
121 
+
122 
+    <p><img src="img/flash02.png" alt="Flash player and other software now using Tor" /></p>
123 
+
124 
+    <hr />
125 
+    <a id="Shutdown"></a>
126 
+    <h2><a class="anchor" href="#Shutdown">Step Five: Shutdown Tor VM</a></h2>
127 
+
128 
+    <p>Press The Windows Key + L to switch back to administrator User.</p>
129 
+
130 
+    <p><img src="img/win-el.png" alt="Windows Key + L to switch user" /></p>
131 
+
132 
+    <p><img src="img/admin-user-switchback.png" alt="Switch back to admin user account" /></p>
133 
+
134 
+    <p>Select the Vidalia "Exit" option to shutdown the VM and restore network settings.
135 
+    The restricted Tor user will be logged off automatically.</p>
136 
+
137 
+    <p><img src="img/exit-vidalia.png" alt="Select Vidalia Exit option to close VM" /></p>
138 
+
139 
+    <p>Do not close the Tor VM controller window while restoring network settings.</p>
140 
+
141 
+    <p><img src="img/vm-shutdown.png" alt="Do not close the Tor VM window while restoring network settings" /></p>
142 
+
143 
+
144 
+    <hr />
145 
+    <a id="Remove"></a>
146 
+    <h2><a class="anchor" href="#Remove">Uninstall Tor Bundle Software</a></h2>
147 
+
148 
+    <p>A script to uninstall all of the Tor bundle applications is placed
149 
+    on the desktop. Run this utility to remove all of the Tor software and files.</p>
150 
+
151 
+    <p><img src="img/uninstall.png" alt="The Uninstall_Tor script will remove all Tor packages and files" /></p>
152 
+
153 
+
154 
+    <hr />
155 
+    <a id="Debug"></a>
156 
+    <h2><a class="anchor" href="#Debug">Troubleshoot Problems and Report Bugs</a></h2>
157 
+
158 
+    <p>The Tor VM category in the Tor flyspray bug tracker is used to manage
159 
+    defects and features. See the
160 
+    <a href="http://bugs.noreply.org/flyspray/index.php?tasks=all&amp;project=4"
161 
+    >Tor flyspray bug tracker</a> for known issues and pending changes.</p>
162 
+
163 
+    <p>Features and fixes planned for the Tor VM software are documented in the
164 
+    <a href="https://svn.torproject.org/svn/torvm/trunk/TODO">Tor VM TODO</a>.</p>
165 
+  </div>
166 
+  <!-- END MAINCOL -->
167 
+  <div id = "sidecol">
168 
+#include "side.wmi"
169 
+#include "info.wmi"
170 
+  </div>
171 
+  <!-- END SIDECOL -->
172 
+</div>
173 
+<!-- END CONTENT -->
174 
+#include <foot.wmi>
projects/en/vidalia.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,102 @@
1 
+## translation metadata
2 
+# Revision: $Revision: 22399 $
3 
+# Translation-Priority: 4-optional
4 
+
5 
+#include "head.wmi" TITLE="Tor Project: Projects Overview" CHARSET="UTF-8" ANNOUNCE_RSS="yes"
6 
+<div id="content" class="clearfix">
7 
+	<div id="breadcrumbs">
8 
+    <a href="<page home>">Home &raquo; </a>
9 
+    <a href="<page projects/projects>">Projects &raquo; </a>
10 
+    <a href="<page projects/vidalia>">Vidalia &raquo; </a>
11 
+  </div>
12 
+	<div id="maincol">
13 
+    <!-- PUT CONTENT AFTER THIS TAG -->
14 
+
15 
+    <h2>Vidalia</h2>
16 
+    <div class="underline"></div>
17 
+
18 
+    <!-- BEGIN SIDEBAR -->
19 
+    <div class="sidebar-left">
20 
+    <img src="../img/Screenshot-Vidalia-Control-Panel.png" width="261" height="255" alt="Vidalia Control Panel Screenshot" />
21 
+    </div>
22 
+    <!-- END SIDEBAR -->
23 
+
24 
+    <p>
25 
+    Vidalia is a cross-platform controller GUI for the <a
26 
+    href="https://www.torproject.org/">Tor</a> software, built using the <a
27 
+    href="http://trolltech.com/products/qt">Qt</a> framework. Vidalia runs on
28 
+    most platforms supported by Qt 4.3 or later, including Windows, Mac OS X,
29 
+    and Linux or other Unix variants using the X11 window system.
30 
+    </p>
31 
+
32 
+
33 
+    <a id="Downloads"></a>
34 
+    <h3><a class="anchor" href="#Downloads">Downloads</a></h3>
35 
+
36 
+    <p>
37 
+    Most Windows and Mac OS X users should simply download Vidalia as part of a
38 
+    <a href="<page download/easy-download>">Tor software
39 
+    bundle</a>. If you want to upgrade the Vidalia software included in a Tor
40 
+    bundle you currently have installed, you can use one of the installer
41 
+    packages below.
42 
+    </p>
43 
+
44 
+    <h4>Stable Releases</h4>
45 
+    <p> The most recent stable release is:
46 
+    <a href="https://trac.vidalia-project.net/milestone/Vidalia%200.2.9">0.2.9</a>
47 
+    </p>
48 
+
49 
+    <ul>
50 
+      <li>
51 
+         <a href="dist/vidalia-0.2.9.msi">Windows Installer</a>
52 
+        (<a href="dist/vidalia-0.2.9.msi.asc">sig</a>)
53 
+      </li>
54 
+      <li>
55 
+         <a href="dist/vidalia-0.2.9-i386.dmg">Mac OS X x86 Only</a>
56 
+        (<a href="dist/vidalia-0.2.9-i386.dmg.asc">sig</a>)
57 
+      </li>
58 
+      <li>
59 
+         <a href="dist/vidalia-0.2.9-ppc.dmg">Mac OS X PPC-only</a>
60 
+        (<a href="dist/vidalia-0.2.9-ppc.dmg.asc">sig</a>)
61 
+      </li>
62 
+      <li>
63 
+        <a href="<page docs/debian-vidalia>">Instructions for Debian/Ubuntu/Knoppix Repositories</a>
64 
+      </li>
65 
+      <li>
66 
+         <a href="dist/vidalia-0.2.9.tar.gz">Source Tarball</a>
67 
+        (<a href="dist/vidalia-0.2.9.tar.gz.asc">sig</a>)
68 
+      </li>
69 
+    </ul>
70 
+
71 
+
72 
+    <a id="Support"></a>
73 
+    <h3><a class="anchor" href="#Support">Support &amp; Development</a></h3>
74 
+
75 
+    <p>
76 
+    Please open a <a
77 
+    href="https://trac.vidalia-project.net/report/1">ticket</a> on our bug
78 
+    tracker for any <a
79 
+    href="https://trac.vidalia-project.net/wiki/ReportingBugs">bugs you
80 
+    find</a> or <a
81 
+    href="https://trac.vidalia-project.net/wiki/RequestingFeatures">features you would like
82 
+    to see</a> added in future releases.
83 
+    </p>
84 
+
85 
+    <p>
86 
+    We also have a <a
87 
+    href="http://lists.vidalia-project.net/cgi-bin/mailman/listinfo/vidalia-users">vidalia-users</a>
88 
+    mailing list for support-related questions. You may also be able to find
89 
+    answers to your questions by <a
90 
+    href="https://trac.vidalia-project.net/search">searching</a> our <a
91 
+    href="https://trac.vidalia-project.net/wiki">wiki</a>.
92 
+    </p>
93 
+  </div>
94 
+  <!-- END MAINCOL -->
95 
+  <div id = "sidecol">
96 
+#include "side.wmi"
97 
+#include "info.wmi"
98 
+  </div>
99 
+  <!-- END SIDECOL -->
100 
+</div>
101 
+<!-- END CONTENT -->
102 
+#include <foot.wmi>
projects/es/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/et/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/fmetrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/fr/google.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,89 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22051 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="Google Project: Secure Upgrade of Tor" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Projet Google: Mise à jour sécurisée de Tor</h2>
17 
+
18 
+<hr />
19 
+
20 
+<p>
21 
+
22 
+
23 
+</p>
24 
+
25 
+<p>
26 
+Ce projet est généreusement financé par <a
27 
+href="http://www.google.com">Google</a>.
28 
+</p>
29 
+
30 
+<a id="Timetable"></a>
31 
+<h2><a class="anchor" href="#Timetable">Calendrier</a></h2>
32 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
33 
+
34 
+
35 
+<!-- <thead>
36 
+
37 
+<tr bgcolor="#e5e5e5">
38 
+<th>Deliverable</th>
39 
+<th>Due Date</th>
40 
+</tr>
41 
+</thead> -->
42 
+<tr bgcolor="#e5e5e5">
43 
+  <td>
44 
+    <b>Étape 1:</b> Vidalia reconnait quand Tor a besoin d'une mise à jour, et
45 
+montre la version la plus appropriée et où l'obtenir.<br />
46 
+<small><em>Consultation du consensus adopté à la majorité pour décider quand
47 
+mettre à jour et vers quelle version (Tor fournit déjà une liste des
48 
+versions considérées comme sûres, dans chaque document d'état du
49 
+réseau)</em></small>
50 
+  </td>
51 
+  <td>
52 
+    15 Novembre 2008
53 
+  </td>
54 
+</tr>
55 
+
56 
+<tr>
57 
+  <td>
58 
+    <b>Étape 2:</b>Vidalia peut aller chercher une nouvelle version de Tor sur
59 
+le site de Tor et vérifier sa signature.<br /> <small><em>Mettre à jour par
60 
+Tor ou par le protocole de mise à jour des miroirs (proposition 127) si
61 
+possible, pour un complément de confidentialité.  Contrôle les signatures
62 
+des packages pour vérifier leur validité.</em></small>
63 
+  </td>
64 
+  <td>
65 
+    15 Novembre 2008
66 
+  </td>
67 
+</tr>
68 
+
69 
+<tr bgcolor="#e5e5e5">
70 
+  <td>
71 
+    <b>Étape 3:</b>Vidalia dispose d'une interface pour informer l'utilisateur
72 
+des mises à niveau et l'aide à faire cette mise à niveau. <br />
73 
+<small><em>Donne à l'utilisateur une interface pour ces mises à jour, et lui
74 
+donne la possibilité de migrer d'une version majeure de Tor à la suivante.
75 
+</em></small>
76 
+  </td>
77 
+  <td>
78 
+    15 Novembre 2008
79 
+  </td>
80 
+</tr>
81 
+</table>
82 
+
83 
+<br />
84 
+
85 
+</div>
86 
+
87 
+
88 
+
89 
+#include <foot.wmi>
projects/fr/hidserv.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,447 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22051 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="NLnet Project: Speed Up Tor Hidden Services" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Projet NLnet: accélérer les Services Cachés Tor</h2>
17 
+<hr />
18 
+
19 
+<p>
20 
+Les services cachés Tor permettent aux utilisateurs de mettre en place des
21 
+services d'information anonymes tels que des sites web qui peuvent
22 
+uniquement être accédés à travers le réseau Tor et qui sont protégés contre
23 
+l'identification des machines qui font tourner le service.  Les limites les
24 
+plus critiquées des services cachés Tor sont le temps nécessaire à
25 
+l'enregistrement du service dans le réseau et le temps de latence lorsque le
26 
+client accède au service.  En raison de problèmes de conception dans le
27 
+protocole Tor d'origine, la connexion vers un nouveau service caché peut
28 
+prendre plusieurs minutes ce qui conduit la majorité des utilisateurs à
29 
+abandonner avant que la connexion ne se fasse.  A cause de cette grande
30 
+latence dans le circuit des services cachés, il est pratiquement impossible
31 
+de réaliser des communications interactives d'utilisateur à utilisateur (ex:
32 
+messagerie instantanée) à l'aide de ces services.
33 
+</p>
34 
+
35 
+<p>
36 
+Ce projet a pour but d'accélérer d'une part les services cachés Tor en
37 
+améliorant la manière dont les circuits Tor sont construits entre
38 
+l'utilisateur et le service et d'autre part, leurs enregistrements dans le
39 
+réseau Tor.  Dans un premier temps, des diagnostics précis sur le
40 
+comportement des services cachés en conditions de laboratoire ou en
41 
+conditions réelles seront menés afin de découvrir les causes principales de
42 
+ces lenteurs.  Des stratégies d'optimisation, basées sur ces diagnostics,
43 
+seront élaborées de manière à éviter les risques de sécurité et d'anonymat
44 
+dans le réseau Tor.  Les optimisations les plus prometteuses seront alors
45 
+implémentées de manière à améliorer sensiblement les performances pour les
46 
+utilisateurs. Des mesures précises seront mises en place lors de la phase de
47 
+diagnostic, une fois que la lumière sera faîte sur les causes de lenteur et
48 
+sur les améliorations réalistes.  L'objectif principal est de réaliser le
49 
+changement du protocole des services cachés en production et propagé à
50 
+l'ensemble des utilisateurs Tor dans un pas de temps de moins de 12 mois.
51 
+</p>
52 
+
53 
+<p>
54 
+Ce projet est généreusement financé par:
55 
+</p>
56 
+
57 
+<p>
58 
+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html"> <img
59 
+src="$(IMGROOT)/nlnet-160x60.png" alt="La fondation NLnet" /></a>
60 
+</p>
61 
+
62 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
63 
+<thead>
64 
+<tr>
65 
+<th><big>Projet</big></th>
66 
+<th><big>Date de rendu</big></th>
67 
+</tr>
68 
+</thead>
69 
+
70 
+<tr bgcolor="#e5e5e5">
71 
+  <td>
72 
+    <b>Livrable A:</b> Analyse, mesures et exposé des problèmes<br />
73 
+<small><em>Etant donné qu'il y a eu peu de développement sur les services
74 
+cachés Tor au cours des dernières années, certains aspects des problèmes
75 
+sont sous-diagnostiqués. Il est nécessaire d'effectuer une analyse complète
76 
+des causes de latence et de perte de temps. Le livrable A nécessite environ
77 
+un mois de travail. Les résultats de l'analyse influenceront les décisions
78 
+de conception à prendre pour le livrable B.</em></small>
79 
+  </td>
80 
+  <td>
81 
+    15 juin 2008
82 
+  </td>
83 
+</tr>
84 
+
85 
+<tr>
86 
+  <td>
87 
+    <b>Livrable B:</b> Conception et évaluation des changements nécessaires<br
88 
+/> <small><em>Les changements dans les services cachés Tor affecteront les
89 
+fonctionnalités au coeur du protocole et imposent une évaluation prudente
90 
+des possibles répercussion en matière de sécurité et d'anonymat. Une période
91 
+de deux mois est planifiée pour la phase de conception et d'évaluation qui
92 
+se conclura par des tests utilisateurs.</em></small>
93 
+  </td>
94 
+  <td>
95 
+    15 août 2008
96 
+  </td>
97 
+</tr>
98 
+
99 
+<tr bgcolor="#e5e5e5">
100 
+  <td>
101 
+    <b>Livrable C:</b> Implémentation<br /> <small><em>Après la conception,
102 
+l'évaluation et le test utilisateur, les modifications doivent être
103 
+implémentées et intégrées dans la base actuelle du code source de Tor. Cette
104 
+implémentation prendra approximativement deux mois.  </em></small>
105 
+  </td>
106 
+  <td>
107 
+    15 octobre 2008
108 
+  </td>
109 
+</tr>
110 
+
111 
+<tr>
112 
+  <td>
113 
+    <b>Livrable D:</b> Implémentation et tests des changements jusqu'à l'état de
114 
+livraison<br /> <small><em>Étant donné que la modification est hautement
115 
+critique en terme de sécurité et de maintient d'anonymat pour le réseau Tor,
116 
+elle requière des tests et du debugging en conditions de laboratoire et en
117 
+conditions réelles. Une période de trois mois est planifiée pour ces
118 
+opérations où le développeur responsable est dévolu à ce travail à 1/3 de
119 
+son temps. Une partie de la phase de tests sera une période de version beta
120 
+publique.</em></small>
121 
+  </td>
122 
+  <td>
123 
+    15 janvier 2009
124 
+  </td>
125 
+</tr>
126 
+
127 
+<tr bgcolor="#e5e5e5">
128 
+  <td>
129 
+    <b>Livrable E:</b> Déploiement<br /> <small><em>Le déploiement vers le
130 
+serveur Tor sur le réseau sera mené en lien avec le calendrier des versions
131 
+régulières de Tor. Étant donné que ce calendrier dépend d'un certain nombre
132 
+de facteurs externes tels que l'état des autres projets logiciels devant
133 
+être incorporés dans la version, la date de livraison de la version actuelle
134 
+et celle où les modifications auront été complètement acceptées et
135 
+installées par la majorité des opérateurs de serveurs Tor peuvent
136 
+varier. D'expérience, on peut s'attendre à une période de trois à quatre
137 
+mois.</em></small>
138 
+  </td>
139 
+  <td>
140 
+    15 mars 2009
141 
+  </td>
142 
+</tr>
143 
+</table>
144 
+
145 
+<br /> <a id="Reports"></a>
146 
+<h2><a class="anchor" href="#Reports">Rapports mensuels d'avancement</a></h2>
147 
+<p>
148 
+Il y aura au total huit rapports mensuels d'état qui commenceront avec le
149 
+premier livrable aux alentours du 15 juin 2008 et se termineront avec la fin
150 
+de l'implémentation et des tests aux alentours du 15 janvier 2009.
151 
+</p>
152 
+
153 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
154 
+<thead>
155 
+<tr>
156 
+<th><big>Mois,</big></th>
157 
+<th><big>Rapport d'avancement</big></th>
158 
+</tr>
159 
+</thead>
160 
+
161 
+<tr bgcolor="#e5e5e5">
162 
+  <td>
163 
+    <a id="Jun08"></a> <a class="anchor" href="#Jun08">Juin 2008</a>
164 
+  </td>
165 
+  <td>
166 
+    <small><em>L'objectif d'origine de l'analyse de la lenteur des services
167 
+cachés Tor a été atteint. Une partie de cette analyse a été de mesurer le
168 
+temps pour mettre en place ou accéder à un service caché. De plus, on peut
169 
+maintenant tirer parti des données de mesure d'avril 2008 en vue d'explorer
170 
+les temps intermédiaires pendant la mise en place d'une connexion vers un
171 
+service caché. Les résultats sont disponibles dans <a
172 
+href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">un
173 
+rapport de 22 pages</a> qui a été rendu public sur <a
174 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">la liste de
175 
+diffusion des développeurs Tor</a>.</em></small> <br/> <small><em> L'analyse
176 
+a également révélé quelques bugs responsables des délais importants avant
177 
+qu'un service caché soit accessible. Quelques-uns de ces bugs ont été
178 
+corrigés, les autres le seront bientôt. L'évaluation a amené plusieurs
179 
+approches pour améliorer la performance des services cachés. Quelques-unes
180 
+de ces idées peuvent-être appliquées tout de suite alors que d'autres
181 
+nécessitent davantage d'analyse ainsi que de nouvelles mesures. Finalement,
182 
+au cours de l'analyse, nous avons découvert que certaines améliorations
183 
+imposent de profonds changements à Tor qui ne sont pas forcément liés aux
184 
+services cachés. Ces changement ne pourront intervenir dans le pas de temps
185 
+prévu pour ce projet.</em></small>
186 
+  </td>
187 
+</tr>
188 
+
189 
+<tr>
190 
+  <td>
191 
+    <a id="Jul08"></a> <a class="anchor" href="#Jul08">Juillet 2008</a>
192 
+  </td>
193 
+  <td>
194 
+    <small><em>Tous les bugs trouvés dans l'analyse ont été corrigés. Cela
195 
+inclut les 2 bugs corrigés pendant l'analyse et 4 autres corrigés dans les
196 
+30 derniers jours. Alors que la correction des bugs a supprimé les goulets
197 
+d'étranglement des performances dûs aux erreurs de programmation,
198 
+quelques-uns des changements de conception mis en avant au cours de la
199 
+précédente analyse ont des effets sur l'anonymat ou sur la charge réseau et
200 
+doivent être expertisés pour vérifier si les gains qu'ils permettent sont
201 
+valables compte-tenu de leur impact. Un <a
202 
+href="http://freehaven.net/~karsten/hidserv/discussion-2008-07-15.pdf">rapport</a>
203 
+a été publié sur <a
204 
+href="http://archives.seul.org/or/dev/Jul-2008/msg00034.html">la liste de
205 
+diffusion des développeurs</a> et inclue potentiellement 7 changements de
206 
+conception devant être débattus. Certaines évaluations (les mesures de
207 
+faible bande passante et le plan de grande échelle) nécessitent plus de
208 
+temps que prévu et doivent être planifiées après le livrable B. Le plan
209 
+actuel consiste à réaliser ces évaluations avant le 15 janvier et à
210 
+travailler avec des hypothèses avant la publication du résultat
211 
+final.</em></small>
212 
+  </td>
213 
+</tr>
214 
+
215 
+<tr bgcolor="#e5e5e5">
216 
+  <td>
217 
+    <a id="Aug08"></a> <a class="anchor" href="#Aug08">Août 2008</a>
218 
+  </td>
219 
+  <td>
220 
+    <small><em>Durant les 30 derniers jours, les 7 propositions de conception
221 
+ont été mieux évaluées et débattues. Quatre d'entre-elles se sont montrées
222 
+réalisables en terme de changement de code et de respect de l'anonymat. Une
223 
+a été classée comme bug plutôt que comme changement de conception. Deux ont
224 
+dû être exclues car elles menaient à des problèmes de sécurité ou à des
225 
+incertitudes dans l'amélioration des performances.</em></small> <br/>
226 
+<small><em> Selon les résultats du 15 juillet, la phase de conception est
227 
+terminée. Les tâches à venir pour la phase d'implémentation sont maintenant
228 
+clairement définies: un bug doit être corrigé et quatre changements de
229 
+conception doivent être implémentés. De plus, il faudra réaliser des
230 
+évaluations des changements de conception afin de vérifier leur utilité. Un
231 
+<a
232 
+href="http://freehaven.net/~karsten/hidserv/design-2008-08-15.pdf">rapport</a>
233 
+contenant les résultats de la phase de conception a été publié sur <a
234 
+href="http://archives.seul.org/or/dev/Aug-2008/msg00025.html">la liste de
235 
+diffusion des développeurs</a>.</em></small>
236 
+  </td>
237 
+</tr>
238 
+
239 
+<tr>
240 
+  <td>
241 
+    <a id="Sep08"></a> <a class="anchor" href="#Sep08">Septembre 2008</a>
242 
+  </td>
243 
+  <td>
244 
+    <small><em>Durant la première moitié de la phase d'implémentation, deux bugs
245 
+relatifs aux services cachés ont pu être corrigés: <a
246 
+href="http://bugs.noreply.org/flyspray/index.php?do=details&amp;id=767">le
247 
+premier</a> avait déjà été identifié dans la phase de conception et était
248 
+responsable d'un grand taux d'échec lors de la mise en place du service
249 
+caché dans le système. Le <a
250 
+href="http://bugs.noreply.org/flyspray/index.php?id=814&amp;do=details">second
251 
+bug</a> a été trouvé pendant la phase d'implémentation et était responsable
252 
+des echecs de connexions à un service caché actif. Ces deux corrections
253 
+seront livrées dans la prochaine version instable et probablement incluses
254 
+dans une des prochaines versions stables.</em></small> <br/> <small><em>Les
255 
+quatre changements de conception qui ont été proposés ont été implémentés
256 
+dans <a
257 
+href="https://tor-svn.freehaven.net/svn/tor/branches/hidserv-design-changes/">une
258 
+branche expérimentale</a> de l'arbre de développement non-stable. Les
259 
+premiers tests fonctionnels montrent que ces changements fonctionnent et
260 
+permettent de meilleures performances (ressenties). Cela doit être confirmé
261 
+au cours des prochaines quatre semaines lors des tests internes. Le prochain
262 
+objectif est de de préparer une version de cette branche expérimentale
263 
+pouvant être livrée à des beta-testeurs au début de la prochaine phase de
264 
+tests.</em></small>
265 
+  </td>
266 
+</tr>
267 
+
268 
+<tr bgcolor="#e5e5e5">
269 
+  <td>
270 
+    <a id="Oct08"></a> <a class="anchor" href="#Oct08">Octobre 2008</a>
271 
+  </td>
272 
+  <td>
273 
+    <small><em>La phase d'implémentation est terminée. Les corrections de bugs
274 
+trouvés lors des 30 derniers jours ont été ajoutées dans la version de
275 
+développement <a
276 
+href="http://archives.seul.org/or/talk/Oct-2008/msg00093.html">0.2.1.6-alpha</a>.
277 
+Les quatre changements de conception qui ont été identifiés lors de la phase
278 
+de conception ont été décrits dans <a
279 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/155-four-hidden-service-improvements.txt">la
280 
+proposition 155</a>.  Trois changements de conception ont été ajoutés au
281 
+code de développement et seront automatiquement injectés dans la prochaine
282 
+version de développement. Les deux premiers améliorent l'établissement de la
283 
+connexion à un service caché en réduisant le temps nécessaire à cette
284 
+opération de 60 à 30 secondes tout en lançant un deuxième essai en parallèle
285 
+après 15 secondes. Le troisième changement concerne la publication d'un
286 
+service caché dans le réseau en annonçant le service à 5 au lieu de 3 points
287 
+dans le réseau en parallèle et en considérant la publication valide dès que
288 
+les 3 points sont atteints. Maintenant, il n'y a  plus de bugs ni de
289 
+nouveaux concepts. Tous les changements sont dans le code source et peuvent
290 
+être testés dans la prochaine phase.</em></small>
291 
+  </td>
292 
+</tr>
293 
+
294 
+<tr>
295 
+  <td>
296 
+    <a id="Nov08"></a> <a class="anchor" href="#Nov08">Novembre 2008</a>
297 
+  </td>
298 
+  <td>
299 
+    <small><em>Les améliorations de performance qui ont été implémentés lors de
300 
+la dernière phase ont été livrés dans la version 0.2.1.7-alpha de Tor. Les
301 
+utilisateurs peuvent télécharger cette version de développement depuis la
302 
+page d'accueil de Tor et tester ainsi les améliorations au prix d'un effort
303 
+minime. De plus, deux corrections de bugs (<a
304 
+href="http://bugs.noreply.org/flyspray/index.php?id=767&amp;do=details">1</a>,
305 
+<a
306 
+href="http://bugs.noreply.org/flyspray/index.php?id=814&amp;do=details">2</a>)
307 
+qui avaient été découverts au cours de ce projet ont été rétroportées dans
308 
+la branche stable et seront incluses dans la prochaine version stable
309 
+0.2.0.31.</em></small> <br/> <small><em>L'objectif principal des 31 derniers
310 
+jours s'est concentré sur de nouvelles mesures afin de vérifier l'état des
311 
+améliorations.  Les mesures se sont déroulées sur deux jours entre le 6 et
312 
+le 8 novembre. Malheureusement, le réseau Tor a connu un problème sérieux
313 
+pendant cette période: un certificat périmé d'une autorité d'annuaire a
314 
+provoqué un grande quantité de trafic au sein du réseau Tor ce qui a <a
315 
+href="http://archives.seul.org/or/talk/Nov-2008/msg00053.html">forcé un
316 
+grand nombre d'opérateurs à fermer leur relais</a>. Une seconde mesure a été
317 
+réalisée entre le 13 et le 15. Les données brutes sont disponibles <a
318 
+href="http://freehaven.net/~karsten/hidserv/perfdata-2008-11-13.tar.gz">ici</a>
319 
+(40Mo). Néanmoins, les résultats montrent que les performances globales du
320 
+réseau sont encore plus mauvaises qu'au mois de juin 2008, date de la
321 
+première mesure sur les services cachés. C'est visible quand on observe les
322 
+requêtes vers les annuaires Tor qui n'ont pas été touchées par les
323 
+améliorations et qui montrent une performance plus mauvaise
324 
+qu'auparavant. Les effets sur l'amélioration des performances sont bien
325 
+visibles même si les valeurs absolues ne sont pas comparables pour le
326 
+moment. De nouvelles mesures seront lancées en décembre dans l'espoir de
327 
+réduire les effets de ce problème.</em></small> <br/> <small><em>De plus, il
328 
+y a peut-être un <a
329 
+href="http://bugs.noreply.org/flyspray/index.php?id=847&amp;do=details">bug</a>
330 
+dans la manière dont Tor télécharge les informations d'annuaire pendant
331 
+l'amorçage. Même si cela n'est pas lié aux services cachés, une amélioration
332 
+de ce côté profiterait quand même à ces derniers. Une partie du travail pour
333 
+les 30 jours à venir concernera ce bug.  </em></small>
334 
+  </td>
335 
+</tr>
336 
+
337 
+<tr bgcolor="#e5e5e5">
338 
+  <td>
339 
+    <a id="Dec08"></a> <a class="anchor" href="#Dec08">Décembre 2008</a>
340 
+  </td>
341 
+  <td>
342 
+    <small><em>Une partie des 30 derniers jours a été consacrée à la correction
343 
+de bugs qui ont influencé les dernières mesures sur les services cachés. La
344 
+première <a
345 
+href="http://archives.seul.org/or/cvs/Nov-2008/msg00100.html">correction</a>
346 
+efface un problème d'erreur de segmentation reponsable en grande partie de
347 
+nombreux échecs de mesures. Un autre <a
348 
+href="https://bugs.torproject.org/flyspray/index.php?id=847&amp;do=details">bug</a>
349 
+était responsable du délai important dans l'amorçage: les autorités
350 
+d'annuaire lentes occupaient pendant longtemps l'amorçage des clients avant
351 
+que ces derniers abandonnent et utilisent une nouvelle autorité. Par
352 
+conséquent, nous avons alloué davantage de bande passante aux deux plus
353 
+lentes autorités d'annuaire, de manière à réduire ces désagréments. Un
354 
+troisième <a
355 
+href="https://bugs.torproject.org/flyspray/index.php?id=874&amp;do=details">bug</a>
356 
+a été introduit avec l'amélioration des performances des services cachés de
357 
+novembre. L'effet entraîné était que les processus Tor qui faisaient tourner
358 
+des services cachés arrêtaient d'annoncer ces services lors de
359 
+l'actualisation de leur configuration. De plus, ce bug a révélé que Tor
360 
+recréait ces points d'introduction à chaque actualisation ce qui pouvait
361 
+affecter la stabilisation des services cachés. Ce bug a été corrigé et sera
362 
+inclus dans la version 0.2.1.9-alpha à venir.</em></small> <br/>
363 
+<small><em>En dehors de la correction de bugs, de nouvelles mesures ont été
364 
+effectuées entre le 8 et le 10 décembre. Elles seront probablement les
365 
+dernières pour comparer les performances actuelles des services cachés avec
366 
+celles du début du projet. Les données n'ont pas complètement été évaluées,
367 
+il est donc difficile de faire un jugement sur ces améliorations à ce
368 
+stade. Toutefois, une <a
369 
+href="http://freehaven.net/~karsten/hidserv/prelimreport-2008-12-15.pdf">analyse
370 
+préliminaire</a> montre que les temps de publication des services ont été
371 
+largement améliorés. C'est le résultat d'un amorçage plus rapide des clients
372 
+et des améliorations ajoutées en novembre. En revanche, les résultats
373 
+concernant l'établissement des connexions vers un service caché sont moins
374 
+prometteurs. Un exemple est la récupération des descripteurs de services
375 
+afin de rentrer en contact avec un service caché. Une explication possible
376 
+est que l'augmentation soudaine du nombre de noeuds d'annuaire de services
377 
+cachés au cours du mois de septembre a eut un effet négatif sur les
378 
+performances. Une partie du travail de ces 31 derniers jours consistera à
379 
+évaluer plus finement ces données et à rendre une conclusion sur
380 
+l'achèvement de ce projet.</em></small>
381 
+  </td>
382 
+</tr>
383 
+
384 
+<tr>
385 
+  <td>
386 
+    <a id="Jan09"></a> <a class="anchor" href="#Jan09">Janvier 2009</a>
387 
+  </td>
388 
+  <td>
389 
+    <small><em>La phase de test est terminée. Ces tests ont été menés en tant
390 
+que phase de beta-test publique incluant tout les changements concernant les
391 
+service cachés dans la série 0.2.1.x-alpha. Suite à ces tests, deux bugs ont
392 
+été identifiés, il peuvent d'ores et déjà être corrigés.</em></small> <br/>
393 
+<small><em>Les autres tests ont servi de mesures et ont été menés en
394 
+décembre. Une <a
395 
+href="http://freehaven.net/~karsten/hidserv/comparison-2009-01-15.pdf">comparaison</a>
396 
+des mesures effectuées successivement en juin et en décembre a montré que
397 
+les changements dûs à ce projet sont efficaces. En moyenne, le temps de
398 
+publication du service est passé de 2 minutes 12 à 58 secondes. Cette
399 
+amélioration dépasse les attentes. Grâce à cette amélioration, il est
400 
+également envisageable de réduire le temps de stabilisation de 30 secondes à
401 
+une valeur plus faible dans le futur. Toutefois, l'établissement de la
402 
+connexion reste aux alentours de 56 secondes entre la requête et la
403 
+connexion au serveur caché.  La principale cause de ce problème est le
404 
+passage d'un stockage centralisé des descripteurs de services cachés à une
405 
+forme décentralisée.  Cet effet de détérioration de la distribution de
406 
+l'annuaire des services cachés n'avait pas été envisagé jusqu'à présent. Un
407 
+travail futur devrait se focaliser sur l'amélioration du téléchargement de
408 
+l'annuaire distribué des services cachés par exemple, en parallélisant les
409 
+requêtes.</em></small> <br/> <small><em>Ce rapport est le dernier de la
410 
+série.  Le déploiement de la série 0.2.1.x qui inclue les améliorations des
411 
+services cachés devrait se dérouler dans les prochaines semaines ou
412 
+prochains mois.</em></small>
413 
+  </td>
414 
+</tr>
415 
+</table>
416 
+
417 
+<!-- Do we want a people section? If so, would it make sense to write what
418 
+these people will be doing? And what exactly are these people going to
419 
+do? :)
420 
+<a id="People">
421 
+</a>
422 
+<h2><a class="anchor" href="#People">People</a></h2>
423 
+<ul>
424 
+<li><a href="<page about/people>#Core">Karsten Loesing</a></li>
425 
+<li><a href="<page about/people>#Core">Steven Murdoch</a></li>
426 
+</ul>
427 
+-->
428 
+<br /> <a id="Links"></a>
429 
+<h2><a class="anchor" href="#Links">Liens</a></h2>
430 
+<ul>
431 
+<li>Papier de recherche sur <b>Mesures de performance et de statistiques sur les
432 
+services cachés Tor</b> (<a
433 
+href="http://www.uni-bamberg.de/fileadmin/uni/fakultaeten/wiai_lehrstuehle/praktische_informatik/Dateien/Publikationen/loesing2008performance.pdf">PDF</a>)
434 
+par Karsten Loesing, Werner Sandmann, Christian Wilms, and Guido Wirtz. Dans
435 
+the Proceedings of the 2008 International Symposium on Applications and the
436 
+Internet (SAINT), Turku, Finlande juillet 2008.</li>
437 
+
438 
+
439 
+
440 
+<!-- In the future, put links to proposal, preliminary results, etc. here -->
441 
+</ul>
442 
+
443 
+</div>
444 
+
445 
+
446 
+
447 
+#include <foot.wmi>
projects/fr/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,199 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22186 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="Tor Projects Page" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Aperçu général des projets dans Tor</h2>
17 
+<hr/>
18 
+
19 
+<p>L'écosystème du projet Tor est riche d'une grande variété de projets,
20 
+certains gérés par les développeurs centraux de Tor et d'autres, par des
21 
+volontaires. Cette page tente d'organiser et de lister ces projets afin
22 
+d'aider à la fois les nouveaux contributeurs développeurs à se lancer et
23 
+également pour être sûr que personne ne se lance dans les mêmes tâches.</p>
24 
+
25 
+<p>En construction ! Merci de votre patience...</p>
26 
+
27 
+<a id="Controllers"></a>
28 
+<h3><a class="anchor" href="#Controllers">Les controleurs Tor</a></h3>
29 
+<ul>
30 
+<li><a href="<page vidalia/index>">Vidalia</a> est notre interface graphique
31 
+multi-plateforme de contrôle recommandée, maintenue par Matt Edman. Ce
32 
+contrôleur est inclus dans la plupart des packs.</li>
33 
+<li><a href="http://www.anonymityanywhere.com/tork/">TorK</a> est un contrôleur
34 
+écrit par Robert Hogan pour l'environnement KDE (Linux). Il dispose de
35 
+quelques fonctionnalités supplémentaires par rapport à Vidalia (comme la
36 
+possibilité de définir les chemins) mais il est moins fin sur les autres.</li>
37 
+<li><a href="http://www.atagar.com/arm/">arm</a> est un contrôleur en ligne de
38 
+commande basé sur curses spécifiquement conçu pour résumer les opérations de
39 
+relais.</li>
40 
+<li><a href="https://svn.torproject.org/svn/blossom/trunk/">Blossom</a> est un
41 
+contrôleur obsolete et non maintenu issu de la thèse de Geoff Goodell à
42 
+Harvard. Son objectif était d'offrir un accès plus efficace aux ressources
43 
+depuis l'emplacement réseau de votre choix.</li>
44 
+</ul>
45 
+
46 
+<a id="Applications"></a>
47 
+<h3><a class="anchor" href="#Applications">Applications supplémentaires</a></h3>
48 
+<ul>
49 
+<li><a href="<page torbutton/index>">TorButton</a> est une extension Firefox qui
50 
+vous permet de surfer de manière sécurisée avec Tor. A l'origine, elle
51 
+s'occupait juste d'activer ou non vos paramètres de proxy, mais maintenant,
52 
+elle gère <a href="https://www.torproject.org/torbutton/design/">une large
53 
+gamme</a> de fuites.</li>
54 
+<li><a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> est un
55 
+proxy-cache http qui gère le pipelining et http/1.1. Nous l'incluons avec
56 
+Firefox et Torbutton essentiellement car Firefox ne peut toujours pas <a
57 
+href="https://bugzilla.mozilla.org/show_bug.cgi?id=280661">gérer</a> les
58 
+proxy socks directement.</li>
59 
+<li><a href="http://www.privoxy.org/">Privoxy</a> est un autre proxy http que
60 
+vous pouvez utiliser entre votre Firefox et Tor. Nous avons basculé vers
61 
+Polipo essentiellement en raison de son support d'http/1.1 et des sessions
62 
+continues.</li>
63 
+<li><a href="http://code.google.com/p/torsocks/">torsocks</a> (basé sur son
64 
+prédécesseur <a href="http://tsocks.sourceforge.net/">tsocks</a>) est un
65 
+conteneur réseau sous Linux / UNIX (mais pas sous OS X) qui remplace
66 
+dynamiquement les appels systèmes réseaux vers des connexions pointant sur
67 
+Tor.</li>
68 
+<li><a href="http://monkey.org/~dugsong/dsocks/">dsocks</a> est une alternative
69 
+à tsocks qui fonctionne sous OS X / BSD.</li>
70 
+<li><a href="https://git.torproject.org/checkout/thandy/master/">Thandy</a>,
71 
+notre <a
72 
+href="http://google-opensource.blogspot.com/2009/03/thandy-secure-update-for-tor.html">programme
73 
+de mise à jour sécurisé</a> (toujours en développement) est conçu pour aider
74 
+les utilisateurs à maintenir leur version de Tor à jour. Alors que les
75 
+organisations commerciales concentrent leurs moyens de mise à jour dans des
76 
+coffres forts, Thandy a pour objectif de mieux aborder l'environnement
77 
+distribué de Tor. Son principal avantage à l'heure actuelle est la revue
78 
+d'hôtes (<a
79 
+href="https://git.torproject.org/checkout/thandy/master/specs/thandy-spec.txt">spec</a>),
80 
+mais vous pouvez également le voir en action dans notre <a
81 
+href="https://data.peertech.org/files/demo/updater/index.html">installeur
82 
+réseau expériment</a>.</li>
83 
+</ul>
84 
+
85 
+<a id="Installers"></a>
86 
+<h3><a class="anchor" href="#Installers">Installeurs</a></h3>
87 
+<ul>
88 
+<li>TBB, TBB-for-Linux</li>
89 
+<li>debs, rpms</li>
90 
+<li>osx image</li>
91 
+<li>torvm</li>
92 
+<li>orbot</li>
93 
+<li>live cd: <a href="https://amnesia.boum.org/">Le système live (Amnesic)
94 
+Incognito</a>, tor ramdisk</li>
95 
+</ul>
96 
+
97 
+<a id="Implementations"></a>
98 
+<h3><a class="anchor" href="#Implementations">Implémentations alternatives de
99 
+Tor</a></h3>
100 
+<ul>
101 
+<li>xmux's thing</li>
102 
+<li>onioncoffee</li>
103 
+<li>tortunnel</li>
104 
+<li>jap?</li>
105 
+</ul>
106 
+
107 
+<a id="Listings"></a>
108 
+<h3><a class="anchor" href="#Listings">Listes de relais</a></h3>
109 
+<ul>
110 
+<li>torstatus</li>
111 
+<li>xenobite's torstatus</li>
112 
+<li>check.torproject.org</li>
113 
+<li>bulk exitlist</li>
114 
+<li>tordnsel</li>
115 
+<li>moria1's v3 votes export</li>
116 
+</ul>
117 
+
118 
+<a id="Monitoring"></a>
119 
+<h3><a class="anchor" href="#Monitoring">Surveillance du Réseau</a></h3>
120 
+<ul>
121 
+<li>weather</li>
122 
+<li><a href="http://metrics.torproject.org/">Projet Metrics: Mesurer le réseau
123 
+Tor</a></li>
124 
+<li>torperf</li>
125 
+<li>archives</li>
126 
+<li>https://svn.torproject.org/svn/projects/archives/trunk/exonerator/HOWTO</li>
127 
+</ul>
128 
+
129 
+<a id="Performance"></a>
130 
+<h3><a class="anchor" href="#Performance">Performance du réseau</a></h3>
131 
+<ul>
132 
+<li>whytorisslow</li>
133 
+<li>torflow</li>
134 
+<li>bwauthority</li>
135 
+<li>exitscanner</li>
136 
+<li>NLnet: <a href="<page projects/hidserv>">Améliorer les performances des
137 
+services cachés</a></li>
138 
+<li>udp-tor: joel, chris, ian, etc</li>
139 
+<li>NLnet: <a href="<page projects/lowbandwidth>">Tor pour les clients à faible
140 
+bande passante</a></li>
141 
+</ul>
142 
+
143 
+<a id="Censorship"></a>
144 
+<h3><a class="anchor" href="#Censorship">Résistance à la Censure</a></h3>
145 
+<ul>
146 
+<li>gettor</li>
147 
+<li>bridgedb</li>
148 
+<li>bridge distribution strategies</li>
149 
+<li>obfuscaTOR</li>
150 
+</ul>
151 
+
152 
+<a id="Libraries"></a>
153 
+<h3><a class="anchor" href="#Libraries">Bibliothèques des contrôleurs</a></h3>
154 
+<ul>
155 
+<li>torctl</li>
156 
+<li>Les bibliothèques de contrôleurs Java et c#</li>
157 
+</ul>
158 
+
159 
+<a id="Infrastructure"></a>
160 
+<h3><a class="anchor" href="#Infrastructure">Infrastructure</a></h3>
161 
+<ul>
162 
+<li>bug tracker (flyspray)</li>
163 
+<li>blog</li>
164 
+<li>wiki</li>
165 
+<li>pootle, translation.tp.o</li>
166 
+<li>buildbot https://buildbot.vidalia-project.net/one_line_per_build</li>
167 
+<li>https://data.peertech.org/torbld</li>
168 
+<li>tor mirrors</li>
169 
+<li>rsync</li>
170 
+<li>a nagios?</li>
171 
+<li>git, svn</li>
172 
+<li>gitweb</li>
173 
+</ul>
174 
+
175 
+<a id="HiddenServices"></a>
176 
+<h3><a class="anchor" href="#HiddenServices">Services Cachés</a></h3>
177 
+<ul>
178 
+<li>Schéma de leur fonctionnement</li>
179 
+<li>tor2web</li>
180 
+<li>onioncat</li>
181 
+<li>shallot</li>
182 
+</ul>
183 
+
184 
+<a id="Other"></a>
185 
+<h3><a class="anchor" href="#Other">Autre</a></h3>
186 
+<ul>
187 
+<li>puppetor</li>
188 
+<li>torwall</li>
189 
+<li>topf</li>
190 
+<li>nym</li>
191 
+<li>nymble</li>
192 
+<li>extension firefox de foebud</li>
193 
+</ul>
194 
+
195 
+</div>
196 
+
197 
+
198 
+
199 
+#include <foot.wmi>
projects/fr/lowbandwidth.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,370 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22051 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="NLnet Project: Tor for Low Bandwidth Clients" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Projet NLNet: Tor pour les clients à faible bande passante:</h2>
17 
+<hr />
18 
+
19 
+<p>
20 
+Le système d'anonymat Tor est pour l'instant utilisable uniquement pour les
21 
+utilisateurs Internet qui disposent d'une connexion avec une bande passante
22 
+large. Dès le démarrage du client Tor, un fichier volumineux contenant la
23 
+description de tous les serveurs Tor est téléchargé. Ce fichier est celui
24 
+qui est appelé l'Annuaire Tor et permet au client de choisir parmi la
25 
+multitude de serveurs disponibles dans le réseau Tor. Le téléchargement de
26 
+l'intégralité de l'Annuaire Tor est indispensable dans le protocole Tor
27 
+actuellement employé. Ce fichier est trop volumineux pour les utilisateurs
28 
+de lignes modem ou pour les réseaux mobiles de données comme le GPRS car le
29 
+chargement initial qui est lancé à chaque fois que l'utilisateur se connecte
30 
+prend de 10 à 30 minutes sur une ligne lente. En conséquence, Tor n'est pas
31 
+utilisable sur les personnes utilisant une ligne modem ou une ligne
32 
+mobile. L'un des objectifs majeurs du projet Tor est de fournir un accès
33 
+Internet anonyme et sécurisé aux utilisateurs vivants dans les états
34 
+répréssifs et dictatoriaux. Ces lieux ont souvent des connexion à Internet
35 
+lentes, soit par modem soit à cause de la faiblesse des liens vers le reste
36 
+du monde. En permettant à ces utilisateurs d'utiliser le réseau Tor, un
37 
+progrès significatif sera réalisé pour la libre information dans ces pays.
38 
+</p>
39 
+
40 
+<p>
41 
+Pour rendre Tor utilisable également par les utilisateurs ayant une
42 
+connexion à faible bande passante, une évolution du protocole Tor est
43 
+indispensable en vue de réduire la taille du téléchargement initial. Cette
44 
+nouvelle version du protocole devrait modifier le moyen pour le client de
45 
+recevoir l'information nécéssaire à l'établissement d'un circuit Tor de
46 
+manière à ce qu'elle puisse être récupérée en environ trois minutes par une
47 
+ligne modem à 14,4Kbps. Le travail à fournir à partir de cette proposition a
48 
+l'objectif final de rendre le changement de protocole en production et
49 
+propagé à l'ensemble des utilisateurs Tor dans un pas de temps de moins de
50 
+12 mois. Le logiciel résultant sera publié sous licence BSD 3-Clause comme
51 
+le reste du code source de Tor. Tous les livrables seront entièrement
52 
+publics.
53 
+</p>
54 
+
55 
+<p>
56 
+Ce projet est généreusement financé par:
57 
+</p>
58 
+
59 
+<p>
60 
+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html"> <img
61 
+src="$(IMGROOT)/nlnet-160x60.png" alt="La fondation NLnet" /></a>
62 
+</p>
63 
+
64 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
65 
+<thead>
66 
+<tr>
67 
+<th><big>Projet</big></th>
68 
+<th><big>Date de rendu</big></th>
69 
+</tr>
70 
+</thead>
71 
+
72 
+<tr bgcolor="#e5e5e5">
73 
+  <td>
74 
+    <b>Livrable A:</b> Fonctionnalités et évaluation du changement de
75 
+protocole<br /><small><em>Ce livrable couvre le design détaillé et
76 
+l'évaluation basée sur une simulation des changements nécessaires et des
77 
+modifications de fonctionnalités du protocole Tor actuel.  Les changements
78 
+dans le protocole seront relativement substantiels, ils nécessitent donc une
79 
+évaluation prudente sur les possibles répercussions en terme de sécurité et
80 
+d'anonymat sur le réseau Tor. Une période de deux mois est planifiée pour
81 
+cette phase de design et d'évaluation qui conclura à une évaluation
82 
+intensive par les utilisateurs. Une partie du livrable A sera une définition
83 
+d'objectif de performance pour la phase d'implémentation. L'objectif de
84 
+design est de réduire la taille de l'annuaire Tor qu'il faut télécharger aux
85 
+environ de 300Ko ce qui permettra à un utilisateur sur une ligne à 14,4kbps
86 
+de le télécharger en environ trois minutes. Il y aura peut-être des écarts
87 
+par rapport à cet objectif pour des raisons de maintien d'anonymat et de
88 
+sécurité, mais ce chiffre est bien celui à atteindre.  </em></small>
89 
+  </td>
90 
+  <td>
91 
+    15 juillet 2008
92 
+  </td>
93 
+</tr>
94 
+
95 
+<tr>
96 
+  <td>
97 
+    <b>Livrable B:</b>Implémentation du changement de protocole<br />
98 
+<small><em>Après le design, l'évaluation et le test utilisateur, les
99 
+modifications doivent être implémentées et intégrées dans la base actuelle
100 
+du code source de Tor. Cette implémentation prendra approximativement trois
101 
+mois.  </em></small>
102 
+  </td>
103 
+  <td>
104 
+    15 octobre 2008
105 
+  </td>
106 
+</tr>
107 
+
108 
+<tr bgcolor="#e5e5e5">
109 
+  <td>
110 
+    <b>Livrable C:</b>Tests<br /> <small><em>Étant donné que la modification est
111 
+hautement critique en terme de sécurité et de maintient d'anonymat pour le
112 
+réseau Tor, elle requière des tests et du debugging en conditions de
113 
+laboratoire et en conditions réelles. Une période de trois mois est
114 
+planifiée pour ces opérations où le développeur responsable est dévolu à ce
115 
+travail à 1/3 de son temps. Une partie de la phase de tests sera une période
116 
+de version beta publique.  </em></small>
117 
+  </td>
118 
+  <td>
119 
+    15 janvier 2009
120 
+  </td>
121 
+</tr>
122 
+
123 
+<tr>
124 
+  <td>
125 
+    <b>Livrable D:</b> Déploiement<br /> <small><em>Le déploiement vers le
126 
+serveur Tor sur le réseau sera mené en lien avec le calendrier des versions
127 
+régulières de Tor. Étant donné que ce calendrier dépend d'un certain nombre
128 
+de facteurs externes tels que l'état des autres projets logiciels devant
129 
+être incorporés dans la version, la date de livraison de la version actuelle
130 
+et celle où les modifications auront été complètement acceptées et
131 
+installées par la majorité des opérateurs de serveurs Tor peuvent
132 
+varier. D'expérience, on peut s'attendre à une période de trois à quatre
133 
+mois. Le déploiement sera intégré au processus de versions régulières de Tor
134 
+qui est une activité continue réalisée par des volontaires et du personnel
135 
+payés grâce aux dons au projet Tor.  </em></small>
136 
+  </td>
137 
+  <td>
138 
+    15 avril 2009
139 
+  </td>
140 
+</tr>
141 
+</table>
142 
+
143 
+<br /> <a id="Reports"></a>
144 
+<h2><a class="anchor" href="#Reports">Rapports mensuels d'avancement</a></h2>
145 
+<p>
146 
+Il y aura au total huit rapports mensuels d'état qui commenceront avec le
147 
+premier livrable aux alentours du 15 juillet 2008 et se termineront avec la
148 
+fin de l'implémentation et des tests aux alentours du 15 janvier 2009.
149 
+</p>
150 
+
151 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
152 
+<thead>
153 
+<tr>
154 
+<th><big>Mois,</big></th>
155 
+<th><big>Rapport d'avancement</big></th>
156 
+</tr>
157 
+</thead>
158 
+
159 
+<tr bgcolor="#e5e5e5">
160 
+  <td>
161 
+    <a id="Jun08"></a> <a class="anchor" href="#Jun08">Juin 2008</a>
162 
+  </td>
163 
+  <td>
164 
+    <small><em>Nous avons effectué les premières mesures sur l'amorçage des
165 
+clients Tor. Les résultats ne sont pas très surprenants: un client récupère
166 
+environ 10ko de certificats, un document de consensus pour 140Ko (maintenant
167 
+90Ko voir le paragraphe suivant) et environ 1,5Mo de descripteurs de serveur
168 
+(la construction des circuits démarre dès la moitié de ce
169 
+téléchargement).</em></small> <br /> <small><em><a
170 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/138-remove-down-routers-from-consensus.txt">La
171 
+proposition 138</a> réduit la taille des documents de consensus de 30 à 40%
172 
+et a déjà été implémentée et intégrée dans la
173 
+spécification. L'implémentation fait partie de la branche 0.2.1.x-alpha et
174 
+le code source prendra effet une fois que plus des deux-tiers des autorités
175 
+d'annuaire (soit 5 sur 6) auront été mises à jour.</em></small> <br />
176 
+<small><em><a
177 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">La
178 
+proposition 140</a> n'est pas directement liée à la réduction du volume à
179 
+télécharger au démarrage mais essaye au contraire de rendre le
180 
+téléchargement des nouveaux documents de consensus moins volumineux. Elle a
181 
+été rédigée et <a
182 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00013.html">envoyée sur la
183 
+liste de diffusion or-dev</a>. Il y a quelques questions qui doivent d'abord
184 
+être réglées par les autres développeurs Tor mais le reste me semble correct
185 
+et pourrait-être implémenté.</em></small> <br /> <small><em>Le gros du
186 
+projet est de faire en sorte que les clients ne doivent plus télécharger
187 
+1,5Mo de descripteurs de serveurs. <a
188 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">La
189 
+proposition 141</a> a été <a
190 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00017.html">envoyée sur la
191 
+liste de diffusion or-dev</a>. Pour le moment, j'y vois 3 choses à faire:
192 
+déplacer l'information sur l'équilibrage de charge dans le consensus (pas
193 
+trop complexe), mettre en place un dispositif pour que les clients Tor
194 
+puissent récupérer des descripteurs de serveurs à la demande depuis les
195 
+routeurs lorsqu'ils élaborent leur circuit (décrit dans le brouillon) et
196 
+enfin, gérer la sélection des sorties. Nous sommes toujours en cours de
197 
+réflexion concernant la dernière partie; quelques possibilités sont
198 
+mentionnées dans le brouillon.</em></small>
199 
+  </td>
200 
+</tr>
201 
+
202 
+<tr>
203 
+  <td>
204 
+    <a id="Jul08"></a> <a class="anchor" href="#Jul08">Juillet 2008</a>
205 
+  </td>
206 
+  <td>
207 
+    <small><em>Le travail sur <a
208 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">la
209 
+proposition 141</a> avance: Il y a deux idées simples pour déplacer
210 
+l'information de répartition de charge dans le consensus: l'une est basée
211 
+sur les autorités générant les poids que les clients peuvent utiliser et
212 
+mettre dans le consensus, l'autre approche consiste à y insérer directement
213 
+l'information de bande passante depuis le descripteur de serveur.  La
214 
+dernière option est probablement la plus abordable lorsqu'on étudie
215 
+également <a
216 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">la
217 
+proposition 140</a>. Cette dernière évite d'avoir trop d'éléments fluctuants
218 
+dans le consensus.</em></small> <br /> <small><em>Pour la gestion de la
219 
+politique de sortie, <a
220 
+href="http://archives.seul.org/or/dev/Jul-2008/msg00022.html">un post de la
221 
+liste de diffusion or-dev</a> suggère l'ajout d'un hash d'identification de
222 
+la politique de sortie du noeud soit ajouté au document de consensus.
223 
+L'ajout dans le consensus de 160 bits à haute entropie par noeud est risqué
224 
+mais nous pensons que puisque les politiques de sortie sont souvent
225 
+identiques, le document de consensus devrait se compresser correctement.
226 
+Nous attendons les mesures sur ce sujet.</em></small>
227 
+  </td>
228 
+</tr>
229 
+
230 
+<tr bgcolor="#e5e5e5">
231 
+  <td>
232 
+    <a id="Aug08"></a> <a class="anchor" href="#Aug08">Août 2008</a>
233 
+  </td>
234 
+  <td>
235 
+    <small><em>Les documents de vote des autorités d'annuaire et l'algorithme de
236 
+création de leur consensus ont été modifiés de manière à inclure
237 
+l'information sur la bande passante et les résumés des politiques de sorties
238 
+tels qu'indiqués dans la proposition 141.  Une fois que cinq des six
239 
+autorités en fonctionnement auront mis à jour leur base à la révision 16554,
240 
+le consensus commencera à inclure cette information.</em></small>
241 
+  </td>
242 
+</tr>
243 
+
244 
+<tr>
245 
+  <td>
246 
+    <a id="Sep08"></a> <a class="anchor" href="#Sep08">Septembre 08</a>
247 
+  </td>
248 
+  <td>
249 
+<small><em>Pas de mises à jour pour Septembre.</em></small>
250 
+  </td>
251 
+</tr>
252 
+
253 
+<tr bgcolor="#e5e5e5">
254 
+  <td>
255 
+    <a id="Oct08"></a> <a class="anchor" href="#Oct08">Octobre 08</a>
256 
+  </td>
257 
+  <td><p>
258 
+<small><em>Nous n'avons pas réussi à atteindre notre jalon "terminer
259 
+l'implémentation" ce mois-ci car le développeur principal du projet avait
260 
+trop de travail à mener. La bonne nouvelle est que nous avons réalisé une
261 
+grande partie du travail d'implémentation et il est en cours depuis
262 
+plusieurs mois maintenant (depuis le jalon d'août) et a donc déjà bénéficié
263 
+de nombreux tests. Les étapes restantes sont: faire en sorte que les relais
264 
+sachent comment récupérer les requêtes de demande de descripteurs à partir
265 
+de l'intérieur du circuit (nous allons probablement utiliser un nouveau type
266 
+de cellule pour ça de manière à éviter un aller-retour); puis de faire en
267 
+sorte que les clients puissent effectuer ces requêtes dès lors qu'ils sont
268 
+dans une version suffisamment récente. Ces deux étapes sont rédigées de
269 
+manière détaillée dans <a
270 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">la
271 
+Section 3.2 de la proposition 141</a>.</em></small></p>
272 
+
273 
+<p><small><em>Notre nouveau plan est de disposer de ces deux morceaux courant
274 
+novembre, et si cela se présente moins bien, alors nous procéderons à une
275 
+refonte plus radicale de notre planning et peut-être également sur le
276 
+design.</em></small></p>
277 
+
278 
+<p><small><em>Il y a d'autres composants que nous aimerions créer après
279 
+celui-ci: le premier auquel nous pensons consiste à télécharger des "diffs"
280 
+du dernier consensus: <a
281 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">140-consensus-diffs.txt</a>.
282 
+D'abord, cela pourrait consommer moins de bande passante ce qui est toujours
283 
+appréciable lorsque multiplié par le nombre total de clients, mais aussi,
284 
+cela signifie que nous pouvons utiliser cette bande passante pour récupérer
285 
+les diffs plus souvent que l'actuel "toutes les 3 ou 4 heures". Si les
286 
+clients récupère plus souvent les informations à jour des annuaires, ils
287 
+peuvent alors construire des chemins plus rapides car ils disposent
288 
+d'information plus fraîche sur la bande passante de chaque relais (ce qui
289 
+est lié avec le premier projet NLnet ci-dessus). La nouvelle idée importante
290 
+est que cela signifie également que nous gérons mieux les relais
291 
+transitoires: actuellement, un relais doit tourner depuis au moins 3 à 4
292 
+heures avant de voir des utilisateurs et cela met de côté un grand nombre de
293 
+volontaires qui désirent faire tourner un relais seulement quelques
294 
+heures.</em></small></p>
295 
+<p><small><em>La prochaine étape est de terminer l'implémentation de la
296 
+proposition 114 de manière à ce que nous puissions la faire tester par les
297 
+utilisateurs. Espérons que ce sera pour bientôt !</em></small></p>
298 
+  </td>
299 
+</tr>
300 
+
301 
+<tr>
302 
+  <td>
303 
+    <a id="Nov08"></a> <a class="anchor" href="#Nov08">Novembre 2008</a>
304 
+  </td>
305 
+  <td>
306 
+<p><small><em>Il semble que le plan original que nous avions mis en place pour
307 
+la dernière partie de développement était à la fois a) beaucoup plus
308 
+compliqué que prévu et b) heureusement très efficace comparé à ce dont nous
309 
+avions besoin.</em></small></p>
310 
+
311 
+<p><small><em> Roger a relancé la discussion sur le design sur la liste de
312 
+diffusion or-dev: <a
313 
+href="http://archives.seul.org/or/dev/Nov-2008/threads.html">http://archives.seul.org/or/dev/Nov-2008/threads.html</a>.</em></small></p>
314 
+
315 
+<p><small><em>Je pense que nous avons maintenant une meilleure vision des
316 
+options et des arbitrages: <a
317 
+href="http://archives.seul.org/or/dev/Nov-2008/msg00007.html">http://archives.seul.org/or/dev/Nov-2008/msg00007.html</a>.</em></small></p>
318 
+
319 
+<p><small><em>Nick a été enterré par d'autres projets de développement
320 
+(heureusement, ça devrait aller mieux pour le mois à venir) et je veux avoir
321 
+son opinion sur comment procéder. J'espère que nous retiendrons l'approche
322 
+la plus simple.</em></small></p>
323 
+
324 
+<p><small><em>Hélas, les approches très simples permettent moins
325 
+d'évolutivité. Néanmoins, je pense qu'elles feront des bouches-trous
326 
+corrects pour plus tard -- et comme on ne sait pas quand 'plus tard' arrive,
327 
+qui sait ce qui aura changé ?</em></small></p>
328 
+  </td>
329 
+</tr>
330 
+
331 
+<tr bgcolor="#e5e5e5">
332 
+  <td>
333 
+    <a id="Jan09"></a> <a class="anchor" href="#Jan09">Janvier 2009</a>
334 
+  </td>
335 
+  <td>
336 
+<p><small><em> J'ai rédigé une version plus détaillée de notre nouvelle idée de
337 
+design, sous la <a
338 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/158-microdescriptors.txt">proposition
339 
+Tor #158</a>, et la discussion a commencé ici: <a
340 
+href="http://archives.seul.org/or/dev/Jan-2009/msg00010.html">http://archives.seul.org/or/dev/Jan-2009/msg00010.html</a>.</em></small></p>
341 
+
342 
+<p><small><em> Je pense que nous en avons terminé ! (En fait, une fois que
343 
+j'aurais tenu compte de tous les commentaires.)  </em></small></p>
344 
+
345 
+<p><small><em> La raison principale du fait que le projet ne tienne pas le
346 
+calendrier prévu tient à la conclusion du <a href="<page
347 
+projects/hidserv>">projet de Karsten de la NLnet sur la performance des
348 
+services cachés</a>: le principal responsable est l'extension de
349 
+circuit. Pour le moment, ce projet a proposé d'ajouter davantage
350 
+d'aller-retours et de complexité sur ce sujet. Ainsi, il nous faut élaborer
351 
+un meilleur plan pour atteindre l'objectif final sans sacrifier encore plus
352 
+de performance.  </em></small></p>
353 
+
354 
+<p><small><em>Nous avons modifié la proposition de conception au cours des
355 
+semaines passées et je pense que nous serons bientôt prêts pour
356 
+l'implémentation. A noter qu'étant donné notre charge de travail en cours
357 
+sur le développement qui devrait s'étaler jusqu'à mi-février, il est
358 
+probable que cette implémentation ne sera mise en oeuvre qu'à partir de la
359 
+fin février ou pour mars. Cette fois, pour de bon !</em></small></p>
360 
+  </td>
361 
+</tr>
362 
+</table>
363 
+
364 
+<br />
365 
+
366 
+</div>
367 
+
368 
+
369 
+
370 
+#include <foot.wmi>
projects/fr/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/it/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,24 @@
1 
+## translation metadata
2 
+# Based-On-Revision: 20047
3 
+# Last-Translator: jan at seul . org
4 
+
5 
+#include "head.wmi" TITLE="Pagina dei progetti Tor"
6 
+
7 
+<div class="main-column">
8 
+
9 
+<!-- PUT CONTENT AFTER THIS TAG -->
10 
+
11 
+<h2>Indice dei progetti Tor</h2>
12 
+<hr/>
13 
+
14 
+<ul>
15 
+<li>NLnet <a href="<page projects/hidserv>">Accelerare i hidden services</a></li>
16 
+<li>NLnet <a href="<page projects/lowbandwidth>">Tor per client con banda lenta</a></li>
17 
+<li>Google <a href="<page projects/google>">Auto-aggiornamento per Tor</a></li>
18 
+<li><a href="http://metrics.torproject.org/">Metrics Project: Misurare la rete Tor</a></li>
19 
+</ul>
20 
+
21 
+</div><!-- #main -->
22 
+
23 
+#include <foot.wmi>
24 
+
projects/it/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/nl/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/no/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/pl/google.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,88 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22186 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="Google Project: Secure Upgrade of Tor" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Projekt Google: Bezpieczna aktualizacja Tora</h2>
17 
+
18 
+<hr />
19 
+
20 
+<p>
21 
+
22 
+
23 
+</p>
24 
+
25 
+<p>
26 
+Ten projekt jest hojnie sponsorowany przez <a
27 
+href="http://www.google.com">Google</a>.
28 
+</p>
29 
+
30 
+<a id="Timetable"></a>
31 
+<h2><a class="anchor" href="#Timetable">Plan</a></h2>
32 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
33 
+
34 
+
35 
+<!-- <thead>
36 
+
37 
+<tr bgcolor="#e5e5e5">
38 
+<th>Deliverable</th>
39 
+<th>Due Date</th>
40 
+</tr>
41 
+</thead> -->
42 
+<tr bgcolor="#e5e5e5">
43 
+  <td>
44 
+    <b>Kamień milowy 1:</b> Vidalia rozpoznaje, kiedy Tor musi zostać
45 
+zaktualizowany oraz dowiaduje się, jaka jest najnowsza odpowiednia wersja i
46 
+gdzie ją znaleźć.<br /> <small><em>Patrząc na podpisany przez większość
47 
+status sieci zdecyduje, kiedy aktualizować i do jakiej wersji (Tor już
48 
+wypisuje wersje uważane za bezpieczne w każdym dokumencie statusu
49 
+sieci)</em></small>
50 
+  </td>
51 
+  <td>
52 
+    15 Listopada 2008
53 
+  </td>
54 
+</tr>
55 
+
56 
+<tr>
57 
+  <td>
58 
+    <b>Kamień milowy 2:</b>Vidalia może pobrać nową wersję Tora z jego witryny i
59 
+sprawdzić jej podpis.<br /> <small><em>Aktualizacja albo przez Tora albo
60 
+przez protokół aktualizacji katalogu mirrorów (propozycja 127), jeśli
61 
+możliwe, dla dodatkowej prywatności. Sprawdzanie podpisów paczek w celu
62 
+upewnienia się co do ich wiarygodności.</em></small>
63 
+  </td>
64 
+  <td>
65 
+    15 Listopada 2008
66 
+  </td>
67 
+</tr>
68 
+
69 
+<tr bgcolor="#e5e5e5">
70 
+  <td>
71 
+    <b>Kamień milowy 3:</b> Vidalia ma interfejs powiadamiający użytkownika o
72 
+aktualizacjach i pomagający mu w aktualizacji. <br /> <small><em>Dajmy
73 
+użytkownikowi interfejs dla aktualizacji, łącznie z możliwością migracji na
74 
+kolejną dużą wersję Tora.  </em></small>
75 
+  </td>
76 
+  <td>
77 
+    15 Listopada 2008
78 
+  </td>
79 
+</tr>
80 
+</table>
81 
+
82 
+<br />
83 
+
84 
+</div>
85 
+
86 
+
87 
+
88 
+#include <foot.wmi>
projects/pl/hidserv.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,428 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22186 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="NLnet Project: Speed Up Tor Hidden Services" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Projekt NLnet: Przyspieszenie usług ukrytych Tora</h2>
17 
+<hr />
18 
+
19 
+<p>
20 
+Tor Hidden Services allow users to set up anonymous information services,
21 
+like websites, that can only be accessed through the Tor network and are
22 
+protected against identification of the host that runs the services.  The
23 
+most critical limitations of Tor Hidden Services are the time it takes until
24 
+a Hidden Service is registered in the network and the latency of contact
25 
+establishment when accessed by a user.  Due to design issues in the original
26 
+Tor protocol, the connection to a new Hidden Service can take several
27 
+minutes, which leads most users to give up before the connection has been
28 
+established.  Using Tor Hidden Services for direct interactive user-to-user
29 
+communication (e.g. messaging) is nearly impossible due to the high latency
30 
+of Hidden Service circuit setup.
31 
+</p>
32 
+
33 
+<p>
34 
+Celem tego projektu jest przyspieszenie usług ukrytych Tora poprzez
35 
+usprawnienie metody tworzenia obwodów między użytkownikiem a usługą, jak
36 
+również sposobu, w jaki usługa jest rejestrowana w sieci.  W pierwszym kroku
37 
+poprowadzone będą dokładne pomiary zachowania usług ukrytych w warunkach
38 
+laboratoryjnych i rzeczywistych, by znaleźć główne przyczyny opóźnień.
39 
+Opierając się na wynikach pomiarów, zaprojektowane i zweryfikowane będą
40 
+strategie optymalizacji niechcianych implikacji związanymi z bezpieczeństwem
41 
+i anonimowością sieci Tora.  Najbardziej obiecujące optymalizacje zostaną
42 
+zaimplementowane, by dać użytkownikom widoczny efekt. Dokładne pomiary
43 
+sukcesu zostaną stworzone w fazie diagnostyki, gdy już będzie jasne, gdzie
44 
+tracony jest czas i jakie ulepszenia są możliwe.  Ostatecznym celem jest
45 
+umożliwienie wprowadzenia zmian w protokole usług ukrytych i rozprowadzenia
46 
+ich wśród użytkowników Tora w przeciągu 12 miesięcy.
47 
+</p>
48 
+
49 
+<p>
50 
+Ten projekt jest hojnie sponsorowany przez:
51 
+</p>
52 
+
53 
+<p>
54 
+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html" ><img
55 
+src="$(IMGROOT)/nlnet-160x60.png" alt="Fundacja NLnet" /></a>
56 
+</p>
57 
+
58 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
59 
+<thead>
60 
+<tr>
61 
+<th><big>Projekt</big></th>
62 
+<th><big>Czas zakończenia</big></th>
63 
+</tr>
64 
+</thead>
65 
+
66 
+<tr bgcolor="#e5e5e5">
67 
+  <td>
68 
+    <b>Część A:</b> Analiza, pomiary i klaryfikacja problemu<br />
69 
+<small><em>Jako że usługi ukryte Tora nie były aktywnie rozwijane przez
70 
+około ostatni rok rozwoju Tora, niektóre aspekty tych problemów są nie do
71 
+końca zbadane. Należy przeprowadzić dogłębną analizę przyczyn strat czasu,
72 
+by znaleźć ich dokładne źródła. Część A będzie wymagać około miesiąca
73 
+pracy. Wyniki analizy wpłyną na decyzje projektowe, które zostaną podjęte w
74 
+Części B.</em></small>
75 
+  </td>
76 
+  <td>
77 
+    15 Czerwca 2008
78 
+  </td>
79 
+</tr>
80 
+
81 
+<tr>
82 
+  <td>
83 
+    <b>Część B:</b> Projektowanie i sprawdzanie niezbędnych zmian<br />
84 
+<small><em>Zmiany w usługach ukrytych wpłyną na podstawy funkcjonowania
85 
+protokołu i dlatego wymagają dokładnego sprawdzenia możliwych skutków dla
86 
+bezpieczeństwa i anonimowości. Na projekt i sprawdzanie przewidziany jest
87 
+dwumiesięczny okres, zakończony wyczerpującą recenzją.</em></small>
88 
+  </td>
89 
+  <td>
90 
+    15 Sierpnia 2008
91 
+  </td>
92 
+</tr>
93 
+
94 
+<tr bgcolor="#e5e5e5">
95 
+  <td>
96 
+    <b>Część C:</b> Implementacja<br /> <small><em>Po projekcie, sprawdzeniu i
97 
+przeglądzie, zmiany muszą zostać zaimplementowane i zintegrowane z bieżącym
98 
+kodem Tora. Sama implementacja niezbędnych zmian zajmie około dwóch
99 
+miesięcy.</em></small>
100 
+  </td>
101 
+  <td>
102 
+    15 Października 2008
103 
+  </td>
104 
+</tr>
105 
+
106 
+<tr>
107 
+  <td>
108 
+    <b>Część D:</b> Implementacja i testowanie aż do wydania<br />
109 
+<small><em>Zmiana jest bardzo ważna dla bezpieczeństwa i anonimowości sieci
110 
+Tora, wymaga więc dogłębnego testowania i szukania błędów w warunkach
111 
+laboratoryjnych i rzeczywistych. Okres trzech miesięcy jest przewidziany na
112 
+testowanie i usuwanie błędów, podczas którego odpowiedzialny za to
113 
+programista poświęci 1/3 swojego czasu na testowanie.  Część fazy testowania
114 
+będzie okresem publicznej wersji beta.</em></small>
115 
+  </td>
116 
+  <td>
117 
+    15 Stycznia 2009
118 
+  </td>
119 
+</tr>
120 
+
121 
+<tr bgcolor="#e5e5e5">
122 
+  <td>
123 
+    <b>Część E:</b> Wypuszczenie<br /> <small><em>Wypuszczenie zmian do sieci
124 
+serwerów Tora będzie zsynchronizowane z regularnymi wydaniami Tora. Jako że
125 
+regularne wydania zależą od wielu czynników zewnętrznych, jak zakończenie
126 
+innych projektów, które powinny wyjść w tym samym wydaniu, właściwy czas
127 
+wydania i instalacji u większości operatorów serwerów Tora może być różny. Z
128 
+doświadczenia wiemy, że można oczekiwać okresu od trzech do czterech
129 
+miesięcy.</em></small>
130 
+  </td>
131 
+  <td>
132 
+    15 Maja 2009
133 
+  </td>
134 
+</tr>
135 
+</table>
136 
+
137 
+<br /> <a id="Reports"></a>
138 
+<h2><a class="anchor" href="#Reports">Miesięczne raporty o bieżącym stanie</a></h2>
139 
+<p>
140 
+Łącznie będzie osiem miesięcznych raportów zaczynających się od pierwszej
141 
+części 15. czerwca 2008 i kończących się na ukończeniu implementacji i
142 
+testów 15. stycznia 2009.
143 
+</p>
144 
+
145 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
146 
+<thead>
147 
+<tr>
148 
+<th><big>Miesiąc,</big></th>
149 
+<th><big>Raport o stanie</big></th>
150 
+</tr>
151 
+</thead>
152 
+
153 
+<tr bgcolor="#e5e5e5">
154 
+  <td>
155 
+    <a id="Jun08"></a> <a class="anchor" href="#Jun08">Czerwiec 08</a>
156 
+  </td>
157 
+  <td>
158 
+    <small><em>Pierwotny cel analizy problemu, który prowadził do spowolnienia
159 
+usług ukrytych, został osiągnięty. Częścią tej analizy był pomiar opóźnienia
160 
+doświadczanego przez użytkownika podczas tworzenia lub łączenia się z
161 
+usługą.  Ponadto, dane z kwietnia 2008 mogą zostać użyte do badania czasu
162 
+wykonania wewnętrznych kroków nawiązywania połączenia z usługą
163 
+ukrytą. Wyniki analizy zawarte są w 22-stronicowym <a
164 
+href="http://freehaven.net/~karsten/hidserv/perfanalysis-2008-06-15.pdf">raporcie</a>
165 
+upublicznionym na <a
166 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00019.html">liście
167 
+mailingowej deweloperów</a> Tora.</em></small> <br/> <small><em>Analiza
168 
+odkryła także kilka błędów odpowiedzialnych za część opóźnienia w
169 
+udostępnianiu usługi ukrytej klientom. Kilka błędów zostało poprawionych po
170 
+analizie, inne będą poprawione wkrótce. Badanie ukazało kilka możliwych
171 
+podejść do polepszenia wydajności usług ukrytych. Część z tych pomysłów może
172 
+zostać zastosowana natychmiast, inne wymagają głębszej analizy i nowych
173 
+pomiarów. W trakcie analizy odkryliśmy, że część usprawnień wymaga głębszych
174 
+zmian w Torze, które nie są bezpośrednio związane z usługami ukrytymi. Zmian
175 
+tych nie da się osiągnąć w czasie przeznaczonym na ten projekt.</em></small>
176 
+  </td>
177 
+</tr>
178 
+
179 
+<tr>
180 
+  <td>
181 
+    <a id="Jul08"></a> <a class="anchor" href="#Jul08">Lipiec 08</a>
182 
+  </td>
183 
+  <td>
184 
+    <small><em>Wszystkie błędy znalezione w analizie zostały naprawione, łącznie
185 
+z 2 błędami naprawionymi w czasie analizy i jeszcze 4 znalezionymi w ciągu
186 
+ostatnich 30 dni. Podczas gdy usunięcie błędów usunęło niechciane wąskie
187 
+gardła wydajności związane z błędami w programowaniu, część zmian
188 
+projektowych zauważonych w poprzedniej analizie ma efekty uboczne na
189 
+anonimowości lub sumarycznym obciążeniu sieci. Efekty te muszą zostać
190 
+zanalizowane w odniesieniu do poszczególnych celów wydajnościowych. <a
191 
+href="http://freehaven.net/~karsten/hidserv/discussion-2008-07-15.pdf"
192 
+>Raport</a> został wydany na <a
193 
+href="http://archives.seul.org/or/dev/Jul-2008/msg00034.html" >listę
194 
+mailingową deweloperów</a>, zawiera on 7 możliwych zmian projektu, które
195 
+muszą zostać przedyskutowane. Okazało się, że część badań (pomiary wolnego
196 
+łącza i wielki plan skalowania) zajmie więcej czasu, niż się spodziewano,
197 
+więc zostały przełożonych na dalszą przyszłość niż część B. Bieżący plan
198 
+zakłada przeprowadzenie tych badań do 15. stycznia i pracę z założeniami do
199 
+czasu, gdy dostępne będą końcowe wyniki.</em></small>
200 
+  </td>
201 
+</tr>
202 
+
203 
+<tr bgcolor="#e5e5e5">
204 
+  <td>
205 
+    <a id="Aug08"></a> <a class="anchor" href="#Aug08">Sierpień 08</a>
206 
+  </td>
207 
+  <td>
208 
+    <small><em>W przeciągu ostatnich 30 dni 7 zaproponowanych projektów zostało
209 
+dalej rozpatrzonych i omówionych. Cztery z nich okazały się możliwe do
210 
+zastosowania, biorąc pod uwagę wymagane zmiany kodu i możliwe implikacje na
211 
+anonimowość.  Jeden został zakwalifikowany jako błąd, a nie zmiana
212 
+projektu. Dwa musiały zostać wykluczone ze względów albo nieprzewidywalnych
213 
+problemów z anonimowością albo niepewnością co do zysków
214 
+wydajności.</em></small> <br/> <small><em>Łącznie z wynikami z 15. licpa,
215 
+faza projektowania została zakończona.  Zadania dla zbliżającej się fazy
216 
+implementacji są teraz całkiem jasne: należy usunąć jeden błąd i
217 
+zaimplementować cztery zmiany projektowe. Ponadto, należy przeprowadzić
218 
+badania zmienionego projektu, by sprawdzić jego przydatność.  <a
219 
+href="http://freehaven.net/~karsten/hidserv/design-2008-08-15.pdf">Raport</a>
220 
+z wynikami fazy projektowej został wydany na <a
221 
+href="http://archives.seul.org/or/dev/Aug-2008/msg00025.html">listę
222 
+mailingową deweloperów</a>.</em></small>
223 
+  </td>
224 
+</tr>
225 
+
226 
+<tr>
227 
+  <td>
228 
+    <a id="Sep08"></a> <a class="anchor" href="#Sep08">Wrzesień 08</a>
229 
+  </td>
230 
+  <td>
231 
+    <small><em>W czasie pierwszej połowy fazy implementacji naprawiono dwa błędy
232 
+związane z usługami ukrytymi: <a
233 
+href="http://bugs.noreply.org/flyspray/index.php?do=details&amp;id=767">pierwszy
234 
+błąd</a> został odkryty w już fazie projektowania i był odpowiedzialny za
235 
+wysoki odsetek niepowodzeń w czasie udostępniania usługi ukrytej w systemie;
236 
+<a
237 
+href="http://bugs.noreply.org/flyspray/index.php?id=814&amp;do=details">drugi
238 
+błąd</a> został znaleziony w fazie implementacji i był odpowiedzialny za
239 
+nieudane połączenia do działającej usługi ukrytej. Obie poprawki będą
240 
+dołączone do najbliższej wersji niestabilnej i prawdopodobnie przeniesione
241 
+do jednej z następnych wersji stabilnych.</em></small> <br/>
242 
+<small><em>Cztery zmiany projektu, które zostały zaproponowane jako wynik
243 
+fazy projektowania, zostały zaimplementowane w <a
244 
+href="https://tor-svn.freehaven.net/svn/tor/branches/hidserv-design-changes/">eksperymentalnej
245 
+gałęzi</a> drzewa rozwojowego wersji niestabilnej. Pierwsze testy
246 
+funkcjonalne pokazały, że te zmiany działają i dają lepsze (widoczne)
247 
+osiągi.  To musi być potwierdzone przez następne cztery tygodnie testów
248 
+wewnętrznych.  Kolejnym celem jest przygotowanie wydania tej
249 
+eksperymentalnej gałęzi, które można byłoby dać beta-testerom na początku
250 
+zbliżającej się fazy testów.</em></small>
251 
+  </td>
252 
+</tr>
253 
+
254 
+<tr bgcolor="#e5e5e5">
255 
+  <td>
256 
+    <a id="Oct08"></a> <a class="anchor" href="#Oct08">Październik 08</a>
257 
+  </td>
258 
+  <td>
259 
+    <small><em>The implementation phase has been concluded. The bugfixes that
260 
+were found in the past 30 days have been released in developer version <a
261 
+href="http://archives.seul.org/or/talk/Oct-2008/msg00093.html">0.2.1.6-alpha</a>.
262 
+The four design changes that were identified in the design phase have been
263 
+specified in <a
264 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/155-four-hidden-service-improvements.txt">proposal
265 
+155</a>.  Three design changes have been included in the development
266 
+codebase and will automatically be included in the next development
267 
+version. The first two design changes improve connection establishment to a
268 
+hidden service by reducing a timeout from 60 to 30 seconds and by making a
269 
+second attempt in parallel after a delay of 15 seconds. The third design
270 
+change affects publication of a hidden service in the network by advertising
271 
+the service at 5 rather than 3 points in the network in parallel and
272 
+succeeding as soon as 3 points are established. The fourth design change has
273 
+turned out to be rather ineffective, but would add considerable code
274 
+complexity and was therefore dismissed. By now there are no more open
275 
+bugfixes or new designs. All changes are in the development codebase and can
276 
+be tested in the next phase.</em></small>
277 
+  </td>
278 
+</tr>
279 
+
280 
+<tr>
281 
+  <td>
282 
+    <a id="Nov08"></a> <a class="anchor" href="#Nov08">Listopad 08</a>
283 
+  </td>
284 
+  <td>
285 
+    <small><em>Usprawnienia zaimplementowane w poprzedniej fazie zostały wydane
286 
+w wersji Tora 0.2.1.7-alpha. Użytkownicy mogą pobrać tę wersję rozwojową ze
287 
+strony Tora i sprawdzić usprawnienia minimalnym wysiłkiem. Ponadto, dwie
288 
+poprawki błędów (<a
289 
+href="http://bugs.noreply.org/flyspray/index.php?id=767&amp;do=details">1</a>,
290 
+<a
291 
+href="http://bugs.noreply.org/flyspray/index.php?id=814&amp;do=details">2</a>),
292 
+które znaleziono w trakcie projektu, zostały przeniesione też do gałęzi
293 
+stabilnej i będą dołączone w najbliższej stabilnej wersji
294 
+0.2.0.32.</em></small> <br/> <small><em>Głównym celem ostatnich 31 dni było
295 
+przeprowadzenie nowych pomiarów, by sprawdzić, czy nowe usprawnienia są
296 
+efektywne, czy nie. Pomiary były prowadzone przez dwa dni, od 6. listopada
297 
+do 8. listopada. Niestety, sieć Tora miała wtedy poważny problem:
298 
+przedawniony certyfikat centrum katalogowego spowodował olbrzymi ruch w
299 
+sieci Tor, który <a
300 
+href="http://archives.seul.org/or/talk/Nov-2008/msg00053.html">zmusił wielu
301 
+operatorów do wyłączenia swoich przekaźników</a>. Drugi pomiar został
302 
+przeprowadzony między 13. a 15. listopada. Surowe dane są dostępne <a
303 
+href="http://freehaven.net/~karsten/hidserv/perfdata-2008-11-13.tar.gz">tutaj</a>
304 
+(40 MB). Ale wyniki pokazują, że całkowita wydajność sieci jest dalej gorsza
305 
+niż w Czerwcu 2008, gdy dokonano pierwszych pomiarów usług ukrytych. Widać
306 
+to, gdy porównuje się żądania do serwerów katalogowych Tora, na które nie
307 
+wpłynęły usprawnienia i które pokazują znacznie gorszą wydajność niż
308 
+przedtem. Efekty polepszenia wydajności są widoczne, ale wartości
309 
+bezwzględne nie są w tej chwili porównywalne. Nowe pomiary zostaną
310 
+przeprowadzone w grudniu z nadzieją, że efekty tego problemu zostaną
311 
+złagodzone.</em></small> <br/> <small><em>Ponadto, może istnieć <a
312 
+href="http://bugs.noreply.org/flyspray/index.php?id=847&amp;do=details">błąd</a>
313 
+w metodzie, której używa Tor do pobierania informacji katalogowych w czasie
314 
+startu.  Mimo iż nie jest to powiązane z usługami ukrytymi, polepszenie w
315 
+tej kwestii poprawiłoby też publikację usług ukrytych. Część pracy w ciągu
316 
+najbliższych 30 dni będzie poświęcona na zbadanie tego błędu.  </em></small>
317 
+  </td>
318 
+</tr>
319 
+
320 
+<tr bgcolor="#e5e5e5">
321 
+  <td>
322 
+    <a id="Dec08"></a> <a class="anchor" href="#Dec08">Grudzień 08</a>
323 
+  </td>
324 
+  <td>
325 
+    <small><em>Część ostatnich 30 dni została wykorzystana na naprawę błędów,
326 
+które wpłynęły na poprzednie pomiary usług ukrytych. Pierwsza <a
327 
+href="http://archives.seul.org/or/cvs/Nov-2008/msg00100.html">poprawka</a>
328 
+poprawia możliwość pojawienia się naruszenia ochrony pamięci, które bardzo
329 
+prawdopodobnie było odpowiedzialne za pewną liczbę nieudanych prób
330 
+pomiarów. Kolejny <a
331 
+href="https://bugs.torproject.org/flyspray/index.php?id=847&amp;do=details">błąd</a>
332 
+mógł prowadzić do sporych opóźnień w czasie uruchamiania: bardzo wolne
333 
+serwery katalogowe zajmowały uruchamiających się klientów przez długi czas
334 
+zanim te w końcu poddały się i uruchomiły z wykorzystaniem innego serwera. W
335 
+wyniku tego, dwa najwolniejsze serwery katalogowe dały więcej pasma swoim
336 
+węzłom, by złagodzić ten efekt. Trzeci <a
337 
+href="https://bugs.torproject.org/flyspray/index.php?id=874&amp;do=details">błąd</a>
338 
+został wprowadzony do kodu w czasie poprawek wydajności usług ukrytych w
339 
+listopadzie; efektem tego było to, że procesy Tora posiadające uruchomione
340 
+usługi ukryte przestawały o nich informować po przeładowaniu
341 
+konfiguracji. Ponadto, ten błąd odsłonił fakt, że Tor w czasie przeładowania
342 
+ponownie nawiązuje połączenia ze swoimi punktami przedstawiającymi, co mogło
343 
+wpłynąć na stabilność usług ukrytych. Ten błąd został naprawiony i będzie
344 
+dołączony w zbliżającej się wersji 0.2.1.9-alpha.</em></small> <br/>
345 
+<small><em>Poza poprawkami błędów, przeprowadzono nowe pomiary między 8. a
346 
+10. grudnia.  Będą to prawdopodobnie ostateczne pomiary do porównania
347 
+bieżącej wydajności usług ukrytych z tą na początku projektu. Dane nie
348 
+zostały całkowicie ocenione, więc trudno stawiać tezy o wydajności w chwili
349 
+bieżącej. Jednak <a
350 
+href="http://freehaven.net/~karsten/hidserv/prelimreport-2008-12-15.pdf">wstępna
351 
+ocena</a> pokazuje, że czasy publikacji usług znacznie się polepszyły. Jest
352 
+to wynik szybszego uruchamiania się klientów Tora i polepszeń wydajności
353 
+dodanych w listopadzie. Z drugiej strony, wyniki nawiązywania połączenia z
354 
+usługą ukrytą są mniej obiecujące. Podczas gdy ulepszenia dodane w
355 
+listopadzie zdają się mieć pozytywny wpływ na wydajność, niektóre podkroki
356 
+wykazują znacznie gorszą wydajność.  Jednym z przykładów jest pobieranie
357 
+deskryptorów usług ukrytych w celu skontaktowania się z usługą
358 
+ukrytą. Możliwe wyjaśnienie jest takie, że nagły wzrost liczby węzłów z
359 
+usługami ukrytymi we wrześniu miał negatywny wpływ na wydajność. Część pracy
360 
+w ostatnich 31 dniach będzie polegać na bardziej szczegółowej ocenie tych
361 
+danych i wysnuciu ostatecznego wniosku o osiągnięciach tego
362 
+projektu.</em></small>
363 
+  </td>
364 
+</tr>
365 
+
366 
+<tr>
367 
+  <td>
368 
+    <a id="Jan09"></a> <a class="anchor" href="#Jan09">Styczeń 09</a>
369 
+  </td>
370 
+  <td>
371 
+    <small><em>Faza testów została zakończona. Testy zostały przeprowadzone w
372 
+publicznej fazie beta, w której wszystkie zmiany w usługach ukrytych stały
373 
+się częścią serii 0.2.1.x-alpha. Wynikiem publicznej fazy beta jest kilka
374 
+znalezionych błędów, które mogły już być naprawione.</em></small> <br/>
375 
+<small><em>Kolejną częścią testów był drugi zestaw pomiarów przeprowadzonych
376 
+w grudniu <a
377 
+href="http://freehaven.net/~karsten/hidserv/comparison-2009-01-15.pdf">Porównanie</a>
378 
+pomiarów z czerwca i grudnia odkryło, że zmiany z tego projektu dają
379 
+efekt. Czasy publikacji usług mogą być ponad dwa razy mniejsze - z 2:12
380 
+minut do 58 sekund średnio.  To polepszenie jest znacznie lepsze, niż się
381 
+spodziewaliśmy. Mając taki postęp, można w przyszłości pomyśleć o
382 
+zmniejszeniu czasu stabilizacji z 30 sekund do jakiejś niższej
383 
+wartości. Jednak czas nawiązania połączenia zostaje na poziomie około 56
384 
+sekund między żądaniem usługi ukrytej a nawiązaniem połączenia z ukrytym
385 
+serwerem. Głównym powodem braku postępu jest przełączenie się między
386 
+scentralizowanym a zdecentralizowanym przechowywaniem deskryptorów usług
387 
+ukrytych. Ten pogarszający efekt dystrybucji katalogu usług ukrytych nie był
388 
+wcześniej spodziewany. Przyszłe prace powinny skupić się na polepszeniu
389 
+pobierania z rozproszonego katalogu usług ukrytych, na przykład poprzez
390 
+prowadzenie równoległych żądań.</em></small> <br/> <small><em>Ten raport
391 
+kończy serię comiesięcznych aktualizacji statusu. Wydanie serii 0.2.1.x
392 
+zawierającej polepszenia wydajności usług krytych odbędzie się w przeciągu
393 
+od najbliższych tygodni do miesięcy.</em></small>
394 
+  </td>
395 
+</tr>
396 
+</table>
397 
+
398 
+<!-- Do we want a people section? If so, would it make sense to write what
399 
+these people will be doing? And what exactly are these people going to
400 
+do? :)
401 
+<a id="People">
402 
+</a>
403 
+<h2><a class="anchor" href="#People">People</a></h2>
404 
+<ul>
405 
+<li><a href="<page about/people>#Core">Karsten Loesing</a></li>
406 
+<li><a href="<page about/people>#Core">Steven Murdoch</a></li>
407 
+</ul>
408 
+-->
409 
+<br /> <a id="Links"></a>
410 
+<h2><a class="anchor" href="#Links">Linki</a></h2>
411 
+<ul>
412 
+<li>Dokument badań <b>Performance Measurements and Statistics of Tor Hidden
413 
+Services</b> ("Pomiary wydajności i statystyki usług ukrytych Tora")  (<a
414 
+href="http://www.uni-bamberg.de/fileadmin/uni/fakultaeten/wiai_lehrstuehle/praktische_informatik/Dateien/Publikationen/loesing2008performance.pdf">PDF</a>)
415 
+napisali: Karsten Loesing, Werner Sandmann, Christian Wilms, i Guido
416 
+Wirtz. We Wstępie do 2008 International Symposium on Applications and the
417 
+Internet (SAINT), Turku, Finlandia, lipiec 2008.</li>
418 
+
419 
+
420 
+
421 
+<!-- In the future, put links to proposal, preliminary results, etc. here -->
422 
+</ul>
423 
+
424 
+</div>
425 
+
426 
+
427 
+
428 
+#include <foot.wmi>
projects/pl/index.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,197 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22186 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="Tor Projects Page" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Wprowadzenie do Projektów Tora</h2>
17 
+<hr/>
18 
+
19 
+<p>Ekosystem Projektu Tor zawiera wiele projektów, część prowadzony przez
20 
+głównych deweloperów, a część przez wolontariuszy. Ta strona jest próbą
21 
+zorganizowania i podsumowania tych projektów, aby pomóc w starcie nowym
22 
+ochotnikom-deweloperom oraz aby upewnić się, że ludzie nie duplikują
23 
+niechcący wysiłków. </p>
24 
+
25 
+<p>W budowie! Proszę wytrzymać, zanim nie oczyścimy listy.</p>
26 
+
27 
+<a id="Controllers"></a>
28 
+<h3><a class="anchor" href="#Controllers">Kontrolery Tora</a></h3>
29 
+<ul>
30 
+<li><a href="<page vidalia/index>">Vidalia</a> jest naszym rekomendowanym
31 
+międzyplatformowym graficznym kontrolerem Tora, rozwijaną przez Matta
32 
+Edmana. Jest zawarta w większości paczek.</li>
33 
+<li><a href="http://www.anonymityanywhere.com/tork/">TorK</a> jest kontrolerem
34 
+napisanym przez Roberta Hogana dla środowiska KDE (Linux). Ma kilka
35 
+dodatkowych funkcjonalności nad Vidalię (jak wybór ścieżki), ale jest nieco
36 
+trudniejsze.</li>
37 
+<li><a href="http://www.atagar.com/arm/">arm</a> jest opartym na curses (linia
38 
+poleceń, bez GUI) kontrolerem zaprojektowanym specjalnie do podsumowania
39 
+działania przekaźnika.</li>
40 
+<li><a href="https://svn.torproject.org/svn/blossom/trunk/">Blossom</a> jest
41 
+przestarzałym i nierozwijanym kontrolerem opartym na tezie Geoffa Goodella z
42 
+Harvardu. Jego celem było ułatwienie dostępu do zasobów z wybranej
43 
+lokalizacji sieci.</li>
44 
+</ul>
45 
+
46 
+<a id="Applications"></a>
47 
+<h3><a class="anchor" href="#Applications">Aplikacje towarzyszące</a></h3>
48 
+<ul>
49 
+<li><a href="<page torbutton/index>">TorButton</a> jest rozszerzeniem dla
50 
+Firefoksa, który pomaga chronić Cię, gdy przeglądasz sieć z
51 
+Torem. Pierwotnie po prostu przełączało Twoje ustawienia proxy, ale teraz
52 
+zajmuje się <a href="https://www.torproject.org/torbutton/design/">szeroką
53 
+gamą</a> zagrożeń poziomu aplikacji.</li>
54 
+<li><a href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> jest
55 
+cache'ującym proxy HTTP, które obsługuje potokowość i HTTP/1.1. Dodajemy je
56 
+do instalatorów, wraz z Firefoksem i Torbuttonem głównie dlatego, że Firefox
57 
+ciągle <a href="https://bugzilla.mozilla.org/show_bug.cgi?id=280661">nie
58 
+obsługuje</a> bezpośrednio proxy typu socks.</li>
59 
+<li><a href="http://www.privoxy.org/">Privoxy</a> jest kolejnym dobrym serwerem
60 
+proxy dla HTTP, którego możesz używać między Firefoksem a Torem. Przeszliśmy
61 
+na Polipo ze względu na obsługę http/1.1 i utrzymywania połączeń.</li>
62 
+<li><a href="http://code.google.com/p/torsocks/">torsocks</a> (oparte na swym
63 
+pierwowzorze <a href="http://tsocks.sourceforge.net/">tsocks</a>) jest
64 
+owijką dla Linux / UNIX (ale nie OS X) do dynamicznego zastępowania
65 
+sieciowych wywołań systemowych w Twojej aplikacji takimi, które używają
66 
+Tora.</li>
67 
+<li><a href="http://monkey.org/~dugsong/dsocks/">dsocks</a> jest alternatywą dla
68 
+tsocks, która działa na OS X / BSD.</li>
69 
+<li><a href="https://git.torproject.org/checkout/thandy/master/">Thandy</a>,
70 
+nasz <a
71 
+href="http://google-opensource.blogspot.com/2009/03/thandy-secure-update-for-tor.html">bezpieczny
72 
+aktualizator</a>, będący ciągle w rozwoju, jest zaprojektowany, by pomagać
73 
+użytkownikom w aktualizacjach wersji Tora. Podczas gdy komercyjne
74 
+organizacje kupują własne sejfy bankowe pod strażą do ochrony swoich kluczy
75 
+aktualizacji, celem Thandy są bardziej rozproszone sytuacje dla systemów
76 
+takich jak Tor. Obecnie jej główną zaletą jest przejrzana przez recenzenta
77 
+<a
78 
+href="https://git.torproject.org/checkout/thandy/master/specs/thandy-spec.txt">specyfikacja</a>,
79 
+ale możesz zobaczyć to w akcji jako część naszego eksperymentalnego <a
80 
+href="https://data.peertech.org/files/demo/updater/index.html">instalatora
81 
+sieciowego</a>.</li>
82 
+</ul>
83 
+
84 
+<a id="Installers"></a>
85 
+<h3><a class="anchor" href="#Installers">Instalatory</a></h3>
86 
+<ul>
87 
+<li>TBB, TBB-dla-Linux</li>
88 
+<li>deb, rpm</li>
89 
+<li>obrazy osx</li>
90 
+<li>torvm</li>
91 
+<li>orbot</li>
92 
+<li>livecd: <a href="https://amnesia.boum.org/">The (Amnesic)  Incognito Live
93 
+System</a>, tor ramdisk</li>
94 
+</ul>
95 
+
96 
+<a id="Implementations"></a>
97 
+<h3><a class="anchor" href="#Implementations">Alternatywne implementacje
98 
+Tora</a></h3>
99 
+<ul>
100 
+<li>xmux's thing</li>
101 
+<li>onioncoffee</li>
102 
+<li>tortunnel</li>
103 
+<li>jap?</li>
104 
+</ul>
105 
+
106 
+<a id="Listings"></a>
107 
+<h3><a class="anchor" href="#Listings">Listingi Przekaźników</a></h3>
108 
+<ul>
109 
+<li>torstatus</li>
110 
+<li>torstatus xenobite'a</li>
111 
+<li>check.torproject.org</li>
112 
+<li>hurtowa lista wyjść</li>
113 
+<li>tordnsel</li>
114 
+<li>eksport głosoawń v3 z moria1</li>
115 
+</ul>
116 
+
117 
+<a id="Monitoring"></a>
118 
+<h3><a class="anchor" href="#Monitoring">Monitoring Sieci</a></h3>
119 
+<ul>
120 
+<li>weather</li>
121 
+<li><a href="http://metrics.torproject.org/">Projekt Mierzenia: Pomiary sieci
122 
+Tora</a></li>
123 
+<li>torperf</li>
124 
+<li>archiwa</li>
125 
+<li>https://svn.torproject.org/svn/projects/archives/trunk/exonerator/HOWTO</li>
126 
+</ul>
127 
+
128 
+<a id="Performance"></a>
129 
+<h3><a class="anchor" href="#Performance">Wydajnosć Sieci</a></h3>
130 
+<ul>
131 
+<li>whytorisslow</li>
132 
+<li>torflow</li>
133 
+<li>bwauthority</li>
134 
+<li>exitscanner</li>
135 
+<li>NLnet <a href="<page projects/hidserv>">Przyspieszenie usług ukrytych</a></li>
136 
+<li>udp-tor: joel, chris, ian, etc</li>
137 
+<li>NLnet <a href="<page projects/lowbandwidth>">Tor dla klientów o wolnym
138 
+łączu</a></li>
139 
+</ul>
140 
+
141 
+<a id="Censorship"></a>
142 
+<h3><a class="anchor" href="#Censorship">Opieranie się cenzurze</a></h3>
143 
+<ul>
144 
+<li>gettor</li>
145 
+<li>bridgedb</li>
146 
+<li>strategi dystrybucji mostków</li>
147 
+<li>obfuscaTOR</li>
148 
+</ul>
149 
+
150 
+<a id="Libraries"></a>
151 
+<h3><a class="anchor" href="#Libraries">Biblioteki Kontrolerów</a></h3>
152 
+<ul>
153 
+<li>torctl</li>
154 
+<li>biblioteki kontrolerów w c# i javie</li>
155 
+</ul>
156 
+
157 
+<a id="Infrastructure"></a>
158 
+<h3><a class="anchor" href="#Infrastructure">Infrastruktura</a></h3>
159 
+<ul>
160 
+<li>system śledzenia błędów (flyspray)</li>
161 
+<li>blog</li>
162 
+<li>wiki</li>
163 
+<li>pootle, translation.tp.o</li>
164 
+<li>buildbot https://buildbot.vidalia-project.net/one_line_per_build</li>
165 
+<li>https://data.peertech.org/torbld</li>
166 
+<li>mirrory tora</li>
167 
+<li>rsync</li>
168 
+<li>a nagios?</li>
169 
+<li>git, svn</li>
170 
+<li>gitweb</li>
171 
+</ul>
172 
+
173 
+<a id="HiddenServices"></a>
174 
+<h3><a class="anchor" href="#HiddenServices">Usługi Ukryte</a></h3>
175 
+<ul>
176 
+<li>diagramy o tym, jak działają</li>
177 
+<li>tor2web</li>
178 
+<li>onioncat</li>
179 
+<li>shallot</li>
180 
+</ul>
181 
+
182 
+<a id="Other"></a>
183 
+<h3><a class="anchor" href="#Other">Inne</a></h3>
184 
+<ul>
185 
+<li>puppetor</li>
186 
+<li>torwall</li>
187 
+<li>topf</li>
188 
+<li>nym</li>
189 
+<li>nymble</li>
190 
+<li>Rozszerzenia do Firefoksa foebuda</li>
191 
+</ul>
192 
+
193 
+</div>
194 
+
195 
+
196 
+
197 
+#include <foot.wmi>
projects/pl/lowbandwidth.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,346 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22186 $
9 
+# Translation-Priority: 4-optional
10 
+#include "head.wmi" TITLE="NLnet Project: Tor for Low Bandwidth Clients" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Projekt NLnet: Tor dla klientów o wolnym łączu</h2>
17 
+<hr />
18 
+
19 
+<p>
20 
+System Tor jest w tej chwili najbardziej nadający się do używania dla ludzi
21 
+mających połączenie z Internetem o dużej przepustowości. W czasie
22 
+uruchamiania klienta Tora pobierany jest ogromny plik z opisem wszystkich
23 
+serwerów Tora. Ten plik to tak zwany Katalog Tora i umożliwia on klientowi
24 
+wybieranie spośród serwerów w sieci Tora. Pobieranie całego katalogu jest
25 
+wymagane w bieżącej wersji protokołu Tora. Ten plik z katalogiem jest zbyt
26 
+duży dla użytkowników z modemami lub będącymi w sieciach mobilnych jak GPRS,
27 
+jako że wstępne pobieranie uruchamiane przy każdym logowaniu użytkownika
28 
+trwa od 10 do 30 minut na wolnym połączeniu. W wyniku tego, Tor nie jest
29 
+zdatny do używania przez użytkowników modemów lub sieci mobilnych. Jednym z
30 
+głównych celów Tora jest dostarczanie bezpiecznego anonimowego Internetu
31 
+użytkownikom w krajach z dyktaturą lub represjami. Takie miejsca często mają
32 
+wolne połączenia internetowe, przez modem albo niskiej przepustowości łącza
33 
+do świata zewnętrznego.  Poprzez umożliwienie tym użytkownikom używania
34 
+sieci Tora można uczynić znaczny postęp w kierunku swobodnej komunikacji i
35 
+informacji w tych krajach.
36 
+</p>
37 
+
38 
+<p>
39 
+By Tor nadawał się do użycia na wolnych łączach, potrzebny jest rozwój
40 
+protokołu Tora, by zmniejszyć rozmiar wstępnego pobierania. Nowa wersja
41 
+protokołu Tora powinna zmienić sposób, w jaki klient otrzymuje informacje do
42 
+stworzenia obwodu tak, by pierwsze pobieranie mogło być wykonane na linii
43 
+modemowej 14.4k w czasie około trzech minut. Celem prac w tym projekcie jest
44 
+umożliwienie wprowadzenia zmian w protokole i rozprowadzenia ich wśród
45 
+użytkowników Tora w przeciągu 12 miesięcy. Stworzone oprogramowanie zostanie
46 
+wydane na 3-punktowej licencji BSD, jak cały kod Tora. Wszystkie części będą
47 
+całkowicie publiczne.
48 
+</p>
49 
+
50 
+<p>
51 
+Ten projekt jest hojnie sponsorowany przez:
52 
+</p>
53 
+
54 
+<p>
55 
+<a href="http://www.nlnet.nl/news/2008/20080514-awards.html"> <img
56 
+src="$(IMGROOT)/nlnet-160x60.png" alt="Fundacja NLnet" /></a>
57 
+</p>
58 
+
59 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
60 
+<thead>
61 
+<tr>
62 
+<th><big>Projekt</big></th>
63 
+<th><big>Czas zakończenia</big></th>
64 
+</tr>
65 
+</thead>
66 
+
67 
+<tr bgcolor="#e5e5e5">
68 
+  <td>
69 
+    <b>Część A:</b> Projektowanie i sprawdzanie zmian protokołu<br />
70 
+<small><em>W tej części zawarty jest szczegółowy projekt i oparte na
71 
+symulacjach sprawdzenie niezbędnych zmian i modyfikacji projektu bieżącego
72 
+protokołu Tora.  Zmiany w protokole będą raczej istotne, więc wymaga to
73 
+dokładnego sprawdzenia wszystkich możliwych skutków dla bezpieczeństwa i
74 
+anonimowości sieci Tora. Dla tej fazy projektowania i sprawdzania
75 
+przewidziany jest dwumiesięczny okres, zakończony wyczerpującą recenzją.
76 
+Celem tej części jest m.in. zdefiniowanie wydajności do osiągnięcia w fazie
77 
+implementacji.  Celem projektowym jest zmniejszenie pobieranego rozmiaru
78 
+Katalogu Tora do około 300 kilobajtów, co umożliwiłoby użytkownikowi łącza
79 
+14.4 kbps pobranie go w ciągu około trzech minut. Mogą być odstępstwa od
80 
+tego celu, jeśli będą wymagane do zachowania bezpieczeństwa i anonimowości,
81 
+ale to jest obszar, w który należy celować.  </em></small>
82 
+  </td>
83 
+  <td>
84 
+    15 Lipca 2008
85 
+  </td>
86 
+</tr>
87 
+
88 
+<tr>
89 
+  <td>
90 
+    <b>Część B:</b>Implementacja zmiany protokołu<br /> <small><em>Po projekcie,
91 
+sprawdzeniu i przeglądzie, zmiany muszą zostać zaimplementowane i
92 
+zintegrowane z bieżącym kodem Tora. Sama implementacja niezbędnych zmian
93 
+zajmie około trzech miesięcy.  </em></small>
94 
+  </td>
95 
+  <td>
96 
+    15 Października 2008
97 
+  </td>
98 
+</tr>
99 
+
100 
+<tr bgcolor="#e5e5e5">
101 
+  <td>
102 
+    <b>Część C:</b>Testowanie<br /> <small><em>Zmiana jest bardzo ważna dla
103 
+bezpieczeństwa i anonimowości sieci Tora, wymaga więc dogłębnego testowania
104 
+i szukania błędów w warunkach laboratoryjnych i rzeczywistych. Okres trzech
105 
+miesięcy jest przewidziany na testowanie i usuwanie błędów, podczas którego
106 
+odpowiedzialny za to programista poświęci 1/3 swojego czasu na testowanie.
107 
+Część fazy testowania będzie okresem publicznej wersji beta.  </em></small>
108 
+  </td>
109 
+  <td>
110 
+    January 15, 2009
111 
+  </td>
112 
+</tr>
113 
+
114 
+<tr>
115 
+  <td>
116 
+    <b>Część D:</b>Wypuszczenie<br /> <small><em>Wypuszczenie zmian do sieci
117 
+serwerów Tora będzie zsynchronizowane z regularnymi wydaniami Tora. Jako że
118 
+regularne wydania zależą od wielu czynników zewnętrznych, jak zakończenie
119 
+innych projektów, które powinny wyjść w tym samym wydaniu, właściwy czas
120 
+wydania i instalacji u większości operatorów serwerów Tora może być różny. Z
121 
+doświadczenia wiemy, że można oczekiwać okresu od trzech do czterech
122 
+miesięcy. Wydanie będzie przeprowadzone jako część regularnego procesu
123 
+wydawania Tora, który jest działaniem wykonywanym przez wolontariuszy i
124 
+personel wynagradzany z innych grantów przeznaczonych na projekt Tor.
125 
+</em></small>
126 
+  </td>
127 
+  <td>
128 
+    15 Kwietnia 2009
129 
+  </td>
130 
+</tr>
131 
+</table>
132 
+
133 
+<br /> <a id="Reports"></a>
134 
+<h2><a class="anchor" href="#Reports">Miesięczne raporty o bieżącym stanie</a></h2>
135 
+<p>
136 
+There will be in total eight monthly status reports beginning with the first
137 
+deliverable on July 15, 2008 and ending with completion of implementation
138 
+and testing work on January 15, 2009.
139 
+</p>
140 
+
141 
+<table width="100%" border="0" cellspacing="0" cellpadding="3">
142 
+<thead>
143 
+<tr>
144 
+<th><big>Miesiąc,</big></th>
145 
+<th><big>Raport o stanie</big></th>
146 
+</tr>
147 
+</thead>
148 
+
149 
+<tr bgcolor="#e5e5e5">
150 
+  <td>
151 
+    <a id="Jun08"></a> <a class="anchor" href="#Jun08">Czerwiec 08</a>
152 
+  </td>
153 
+  <td>
154 
+    <small><em>We did some initial measuring of Tor clients bootstrapping. The
155 
+results are not very surprising: a client fetches about 10KB of certs, one
156 
+consensus for 140KB (now 90KB, see next paragraph), and about 1.5 megs of
157 
+Server Descriptors (after half of which it starts building
158 
+circuits).</em></small> <br /> <small><em><a
159 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/138-remove-down-routers-from-consensus.txt">Proposal
160 
+138</a> shrinks consensus documents by 30% to 40% and has already been
161 
+implemented and merged into the spec.  Implementation is part of the
162 
+0.2.1.x-alpha tree and the code will take effect once over two-thirds of the
163 
+directory authorities (i.e. 5 out of 6) have upgraded.</em></small> <br />
164 
+<small><em><a
165 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">Proposal
166 
+140</a> does not directly relate to reducing initial download size, but
167 
+instead tries to make subsequent downloads of new consensus documents use
168 
+fewer bytes has also been written up and <a
169 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00013.html">sent to
170 
+or-dev</a>. There are some questions to be answered from other Tor
171 
+developers first, but other than that I think it's fine and could be
172 
+implemented.</em></small> <br /> <small><em>The Big Thing is making clients
173 
+not download all 1.5 megs of server descriptors. <a
174 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Proposal
175 
+141</a> has been <a
176 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00017.html">sent to
177 
+or-dev</a>. There are basically 3 things to it, as far as I can see at the
178 
+moment: move load balancing info into the consensus (should not be hard),
179 
+implement something so that Tor clients can fetch SDs on demand from routers
180 
+along their circuit while they are building it (described in the draft), and
181 
+deal with exit selection. We're still developing ideas for the last part;
182 
+some possibilities are mentioned in the draft.</em></small>
183 
+  </td>
184 
+</tr>
185 
+
186 
+<tr>
187 
+  <td>
188 
+    <a id="Jul08"></a> <a class="anchor" href="#Jul08">Lipiec 08</a>
189 
+  </td>
190 
+  <td>
191 
+    <small><em>Praca nad <a
192 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt">Propozycją
193 
+141</a> trwa: Są dwa podstawowe pomysły na to, jak przenieść informacje o
194 
+równowadze wykorzystania łącza do konsensusu: jeden pomysł mówi, że centra
195 
+katalogowe generują wagi, których klienci powinni używać i umieszczają to w
196 
+konsensusie, drugi jest taki, by po prostu umieścić w nim informacje o łączu
197 
+z deskryptora serwera. Ta druga opcja jest prawdopodobnie lepsza, gdy weźmie
198 
+się też pod uwagę <a
199 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt">Propozycję
200 
+140</a>, gdyż unika to dużej ilości często zmieniających się liczb w
201 
+konsensusie.</em></small> <br /> <small><em>Odnośnie polityk wyjścia, <a
202 
+href="http://archives.seul.org/or/dev/Jul-2008/msg00022.html">list na liście
203 
+mailingowej or-dev</a> sugeruje dodanie hasza identyfikującego politykę
204 
+wyjścia węzła do dokumentu konsensusu. Dodanie kolejnych 160 bitów o
205 
+wysokiej entropii na każdy węzeł może budzić niepokój, ale naszym zdaniem
206 
+wiele polityk wyjścia jest takich samych, więc dokument konsensusu powinien
207 
+dobrze się kompresować. Pomiary trwają.</em></small>
208 
+  </td>
209 
+</tr>
210 
+
211 
+<tr bgcolor="#e5e5e5">
212 
+  <td>
213 
+    <a id="Aug08"></a> <a class="anchor" href="#Aug08">Sierpień 08</a>
214 
+  </td>
215 
+  <td>
216 
+    <small><em>Dokumenty głosowania serwerów katalogowych i ich algorytm
217 
+tworzenia dokumentów konsensusu zostały zmienione, by uwzględniać informacje
218 
+o przepustowości łącza i podsumowania polityk, według Propozycji 141. Gdy
219 
+już pięć z sześciu działających centrów katalogowych zaktualizują się do
220 
+wersji SVN co najmniej 16554, dokumenty konsensusu zaczną zawierać te
221 
+informacje.</em></small>
222 
+  </td>
223 
+</tr>
224 
+
225 
+<tr>
226 
+  <td>
227 
+    <a id="Sep08"></a> <a class="anchor" href="#Sep08">Wrzesień 08</a>
228 
+  </td>
229 
+  <td>
230 
+<small><em>We wrześniu nie było żadnych aktualizacji.</em></small>
231 
+  </td>
232 
+</tr>
233 
+
234 
+<tr bgcolor="#e5e5e5">
235 
+  <td>
236 
+    <a id="Oct08"></a> <a class="anchor" href="#Oct08">Październik 08</a>
237 
+  </td>
238 
+  <td><p>
239 
+<small><em>Nie osiągnęliśmy naszego kroku milowego "skończenia
240 
+implementacji" w tym miesiącu, gdyż deweloper prowadzący ten projekt ma zbyt
241 
+dużo zajęć.  Dobrą wiadomością jest to, że zrobiliśmy całkiem sporą część
242 
+implementacji, a było to kilka miesięcy temu (od etapu sierpniowego), więc
243 
+zdążyliśmy już ją nieźle przetestować. Pozostałe kroki implementacji to
244 
+nauczenie przekaźników, jak otrzymywać żądania pobierania deskryptorów
245 
+przekaźników z wewnątrz obwodów (prawdopodobnie potrzebujemy nowego typu
246 
+komórki specjalnie do tych celów, abyśmy mogli wyciąć drogę naokoło), a
247 
+potem nauczyć klientów, by robiły to, gdy używany przez nich przekaźnik
248 
+używa dostatecznie nowej wersji. Te dwa kroki są szczegółowo opisane w <a
249 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/141-jit-sd-downloads.txt"
250 
+>Sekcji 3.2 propozycji 141</a></em></small></p>
251 
+
252 
+<p><small><em>Nasz nowy plan czasowy to zrobienie tych dwóch rzeczy do połowy
253 
+listopada, a jeśli to zacznie wyglądać na coraz mniej prawdopodobne, zrobimy
254 
+większe zmiany planu i być może też projektu.</em></small></p>
255 
+
256 
+<p><small><em>Jest kilka innych komponentów, którymi chcielibyśmy się zająć
257 
+potem -- jeden, o którym dużo ostatni myśleliśmy, to pobieranie różnic
258 
+ostatnich konsensusów: <a
259 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/140-consensus-diffs.txt"
260 
+>140-consensus-diffs.txt</a>.  Po pierwsze, to mogłoby zaoszczędzić
261 
+przepustowość łącza, co zawsze jest dobre, gdy pomnożyć je przez liczbę
262 
+klientów, ale to też oznacza, że możemy użyć tej zaoszczędzonej
263 
+przepustowości do pobierania różnic częściej niż bieżące "co 3-4
264 
+godziny". Jeśli klienci poznają bardziej aktualne informacje katalogowe,
265 
+mogą budować szybsze ścieżki, gdyż mają lepsze dane o przepustowości każdego
266 
+przekaźnika (co wiąże się z projektem NLnet), ale głównym nowym pomysłem
267 
+jest to, że lepiej korzystamy z przelotnych przekaźników: w chwili obecnej
268 
+przekaźnik musi działać przez 3-4 godziny, zanim zobaczy jakichkolwiek
269 
+użytkowników, a to wyklucza wielu wolontariuszy chcących prowadzić
270 
+przekaźniki tylko przez kilka godzin na raz.</em></small></p>
271 
+<p><small><em>Kolejnym krokiem jest skończenie implementacji propozycji 141,
272 
+byśmy mogli przedstawić ją użytkownikom do testów. Mamy nadzieję, że
273 
+wkrótce!</em></small></p>
274 
+  </td>
275 
+</tr>
276 
+
277 
+<tr>
278 
+  <td>
279 
+    <a id="Nov08"></a> <a class="anchor" href="#Nov08">Listopad 08</a>
280 
+  </td>
281 
+  <td>
282 
+<p><small><em>Zdaje się, że pierwszy plan, który mieliśmy na ostatnią fazę
283 
+rozwoju jest zarówno a) znacznie trudniejszy, niż myśleliśmy i b)
284 
+przypuszczalnie przesadny w stosunku do tego, czego
285 
+potrzebujemy.</em></small></p>
286 
+
287 
+<p><small><em> Roger wznowił dyskusję projektową na or-dev: <a
288 
+href="http://archives.seul.org/or/dev/Nov-2008/threads.html">http://archives.seul.org/or/dev/Nov-2008/threads.html</a>.
289 
+</em></small></p>
290 
+
291 
+<p><small><em>Myślę, że teraz mamy lepsze rozeznanie w możliwościach i ich
292 
+kosztach: <a
293 
+href="http://archives.seul.org/or/dev/Nov-2008/msg00007.html">http://archives.seul.org/or/dev/Nov-2008/msg00007.html</a>.
294 
+</em></small></p>
295 
+
296 
+<p><small><em>Nick został zasypany innymi projektami deweloperskimi (miejmy
297 
+nadzieję, że zacznie kończenie ich w tym miesiącu), a ja chcę znać jego
298 
+zdanie na temat kontynuacji; mam nadzieję, że wybierzemy jedno z prostszych
299 
+podejść.</em></small></p>
300 
+
301 
+<p><small><em>Z drugiej strony, te najprostsze rozwiązania dają też mniejszą
302 
+skalowalność.  Ale moim zdaniem będą dobrymi rozwiązaniami tymczasowymi na
303 
+pewien czas -- a gdy nadejdzie ta chwila, kto wie, co jeszcze zostanie
304 
+zmienione.</em></small></p>
305 
+  </td>
306 
+</tr>
307 
+
308 
+<tr bgcolor="#e5e5e5">
309 
+  <td>
310 
+    <a id="Jan09"></a> <a class="anchor" href="#Jan09">Jan 09</a>
311 
+  </td>
312 
+  <td>
313 
+<p><small><em> Napisałem bardziej szczegółową wersję naszego nowego pomysłu
314 
+projektowego jako <a
315 
+href="https://svn.torproject.org/svn/tor/trunk/doc/spec/proposals/158-microdescriptors.txt"
316 
+>propozycję #158</a>, a dyskusja zaczęła się od <a
317 
+href="http://archives.seul.org/or/dev/Jan-2009/msg00010.html"
318 
+>http://archives.seul.org/or/dev/Jan-2009/msg00010.html</a>.</em></small></p>
319 
+
320 
+<p><small><em> Myślę, że to w końcu jest to! (No, jak już skończę zajmować się
321 
+komentarzami.)  </em></small></p>
322 
+
323 
+<p><small><em> Jednym z głównych powodów, dla których ten projekt nie jest
324 
+realizowany zgodnie z planem jest to, że główny wniosek z <a href="<page
325 
+projects/hidserv>">projektu Karstena z NLnet o wydajności usług ukrytych</a>
326 
+mówi, iż to rozszerzenie obwodu jest głównym powodem spadku wydajności. Ale
327 
+ten projekt zaproponował dodanie większej liczby przejść i złożoności
328 
+właśnie do tego punktu. Tak więc, musimy stworzyć lepszy plan, by dotrzeć do
329 
+pierwotnego celu bez dodatkowego pogarszania wydajności.  </em></small></p>
330 
+
331 
+<p><small><em> Przeglądaliśmy propozycję projektową w ciagu ostatnich kilku
332 
+tygodni i moim zdaniem wkrótce będziemy gotowi, by zacząć
333 
+implementację. Skoro jednak mamy kilka zadań deweloperskich, które już
334 
+lądują w lutym, jest prawdopodobne, że tą implementacją nie zajmiemy się
335 
+przed końcem lutego lub w marcu. Ale tym razem na pewno!</em></small></p>
336 
+  </td>
337 
+</tr>
338 
+</table>
339 
+
340 
+<br />
341 
+
342 
+</div>
343 
+
344 
+
345 
+
346 
+#include <foot.wmi>
projects/pl/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/pt/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/ru/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/se/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/tr/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
projects/zh-cn/metrics.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,12 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+
8 
+
9 
+## translation metadata
10 
+# Revision: $Revision: 22100 $
11 
+# Status: obsolete
12 
+#include <foot.wmi>
pt/mirrors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,48 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Mirrors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Mirrors</h2>
14 
+<hr />
15 
+
16 
+<p>
17 
+O endereço primário deste site é <a
18 
+href="https://www.torproject.org/">https://www.torproject.org/</a>, no
19 
+entanto, existem <em>cópias</em> (mirrors) em outros locais.
20 
+</p>
21 
+
22 
+<p>
23 
+Se gostaria de colaborar no projecto através de um mirror, por favor <a
24 
+href="<page docs/running-a-mirror>">siga estas instruções.</a>.
25 
+</p>
26 
+
27 
+<table class="mirrors">
28 
+<tr>
29 
+  <th>País</th>
30 
+  <th>Organização</th>
31 
+  <th>Status</th>
32 
+  <th>ftp</th>
33 
+  <th>http dist/</th>
34 
+  <th>http website</th>
35 
+  <th>https dist/</th>
36 
+  <th>https website</th>
37 
+  <th>rsync dist/</th>
38 
+  <th>rsync website</th>
39 
+</tr>
40 
+
41 
+<!--PO4ASHARPBEGINinclude <mirrors-table.wmi>
42 
+PO4ASHARPEND-->
43 
+</table>
44 
+
45 
+  </div>
46 
+
47 
+
48 
+#include <foot.wmi>
publish
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,23 @@
1 
+#!/bin/sh
2 
+set -e # stop if we encounter an error
3 
+
4 
+svn update
5 
+make
6 
+
7 
+# Update a timestamp so we can check whether each mirror is
8 
+# up to date.
9 
+[ -d project/trace ] || mkdir -p project/trace
10 
+date -u > project/trace/www.torproject.org
11 
+
12 
+# don't copy over stuff with permissions that make it useless
13 
+chmod a+r * -R
14 
+
15 
+## I'm not comfortable having arbitrary people use --delete yet,
16 
+## since if they screw up it'll blow away arbitrary things.
17 
+#rsync -Prvz --delete . tor.eff.org:directory/
18 
+
19 
+rsync --exclude .svn --exclude .deps -Prvz . byblos:/var/www/www.torproject.org/htdocs/
20 
+
21 
+echo "Forcing mirror update"
22 
+ssh byblos '/var/lib/mirror-tor/trigger-sync'
23 
+
ru/contact.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,72 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22359 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Contact" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Контакты</h2>
14 
+
15 
+<div class="underline"></div>
16 
+
17 
+<!-- BEGIN SIDEBAR -->
18 
+<div class="sidebar">
19 
+<h3>Представитель масс-медиа?</h3>
20 
+<a href="<page press/index>">Страница для прессы</a>
21 
+</div>
22 
+
23 
+<p>Первым делом, если у вас возникла проблема или вопрос в связи с
24 
+использованием Tor, посмотрите <a href="<page
25 
+documentation>#Support">страницу поддержки</a>.  Разработчики Tor большую
26 
+часть времени заняты улучшением Tor и у нас нет специальных людей для
27 
+поддержки пользователей, поэтому постарайтесь помочь себе сами перед тем,
28 
+как <a href="<page faq>#SupportMail">вежливо попытаться найти
29 
+добровольца</a>.</p>
30 
+
31 
+<p>Если вам всё-таки крайне необходимо достать нас, вот несколько вариантов.
32 
+Ко всем адресам ниже надо добавить @torproject.org. Почти все эти адреса
33 
+перенаправляют почту одной и той же небольшой группе людей, поэтому
34 
+пожалуйста будьте терпеливы и <a
35 
+href="http://www.catb.org/~esr/faqs/smart-questions.html">полезны</a>.
36 
+Пожалуйста пишите на английском языке.</p>
37 
+
38 
+<ul>
39 
+<li><tt>tor-assistants</tt> для всего остального.</li>
40 
+<li><tt>tor-ops</tt> это люди которые занимаются сервером директорий.  Пишите
41 
+сюда если вы запустили сервер Tor и у вас есть вопрос или проблема с вашим
42 
+сервером.</li>
43 
+<li><tt>tor-webmaster</tt> can fix typos on the website, change wrong statements
44 
+or directions on the website, and add new sections and paragraphs that you
45 
+send us. You might want to make a draft of your new sections on <a
46 
+href="https://trac.torproject.org/projects/tor/wiki">the Tor wiki</a> first.</li>
47 
+<li><tt>tor-volunteer</tt> будет рад услышать о ваших документах, патчах,
48 
+тестировании, опыте поддержки приложений, итп вещах описанных на <a
49 
+href="<page volunteer>">странице добровольцев</a> (или о других проблемах
50 
+которые вы исправили итд). Не стоит писать нам перед тем как вы начали
51 
+работать над чем-то - как и все проекты добровольцев в Интернете, мы
52 
+получаем много писем от восторженных людей, которые потом через некоторое
53 
+время исчезают, поэтому мы более всего заинтересованы услышать о конкретных
54 
+результатах.</li>
55 
+<li><tt>tor-translation</tt> может разместить новый <a href="<page
56 
+translation>">вариант перевода</a> на сайте, а также ответить на вопросы о
57 
+существующих и новых переводах.</li>
58 
+<li><tt>tordnsel</tt> для связи с людьми ответственными за tordns exitlist.</li>
59 
+<li><tt>donations</tt> для вопросов и комментариев по <a href="<page
60 
+donate>">пожертвованию денег для разработчиков</a>. Больше пожертвований
61 
+значит <a href="<page faq>#Funding">больше Tor'а</a>. Мы рады помочь
62 
+продумать другие варианты вашей помощи.</li>
63 
+<li><tt>execdir</tt> для прессы/медиа, вопросов и комментариев к Tor как
64 
+некоммерческой организации: вопросы о торговых марках, affiliation и
65 
+coordination, большие пожертвования, запросы контактной информации,
66 
+лицензирование и сертификация, etc.</li>
67 
+</ul>
68 
+
69 
+  </div>
70 
+
71 
+
72 
+#include <foot.wmi>
ru/documentation.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,281 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22359 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor: Documentation" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<a id="RunningTor"></a>
14 
+<h2><a class="anchor" href="#RunningTor">Использование Tor</a></h2>
15 
+<ul>
16 
+<li><a href="<page docs/tor-doc-windows>">Установка Tor на системах Win32</a></li>
17 
+<li><a href="<page docs/tor-doc-osx>">Установка Tor на ОС Mac X</a></li>
18 
+<li><a href="<page docs/tor-doc-unix>">Установка Tor на ОС Linux/BSD/Unix</a></li>
19 
+<li><a href="<page torbutton/index>">Установка Torbutton для Tor</a></li>
20 
+<li><a href="<page docs/tor-doc-relay>">Настройка ретранслятора Tor</a></li>
21 
+<li><a href="<page docs/tor-hidden-service>">Настройка скрытого сервиса Tor</a></li>
22 
+</ul>
23 
+
24 
+<a id="Support"></a> <a id="UpToSpeed"></a>
25 
+<h2><a class="anchor" href="#UpToSpeed">Как войти в курс дел — прошлое,
26 
+настоящее и будущее Tor</a></h2>
27 
+
28 
+<ol>
29 
+<li>
30 
+Сперва ознакомьтесь со <a href="<page overview>">страницей обзора</a> для
31 
+того чтобы понять основной принцип работы Tor, узнать для чего нужен этот
32 
+сервис, и кто его использует.
33 
+</li>
34 
+
35 
+<li>
36 
+<a href="<page download>">Установите комплект Tor</a> и опробуйте
37 
+его. Убедитесь, что перед этим вы установили браузер Firefox и обязательно
38 
+прочитайте <a href="<page download>#Warning">список предупреждений</a> о
39 
+том, как вы сами можете разрушить свою анонимность.
40 
+</li>
41 
+
42 
+<li>
43 
+Our <a
44 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">FAQ</a>
45 
+covers all sorts of topics, including questions about setting up a client or
46 
+relay, concerns about anonymity attacks, why we didn't build Tor in other
47 
+ways, etc.  There's a separate <a href="<page faq-abuse>">Abuse FAQ</a> to
48 
+answer common questions from or for relay operators.  The <a href="<page
49 
+eff/tor-legal-faq>">Tor Legal FAQ</a> is written by EFF lawyers, and aims to
50 
+give you an overview of some of the legal issues that arise from the Tor
51 
+project in the US.
52 
+</li>
53 
+
54 
+<li>The <a href="<page tor-manual>">manual</a> lists all the possible entries
55 
+you can put in your <a
56 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Imsupposedtoeditmytorrc.Whatdoesthatmean">torrc
57 
+file</a>. We also provide a <a href="<page tor-manual-dev>">manual for the
58 
+development version of Tor</a>.</li>
59 
+
60 
+<li>If you have questions, we have an IRC channel (for users, relay operators,
61 
+and developers)  at <a href="irc://irc.oftc.net/tor">#tor on
62 
+irc.oftc.net</a>. If you have a bug, especially a crash bug, read <a
63 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#MyTorkeepscrashing.">how
64 
+to report a Tor bug</a> first and then tell us as much information about it
65 
+as you can in <a href="https://bugs.torproject.org/tor">our bugtracker</a>.
66 
+(If your bug is with Polipo, your browser, or some other application, please
67 
+don't put it in our bugtracker.) The <a href="#MailingLists">or-talk mailing
68 
+list</a> can also be useful.
69 
+</li>
70 
+
71 
+<li>
72 
+<a href="https://blog.torproject.org/">Блог проекта Tor</a>. Мы стараемся
73 
+публиковать свежие новости раз в одну, две недели.
74 
+</li>
75 
+
76 
+<li>
77 
+Скачайте и просмотрите обзорный доклад Роджера с What The Hack (<a
78 
+href="http://freehaven.net/~arma/wth-anonymous-communication-58.mp4">видео</a>,
79 
+<a href="http://freehaven.net/~arma/wth1.pdf">слайды</a>, <a
80 
+href="http://wiki.whatthehack.org/index.php/Anonymous_communication_for_the_United_States_Department_of_Defense...and_you">аннотация</a>).
81 
+Этот доклад был сделан в июле 2005-го, когда нас ещё спонсировал EFF и сеть
82 
+была достаточно маленькой, но он всё ещё даёт неплохое представление о том,
83 
+как работает Tor и для чего он нужен.
84 
+</li>
85 
+
86 
+<li>
87 
+Просмотрите наши <a href="#DesignDoc">документы по архитектуре</a>. Обратите
88 
+внимание что у нас есть спецификации в стиле RFC, чтобы максимально точно и
89 
+подробно описать как сконструирован Tor.
90 
+</li>
91 
+
92 
+<li>
93 
+Существует набросок <a
94 
+href="https://svn.torproject.org/svn/projects/roadmaps/2008-12-19-roadmap-full.pdf">списка
95 
+вопросов, которые мы бы хотели затронуть в будущем</a>. К сожалению, многие
96 
+из этих вопросов требуют более подробного описания чтобы, быть понятными
97 
+кому-либо кроме разработчиков Tor. Но тем не менее, вы можете получить
98 
+поверхностное представление о том, какие вопросы должны быть решены в
99 
+будущем.
100 
+</li>
101 
+
102 
+<li>
103 
+Скачайте и посмотрите доклад Ника с Defcon, сделанный в июле 2007-го о
104 
+"Технических переменах, произошедших с 2004 года"(<a
105 
+href="http://freehaven.net/~arma/Defcon15-Mathewson-Technical_Changes_since_you_Last_Heard_about_Tor.mp4">видео</a>,
106 
+<a
107 
+href="http://freehaven.net/~nickm/slides/Defcon07/TorChanges.pdf">слайды</a>),доклад
108 
+Роджера "противостояние блокированию и обход цензуры" с 23C3, сделанный в
109 
+декабре 2006-го (<a
110 
+href="http://freehaven.net/~arma/23C3-1444-en-tor_and_china.m4v">видео</a>,<a
111 
+href="http://freehaven.net/~arma/slides-23c3.pdf">слайды</a>,<a
112 
+href="http://events.ccc.de/congress/2006/Fahrplan/events/1444.en.html">аннотация</a>,
113 
+<a
114 
+href="https://svn.torproject.org/svn/projects/design-paper/blocking.html">дизайн
115 
+устойчивой к блокированию системы анонимности</a>), и доклад Роджера о
116 
+"Текущих мероприятиях в 2007" с 24C3, сделанный в декабре 2007 года (<a
117 
+href="http://freehaven.net/~arma/24c3-2325-en-current_events_in_tor_development.mp4">видео</a>,
118 
+<a href="http://freehaven.net/~arma/slides-24c3.pdf">слайды</a>, <a
119 
+href="http://events.ccc.de/congress/2007/Fahrplan/events/2325.en.html">аннотация</a>).
120 
+У нас также есть учебный материал по скрытым сервисам Tor от What The Hack
121 
+(<a href="http://freehaven.net/~arma/wth_tor_hidden_services.mp4">видео</a>,
122 
+<a href="http://freehaven.net/~arma/wth3.pdf">слайды</a>).
123 
+</li>
124 
+
125 
+<li>
126 
+Посмотрите доклад Майка "Обеспечивая безопасность сети Tor", сделанный на
127 
+Defcon в июле 2007-го(<a
128 
+href="http://freehaven.net/~arma/Defcon15-Mike_Perry-Securing_the_Tor_Network.mp4">видео</a>,<a
129 
+href="http://freehaven.net/~arma/SecuringTheTorNetwork.pdf">слайды</a>).В
130 
+нём описываются наиболее распространённые атаки на сети подобные Tor и наши
131 
+попытки защиты от этих атак, а также демонстрируется набор скриптов<a
132 
+href="https://svn.torproject.org/svn/torflow/trunk/README">Torflow</a>.
133 
+</li>
134 
+
135 
+<li>
136 
+Изучите <a href="<svnsandbox>doc/spec/proposals/001-process.txt">процесс
137 
+внесения предложений по модификации архитектуры Tor</a>, и посмотрите список
138 
+<a href="<svnsandbox>doc/spec/proposals/">текущих предложений</a>.
139 
+</li>
140 
+
141 
+<li>
142 
+Наш файл <a href="<svnsandbox>doc/TODO">TODO для разработчиков</a>
143 
+начинается со сроков выполнения обещаний, тех за которые <a href="<page
144 
+sponsors>">наши спонсоры</a> платят деньги. Там также перечислено множество
145 
+других задач и тем, с которыми мы хотели бы разобраться.
146 
+</li>
147 
+
148 
+<li>
149 
+Как только вы войдёте в курс дел, всё будет продолжать меняться на удивление
150 
+быстро. В <a href="#MailingLists">почтовой рассылке or-dev</a> проводятся
151 
+серьёзные обсуждения; на IRC канале #tor проходят более простые дискуссии.
152 
+</li>
153 
+
154 
+</ol>
155 
+
156 
+<a id="MailingLists"></a>
157 
+<h2><a class="anchor" href="#MailingLists">Информация о почтовых рассылках</a></h2>
158 
+<ul>
159 
+<li>Рассылка <a href="http://archives.seul.org/or/announce/">or-announce</a> для
160 
+объявлений о новых релизах и критических обновлениях, связанных с
161 
+обеспечением безопасности (малый объем рассылки). Каждый должен подписаться
162 
+на эту рассылку. Есть также <a
163 
+href="http://rss.gmane.org/gmane.network.onion-routing.announce">RSS фид</a>
164 
+на <a href="http://gmane.org">gmane.org</a>, дублирующий рассылку
165 
+or-announce.</li>
166 
+<li>В рассылке <a href="http://archives.seul.org/or/talk/">or-talk</a> проходит
167 
+множество дискуссий, также сюда мы выкладываем сообщения о предварительных
168 
+релизах и кандидатах на релиз.</li>
169 
+<li>Список рассылки <a
170 
+href="http://archives.seul.org/tor/relays/">ретрансляторов Tor</a> - это
171 
+место, где происходят дискуссии о предоставлении, настройке, и работе с
172 
+вашим ретранслятором Tor.  Если в настоящее время вы предоставляете
173 
+ретранслятор, или думаете об этом, этот список для вас.</li>
174 
+<li>Рассылка <a href="http://archives.seul.org/or/dev/">or-dev</a> только для
175 
+разработчиков. Очень малый объем рассылки.</li>
176 
+<li>Рассылка для <a href="http://archives.seul.org/tor/mirrors/">операторов
177 
+зеркал</a>для новых зеркал сайтов и поддержки <a href="<page
178 
+mirrors>">существующих зеркал</a>.</li>
179 
+<li>Рассылка уведомлений о <a href="http://archives.seul.org/or/cvs/">коммитах в
180 
+svn и git</a> может быть интересна для разработчиков.</li>
181 
+<li>An automated list for <a href="http://archives.seul.org/tor/bugs/">bug
182 
+reports from trac</a> may be interesting for users and developers.</li>
183 
+</ul>
184 
+
185 
+<a id="DesignDoc"></a>
186 
+<h2><a class="anchor" href="#DesignDoc">Документы об архитектуре</a></h2>
187 
+<ul>
188 
+<li><b>Документ по архитектуре</b> (опубликован на Usenix Security в 2004)
189 
+излагает наши суждения и анализ степени безопасности архитектуры Tor:
190 
+доступны версии в <a
191 
+href="<svnsandbox>doc/design-paper/tor-design.pdf">PDF</a> и <a
192 
+href="<svnsandbox>doc/design-paper/tor-design.html">HTML</a>.</li>
193 
+<li>Наш завершенный документ по <b>анонимной связи с малой задержкой
194 
+(low-latency anonymity)</b> (всё ещё в виде черновика) описывает недавние
195 
+эксперименты и направления: <a
196 
+href="<svnsandbox>doc/design-paper/challenges.pdf">PDF</a>.</li>
197 
+<li>Наш доклад на WEIS 2006 &mdash; <b>Анонимность Одна не Ходит: Практичность и
198 
+Эффект Сети (Anonymity Loves Company: Usability and the Network Effect)</b>
199 
+&mdash; обьясняет почему практичность в системах анонимности влияет на
200 
+безопасность этих систем: <a
201 
+href="http://freehaven.net/anonbib/cache/usability:weis2006.pdf">PDF</a>.</li>
202 
+<li>Наша предварительная архитектура для противостояния блокированию доступа к
203 
+сети Tor крупными брандмауэрами описана в документе <b>создание устойчивой к
204 
+блокированию системы анонимности</b>: <a
205 
+href="<svnsandbox>doc/design-paper/blocking.pdf"> PDF</a> и <a
206 
+href="<svnsandbox>doc/design-paper/blocking.html"> HTML</a>. Хотите <a
207 
+href="<page volunteer>#Coding">помочь нам построить такую систему</a>?</li>
208 
+<li><b>Спецификации</b> предназначены для разработчиков и дают достаточно
209 
+информации, чтобы сделать совместимую версию Tor:
210 
+<ul>
211 
+<li><a href="<svnsandbox>doc/spec/tor-spec.txt">Основные характеристики Tor</a></li>
212 
+<li><a href="<svnsandbox>doc/spec/dir-spec.txt">Характеристики 3-й версии
213 
+сервера директорий Tor</a> (и предыдущие <a
214 
+href="<svnsandbox>doc/spec/dir-spec-v1.txt">версия 1</a> и <a
215 
+href="<svnsandbox>doc/spec/dir-spec-v2.txt">версия 2</a>)</li>
216 
+<li><a href="<svnsandbox>doc/spec/control-spec.txt">Характеристики контрольного
217 
+протокола Tor</a></li>
218 
+<li><a href="<svnsandbox>doc/spec/rend-spec.txt">Характеристики точки
219 
+синхронизации Tor</a></li>
220 
+<li><a href="<svnsandbox>doc/spec/path-spec.txt">Характеристики алгоритма выбора
221 
+пути</a></li>
222 
+<li><a href="<svnsandbox>doc/spec/address-spec.txt">Специальные хост-имена,
223 
+поддерживаемые Tor</a></li>
224 
+<li><a href="<svnsandbox>doc/spec/socks-extensions.txt">Поддержка сетью Tor
225 
+протокола SOCKS и расширений</a></li>
226 
+<li><a href="<svnsandbox>doc/spec/version-spec.txt">Как работает система номеров
227 
+версий Tor</a></li>
228 
+<li><a href="<svnsandbox>doc/spec/proposals/">Обрабатываемые черновые описания
229 
+новых характеристик и предлагаемых изменений</a></li>
230 
+</ul></li>
231 
+
232 
+</ul>
233 
+
234 
+<a id="NeatLinks"></a>
235 
+<h2><a class="anchor" href="#NeatLinks">Полезные ссылки</a></h2>
236 
+<ul>
237 
+<li>The <a href="https://trac.torproject.org/projects/tor/wiki">Tor wiki</a>
238 
+provides a plethora of helpful contributions from Tor users. Check it out!</li>
239 
+<li><a
240 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">A
241 
+list of supporting programs you might want to use in association with
242 
+Tor</a>.</li>
243 
+<li><a href="https://check.torproject.org/">Tor детектор 1</a> и <a
244 
+href="http://torcheck.xenobite.eu/">Tor детектор 2</a> помогут вам
245 
+определить, используете ли вы Tor или нет.</li>
246 
+<li>Ознакомьтесь с страницами статуса сети Tor : <a
247 
+href="http://trunk.torstatus.kgprog.com/index.php">http://trunk.torstatus.kgprog.com/</a>
248 
+или <a
249 
+href="https://torstat.xenobite.eu/">https://torstat.xenobite.eu/</a>.
250 
+Помните, что приведенные списки могут быть менее точными, чем те, которые
251 
+использует ваш клиент, так как он получает свою информацию от директорий и
252 
+анализирует их локально.</li>
253 
+<li>Прочитайте <a
254 
+href="http://freehaven.net/anonbib/topic.html#Anonymous_20communication">эти
255 
+документы</a> (особенно те, что выделены), чтобы лучше ознакомиться с
256 
+состоянием дел с анонимными системами передачи данных.</li>
257 
+</ul>
258 
+
259 
+<a id="Developers"></a>
260 
+<h2><a class="anchor" href="#Developers">Для разработчиков</a></h2>
261 
+  Просмотрите <b>хранилище исходных кодов</b> Tor:
262 
+  <ul>
263 
+    <li><a href="<svnsandbox>">Напрямую ознакомьтесь с содержимым дерева
264 
+каталогов</a></li>
265 
+    <li>Доступ Git и SVN:
266 
+      <ul>
267 
+        <li><kbd>клон git git://git.torproject.org/git/tor</kbd></li>
268 
+        <li>Основная ветка <kbd>master</kbd>. Активно поддерживаются ветки
269 
+<kbd>maint-0.2.0</kbd> и <kbd>maint-0.2.1</kbd>.</li>
270 
+        <li><kbd>svn проверка https://svn.torproject.org/svn/website/trunk website</kbd></li>
271 
+      </ul>
272 
+    </li>
273 
+    <li><a
274 
+href="https://gitweb.torproject.org//githax.git?a=blob;f=doc/Howto.txt;hb=HEAD">Basic
275 
+instructions for using Git to contribute to Tor software.</a></li>
276 
+  </ul>
277 
+
278 
+  </div>
279 
+
280 
+
281 
+#include <foot.wmi>
ru/faq-abuse.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,449 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22308 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Abuse FAQ" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Часто задаваемые вопросы (FAQ) по злоупотреблению сетью Tor</h2>
17 
+
18 
+<!-- BEGIN SIDEBAR -->
19 
+<div class="sidebar-left">
20 
+<h3>Вопросы</h3>
21 
+<ul>
22 
+<li><a href="<page faq-abuse>#WhatAboutCriminals">Не помогает ли Tor
23 
+преступникам осуществлять их коварные планы?</a></li>
24 
+<li><a href="<page faq-abuse>#DDoS">Что на счет распределённой атаки типа "отказ
25 
+в обслуживании" (DDos)?</a></li>
26 
+<li><a href="<page faq-abuse>#WhatAboutSpammers">Что по поводу спамеров?</a></li>
27 
+<li><a href="<page faq-abuse>#HowMuchAbuse">Часто ли Tor используется
28 
+злоумышленниками?</a></li>
29 
+<li><a href="<page faq-abuse>#TypicalAbuses">Итак, чего мне ожидать, если я
30 
+предоставляю выводной узел?</a></li>
31 
+<li><a href="<page faq-abuse>#IrcBans">Сервис Tor запрещен в IRC сети, которую я
32 
+хочу использовать.</a></li>
33 
+<li><a href="<page faq-abuse>#SMTPBans">Ваши узлы заблокированы почтовым
34 
+сервером, который я хочу использовать.</a></li>
35 
+<li><a href="<page faq-abuse>#Bans">Я хочу заблокировать сеть Tor на моем
36 
+сервисе.</a></li>
37 
+<li><a href="<page faq-abuse>#TracingUsers">У меня есть неопровержимый довод для
38 
+вычисления пользователя Tor. Вы можете помочь?</a></li>
39 
+<li><a href="<page faq-abuse>#RemoveContent">Я хочу удалить часть содержимого с
40 
+адреса .onion.</a></li>
41 
+<li><a href="<page faq-abuse>#LegalQuestions">У меня есть правовые вопросы
42 
+относительно злоупотреблений сервисом Tor.</a></li>
43 
+</ul>
44 
+</div>
45 
+
46 
+<!-- END SIDEBAR -->
47 
+<hr />
48 
+
49 
+<a id="WhatAboutCriminals"></a>
50 
+<h3><a class="anchor" href="#WhatAboutCriminals">Не помогает ли Tor преступникам
51 
+осуществлять их коварные планы?</a></h3>
52 
+
53 
+<p>У преступников уже есть множество возможностей. Так как они хотят нарушить
54 
+закон, у них уже есть множество доступных возможностей, которые по уровню
55 
+обеспечиваемой конфиденциальности <em>превосходят<em> Tor. Они могут
56 
+воровать сотовые телефоны, использовать их, а затем – выкидывать в канаву;
57 
+они могут взламывать компьютеры, расположенные в Корее или Бразилии, и
58 
+использовать их для осуществления вредоносной деятельности; они могут
59 
+использовать шпионское программное обеспечение, вирусы и другие методы,
60 
+позволяющие получить контроль над буквально миллионами Windows компьютеров в
61 
+мире. </p>
62 
+
63 
+<p>Проект Tor нацелен на предоставление защиты обычным людям, которые хотят
64 
+следовать букве закона. Сейчас конфиденциальность есть только у
65 
+преступников, и нам необходимо это исправить. </p>
66 
+
67 
+<p>Некоторые защитники анонимности объясняют, что это просто компромисс –
68 
+допустить плохое использование для того, чтобы дать возможность хорошим
69 
+людям обеспечить свою конфиденциальность – но этот вопрос гораздо
70 
+серьезней. Преступники и другие плохие люди мотивированы изучать способы
71 
+получения хорошей анонимности, и у многих из них есть возможность за это
72 
+хорошо заплатить. Факт наличия возможности воровать и пользоваться
73 
+идентификационной информацией невинных жертв (чтобы замести следы) делает
74 
+это еще проще. С другой стороны, хорошие люди чаще всего лишены времени или
75 
+денег на изучение вопросов обеспечения конфиденциальности в сети
76 
+Интернет. Это наихудшая из возможных ситуаций. </p>
77 
+
78 
+<p>Таким образом, да, преступники теоретически могут пользоваться Tor, но у них
79 
+уже есть более серьезные инструменты. И вряд ли закрытие сети Tor в мире
80 
+помешает преступникам делать их грязные дела. В то же время Tor и другие
81 
+инструменты обеспечения конфиденциальности могут <em>бороться<em> и
82 
+идентифицировать воров, физические преступления, такие как сталкинг и т.д. </p>
83 
+
84 
+
85 
+
86 
+<!--
87 
+<a id="Pervasive">
88 
+</a>
89 
+<h3><a class="anchor" href="#Pervasive">If the whole world starts using
90 
+Tor, won't civilization collapse?</a></h3>
91 
+-->
92 
+<a id="DDoS"></a>
93 
+<h3><a class="anchor" href="#DDoS">Что на счет распределённой атаки типа «отказ
94 
+в обслуживании» (DDos)?</a></h3>
95 
+
96 
+<p>Распределенные атаки типа «отказ в обслуживании» (DDoS), как правило,
97 
+основываются на наличии группы, состоящей из тысяч компьютеров, каждый из
98 
+которых отсылает потоки трафика жертве. Учитывая, что целью при этом
99 
+является перегрузка полосы пропускания жертвы, отправляют они обычно пакеты
100 
+UDP, так как они не требуют квитирования установления связи или координации. </p>
101 
+
102 
+<p>Но по той причине, что Tor пропускает только корректно сформированные TCP
103 
+потоки, а не все IP пакеты, вы не можете отправлять UDP пакеты через
104 
+Tor. (Вы также не можете осуществлять специализированные формы этих атак,
105 
+такие как, например, SYN флудинг.) Таким образом, обычные DDoS атаки
106 
+невозможно осуществлять через Tor. Сеть Tor, помимо прочего, не позволяет
107 
+осуществлять атаки с ускорением полосы пропускания по отношению к внешним
108 
+сайтам: вам придется отправлять байт за байтом, которые сеть Tor затем
109 
+перешлет к пункту назначения. Поэтому, обобщив, можно сказать, что
110 
+атакующие, обладающие достаточной полосой пропускания для запуска
111 
+эффективных DDoS атак, могут легко осуществлять их без сети Tor. </p>
112 
+
113 
+<a id="WhatAboutSpammers"></a>
114 
+<h3><a class="anchor" href="#WhatAboutSpammers">Что по поводу спамеров?</a></h3>
115 
+
116 
+<p>Во-первых, правила выводных узлов Tor установленные по умолчанию запрещают
117 
+отправку трафика через 25 порт (SMTP). Таким образом, отправка спам писем
118 
+через Tor не будет работать по умолчанию. Возможно, что некоторые операторы
119 
+ретрансляторов разрешат отправку через 25 порт на их собственных выводных
120 
+узлах. В этом случае этот компьютер разрешит отправку исходящей почты, но
121 
+такие пользователи могут с таким же успехом установить и открытый почтовый
122 
+ретранслятор, независимый от сети Tor. Короче говоря, сеть Tor не подходит
123 
+для спама, потому как почти все ретрансляторы Tor настроены на запрет
124 
+отправки исходящей почты. </p>
125 
+
126 
+<p>Естественно запретом на отправку писем все не ограничивается. Спамеры могут
127 
+использовать сеть Tor чтобы: подключаться к открытым HTTP прокси-серверам (а
128 
+уже оттуда к серверам SMTP); подключаться к плохо написанным почтовым
129 
+скриптам общего шлюзового интерфейса (Common Gateway Interface - CGI) и
130 
+контролировать их ботнеты, для того, чтобы тайно обмениваться информацией с
131 
+армиями компьютеров рассылающих спам.
132 
+</p>
133 
+
134 
+<p>
135 
+Печально, но факт, что спамеры отлично справлялись со своей работой и до
136 
+появления сервиса Tor. Также помните, что многие из более хитрых механизмов
137 
+коммуникации (такие как поддельные пакеты UDP) не могут быть использованы
138 
+через Tor, так как сеть пропускает только корректно сформулированные TCP
139 
+подключения.
140 
+</p>
141 
+
142 
+<a id="ExitPolicies"></a>
143 
+<h3><a class="anchor" href="#ExitPolicies">Как работают правила выводных узлов
144 
+Tor?</a></h3>
145 
+
146 
+<p>
147 
+<a href="<page faq>#ExitPolicies">Тема перенесена в новый список часто
148 
+задаваемых вопросов (FAQ) по использованию Tor</a>
149 
+</p>
150 
+
151 
+<a id="HowMuchAbuse"></a>
152 
+<h3><a class="anchor" href="#HowMuchAbuse">Часто ли Tor используется
153 
+злоумышленниками?</a></h3>
154 
+
155 
+<p>Говоря в целом, можно сказать, что не часто. Мы предоставляем сервис уже с
156 
+октября 2003 года, а жалоб было всего несколько. Конечно же, как и все
157 
+остальные ориентированные на предоставление конфиденциальности сети в
158 
+Интернете, мы притягиваем свою долю болванов. Выводные правила Tor помогают
159 
+разделять роль "желания внести свой вклад в развитие ресурсов сети" от роли
160 
+"желания иметь дело с жалобами" так что мы надеемся, что наша сеть более
161 
+устойчива чем прошлые попытки на сети анонимности. </p>
162 
+
163 
+<p>Так как сеть Tor насчитывает также <a href="<page overview>">множество
164 
+хороших пользователей</a>, мы чувствуем, что сейчас дела по поддержанию
165 
+баланса идут неплохо. </p>
166 
+
167 
+<a id="TypicalAbuses"></a>
168 
+<h3><a class="anchor" href="#TypicalAbuses">Итак, чего мне ожидать, если я
169 
+предоставляю выводной узел?</a></h3>
170 
+
171 
+<p>Если вы предоставляете Tor узел, разрешающий внешние подключения (в
172 
+соответствии с правилами вывода, установленными по умолчанию), то можно с
173 
+уверенностью сказать, что вы время от времени будете получать жалобы. Они
174 
+могут поступать в различных формах, например: </p>
175 
+<ul>
176 
+<li>Кто-то подключается к службе Hotmail и отсылает в компанию шантажирующие
177 
+письма. Служба ФБР отсылает вам вежливое письмо, вы объясняете им, что
178 
+предоставляете ретранслятор Tor, они говорят "а, ну ладно" и оставляют вас в
179 
+покое. [Порт 80]</li>
180 
+<li>Кто-то хочет «убить» ваш узел, подключается к сервису группы Google и
181 
+рассылает спам на портале Usenet, после чего отсылает жалобное письмо вашему
182 
+Интернет провайдеру, в котором рассказывает, как вы разрушаете мир. [Порт
183 
+80]</li>
184 
+<li>Кто-то подключается к сети IRC и выводит всех своим поведением. Ваш Интернет
185 
+сервис провайдер получает вежливое письмо, в котором говорится, что ваш
186 
+компьютер был взломан; и/или ваш компьютер подвергается DDoS атаке. [Порт
187 
+6667]</li>
188 
+<li>Кто-то использует сервис Tor, чтобы скачать фильм Вина Дизеля и ваш Интернет
189 
+сервис провайдер получает сообщение о нарушении DMCA (Закон о защите
190 
+авторских прав в сфере цифровой информации в новом тысячелетии). Обратите
191 
+внимание на <a href="<page eff/tor-dmca-response>">шаблон ответов на
192 
+подобные запросы</a>, которые объясняют, почему ваш Интернет сервис
193 
+провайдер, скорее всего, проигнорирует такое сообщение без ущерба для
194 
+себя. [Случайные порты]</li>
195 
+</ul>
196 
+
197 
+<p>Вы также можете обнаружить, что для IP адреса вашего узла Tor доступ к
198 
+некоторым сайтам/сервисам заблокирован. Это может случиться, несмотря на
199 
+используемые вами правила вывода, потому что некоторым группам людей дела
200 
+нет до того, есть ли у сервиса Tor подобные правила или нет. (Если у вас
201 
+есть запасной IP адрес, не используемый для другой деятельности, вам стоит
202 
+сделать так, чтобы ретранслятор Tor работал через него). Для этого есть
203 
+несколько причин. Например, </p>
204 
+
205 
+<ul>
206 
+<li>Открытая энциклопедия Wikipedia запретила редактирование своего содержимого
207 
+с IP адресов множества ретрансляторов Tor (читать пока можно) по той
208 
+причине, что в нескольких случаях анонимные  и не очень умные люди
209 
+дурачились с её страницами. Мы ведем переговоры с сотрудниками Wikipedia о
210 
+том, как они могут контролировать неправильное использование, обеспечивая
211 
+доступ анонимным участникам, которые зачастую имеют свежие новости или
212 
+внутреннюю информацию по теме, но не хотят раскрывать свою личность при
213 
+публикации (либо не хотят показывать местным властям, что они подключаются к
214 
+Wikipedia). Это также относится к сервису Slashdot.</li>
215 
+
216 
+<li>Служба SORBS также вносит IP адреса некоторых ретрансляторов Tor в черные
217 
+списки электронной почты. Причиной тому является пассивное определение
218 
+подключения вашего ретранслятора к определенным IRC сетям, из чего они
219 
+заключают, что ваш ретранслятор может заниматься спамом. Мы пытались
220 
+работать с ними и объяснить, что не все программное обеспечение работает
221 
+так, но в итоге сдались. Мы рекомендуем вам избегать их, и <a
222 
+href="http://paulgraham.com/spamhausblacklist.html">научить ваших друзей
223 
+(если они пользуются этой службой) избегать вводящих в заблуждение черных
224 
+списков</a>.</li>
225 
+
226 
+</ul>
227 
+
228 
+<a id="IrcBans"></a>
229 
+<h3><a class="anchor" href="#IrcBans">Сервис Tor запрещен в IRC сети, которую я
230 
+хочу использовать.</a></h3>
231 
+
232 
+<p>Иногда болваны пользуются сервисом Tor, чтобы пакостить в IRC каналах. Такое
233 
+использование сервиса заканчивается IP-специфичным временным блокированием
234 
+(на IRC языке называемым "klines"), так как операторы сети пытаются закрыть
235 
+троллям доступ к своей сети. </p>
236 
+
237 
+<p>Такая реакция подчеркивает фундаментальный изъян модели безопасности IRC:
238 
+они полагают, что за IP-адресами стоят реальные люди и что путем
239 
+блокирования IP-адресов они могут заблокировать людей. В реальности это не
240 
+так — большинство троллей регулярно пользуются буквально миллионом открытых
241 
+прокси-серверов и взломанных компьютеров, доступных посредством сети
242 
+Интернет. Сети IRC ведут обреченную на поражение борьбу, пытаясь блокировать
243 
+все такие узлы, а на базе дефектной модели обеспечения безопасности
244 
+(примерно также как и индустрия антивирусов) появилась вся эта кустарная
245 
+промышленность черных списков и антитроллей. В сложившейся ситуации сеть Tor
246 
+– это капля в море. </p>
247 
+
248 
+<p>С другой стороны, с точки зрения операторов IRC серверов, безопасность – это
249 
+не процесс «все или ничего». Путем быстрого реагирования на атаки троллей и
250 
+другие социальные атаки их сценарий можно сделать менее привлекательным для
251 
+атакующего субъекта. К тому же в большинстве случаев IP-адреса все же
252 
+совпадают с отдельными людьми, в любой имеющейся IRC сети и в любой момент
253 
+времени. К исключениям относятся, помимо прочего, и шлюзы NAT (национальных
254 
+точек подключения), которые в особых случаях могут быть перераспределены. В
255 
+то время как сама битва за прекращение использования открытых
256 
+прокси-серверов обречена на поражение, бороться с отдельными неадекватными
257 
+пользователями IRC сетей удается. В конце концов, таким пользователям
258 
+надоедает и они уходят. </p>
259 
+
260 
+<p>Но на самом деле решением было бы внедрение систем аутентификации уровня
261 
+приложений, которые бы впускали адекватных и блокировали неадекватных
262 
+пользователей. Такие системы должны основываться на своего рода
263 
+собственности человека (такой как известный только ей/ему пароль), а не на
264 
+характеристиках пути, по которому передаются пакеты информации. </p>
265 
+
266 
+<p>Конечно же, не все IRC сети пытаются блокировать узлы Tor. В конце концов,
267 
+только небольшое количество людей используют сеть Tor для конфиденциального
268 
+общения через IRC с тем, чтобы осуществлять легитимные коммуникации без
269 
+раскрытия своей личной информации. Каждая IRC сеть должна самостоятельно
270 
+решить, стоит ли блокирование нескольких миллионов IP-адресов, которые
271 
+теоретически могут быть использованы плохими людьми, потери вклада от
272 
+адекватных пользователей сети Tor. </p>
273 
+
274 
+<p>Если вас блокируют, свяжитесь с операторами сети и объясните им свою
275 
+ситуацию. Они, возможно, вообще понятия не имеют о существовании сети Tor,
276 
+или не осведомлены о том, что блокируемые ими имена хостов являются
277 
+выводными узлами сети Tor. Если вы объясните проблему, и они решат, что Tor
278 
+должен быть заблокирован, вам, возможно, стоит перейти на другую сеть,
279 
+которая более открыта для свободной речи. Возможно, также стоит пригласить
280 
+операторов на #tor на irc.oftc.net и они, в конце концов, поймут, что не все
281 
+мы являемся исчадьем ада. </p>
282 
+
283 
+<p>В заключении, если вы узнали о IRC сети, которая блокирует Tor, или
284 
+отдельный выводной узел нашей сети, пожалуйста, поместите эту информацию в
285 
+<a
286 
+href="https://wiki.torproject.org/wiki/TheOnionRouter/BlockingIrc">систему
287 
+отслеживания IRC блокировки</a> с тем, чтобы ей могли воспользоваться
288 
+другие. Хотя бы одна IRC сеть в итоге разблокирует выводные узлы, признав,
289 
+что блокирование было ошибочным. </p>
290 
+
291 
+<a id="SMTPBans"></a>
292 
+<h3><a class="anchor" href="#SMTPBans">Ваши узлы заблокированы почтовым
293 
+сервером, который я хочу использовать.</a></h3>
294 
+
295 
+<p>Несмотря на то, что <a href="#WhatAboutSpammers">сеть Tor не предназначена
296 
+для спаминга</a>, некоторые особо усердные составители черных списков, по
297 
+всей видимости, считают, что все открытые сети аналогичные Tor являются злом
298 
+— они пытаются оказывать давление на администраторов сетей в вопросах
299 
+правил, сервисов и маршрутизации, а затем требуют у жертв выкуп. </p>
300 
+
301 
+<p>Если администраторы вашего сервера решили воспользоваться такими черными
302 
+списками и запретить входящую почту, вам стоит с ними связаться и рассказать
303 
+о проекте Tor и о выводных правилах нашей сети. </p>
304 
+
305 
+<a id="Bans"></a>
306 
+<h3><a class="anchor" href="#Bans">Я хочу заблокировать сеть Tor на моем
307 
+сервисе.</a></h3>
308 
+
309 
+<p>Нам очень жаль об этом слышать. Есть некоторые ситуации, в которых вполне
310 
+логично блокировать доступ анонимных пользователей к сервису сети
311 
+Интернет. Но во многих случаях есть более простые решения вашей проблемы,
312 
+которые позволят пользователям безопасно подключаться к вашему веб сайту.</p>
313 
+
314 
+<p>В первую очередь спросите себя, есть ли в вашем конкретном случае
315 
+возможность внедрения механизма определения адекватности
316 
+пользователей. Например, вы можете разделить сайт на несколько «территорий»
317 
+или распределить конкретные привилегии, такие как возможность оставлять
318 
+сообщения/комментарии, доступные только для зарегистрированных
319 
+пользователей. Можно легко создать постоянно обновляемый список IP-адресов
320 
+узлов Tor, которые разрешают подключение к вашему сервису, таким образом, вы
321 
+могли бы настроить распознавание пользователей сети Tor на вашем сервисе. В
322 
+этом случае вы можете иметь многоуровневый доступ, не блокируя каждый
323 
+отдельный аспект вашего сервиса. </p>
324 
+
325 
+<p>Например, <a href="http://freenode.net/policy.shtml#tor">IRC сеть
326 
+Freenode</a> испытывала трудности с координированной группой хакеров,
327 
+которые подключались к каналу и скрыто овладевали разговором; но когда они
328 
+пометили всех пользователей, подключавшихся через узлы Tor, как "анонимных
329 
+пользователей", исключая возможность хакеров затеряться в толпе, хакеры
330 
+вернулись к использованию своих открытых прокси-серверов и бот сетей. </p>
331 
+
332 
+<p>Во-вторых, учтите, что сервисом Tor только из соображений сохранения
333 
+конфиденциальности информации ежедневно пользуются сотни тысяч людей —
334 
+например, для защиты от сбора данных рекламными компаниями при совершении
335 
+совершенно обычных повседневных операций. Другие используют Tor, как
336 
+единственный их способ обойти локальные ограничивающие брандмауэры. Многие
337 
+пользователи сети Tor подключаются к вашему сервису для выполнения
338 
+совершенно нормальных действий. Вам нужно определиться стоит ли блокирование
339 
+нескольких миллионов IP-адресов, которые теоретически могут быть
340 
+использованы плохими людьми, потери вклада от адекватных пользователей сети
341 
+Tor, которые являются настоящими либо потенциальными пользователями вашего
342 
+ресурса. (Зачастую люди не могут адекватно определить, как много вежливых
343 
+пользователей сети Tor подключаются к их сервису — вы никогда их не
344 
+заметите, пока среди них не появляются невежливые.)</p>
345 
+
346 
+<p>Вам также стоит спросить себя, как вы будете поступать по отношению к другим
347 
+сервисам, которые позволяют множеству пользователей работать через несколько
348 
+IP-адресов. Сеть Tor в этом смысле не сильно отличается от AOL (America
349 
+On-Line).</p>
350 
+
351 
+<p>В заключении, пожалуйста, помните, что узлы Tor имеют <a href="<page
352 
+faq>#ExitPolicies">индивидуальные правила вывода</a>. Многие из них вообще
353 
+не допускают внешних соединений. Многие из тех, которые разрешают некоторые
354 
+внешние соединения возможно уже запретили доступ к вашему сервису. Если вы
355 
+начинаете блокировать узлы, вам стоит проанализировать правила вывода
356 
+ретрансляторов Tor и блокировать только те из них, которые разрешают
357 
+соединения с вашим сервисом; при этом необходимо обратить внимание на тот
358 
+факт, что правила вывода отдельных узлов могут меняться (так же как и общий
359 
+список узлов сети).</p>
360 
+
361 
+<p>Если вы действительно хотите заблокировать доступ к вашему сервису через
362 
+узлы Tor, мы готовы предоставить вам <a
363 
+href="https://check.torproject.org/cgi-bin/TorBulkExitList.py">список
364 
+выводных узлов Tor</a> или <a href="<page tordnsel/index>">список,
365 
+основанный на DNS запросах</a>.
366 
+</p>
367 
+
368 
+<p>
369 
+(Некоторые системные администраторы блокируют диапазоны IP-адресов в связи с
370 
+официальным предписанием или в ответ на определенную модель
371 
+злоупотребления. При этом многие из них также запрашивают информацию о
372 
+выводных узлах Tor для составления белых списков с тем, чтобы разрешить
373 
+доступ к своей системе только пользователям Tor. Эти документы также полезны
374 
+для составления белых списков.)
375 
+</p>
376 
+
377 
+<a id="TracingUsers"></a>
378 
+<h3><a class="anchor" href="#TracingUsers">У меня есть неопровержимый довод для
379 
+вычисления пользователя Tor. Вы можете помочь?</a></h3>
380 
+
381 
+<p>
382 
+Нет ничего, что могли бы сделать разработчики Tor для отслеживания
383 
+пользователей сервиса. Та же защита, которая не дает посторонним людям
384 
+взломать анонимность сети Tor, не дает нам возможность отслеживать
385 
+пользователей сети.
386 
+</p>
387 
+
388 
+<p>
389 
+Некоторые фанаты предлагали, чтобы мы модифицировали Tor и встроили в наше
390 
+программное обеспечение так называемый <a href="<page faq>#Backdoor">«черных
391 
+ход»</a>. Есть две большие проблемы, которые связаны с реализацией этой
392 
+идеи. Во-первых, это слишком ослабит систему в техническом
393 
+плане. Централизованные системы с одним путем связи пользователей с их
394 
+действиями имеют дыры в защите, которые могут использоваться для различного
395 
+рода атак; более того, необходимы механизмы управления, обеспечивающие
396 
+должную надежность работы такой системы, создать которые очень
397 
+сложно. Во-вторых, мошенников <a href="#WhatAboutCriminals">таким способом
398 
+поймать все равно не удастся</a>, так как они станут использовать другие
399 
+средства обеспечения своей анонимности («кража личности», взлом компьютеров
400 
+и использование их как связных узлов и т.д.).
401 
+</p>
402 
+
403 
+<p>
404 
+Но помните, это не означает, что сеть Tor является неуязвимой. Традиционные
405 
+полицейские методы все же могут быть очень эффективны против сервиса Tor, к
406 
+ним, например, относятся интервьюирование подозреваемых, надзор,
407 
+установление клавиатурных жучков, анализ, провокации и другие физические
408 
+расследования.
409 
+</p>
410 
+
411 
+<a id="RemoveContent"></a>
412 
+<h3><a class="anchor" href="#RemoveContent">Я хочу удалить часть содержимого с
413 
+адреса .onion.</a></h3>
414 
+<p>The Tor Project does not host, control, nor have the ability to discover the
415 
+owner or location of a .onion address.  The .onion address is an address
416 
+from <a href="<page hidden-services>">a hidden service</a>.  The name you
417 
+see ending in .onion is a hidden service descriptor.  It's an automatically
418 
+generated name which can be located on any Tor relay or client anywhere on
419 
+the Internet.  Hidden services are designed to protect both the user and
420 
+service provider from discovering who they are and where they are from.  The
421 
+design of hidden services means the owner and location of the .onion site is
422 
+hidden even from us.</p>
423 
+<p>Но помните, это не означает, что скрытые сервисы являются
424 
+неуязвимыми. Традиционные полицейские методы все же могут быть очень
425 
+эффективны, к ним, например, относятся интервьюирование подозреваемых,
426 
+надзор, установление клавиатурных жучков, анализ, провокации и другие
427 
+физические расследования.</p>
428 
+<p>If you have a complaint about child pornography, you may wish to report it
429 
+to the National Center for Missing and Exploited Children, which serves as a
430 
+national coordination point for investigation of child pornography: <a
431 
+href="http://www.missingkids.com/">http://www.missingkids.com/</a>.  We do
432 
+not view links you report.</p>
433 
+
434 
+<a id="LegalQuestions"></a>
435 
+<h3><a class="anchor" href="#LegalQuestions">У меня есть правовые вопросы
436 
+относительно злоупотреблений сервисом Tor.</a></h3>
437 
+
438 
+<p>Мы – только разработчики. Мы можем ответить на технические вопросы, но мы не
439 
+те, кто может говорить о правовых вопросах или аспектах. </p>
440 
+
441 
+<p>Пожалуйста, обратите внимание на <a href="<page eff/tor-legal-faq>">Список
442 
+правовых вопросов, касающихся деятельности Tor (Tor Legal FAQ)</a>, и
443 
+свяжитесь с EFF (Electronic Frontier Foundation) напрямую в случае, если у
444 
+вас возникли дополнительные правовые вопросы. </p>
445 
+
446 
+  </div>
447 
+
448 
+
449 
+#include <foot.wmi>
ru/faq.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,1286 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22360 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor FAQ" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+
14 
+
15 
+<!-- PUT CONTENT AFTER THIS TAG -->
16 
+<h2>Часто задаваемые вопросы по использованию Tor (FAQ)</h2>
17 
+<hr />
18 
+
19 
+<p>Основные вопросы:</p>
20 
+<ul>
21 
+<li><a href="#WhatIsTor">Что такое Tor?</a></li>
22 
+<li><a href="#Torisdifferent">Чем Tor отличается от других прокси сервисов?</a></li>
23 
+<li><a href="#CompatibleApplications">Какие программы можно использовать с
24 
+Tor?</a></li>
25 
+<li><a href="#WhyCalledTor">Как появилось название Tor?</a></li>
26 
+<li><a href="#Backdoor">Существует ли "черный ход" в программном коде Tor?</a></li>
27 
+<li><a href="#DistributingTor">Могу ли я предоставлять Tor в CD приложении к
28 
+моему журналу?</a></li>
29 
+<li><a href="#SupportMail">Как получить ответ на мои вопросы по использованию
30 
+Tor от службы поддержки?</a></li>
31 
+<li><a href="#WhySlow">Почему Tor работает медленно?</a></li>
32 
+<li><a href="#Funding">Что проект Tor сделал бы при наличии большего
33 
+финансирования?</a></li>
34 
+</ul>
35 
+
36 
+<p>Компиляция и установка:</p>
37 
+<ul>
38 
+<li><a href="#HowUninstallTor">Как удалить программу Tor с компьютера?</a></li>
39 
+<li><a href="#PGPSigs">Для чего нужны "sig" файлы, предоставленные на странице
40 
+загрузки?</a></li>
41 
+<li><a href="#CompileTorWindows">Как скомпилировать Tor под Windows?</a></li>
42 
+<li><a href="#VirusFalsePositives">Почему в моем исполнимом файле Tor (tor.exe)
43 
+обнаруживается вирус или шпионское ПО?</a></li>
44 
+<li><a href="#LiveCD">Существует ли LiveCD или другой пакет программ, включающий
45 
+Tor?</a></li>
46 
+</ul>
47 
+
48 
+<p>Работа с Tor:</p>
49 
+
50 
+<p>Работа с программой-клиентом Tor:</p>
51 
+<ul>
52 
+<li><a href="#ChooseEntryExit">Могу ли я выбирать узлы (или страны),
53 
+используемые для ввода/вывода?</a></li>
54 
+</ul>
55 
+
56 
+<p>Работа с Tor ретранслятором:</p>
57 
+<ul>
58 
+<li><a href="#RelayFlexible">Насколько стабильным должен быть мой
59 
+ретранслятор?</a></li>
60 
+<li><a href="#ExitPolicies">Я бы установил ретранслятор, но я не хочу иметь дело
61 
+с различного рода злоупотреблениями.</a></li>
62 
+<li><a href="#RelayOrBridge">Что лучше установить обычный ретранслятор или
63 
+ретранслятор типа мост?</a></li>
64 
+<li><a href="#RelayMemory">Почему мой ретранслятор использует так много
65 
+памяти?</a></li>
66 
+<li><a href="#WhyNotNamed">Почему моему ретранслятору не присваивается имя?</a></li>
67 
+</ul>
68 
+
69 
+<p>Использование скрытого сервиса Tor:</p>
70 
+
71 
+<p>Анонимность и безопасность:</p>
72 
+<ul>
73 
+<li><a href="#KeyManagement">Хочу информацию обо всех ключах, используемых
74 
+Tor.</a></li>
75 
+</ul>
76 
+
77 
+<p>Альтернативные планы, которые мы не осуществили (пока):</p>
78 
+<ul>
79 
+<li><a href="#EverybodyARelay">Нужно сделать каждого пользователя Tor
80 
+ретранслятором.</a></li>
81 
+</ul>
82 
+
83 
+<p>Угрозы:</p>
84 
+<ul>
85 
+<li><a href="#Criminals">Не дает ли Tor возможность преступникам осуществлять их
86 
+коварные планы?</a></li>
87 
+<li><a href="#RespondISP">Как мне отреагировать на запросы Интернет провайдера
88 
+по поводу моего выводного ретранслятора?</a></li>
89 
+</ul>
90 
+
91 
+<p>For other questions not yet on this version of the FAQ, see the <a
92 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ">wiki
93 
+FAQ</a> for now.</p>
94 
+
95 
+<hr />
96 
+
97 
+<a id="General"></a> <a id="WhatIsTor"></a>
98 
+<h3><a class="anchor" href="#WhatIsTor">Что такое Tor?</a></h3>
99 
+
100 
+<p>
101 
+Название "Tor" может относиться к нескольким различным компонентам.
102 
+</p>
103 
+
104 
+<p>
105 
+Программное обеспечение Tor – это программа, которую вы можете установить на
106 
+свой компьютер для повышения безопасности при работе в сети Интернет. ПО Tor
107 
+защищает вас путем переадресации ваших запросов через сеть ретрансляторов,
108 
+предоставляемых волонтерами со всего мира: в результате люди имеющие доступ
109 
+к просмотру вашего Интернет соединения не могут получить информацию о том,
110 
+какие сайты вы посещаете, а посещаемые вами сайты не могут определить ваше
111 
+физическое местоположение. Этот набор волонтерских ретрансляторов называется
112 
+сетью Tor. Вы можете узнать больше о процессе работы Tor, прочитав <a
113 
+href="<page overview>">страницу обзора</a>.
114 
+</p>
115 
+
116 
+<p>
117 
+Проект Tor является некоммерческой (благотворительной) организацией,
118 
+поддерживающей и развивающей программное обеспечение Tor.
119 
+</p>
120 
+
121 
+<hr />
122 
+
123 
+<a id="Torisdifferent"></a>
124 
+<h3><a class="anchor" href="#Torisdifferent">Чем Tor отличается от других прокси
125 
+сервисов?</a></h3>
126 
+<p>
127 
+Обычные провайдеры прокси сервисов устанавливают сервер в сети Интернет и
128 
+позволяют вам использовать его для перенаправления своего трафика. Это
129 
+создает простую, легкую в поддержании архитектуру. Трафик всех пользователей
130 
+проходит через один и тот же сервер. Провайдер может требовать плату за
131 
+использование прокси сервера, или финансироваться за счет размещения рекламы
132 
+на сервере. В самой простой конфигурации вам ничего не надо
133 
+устанавливать. Вам необходимо только указать своему браузеру путь к
134 
+желаемому прокси серверу. Простые провайдеры прокси сервисов являются
135 
+нормальным решением в том случае, если вам не нужна защита вашей
136 
+конфиденциальности и анонимности в сети Интернет, и вы доверяете провайдеру
137 
+услуг. Некоторые простые провайдеры прокси сервисов используют
138 
+SSL-шифрование для обеспечения безопасности вашего подключения к их
139 
+серверу. Это может защитить вас от «прослушивания» местными операторами,
140 
+например, в кафе с бесплатным Интернет подключением (wifi).
141 
+</p>
142 
+<p>
143 
+Простые провайдеры прокси сервисов также создают единственную критическую
144 
+точку. Провайдер знает кто вы, и какие страницы вы посещаете в сети
145 
+Интернет. Они могут просматривать ваш трафик, так как он проходит через их
146 
+сервер. В некоторых случаях они могут видеть ваш кодированный трафик, в то
147 
+время как они пересылают его на страницу банковских услуг (e-banking), или
148 
+на сайты электронных магазинов. Вы должны доверять провайдеру в том, что он
149 
+не злоупотребляет получаемой информацией, т.е. не просматривает ваш трафик,
150 
+не вставляет свои собственные рекламные объявления в ваш поток трафика, и не
151 
+записывает вашу персональную информацию.
152 
+</p>
153 
+<p>
154 
+Система Tor пропускает ваш трафик через как минимум три разных сервера,
155 
+прежде чем отправить его в пункт назначения (например, на веб сайт). Система
156 
+Tor не модифицирует данные и даже не знает, что вы через неё
157 
+отправляете. Она всего лишь перенаправляет ваш полностью зашифрованный
158 
+трафик через сеть Tor и позволяет ему всплыть где-то в другой стране мира,
159 
+абсолютно неизмененным. Программа-клиент Tor необходима, так как мы
160 
+полагаем, что вы доверяете своему локальному компьютеру. Программа-клиент
161 
+Tor управляет шифрованием и путем прохода данных через сеть. Ретрансляторы,
162 
+расположенные по всему миру только пересылают зашифрованные пакеты между
163 
+собой.</p>
164 
+<p>
165 
+<dl>
166 
+<dt>Не может ли первый сервер меня идентифицировать?</dt><dd>Возможно. Только первый из трех серверов может видеть зашифрованный трафик
167 
+Tor, исходящий с вашего компьютера. Однако он не знает, кто вы и что вы
168 
+делаете посредством сети Tor. Он только лишь видит «что с вашего IP адреса
169 
+используется Tor". Сервис Tor не является незаконным нигде в мире, так что
170 
+просто использование Tor – не проблема. Вы все равно защищены от того, что
171 
+узел (ретранслятор) распознает кто вы, и определит, что вы делаете в сети
172 
+Интернет.</dd>
173 
+<dt>Может ли третий сервер видеть мой трафик?</dt><dd>Возможно. Третий из трех серверов может видеть отсылаемый вами в сеть Tor
174 
+трафик. Но ему не будет известно, кто отсылает этот трафик. Если вы
175 
+используете шифрование, например, при использовании сервисов работы с
176 
+банковским счетом через Интернет (всегда шифрованное соединение), при
177 
+посещении веб сайта электронной торговли (всегда шифрованное соединение),
178 
+или во время шифрованного подключения к почтовому серверу и т.д., узлу будет
179 
+известно только направление информационного обмена. Он не сможет увидеть
180 
+данные внутри потока трафика. Вы в любом случае защищены от идентификации
181 
+вас этим узлом, а если вы используете шифрование, то и от распознавания
182 
+посылаемых вами в этом направлении данных.</dd>
183 
+</dl>
184 
+</p>
185 
+
186 
+<hr />
187 
+
188 
+<a id="CompatibleApplications"></a>
189 
+<h3><a class="anchor" href="#CompatibleApplications">Какие программы можно
190 
+использовать с Tor?</a></h3>
191 
+
192 
+<p>
193 
+Существует два важных пункта «Торификации» программы: анонимность уровня
194 
+соединения и анонимность уровня приложения. Анонимность уровня соединения
195 
+фокусируется на обеспечении пересылки данных приложения через канал Tor. Эта
196 
+часть обеспечивается путем настройки программы на использование клиента Tor
197 
+в качестве "socks" прокси, но существуют и другие пути решения этой
198 
+задачи. Для обеспечения анонимности уровня приложения вам необходимо
199 
+убедиться, что информация, рассылаемая приложением, не содержит
200 
+конфиденциальной информации. (Даже если соединения проложены через Tor, вам
201 
+все равно не надо указывать чувствительную информацию, такую, например, как
202 
+ваше имя.) Эта вторая часть должна делаться на базе конкретной программы,
203 
+поэтому мы не можем порекомендовать большое количество программ для
204 
+безопасного использования с Tor.
205 
+</p>
206 
+
207 
+<p>
208 
+Большая часть нашей работы до настоящего момента была сфокусирована на
209 
+браузере Firefox. Пакет программ, <a href="<page download>">предоставленный
210 
+на нашем сайте</a>, автоматически устанавливает <a href="<page
211 
+torbutton/index>">дополнение Torbutton для Firefox</a>, если у вас
212 
+установлен Firefox. Начиная с версии 1.2.0, приложение Torbutton заботится о
213 
+проблемах, связанных как с уровнем соединения, так и с уровнем приложения.
214 
+</p>
215 
+
216 
+<p>
217 
+There are plenty of other programs you can use with Tor, but we haven't
218 
+researched the application-level anonymity issues on them well enough to be
219 
+able to recommend a safe configuration. Our wiki has a list of instructions
220 
+for <a
221 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorifyHOWTO">Torifying
222 
+specific applications</a>. There's also a <a
223 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/SupportPrograms">list
224 
+of applications that help you direct your traffic through Tor</a>.  Please
225 
+add to these lists and help us keep them accurate!
226 
+</p>
227 
+
228 
+<hr />
229 
+
230 
+<a id="WhyCalledTor"></a>
231 
+<h3><a class="anchor" href="#WhyCalledTor">Как появилось название Tor?</a></h3>
232 
+
233 
+<p>
234 
+Это связано с тем, что Tor является луковой (т.е. многослойной) системой
235 
+маршрутизации. Когда мы запускали многослойный маршрутизатор следующего
236 
+поколения в 2001-2002, мы говорили людям, что мы работаем над многослойной
237 
+системой маршрутизации. На что они говорили: «Ясно, над какой?». И хотя
238 
+луковая (многослойная) маршрутизация стала стандартным термином, название
239 
+Tor пошло от действовавшего тогда <a
240 
+href="http://www.onion-router.net/">проекта луковой маршрутизации</a>,
241 
+проводимого Naval Research Lab.
242 
+</p>
243 
+
244 
+<p>
245 
+(Помимо прочего, название имеет интересный перевод с Немецкого и Турецкого
246 
+языка.)
247 
+</p>
248 
+
249 
+<p>
250 
+Важно: несмотря на то, что оригинальное название произошло от акронима, Tor
251 
+не пишется "TOR". Только первая буква - заглавная. На самом деле, мы, как
252 
+правило, можем выделить тех людей, которые не читали информацию на нашем веб
253 
+сайте (а вместо этого узнали все, что они знают о Tor из новостных статей)
254 
+по тому факту, что они обычно пишут название неправильно.
255 
+</p>
256 
+
257 
+<hr />
258 
+
259 
+<a id="Backdoor"></a>
260 
+<h3><a class="anchor" href="#Backdoor">Существует ли "черный ход" в программном
261 
+коде Tor?</a></h3>
262 
+
263 
+<p>
264 
+Нет абсолютно никаких черных ходов (имеется в виду часть кода, дающая
265 
+спецслужбам возможность отслеживать информационный обмен) в программе
266 
+Tor. Никто не просил нас добавить таковые в программный код. Более того, мы
267 
+знаем нескольких хороших адвокатов, которые говорят, что, скорее всего,
268 
+никто и не попробует требовать от нас подобных действий под юрисдикцией
269 
+США. А если потребуют, мы будем с ними судиться, и, скорее всего, (как
270 
+говорят адвокаты) выиграем.
271 
+</p>
272 
+
273 
+<p>
274 
+Мы считаем, что встраивание так называемого черного хода в Tor было бы
275 
+крайне безответственным по отношению к нашим пользователям, более того, это
276 
+был бы плохой прецедент для программного обеспечения по Интернет
277 
+безопасности в целом. Если мы когда-либо вставим черный ход в наш
278 
+программный продукт, это разрушит нашу профессиональную репутацию. Никто и
279 
+никогда больше не станет доверять нашему программному обеспечению — по
280 
+общепонятной причине!
281 
+</p>
282 
+
283 
+<p>
284 
+Но все же, существует масса хитрых атак, которые люди могут
285 
+осуществлять. Некоторые могут выдавать себя за нас, проникать на наши
286 
+компьютеры, или осуществлять другие подобные деяния. Сервис Tor является
287 
+продуктом с открытым программным кодом (open source). И вам необходимо
288 
+всегда проверять источник (или хотя бы diff-ы, начиная с последнего релиза)
289 
+в подозрительных случаях. Если мы (или распространители) не указываем ресурс
290 
+(источник), это знак того, что что-то может быть не так… Вам стоит также
291 
+проверять  <a href="<page verifying-signatures>"> PGP подписи</a> релизов,
292 
+чтобы убедиться в том, что никто не "поработал" над сайтами дистрибьюторов.
293 
+</p>
294 
+
295 
+<p>
296 
+Помимо прочего, есть возможность появления случайных ошибок в Tor, которые
297 
+могут повлиять на вашу анонимность. Периодически мы находим и исправляем
298 
+относящиеся к анонимности ошибки, поэтому постарайтесь держать вашу версию
299 
+Tor обновленной.
300 
+</p>
301 
+
302 
+<hr />
303 
+
304 
+<a id="DistributingTor"></a>
305 
+<h3><a class="anchor" href="#DistributingTor">Могу ли я предоставлять Tor в CD
306 
+приложении к моему журналу?</a></h3>
307 
+
308 
+<p>
309 
+Да.
310 
+</p>
311 
+
312 
+<p>
313 
+Программное обеспечение Tor является <a
314 
+href="https://www.fsf.org/">бесплатным</a>. Это означает, что мы даем вам
315 
+право распространять программное обеспечение Tor, как в модифицированном,
316 
+так и в неизмененном виде, и платно и бесплатно. Вы не должны спрашивать нас
317 
+о специальном разрешении.
318 
+</p>
319 
+
320 
+<p>
321 
+Однако если вы хотите распространять программное обеспечение Tor вы должны
322 
+следовать нашей <a href="<gitblob>LICENSE">ЛИЦЕНЗИИ</a>. Главным образом это
323 
+означает, что вы должны добавлять наш файл ЛИЗЕНЗИИ к любой распространяемой
324 
+вами части программного обеспечения Tor.
325 
+</p>
326 
+
327 
+<p>
328 
+Большинство людей, которые задают нам этот вопрос, не хотят распространять
329 
+только программное обеспечение Tor. Они хотят распространять пакеты Tor,
330 
+которые, как правило, включают <a
331 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a> и <a
332 
+href="<page vidalia/index>">Vidalia</a>. В этом случае вам также необходимо
333 
+будет следовать и лицензиям этих программ. Обе они распространяются по <a
334 
+href="https://www.fsf.org/licensing/licenses/gpl.html">лицензии GNU</a>
335 
+(General Public License – стандартная общественная лицензия). Самый простой
336 
+путь удовлетворить условиям лицензий этих программ – это добавлять их
337 
+исходный код везде, где присутствуют сами программные пакеты. Найдите
338 
+исходные пакеты на страницах закачки веб сайта <a href="<page
339 
+vidalia/index>">Vidalia</a> и <a
340 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/">Polipo</a>.
341 
+</p>
342 
+
343 
+<p>
344 
+Вы также должны убедиться, что не вводите вашего читателя в заблуждение
345 
+касательно того, чем является Tor, кто его создатели, и какие сервисы он
346 
+предоставляет (а какие нет). Обратитесь к нашему <a href="<page
347 
+trademark-faq>">списку часто задаваемых вопросов (FAQ) по торговой марке</a>
348 
+для получения более подробной информации.
349 
+</p>
350 
+
351 
+<p>
352 
+В конце концов, вы должны осознавать, что мы выпускаем новые версии
353 
+программного обеспечения Tor часто, и иногда мы вносим изменения, не
354 
+совместимые с более старыми версиями программы. Так что если вы
355 
+распространяете определенную версию программного обеспечения Tor, она,
356 
+возможно, не будет поддерживаться — или даже работать — шесть месяцев
357 
+спустя. Это факт действительный для любого программного обеспечения Интернет
358 
+безопасности, находящегося в процессе постоянного развития.
359 
+</p>
360 
+
361 
+<hr />
362 
+
363 
+<a id="SupportMail"></a>
364 
+<h3><a class="anchor" href="#SupportMail">Как получить ответ на мои вопросы по
365 
+использованию Tor от службы поддержки?</a></h3>
366 
+
367 
+<p>
368 
+Многие люди отправляют частные электронные письма разработчикам, или письма
369 
+на адреса наших внутренних <a href="<page contact>">списков</a>, задавая
370 
+вопросы о проблемах с установкой – один не может настроить брандмауэр,
371 
+другой – правильно сконфигурировать Polipo и т.д. Иногда наши волонтеры
372 
+могут ответить на эти письма, но обычно они проводят большую часть своего
373 
+времени, работая над задачами усовершенствования программного обеспечения,
374 
+что приносит пользу большему числу людей. Это особенно касается тех случаев,
375 
+когда задаваемый вопрос уже освещен в <a href="<page
376 
+documentation>">документации</a> или в этом списке часто задаваемых вопросов
377 
+(FAQ). Мы не ненавидим вас; мы просто заняты.
378 
+</p>
379 
+
380 
+<p>
381 
+Поэтому если мы не отвечаем на ваш запрос, сначала проверьте страницу <a
382 
+href="<page documentation>">документации</a>, а также этот список часто
383 
+задаваемых вопросов (FAQ), и убедитесь, что ваш вопрос еще не освещен. После
384 
+этого прочтите раздел <a
385 
+href="http://www.catb.org/~esr/faqs/smart-questions.html">«Как правильно
386 
+задавать вопросы» ("How to ask questions the smart way")</a>. Если это вам
387 
+не помогло, обратите внимание на то, что у нас есть <a href="<page
388 
+documentation>#Support">IRC канал</a>, где вы можете задать ваши вопросы (но
389 
+если они до сих пор недоработаны, плохо согласованы или не о Tor, вы, скорее
390 
+всего, не получите там помощи). В конце концов, люди из <a href="<page
391 
+documentation>#MailingLists">списка подписчиков Tor-talk</a>, возможно,
392 
+смогут дать вам несколько подсказок, если у других тоже была подобная вашей
393 
+проблема. Перед тем как задавать вопрос, обязательно просмотрите <a
394 
+href="http://archives.seul.org/or/talk/"> архив</a>.
395 
+</p>
396 
+
397 
+<p>
398 
+Другой стратегией может быть <a href="<page docs/tor-doc-relay>">создание
399 
+ретранслятора Tor</a> и/или <a href="<page donate>">пожертвование денег</a>
400 
+<a href="<page volunteer>">или времени</a> на наш проект. Мы уделяем большее
401 
+внимание людям, которые продемонстрировали интерес и обязательства перед
402 
+сообществом Tor.
403 
+</p>
404 
+
405 
+<p>
406 
+Если вы нашли решение, пожалуйста, примите участие и отвечайте на вопросы
407 
+через IRC канал или список подписчиков.
408 
+</p>
409 
+
410 
+<hr />
411 
+
412 
+<a id="WhySlow"></a>
413 
+<h3><a class="anchor" href="#WhySlow">Почему Tor работает медленно?</a></h3>
414 
+
415 
+<p>
416 
+Существует масса причин тому, что сеть Tor в настоящее время работает
417 
+медленно.
418 
+</p>
419 
+
420 
+<p>
421 
+Но перед тем как мы ответим на вопрос, вы должны понимать, что Tor никогда
422 
+не будет «летать». Ваш трафик проходит через сеть волонтерских компьютеров в
423 
+разных частях света, так что «узкие места» и сетевая задержка всегда будут
424 
+существовать. Вам не стоит ожидать высокоскоростного широкополосного
425 
+подключения через Tor.
426 
+</p>
427 
+
428 
+<p>
429 
+Но это не означает, что сеть не может быть улучшена. Сеть Tor в настоящее
430 
+время является довольно маленькой в сравнении с количеством людей, которые
431 
+пытаются её использовать, и многие из этих пользователей не понимают или не
432 
+думают о том, что Tor не может сейчас быть использован для передачи трафика
433 
+файлообменных программ.
434 
+</p>
435 
+
436 
+<p>
437 
+Для более подробного ответа, смотрите <a
438 
+href="https://blog.torproject.org/blog/why-tor-is-slow"> блог Роджера на эту
439 
+тему</a>, который включает подробные PDF и видео.
440 
+</p>
441 
+
442 
+<p>
443 
+Что можете сделать вы для улучшения?
444 
+</p>
445 
+
446 
+<ul>
447 
+
448 
+<li>
449 
+<a href="<page docs/tor-doc-relay>">Настройте ваш Tor на ретрансляцию
450 
+трафика для других</a>. Помогите сделать сеть Tor достаточно большой для
451 
+обеспечения конфиденциальности и безопасности в сети Интернет для всех
452 
+пользователей, которые этого хотят.
453 
+</li>
454 
+
455 
+<li>
456 
+<a href="<page gui/index>">Помогите нам сделать Tor более удобным</a>. Нам
457 
+особенно нужны люди, которые могут помочь сделать настройку Tor в качестве
458 
+ретранслятора еще более простой. Также нам нужна помощь с ясной, простой
459 
+документацией для облегчения процедуры установки программы.
460 
+</li>
461 
+
462 
+<li>
463 
+Сейчас в работе сети Tor существуют некоторые «узкие места». Помогите нам в
464 
+проведении экспериментов для отслеживания и демонстрации проблемных участков
465 
+сети, после чего нам будет легче сфокусироваться на их исправлении.
466 
+</li>
467 
+
468 
+<li>
469 
+There are some steps that individuals can take to improve their Tor
470 
+performance. <a
471 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/FireFoxTorPerf">You
472 
+can configure your Firefox to handle Tor better</a>, <a
473 
+href="http://www.pps.jussieu.fr/~jch/software/polipo/tor.html">you can use
474 
+Polipo with Tor</a>, or you can try <a href="<page download>">upgrading to
475 
+the latest version of Tor</a>.  If this works well, please help by
476 
+documenting what you did, and letting us know about it.
477 
+</li>
478 
+
479 
+<li>
480 
+Сеть Tor, помимо прочего, нуждается в некоторых архитектурных
481 
+изменениях. Первым важным изменением является <a
482 
+href="#EverybodyARelay">предоставление лучшего сервиса тем людям, которые
483 
+ретранслируют трафик</a>. Мы работаем над этим и закончим скорее, если у нас
484 
+получится уделять этому вопросу больше времени.
485 
+</li>
486 
+
487 
+<li>
488 
+Помогите нам в работе с мелочами, чтобы мы могли уделять больше времени
489 
+усовершенствованию сервиса. Пожалуйста, посветите один момент определению
490 
+ваших навыков и интересов, а затем <a href="<page volunteer>">взгляните на
491 
+нашу волонтерскую страницу</a>.
492 
+</li>
493 
+
494 
+<li>
495 
+Помогите найти спонсоров для Tor. Вы работаете в компании или в
496 
+правительственной структуре, которая использует сервис Tor или нуждается в
497 
+обеспечении анонимности в сети Интернет, например, для осторожного
498 
+просматривания веб сайтов конкурентов, или для подключения к домашним
499 
+серверам, находясь в пути не раскрывая своё местоположение? Если ваша
500 
+организация, так или иначе, заинтересована в работе сервиса Tor, пожалуйста,
501 
+обратитесь к руководству за поддержкой для сети Tor. Без спонсоров, сервис
502 
+Tor станет еще более медленным.
503 
+</li>
504 
+
505 
+<li>
506 
+Если вы не можете помочь ни в одном из вышеперечисленных случаев, вы все же
507 
+можете помочь индивидуально, <a href="<page donate>">сделав пожертвование
508 
+(небольшой суммы денег достаточно!) на наше дело</a>. В сумме могут
509 
+получиться существенные средства!
510 
+</li>
511 
+
512 
+</ul>
513 
+
514 
+<hr />
515 
+
516 
+<a id="Funding"></a>
517 
+<h3><a class="anchor" href="#Funding">Что проект Tor сделал бы при наличии
518 
+большего финансирования?</a></h3>
519 
+
520 
+<p>
521 
+Сеть Tor на данный момент насчитывает около 1500 ретрансляторов, пропуская в
522 
+среднем более 150 Мб/сек трафика. Сеть насчитывает несколько сотен тысяч
523 
+активных пользователей. Но на данный момент Tor не является
524 
+самоподдерживающейся сетью.
525 
+</p>
526 
+
527 
+<p>
528 
+В настоящее время есть шесть главных аспектов развития/поддержания, которые
529 
+требуют внимания:
530 
+</p>
531 
+
532 
+<ul>
533 
+
534 
+<li>
535 
+Расширение: Нам необходимо продолжать расширение и децентрализацию
536 
+архитектуры сети Tor, так чтобы она могла обслуживать тысячи ретрансляторов
537 
+и миллионы пользователей. Выпуск новых стабильных версий программы – это
538 
+главное улучшение, но существует много других не мене важных факторов,
539 
+необходимых для того, чтобы Tor работал быстрей и стабильней.
540 
+</li>
541 
+
542 
+<li>
543 
+Поддержка пользователей: С таким большим числом пользователей, множество
544 
+людей постоянно задают вопросы, предлагают помощь и т.д. Нам необходимо
545 
+иметь понятную документацию, и прилагать больше усилий на координацию работы
546 
+волонтеров.
547 
+</li>
548 
+
549 
+<li>
550 
+Поддержка ретрансляторов: сеть Tor работает за счет волонтеров, но им все
551 
+равно необходима поддержка по своевременному устранению ошибок, разъяснению
552 
+в проблемных ситуациях, напоминанию о наличии обновлений и т.д. Сеть сама
553 
+является общим достоянием, и кто-то должен заботиться о том, чтобы операторы
554 
+ретрансляторов были довольны. Мы также должны работать над повышением  <a
555 
+href="#RelayOS">стабильности</a> работы программы на некоторых платформах —
556 
+например, ретрансляторы Tor в настоящее время не без проблем работают под
557 
+операционной системой Windows XP.
558 
+</li>
559 
+
560 
+<li>
561 
+Практичность: Помимо документации, нам также необходимо работать над
562 
+повышением простоты и удобства использования самого программного
563 
+обеспечения. Это включает инсталляторы, понятные графические интерфейсы
564 
+пользователя, простую настройку взаимодействия с другими приложениями и в
565 
+целом автоматизирование всех сложных и запутанных шагов настройки Tor. Мы
566 
+начали работу в этом направлении с запуском <a href="<page gui/index>">GUI
567 
+Contest</a>, но большая часть работы остается — удобство программ для
568 
+обеспечения конфиденциальности никогда не было легко обеспечиваемым.
569 
+</li>
570 
+
571 
+<li>
572 
+Средства поощрения: Мы должны найти путь мотивирования людей на настройку их
573 
+клиентских программ Tor в качестве ретрансляторов и выходных узлов, а не в
574 
+качестве клиентов системы. <a href="#EverybodyARelay">Нам необходимо
575 
+облегчить легкость настройки ретранслятора, и найти средства поощрения
576 
+людей.</a>
577 
+</li>
578 
+
579 
+<li>
580 
+Исследование: сфера анонимных коммуникаций полна сюрпризов и
581 
+неожиданностей. В свободное время, мы также помогаем в проведении
582 
+конференций по анонимности и конфиденциальности на высшем уровне (такие как
583 
+<a href="http://petsymposium.org/">PETS</a>). Мы определили набор критически
584 
+важных <a href="<page volunteer>#Research">вопросов исследования Tor</a>,
585 
+которые должны нам помочь сделать Tor защищенным против разнообразных атак,
586 
+осуществляемых через сеть Интернет. Конечно, существует больше вопросов для
587 
+исследований, над которыми мы будем работать после того, как разберемся с
588 
+этими.
589 
+</li>
590 
+
591 
+</ul>
592 
+
593 
+<p>
594 
+Мы постоянно продолжаем движение вперед по выше обозначенным аспектам, но в
595 
+настоящее время  <a href="#WhySlow">сеть Tor растет быстрее темпов, которые
596 
+могут обеспечить разработчики</a>. Сейчас самое подходящее время пополнить
597 
+число наших разработчиков, чтобы совместными усилиями мы могли обеспечить
598 
+дальнейший рост сети.
599 
+</p>
600 
+
601 
+<p>
602 
+Мы также увлечены решением связанных с полем нашей деятельности проблем,
603 
+таких как противостояние цензуре.
604 
+</p>
605 
+
606 
+<p>
607 
+Мы гордимся иметь таких <a href="<page sponsors>">спонсоров и поддерживающих
608 
+нас организаций</a>, как: Omidyar Network, International Broadcasting Bureau
609 
+(Международное Бюро Радиовещания), Bell Security Solutions (Решения
610 
+Безопасности Бэлл), Electronic Frontier Foundation (Фонд борьбы с нарушением
611 
+конфиденциальности и гражданских свобод с помощью электронных технологий),
612 
+несколько правительственных агентств и исследовательских групп, а также
613 
+сотен частных спонсоров.
614 
+</p>
615 
+
616 
+<p>
617 
+Однако этой поддержки не достаточно для поддержания конкурентоспособности
618 
+Tor на быстро меняющемся ландшафте обеспечения Интернет
619 
+конфиденциальности. Пожалуйста, <a href="<page donate>">внесите свой
620 
+вклад</a> в развитие проекта, или <a href="<page contact>">свяжитесь</a> с
621 
+нашим исполнительным директором для получения информации о предоставлении
622 
+грантов или крупных пожертвований.
623 
+</p>
624 
+
625 
+<hr />
626 
+
627 
+<a id="HowUninstallTor"></a>
628 
+<h3><a class="anchor" href="#HowUninstallTor">Как удалить программу Tor с
629 
+компьютера?</a></h3>
630 
+
631 
+<p>
632 
+Это полностью зависит от выбранного вами вида установки программы и от того,
633 
+какую операционную систему вы используете. Если вы установили пакет, тогда
634 
+надеемся, что ваш пакет «умеет» сам себя деинсталлировать. Инсталляционные
635 
+пакеты Windows включают деинсталляторы. Подходящий вид полного удаления Tor,
636 
+Vidalia и Torbutton для браузера Firefox и Polipo под любой версией Windows
637 
+описан ниже:
638 
+</p>
639 
+
640 
+<ol>
641 
+<li>На панели задач нажмите правой кнопкой мыши на иконку Vidalia (зеленый лук
642 
+или черная голова) и выберете закрыть.</li>
643 
+<li>Кликните правой кнопкой мыши по панели задач и выберете Менеджер Задач
644 
+(TaskManager). Найдите tor.exe в списке процессов. Если указанный файл
645 
+находится в процессе исполнения, кликните по нему правой кнопкой мыши и
646 
+выберите Завершить Процесс (End Process).</li>
647 
+<li>Нажмите на кнопку Пуск (Start), перейдите в пункт Программы (Programs),
648 
+выберите сначала Vidalia, а затем Удалить (Uninstall). Так вы удалите пакет
649 
+Vidalia, который включает в себя как Tor, так и Polipo.</li>
650 
+<li>Запустите браузер Firefox. Перейдите в меню Инструменты (Tools), выберите
651 
+Дополнения (Add-ons). Выберете пункт Torbutton. Нажмите на кнопку Удалить
652 
+(Uninstall).</li>
653 
+</ol>
654 
+
655 
+<p>
656 
+Если вы не будете следовать этим пунктам (например, пытаясь деинсталлировать
657 
+Vidalia, Tor, и Polipo тогда, когда приложения находятся в процессе работы),
658 
+вам придется перезагрузить компьютер и в ручную удалить папку "Program
659 
+Files\Vidalia Bundle".
660 
+</p>
661 
+
662 
+<p>
663 
+Под операционной системой Mac X, следуйте <a href="<page
664 
+docs/tor-doc-osx>#uninstall">указаниям деинсталляции</a>.
665 
+</p>
666 
+
667 
+<p>
668 
+Если вы установили программу источником, боюсь, что простого метода
669 
+деинсталляции не существует. Но по идее по умолчанию приложение
670 
+устанавливается только в папку /usr/local/ и найти файлы там довольно легко.
671 
+</p>
672 
+
673 
+<hr />
674 
+
675 
+<a id="PGPSigs"></a>
676 
+<h3><a class="anchor" href="#PGPSigs">Для чего нужны "sig" файлы,
677 
+предоставленные на странице загрузки?</a></h3>
678 
+
679 
+<p>
680 
+Это файлы, содержащие подписи PGP. Они необходимы для того, чтобы вы могли
681 
+верифицировать достоверность скаченного вами файла, то есть определить
682 
+является ли этот файл тем, который мы намеревались вам предоставить.
683 
+</p>
684 
+
685 
+<p>
686 
+Пожалуйста, прочитайте страницу <a href="<page
687 
+verifying-signatures>">верификации подписей</a> для получения дальнейшей
688 
+информации по этой теме.
689 
+</p>
690 
+
691 
+<hr />
692 
+
693 
+<a id="CompileTorWindows"></a>
694 
+<h3><a class="anchor" href="#CompileTorWindows">Как скомпилировать Tor под
695 
+Windows?</a></h3>
696 
+
697 
+<p>
698 
+Попробуйте следовать поэтапной инструкции доступной на: <a
699 
+href="<svnsandbox>doc/tor-win32-mingw-creation.txt"><svnsandbox>doc/tor-win32-mingw-creation.txt</a>.
700 
+</p>
701 
+
702 
+<p>
703 
+(Обратите внимание на тот факт, что вам не надо самостоятельно компилировать
704 
+клиентскую программу Tor, чтобы её использовать; большинство людей просто
705 
+используют пакеты доступные на <a href="<page download>">странице
706 
+загрузки</a>.)
707 
+</p>
708 
+
709 
+<hr />
710 
+
711 
+<a id="VirusFalsePositives"></a>
712 
+<h3><a class="anchor" href="#VirusFalsePositives">Почему в моем исполнимом файле
713 
+Tor (tor.exe) обнаруживается вирус или шпионское ПО?</a></h3>
714 
+
715 
+<p>
716 
+Иногда усердные антивирусные программы под операционной системой Windows, а
717 
+также детекторы шпионских программ реагируют на некоторые части бинарного
718 
+кода Tor для Windows. Наилучшим нашим объяснением этой ситуации является
719 
+ложноположительный результат проверки. В конце концов, работа антивирусных и
720 
+антишпионских программ – это игра догадок. В случае наличия данной проблемы
721 
+вам необходимо обратиться к производителю программного обеспечения и
722 
+сообщить о том, что программа выдает ложноположительный результат. Или
723 
+выбрать лучшего производителя.
724 
+</p>
725 
+
726 
+<p>
727 
+Между тем, мы просим вас не принимать наше слово на веру. Наша работа –
728 
+предоставлять источник; если вы обеспокоены, пожалуйста, <a
729 
+href="#CompileTorWindows">перекомпилируйте файл самостоятельно</a>.
730 
+</p>
731 
+
732 
+<hr />
733 
+
734 
+<a id="LiveCD"></a>
735 
+<h3><a class="anchor" href="#LiveCD">Существует ли LiveCD или другой пакет
736 
+программ, включающий Tor?</a></h3>
737 
+
738 
+<p>
739 
+В настоящее время официального диска LiveCD не существует. Мы все еще
740 
+пытаемся найти хорошие решения и понять влияние различных опций на аспекты
741 
+безопасности и анонимности. На данном этапе мы предлагаем вам просмотреть
742 
+приведенный ниже список и принять собственное решение:
743 
+</p>
744 
+
745 
+<p>
746 
+Диски LiveCDs:
747 
+</p>
748 
+
749 
+<ol>
750 
+<li><a href="https://amnesia.boum.org/">The (Amnesic) Incognito Live System</a>
751 
+is a Live System aimed at preserving your privacy and anonymity:
752 
+<ul>
753 
+<li> Все исходящие подключения к Интернету, вынуждены проходить через сеть Tor.</li>
754 
+<li> Не осталось и следа на локальных устройствах хранения, если явно не спросил.</li>
755 
+<li> Она включает в себя Firefox, Tor, Torbutton, Vidalia графического
756 
+контроллера Tor, Pidgin клиент обмена мгновенными сообщениями и многое
757 
+другое программное обеспечение.</li>
758 
+<li> Он основан на Debian GNU / Linux и поставляется с рабочего окружения GNOME.</li>
759 
+</ul>
760 
+<li><a href="http://tork.sourceforge.net/wiki/index.php/LiveCD">TorK LiveCD</a>
761 
+основан на системе Knoppix. При его создании особый упор делался на удобство
762 
+использования. Вы можете работать как анонимно, так и неанонимно, при этом
763 
+TorK информирует вас о последствиях ваших действий. Диск TorK LiveCD
764 
+является экспериментальным продуктом, так что целью является предоставление
765 
+регулярных релизов с 2007 и в последующие годы.</li>
766 
+<li><a href="http://mandalka.name/privatix/">Privatix LiveCD/USB</a> является
767 
+основанным на системе debian продуктом, включающим в свой состав tor,
768 
+firefox и torbutton. Приложения позволяют сохранять закладки и другие
769 
+настройки или данные на зашифрованном флеш диске USB.</li>
770 
+</li>
771 
+</ol>
772 
+
773 
+<p>
774 
+Пакеты для Windows:
775 
+</p>
776 
+
777 
+<ol>
778 
+<li>Пакет программ <a href="<page torbrowser/index>">Tor Browser Bundle</a> для
779 
+Windows предлагается с заранее настроенным веб браузером и может быть
780 
+запущен с USB носителя.</li>
781 
+<li>Программа <a href="http://www.janusvm.com/tor_vm/">Tor VM</a> является
782 
+преемником JanusVM. Она нуждается в вашем тестировании!</li>
783 
+<li>Программа <a href="http://janusvm.com/">JanusVM</a> является ядром и
784 
+программным обеспечением, работающим в VMWare. Она «находится» между вашим
785 
+компьютером (Windows) и Интернетом, обеспечивая анонимизацию вашего Интернет
786 
+трафика.</li>
787 
+<li><a href="http://www.xerobank.com/xB_browser.html">xB Browser</a>, ранее
788 
+известный как Torpark, - это пакет Firefox+Tor для Win32, который может быть
789 
+установлен на флеш диск USB. Для корректной работы программы необходимо
790 
+наличие операционной системы с 32-разрядным интерфейсом (Win32).</li>
791 
+</ol>
792 
+
793 
+<p>
794 
+В настоящее время не поддерживаемые диски (по нашим данным):
795 
+</p>
796 
+
797 
+<ol>
798 
+<li>Polippix / Privatlivets Fred – это датский диск LiveCD, основанный на
799 
+Knoppix; содержащий Tor и утилиты для шифрования IP-телефонии. <a
800 
+href="http://polippix.org/">Информация и загрузка</a>.</li>
801 
+<li>ELE – это Linux диск LiveCD, фокусирующийся на программах обеспечения
802 
+конфиденциальности. В его состав входит Tor и вы можете скачать его здесь:
803 
+<a
804 
+href="http://www.northernsecurity.net/download/ele/">http://www.northernsecurity.net/download/ele/</a>.</li>
805 
+<li>Virtual Privacy Machine is a Linux LiveCD that includes Firefox, Privoxy,
806 
+Tor, some IRC and IM applications, and a set of ipchains rules aimed to
807 
+prevent non-Tor traffic from accidentally leaving your computer. More
808 
+information at <a
809 
+href="https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine">https://trac.torproject.org/projects/tor/wiki/VirtualPrivacyMachine</a>.</li>
810 
+<li>Anonym.OS – это аналогичный вышеописанному диск LiveCD. Различие заключается
811 
+в том, что этот продукт основан на OpenBSD, а не на Linux для обеспечения
812 
+максимальной безопасности. При его разработке особое внимание уделялось
813 
+аспектам анонимности и безопасности, и, таким образом, он имеет некоторые
814 
+характеристики и ограничения, не встречающиеся в других дисках LiveCD
815 
+(относящихся к Tor и других). Вы можете получить больше информации о
816 
+продукте и скачать Anonym.OS с <a
817 
+href="http://theory.kaos.to/projects.html">Kaos.Theory</a>.</li>
818 
+<li>Phantomix – это диск LiveCD, предназначенный для обеспечения анонимного
819 
+серфинга и чата. Основан продукт на последнем выпуске KNOPPIX. Он
820 
+поставляется преднастроенным с privoxiTor и Polipo. Скачать диск можно на
821 
+веб сайте <a href="http://phantomix.ytternhagen.de/">Phantomix</a>.</li>
822 
+</ol>
823 
+
824 
+<p>
825 
+Пожалуйста, сообщите нам, если вам известны другие диски LiveCD.
826 
+</p>
827 
+
828 
+<hr />
829 
+
830 
+<a id="ChooseEntryExit"></a>
831 
+<h3><a class="anchor" href="#ChooseEntryExit">Могу ли я выбирать узлы (или
832 
+страны), используемые для ввода/вывода?</a></h3>
833 
+
834 
+<p>
835 
+Да. Вы можете выбрать предпочитаемые входные и выводные узлы, а также
836 
+проинформировать Tor о том, какие узлы вы использовать не хотите. Следующие
837 
+опции могут быть добавлены или прописаны в командной строке вашего
838 
+конфигурационного файла "torrc":
839 
+</p>
840 
+<dl>
841 
+  <dt><tt>EntryNodes $fingerprint,$fingerprint,...</tt></dt>
842 
+    <dd>Список предпочитаемых узлов, используемых на первом этапе в цикле (в
843 
+качестве вводных), если возможно.
844 
+    </dd>
845 
+  <dt><tt>ExitNodes $fingerprint,$fingerprint,...</tt></dt>
846 
+    <dd>Список предпочитаемых узлов, используемых на последнем этапе в цикле (в
847 
+качестве выводных), если возможно.
848 
+    </dd>
849 
+  <dt><tt>ExcludeNodes $fingerprint,$fingerprint,...</tt></dt>
850 
+    <dd>Список узлов, которые не должны быть использованы при построении цикла.
851 
+    </dd>
852 
+  <dt><tt>ExcludeExitNodes $fingerprint,$fingerprint,...</tt></dt>
853 
+    <dd>Список узлов, которые не должны быть использованы при выборе выводного
854 
+узла. Узлы, перечисленные в команде <tt>ExcludeNodes</tt> (см. пункт выше),
855 
+автоматически попадают в этот список.
856 
+    </dd>
857 
+</dl>
858 
+<p>
859 
+<em>Мы рекомендуем вам не использовать эти функции </em> – они были задуманы
860 
+для тестирования и могут исчезнуть в будущих версиях. Вы получаете лучший
861 
+уровень безопасности, когда оставляете выбор маршрутов сервису Tor; ручной
862 
+выбор выводных / вводных узлов может навредить вашей анонимности по
863 
+непонятной нам причине.
864 
+</p>
865 
+<p>
866 
+Опции конфигурации входных и выводных узлов (<tt>EntryNodes</tt> и
867 
+<tt>ExitNodes</tt>) воспринимаются как запросы. Это означает, что если узлы
868 
+недоступны или работают медленно, система Tor будет их избегать. Вы можете
869 
+сделать эту опцию обязательной, установив значение 1 в поле
870 
+<tt>StrictExitNodes</tt> или <tt>StrictEntryNodes</tt>. Но если вы сделаете
871 
+так, ваши соединения Tor прекратят работу, если все из перечисленных вами
872 
+узлов станут недоступными. Просмотрите <a
873 
+href="https://www.torproject.org/documentation.html.en#NeatLinks">страницу
874 
+статусов Tor</a> для выбора узлов.
875 
+</p>
876 
+<p>
877 
+Вместо этого вы можете в поле <tt>$fingerprint</tt> обозначить двухбуквенный
878 
+код страны ISO3166, заключенный в фигурные скобки (например, {de}), или
879 
+образец ip адресов (например, 255.254.0.0/8), или имя узла. Убедитесь, что
880 
+между запятыми и элементами списка нет пробелов.
881 
+</p>
882 
+<p>
883 
+Если вы хотите подключаться к сервису напрямую через SOCKS интерфейс Tor
884 
+(например, используя ssh через connect.c), другой возможностью является
885 
+установка внутреннего преобразования в вашем конфигурационном файле
886 
+<tt>MapAddress</tt>. Прочитайте страницу руководства для получения подробной
887 
+информации.
888 
+</p>
889 
+
890 
+<hr />
891 
+
892 
+<a id="RelayFlexible"></a>
893 
+<h3><a class="anchor" href="#RelayFlexible">Насколько стабильным должен быть мой
894 
+ретранслятор?</a></h3>
895 
+
896 
+<p>
897 
+Мы нацелены на то, чтобы сделать установку ретранслятора Tor простой и
898 
+удобной:
899 
+</p>
900 
+
901 
+<ul>
902 
+<li>Tor has built-in support for <a
903 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#LimitBandwidth">
904 
+rate limiting</a>. Further, if you have a fast link but want to limit the
905 
+number of bytes per day (or week or month) that you donate, check out the <a
906 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Hibernation">hibernation
907 
+feature</a>.
908 
+</li>
909 
+<li>Каждый ретранслятор Tor имеет <a href="#ExitPolicies">правила вывода</a>,
910 
+которые устанавливают разрешенные и запрещенные внешние соединения этого
911 
+узла. Если вы не хотите разрешать пользователям выход с вашего узла в сеть,
912 
+вы можете установить ограничение на такие соединения и разрешить только
913 
+подключение к другим ретрансляторам сети Tor.
914 
+</li>
915 
+<li>Вполне нормально, что ретранслятор иногда переходит в режим вне
916 
+сети. Директории быстро это определяют и не предлагают использовать этот
917 
+ретранслятор. Только убедитесь, что это происходит не слишком часто, так как
918 
+соединения, использующие ретранслятор при его отключении разрываются.
919 
+</li>
920 
+<li>Мы можем работать с ретрансляторами, имеющими динамические IP адреса — в
921 
+таких случаях при настройке нужно просто оставлять Address config пустым, и
922 
+Tor попытается определить адрес автоматически.
923 
+</li>
924 
+<li>If your relay is behind a NAT and it doesn't know its public IP (e.g. it has
925 
+an IP of 192.168.x.y), you'll need to set up port forwarding. Forwarding TCP
926 
+connections is system dependent but <a
927 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#ServerForFirewalledClients">this
928 
+FAQ entry</a> offers some examples on how to do this.
929 
+</li>
930 
+<li>Ваш ретранслятор будет пассивно оценивать, и передавать информацию о своем
931 
+текущем потенциале полосы пропускания, таким образом, высокоскоростные
932 
+ретрансляторы будут привлекать больше пользователей чем
933 
+низкоскоростные. Поэтому предоставление низкоскоростных ретрансляторов тоже
934 
+полезно.
935 
+</li>
936 
+</ul>
937 
+
938 
+<hr />
939 
+
940 
+<a id="RunARelayBut"></a> <a id="ExitPolicies"></a>
941 
+<h3><a class="anchor" href="#ExitPolicies">Я бы установил ретранслятор, но я не
942 
+хочу иметь дело с различного рода злоупотреблениями.</a></h3>
943 
+
944 
+<p>
945 
+Отлично. Это и является причиной внедрения правил вывода.
946 
+</p>
947 
+
948 
+<p>
949 
+Каждый ретранслятор Tor имеет правила вывода, которые устанавливают
950 
+разрешенные или запрещенные подключения вне сети для этого конкретного
951 
+ретранслятора. Правила вывода отдельных узлов представлены в директории Tor,
952 
+таким образом, клиент автоматически будет избегать подключения к тем узлам,
953 
+которые не разрешают подключение к интересующим его ресурсам. Так каждый
954 
+ретранслятор может решить, к каким сервисам, хостам и сетям разрешить
955 
+подключение, основываясь на их вредоносном потенциале и своих собственных
956 
+условиях. Прочитайте разделы часто задаваемых вопросов (FAQ), касающиеся <a
957 
+href="<page faq-abuse>#TypicalAbuses">условий использования стандартных
958 
+правил вывода</a>, а затем ознакомьтесь с советами Майка Перри (Mike Perry)
959 
+<a
960 
+href="https://blog.torproject.org/blog/tips-running-exit-node-minimal-harassment">о
961 
+том, как минимизировать угрозы предоставления выводного узла</a>.
962 
+</p>
963 
+
964 
+<p>
965 
+The default exit policy allows access to many popular services (e.g. web
966 
+browsing), but <a
967 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#DefaultPorts">restricts</a>
968 
+some due to abuse potential (e.g. mail) and some since the Tor network can't
969 
+handle the load (e.g. default file-sharing ports). You can change your exit
970 
+policy using Vidalia's "Sharing" tab, or by manually editing your <a
971 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#torrc">torrc</a>
972 
+file. If you want to avoid most if not all abuse potential, set it to
973 
+"reject *:*" (or un-check all the boxes in Vidalia). This setting means that
974 
+your relay will be used for relaying traffic inside the Tor network, but not
975 
+for connections to external websites or other services.
976 
+</p>
977 
+
978 
+<p>
979 
+Если вы разрешите внешние подключения, пожалуйста, убедитесь в том, что
980 
+разрешение имён работает корректно (то есть, ваш компьютер может корректно
981 
+определять IP адрес сервисов сети Интернет, используя их доменные
982 
+имена). Если есть ресурсы, доступ к которым с вашего компьютера заблокирован
983 
+(например, при использовании ограничительного брандмауэра или фильтра по
984 
+содержанию), пожалуйста, подробно укажите их в правилах вывода своего
985 
+ретранслятора — в противном случае ограничения будут распространяться и на
986 
+пользователей Tor.
987 
+</p>
988 
+
989 
+<hr />
990 
+
991 
+<a id="RelayOrBridge"></a>
992 
+<h3><a class="anchor" href="#RelayOrBridge">Что лучше установить обычный
993 
+ретранслятор или ретранслятор типа мост?</a></h3>
994 
+
995 
+<p><a href="<page bridges>">Ретрансляторы типа мост </a> (или, для краткости,
996 
+"мосты") являются <a href="<page docs/tor-doc-relay>"> ретрансляторами
997 
+Tor</a>, которые не указаны в главной директории сети Tor. Это означает, что
998 
+даже Интернет сервис провайдеры и правительства, пытающиеся фильтровать
999 
+соединения с сетью Tor, скорее всего, не смогут заблокировать все мосты.
1000 
+</p>
1001 
+
1002 
+<p>В остальном конфигурация обычного узла практически не отличается от
1003 
+конфигурации моста: разница состоит лишь в том, внесен ретранслятор в
1004 
+публичный список или нет.
1005 
+</p>
1006 
+
1007 
+<p>В настоящее время в мире практически не существует стран, которые бы
1008 
+фильтровали подключения к сети Tor. Таким образом, создание большого
1009 
+количества мостов скорее является мерой предосторожности. Например: а) на
1010 
+случай, если сеть Tor будет где-то заблокирована, и б) для людей, которым
1011 
+нужен дополнительный уровень безопасности; связанно это может быть с
1012 
+беспокойством о том, что кто-то сможет опознать подключение к IP адресу
1013 
+публичного ретранслятора Tor.
1014 
+</p>
1015 
+
1016 
+<p>Итак, стоит ли вам установить обычный ретранслятор или ретранслятор типа
1017 
+мост? Если вы имеете высокоскоростное подключение к сети Интернет, вам
1018 
+определенно стоит установить обычный ретранслятор — мостами, в настоящее
1019 
+время, пользуется только очень небольшое число пользователей. Если вы хотите
1020 
+<a href="#ExitPolicies">предоставлять услуги выводного узла</a>, вам
1021 
+совершенно точно лучше установить обычный ретранслятор, так как сейчас
1022 
+налицо их нехватка. Если вы не можете предоставлять услуги выводного узла и
1023 
+имеете ограниченное по скорости соединение, бросьте монетку. Большое спасибо
1024 
+за ваш вклад!
1025 
+</p>
1026 
+
1027 
+<hr />
1028 
+
1029 
+<a id="RelayMemory"></a>
1030 
+<h3><a class="anchor" href="#RelayMemory">Почему мой ретранслятор использует так
1031 
+много памяти?</a></h3>
1032 
+
1033 
+<p>Если ваш сервер использует больше памяти, чем вам хотелось бы, вот несколько
1034 
+советов для сокращения своего присутствия:
1035 
+</p>
1036 
+
1037 
+<ol>
1038 
+<li>Если вы на Linux, у вас могут возникнуть ошибки фрагментации памяти в
1039 
+осуществлении MALLOC Glibc. То есть, когда Тор освобождает память обратно в
1040 
+систему, куски памяти становится фрагментированной, поэтому они трудно
1041 
+повторно. поэтому они трудно повторно. Тор архива суда с осуществлением
1042 
+MALLOC OpenBSD, который не имеет как много ошибок фрагментации (но выбор
1043 
+стоит выше загрузка процессора). Вы можете установить Tor, чтобы
1044 
+использовать эту MALLOC осуществление вместо: <tt>./configure
1045 
+--enable-openbsd-malloc</tt></li>
1046 
+
1047 
+<li>If you're running a fast relay, meaning you have many TLS connections open,
1048 
+you are probably losing a lot of memory to OpenSSL's internal buffers (38KB+
1049 
+per socket). We've patched OpenSSL to <a
1050 
+href="http://archives.seul.org/or/dev/Jun-2008/msg00001.html">release unused
1051 
+buffer memory more aggressively</a>. If you update to OpenSSL 1.0.0-beta5,
1052 
+Tor's build process will automatically recognize and use this feature.</li>
1053 
+
1054 
+<li>If you're running on Solaris, OpenBSD, NetBSD, or old FreeBSD, Tor is
1055 
+probably forking separate processes rather than using threads. Consider
1056 
+switching to a <a
1057 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayOS">better
1058 
+operating system</a>.</li>
1059 
+
1060 
+<li>Если вы все еще не может справиться с нагрузкой памяти, можно также
1061 
+уменьшить возможности вашего сервера объявляет. Объявляя меньшей пропускной
1062 
+способности означает, что вас привлекает меньше пользователей, так что ваш
1063 
+сервер не должна расти как крупные. См. <tt>MaxAdvertisedBandwidth</tt>
1064 
+опцию в странице руководства (man page).</li>
1065 
+
1066 
+</ol>
1067 
+
1068 
+<p>
1069 
+Все-таки, быстрые серверы Tor используют много памяти. Это не является
1070 
+необычным для быстрого выводного ретранслятора использовать 500-1000 Мбайт
1071 
+памяти.
1072 
+</p>
1073 
+
1074 
+<hr />
1075 
+
1076 
+<a id="WhyNotNamed"></a>
1077 
+<h3><a class="anchor" href="#WhyNotNamed">Почему моему ретранслятору не
1078 
+присваивается имя?</a></h3>
1079 
+
1080 
+<p>
1081 
+We currently use these metrics to determine if your relay should be named:<br />
1082 
+</p>
1083 
+<ul>
1084 
+<li>Не было ли предложенное имя зарегистрировано в сети Tor ранее. Существующие
1085 
+записи удаляются через 6 месяцев неактивности узлов.</li>
1086 
+<li>Ретранслятор должен работать минимум на протяжении двух недель.</li>
1087 
+<li>Никакой другой роутер не запрашивал регистрацию этого имени за прошедший
1088 
+месяц.</li>
1089 
+</ul>
1090 
+
1091 
+<hr />
1092 
+
1093 
+<a id="KeyManagement"></a>
1094 
+<h3><a class="anchor" href="#KeyManagement">Хочу информацию обо всех ключах,
1095 
+используемых Tor.</a></h3>
1096 
+
1097 
+<p>
1098 
+В сервисе Tor используется множество различных ключей. Цели их
1099 
+использования: 1) шифрование для обеспечения конфиденциальности данных
1100 
+внутри сети Tor, 2) идентификация, чтобы клиенты знали, что обращаются
1101 
+именно к тем ретрансляторам, к которым обратиться хотели, и 3) подписи,
1102 
+чтобы убедиться, что все клиенты имеют информацию обо всех доступных
1103 
+ретрансляторах.
1104 
+</p>
1105 
+
1106 
+<p>
1107 
+<b>Шифрование</b>: во-первых, все подключения в сети Tor используют TLS
1108 
+шифрование, так что наблюдатели не могут просматривать направления
1109 
+информационного обмена. Более того, клиентская программа Tor создает
1110 
+эфемерные ключи кодирования со всеми ретрансляторами, таким образом, только
1111 
+последний узел может считать передаваемую информацию. Обе стороны аннулируют
1112 
+временный ключ в конце операции, поэтому сохранение трафика и последующий
1113 
+взлом ретранслятора с целью выяснения ключа - пустая трата времени.
1114 
+</p>
1115 
+
1116 
+<p>
1117 
+<b>Authentication</b>: Every Tor relay has a public decryption key called
1118 
+the "onion key".  When the Tor client establishes circuits, at each step it
1119 
+<a href="<svnprojects>design-paper/tor-design.html#subsec:circuits">demands
1120 
+that the Tor relay prove knowledge of its onion key</a>. That way the first
1121 
+node in the path can't just spoof the rest of the path.  Each relay rotates
1122 
+its onion key once a week.
1123 
+</p>
1124 
+
1125 
+<p>
1126 
+<b>Координация</b>: как клиенты идентифицируют ретрансляторы и подбирают для
1127 
+них правильные ключи? Каждый ретранслятор имеет долговременный публичный
1128 
+ключ подписи, называемый "ключ идентификации". Каждое управление директорией
1129 
+дополнительно имеет "ключ подписи директории". Управление директорией <a
1130 
+href="<svnsandbox>doc/spec/dir-spec.txt"> содержит подтвержденный список</a>
1131 
+всех известных ретрансляторов, и в этом списке есть набор их сертификатов
1132 
+(подписанных идентификационными ключами ретрансляторов). Этот набор содержит
1133 
+спецификации ключей, местоположений, правил вывода и т.д. обо всех
1134 
+ретрансляторах сети. Таким образом, если недоброжелатель не может
1135 
+контролировать управление директорией, он не может заставить клиента
1136 
+использовать другие ретрансляторы Tor.
1137 
+</p>
1138 
+
1139 
+<p>
1140 
+Как клиенты распознают управление директорией? Программное обеспечение Tor
1141 
+поставляется с встроенным списком локаций и публичных ключей для каждого
1142 
+управления директорией. Таким образом, единственной возможностью заставить
1143 
+пользователей использовать фальшивую сеть Tor - это предоставлять им
1144 
+модифицированные версии программного обеспечения.
1145 
+</p>
1146 
+
1147 
+<p>
1148 
+Как пользователи могут узнать, верную ли версию программного обеспечения они
1149 
+используют? Когда мы распространяем код источника или пакета программ, мы
1150 
+оснащаем их цифровыми подписями с <a href="http://www.gnupg.org/">GNU
1151 
+Privacy Guard</a>. Ознакомьтесь с <a href="<page
1152 
+verifying-signatures>">инструкциями определения Tor подписей</a>.
1153 
+</p>
1154 
+
1155 
+<p>
1156 
+Чтобы точно убедиться, что подпись действительно наша, вам необходимо
1157 
+встретиться с нами и получить копию нашего GPG ключа, или вам необходимо
1158 
+знать человека, у которого такой ключ уже есть. Если вы обеспокоены атакой
1159 
+на этом уровне, мы рекомендуем вам стать частью сообщества по обеспечению
1160 
+безопасности и начать встречаться с людьми.
1161 
+</p>
1162 
+
1163 
+<hr />
1164 
+
1165 
+<a id="EverybodyARelay"></a>
1166 
+<h3><a class="anchor" href="#EverybodyARelay">Нужно сделать каждого пользователя
1167 
+Tor ретранслятором.</a></h3>
1168 
+
1169 
+<p>
1170 
+Requiring every Tor user to be a relay would help with scaling the network
1171 
+to handle all our users, and <a
1172 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#RelayAnonymity">running
1173 
+a Tor relay may help your anonymity</a>. However, many Tor users cannot be
1174 
+good relays &mdash; for example, some Tor clients operate from behind
1175 
+restrictive firewalls, connect via modem, or otherwise aren't in a position
1176 
+where they can relay traffic. Providing service to these clients is a
1177 
+critical part of providing effective anonymity for everyone, since many Tor
1178 
+users are subject to these or similar constraints and including these
1179 
+clients increases the size of the anonymity set.
1180 
+</p>
1181 
+
1182 
+<p>
1183 
+Не смотря на это, мы все же хотим мотивировать пользователей Tor на
1184 
+предоставление услуг ретрансляторов, поэтому нашей настоящей задачей
1185 
+является упрощение процесса установки и поддержания работы ретранслятора. За
1186 
+последние несколько лет мы многое сделали в направлении упрощения
1187 
+конфигурирования: программа Vidalia имеет простой интерфейс настройки
1188 
+ретранслятора, а также поддерживает uPnP. Программа Tor хороша в
1189 
+автоматическом определении доступности ретрансляторов и предлагаемой ими
1190 
+пропускной способности.
1191 
+</p>
1192 
+
1193 
+<p>
1194 
+Однако на этом пути у нас еще есть пять важных шагов:
1195 
+</p>
1196 
+
1197 
+<p>
1198 
+Во-первых, мы должны сделать Tor стабильным при работе в качестве
1199 
+ретранслятора на всех распространенных операционных системах. Главной
1200 
+платформой по прежнему остается Windows, мы планируем завершить этот этап в
1201 
+2009 году. Смотри Секцию 4.1 <a
1202 
+href="https://www.torproject.org/press/2008-12-19-roadmap-press-release">нашего
1203 
+плана развития</a>.
1204 
+</p>
1205 
+
1206 
+<p>
1207 
+Second, we still need to get better at automatically estimating the right
1208 
+amount of bandwidth to allow. See item #7 on the <a href="<page
1209 
+volunteer>#Research">research section of the volunteer page</a>: "Tor
1210 
+doesn't work very well when relays have asymmetric bandwidth (e.g. cable or
1211 
+DSL)". It might be that <a
1212 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#TransportIPnotTCP">switching
1213 
+to UDP transport</a> is the simplest answer here &mdash; which alas is not a
1214 
+very simple answer at all.
1215 
+</p>
1216 
+
1217 
+<p>
1218 
+Third, we need to work on scalability, both of the network (how to stop
1219 
+requiring that all Tor relays be able to connect to all Tor relays) and of
1220 
+the directory (how to stop requiring that all Tor users know about all Tor
1221 
+relays). Changes like this can have large impact on potential and actual
1222 
+anonymity. See Section 5 of the <a
1223 
+href="<svnprojects>design-paper/challenges.pdf">Challenges</a> paper for
1224 
+details. Again, UDP transport would help here.
1225 
+</p>
1226 
+
1227 
+<p>
1228 
+В-четвертых, нам необходимо лучше понимать риск от действия
1229 
+недоброжелателей, которые могут отправлять трафик через ваш ретранслятор, в
1230 
+то время как вы инициализируете свой собственный анонимизированный
1231 
+трафик. <a href="http://freehaven.net/anonbib/#back01">Три</a>  <a
1232 
+href="http://freehaven.net/anonbib/#clog-the-queue">различные</a>  <a
1233 
+href="http://freehaven.net/anonbib/#torta05">исследовательские</a> работы
1234 
+описывают пути идентификации ретрансляторов в цепочке путем пропускания
1235 
+трафика через интересующие ретрансляторы и в отслеживании падений в передаче
1236 
+данных во время активности цепочки. Эти загрязняющие атаки не так страшны в
1237 
+контексте сервиса Tor, до тех пор, пока ретрансляторы не являются
1238 
+клиентами. Но учитывая, что мы пытаемся мотивировать большее количество
1239 
+клиентов на включение функции ретранслятора (неважно в качестве <a
1240 
+href="<page bridges>">моста</a> или обычного ретранслятора), мы должны лучше
1241 
+понимать эту угрозу и придумать способ борьбы с ней.
1242 
+</p>
1243 
+
1244 
+<p>
1245 
+В-пятых, нам необходимо разработать схему мотивации, чтобы привлекать людей
1246 
+к ретрансляции трафика для других, и/или к предоставлению услуг выводного
1247 
+узла. Здесь найдете наши <a
1248 
+href="https://blog.torproject.org/blog/two-incentive-designs-tor">настоящие
1249 
+идеи по схеме мотивации Tor</a>.
1250 
+</p>
1251 
+
1252 
+<p>
1253 
+Пожалуйста, помогите нам в решении этих задач!
1254 
+</p>
1255 
+
1256 
+<hr />
1257 
+
1258 
+<a id="Criminals"></a>
1259 
+<h3><a class="anchor" href="#Criminals">Не дает ли Tor возможность преступникам
1260 
+осуществлять их коварные планы?</a></h3>
1261 
+
1262 
+<p>
1263 
+Для получения ответа на этот и другие вопросы, пожалуйста, ознакомьтесь со
1264 
+<a href="<page faq-abuse>"> списком часто задаваемых вопросов (FAQ) по
1265 
+Злоупотреблению сетью Tor </a>.
1266 
+</p>
1267 
+
1268 
+<hr />
1269 
+
1270 
+<a id="RespondISP"></a>
1271 
+<h3><a class="anchor" href="#RespondISP">Как мне отреагировать на запросы
1272 
+Интернет провайдера по поводу моего выводного ретранслятора?</a></h3>
1273 
+
1274 
+<p>
1275 
+A collection of templates for successfully responding to ISPs is <a
1276 
+href="https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorAbuseTemplates">collected
1277 
+here</a>.
1278 
+</p>
1279 
+
1280 
+<hr />
1281 
+
1282 
+  </div>
1283 
+
1284 
+
1285 
+
1286 
+#include <foot.wmi>
ru/mirrors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,48 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Mirrors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor: Зеркала</h2>
14 
+<hr />
15 
+
16 
+<p>
17 
+Основной URL этого сайта - <a
18 
+href="https://www.torproject.org/">https://www.torproject.org</a>, и есть
19 
+ещё несколько зеркал.
20 
+</p>
21 
+
22 
+<p>
23 
+Если вы хотите запустить зеркало этого сайта, пожалуйста <a href="<page
24 
+docs/running-a-mirror>">прочитайте наши инструкции по зеркалированию</a>.
25 
+</p>
26 
+
27 
+<table class="mirrors">
28 
+<tr>
29 
+  <th>Страна</th>
30 
+  <th>Организация</th>
31 
+  <th>Состояние</th>
32 
+  <th>ftp</th>
33 
+  <th>http dist/</th>
34 
+  <th>http сайт</th>
35 
+  <th>https dist/</th>
36 
+  <th>https сайт</th>
37 
+  <th>rsync dist/</th>
38 
+  <th>rsync сайт</th>
39 
+</tr>
40 
+
41 
+<!--PO4ASHARPBEGINinclude <mirrors-table.wmi>
42 
+PO4ASHARPEND-->
43 
+</table>
44 
+
45 
+  </div>
46 
+
47 
+
48 
+#include <foot.wmi>
ru/overview.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,252 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22308 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor: Overview" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<a name="overview"></a>
14 
+<h2><a class="anchor" href="#overview">Tor: Обзор</a></h2>
15 
+
16 
+<!-- BEGIN SIDEBAR -->
17 
+<div class="sidebar-left">
18 
+<h3>Разделы</h3>
19 
+<ul>
20 
+<li><a href="<page overview>#overview">Обзор</a></li>
21 
+<li><a href="<page overview>#whyweneedtor">Зачем нам нужен Tor</a></li>
22 
+<li><a href="<page overview>#thesolution">Решение</a></li>
23 
+<li><a href="<page overview>#hiddenservices">Скрытые сервисы</a></li>
24 
+<li><a href="<page overview>#stayinganonymous">Оставаясь анонимным</a></li>
25 
+<li><a href="<page overview>#thefutureoftor">Будущее Tor</a></li>
26 
+</ul>
27 
+</div>
28 
+
29 
+
30 
+<!-- END SIDEBAR -->
31 
+<hr />
32 
+
33 
+<p>
34 
+Tor это сеть виртуальных туннелей, которые позволяют отдельным пользователям
35 
+и группам людей повысить свою конфиденциальность и безопасность в сети
36 
+Интернет. Для программистов Tor предоставляет возможность разрабатывать
37 
+новые инструменты коммуникации со встроенной защитой конфиденциальности. Tor
38 
+обеспечивает основу для определенного спектра приложений, которая позволяет
39 
+организациями и индивидуальным пользователям делиться информацией через
40 
+публичные сети, не подвергая опасности свою конфиденциальность.
41 
+</p>
42 
+
43 
+<p>
44 
+Individuals use Tor to keep websites from tracking them and their family
45 
+members, or to connect to news sites, instant messaging services, or the
46 
+like when these are blocked by their local Internet providers.  Tor's <a
47 
+href="<page hidden-services>">hidden services</a> let users publish web
48 
+sites and other services without needing to reveal the location of the
49 
+site. Individuals also use Tor for socially sensitive communication: chat
50 
+rooms and web forums for rape and abuse survivors, or people with illnesses.
51 
+</p>
52 
+
53 
+<p>
54 
+Журналисты используют Tor, чтобы свободно и безопасно общаться с
55 
+диссидентами и обличителями режимов. Негосударственные организации
56 
+используют Tor для обеспечения доступа своих служащих к домашним сайтам в то
57 
+время как они находятся за рубежом, не оглашая публично, что они работают на
58 
+данную организацию.
59 
+</p>
60 
+
61 
+<p>
62 
+Такие группы как Indymedia рекомендуют Tor своим пользователям для защиты
63 
+конфиденциальности и безопасности в сети Интернет. Группы активистов
64 
+(например, Electronic Frontier Foundation (EFF)) рекомендуют Tor как
65 
+механизм обеспечения гражданских свобод в сети Интернет. Корпорации
66 
+используют Tor для проведения безопасного конкурентного анализа и для защиты
67 
+важных путей поставок от наблюдателей. Ещё одно использование Tor - замена
68 
+обычного VPN, который не скрывает от злоумышленника точное количество и
69 
+временные промежутки сеанса связи. Где живут сотрудники которые поздно
70 
+работают? Кто те сотрудники, что посещают сайты работ? Кто из исследователей
71 
+общается с юристами по патентам компании?
72 
+</p>
73 
+
74 
+<p>
75 
+Часть Военно-Морских Сил США использует Tor для сбора разведданных, а одно
76 
+подразделение использовало Tor во время недавнего пребывания на Ближнем
77 
+Востоке. Правоохранительные органы используют Tor для посещения веб сайтов,
78 
+не оставляя при этом зарегистрированный на гос. структуру IP-адресов в его
79 
+логах, и для безопасности во время операций.
80 
+</p>
81 
+
82 
+<p>
83 
+Разнообразие людей использующих Tor вносит большой вклад <a
84 
+href="http://freehaven.net/doc/fc03/econymics.pdf">в его безопасность</a>.
85 
+Tor прячет вас среди <a href="<page torusers>">других пользователей
86 
+сети</a>, и, таким образом, ваша анонимность будет защищена тем сильнее, чем
87 
+больше разных людей используют Tor.
88 
+</p>
89 
+
90 
+<a name="whyweneedtor"></a>
91 
+<h3><a class="anchor" href="#whyweneedtor">Зачем нам нужен Tor</a></h3>
92 
+
93 
+<p>
94 
+Использование Tor защищает вас от частой формы наблюдения в сети Интернет
95 
+известной как "анализ потока данных". Анализ потока данных позволяет узнать
96 
+кто с кем общается по публичным сетям. Знание источника и приёмника вашего
97 
+Интернет-трафика позволяет третьим сторонам отслеживать ваше поведение и
98 
+интересы в сети. Это может повлиять на ваш бумажник, например если в
99 
+электронном магазине реализована дискриминация по ценам для разных стран или
100 
+организаций. Это может даже угрожать вашей работе и физической безопасности,
101 
+так как раскрывает сведения о том, кто вы такой и где находитесь. Например,
102 
+вы путешествуете заграницей и соединяетесь со своим рабочим сервером чтобы
103 
+проверить или послать почту, и при этом вы открываете свою страну и
104 
+профессиональные данные любому наблюдателю сети, даже если соединение
105 
+зашифровано.
106 
+</p>
107 
+
108 
+<p>
109 
+Как работает анализ потока данных? Пакеты данных в интернете состоят из двух
110 
+частей: полезная нагрузка - данные, и заголовок, используемый для
111 
+маршрутизации.  Данные - это то что посылается (email, веб-страница,
112 
+аудио-файл, и т.п.). Даже если вы шифруете пересылаемые данные, анализ
113 
+трафика позволит узнать очень многое про то, что именно вы делаете и,
114 
+возможно, что вы говорите. Наблюдение фокусируется на заголовке и позволяет
115 
+узнать источник, приёмник, размер, временные характеристики, и т.д.
116 
+</p>
117 
+
118 
+<p>
119 
+Основная проблема состоит в том, что сторонний получатель ваших коммуникаций
120 
+может просматривать заголовки пакетов. Это могут делать авторизированные
121 
+посредники, как, например, Интернет сервис провайдер, а иногда и
122 
+неавторизированные. Очень простую форму анализа потока данных можно
123 
+реализовать просматривая заголовки всех пакетов между получателем и
124 
+отправителем.
125 
+</p>
126 
+
127 
+<p>
128 
+Но есть ещё более мощные техники такого надзора. Многие заинтересованные
129 
+стороны наблюдают за несколькими сегментами Интернета и используют
130 
+продвинутые статистические методы, чтобы проследить характерные сеансы связи
131 
+разных организаций и индивидов. Шифрование в таких случаях бессмысленно,
132 
+т. к. оно прячет только содержание коммуникаций, а не заголовки.
133 
+</p>
134 
+
135 
+<a name="thesolution"></a>
136 
+<h3><a class="anchor" href="#thesolution">Решение: распределённая, анонимная
137 
+сеть</a></h3>
138 
+
139 
+<p>
140 
+Сервис Tor помогает уменьшить риск, как простого, так и продвинутого анализа
141 
+трафика, проводя ваши операции связи через несколько мест в Интернете, так
142 
+что ни одна из точек не может "связать" вас с запрашиваемым вами
143 
+сервером. Идея заключается в использовании запутанного,
144 
+сложно-прослеживаемого пути, чтобы сбить с толку преследователя, а затем -
145 
+периодическое уничтожение следов.  Вместо того, чтобы идти по прямому пути
146 
+от отправителя к получателю, пакеты данных в сети Tor выбирают случайные
147 
+маршруты через несколько серверов, которые скрывают ваши следы так, что ни
148 
+один наблюдатель в любой точке не может сказать откуда или куда направляются
149 
+данные.
150 
+</p>
151 
+
152 
+<p><img alt="Tor circuit step one" src="$(IMGROOT)/htw1.png" /></p>
153 
+
154 
+<p>
155 
+Чтобы установить приватный путь с помощью Tor, программа пользователя, или
156 
+клиент, последовательно строит цепочки зашифрованных соединений с серверами
157 
+сети. Цепочка вырастает с каждым разом на один сервер, и каждый участвующий
158 
+сервер знает только то, от какого сервера он получил данные и какому серверу
159 
+эти данные он передаёт. Ни один из серверов не знает полный путь, по
160 
+которому будут идти пакеты данных. Клиент определяет для каждого шага
161 
+отдельный набор ключей шифрования, так чтобы нельзя было проследить
162 
+соединение во время передачи данных.
163 
+</p>
164 
+
165 
+<p><img alt="Tor circuit step two" src="$(IMGROOT)/htw2.png" /></p>
166 
+
167 
+<p>
168 
+Как только цепочка выбрана, можно передавать различные данные и разные
169 
+приложения могут использовать сеть Tor. Так как каждый сервер в цепочке
170 
+видит не больше одного шага, то ни сторонний наблюдатель, ни "плохой" сервер
171 
+не могут связать получателя и отправителя. Сеть Tor работает только с TCP
172 
+потоками и может быть использована любым приложением, поддерживающим SOCKS.
173 
+</p>
174 
+
175 
+<p>
176 
+Для повышения скорости Tor использует одну и ту же цепочку для соединений в
177 
+течение десяти минут, или около того. После этого рассчитывается новая
178 
+цепочка, чтобы не связывать ваши предыдущие действия с последующими.
179 
+</p>
180 
+
181 
+<p><img alt="Tor circuit step three" src="$(IMGROOT)/htw3.png" /></p>
182 
+
183 
+
184 
+<a name="hiddenservices"></a>
185 
+<h3><a class="anchor" href="#hiddenservices">Скрытые сервисы</a></h3>
186 
+
187 
+<p>
188 
+Пользователи Tor могут предоставлять различные сервисы, такие как веб-доступ
189 
+или сервер системы обмена мгновенными сообщениями, не раскрывая своё
190 
+истинное местоположение. Используя "rendezvous" точки Tor пользователи могут
191 
+соединяться с этими скрытыми сервисами, причём ни одна из сторон не может
192 
+узнать, кто находится на другом конце связи. Этот функционал можно
193 
+использовать для размещения сайта не беспокоясь о цензуре. Никто не будет в
194 
+состоянии определить владельца сайта, и владелец сайта не будет в состоянии
195 
+узнать, кто использовал сайт.  Узнайте больше о том как <a href="<page
196 
+docs/tor-hidden-service>">самостоятельно создать скрытый сервис</a> и как <a
197 
+href="<page hidden-services>">работает протокол скрытых сервисов</a>.
198 
+</p>
199 
+
200 
+<a name="stayinganonymous"></a>
201 
+<h3><a class="anchor" href="#stayinganonymous">Оставаясь анонимным</a></h3>
202 
+
203 
+<p>
204 
+Сервис Tor сам по себе не может решить все проблемы анонимности. Он
205 
+фокусируется только на защите передачи данных. Вы должны дополнительно
206 
+использовать специфичные для протокола программные продукты, чтобы скрыть
207 
+частную или идентифицирующую вас информацию. Например, вы может использовать
208 
+веб прокси (такие как Privoxy) при серфинге, чтобы блокировать cookie и
209 
+скрыть информацию идентифицирующую ваш браузер.
210 
+</p>
211 
+
212 
+<p>
213 
+Также, чтобы сохранить анонимность, будьте умны. Не оставляйте своё
214 
+настоящее имя или другую информацию в веб формах. Помните , что как и любая
215 
+анонимизирующая сеть, которая достаточно быстро работает, Tor не защищает от
216 
+сквозных тайминг-атак: если атакующий видит трафик исходящий из вашего
217 
+компьютера, и видит какой-то трафик входящий на выбранный ресурс, он может
218 
+использовать статистический анализ чтобы определить что эти два трафика
219 
+связаны.
220 
+</p>
221 
+
222 
+<a name="thefutureoftor"></a>
223 
+<h3><a class="anchor" href="#thefutureoftor">Будущее сети Tor</a></h3>
224 
+
225 
+<p>
226 
+Текущая цель проекта - предоставить удобную для использования
227 
+анонимизирующую сети в Интернет. Мы хотим иметь программное обеспечение,
228 
+которое оправдает надежды пользователей. Мы хотим, чтобы сеть работала при
229 
+любом количестве пользователей. Безопасность и простота использования не
230 
+должны противоречить друг другу: чем более удобным становится Tor, тем
231 
+больше пользователей он имеет, тем больше возможных входов-выходов для
232 
+каждого соединения, тем больше безопасность для каждого. Прогресс идёт, но
233 
+нам нужна ваша помощь.  Пожалуйста задумайтесь над возможностью <a
234 
+href="<page docs/tor-doc-relay>">предоставить ретранслятор</a> или <a
235 
+href="<page volunteer>">стать добровольцем</a>- <a href="<page
236 
+documentation>#Developers">разработчиком</a>.
237 
+</p>
238 
+
239 
+<p>
240 
+Последние веяния в законах и технологиях угрожают анонимности как никогда
241 
+раньше, убивая на корню возможность свободно читать и писать в сети. Это
242 
+также угрожает национальной безопасности и инфраструктуре, так как связь
243 
+между индивидами, организациями, корпорациями, и государствами становится
244 
+более подверженной анализу. Каждый новый пользователь и сервер добавляют
245 
+разнообразия, укрепляя способность сети Tor, вернуть контроль над
246 
+конфиденциальностью и безопасностью в ваши руки.
247 
+</p>
248 
+
249 
+  </div>
250 
+
251 
+
252 
+#include <foot.wmi>
ru/torusers.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,449 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22261 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Who uses Tor?" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Начало</h2>
14 
+
15 
+
16 
+<!-- BEGIN SIDEBAR -->
17 
+<div class="sidebar-left">
18 
+<h3>Кто использует сервис Tor?</h3>
19 
+<ul>
20 
+<li><a href="<page torusers>#normalusers">Обычные люди используют Tor</a></li>
21 
+<li><a href="<page torusers>#military">Военные используют Tor</a></li>
22 
+<li><a href="<page torusers>#journalist">Журналисты и их публика используют
23 
+Tor</a></li>
24 
+<li><a href="<page torusers>#lawenforcement">Сотрудники правоохранительных
25 
+органов используют Tor</a></li>
26 
+<li><a href="<page torusers>#activists">Активисты и правдолюбы используют
27 
+Tor</a></li>
28 
+<li><a href="<page torusers>#spotlight">Люди занимающие высокое и низкое
29 
+положение в обществе используют Tor</a></li>
30 
+<li><a href="<page torusers>#executives">Управляющие из сферы бизнеса используют
31 
+Tor</a></li>
32 
+<li><a href="<page torusers>#bloggers">Блоггеры используют Tor</a></li>
33 
+<li><a href="<page torusers>#itprofessionals">Профессионалы из сферы
34 
+Информационных Технологий используют Tor</a></li>
35 
+</ul>
36 
+</div>
37 
+
38 
+
39 
+<!-- END SIDEBAR -->
40 
+<hr />
41 
+<p>
42 
+Сеть Tor изначально разрабатывалась и внедрялась в рамках <a
43 
+href="http://www.onion-router.net/"> проекта по созданию лукового
44 
+маршрутизатора Военно-Морской Исследовательской Лаборатории (Naval Research
45 
+Laboratory)</a> третьего поколения.  Изначально сеть была разработана с
46 
+расчетом на Военно-Морской Флот США, главной целью при этом была защита
47 
+правительственных коммуникаций. Сегодня, сеть ежедневно используется по
48 
+широкому спектру причин военными, журналистами, сотрудниками
49 
+правоохранительных органов, активистами и множеством других людей. Здесь
50 
+перечислены несколько специфичных видов использования, о которых мы знаем, и
51 
+которые мы рекомендуем.
52 
+</p>
53 
+
54 
+<a name="normalusers"></a>
55 
+<h2><a class="anchor" href="#normalusers">Обычные люди используют Tor</a></h2>
56 
+<hr />
57 
+<ul>
58 
+<li><strong>Они защищают свою конфиденциальную информацию от беспринципных
59 
+торговцев и "воров личности".</strong> Интернет сервис провайдеры (ISP) <a
60 
+href="http://seekingalpha.com/article/29449-compete-ceo-isps-sell-clickstreams-for-5-a-month">
61 
+продают записи ваших просмотров Интернет страниц</a> продавцам и другим
62 
+людям, желающим заплатить за эту информацию. Провайдеры обычно говорят, что
63 
+они анонимизируют данные, не предоставляя информацию, идентифицирующую
64 
+конкретных людей, <a
65 
+href="http://www.wired.com/politics/security/news/2006/08/71579?currentPage=all">но,
66 
+как оказалось, это не правда</a>. Полная запись всех посещаемых вами сайтов,
67 
+текст каждого поискового запроса, а возможно также и идентификационная
68 
+информация о пользователе и даже пароли могут быть частью этих
69 
+данных. Помимо вашего Интернет сервис провайдера, веб сайты (<a
70 
+href="http://www.google.com/privacy_faq.html">и поисковые машины</a>),
71 
+которые вы посещаете, имеют свои собственные логи, содержащие ту же, а,
72 
+возможно, и более полную информацию.
73 
+</li>
74 
+<li><strong> Они защищают свои коммуникации от безответственных
75 
+корпораций.</strong> По всему Интернету, Tor рекомендуют людям, с недавних
76 
+пор заинтересовавшимся вопросами собственной конфиденциальности в виду
77 
+увеличения количества брешей в системах безопасности и случаев
78 
+злоупотреблений частной информацией. Начиная <a
79 
+href="http://www.securityfocus.com/news/11048">утерянными резервными копиями
80 
+данных</a>, и заканчивая <a
81 
+href="http://www.nytimes.com/2006/08/09/technology/09aol.html?ex=1312776000&amp;en=f6f61949c6da4d38&amp;ei=5090">передачей
82 
+данных исследователям</a>, ваша информация очень часто не достаточно хорошо
83 
+защищена теми, кому вы её доверяете.
84 
+</li>
85 
+<li><strong>Они защищают своих детей в сети Интернет.</strong> Вы сказали своим
86 
+детям, что им не стоит раскрывать идентифицирующую их информацию в сети, но,
87 
+возможно, они раскрывают свое местоположение, просто не маскируя свои
88 
+IP-адреса. IP-адреса все чаще могут быть использованы<a
89 
+href="http://whatismyipaddress.com/">буквально для определения улицы, с
90 
+которой осуществлен доступ в Интернет</a>. Они также <a
91 
+href="http://whatsmyip.org/more/">раскрывают информацию</a> о том, как вы
92 
+подключаетесь к сети Интернет. В США правительство продвигает эту
93 
+технологию, чтобы карты IP-адресов стали еще более точными.
94 
+</li>
95 
+<li><strong>Они исследуют щекотливые темы.</strong> Сеть Интернет - это кладезь
96 
+информации. Но, возможно, в вашей стране доступ к информации о СПИДе,
97 
+контроле за рождаемостью, <a
98 
+href="http://www.cbsnews.com/stories/2002/12/03/tech/main531567.shtml">Тибетской
99 
+культуре</a>, или мировых религиях блокируется национальным брандмауэром.
100 
+</li>
101 
+</ul>
102 
+
103 
+<a name="military"></a>
104 
+<h2><a class="anchor" href="#military">Военные используют Tor</a></h2>
105 
+<hr />
106 
+<ul>
107 
+
108 
+<li>
109 
+<strong>Полевые агенты:</strong> Инсургентам не сложно мониторить Интернет
110 
+трафик и определять все отели и другие локации, с которых люди подключаются
111 
+к известным военным серверам. Военные полевые агенты, дислоцированные в
112 
+другие страны, используют Tor, чтобы маскировать информацию о том, какие
113 
+сайты они посещают, защищая таким образом интересы и операции армии, а также
114 
+защищая себя от возможной физической расправы.
115 
+</li>
116 
+
117 
+<li><strong>Скрытые сервисы:</strong> Когда сеть Интернет разрабатывалась DARPA,
118 
+главной целью организации было упрощение распределенной, надежной
119 
+коммуникации на случай локальных забастовок. Однако некоторые функции должны
120 
+были быть централизованными, такие как управление и контроль за сайтами. По
121 
+своей природе протоколы сети Интернет раскрывают географическое положение
122 
+любого сервера, который доступен через сеть. Скрытые сервисы Tor позволяют
123 
+обеспечить физическую защиту от раскрытия местоположения и уничтожения
124 
+военного командования и контроля.
125 
+</li>
126 
+<li><strong>Сбор разведывательных данных:</strong> Военный персонал нуждается в
127 
+использовании электронных ресурсов, управляемых и просматриваемых
128 
+инсургентами. Военные не хотят, чтобы в логах веб сервера инсургентов
129 
+появились записи военных адресов, раскрывающие факт прослушивания.
130 
+</li>
131 
+</ul>
132 
+
133 
+<a name="journalist"></a>
134 
+<h2><a class="anchor" href="#journalist">Журналисты и их публика используют
135 
+Tor</a></h2>
136 
+<hr />
137 
+<ul>
138 
+<li><strong><a href="http://www.rsf.org/">Организация Репортеры без
139 
+Границ</a></strong> отслеживает случаи политических заключенных или
140 
+наказания журналистов по всему миру. Они советуют журналистам, источникам,
141 
+блоггерам и диссидентам использовать Tor для обеспечения их
142 
+конфиденциальности и безопасности.
143 
+</li>
144 
+<li><strong><a href="http://www.ibb.gov/">Международное Радиовещательное
145 
+Бюро</a> Соединенных Штатов Америки</strong> (Голос Америки/Радио Свободная
146 
+Европа/Радио Свободная Азия) поддерживает развитие сети Tor для
147 
+предоставления помощи пользователям сети Интернет в странах, где нет
148 
+безопасного доступа к свободным медиа. Сеть Tor сохраняет способность людей,
149 
+находящихся за национальными брандмауэрами или под прослушиванием
150 
+репрессивных режимов, получать глобальную перспективу по спорным темам,
151 
+включая демократию, экономику и религию.
152 
+</li>
153 
+<li><strong>Гражданские журналисты в Китае</strong> используют сервис Tor для
154 
+написания статей о локальных событиях, способствуя социальным переменам и
155 
+политическим реформам.
156 
+</li>
157 
+<li><strong>Активные граждане и журналисты в <a
158 
+href="http://www.rsf.org/rubrique.php3?id_rubrique=554">Черных дырах
159 
+Интернета</a></strong> используют сервис Tor для исследования
160 
+государственной пропаганды и точек зрения оппозиционеров, для написания
161 
+историй в неконтролируемых государством медиа, и для избежания риска личных
162 
+последствий интеллектуального любопытства.
163 
+</li>
164 
+</ul>
165 
+
166 
+<a name="lawenforcement"></a>
167 
+<h2><a class="anchor" href="#lawenforcement">Сотрудники правоохранительных
168 
+органов используют Tor</a></h2>
169 
+<hr />
170 
+<ul>
171 
+<li><strong>Прослушивание в сети:</strong> Сервис Tor позволяет властям
172 
+просматривать сомнительные веб сайты и сервисы, не оставляя на них своих
173 
+следов. Если системный администратор нелегального сайта азартных игр,
174 
+например, увидел бы в логах посещений множество подключений от IP-адресов
175 
+правительственных или правоохранительных органов, расследование по этому
176 
+делу могло бы столкнуться со множеством сложностей.
177 
+</li>
178 
+<li><strong>Провокационные операции:</strong> Аналогично анонимность позволяет
179 
+сотрудникам правоохранительных органов участвовать в он-лайн операциях под
180 
+прикрытием. Не важно насколько хорошим может быть прикрытие офицера на
181 
+улице, если коммуникации включают IP-адреса, относящиеся к диапазону
182 
+полиции, прикрытие разрушено.
183 
+</li>
184 
+<li><strong>Настоящие советы по обеспечению анонимности:</strong> В то время как
185 
+он-лайн советы по обеспечению анонимности пользуются немалой популярностью,
186 
+без специального программного обеспечения, они не очень полезны. Опытные
187 
+источники понимают, что даже если информация об имени или адрес электронной
188 
+почты не предоставляются, логи сервера могут определить их очень быстро. В
189 
+результате, сайты с советами, которые не задействуют анонимность,
190 
+ограничивают свои советы.
191 
+</li>
192 
+</ul>
193 
+
194 
+<a name="activists"></a>
195 
+<h2><a class="anchor" href="#activists">Активисты и правдолюбы используют
196 
+Tor</a></h2>
197 
+<hr />
198 
+<ul>
199 
+<li><strong>Активисты защиты прав человека используют Tor, чтобы анонимно
200 
+докладывать из опасных зон о их нарушениях.</strong> Активные борцы за
201 
+соблюдение прав трудящихся намеренно используют Tor и другие формы онлайн и
202 
+оффлайн анонимности для организации работников в соответствии с
203 
+Универсальной Декларацией по Правам Человека. И хотя их деятельность вполне
204 
+законна, это не означает, что они в безопасности. Сервис Tor обеспечивает
205 
+возможность избежать расправы, не отказываясь от своего права выразить
206 
+протест.
207 
+</li>
208 
+<li>Когда такие группы как <strong>Комитет Друзей на Службе Обществу и
209 
+природоохранные группы все чаще<a
210 
+href="http://www.afsc.org/news/2005/government-spying.htm">подвергаются
211 
+прослушиванию</a> в Соединенных Штатах</strong> в рамках закона по защите от
212 
+терроризма, многие миролюбивые агенты, лоббирующие перемены, используют
213 
+сервис Tor для обеспечения базовой конфиденциальности во время своей
214 
+легальной деятельности.
215 
+</li>
216 
+<li><strong><a href="http://hrw.org/doc/?t=internet">Наблюдение за правами
217 
+человека (Human Rights Watch)</a></strong> рекомендует использование сети
218 
+Tor в своем докладе <a
219 
+href="http://www.hrw.org/reports/2006/china0806/">Гонка ко Дну:
220 
+Корпоративное Пособничество Китайской Интернет Цензуре (Race to the Bottom:
221 
+Corporate Complicity in Chinese Internet Censorship)</a>. Со автор доклада
222 
+взял интервью у Роджера Динглдайна (Roger Dingledine), Руководителя Проекта
223 
+Tor, об использовании сети Tor. Исследование рассказывает о том, как можно
224 
+при помощи сети Tor пробить брешь в <a
225 
+href="http://www.hrw.org/reports/2006/china0806/3.htm#_Toc142395820">Великом
226 
+Китайском Брандмауэре</a> и рекомендует правозащитникам по всему миру
227 
+использовать Tor для защиты просмотра Интернет страниц и коммуникаций.
228 
+</li>
229 
+<li> Проект Tor консультировал на волонтерской основе и помогал
230 
+<strong>недавней<a href="http://irrepressible.info/">кампании по
231 
+корпоративной ответственности</a>, проводимой Международной Амнистией
232 
+(Amnesty international)</strong>.  Посмотрите также их <a
233 
+href="http://irrepressible.info/static/pdf/FOE-in-china-2006-lores.pdf">полный
234 
+отчет</a> по теме Интернет в Китае.
235 
+</li>
236 
+<li>a href="http://www.globalvoicesonline.org">Проект Global Voices</a>
237 
+рекомендует использование Tor, особенно <strong>анонимным
238 
+блоггерам</strong>, на своем<a
239 
+href="http://advocacy.globalvoicesonline.org/projects/guide/"> веб
240 
+сайте.</a>
241 
+</li>
242 
+<li>Верховный суд США недавно снял легальную защиту с правительственных
243 
+правдолюбов. Но разоблачители, работающие над прозрачностью правительства
244 
+или корпоративной ответственностью, могут использовать Tor для поиска
245 
+справедливости, не раскрывая своей личности.
246 
+</li>
247 
+<li>Наш источник, работающий в некоммерческой организации в сфере
248 
+здравоохранения в Африке, рассказал нам, что его некоммерческая организация
249 
+<strong>должна тратить 10% своего бюджета на различного вида
250 
+коррупцию</strong>, главным образом, это различного рода взятки. Если эта
251 
+процентная ставка резко возрастёт, они не смогут ни позволить себе этих
252 
+денег, не пожаловаться; это тот случай, когда любые возражения могут стать
253 
+очень опасными. Таким образом, его некоммерческая организация <strong>начала
254 
+использовать Tor, чтобы безопасно разоблачать коррумпированное
255 
+правительство</strong> с тем, чтобы продолжить свою работу.
256 
+</li>
257 
+<li>На недавней конференции штатный сотрудник Tor наткнулся на женщину, которая
258 
+приехала из посёлка, расположенного на территории, принадлежащей
259 
+промышленной фирме на востоке Соединенных Штатов. Она пыталась анонимно
260 
+вести блог, чтобы сплотить местных жителей и <strong>ускорить реформу в
261 
+компании</strong>, которая доминировала в экономической и политической жизни
262 
+города. Она абсолютно уверена, что проделываемая ею организаторская работа
263 
+<strong>может привести к причинению вреда или даже к несчастному случаю со
264 
+смертельным исходом.</strong>
265 
+</li>
266 
+<li>В восточной Азии некоторые борцы за права трудящихся используют анонимность,
267 
+чтобы <strong>раскрывать информацию о потогонном производстве</strong>,
268 
+производящем товары для западных стран. Они пытаются организовать местных
269 
+работников.
270 
+</li>
271 
+<li>
272 
+Tor can help activists avoid government or corporate censorship that hinders
273 
+organization.  In one such case, a <a
274 
+href="http://www.cbc.ca/canada/story/2005/07/24/telus-sites050724.html">Canadian
275 
+ISP blocked access to a union website used by their own employees</a> to
276 
+help organize a strike.
277 
+</li>
278 
+</ul>
279 
+
280 
+<a name="spotlight"></a>
281 
+<h2><a class="anchor" href="#spotlight">Люди занимающие высокое и низкое
282 
+положение в обществе используют Tor</a></h2>
283 
+<hr />
284 
+<ul>
285 
+<li>Попадание под свет "публичных прожекторов" навсегда лишит вас частной жизни
286 
+в сети? Сельский юрист в Новой Англии (New England) анонимно ведет блог,
287 
+потому что учитывая многообразную клиентуру его престижной юридической
288 
+фирмы, <strong>его личные политические взгляды могут задеть
289 
+других</strong>. В то же время он не хочет сохранять молчание по тем
290 
+вопросам, которые его сильно заботят. Сеть Tor помогает ему чувствовать себя
291 
+безопасно, и он может выражать свое мнение без последствий для его публичной
292 
+роли.
293 
+</li>
294 
+<li>Люди, живущие в бедности чаще всего не могут в полной мере участвовать в
295 
+жизни гражданского общества - не из-за невежественности или апатии, а из-за
296 
+страха. Если что-то из того, что ты напишешь, будет прочитано твоим боссом,
297 
+потеряешь ли ты свою работу? Если твой социальный работник прочитает твое
298 
+мнение о системе, станет ли она относится к тебе по другому? Анонимность
299 
+дает голос безгласным. Чтобы поддержать это, <strong>проект Tor с недавних
300 
+пор имеет открытую Americorps/VISTA позицию</strong>, находящуюся сейчас в
301 
+режиме ожидания. Этот правительственный грант покроет полную стипендию для
302 
+волонтера, который должен будет создать учебный план для
303 
+<strong>демонстрации бедному населению способов использования анонимности в
304 
+сети Интернет для более безопасного гражданского участия</strong>. И хотя
305 
+часто говорится, что бедные не используют доступ к сети Интернет для
306 
+гражданского участия, в виду отсутствия возможности действовать в своих
307 
+собственных интересах, это наша гипотеза (основанная на персональном общении
308 
+и случайной информации), что именно постоянная запись оставленного в сети,
309 
+не позволяет многим бедным людям открыто говорить посредством сети
310 
+Интернет. Мы надеемся показать людям, как создать более безопасное
311 
+подключение к сети Интернет, а затем в конце года, оценить, как изменилось
312 
+гражданское участие в он- и оффлайн. Также интересно узнать, какое
313 
+продолжение этих изменений в будущем видит население.
314 
+</li>
315 
+</ul>
316 
+
317 
+<a name="executives"></a>
318 
+<h2><a class="anchor" href="#executives">Управляющие из сферы бизнеса используют
319 
+Tor</a></h2>
320 
+<hr />
321 
+<ul>
322 
+<li><strong>Информационный центр по безопасности и утечкам информации:</strong>
323 
+Скажем финансовый институт принимает участие в сохранении информации об
324 
+Интернет атаках. При наличие такой базы данных её участники должны
325 
+информировать центральную группу при обнаружении дыр. Центральная группа
326 
+коррелирует атаки, определяет их координированные механизмы и рассылает
327 
+предупреждения. Но если определенный банк в Сэйнт Луисе взломан, они не
328 
+захотят чтобы атакующий видел трафик между банком и таким центром. Так как в
329 
+этом случае атакующий сможет определить наличие определенной связи между
330 
+этими институтами. И хотя каждый пакет был бы зашифрован, IP-адрес выдавал
331 
+бы местоположение взломанной системы и базы данных. Сеть Tor позволяет таким
332 
+хранилищам чувствительной информации противостоять описанной выше опасности.
333 
+</li>
334 
+<li><strong>Видеть ваше соперничество так, как его видит рынок:</strong> Если вы
335 
+пытаетесь определить цены вашего конкурента, на сайте вы, возможно, либо
336 
+вообще не найдете такой информации, либо найдете обманчивые данные. Возможно
337 
+конкурент специально установил систему определения IP-адресов конкурирующих
338 
+фирм и либо блокирует ваш доступ на сайт, либо дезинформирует ваш
339 
+персонал. Сеть Tor позволяет бизнес структурам видеть их рыночный сектор
340 
+так, как его видит общественность.
341 
+</li>
342 
+<li><strong>Сохранить информацию о стратегиях конфиденциальной:</strong>
343 
+Инвестиционный банк, например, скорее всего не захочет, чтобы промышленные
344 
+"нюхачи" могли отслеживать, какие веб сайты просматривают его
345 
+аналитики. Стратегическая важность образцов трафика, и уязвимость
346 
+подслушивания подобных данных, начинает все больше признаваться в нескольких
347 
+сферах бизнес мира.
348 
+</li>
349 
+<li><strong>Подотчетность:</strong> В эпоху, когда безответственная и не
350 
+доложенная корпоративная деятельность подрывает бизнес структуры, стоимостью
351 
+много миллиардов долларов, управленец практикующий правильное управление
352 
+хочет, чтобы весь персонал свободно раскрывал внутренние
353 
+преступления. Сервис Tor упрощает внутреннюю подотчетность прежде чем эта
354 
+информация выйдет наружу.
355 
+</li>
356 
+</ul>
357 
+
358 
+<a name="bloggers"></a>
359 
+<h2><a class="anchor" href="#bloggers">Блоггеры используют Tor</a></h2>
360 
+<hr />
361 
+<ul>
362 
+<li>Довольно часто мы слышим о блоггерах, которые <a
363 
+href="http://online.wsj.com/public/article/SB112541909221726743-Kl4kLxv0wSbjqrkXg_DieY3c8lg_20050930.html">предстали
364 
+перед судом</a> или <a
365 
+href="http://www.usatoday.com/money/workplace/2005-06-14-worker-blogs-usat_x.htm">были
366 
+уволены</a> за совершенно легальные публикации на их блогах.</li>
367 
+<li>Мы рекомендуем <a
368 
+href="http://www.eff.org/issues/bloggers/legal">Юридическое Руководство от
369 
+EFF для Блоггеров</a>.</li>
370 
+<li>Проект Global Voices поддерживает работу <a
371 
+href="http://advocacy.globalvoicesonline.org/projects/guide/">руководства по
372 
+анонимному блоггингу совместно с Wordpress и проектом Tor</a>.</li>
373 
+</ul>
374 
+
375 
+<a name="itprofessionals"></a>
376 
+<h2><a class="anchor" href="#itprofessionals">Профессионалы из сферы
377 
+Информационных Технологий используют Tor</a></h2>
378 
+<hr />
379 
+<ul>
380 
+<li>Для того, чтобы определить правила фильтрации по IP-адресам: Брандмауэр
381 
+может иметь некоторые правила, которые пропускают только определенные
382 
+IP-адреса или их определенный спектр. Сервис Tor может быть использован для
383 
+определения этих настроек, используя IP-номер, находящийся вне IP блока
384 
+компании.</li>
385 
+<li>Для обхода своих собственных систем безопасности с целью осуществления
386 
+особой профессиональной деятельности: Например, компания может иметь строгие
387 
+правила, касательно сайтов сети Интернет, которые сотрудники могут
388 
+просматривать. Просмотр логов открывает возможные нарушения. Сеть Tor может
389 
+быть использована для верификации информации без внесения исключений в
390 
+корпоративную систему безопасности.</li>
391 
+<li>Для повторного подключения к тестируемым сервисам: Системный инженер может
392 
+использовать Tor для удаленного повторного подключения к сервисам, без
393 
+необходимости во внешней машине или пользовательском аккаунте, при
394 
+проведении операционного тестирования.</li>
395 
+<li>Для доступа к Интернет ресурсам: Допустимые правила использования сети для
396 
+ИТ персонала и обычных сотрудников, как правило, различаются. Сервис Tor
397 
+может обеспечить неограниченный доступ к сети Интернет, без необходимости
398 
+внесения изменений в стандартные настройки безопасности в офисе.</li>
399 
+<li>Для обеспечения работы провайдера в проблемных ситуациях: Иногда, когда
400 
+Интернет сервис провайдер испытывает проблемы с маршрутизацией или DNS, Tor
401 
+может сохранить доступность Интернет ресурсов, в то время как сам провайдер
402 
+работает с перебоями. Это может не сработать в критических ситуациях. </li>
403 
+</ul>
404 
+
405 
+<p>
406 
+Пожалуйста, высылайте нам истории успеха. Они очень важны, так как Tor
407 
+обеспечивает анонимность. В то время как все норовят поспорить о <a
408 
+href="<page faq-abuse>">нежелательных эффектах Tor</a>, никто не замечает
409 
+успехи нашей сети. Это замечательно для пользователей, но не очень хорошо
410 
+для нас, так как публикация историй успеха о том, как люди или организации
411 
+остаются анонимными могла бы быть контр продуктивной. Например, мы говорили
412 
+с офицером ФБР, который объяснил, что он использует Tor в работе ежедневно;
413 
+но он сразу попросил нас не предоставлять детали и не упоминать его имя.</p>
414 
+
415 
+<p> Как и любая другая технология, от карандаша до сотового телефона,
416 
+анонимность может быть использована как для плохих, так и для хороших
417 
+дел. Вы наверняка уже сталкивались с серьезными дебатами (<a
418 
+href="http://www.wired.com/politics/security/commentary/securitymatters/2006/01/70000">точка
419 
+зрения «за»</a>, <a href="http://www.edge.org/q2006/q06_4.html#kelly">точка
420 
+зрения «против»</a>, и <a
421 
+href="http://web.mit.edu/gtmarx/www/anon.html">академическая точка
422 
+зрения</a>) об анонимности. Проект Tor основан на убеждении, что анонимность
423 
+– это не просто хорошая идея, – это необходимое требование для свободного и
424 
+действующего общества. Организация <a
425 
+href="http://www.eff.org/issues/anonymity">EFF предоставляет хороший
426 
+обзор</a> того, насколько важна была анонимность при создании Соединенных
427 
+Штатов Америки. Анонимность признана судами США как фундаментальное и важное
428 
+право. На самом деле правительства дают полномочия на анонимность во многих
429 
+случаях сами: <a href="https://www.crimeline.co.za/default.asp">советы
430 
+полиции</a>, <a
431 
+href="http://www.texasbar.com/Content/ContentGroups/Public_Information1/Legal_Resources_Consumer_Information/Family_Law1/Adoption_Options.htm#sect2">сервисы
432 
+по усыновлению/удочерению</a>, <a
433 
+href="http://writ.news.findlaw.com/aronson/20020827.html">подлинность
434 
+офицера полиции</a>, и так далее. Было бы невозможно изложить все дебаты по
435 
+анонимности здесь – это слишком большая тема с множеством нюансов. К тому же
436 
+есть множество других источников, где вы можете найти эту информацию. У нас
437 
+есть <a href="<page faq-abuse>">Список часто задаваемых вопросов по
438 
+злоупотреблению сетью Tor</a> , где вы найдете несколько возможных случаев
439 
+злоупотреблений Tor, но достаточно сказать, что если вы хотите злоупотребить
440 
+системой, вы скорее всего найдете её по по большей части закрытой для ваших
441 
+целей (например, большая часть ретрансляторов Tor не поддерживает SMTP во
442 
+избежание анонимного спаминга), или если вы один из <a
443 
+href="http://www.schneier.com/blog/archives/2005/12/computer_crime_1.html">Четырех
444 
+Всадников Информационного Апокалипсиса</a>, у вас есть более хорошие
445 
+инструменты, чем Tor. Не отвергая потенциальные способы злоупотребления
446 
+системой Tor, эта страница демонстрирует несколько из многих важных способов
447 
+использования онлайн анонимности сегодня.</p>
448 
+</div>
449 
+#include <foot.wmi>
update-mirrors.pl
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,973 @@
1 
+#!/usr/bin/perl -w
2 
+use warnings;
3 
+use strict;
4 
+use LWP::Simple;
5 
+use LWP;
6 
+use Date::Parse;
7 
+use Date::Format;
8 
+
9 
+#
10 
+# A quick hack by Jacob Appelbaum <jacob@appelbaum.net>
11 
+# LWP suggestions by Leigh Honeywell
12 
+# This is Free Software (GPLv3)
13 
+# http://www.gnu.org/licenses/gpl-3.0.txt
14 
+#
15 
+#Contacted
16 
+# http://tor.askapache.com/ HTTP 403 Contacted 20091027
17 
+#
18 
+#CHANGELOG
19 
+#20091003 Code changes to elimiate the need for a trailing slash in addresses for script runtime
20 
+#20091004 Code changes to increase out of date tolerance to 48 hours
21 
+#20091028 Code changes to increase timout to 30 seconds (attempting to resolve "unknown" status'
22 
+#20091028 Code changes to change user agent of script
23 
+
24 
+print "Creating LWP agent ($LWP::VERSION)...\n";
25 
+my $lua = LWP::UserAgent->new(
26 
+    keep_alive => 1,
27 
+    timeout => 30,
28 
+    agent => "Tor MirrorCheck Agent"
29 
+);
30 
+
31 
+sub sanitize {
32 
+    my $taintedData = shift;
33 
+    my $cleanedData;
34 
+    my $whitelist = '-a-zA-Z0-9: +';
35 
+
36 
+    # clean the data, return cleaned data
37 
+    $taintedData =~ s/[^$whitelist]//go;
38 
+    $cleanedData = $taintedData;
39 
+
40 
+    return $cleanedData;
41 
+}
42 
+
43 
+sub FetchDate {
44 
+    my $url = shift; # Base url for mirror
45 
+    my $trace = "/project/trace/www.torproject.org"; # Location of recent update info
46 
+    $url = "$url$trace";
47 
+
48 
+    print "Fetching possible date from: $url\n";
49 
+
50 
+    my $request = new HTTP::Request GET => "$url";
51 
+    my $result = $lua->request($request);
52 
+    my $code = $result->code();
53 
+    print "Result code $code\n";
54 
+
55 
+    if ($result->is_success && $code eq "200"){
56 
+       my $taint = $result->content;
57 
+       my $content = sanitize($taint);
58 
+       if ($content) {
59 
+
60 
+            my $date = str2time($content);
61 
+
62 
+            if ($date) {
63 
+                print "We've fetched a date $date.\n";
64 
+                return $date;
65 
+            } else {
66 
+                print "We've haven't fetched a date.\n";
67 
+                return "Unknown";
68 
+            }
69 
+
70 
+        } else {
71 
+            print "Unable to fetch date, empty content returned.\n";
72 
+            return "Unknown";
73 
+        }
74 
+
75 
+    } else {
76 
+       print "Our request failed, we had no result.\n";
77 
+       return "Unknown";
78 
+    }
79 
+
80 
+    return "Unknown";
81 
+}
82 
+
83 
+# This is the list of all known Tor mirrors
84 
+# Add new mirrors to the bottom!
85 
+my %m = (
86 
+
87 
+        mirror001 => {
88 
+            adminContact => "BarkerJr AT barkerjr DOT net",
89 
+            orgName => "BarkerJr",
90 
+            isoCC => "FR",
91 
+            subRegion => "",
92 
+            region => "FR",
93 
+            ipv4 => "True",
94 
+            ipv6 => "False",
95 
+            loadBalanced => "No",
96 
+            httpWebsiteMirror => "http://www.oignon.net/",
97 
+            httpsWebsiteMirror => "https://oignon.net/",
98 
+            rsyncWebsiteMirror => "",
99 
+            ftpWebsiteMirror => "",
100 
+            httpDistMirror => "http://www.oignon.net/dist/",
101 
+            httpsDistMirror => "https://oignon.net/dist/",
102 
+            rsyncDistMirror => "",
103 
+            hiddenServiceMirror => "",
104 
+            updateDate => "Unknown",
105 
+        },
106 
+
107 
+       mirror002 => {
108 
+            adminContact => "operator AT hermetix DOT org",
109 
+            orgName => "Hermetix",
110 
+            isoCC => "CA",
111 
+            subRegion => "QC",
112 
+            region => "North America",
113 
+            ipv4 => "True",
114 
+            ipv6 => "False",
115 
+            loadBalanced => "Unknown",
116 
+            httpWebsiteMirror => "http://tor.hermetix.org/",
117 
+            rsyncWebsiteMirror => "",
118 
+            httpDistMirror => "",
119 
+            rsyncDistMirror => "",
120 
+            updateDate => "Unknown",
121 
+        },
122 
+
123 
+       mirror003 => {
124 
+            adminContact => "",
125 
+            orgName => "Boinc",
126 
+            isoCC => "CH",
127 
+            subRegion => "",
128 
+            region => "Europe",
129 
+            ipv4 => "True",
130 
+            ipv6 => "False",
131 
+            loadBalanced => "Unknown",
132 
+            httpWebsiteMirror => "http://tor.boinc.ch/",
133 
+            ftpWebsiteMirror => "",
134 
+            rsyncWebsiteMirror => "",
135 
+            httpDistMirror => "http://tor.boinc.ch/dist/",
136 
+            rsyncDistMirror => "",
137 
+            updateDate => "Unknown",
138 
+        },
139 
+
140 
+       mirror005 => {
141 
+            adminContact => "citizen428 AT gmail DOT com",
142 
+            orgName => "Bbs",
143 
+            isoCC => "DE",
144 
+            subRegion => "",
145 
+            region => "Europe",
146 
+            ipv4 => "True",
147 
+            ipv6 => "False",
148 
+            loadBalanced => "Unknown",
149 
+            httpWebsiteMirror => "http://tor.blingblingsquad.net/",
150 
+            ftpWebsiteMirror => "",
151 
+            rsyncWebsiteMirror => "",
152 
+            httpDistMirror => "",
153 
+            rsyncDistMirror => "",
154 
+            updateDate => "Unknown",
155 
+        },
156 
+
157 
+       mirror006 => {
158 
+            adminContact => "doc DOT kuehn AT nexgo DOT de",
159 
+            orgName => " spacecowboy ",
160 
+            isoCC => " ",
161 
+            subRegion => "",
162 
+            region => "DE",
163 
+            ipv4 => "True",
164 
+            ipv6 => "False",
165 
+            loadBalanced => "No",
166 
+            httpWebsiteMirror => "http://tor-proxy.de/tor-mirror/",
167 
+            httpsWebsiteMirror => "https://tor-proxy.de/tor-mirror/",
168 
+            rsyncWebsiteMirror => "",
169 
+            ftpWebsiteMirror => "",
170 
+            httpDistMirror => "http://tor-proxy.de/tor-mirror/dist/",
171 
+            httpsDistMirror => "https://tor-proxy.de/tor-mirror/dist/",
172 
+            rsyncDistMirror => "",
173 
+            hiddenServiceMirror => "",
174 
+            updateDate => "Unknown",
175 
+        },
176 
+
177 
+       mirror007 => {
178 
+            adminContact => "cm AT cybermirror DOT org",
179 
+            orgName => "Cybermirror",
180 
+            isoCC => "DE",
181 
+            subRegion => "",
182 
+            region => "Europe",
183 
+            ipv4 => "True",
184 
+            ipv6 => "False",
185 
+            loadBalanced => "Unknown",
186 
+            httpWebsiteMirror => "http://tor.cybermirror.org/",
187 
+            ftpWebsiteMirror => "",
188 
+            rsyncWebsiteMirror => "",
189 
+            httpDistMirror => "http://tor.cybermirror.org/dist/",
190 
+            rsyncDistMirror => "",
191 
+            updateDate => "Unknown",
192 
+        },
193 
+
194 
+       mirror008 => {
195 
+            adminContact => "contact AT algorithmus DOT com",
196 
+            orgName => "Spline",
197 
+            isoCC => "DE",
198 
+            subRegion => "FU",
199 
+            region => "Europe",
200 
+            ipv4 => "True",
201 
+            ipv6 => "False",
202 
+            loadBalanced => "Unknown",
203 
+            httpWebsiteMirror => "",
204 
+            ftpWebsiteMirror => "",
205 
+            rsyncWebsiteMirror => "",
206 
+            httpDistMirror => "http://rem.spline.de/tor/",
207 
+            rsyncDistMirror => "",
208 
+            updateDate => "Unknown",
209 
+        },
210 
+
211 
+	mirror009 => {
212 
+            adminContact => "BarkerJr AT barkerjr DOT net",
213 
+            orgName => "BarkerJr",
214 
+            isoCC => "US",
215 
+            subRegion => "",
216 
+            region => "US",
217 
+            ipv4 => "True",
218 
+            ipv6 => "False",
219 
+            loadBalanced => "No",
220 
+            httpWebsiteMirror => "http://www.torproject.us/",
221 
+            httpsWebsiteMirror => "https://www.torproject.us/",
222 
+            rsyncWebsiteMirror => "rsync://rsync.torproject.us/tor",
223 
+            ftpWebsiteMirror => "",
224 
+            httpDistMirror => "http://www.torproject.us/dist/",
225 
+            httpsDistMirror => "https://www.torproject.us/dist/",
226 
+            rsyncDistMirror => "rsync://rsync.torproject.us/tor/dist",
227 
+            hiddenServiceMirror => "",
228 
+            updateDate => "Unknown",
229 
+        },
230 
+
231 
+	mirror010 => {
232 
+            adminContact => "",
233 
+            orgName => "zuola",
234 
+            isoCC => "CN",
235 
+            subRegion => "",
236 
+            region => "CN",
237 
+            ipv4 => "True",
238 
+            ipv6 => "False",
239 
+            loadBalanced => "No",
240 
+            httpWebsiteMirror => "http://tor.zuo.la/",
241 
+            httpsWebsiteMirror => "",
242 
+            rsyncWebsiteMirror => "",
243 
+            ftpWebsiteMirror => "",
244 
+            httpDistMirror => "http://tor.zuo.la/dist/",
245 
+            httpsDistMirror => "",
246 
+            rsyncDistMirror => "",
247 
+            hiddenServiceMirror => "",
248 
+            updateDate => "Unknown",
249 
+        },
250 
+
251 
+       mirror011 => {
252 
+            adminContact => "info AT zentrum-der-gesundheit DOT de",
253 
+            orgName => "Zentrum der Gesundheit",
254 
+            isoCC => "DK",
255 
+            subRegion => "",
256 
+            region => "Europe",
257 
+            ipv4 => "True",
258 
+            ipv6 => "False",
259 
+            loadBalanced => "Unknown",
260 
+            httpWebsiteMirror => "http://tor.idnr.ws/",
261 
+            ftpWebsiteMirror => "",
262 
+            rsyncWebsiteMirror => "",
263 
+            httpDistMirror => "http://tor.idnr.ws/dist/",
264 
+            rsyncDistMirror => "",
265 
+            updateDate => "Unknown",
266 
+        },
267 
+
268 
+       mirror012 => {
269 
+            adminContact => "kurt AT miroir-francais DOT fr",
270 
+            orgName => "CRAN",
271 
+            isoCC => "FR",
272 
+            subRegion => "Ile de France",
273 
+            region => "Europe",
274 
+            ipv4 => "True",
275 
+            ipv6 => "False",
276 
+            loadBalanced => "Unknown",
277 
+            httpWebsiteMirror => "",
278 
+            rsyncWebsiteMirror => "rsync://miroir-francais.fr::tor",
279 
+            ftpWebsiteMirror => "ftp://miroir-francais.fr/pub/tor/",
280 
+            httpDistMirror => "http://tor.miroir-francais.fr/",
281 
+            rsyncDistMirror => "",
282 
+            updateDate => "Unknown",
283 
+        },
284 
+
285 
+       mirror013 => {
286 
+            adminContact => "root AT amorphis DOT eu",
287 
+            orgName => "Amorphis",
288 
+            isoCC => "NL",
289 
+            subRegion => "",
290 
+            region => "Europe",
291 
+            ipv4 => "True",
292 
+            ipv6 => "False",
293 
+            loadBalanced => "Unknown",
294 
+            httpWebsiteMirror => "http://tor.amorphis.eu/",
295 
+            rsyncWebsiteMirror => "",
296 
+            ftpWebsiteMirror => "",
297 
+            httpDistMirror => "http://tor.amorphis.eu/dist/",
298 
+            rsyncDistMirror => "",
299 
+            updateDate => "Unknown",
300 
+        },
301 
+
302 
+       mirror014 => {
303 
+            adminContact => "mirror AT bit DOT nl",
304 
+            orgName => "BIT BV",
305 
+            isoCC => "NL",
306 
+            subRegion => "",
307 
+            region => "Europe",
308 
+            ipv4 => "True",
309 
+            ipv6 => "False",
310 
+            loadBalanced => "Unknown",
311 
+            httpWebsiteMirror => "",
312 
+            rsyncWebsiteMirror => "",
313 
+            ftpWebsiteMirror => "ftp://ftp.bit.nl/mirror/tor/",
314 
+            httpDistMirror => "http://ftp.bit.nl/mirror/tor/",
315 
+            rsyncDistMirror => "",
316 
+            updateDate => "Unknown",
317 
+        },
318 
+
319 
+       mirror015 => {
320 
+            adminContact => "webmaster AT ccc DOT de",
321 
+            orgName => "CCC",
322 
+            isoCC => "NL",
323 
+            subRegion => "",
324 
+            region => "Europe",
325 
+            ipv4 => "True",
326 
+            ipv6 => "False",
327 
+            loadBalanced => "Unknown",
328 
+            httpWebsiteMirror => "http://tor.ccc.de/",
329 
+            rsyncWebsiteMirror => "",
330 
+            ftpWebsiteMirror => "",
331 
+            httpDistMirror => "http://tor.ccc.de/dist/",
332 
+            rsyncDistMirror => "",
333 
+            updateDate => "Unknown",
334 
+        },
335 
+
336 
+       mirror016 => {
337 
+            adminContact => "root AT kamagurka DOT org",
338 
+            orgName => "Kamagurka",
339 
+            isoCC => "NL",
340 
+            subRegion => "Haarlem",
341 
+            region => "Europe",
342 
+            ipv4 => "True",
343 
+            ipv6 => "False",
344 
+            loadBalanced => "Unknown",
345 
+            httpWebsiteMirror => "http://tor.kamagurka.org/",
346 
+            rsyncWebsiteMirror => "",
347 
+            ftpWebsiteMirror => "",
348 
+            httpDistMirror => "http://tor.kamagurka.org/dist/",
349 
+            rsyncDistMirror => "",
350 
+            updateDate => "Unknown",
351 
+        },
352 
+
353 
+       mirror018 => {
354 
+            adminContact => "evert AT meulie DOT net",
355 
+            orgName => "Meulie",
356 
+            isoCC => "NO",
357 
+            subRegion => "",
358 
+            region => "Europe",
359 
+            ipv4 => "True",
360 
+            ipv6 => "False",
361 
+            loadBalanced => "Unknown",
362 
+            httpWebsiteMirror => "",
363 
+            rsyncWebsiteMirror => "",
364 
+            ftpWebsiteMirror => "",
365 
+            httpDistMirror => "http://tor.meulie.net/",
366 
+            rsyncDistMirror => "",
367 
+            updateDate => "Unknown",
368 
+        },
369 
+
370 
+       mirror019 => {
371 
+            adminContact => "ghirai AT ghirai DOT com",
372 
+            orgName => "Ghirai",
373 
+            isoCC => "UK",
374 
+            subRegion => "London",
375 
+            region => "Europe",
376 
+            ipv4 => "True",
377 
+            ipv6 => "False",
378 
+            loadBalanced => "Unknown",
379 
+            httpWebsiteMirror => "",
380 
+            rsyncWebsiteMirror => "",
381 
+            ftpWebsiteMirror => "",
382 
+            httpDistMirror => "http://www.ghirai.com/tor/",
383 
+            rsyncDistMirror => "",
384 
+            updateDate => "Unknown",
385 
+        },
386 
+
387 
+	mirror020 => {
388 
+            adminContact => "",
389 
+            orgName => "ax",
390 
+            isoCC => "HU",
391 
+            subRegion => "",
392 
+            region => "HU",
393 
+            ipv4 => "True",
394 
+            ipv6 => "False",
395 
+            loadBalanced => "No",
396 
+            httpWebsiteMirror => "",
397 
+            httpsWebsiteMirror => "",
398 
+            rsyncWebsiteMirror => "",
399 
+            ftpWebsiteMirror => "",
400 
+            httpDistMirror => "http://tor.initrd.net/dist/",
401 
+            httpsDistMirror => "",
402 
+            rsyncDistMirror => "",
403 
+            hiddenServiceMirror => "",
404 
+            updateDate => "Unknown",
405 
+        },
406 
+
407 
+       mirror021 => {
408 
+	    adminContact => "hostmaster AT zombiewerks DOT com",
409 
+            orgName => "TheOnionRouter",
410 
+            isoCC => "US",
411 
+            subRegion => "New Jersey",
412 
+            region => "North America",
413 
+            ipv4 => "True",
414 
+            ipv6 => "False",
415 
+            loadBalanced => "Unknown",
416 
+            httpWebsiteMirror => "http://www.theonionrouter.com/",
417 
+            rsyncWebsiteMirror => "",
418 
+            ftpWebsiteMirror => "",
419 
+            httpDistMirror => "http://www.theonionrouter.com/dist/",
420 
+            rsyncDistMirror => "",
421 
+            updateDate => "Unknown",
422 
+        },
423 
+
424 
+       mirror022 => {
425 
+            adminContact => "jeroen AT unfix DOT org",
426 
+            orgName => "Unfix",
427 
+            isoCC => "CH",
428 
+            subRegion => "",
429 
+            region => "Europe",
430 
+            ipv4 => "True",
431 
+            ipv6 => "True",
432 
+            loadBalanced => "Unknown",
433 
+            httpWebsiteMirror => "http://tor.unfix.org/",
434 
+            rsyncWebsiteMirror => "",
435 
+            ftpWebsiteMirror => "",
436 
+            httpDistMirror => "http://tor.unfix.org/dist/",
437 
+            rsyncDistMirror => "",
438 
+            updateDate => "Unknown",
439 
+        },
440 
+
441 
+       mirror023 => {
442 
+            adminContact => "jeroen AT unfix DOT org",
443 
+            orgName => "Sixx",
444 
+            isoCC => "CH",
445 
+            subRegion => "",
446 
+            region => "Europe",
447 
+            ipv4 => "True",
448 
+            ipv6 => "True",
449 
+            loadBalanced => "Unknown",
450 
+            httpWebsiteMirror => "http://tor.sixxs.net/",
451 
+            rsyncWebsiteMirror => "",
452 
+            ftpWebsiteMirror => "",
453 
+            httpDistMirror => "http://tor.sixxs.net/dist/",
454 
+            rsyncDistMirror => "",
455 
+            updateDate => "Unknown",
456 
+        },
457 
+
458 
+       mirror024 => {
459 
+            adminContact => "",
460 
+            orgName => "StrangeCharm",
461 
+            isoCC => "",
462 
+            subRegion => "",
463 
+            region => "FR",
464 
+            ipv4 => "True",
465 
+            ipv6 => "False",
466 
+            loadBalanced => "No",
467 
+            httpWebsiteMirror => "http://torproject.the-onion-router.net/",
468 
+            httpsWebsiteMirror => "",
469 
+            rsyncWebsiteMirror => "",
470 
+            ftpWebsiteMirror => "",
471 
+            httpDistMirror => "http://torproject.the-onion-router.net/dist/",
472 
+            httpsDistMirror => "",
473 
+            rsyncDistMirror => "",
474 
+            hiddenServiceMirror => "",
475 
+        },
476 
+
477 
+       mirror025 => {
478 
+            adminContact => "web2005a AT year2005a.wiretapped DOT net",
479 
+            orgName => "Wiretapped",
480 
+            isoCC => "AU",
481 
+            subRegion => "Sydney",
482 
+            region => "Oceania",
483 
+            ipv4 => "True",
484 
+            ipv6 => "False",
485 
+            loadBalanced => "Unknown",
486 
+            httpWebsiteMirror => "",
487 
+            rsyncWebsiteMirror => "",
488 
+            ftpWebsiteMirror => "ftp://ftp.mirrors.wiretapped.net/pub/security/cryptography/network/tor/",
489 
+            httpDistMirror => "http://www.mirrors.wiretapped.net/security/cryptography/network/tor/",
490 
+            rsyncDistMirror => "",
491 
+            updateDate => "Unknown",
492 
+        },
493 
+
494 
+        mirror026 => {
495 
+            adminContact => "tormaster AT xpdm DOT us",
496 
+            orgName => "Xpdm",
497 
+            isoCC => "US",
498 
+            subRegion => "",
499 
+            region => "North America",
500 
+            ipv4 => "True",
501 
+            ipv6 => "False",
502 
+            loadBalanced => "Unknown",
503 
+            httpWebsiteMirror => "http://torproj.xpdm.us/",
504 
+            httpsWebsiteMirror => "https://torproj.xpdm.us/",
505 
+            rsyncWebsiteMirror => "",
506 
+            ftpWebsiteMirror => "",
507 
+            httpDistMirror => "http://torproj.xpdm.us/dist/",
508 
+            httpsDistMirror => "https://torproj.xpdm.us/dist/",
509 
+            rsyncDistMirror => "",
510 
+            hiddenServiceMirror => "http://h3prhz46uktgm4tt.onion/",
511 
+            updateDate => "Unknown",
512 
+        },
513 
+
514 
+        mirror027 => {
515 
+            adminContact => "",
516 
+            orgName => " cybervalley ",
517 
+            isoCC => " ",
518 
+            subRegion => "",
519 
+            region => " ",
520 
+            ipv4 => "True",
521 
+            ipv6 => "False",
522 
+            loadBalanced => "No",
523 
+            httpWebsiteMirror => "http://torproject.cybervalley.org/",
524 
+            httpsWebsiteMirror => "",
525 
+            rsyncWebsiteMirror => "",
526 
+            ftpWebsiteMirror => "",
527 
+            httpDistMirror => "",
528 
+            httpsDistMirror => "",
529 
+            rsyncDistMirror => "",
530 
+            hiddenServiceMirror => "",
531 
+            updateDate => "Unknown",
532 
+        },
533 
+
534 
+        mirror028 => {
535 
+            adminContact => "security AT hostoffice DOT hu",
536 
+            orgName => "Unknown",
537 
+            isoCC => "HU",
538 
+            subRegion => "Hungary",
539 
+            region => "Europe",
540 
+            ipv4 => "True",
541 
+            ipv6 => "False",
542 
+            loadBalanced => "No",
543 
+            httpWebsiteMirror => "http://tor.hu/",
544 
+            httpsWebsiteMirror => "",
545 
+            rsyncWebsiteMirror => "",
546 
+            ftpWebsiteMirror => "",
547 
+            httpDistMirror => "",
548 
+            httpsDistMirror => "",
549 
+            rsyncDistMirror => "",
550 
+            hiddenServiceMirror => "",
551 
+            updateDate => "Unknown",
552 
+        },
553 
+
554 
+        mirror029 => {
555 
+            adminContact => "",
556 
+            orgName => "Technica-03",
557 
+            isoCC => "UA",
558 
+            subRegion => "Ukraine",
559 
+            region => "Eastern Europe",
560 
+            ipv4 => "True",
561 
+            ipv6 => "False",
562 
+            loadBalanced => "No",
563 
+            httpWebsiteMirror => "http://torua.reactor-xg.kiev.ua/",
564 
+            httpsWebsiteMirror => "",
565 
+            rsyncWebsiteMirror => "",
566 
+            ftpWebsiteMirror => "",
567 
+            httpDistMirror => "http://tordistua.reactor-xg.kiev.ua/",
568 
+            httpsDistMirror => "",
569 
+            rsyncDistMirror => "",
570 
+            hiddenServiceMirror => "",
571 
+            updateDate => "Unknown",
572 
+        },
573 
+
574 
+	mirror030 => {
575 
+            adminContact => "",
576 
+            orgName => "chaos darmstadt",
577 
+            isoCC => "DE",
578 
+            subRegion => "Germany",
579 
+            region => "Europe",
580 
+            ipv4 => "True",
581 
+            ipv6 => "False",
582 
+            loadBalanced => "No",
583 
+            httpWebsiteMirror => "http://mirrors.chaos-darmstadt.de/tor-mirror/",
584 
+            httpsWebsiteMirror => "",
585 
+            rsyncWebsiteMirror => "",
586 
+            ftpWebsiteMirror => "",
587 
+            httpDistMirror => "http://mirrors.chaos-darmstadt.de/tor-mirror/dist/",
588 
+            httpsDistMirror => "",
589 
+            rsyncDistMirror => "",
590 
+            hiddenServiceMirror => "",
591 
+            updateDate => "Unknown",
592 
+        },
593 
+
594 
+	mirror031 => {
595 
+            adminContact => "webmaster AT askapache DOT com",
596 
+            orgName => "AskApache",
597 
+            isoCC => "US",
598 
+            subRegion => "California",
599 
+            region => "US",
600 
+            ipv4 => "True",
601 
+            ipv6 => "False",
602 
+            loadBalanced => "No",
603 
+            httpWebsiteMirror => "http://tor.askapache.com/",
604 
+            httpsWebsiteMirror => "",
605 
+            rsyncWebsiteMirror => "",
606 
+            ftpWebsiteMirror => "",
607 
+            httpDistMirror => "http://tor.askapache.com/dist/",
608 
+            httpsDistMirror => "",
609 
+            rsyncDistMirror => "",
610 
+            hiddenServiceMirror => "",
611 
+            updateDate => "Unknown",
612 
+        },
613 
+
614 
+	mirror032 => {
615 
+            adminContact => "",
616 
+            orgName => "I'm on the roof",
617 
+            isoCC => "US",
618 
+            subRegion => "",
619 
+            region => "US",
620 
+            ipv4 => "True",
621 
+            ipv6 => "False",
622 
+            loadBalanced => "No",
623 
+            httpWebsiteMirror => "http://mirror.imontheroof.com/tor-mirror/",
624 
+            httpsWebsiteMirror => "",
625 
+            rsyncWebsiteMirror => "",
626 
+            ftpWebsiteMirror => "",
627 
+            httpDistMirror => "http://mirror.imontheroof.com/tor-mirror/dist/",
628 
+            httpsDistMirror => "",
629 
+            rsyncDistMirror => "",
630 
+            hiddenServiceMirror => "",
631 
+            updateDate => "Unknown",
632 
+        },
633 
+
634 
+	mirror033 => {
635 
+            adminContact => "",
636 
+            orgName => "bullog",
637 
+            isoCC => "CN",
638 
+            subRegion => "",
639 
+            region => "CN",
640 
+            ipv4 => "True",
641 
+            ipv6 => "False",
642 
+            loadBalanced => "No",
643 
+            httpWebsiteMirror => "http://tor.bullog.org/",
644 
+            httpsWebsiteMirror => "",
645 
+            rsyncWebsiteMirror => "",
646 
+            ftpWebsiteMirror => "",
647 
+            httpDistMirror => "http://tor.bullog.org/dist/",
648 
+            httpsDistMirror => "",
649 
+            rsyncDistMirror => "",
650 
+            hiddenServiceMirror => "",
651 
+            updateDate => "Unknown",
652 
+        },
653 
+
654 
+	mirror034 => {
655 
+            adminContact => " mail AT benjamin-meier DOT info ",
656 
+            orgName => "beme it",
657 
+            isoCC => "DE",
658 
+            subRegion => "",
659 
+            region => "DE",
660 
+            ipv4 => "True",
661 
+            ipv6 => "False",
662 
+            loadBalanced => "No",
663 
+            httpWebsiteMirror => "http://tor.beme-it.de/",
664 
+            httpsWebsiteMirror => "",
665 
+            rsyncWebsiteMirror => "rsync://tor.beme-it.de/tor",
666 
+            ftpWebsiteMirror => "",
667 
+            httpDistMirror => "http://tor.beme-it.de/dist/",
668 
+            httpsDistMirror => "",
669 
+            rsyncDistMirror => "rsync://tor.beme-it.de/tor/dist",
670 
+            hiddenServiceMirror => "",
671 
+            updateDate => "Unknown",
672 
+        },
673 
+
674 
+	mirror035 => {
675 
+            adminContact => "",
676 
+            orgName => "shizhao",
677 
+            isoCC => "CN",
678 
+            subRegion => "",
679 
+            region => "CN",
680 
+            ipv4 => "True",
681 
+            ipv6 => "False",
682 
+            loadBalanced => "No",
683 
+            httpWebsiteMirror => "http://tor.shizhao.org/",
684 
+            httpsWebsiteMirror => "",
685 
+            rsyncWebsiteMirror => "",
686 
+            ftpWebsiteMirror => "",
687 
+            httpDistMirror => "http://tor.shizhao.org/dist/",
688 
+            httpsDistMirror => "",
689 
+            rsyncDistMirror => "",
690 
+            hiddenServiceMirror => "",
691 
+            updateDate => "Unknown",
692 
+        },
693 
+
694 
+	mirror036 => {
695 
+            adminContact => "",
696 
+            orgName => "ranyunfei",
697 
+            isoCC => "CN",
698 
+            subRegion => "",
699 
+            region => "CN",
700 
+            ipv4 => "True",
701 
+            ipv6 => "False",
702 
+            loadBalanced => "No",
703 
+            httpWebsiteMirror => "http://tor.ranyunfei.com/",
704 
+            httpsWebsiteMirror => "",
705 
+            rsyncWebsiteMirror => "",
706 
+            ftpWebsiteMirror => "",
707 
+            httpDistMirror => "http://tor.ranyunfei.com/dist/",
708 
+            httpsDistMirror => "",
709 
+            rsyncDistMirror => "",
710 
+            hiddenServiceMirror => "",
711 
+            updateDate => "Unknown",
712 
+        },
713 
+
714 
+	mirror037 => {
715 
+            adminContact => "",
716 
+            orgName => "wuerkaixi",
717 
+            isoCC => "CN",
718 
+            subRegion => "",
719 
+            region => "CN",
720 
+            ipv4 => "True",
721 
+            ipv6 => "False",
722 
+            loadBalanced => "No",
723 
+            httpWebsiteMirror => "http://tor.wuerkaixi.com/",
724 
+            httpsWebsiteMirror => "",
725 
+            rsyncWebsiteMirror => "",
726 
+            ftpWebsiteMirror => "",
727 
+            httpDistMirror => "http://tor.wuerkaixi.com/dist/",
728 
+            httpsDistMirror => "",
729 
+            rsyncDistMirror => "",
730 
+            hiddenServiceMirror => "",
731 
+            updateDate => "Unknown",
732 
+        },
733 
+
734 
+        mirror038 => {
735 
+            adminContact => "",
736 
+            orgName => "",
737 
+            isoCC => "IN",
738 
+            subRegion => "",
739 
+            region => "IN",
740 
+            ipv4 => "True",
741 
+            ipv6 => "False",
742 
+            loadBalanced => "No",
743 
+            httpWebsiteMirror => "http://www.torproject.org.in/",
744 
+            httpsWebsiteMirror => "",
745 
+            rsyncWebsiteMirror => "",
746 
+            ftpWebsiteMirror => "",
747 
+            httpDistMirror => "http://www.torproject.org.in/dist/",
748 
+            httpsDistMirror => "",
749 
+            rsyncDistMirror => "",
750 
+            hiddenServiceMirror => "",
751 
+            updateDate => "Unknown",
752 
+        },
753 
+
754 
+        mirror039 => {
755 
+            adminContact => "",
756 
+            orgName => "",
757 
+            isoCC => "AT",
758 
+            subRegion => "",
759 
+            region => "LU",
760 
+            ipv4 => "True",
761 
+            ipv6 => "False",
762 
+            loadBalanced => "No",
763 
+            httpWebsiteMirror => "http://tor.idnr.at/",
764 
+            httpsWebsiteMirror => "",
765 
+            rsyncWebsiteMirror => "",
766 
+            ftpWebsiteMirror => "",
767 
+            httpDistMirror => "http://tor.idnr.at/dist/",
768 
+            httpsDistMirror => "",
769 
+            rsyncDistMirror => "",
770 
+            hiddenServiceMirror => "",
771 
+        },
772 
+
773 
+        mirror040 => {
774 
+            adminContact => "",
775 
+            orgName => "NIIF Institute",
776 
+            isoCC => "HU",
777 
+            subRegion => "",
778 
+            region => "HU",
779 
+            ipv4 => "True",
780 
+            ipv6 => "False",
781 
+            loadBalanced => "No",
782 
+            httpWebsiteMirror => "http://trak.tor.hu/",
783 
+            httpsWebsiteMirror => "",
784 
+            rsyncWebsiteMirror => "",
785 
+            ftpWebsiteMirror => "",
786 
+            httpDistMirror => "http://trak.tor.hu/dist/",
787 
+            httpsDistMirror => "",
788 
+            rsyncDistMirror => "",
789 
+            hiddenServiceMirror => "",
790 
+        },
791 
+
792 
+        mirror041 => {
793 
+            adminContact => "sina at accessnow.org",
794 
+            orgName => "Access",
795 
+            isoCC => "IR",
796 
+            subRegion => "",
797 
+            region => "IR",
798 
+            ipv4 => "True",
799 
+            ipv6 => "False",
800 
+            loadBalanced => "Yes",
801 
+            httpWebsiteMirror => "http://irani-tor.ath.cx/",
802 
+            httpsWebsiteMirror => "",
803 
+            rsyncWebsiteMirror => "",
804 
+            ftpWebsiteMirror => "",
805 
+            httpDistMirror => "http://irani-tor.ath.cx/dist/",
806 
+            httpsDistMirror => "",
807 
+            rsyncDistMirror => "",
808 
+            hiddenServiceMirror => "",
809 
+        },
810 
+
811 
+        mirror042 => {
812 
+            adminContact => "kovtalex at mail.ru",
813 
+            orgName => "",
814 
+            isoCC => "RU",
815 
+            subRegion => "",
816 
+            region => "RU",
817 
+            ipv4 => "True",
818 
+            ipv6 => "False",
819 
+            loadBalanced => "No",
820 
+            httpWebsiteMirror => "http://www.tor.myeveryday.ru/",
821 
+            httpsWebsiteMirror => "",
822 
+            rsyncWebsiteMirror => "",
823 
+            ftpWebsiteMirror => "",
824 
+            httpDistMirror => "http://www.tor.myeveryday.ru/dist/",
825 
+            httpsDistMirror => "",
826 
+            rsyncDistMirror => "",
827 
+            hiddenServiceMirror => "",
828 
+        },
829 
+
830 
+        mirror043 => {
831 
+            adminContact => "",
832 
+            orgName => "",
833 
+            isoCC => "SE",
834 
+            subRegion => "",
835 
+            region => "SE",
836 
+            ipv4 => "True",
837 
+            ipv6 => "False",
838 
+            loadBalanced => "No",
839 
+            httpWebsiteMirror => "http://tor.homosu.net/",
840 
+            httpsWebsiteMirror => "",
841 
+            rsyncWebsiteMirror => "",
842 
+            ftpWebsiteMirror => "",
843 
+            httpDistMirror => "http://tor.homosu.net/dist",
844 
+            httpsDistMirror => "",
845 
+            rsyncDistMirror => "",
846 
+            hiddenServiceMirror => "",
847 
+        },
848 
+
849 
+        mirror044 => {
850 
+            adminContact => "margus.random at mail.ee",
851 
+            orgName => "CyberSIDE",
852 
+            isoCC => "EE",
853 
+            subRegion => "",
854 
+            region => "EE",
855 
+            ipv4 => "True",
856 
+            ipv6 => "False",
857 
+            loadBalanced => "No",
858 
+            httpWebsiteMirror => "http://cyberside.planet.ee/tor/",
859 
+            httpsWebsiteMirror => "",
860 
+            rsyncWebsiteMirror => "",
861 
+            ftpWebsiteMirror => "",
862 
+            httpDistMirror => "http://freedos.pri.ee/tor/",
863 
+            httpsDistMirror => "",
864 
+            rsyncDistMirror => "",
865 
+            hiddenServiceMirror => "",
866 
+        },
867 
+
868 
+        mirror045 => {
869 
+            adminContact => "me_ at tomyn dot com",
870 
+            orgName => "tomyn",
871 
+            isoCC => "UK",
872 
+            subRegion => "",
873 
+            region => "UK",
874 
+            ipv4 => "True",
875 
+            ipv6 => "False",
876 
+            loadBalanced => "No",
877 
+            httpWebsiteMirror => "http://tor.tomyn.com",
878 
+            httpsWebsiteMirror => "https://tor.tomyn.com",
879 
+            rsyncWebsiteMirror => "",
880 
+            ftpWebsiteMirror => "ftp://tor.tomyn.com",
881 
+            httpDistMirror => "http://tor.tomyn.com/dist",
882 
+            httpsDistMirror => "https://tor.tomyn.com/dist",
883 
+            rsyncDistMirror => "",
884 
+            hiddenServiceMirror => "",
885 
+        }
886 
+);
887 
+
888 
+my $count = values %m;
889 
+print "We have a total of $count mirrors\n";
890 
+print "Fetching the last updated date for each mirror.\n";
891 
+
892 
+my $tortime;
893 
+$tortime = FetchDate("http://www.torproject.org/");
894 
+# Adjust offical Tor time by out-of-date offset: number of days * seconds per day
895 
+$tortime -= 1 * 172800;
896 
+print "The official time for Tor is $tortime. \n";
897 
+
898 
+foreach my $server ( keys %m ) {
899 
+
900 
+    print "Attempting to fetch from $m{$server}{'orgName'}\n";
901 
+
902 
+    if ($m{$server}{'httpWebsiteMirror'}) {
903 
+        print "Attempt to fetch via HTTP.\n";
904 
+        $m{$server}{"updateDate"} = FetchDate("$m{$server}{'httpWebsiteMirror'}");
905 
+    } elsif ($m{$server}{'httpsWebsiteMirror'}) {
906 
+        print "Attempt to fetch via HTTPS.\n";
907 
+        $m{$server}{"updateDate"} = FetchDate("$m{$server}{'httpsWebsiteMirror'}");
908 
+    } elsif ($m{$server}{'ftpWebsiteMirror'}) {
909 
+        print "Attempt to fetch via FTP.\n";
910 
+        $m{$server}{"updateDate"} = FetchDate("$m{$server}{'ftpWebsiteMirror'}");
911 
+    } else {
912 
+        print "We were unable to fetch or store anything. We still have the following: $m{$server}{'updateDate'}\n";
913 
+    }
914 
+
915 
+    print "We fetched and stored the following: $m{$server}{'updateDate'}\n";
916 
+
917 
+ }
918 
+
919 
+
920 
+print "We sorted the following mirrors by their date of last update: \n";
921 
+foreach my $server ( sort { $m{$b}{'updateDate'} <=> $m{$a}{'updateDate'}} keys %m ) {
922 
+
923 
+     print "\n";
924 
+     print "Mirror $m{$server}{'orgName'}: \n";
925 
+
926 
+     foreach my $attrib ( sort keys %{$m{$server}} ) {
927 
+        print "$attrib = $m{$server}{$attrib}";
928 
+        print "\n";
929 
+     };
930 
+}
931 
+
932 
+my $outFile = "include/mirrors-table.wmi";
933 
+my $html;
934 
+open(OUT, "> $outFile") or die "Can't open $outFile: $!";
935 
+
936 
+# Here's where we open a file and print some wml include goodness
937 
+# This is storted from last known recent update to unknown update times
938 
+foreach my $server ( sort { $m{$b}{'updateDate'} <=> $m{$a}{'updateDate'}} keys %m ) {
939 
+
940 
+     my $time;
941 
+     if ( "$m{$server}{'updateDate'}" ne "Unknown") {
942 
+	  if ( $m{$server}{'updateDate'} > $tortime ) {
943 
+	    $time = "Up to date";
944 
+	  } else { $time = "Out of date"; }
945 
+     } else { $time = "Unknown"; }
946 
+print OUT <<"END";
947 
+     \n<tr>\n
948 
+         <td>$m{$server}{'isoCC'}</td>\n
949 
+         <td>$m{$server}{'orgName'}</td>\n
950 
+         <td>$time</td>\n
951 
+END
952 
+
953 
+     my %prettyNames = (
954 
+                        httpWebsiteMirror => "http",
955 
+                        httpsWebsiteMirror => "https",
956 
+                        ftpWebsiteMirror => "ftp",
957 
+                        rsyncWebsiteMirror => "rsync",
958 
+                        httpDistMirror => "http",
959 
+                        httpsDistMirror => "https",
960 
+                        rsyncDistMirrors => "rsync", );
961 
+
962 
+     foreach my $precious ( sort keys %prettyNames )
963 
+     {
964 
+        if ($m{$server}{"$precious"}) {
965 
+            print OUT "    <td><a href=\"" . $m{$server}{$precious} . "\">" .
966 
+                      "$prettyNames{$precious}</a></td>\n";
967 
+        } else { print OUT "    <td> - </td>\n"; }
968 
+     }
969 
+
970 
+     print OUT "</tr>\n";
971 
+}
972 
+
973 
+close(OUT);
wml2po.sh
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,260 @@
1 
+#!/bin/bash
2 
+#
3 
+# Author: Runa Sandvik, <runa.sandvik@gmail.com>
4 
+# Google Summer of Code 2009
5 
+#
6 
+# This is Free Software (GPLv3)
7 
+# http://www.gnu.org/licenses/gpl-3.0.txt
8 
+#
9 
+# This script will convert all of the english wml files to po files, and
10 
+# keep them updated. The script will also convert subdirectories that
11 
+# exist in the english website module.
12 
+#
13 
+# For more information, see the HOWTO and README in
14 
+# translation/tools/gsoc09.
15 
+#
16 
+
17 
+### start config ###
18 
+
19 
+# Location of the wml files
20 
+wmldir="$PWD"
21 
+
22 
+# Location of the po files.
23 
+# Assuming that the translation directory is relative to the website
24 
+podir="`dirname $wmldir`/translation/projects/website"
25 
+
26 
+# Set the copyright holder of the po files,
27 
+# for example "The Tor Project, Inc"
28 
+copyright="The Tor Project, Inc"
29 
+
30 
+# A lot of the wml files have custom tags. These tags have been defined
31 
+# in website/include/versions.wmi. Tags that people usually forget to close,
32 
+# as well as tags that are not defined in versions.wmi have been added.
33 
+# See: https://svn.torproject.org/svn/website/trunk/include/versions.wmi
34 
+customtag=`echo $(cat "$wmldir/include/versions.wmi" | awk '{ printf "<%s> " , $2 }' | sed 's/<>//g') "<svnsandbox> <svnwebsite> <svnprojects> <input> <hr> <br> <img> <gitblob> <version-android-components> <package-androidbundle-alpha> <package-androidbundle-alpha-sig>"`
35 
+
36 
+# We also need to use the nodefault option of po4a; space separated list
37 
+# of tags that the module should not try to set by default in any
38 
+# category. For now, we only need the input tag.
39 
+nodefault='<input>'
40 
+
41 
+# The script can write the name of unprocessed files to a log.
42 
+# If you want to enable this option, set the logfile here.
43 
+logfile=""
44 
+
45 
+# This is the temp logfile. Leave this line even if you don't want to
46 
+# log. This will be deleted when the script is done.
47 
+tmplog="`dirname $wmldir`/tmp.log"
48 
+
49 
+### end config ###
50 
+
51 
+# Create a lockfile to make sure that only one instance of the script
52 
+# can run at any time.
53 
+LOCKFILE=wml2po.lock
54 
+
55 
+if lockfile -! -l 60 -r 3 "$LOCKFILE";
56 
+then
57 
+	echo "unable to acquire lock" >2
58 
+	exit 1
59 
+fi
60 
+
61 
+trap "rm -f '$PWD/$LOCKFILE'" exit
62 
+
63 
+# Check if translation/projects/website exist, i.e. has been checked out
64 
+if [ ! -d $podir ]
65 
+then
66 
+	echo "Have you remembered to check out translation/projects/website?"
67 
+	exit 1
68 
+fi
69 
+
70 
+# If the logfile is set, write the date.
71 
+if [ $logfile ]
72 
+then
73 
+	echo `date` > $logfile
74 
+fi
75 
+
76 
+# Create the temp log
77 
+touch $tmplog
78 
+
79 
+# We need to find out which language directories we have.
80 
+# We also need to excluse the website module directory itself, as well
81 
+# as .svn
82 
+langdir=`find "$podir" -maxdepth 1 -type d ! -path "$podir" ! -path "$podir/templates" ! -path "*\.*" | sed "s#$podir/##"`
83 
+
84 
+# We only need the english wml files, but we do not wish to translate
85 
+# the eff documents.
86 
+wml=`find $wmldir -regex '^'$wmldir'/.*en/.*\.wml' -type f | grep -v '^'$wmldir'/eff'`
87 
+
88 
+# For every language directory, create and/or update the po files.
89 
+for lang in $langdir ; do
90 
+
91 
+	# For every english wml, see if the po needs to be created or
92 
+	# updated
93 
+	for file in $wml ; do
94 
+
95 
+		# Get the basename of the file we are dealing with
96 
+		wmlfile=`basename $file`
97 
+
98 
+		# Get the translation priority
99 
+		priority=`cat $file | grep "# Translation-Priority" | awk '{print $3}'`
100 
+
101 
+		# If the file doesn't have a translation-priority, we can assume
102 
+		# that it doesn't need to be translated. Skip this file and
103 
+		# continue on with the next.
104 
+		if [ ! $priority ]
105 
+		then
106 
+			continue
107 
+		fi
108 
+
109 
+		# Strip the file for its original extension and add .po
110 
+		pofile="$priority.${wmlfile%%.*}.po"
111 
+
112 
+		# Find out what directory the file is in.
113 
+		# Also, remove the parth of the path that is $wmldir
114 
+		indir=`dirname $file`
115 
+
116 
+		# We need to know what one dir up is
117 
+		onedirup=`dirname $indir | sed "s#$wmldir/##"`
118 
+
119 
+		# We need to have the correct, full path to the po
120 
+		# directory for the file we are working on.
121 
+		# Also, did the subdirectory exist prior to running this
122 
+		# script? If not, create it now and add it to the
123 
+		# repository.
124 
+		if [ $onedirup = $wmldir ]
125 
+		then
126 
+			popath="$podir/$lang"
127 
+		else
128 
+
129 
+			# We need to know if a subdirectory, such as torbutton,
130 
+			# exist in the translation module. If it does not exist,
131 
+			# the script will create it in all the directories under
132 
+			# translation/projects/website (excluding .svn)
133 
+			subdir=`find "$podir/$lang" -maxdepth 1 -type d	! -path "$ppodir/$lang" ! -path "*\.*"`
134 
+
135 
+			for dir in $subdir ; do
136 
+				if [ ! -d "$podir/$lang/$onedirup" ]
137 
+				then
138 
+					svn mkdir "$podir/$lang/$onedirup"
139 
+				fi
140 
+			done
141 
+
142 
+			# Set the path
143 
+			popath="$podir/$lang/$onedirup"
144 
+
145 
+		fi
146 
+
147 
+		# Check to see if the po existed prior to running this
148 
+		# script. If it didn't, check if there any files with the same
149 
+		# filename, but different priority. If neither of the files
150 
+		# exist, create with po4a-gettextize.
151 
+		if [ -e "$popath/$pofile" ]
152 
+		then
153 
+			poexist=1
154 
+		elif [ `find $popath -type f -name "*.$filename" | wc -l` -gt "0" ]
155 
+		then
156 
+			poexist=2
157 
+
158 
+		# We need to rename the other file
159 
+		for file in `find $popath -type f -name "*.$filename"` ; do
160 
+			svn mv "$file" "$popath/$pofile"
161 
+			echo "$popath/$pofile" > $tmplog
162 
+		done
163 
+
164 
+		else
165 
+			poexist=0
166 
+		fi
167 
+
168 
+		# If the po file does not exist, convert it with
169 
+		# po4a-gettextize, set the right encoding and charset
170 
+		# and the correct copyright.
171 
+		if [ $poexist = 0 ]
172 
+		then
173 
+			# Convert it
174 
+			po4a-gettextize -f wml -m "$file" -p "$popath/$pofile" --master-charset utf-8 -o customtag="$customtag" -o nodefault="$nodefault"
175 
+
176 
+			# Check to see if the file exists
177 
+			if [ -e "$popath/$pofile" ]
178 
+			then
179 
+				# We don't want files without
180 
+				# content, so check the file first.
181 
+				content=`cat "$popath/$pofile" | grep '^#[.]' | wc -l`
182 
+
183 
+				# If the file does not have any
184 
+				# content, delete it.
185 
+				if [ $content = 0 ]
186 
+				then
187 
+					rm -f "$popath/$pofile"
188 
+					echo "$popath/$pofile" > $tmplog
189 
+				else
190 
+					# Set the right encoding and charset, as well
191 
+					# as the correct copyright holder.
192 
+					sed -i '0,/ENCODING/ s/ENCODING/8bit/' "$popath/$pofile"
193 
+					sed -i '0,/CHARSET/ s/CHARSET/utf-8/' "$popath/$pofile"
194 
+					sed -i "0,/Free Software Foundation, Inc/ s/Free Software Foundation, Inc/$copyright/" "$popath/$pofile"
195 
+
196 
+					# And add it to the repository
197 
+					svn add "$popath/$pofile"
198 
+					echo "$popath/$pofile" > $tmplog
199 
+				fi
200 
+			fi
201 
+
202 
+			# Update the file with po4a-updatepo to make the
203 
+			# word wrapping perfect
204 
+			po4a-updatepo -f wml -m "$file" -p "$popath/$pofile" --master-charset utf-8 -o customtag="$customtag" -o nodefault="$nodefault"
205 
+
206 
+			# Delete the backup
207 
+			rm -f "$popath/$pofile~"
208 
+		fi
209 
+
210 
+		# If the po file does exist, calculate the hash first,
211 
+		# then update the file, then calculate the hash again.
212 
+		if [ $poexist = 1 ]
213 
+		then
214 
+			# Calculate the hash before we update the file
215 
+			before=`grep -vE '^("POT-Creation-Date:|#)' "$popath/$pofile" | md5sum | cut -d " " -f1`
216 
+
217 
+			# Update the po file
218 
+			po4a-updatepo -f wml -m "$file" -p "$popath/$pofile" --master-charset utf-8 -o customtag="$customtag" -o nodefault="$nodefault"
219 
+
220 
+			# Calculate the new hash
221 
+			after=`grep -vE '^("POT-Creation-Date:|#)' "$popath/$pofile" | md5sum | cut -d " " -f1`
222 
+
223 
+			# Delete the backup
224 
+			rm -f "$popath/$pofile~"
225 
+
226 
+			# Now we need to compare the before and after
227 
+			# hash. If they match (i.e. nothing has
228 
+			# changed), revert the file.
229 
+			if [ $before = $after ]
230 
+			then
231 
+				svn revert "$popath/$pofile"
232 
+				echo "$popath/$pofile" > $tmplog
233 
+			else
234 
+				echo "$popath/$pofile" > $tmplog
235 
+			fi
236 
+		fi
237 
+
238 
+		# If a file with the same name but different priority
239 
+		# exist, then rename the file (we have done so already)
240 
+		# and update it with po4a-updatepo to make sure
241 
+		# everything else is ok.
242 
+		if [ $poexist = 2 ]
243 
+		then
244 
+			# Update the file
245 
+			po4a-updatepo -f wml -m "$file" -p "$popath/$pofile" --master-charset utf-8 -o customtag="$customtag" -o nodefault="$nodefault"
246 
+		fi
247 
+
248 
+		# Write to the logfile
249 
+		if [ -e $logfile ]
250 
+		then
251 
+			if [ `cat $tmplog | grep "$popath/$pofile" | wc -l` -eq "0" ]
252 
+			then
253 
+				echo "could not process: " "$file" >> $logfile
254 
+			fi
255 
+		fi
256 
+
257 
+		# Delete the temp log
258 
+		rm -f $tmplog
259 
+	done
260 
+done
zh-cn/contact.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,55 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22359 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Contact" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor：联系方式</h2>
14 
+
15 
+<div class="underline"></div>
16 
+
17 
+<!-- BEGIN SIDEBAR -->
18 
+<div class="sidebar">
19 
+<h3>与新闻或媒体</h3>
20 
+<a href="<page press/index>">看看我们的新闻网页</a>
21 
+</div>
22 
+
23 
+<p>首先，如果你有一个使用 Tor 的问题或疑问， 去看看 <a href="<page documentation>#Support">支持章节</a>
24 
+页面得到解答。Tor 的开发者消耗了大量时间来开发 Tor，并没有人员致力于用户支持的人员，所以请在 <a href="<page
25 
+faq>#SupportMail">使用礼貌的方式找到志愿者</a>解答之前，最好试着自己解决问题。</p>
26 
+
27 
+<p>如果您真的需要联系我们，下面列举出了可以联系到我们的一些方法。其中，所有的地址都位于“@torproject.org”。注意，实际上大部分邮件最后都会由同样的一小群人来处理，所以请耐心的等待并且学会
28 
+<a
29 
+href="http://www.catb.org/~esr/faqs/smart-questions.html">聪明的提问方式</a>，或许这样更加有用。<strong>注意，请使用英文撰写您的邮件！</strong></p>
30 
+
31 
+<ul>
32 
+<li><tt>tor-assistants</tt>提供通用的帮助。如果你想问一个较明确的问题，请根据下列提示写信到相应的邮箱。</li>
33 
+<li><tt>tor-ops</tt> 可以联系到具有目录管理权限的人。如果您运行一台 Tor
34 
+中继并且对您的中继怀有疑问或者在使用中遇到了难题，您可以使用这个地址跟我们取得联系。</li>
35 
+<li><tt>tor-webmaster</tt> can fix typos on the website, change wrong statements
36 
+or directions on the website, and add new sections and paragraphs that you
37 
+send us. You might want to make a draft of your new sections on <a
38 
+href="https://trac.torproject.org/projects/tor/wiki">the Tor wiki</a> first.</li>
39 
+<li><tt>tor-volunteer</tt> 希望知道关于所有您从 <a href="<page volunteer>">志愿者页面</a>
40 
+上受到启发后完成的文档、补丁、测试、关于支持应用程序的经验等等信息（或者是其它您已经解决了的问题以及关于使用 Tor
41 
+的文档）。在您开始做某件事情之前，您没有必要发邮件通知我们 —— 像其它志愿者参加的 Internet
42 
+项目一样，很多一开始信心十足的人，到后来很快就销声匿迹了，所以我们更希望知道您的实际进展情况。</li>
43 
+<li><tt>tor-translation</tt> 接收新的 <a href="<page
44 
+translation>">网站翻译</a>，同时回答与已有的和新的翻译有关的问题。</li>
45 
+<li><tt>tordnsel</tt> 是 TorDNSEL 负责人的邮箱别名。</li>
46 
+<li><tt>donations</tt> 是用来发表所有关于 <a href="<page donate>">为开发者捐助</a>
47 
+相关意见和问题的邮件地址。更多的捐助意味着 <a href="<page faq>#Funding">更好的
48 
+Tor</a>。我们很高兴的考虑您为捐助提出的富有创意的方法。</li>
49 
+<li><tt>execdir</tt> 聆听与非盈利组织 Tor 有关的新闻/媒体、问题和评论：商标问题，加入与协调，重大的捐赠，合同询问，许可和证明，等等。</li>
50 
+</ul>
51 
+
52 
+  </div>
53 
+
54 
+
55 
+#include <foot.wmi>
zh-cn/mirrors.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,46 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 21511 $
9 
+# Translation-Priority: 3-low
10 
+#include "head.wmi" TITLE="Tor: Mirrors" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<h2>Tor：镜像</h2>
14 
+<hr />
15 
+
16 
+<p>
17 
+本网站的 URL 是 <a
18 
+href="https://www.torproject.org/">https://www.torproject.org/</a>，但是在其他地方有本站的几个镜像网站。
19 
+</p>
20 
+
21 
+<p>
22 
+如果你想运行一个镜像，请 <a href="<page docs/running-a-mirror>">阅读运行镜像的指导</a>。
23 
+</p>
24 
+
25 
+<table class="mirrors">
26 
+<tr>
27 
+  <th>国家</th>
28 
+  <th>组织</th>
29 
+  <th>状态</th>
30 
+  <th>FTP</th>
31 
+  <th>http dist/</th>
32 
+  <th>http 网站</th>
33 
+  <th>https dist/</th>
34 
+  <th>https 网站</th>
35 
+  <th>rsync dist/</th>
36 
+  <th>rsync 网站</th>
37 
+</tr>
38 
+
39 
+<!--PO4ASHARPBEGINinclude <mirrors-table.wmi>
40 
+PO4ASHARPEND-->
41 
+</table>
42 
+
43 
+  </div>
44 
+
45 
+
46 
+#include <foot.wmi>
zh-cn/overview.wml
Zeige Datei @ 2a9aaa802
... ... 
@@ -0,0 +1,168 @@
1 
+
2 
+
3 
+
4 
+
5 
+
6 
+
7 
+## translation metadata
8 
+# Revision: $Revision: 22308 $
9 
+# Translation-Priority: 2-medium
10 
+#include "head.wmi" TITLE="Tor: Overview" CHARSET="UTF-8"
11 
+<div class="main-column">
12 
+
13 
+<a name="overview"></a>
14 
+<h2><a class="anchor" href="#overview">Tor：概述</a></h2>
15 
+
16 
+<!-- BEGIN SIDEBAR -->
17 
+<div class="sidebar-left">
18 
+<h3>主题</h3>
19 
+<ul>
20 
+<li><a href="<page overview>#overview">概述</a></li>
21 
+<li><a href="<page overview>#whyweneedtor">我们为什么需要 Tor</a></li>
22 
+<li><a href="<page overview>#thesolution">解决方案</a></li>
23 
+<li><a href="<page overview>#hiddenservices">隐匿服务</a></li>
24 
+<li><a href="<page overview>#stayinganonymous">保持匿名</a></li>
25 
+<li><a href="<page overview>#thefutureoftor">Tor 的未来</a></li>
26 
+</ul>
27 
+</div>
28 
+
29 
+
30 
+<!-- END SIDEBAR -->
31 
+<hr />
32 
+
33 
+<p>
34 
+Tor 是一个由虚拟通道组成的网络使人们和团体来提高自己在互联网上的隐私和安全。同时它使软件开发人员能够创建具有内建隐私保护特性的新的通信工具。Tor
35 
+为一系列应用的基础，使组织和个人在公共网络上分享信息而不必担心隐私受到威胁。
36 
+</p>
37 
+
38 
+<p>
39 
+Individuals use Tor to keep websites from tracking them and their family
40 
+members, or to connect to news sites, instant messaging services, or the
41 
+like when these are blocked by their local Internet providers.  Tor's <a
42 
+href="<page hidden-services>">hidden services</a> let users publish web
43 
+sites and other services without needing to reveal the location of the
44 
+site. Individuals also use Tor for socially sensitive communication: chat
45 
+rooms and web forums for rape and abuse survivors, or people with illnesses.
46 
+</p>
47 
+
48 
+<p>
49 
+记者使用 Tor 与告密者和持不同政见者更安全地交流。非政府组织（NGOs）也在使用
50 
+Tor，当工作人员在国外时，他们可以连接自己的网站，而周围的人对他们的工作却一无所知。
51 
+</p>
52 
+
53 
+<p>
54 
+独立媒体中心（Indymedia）之类的团体建议使用 Tor 来保护成员的在线隐私和安全。电子前沿基金会（EFF）之类的社会活动团体建议将 Tor
55 
+作为维护公民在线自由的一种机制。公司使用 Tor
56 
+安全地从事竞争力分析，或者确保敏感的采购模式不被泄露。他们还用它来替代传统的虚拟专用网络（VPNs），后者会泄露精确的通信量和通信时间：最近员工在什么地点工作？在什么地点有员工访问求职网站？哪些研究分支在和公司的专利律师交流？
57 
+</p>
58 
+
59 
+<p>
60 
+美国海军的一个分支使用 Tor 实验开源的情报收集，它的一个小组最近在中东部署的时候也使用了 Tor。执法人员使用
61 
+Tor，一方面为了在访问和监视网站时不在网站的日志中留下政府部门的 IP 地址，另一方面为了特情引诱（sting operations）的安全。
62 
+</p>
63 
+
64 
+<p>
65 
+Tor 的用户的多样性正是 <a
66 
+href="http://freehaven.net/doc/fc03/econymics.pdf">使之如此安全的部分原因</a>。Tor 把你隐藏在
67 
+<a href="<page torusers>">网络上的其他用户</a> 之中，所以 Tor 的用户群越发庞大和复杂，你的匿名性就会得到越好的保护。
68 
+</p>
69 
+
70 
+<a name="whyweneedtor"></a>
71 
+<h3><a class="anchor" href="#whyweneedtor">我们为什么需要 Tor</a></h3>
72 
+
73 
+<p>
74 
+使用 Tor 能抵御一种普遍的网络监视行为——“流量分析”（traffic
75 
+analysis）。流量分析可以用来在一个公共的网络上推断出谁在和谁交流。如果他人知道了你的网络流量的来源和目的地，他们就可以跟踪你的行为和兴趣。这会影响你的钱包，举个例子，电子商务网站可能会针对不同的国家和机构制定不同的价格。泄露你的身份和地点甚至会威胁你的工作和人身安全。举个例子，如果你在国外连接到你的雇主的电脑去接收和发送邮件，你就会在不经意间向任何监视网络的人泄露了你的国籍和职业——即使连接是加密的也没有用。
76 
+</p>
77 
+
78 
+<p>
79 
+流量分析的原理是什么？互联网上的数据包由两部分组成：数据有效载荷（data
80 
+payload）和用来路由的报头（header）。有效载荷是正在发送的数据，它可能是一封邮件、一张网页或是一个音频文件。即便你加密通信中的有效载荷，流量分析一样能够揭露许多你在做的事，甚至有可能揭露你在说些什么。那是因为它所分析的是报头，报头记录着来源、目的地、数据大小、时间等等信息。
81 
+</p>
82 
+
83 
+<p>
84 
+对于一个隐私意识强的人，一个基本问题是：通信的对方可以从报头得到有用的东西，授权的中间媒介（比如
85 
+ISP），有时甚至未授权的中间媒介，也可以这么做。一个非常简单的流量分析的形式是：藏身于网络上发送者和接收者之间的某个地方，偷看报头。
86 
+</p>
87 
+
88 
+<p>
89 
+但是，更强大的流量分析同样存在。一些攻击者暗中监视互联网的多个部分，使用高深的统计技术跟踪许多不同的组织和个人的通信模式。加密并不能抵御这些攻击者，因为加密隐藏的仅仅是流量的内容，而不是报头。
90 
+</p>
91 
+
92 
+<a name="thesolution"></a>
93 
+<h3><a class="anchor" href="#thesolution">解决方案：一个分布式的、匿名的网络</a></h3>
94 
+
95 
+<p>
96 
+Tor 有助于降低简单的和高级的流量分析的风险，Tor
97 
+把你的流量分散到互联网上的多个地点，所以不存在单一的一点可以把你和你的目的地联系起来。这就好像用一条拐弯抹角的、难以辨认的路径甩掉跟踪你的人，然后定期擦掉你的脚印。在
98 
+Tor
99 
+网络上，来源和目的地不是用一条路径直接连接的，而是由一条通过数台中继的随机路径覆盖原始路径，数据包在这条路径上传输，因此，不存在任何单一一点上的观察者能够知道数据从哪里来、到哪里去。
100 
+</p>
101 
+
102 
+<p><img alt="Tor circuit step one" src="$(IMGROOT)/htw1.png" /></p>
103 
+
104 
+<p>
105 
+用 Tor
106 
+创建一条私有网络路径时，用户的软件或客户端通过网络上的中继递增地建立一条由若干加密连接组成的环路（circuit）。环路一次扩展一跳（hop），环路上的中继仅仅知道它从哪一个中继接收数据以及向哪一个中继发送数据。没有一台单独的中继会知道数据包的完整路径。客户端与环路上的每一跳都协商一组独立的密钥，这样可以保证数据通过任何一跳时都无法跟踪。
107 
+</p>
108 
+
109 
+<p><img alt="Tor circuit step two" src="$(IMGROOT)/htw2.png" /></p>
110 
+
111 
+<p>
112 
+一旦环路建立完成，多种类型的数据可以在上面进行交换，不同种类的应用程序也可以在 Tor
113 
+网络上部署。因为每一台中继最多只能知道环路中的一跳，窃听者或者被入侵的中继都无法通过流量分析把连接的来源和目的地联系起来。Tor 仅作用于 TCP
114 
+数据流，任何支持 SOCKS 的应用程序都可以使用它。
115 
+</p>
116 
+
117 
+<p>
118 
+为了提高效率，Tor 为大约在相同的十分钟内发起的连接请求分配同一环路。以后的请求被分配不同的环路，这样他人就不能把你早先的行为和新的行为联系起来。
119 
+</p>
120 
+
121 
+<p><img alt="Tor circuit step three" src="$(IMGROOT)/htw3.png" /></p>
122 
+
123 
+
124 
+<a name="hiddenservices"></a>
125 
+<h3><a class="anchor" href="#hiddenservices">隐匿服务</a></h3>
126 
+
127 
+<p>
128 
+Tor 同样使得用户能够在隐藏自身位置的前提下提供各类服务，例如 Web 发布和及时通讯服务器。其他 Tor 用户使用 Tor
129 
+的“聚合点”（rendezvous points）连接到这些隐匿服务，互相都不知道对方的网络标识。Tor
130 
+用户能够使用这项隐匿服务功能建立网站，人们在网站上发布资料而不用担心遭到审查。没人能够确认到底是谁在运行网站，网站的运行者也不知道到底是谁发布了资料。了解更多有关
131 
+<a href="<page docs/tor-hidden-service>">配置隐匿服务</a> 的信息以及 <a href="<page
132 
+hidden-services>">隐匿服务协议</a> 的原理。
133 
+</p>
134 
+
135 
+<a name="stayinganonymous"></a>
136 
+<h3><a class="anchor" href="#stayinganonymous">保持匿名</a></h3>
137 
+
138 
+<p>
139 
+Tor 并不能解决所有匿名问题。它所关注的仅仅是保护数据的传输。如果你不想让你所访问的网站知道你的身份信息，你需要使用支持特定协议的软件。比如，浏览
140 
+Web 时你可以使用 Privoxy 之类的 Web 代理软件阻挡 cookies，隐藏浏览器的类型。
141 
+</p>
142 
+
143 
+<p>
144 
+同样，在保护匿名时要学得聪明些。不要在 Web 表单里输入你的名字和其他会泄露身份的信息。要知道，和其他速度快到可以进行 Web
145 
+浏览的匿名网络一样，Tor对于端到端的计时攻击（end-to-end timing
146 
+attacks）不提供保护：如果攻击者知道出自你电脑的流量，也知道到达你所选目的地的流量，他就可以使用统计分析发现它们是同一环路的一部分。
147 
+</p>
148 
+
149 
+<a name="thefutureoftor"></a>
150 
+<h3><a class="anchor" href="#thefutureoftor">Tor 的未来</a></h3>
151 
+
152 
+<p>
153 
+今天，在互联网上提供一个可用的匿名网络是一项持续的挑战。我们希望软件能满足用户的需求。我们也需要网络以一种支持尽可能多的用户的方式运行。安全性和可用性并非互相矛盾：随着
154 
+Tor
155 
+的可用性的增加，它会吸引更多的用户，用户的增加提高了每次通信的来源与目的地的可能性，从而增强了每个人的安全性。我们在进步，但我们需要你的帮助。请考虑
156 
+<a href="<page docs/tor-doc-relay>">运行中继</a> 或者 <a href="<page
157 
+volunteer>">志愿</a> 作一名 <a href="<page documentation>#Developers">开发者</a>。
158 
+</p>
159 
+
160 
+<p>
161 
+法律、政策和技术的当前趋势以前所未有的程度威胁着匿名，破坏着我们在线言论与阅读的自由。这些趋势也使得个人、组织、公司、政府间的通信更易分析，削弱了国家和关键基础设施的安全。每一个新的用户、每一台新的中继都会增加网络的多样性，Tor
162 
+由此更能帮助你把安全和隐私的控制权重新掌握在自己手中。
163 
+</p>
164 
+
165 
+  </div>
166 
+
167 
+
168 
+#include <foot.wmi>
0 169