From 225510f58ac44097fa59de183e477f44152696b2 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Sat, 24 Sep 2005 08:36:47 +0000 Subject: mention the new stable version. and explicitly mention that selinux on FC4 is a problem for tor. svn:r5136 --- doc/tor-doc-unix.html | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) (limited to 'doc/tor-doc-unix.html') diff --git a/doc/tor-doc-unix.html b/doc/tor-doc-unix.html index adb6ead86c..516077b005 100644 --- a/doc/tor-doc-unix.html +++ b/doc/tor-doc-unix.html @@ -62,8 +62,8 @@ Red Hat, Gentoo, *BSD, etc there too.

If you're building from source, first install libevent, and make sure you have openssl and zlib (including the -devel packages if -applicable). Then Run tar xzf tor-0.1.0.14.tar.gz; -cd tor-0.1.0.14. Then ./configure && make. Now you +applicable). Then Run tar xzf tor-0.1.0.15.tar.gz; +cd tor-0.1.0.15. Then ./configure && make. Now you can run tor as src/or/tor, or you can run make install (as root if necessary) to install it into /usr/local/, and then you can start it just by running tor. @@ -174,8 +174,10 @@ to Privoxy, and 4) see whether your IP address has changed.

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 +ability to connect to itself (this includes something like SELinux on +Fedora Core 4), be sure to allow connections from +your local applications to Privoxy (local port 8118) and Tor (local port +9050). If your firewall blocks outgoing connections, punch a hole so it can connect to at least TCP ports 80 and 443, and then see this -- cgit v1.2.3-54-g00ecf