clean up osx/win32/generic instructions (ffa1008c) · Commits · Legacy / gitolite / user / hiviah / rpm-tor

doc/tor-doc-osx.html

+12 −12

Changes for doc/tor-doc-osx.html: 12 added lines, 12 removed lines.
Original line number	Diff line number	Diff line
		@@ -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>

		<p>In Mozilla, this is in Mozilla\|Preferences\|Advanced\|Proxies.
		In Firefox it's Firefox\|Preferences\|General\|ConnectionSettings</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>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>

doc/tor-doc-win32.html

+6 −4

Changes for doc/tor-doc-win32.html: 6 added lines, 4 removed lines.
Original line number	Diff line number	Diff line
		@@ -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>

doc/tor-doc.html

+5 −3

Changes for doc/tor-doc.html: 5 added lines, 3 removed lines.
Original line number	Diff line number	Diff line
		@@ -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. -->