add a step to tor-doc-server on backing up your identity key.
Roger Dingledine

Roger Dingledine commited on 2006-04-09 07:50:57
Zeige 6 geänderte Dateien mit 35 Einfügungen und 25 Löschungen.


and start pointing to the v2 directory network-status when telling
people to "see if they're in the directory".

also change the blurb at the base of each page to point to the
contact page.

... ...
@@ -242,9 +242,8 @@ guide.</p>
242 242
 
243 243
 <hr />
244 244
 
245
-<p>If you have suggestions for improving this document, please post
246
-them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
247
-website category. Thanks!</p>
245
+<p>If you have suggestions for improving this document, please <a
246
+href="<page contact>">send them to us</a>. Thanks!</p>
248 247
 
249 248
   </div><!-- #main -->
250 249
 </div>
... ...
@@ -147,7 +147,7 @@ where new development releases are announced.
147 147
 The <a href="<page tor-manual>">manual</a> for the
148 148
 latest stable version provides detailed instructions for how to install
149 149
 and use Tor, including configuration of client and server options.
150
-If you are running the CVS version the manual is available
150
+If you are running the development version of Tor the manual is available
151 151
 <a href="<page tor-manual-cvs>">here</a>.
152 152
 </p>
153 153
 
... ...
@@ -172,7 +172,8 @@ testing the IP and port you think it should be testing, etc.
172 172
 <p>When it decides that it's reachable, it will upload a "server
173 173
 descriptor" to the directories. This will let clients know
174 174
 what address, ports, keys, etc your server is using. You can <a
175
-href="http://belegost.seul.org/">load the directory manually</a> and
175
+href="http://belegost.mit.edu/tor/status/authority">load the network
176
+status manually</a> and
176 177
 look through it to find the nickname you configured, to make sure it's
177 178
 there. You may need to wait a few seconds to give enough time for it to
178 179
 make a fresh directory.</p>
... ...
@@ -237,14 +238,23 @@ limiting FAQ entry</a> for details.
237 238
 </p>
238 239
 
239 240
 <p>
240
-8. If you control the name servers for your domain, consider setting
241
+8. Back up your Tor server's private key (stored in "keys/secret_id_key"
242
+in your DataDirectory). This is your server's "identity," and
243
+you need to keep it safe so nobody can read the traffic that goes
244
+through your server. This is the critical file to keep if you need to <a
245
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#UpgradeServer">move
246
+or restore your Tor server</a> if something goes wrong.
247
+</p>
248
+
249
+<p>
250
+9. If you control the name servers for your domain, consider setting
241 251
 your hostname to 'anonymous' or 'proxy' or 'tor-proxy', so when other
242 252
 people see the address in their web logs, they will more quickly
243 253
 understand what's going on.
244 254
 </p>
245 255
 
246 256
 <p>
247
-9. If your computer isn't running a webserver, please consider
257
+10. If your computer isn't running a webserver, please consider
248 258
 changing your ORPort to 443 and your DirPort to 80. Many Tor
249 259
 users are stuck behind firewalls that only let them browse the
250 260
 web, and this change will let them reach your Tor server. Win32
... ...
@@ -259,7 +269,7 @@ ports are 22, 110, and 143.
259 269
 </p>
260 270
 
261 271
 <p>
262
-10. If your Tor server provides other services on the same IP address
272
+11. If your Tor server provides other services on the same IP address
263 273
 &mdash; such as a public webserver &mdash; make sure that connections to the
264 274
 webserver are allowed from the local host too. You need to allow these
265 275
 connections because Tor clients will detect that your Tor server is the <a
... ...
@@ -270,7 +280,7 @@ explicitly reject them in your exit policy.
270 280
 </p>
271 281
 
272 282
 <p>
273
-11. (Unix only). Make a separate user to run the server. If you
283
+12. (Unix only). Make a separate user to run the server. If you
274 284
 installed the OS X package or the deb or the rpm, this is already
275 285
 done. Otherwise, you can do it by hand. (The Tor server doesn't need to
276 286
 be run as root, so it's good practice to not run it as root. Running
... ...
@@ -281,7 +291,7 @@ into a chroot jail</a>.)
281 291
 </p>
282 292
 
283 293
 <p>
284
-12. (Unix only.) Your operating system probably limits the number
294
+13. (Unix only.) Your operating system probably limits the number
285 295
 of open file descriptors per process to 1024 (or even less). If you
286 296
 plan to be running a fast exit node, this is probably not enough. On
287 297
 Linux, you should add a line like "toruser hard nofile 8192" to your
... ...
@@ -294,20 +304,23 @@ you launch Tor.
294 304
 </p>
295 305
 
296 306
 <p>
297
-13. If you installed Tor via some package or installer, it probably starts
307
+14. If you installed Tor via some package or installer, it probably starts
298 308
 Tor for you automatically on boot. But if you installed from source,
299 309
 you may find the initscripts in contrib/tor.sh or contrib/torctl useful.
300 310
 </p>
301 311
 
302
-When you change your Tor configuration, be sure to restart Tor, and
303
-remember to verify that your server still works correctly after the
304
-change.
312
+<p>
313
+When you change your Tor configuration, <a
314
+href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#Restarting">in
315
+most cases you can reload your configuration without restarting Tor</a>,
316
+and remember to verify that your server still works correctly after
317
+the change.
318
+</p>
305 319
 
306 320
 <hr />
307 321
 
308
-<p>If you have suggestions for improving this document, please post
309
-them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
310
-website category. Thanks!</p>
322
+<p>If you have suggestions for improving this document, please <a
323
+href="<page contact>">send them to us</a>. Thanks!</p>
311 324
 
312 325
   </div><!-- #main -->
313 326
 </div>
... ...
@@ -187,9 +187,8 @@ guide.</p>
187 187
 
188 188
 <hr />
189 189
 
190
-<p>If you have suggestions for improving this document, please post
191
-them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
192
-website category. Thanks!</p>
190
+<p>If you have suggestions for improving this document, please <a
191
+href="<page contact>">send them to us</a>. Thanks!</p>
193 192
 
194 193
   </div><!-- #main -->
195 194
 </div>
... ...
@@ -185,9 +185,8 @@ guide.</p>
185 185
 
186 186
 <hr />
187 187
 
188
-<p>If you have suggestions for improving this document, please post
189
-them on <a href="http://bugs.noreply.org/tor">our bugtracker</a> in the
190
-website category. Thanks!</p>
188
+<p>If you have suggestions for improving this document, please <a
189
+href="<page contact>">send them to us</a>. Thanks!</p>
191 190
 
192 191
   </div><!-- #main -->
193 192
 </div>
... ...
@@ -267,7 +267,7 @@ won't be either. This leaks information to an observant adversary.</li>
267 267
 <hr />
268 268
 
269 269
 <p>If you have suggestions for improving this document, please <a
270
-href="/contact">send them to us</a>. Thanks!</p>
270
+href="<page contact>">send them to us</a>. Thanks!</p>
271 271
 
272 272
   </div><!-- #main -->
273 273
 </div>
... ...
@@ -159,7 +159,7 @@ Preferences" menu.)</p>
159 159
 <hr />
160 160
 
161 161
 <p>If you have suggestions for improving this document, please <a
162
-href="/contact">send them to us</a>. Thanks!</p>
162
+href="<page contact>">send them to us</a>. Thanks!</p>
163 163
 
164 164
   </div><!-- #main -->
165 165
 </div>
166 166