Configuring Tor and Privoxy in Squeeze
AG
I am attempting to get Tor and Privoxy working with Iceweasel, but it
keeps throwing up errors.
The logfile has been enabled to record debugging info (1024 "Log the
destination for requests Privoxy didn't let through, and the reason
why", 4096 "start up banner and warnings" and 32 "debug force feature".
This is all that is shown:
May 31 11:39:48.199 b7ddd8d0 Info: Privoxy version 3.0.12
May 31 11:39:48.199 b7ddd8d0 Info: Program name: /usr/sbin/privoxy
May 31 11:39:48.219 b7ddd8d0 Info: Listening on port 8118 on IP address
localhost
Under the preferences option of the Iceweasel Tor Button, running the
test, this is the output:
Tor proxy test: Internal error
Having searched for over an hour now, I am reasonably sure that I am
following all the correct instructions for setting up the config file
(I've listed mine below) and have the latest Tor and Privoxy installed.
So, I am stumped. Without Tor being enabled, the connection is fine,
and when Tor is enabled, looking through Iceweasel
preferences/Advanced/Network/Settings the following is enabled:
Manual proxy configuration
HTTP Proxy 127.0.0.1 Port 8118
[I do not have "use this proxy server for all protocols" checked]
SSL Proxy 127.0.0.1 Port 8118
Socks Host 127.0.0.1 Port 9050
Socks v5 enabled
No Proxy for: localhost, 127.0.0.1
The following is my /etc/privoxy/config file (without the commented
sections):
user-manual /usr/share/doc/privoxy/user-manual
confdir /etc/privoxy
logdir /var/log/privoxy
actionsfile match-all.action # Actions that are applied to all sites and
maybe overruled later on.
actionsfile default.action # Main actions file
actionsfile user.action # User customizations
filterfile default.filter
logfile logfile
debug 1024 # Log the destination for requests Privoxy didn't let
through, and the reason why.
debug 4096 # Startup banner and warnings
debug 32
listen-address localhost:8118
toggle 1
enable-remote-toggle 0
enable-remote-http-toggle 0
enable-edit-actions 0
enforce-blocks 0
buffer-limit 4096
forward-socks5 / 127.0.0.1:9050 .
accept-intercepted-requests 0
allow-cgi-request-crunching 0
split-large-forms 0
keep-alive-timeout 300
socket-timeout 300
I'm the first to admit that my understanding of this stuff is junior
school at best, so this may be a really simple misconfiguration, but as
I said - when compared to suggested configurations found on the web, my
config file seems fine and yet it just won't allow me access to webpages
which are otherwise accessible without Tor.
Thanks for any suggestions.
Cheers
AG
--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Florian Kulzer
> Hello
>
> I am attempting to get Tor and Privoxy working with Iceweasel, but it
> keeps throwing up errors.
[...]
> Under the preferences option of the Iceweasel Tor Button, running the
> test, this is the output:
>
> Tor proxy test: Internal error
[...]
> So, I am stumped. Without Tor being enabled, the connection is fine,
> and when Tor is enabled, looking through Iceweasel
> preferences/Advanced/Network/Settings the following is enabled:
>
> Manual proxy configuration
> HTTP Proxy 127.0.0.1 Port 8118
> [I do not have "use this proxy server for all protocols" checked]
> SSL Proxy 127.0.0.1 Port 8118
I have the same settings, except for using "localhost" instead of
"127.0.0.1". This should not make any difference, though.
> Socks Host 127.0.0.1 Port 9050
> Socks v5 enabled
> No Proxy for: localhost, 127.0.0.1
The same configuration works for me.
> The following is my /etc/privoxy/config file (without the commented
> sections):
[...]
> forward-socks5 / 127.0.0.1:9050 .
I have this instead, as per the example given in the comments of the
config file:
forward-socks4a / localhost:9050 .
You should check if Tor and privoxy are actually listening for
connections on the ports that you specify; see the output of these
commands (as root):
lsof -i :8118 -i :9050
netstat -plant | grep -E ':(8118|9050)'
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
AG
Thanks for coming to my aid (again!).
Have tried the suggestions, and this is the output:
netstat -plant | grep -E ':(8118|9050)'
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN-
tcp6 0 0 ::1:8118 :::* LISTEN
and
lsof -i :8118 -i :9050
yielded nothing at all.
I also corrected the forward-socks4a string before running these tests.
The good news is is that this used to work on my previous installation.
The bad news is that it did so without me having to do a lot of fiddling
around ... so I have no idea how to fix this issue.
Thank you.
AG
AG
When trying this again as root (sudo), these are the results:
sudo netstat -plant | grep -E ':(8118|9050)'
tcp 0 0 127.0.0.1:9050 0.0.0.0:*
LISTEN19186/tor
tcp6 0 0 ::1:8118 :::*
LISTEN26738/privoxy
Suggesting that this has been picked up, but seems now to simply just
not connect.
Thanks for any help.
Cheers
Florian Kulzer
> AG wrote:
>> Florian Kulzer wrote:
>>> On Sun, May 31, 2009 at 11:59:29 +0100, AG wrote:
>>>
>>>> Hello
>>>>
>>>> I am attempting to get Tor and Privoxy working with Iceweasel, but
>>>> it keeps throwing up errors.
>>>
>>> [...]
>>>
>>>
>>>> Under the preferences option of the Iceweasel Tor Button, running
>>>> the test, this is the output:
>>>>
>>>> Tor proxy test: Internal error
[...]
>>>> The following is my /etc/privoxy/config file (without the commented
>>>> sections):
>>>>
>>>
>>> [...]
>>>
>>>
>>>> forward-socks5 / 127.0.0.1:9050 .
>>>>
>>>
>>> I have this instead, as per the example given in the comments of the
>>> config file:
>>>
>>> forward-socks4a / localhost:9050 .
[...]
>> I also corrected the forward-socks4a string before running these tests.
Did you restart privoxy after changing the configuration file?
[...]
> When trying this again as root (sudo), these are the results:
>
> sudo netstat -plant | grep -E ':(8118|9050)'
> tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 19186/tor
> tcp6 0 0 ::1:8118 :::* LISTEN 26738/privoxy
The line for Tor is as expected, but I am surprised that you have
privoxy listening only for tcp6 connections. I do not recall ever seeing
privoxy listed in any way other than this:
tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN 7152/privoxy
Have you done any IPv6-related customization on your system?
In any case, if two programs do not work together as they should then it
may help to test each one individually.
To see if privoxy is working without Tor, remove the "forward-socks.."
line from the configuration file and restart privoxy. Then open
iceweasel, make sure that torbutton is NOT active and select "localhost"
port 8118 as the manual proxy configuration for http and https; make
sure that the SOCKS field is empty. Try if you can load any websites in
this configuration and if you can reach the configuration front end at
http://config.privoxy.org.
To test Tor without privoxy, clear all fields in iceweasel's manual
proxy configuration except for the SOCKS one, which should have
"localhost" and port 9050. Then go to a site like http://showip.net and
check if the reported IP address is different from your real one. (If
Tor works then you should see the IP address of the current exit node.)
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
AG
> On Mon, Jun 01, 2009 at 19:08:31 +0100, AG wrote:
>
>> AG wrote:
>>
>>> Florian Kulzer wrote:
>>>
>>>> On Sun, May 31, 2009 at 11:59:29 +0100, AG wrote:
>>>>
>>>>
>>>>> Hello
>>>>>
>>>>> I am attempting to get Tor and Privoxy working with Iceweasel, but
>>>>> it keeps throwing up errors.
>>>>>
>>>> [...]
>>>>
>>>>
>>>>
>>>>> Under the preferences option of the Iceweasel Tor Button, running
>>>>> the test, this is the output:
>>>>>
>>>>> Tor proxy test: Internal error
>>>>>
>
> [...]
>
>
>>>>> The following is my /etc/privoxy/config file (without the commented
>>>>> sections):
>>>>>
>>>>>
>>>> [...]
>>>>
>>>>
>>>>
>>>>> forward-socks5 / 127.0.0.1:9050 .
>>>>>
>>>>>
>>>> I have this instead, as per the example given in the comments of the
>>>> config file:
>>>>
>>>> forward-socks4a / localhost:9050 .
>>>>
>
> [...]
>
>
>>> I also corrected the forward-socks4a string before running these tests.
>>>
>
> Did you restart privoxy after changing the configuration file?
>
> [...]
>
>
Yes, I did. For good measure, I also restarted the tor daemon.
>> When trying this again as root (sudo), these are the results:
>>
>> sudo netstat -plant | grep -E ':(8118|9050)'
>> tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 19186/tor
>> tcp6 0 0 ::1:8118 :::* LISTEN 26738/privoxy
>>
>
> The line for Tor is as expected, but I am surprised that you have
> privoxy listening only for tcp6 connections. I do not recall ever seeing
> privoxy listed in any way other than this:
>
> tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN 7152/privoxy
>
> Have you done any IPv6-related customization on your system?
>
No, this is a new install as of Sunday and I don't know enough to have
made those adjustments deliberately. If these happened in the course of
something else, I couldn't say and don't know how to check.
Is this a risk or something?
> In any case, if two programs do not work together as they should then it
> may help to test each one individually.
>
> To see if privoxy is working without Tor, remove the "forward-socks.."
> line from the configuration file and restart privoxy. Then open
> iceweasel, make sure that torbutton is NOT active and select "localhost"
> port 8118 as the manual proxy configuration for http and https; make
> sure that the SOCKS field is empty. Try if you can load any websites in
> this configuration and if you can reach the configuration front end at
> http://config.privoxy.org.
>
> To test Tor without privoxy, clear all fields in iceweasel's manual
> proxy configuration except for the SOCKS one, which should have
> "localhost" and port 9050. Then go to a site like http://showip.net and
> check if the reported IP address is different from your real one. (If
> Tor works then you should see the IP address of the current exit node.)
>
>
OK - followed the directions:
Commented out the "forward-socks ..." line and restarted privoxy.
Changed the manual proxy settings in IW as described and reached
http://config.privoxy.org which reads "This is Privoxy 3.0.12 on
localhost (::1), port 8118, enabled"
Next, cleared all fields in IW settings and entered localhost port 9550
in the socks line. Went to the URL shown, and that server thinks my
machine is in Nebraska, not the UK (must be the exit node you mentioned).
So ... what does all this mean then? The individual components appear
to work? But not together? It may/ not be anything, but under the IW
settings, no matter what I enter in the privoxy/config file, in the
settings the Socksv5 radio button is always marked.
The mystery continues ...
AG
wau...@yahoo.com
I have the same effect with privoxy listening only on IPv6 on an
up-to-date SID system on AMD64.
I had no changes made (knowingly) to the privoxy setting.
Hugo
AG
Does your set-up still make valid connections though?
AG
Florian Kulzer
> Florian Kulzer wrote:
>> On Mon, Jun 01, 2009 at 19:08:31 +0100, AG wrote:
>>
>> [...]
>>
>>
>>> When trying this again as root (sudo), these are the results:
>>>
>>> sudo netstat -plant | grep -E ':(8118|9050)'
>>> tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 19186/tor
>>> tcp6 0 0 ::1:8118 :::* LISTEN 26738/privoxy
>>>
>>
>> The line for Tor is as expected, but I am surprised that you have
>> privoxy listening only for tcp6 connections. I do not recall ever seeing
>> privoxy listed in any way other than this:
>>
>> tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN 7152/privoxy
>>
>> Have you done any IPv6-related customization on your system?
[...]
> I have the same effect with privoxy listening only on IPv6 on an
> up-to-date SID system on AMD64.
> I had no changes made (knowingly) to the privoxy setting.
That is interesting; thanks for the information. Maybe the behavior of
privoxy that I am seeing is not how a fresh install is expected to
behave these days. I also run up-to-date Sid/amd64, but my system might
have acquired some cruft/baggage over its lifetime (2.5 years).
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
AG
TIA
Florian Kulzer
> Florian Kulzer wrote:
>> On Mon, Jun 01, 2009 at 19:08:31 +0100, AG wrote:
>>> AG wrote:
>>>> Florian Kulzer wrote:
>>>>> On Sun, May 31, 2009 at 11:59:29 +0100, AG wrote:
>>>>>
>>>>>> Hello
>>>>>>
>>>>>> I am attempting to get Tor and Privoxy working with Iceweasel,
>>>>>> but it keeps throwing up errors.
[...]
>>> sudo netstat -plant | grep -E ':(8118|9050)'
>>> tcp 0 0 127.0.0.1:9050 0.0.0.0:* LISTEN 19186/tor
>>> tcp6 0 0 ::1:8118 :::* LISTEN 26738/privoxy
>>>
>>
>> The line for Tor is as expected, but I am surprised that you have
>> privoxy listening only for tcp6 connections. I do not recall ever seeing
>> privoxy listed in any way other than this:
>>
>> tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN 7152/privoxy
>>
>> Have you done any IPv6-related customization on your system?
>>
> No, this is a new install as of Sunday and I don't know enough to have
> made those adjustments deliberately. If these happened in the course of
> something else, I couldn't say and don't know how to check.
>
> Is this a risk or something?
Not necessarily a risk, but there have been complaints about the ipv6
patch of privoxy :
(wauhugo pointed out this bug report to me in an off-list message)
[...]
> Commented out the "forward-socks ..." line and restarted privoxy.
> Changed the manual proxy settings in IW as described and reached
> http://config.privoxy.org which reads "This is Privoxy 3.0.12 on
> localhost (::1), port 8118, enabled"
Ok that is what I would have expected. (Again you see an ipv6 address
were I see an ipv4 one, but I am not sure if this is related to your
problem.)
> Next, cleared all fields in IW settings and entered localhost port 9550
> in the socks line. Went to the URL shown, and that server thinks my
> machine is in Nebraska, not the UK (must be the exit node you mentioned).
Yes, at that moment your tor must have been using an exit node in
Nebraska. (The exit node should change regularly to make it harder to
track you.)
> So ... what does all this mean then? The individual components appear
> to work? But not together?
Maybe there is something wrong with the torbutton plugin.
> It may/ not be anything, but under the IW
> settings, no matter what I enter in the privoxy/config file, in the
> settings the Socksv5 radio button is always marked.
I also have the SOCKS5 button marked all the time; it does not seem to
cause any harm.
The next thing I would try is to make privoxy and tor work together
without using the torbutton plugin of iceweasel: Activate the
"forward-socks ..." line again and restart privoxy. Make sure that the
manual proxy configuration for http and https is the same as for the
previous privoxy test (localhost port 8118) *and* that the SOCKS proxy
setting is localhost port 9050. Then try to access the showip.net
website again. What happens now?
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
AG
manually entered the settings in Iceweasel (i.e. manual proxy
configuration):
HTTP Proxy 127.0.0.1 Port 8118
SSL Proxy 127.0.0.1 Port 8118
SOCKS Host: 127.0.0.1 Port 9050
Socks v5 checked
No proxy for: localhost, 127.0.01
Even though I didn't click (engage) the tor button on Iceweasel, it is
still showing green - i.e. is engaged - as a result of changing these
settings.
Entered showip.net into address bar - "Proxy server refused connection"
with the headline message "The connection was refused when attempting to
contact the proxy server you have configured. Please check your proxy
settings and try again."
Was unable to adjust these settings without the torbutton changing
colour according to whether or not I was manually changing the proxy
settings or checked direct connection to the Net. Not sure if this is
relevant to the test though?
AG
advice, I have been entirely unsuccessful. Google has not thrown back
anything of any use, so I decided on the more dramatic approach.
I purged tor and privoxy, adjusted my sources.list to lenny and
reinstalled both tor and privoxy, amended privoxy/config and restarted
privoxy. Then I fired up Iceweasel and viola! I now have an active tor
and privoxy arrangement.
So, the version of privoxy that appears to work best for me is 3.0.9-1,
whilst the one that didn't was 3.0.12-2_i386 I don't know why or how,
but there you go.
Thanks for your input on this issue Florian.
All the best
Florian Kulzer
>> AG wrote:
>>> Hello
>>>
>>> I am attempting to get Tor and Privoxy working with Iceweasel, but it
>>> keeps throwing up errors.
[...]
>>> The following is my /etc/privoxy/config file (without the commented
>>> sections):
[...]
>>> listen-address localhost:8118
[...]
> I purged tor and privoxy, adjusted my sources.list to lenny and
> reinstalled both tor and privoxy, amended privoxy/config and restarted
> privoxy. Then I fired up Iceweasel and viola! I now have an active tor
> and privoxy arrangement.
I have now managed to reproduce your problem by configuring privoxy to
listen on the ipv6 address of localhost, i.e. by making this change to
/etc/privoxy/config:
listen-address [::1]:8118
As soon as I restart privoxy after that, the iceweasel/privoxy/tor
combination stops working.
This means that the problem is definitely related to the ipv6 patch. The
error message that you posted in one of your previous messages also
suggests that your communictaion problem was between iceweasel and
privoxy.
> So, the version of privoxy that appears to work best for me is 3.0.9-1,
> whilst the one that didn't was 3.0.12-2_i386 I don't know why or how,
> but there you go.
That makes sense because the Lenny version does not have the ipv6 patch.
(The patch was disabled in version 3.0.5-beta-3 and reenabled in
3.0.10-2.) I bet that you now find privoxy listening on 127.0.0.1:8118
if you run the "netstat -plant" command again.
It seems that "localhost" resolves to the ipv6 address on your system,
at least as far as the privoxy configuration is concerned, while for me
it still yields the ipv4 address. The following might therefore be a
workaround for the 3.0.12-2 version of privoxy on your installation:
listen-address 127.0.0.1:8118
It would probably be better to find out why "localhost" is interpreted
differently on your box. To this end, I would like to see the output of
getent hosts localhost
and the contents of your /etc/hosts file.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
AG
Your assumption looks spot on about defaulting to ipv6, as can be seen
below:
Working from the bottom back up:
/etc/hosts
127.0.0.1 localhost
192.168.1.40 owndomain.org owndomain
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
and then ...
$ getent hosts localhost
::1 localhost ip6-localhost ip6-loopback
This is a new machine with a SATA drive, although I did install the same
ethernet card that I had in my previous box (which worked fine with Tor
and Privoxy), so I don't know if I inadvertently configured it that way
when I did the fresh install on Saturday last.
And as you suspected, Iceweasel does indeed listen in on 8118, as seen by:
$ netstat -plant
(Not all processes could be identified, non-owned process info
will not be shown, you would have to be root to see it all.)
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address
State PID/Program
name
tcp 0 0 127.0.0.1:3306 0.0.0.0:*
LISTEN
-
tcp 0 0 0.0.0.0:111 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:7634 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:8118 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:631 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:25 0.0.0.0:*
LISTEN
-
tcp 0 0 127.0.0.1:9050 0.0.0.0:*
LISTEN
-
tcp 0 0 0.0.0.0:54779 0.0.0.0:* LISTEN
At this point I am okay with having the Lenny ipv6-non-patched tor and
privoxy arrangement. However, if you are recommending that I do attempt
the workaround then I will do so. This will presumably mean allowing
the two packages to be updated as the Update Notifier wants to keep
doing? If not, then I need to figure out how to stop the UN from
insisting that these packages need upgrading.
Once again, many thanks Florian.
AG
Florian Kulzer
> Florian Kulzer wrote:
>> On Wed, Jun 03, 2009 at 18:31:43 +0100, AG wrote:
>>>> AG wrote:
>>>>>
>>>>> I am attempting to get Tor and Privoxy working with Iceweasel,
>>>>> but it keeps throwing up errors.
[...]
>>>>> The following is my /etc/privoxy/config file (without the
>>>>> commented sections):
[...]
>>>>> listen-address localhost:8118
[...]
>> It seems that "localhost" resolves to the ipv6 address on your system,
>> at least as far as the privoxy configuration is concerned, while for me
>> it still yields the ipv4 address. The following might therefore be a
>> workaround for the 3.0.12-2 version of privoxy on your installation:
>>
>> listen-address 127.0.0.1:8118
>>
>> It would probably be better to find out why "localhost" is interpreted
>> differently on your box. To this end, I would like to see the output of
>>
>> getent hosts localhost
>>
>> and the contents of your /etc/hosts file.
>>
>>
> Florian
>
> Your assumption looks spot on about defaulting to ipv6, as can be seen
> below:
>
> Working from the bottom back up:
>
> /etc/hosts
>
> 127.0.0.1 localhost
> 192.168.1.40 owndomain.org owndomain
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 localhost ip6-localhost ip6-loopback
This is were my /etc/hosts file differs:
::1 ip6-localhost ip6-loopback
[...]
> $ getent hosts localhost
> ::1 localhost ip6-localhost ip6-loopback
As expected from my /etc/hosts, I get this:
127.0.0.1 localhost
I would remove the "localhost" from the line starting with "::1". I
think that making sure that "localhost" resolves to 127.0.0.1 is still
the configuration with the least likelihood to cause trouble.
> This is a new machine with a SATA drive, although I did install the same
> ethernet card that I had in my previous box (which worked fine with Tor
> and Privoxy), so I don't know if I inadvertently configured it that way
> when I did the fresh install on Saturday last.
Which version of the installer did you use? Maybe the default
configuration of /etc/hosts has changed recently (which might be a bug).
> And as you suspected, Iceweasel does indeed listen in on 8118, as seen by:
> $ netstat -plant
[...]
> tcp 0 0 127.0.0.1:8118 0.0.0.0:* LISTEN -
Note: This has to be privoxy, not iceweasel - you will see the process
name if you run netstat with the same options as root.
> At this point I am okay with having the Lenny ipv6-non-patched tor and
> privoxy arrangement. However, if you are recommending that I do attempt
> the workaround then I will do so.
I am pretty sure that you will not even haven to use the workaround if
you make the suggested change to /etc/hosts.
--
Regards, | http://users.icfo.es/Florian.Kulzer
Florian |
AG
Just an update - I deleted the redundant "localhost" entry in the
/etc/hosts file as suggested and accepted the Tor and Privoxy upgrade,
keeping my original config file when asked to keep/ update.
So far - all seems to be well.
You were a tremendous help with this issue and I am very grateful.
Thank you for sharing your expertise with me.
Best wishes to you.
AG
Jivan Amara
I am pretty sure that you will not even haven to use the
workaround if
you make the suggested change to /etc/hosts.
Florian
Just an update - I deleted the redundant "localhost" entry in the
/etc/hosts file as suggested and accepted the Tor and Privoxy upgrade,
keeping my original config file when asked to keep/ update.
So far - all seems to be well.
You were a tremendous help with this issue and I am very grateful.
Thank you for sharing your expertise with me.
Best wishes to you.
AG
Hi guys, I just wanted to confirm the issue. I just performed a fresh
install. I used a USB boot disk with the 'debian-502-i386-netinst.iso'
image. I then set my /etc/apt/sources.list file to use 'testing' and
did a full safe-upgrade. When I installed Tor and Privoxy the same
issue was encountered and eliminating the localhost entry from the IPv6
::1 line in /etc/hosts resolved the issue.
I don't know much about IPv6. Who should be notified of this? Is this
a problem with the default /etc/hosts file or an issue with Privoxy's
defaults?
Jivan