Author: arma Date: 2011-09-27 09:42:40 +0000 (Tue, 27 Sep 2011) New Revision: 25122 Modified: website/trunk/docs/en/faq.wml Log: every time you talk about SOCKS you have to yell Modified: website/trunk/docs/en/faq.wml =================================================================== --- website/trunk/docs/en/faq.wml 2011-09-27 09:39:10 UTC (rev 25121) +++ website/trunk/docs/en/faq.wml 2011-09-27 09:42:40 UTC (rev 25122) @@ -752,7 +752,7 @@ href="https://trac.torproject.org/projects/tor/ticket/3948">working on a feature</a> where Tor will try the usual ports first and then back off to a random choice if they're already in use. Until then, if you -want to configure some other application to use Tor as a socks proxy, +want to configure some other application to use Tor as a SOCKS proxy, here's a workaround: </p> @@ -778,7 +778,7 @@ <p> If you are trying to use some external application with Tor, step zero -should be to <a href="<page download/download>#warning">read the set +should be to <a href="<page download/download>#warning">reread the set of warnings</a> for ways you can screw up. Step one should be to try to use a SOCKS proxy rather than an http proxy — Tor runs a SOCKS proxy on port 9050 on Windows, or <a href="#TBBSocksPort">see above</a>