Originally Posted by
Dr. Nick
just try and start tor and privoxy without the /etc/init.d, Just run "tor" and "privoxy" from a terminal and see what happens
Yes, I added that line, and yes I was running nmap from the same machine that I installed Tor and Privoxy on (this one).
Code:
# Sample Configuration File for Privoxy
#
# Copyright (C) 2001-2004 Privoxy Developers http://privoxy.org
#
# $Id: config,v $
#
# Added for Tor support
forward-socks4a / localhost:9050 .
Running on their own I get this:
Code:
$ sudo tor
Dec 02 08:58:49.920 [notice] Tor v0.1.0.15. This is experimental software. Do not rely on it for strong anonymity.
Dec 02 08:58:49.977 [warn] /var/lib/tor is not owned by this UID (0). You must fix this to proceed.
Dec 02 08:58:49.977 [err] options_act(): Couldn't access/create private data directory /var/lib/tor
Dec 02 08:58:49.978 [err] init_from_config(): Acting on config options left us in a broken state. Dying.
$ sudo privoxy
Dec 02 08:59:03 Privoxy(b7d606c0) Fatal error: can't check configuration file '/{$PWD}/config': No such file or directory
Dec 02 08:59:03 Privoxy(b7d606c0) Fatal error: can't check configuration file '/{$PWD}/config': No such file or directory
$
I filled in {$PWD}, but basically it would just look for the config file anywhere that I tried to run it from.
Running 'ps aux' I see that they run as the following:
Tor - /usr/sbin/tor
Privoxy - /usr/sbin/privoxy --pidfile /var/run/privoxy.pid --user privoxy /etc/privoxy/config
So, this is how I ran the both of them (this time, as root, and not just with sudo):
Code:
# /usr/sbin/tor
Dec 02 09:09:24.772 [notice] Tor v0.1.0.15. This is experimental software. Do not rely on it for strong anonymity.
Dec 02 09:09:24.833 [warn] /var/lib/tor is not owned by this UID (0). You must fix this to proceed.
Dec 02 09:09:24.834 [err] options_act(): Couldn't access/create private data directory /var/lib/tor
Dec 02 09:09:24.834 [err] init_from_config(): Acting on config options left us in a broken state. Dying.
# /usr/sbin/privoxy --pidfile /var/run/privoxy.pid --user privoxy /etc/privoxy/config
Dec 02 09:09:39 Privoxy(b7d786c0) Info: loading configuration file '/etc/privoxy/config':
Dec 02 09:09:39 Privoxy(b7d786c0) Info: Privoxy version 3.0.3
Dec 02 09:09:39 Privoxy(b7d786c0) Info: Program name: /usr/sbin/privoxy
Dec 02 09:09:39 Privoxy(b7d786c0) Info: Listening on port 8118 for local connections only
#
OK, so Privoxy starts, but not Tor (which is odd because Tor was working last night). Despite it saying it's working and listenning on port 8118, nmap still shows nothing. Odd indeed. Maybe not..... when I do 'telnet localhost 8118' it logs in. Typeing "help" results in it exiting saying "HTTP/1.0 400 Invalid header received from browser". Maybe it really is running after all.
Starting Tor from the init script (because it still fails from the command line) gives me:
Code:
# /etc/init.d/tor start
* Starting tor daemon (tor)... Dec 02 09:12:39.343 [notice] Tor v0.1.0.15. This is experimental software. Do not rely on it for strong anonymity.
[ ok ]
#
This leads me to believe that it's running. Again, using telnet to connect works, but it exits on any command (as I guess I'd expect since I don't know what commands to use).
So, time to fire up Firefox. Setting it to use 127.0.0.1:8118 results in it connecting to Privoxy now, but Tor is still MIA. Instead Privoxy results in a 404 error regardless of what page I try to load.
Code:
No such domain
Your request for http://www.google.com/ could not be fulfilled, because the domain name www.google.com could not be resolved.
This is often a temporary failure, so you might just try again.
So, I'm half way there.... kinda. Still seems odd that the init script doesn't want to load it right. I'm missing something, what is it?! The Official Doc only says to add that one line to the Privoxy config and leave the rest alone, which I have done before. This was so easy to set up on Gentoo, and it should be just as easy here. Any more ideas?!
Bookmarks