Debian and Polipo (Vidalia Bundle/Tor)
What I did before is get a copy of a file that gets Polipo working right with Tor, Vidalia and Tor Button (In Iceweasel)
Now the file I got was, I think, was from the Polipo website. I just coped and pasted the configuration file and all worked fine.
Problem I am having is that I forgot to bookmark the website or save a copy of the file. So I tried to go to the Polipo website, I am sure I got it from there I think, but I have not been able to get that website to load the last couple of days.
This is what I get for forgetting to make a copy of the file...
If anyone knows what I am talking, first congratulations lol, could you post me a copy of that file or point me in the right direction?
Sorry I am not more clear on this. I am new to setting all of this up, new and a bit clueless.
My polipo config file and it works just fine
You may want to change proxy name to something else.
# Sample configuration file for Polipo. -*-sh-*
# You should not need to edit this configuration file; all configuration
# variables have reasonable defaults.
# This file only contains some of the configuration variables; see the
# list given by ``polipo -v'' and the manual for more.
### Basic configuration
# Uncomment one of these if you want to allow remote clients to
# proxyAddress = "::0" # both IPv4 and IPv6
# proxyAddress = "0.0.0.0" # IPv4 only
# If you are enabling 'proxyAddress' above, then you want to enable the
# 'allowedClients' variable to the address of your network, e.g.
# allowedClients = 127.0.0.1, 192.168.42.0/24
# allowedClients = 127.0.0.1
# Uncomment this if you want your Polipo to identify itself by
# something else than the host name:
proxyName = "wifi-police"
# Uncomment this if there's only one user using this instance of Polipo:
cacheIsShared = false
# Uncomment this if you want to use a parent proxy:
# parentProxy = "squid.example.org:3128"
# Uncomment this if you want to use a parent SOCKS proxy:
socksParentProxy = "localhost:9050"
socksProxyType = socks5
# Uncomment this if you want Polipo to use a ridiculously small amount
# of memory (a hundred C-64 worth or so):
# chunkHighMark = 819200
# objectHighMark = 128
# Uncomment this if you've got plenty of memory:
chunkHighMark = 50331648
objectHighMark = 16384
### On-disk data
# Uncomment this if you want to disable the on-disk cache:
# diskCacheRoot = ""
# Uncomment this if you want to put the on-disk cache in a
# non-standard location:
# diskCacheRoot = "~/.polipo-cache/"
# Uncomment this if you want to disable the local web server:
# localDocumentRoot = ""
# Uncomment this if you want to enable the pages under /polipo/index?
# and /polipo/servers?. This is a serious privacy leak if your proxy
# is shared.
# disableIndexing = false
# disableServersList = false
### Domain Name System
# Uncomment this if you want to contact IPv4 hosts only (and make DNS
# queries somewhat faster):
dnsQueryIPv6 = no
# Uncomment this if you want Polipo to prefer IPv4 to IPv6 for
# double-stack hosts:
dnsQueryIPv6 = reluctantly
# Uncomment this to disable Polipo's DNS resolver and use the system's
# default resolver instead. If you do that, Polipo will freeze during
# every DNS query:
# dnsUseGethostbyname = yes
# Uncomment this if you want to enable detection of proxy loops.
# This will cause your hostname (or whatever you put into proxyName
# above) to be included in every request:
# Uncomment this if you want to slightly reduce the amount of
# information that you leak about yourself:
censoredHeaders = from, accept-language
censorReferer = maybe
# Uncomment this if you're paranoid. This will break a lot of sites,
# censoredHeaders = set-cookie, cookie, cookie2, from, accept-language
# censorReferer = true
# Uncomment this if you want to use Poor Man's Multiplexing; increase
# the sizes if you're on a fast line. They should each amount to a few
# seconds' worth of transfer; if pmmSize is small, you'll want
# pmmFirstSize to be larger.
# Note that PMM is somewhat unreliable.
pmmFirstSize = 16384
pmmSize = 8192
# Uncomment this if your user-agent does something reasonable with
# Warning headers (most don't):
# relaxTransparency = maybe
# Uncomment this if you never want to revalidate instances for which
# data is available (this is not a good idea):
# relaxTransparency = yes
# Uncomment this if you have no network:
# proxyOffline = yes
# Uncomment this if you want to avoid revalidating instances with a
# Vary header (this is not a good idea):
# mindlesslyCacheVary = true
Thanks. I gave it a try, changing the proxy name of course, and it didn't work. But I think that is my fault. I think I am missing something I did before. Time to Scroogle it and research more (and then make notes and back up those notes!)
I was wrong. The Polipo website is back up and then, of course, I figured out that I actually got that file from the Tor website.
So here is the tor/polipo configuration file that is working for me. I am going to compare the two, the one above and this one, later to see why yours didn't work and this one does. I need to get familiar with all of this anyways so this is a good starting point. Thanks again for your help.
A few comments.
The incognito suggestions are interesting in your copy. I'll have to look into that when I get time.
Your copy is setup to use port 8118 and the default polipo port is 8123. Perhaps your copy is setup to be chained to Privoxy as 8118 is the default port for such.
Your copy does not use PMM while I do in my copy and I do not suffer unreliability.
Your DNS resolver setting is enabled when Polipo warns you against doing so.
And I was hoping to install Vidalia from the package manager in Linux Mint without having to configure everything! Sadly Vidalia starts and cannot connect to Tor anywhere nor does it appear to exist in any dir.
I downloaded the source and compiled it but I can't seem to start it and no messages in the message log. Has anyone got a simple working install of Vidalia on Ubuntu based machines?
Installing Vidalia via the package manager in any buntu including Mint works fine. During the install procedure a window should have popped up asking you if you want vidalia to start and stop tor. You should have answered "yes". Vidalia creates a new torrc file so you need to change a simple setting.
Go to /home/.vidalia/torrc and remove the "#" in front of ControlPort 9051.
Then open a terminal and run sudo /etc/init.d/tor stop. You should be able to start and stop tor with vidalia now. You may have to restart vidalia first.
Tor not found
I can't get this to work!! Updated torrc and ran sudo /etc/init.d/tor stop/start yields:
sudo: /etc/init.d/tor: command not found
Tor is not located in init.d or rather, it ain't init!
I did not get an option to start stop tor during install no. Am I the only one struggling to get Tor via Vidalia to work or have I missed something obvious?
Smudge. Did you add the tor repository to Mint's package manager or apt-get? The version offered in the default buntu repository is too old.
Are you sure tor is installed along with socat and tor-geoipdb?
Sorry if these questions are stupid but I'm struggling to find out what is going on with your tor/vidalia.
I'm running Linux Mint 10 64 and do not know which Ubuntu core this is?
* Ubuntu 10.10 is "maverick"
* Ubuntu 10.04 or Trisquel 4.0 is "lucid"
* Ubuntu 9.10 or Trisquel 3.5 is "karmic"
* Ubuntu 9.04 is "jaunty"
* Ubuntu 8.10 is "intrepid"
* Ubuntu 8.04 is "hardy"
* Debian Etch is "etch"
* Debian Lenny is "lenny"
I uninstalled and will try the version you suggested from http://www.torproject.org/docs/debian.html.en
Just need to confirm which version of Ubuntu this Mint is based on..
According to kernel versions Mint 10 appears to be based on Ubuntu 10.10 Maverick.
There is also a stand-alone version in 32 and 64 bit if all else fails. The torbrowser bundle is ready to go with vidalia/tor/polipo pre-configured.
|All times are GMT -5. The time now is 12:04 AM.|