mirrors/tor
1
0
Fork 0
mirror of https://gitlab.torproject.org/tpo/core/tor.git synced 2025-02-20 13:34:51 +01:00
Code Issues Projects Releases Wiki Activity

clean up osx/win32/generic instructions

Browse source 
svn:r3309
This commit is contained in:
Roger Dingledine 2005-01-05 14:25:53 +00:00
parent a6e587305f
commit ffa1008c3a
3 changed files with 23 additions and 19 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

24
doc/tor-doc-osx.html
View file

@ -71,16 +71,14 @@ configuration for Tor has been installed as part of the installer package.
<p>After installing Tor, you need to configure your applications to use
it. The first step is to set up web browsing.
Change your browser to HTTP proxy at localhost port 8118.
(That's where Privoxy listens.) For Safari you need to change your
Network Settings. Other web browers allow you to change proxy settings
individually.</p>
(That's where Privoxy listens.)
In Mozilla, this is in Mozilla|Preferences|Advanced|Proxies.
In Firefox it's Firefox|Preferences|General|ConnectionSettings.
You should set both your Web Proxy (HTTP) and your Secure Web Proxy
(HTTPS or SSL) to localhost port 8118, to hide your SSL traffic too.
<p>In Mozilla, this is in Mozilla|Preferences|Advanced|Proxies.
In Firefox it's Firefox|Preferences|General|ConnectionSettings</p>
<P>You should set both your Web Proxy (HTTP) and your Secure Web Proxy
(HTTPS) to the same thing, to hide your SSL traffic. For Safari, this
looks something like:</p>
<p>If you want to use Tor with Safari, you need to change your
Network Settings. The process looks something like:</p>
<img alt="LAN settings in IE"
src="http://tor.eff.org/img/screenshot-osx-choose-network.png"
@ -118,9 +116,11 @@ what IP it says you're coming from. (If it's down, you can try the
site instead.)</p>
<p>
If you have a personal firewall, be sure to allow local connections to
port 8118 and port 9050. If your firewall blocks outgoing connections,
punch a hole so it can connect to TCP ports 80, 443, and 9001-9033.
If you have a personal firewall that limits your computer's ability
to connect to itself, be sure to allow connections from your local
applications to
local port 8118 and port 9050. If your firewall blocks outgoing connections,
punch a hole so it can connect to at least TCP ports 80, 443, and 9001-9033.
For more troubleshooting suggestions, see <a
href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ">the FAQ</a>.
</p>

10
doc/tor-doc-win32.html
View file

@ -91,7 +91,7 @@ src="http://tor.eff.org/img/screenshot-win32-privoxy-edit.jpg" />
In Mozilla, this is in Edit|Preferences|Advanced|Proxies. In IE, it's
Tools|Internet Options|Connections|LAN Settings|Advanced.
You should also set your SSL proxy (IE calls it "Secure") to the same
thing, to hide your SSL traffic. In IE, this looks something like:</p>
thing, to hide your SSL traffic too. In IE, this looks something like:</p>
<img alt="LAN settings in IE"
src="http://tor.eff.org/img/screenshot-win32-ie-lan.jpg" />
@ -111,9 +111,11 @@ what IP it says you're coming from. (If it's down, you can try the
site instead.)</p>
<p>
If you have a personal firewall, be sure to allow local connections to
port 8118 and port 9050. If your firewall blocks outgoing connections,
punch a hole so it can connect to TCP ports 80, 443, and 9001-9033.
If you have a personal firewall that limits your computer's ability
to connect to itself, be sure to allow connections from your local
applications to
local port 8118 and port 9050. If your firewall blocks outgoing connections,
punch a hole so it can connect to at least TCP ports 80, 443, and 9001-9033.
For more troubleshooting suggestions, see <a
href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ">the FAQ</a>.
</p>

8
doc/tor-doc.html
View file

@ -202,9 +202,11 @@ what IP it says you're coming from. (If it's down, you can try the
site instead.)</p>
<p>
If you have a personal firewall, be sure to allow local connections to
port 8118 and port 9050. If your firewall blocks outgoing connections,
punch a hole so it can connect to TCP ports 80, 443, and 9001-9033.
If you have a personal firewall that limits your computer's ability
to connect to itself, be sure to allow connections from your local
applications to
local port 8118 and port 9050. If your firewall blocks outgoing connections,
punch a hole so it can connect to at least TCP ports 80, 443, and 9001-9033.
<!--If you're
using Safari as your browser, keep in mind that OS X before 10.3 claims
to support SOCKS but does not. -->