Browse code

Update bridge docu to not recommend port 443 anymore

This aids scanning resistance as per ticket #13996

Sebastian Hahn authored on 24/04/2015 10:27:13
Showing 1 changed files
... ...
@@ -281,7 +281,7 @@
281 281
     the bridges.  Almost instantly, you'll receive a reply that includes:
282 282
     </p>
283 283
     <pre>
284
-    Here are your bridge:
284
+    Here are your bridges:
285 285
 
286 286
      60.16.182.53:9001
287 287
      87.237.118.139:444
... ...
@@ -323,19 +323,13 @@
323 323
     your torrc file</a> to be just these four lines:<br>
324 324
     <pre><code>
325 325
     SocksPort 0
326
-    ORPort 443
326
+    ORPort auto
327 327
     BridgeRelay 1
328 328
     Exitpolicy reject *:*
329 329
     </code></pre></li>
330 330
     </ul>
331 331
     </p>
332 332
 
333
-    <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors
334
-    on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a
335
-    href="<page docs/faq>#HowcanImakemyrelayaccessibletopeoplestuckbehindrestrictivefirewalls">some
336
-    complex port forwarding</a>.
337
-    </p>
338
-
339 333
     <p>
340 334
     When configured as a bridge, your server will <b>not</b> appear in the public
341 335
     Tor network.