Florian Kulzer wrote:
On Mon, Jun 01, 2009 at 21:06:26 +0100, AG wrote:
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 :
http://bugs.debian.org/525274
(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?
Uncommented the line in the config file, restarted tor and privoxy and
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?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
