commit 68fc46d8459f40b323306527fb7f166a04629dda Author: Sebastian Hahn sebastian@torproject.org Date: Fri Apr 24 10:27:13 2015 +0200

Update bridge docu to not recommend port 443 anymore

This aids scanning resistance as per ticket #13996 --- docs/en/bridges.wml | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-)

diff --git a/docs/en/bridges.wml b/docs/en/bridges.wml index 7403235..6a82cc1 100644 --- a/docs/en/bridges.wml +++ b/docs/en/bridges.wml @@ -281,7 +281,7 @@ the bridges. Almost instantly, you'll receive a reply that includes: </p> <pre> - Here are your bridge: + Here are your bridges:

60.16.182.53:9001 87.237.118.139:444 @@ -323,19 +323,13 @@ your torrc file</a> to be just these four lines:<br> <pre><code> SocksPort 0 - ORPort 443 + ORPort auto BridgeRelay 1 Exitpolicy reject *:* </code></pre></li> </ul> </p>

- <p>If you get "Could not bind to 0.0.0.0:443: Permission denied" errors - on startup, you'll need to pick a higher ORPort (e.g. 8080) or do <a - href="<page docs/faq>#HowcanImakemyrelayaccessibletopeoplestuckbehindrestrictivefirewalls">some - complex port forwarding</a>. - </p> - <p> When configured as a bridge, your server will <b>not</b> appear in the public Tor network.