Experimental OS X Drag and Drop Vidalia Bundle Installer

I asked for community feedback in this post about drag and drop installation of the Vidalia bundle for Apple's OS X. In working with the Vidalia team, we now have a drag and drop installer. This is experimental. It's designed for a clean install. It won't migrate your settings, nor will it configure anything for you. Upon installing, your milk may sour and your salt may run off with your pepper. Now that the disclaimers are over, here's what it contains and does do for you.

It includes Universal binaries for:

  • Vidalia version 0.2.0-svn r3425
  • Polipo 1.0.4 configured to use Tor as a socksproxy
  • Tor 0.2.1.10-alpha compiled with prefix and bindir set to /Applications/Vidalia.app

You can download them along with the pgp signature and the SHA-1 hash. **Update 2009-01-22 changed packages to r3467 of Vidalia and updated Tor to 0.2.1.11-alpha.

It's a self-contained disk image that has 3 items. The Vidalia.app package, a README.txt, and a folder full of licenses. There is a pretty background for the disk image courtesy of dr|z3d, and a link to the /Applications folder. And while everything is in a simple dmg file, this is not a Tor Browser Bundle for OS X. Running the applications out of the dmg may work, but OS X writes to plist files, caches, and other things all over the installed system. Please wait until we can properly create a TBB for OS X; for this is not it. However, if you are interested in helping out with a TBB for OS X, we're happy to have you help.

Installation is literally this: "Drag the Vidalia icon to the Applications folder". Boom. Done. Vidalia, Tor, and Polipo are installed. Go to your Applications folder and double-click the Vidalia icon. Everything should work out of the box. All bets are off if you have a pre-configured Tor, Vidalia, Polipo, or Privoxy.

Here is a running CHANGELOG of what's new in Vidalia 0.2.0-svn. One of the changes is that your Vidalia data directory is no longer ~/.vidalia/ but ~/Library/Vidalia. If you don't have a vidalia.conf in ~/Library/Vidalia, there is a sample vidalia.conf in /Applications/Vidalia.app/Contents/Resources that is copied to ~/Library/Vidalia to make this bundle work.

The changes to Polipo are documented. See the README file for some details.

The only change to Tor are the parameters passed to configure:
"CFLAGS="-O -g -mmacosx-version-min=10.4 -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc" LDFLAGS="-Wl,-syslibroot,/Developer/SDKs/MacOSX10.4u.sdk"
CONFDIR=/Applications/Vidalia.app
./configure --prefix=/Applications/Vidalia.app --bindir=/Applications/Vidalia.app
--sysconfdir=/Library --disable-dependency-tracking". And edit the Makefile to remove the tests for /Library/Tor.

The goal is to make it easier for users to install the Vidalia Bundle and get Tor working. Using Vidalia to configure Tor is recommended. I don't know if this is the final direction, but enough people have trouble installing and configuring our packages in OS X, this is worth a test.

I look forward to your feedback. Thanks!

Anonymous

January 13, 2009

Permalink

Hi!

Thank for "OS X"-style distribution of V+T. As for me (Leopard 10.5.6) it works. When dragged and ran, Vidalia could not find tor, it works if change path in Vidalia specifically to /Applications/Vidalia.app/tor

Vidalia 2 svn has some glitches not allowing it to draw its window if clicked on its icon in Dock - in menubar I can manage Vidalia through menubar items, but there is now window of Vidalia itself ))

It would be nice if Vidalia will contain some run string for polipo and with options as proxy. =)

But it works! It is the most important I think...

phobos

January 14, 2009

In reply to by Anonymous (not verified)

Permalink

There should be run strings for polipo in Vidalia, in the "General" pane of the Vidalia Settings, you should the ability to start Polipo, with an option to list the path to the polipo binary. Under that is the ability to specify options, such as "-c /Applications/Vidalia.app/config"

And yes, there appears to be an issue where Vidalia doesn't respond to a single click on the menubar. If you right click it twice, it should pop open. We're still trying to figure out if this is really Qt or Vidalia.

Anonymous

January 13, 2009

Permalink

First I want to say I would love to have a drag and drop installer.

Now, I tested the "Experimental OS X Drag and Drop Vidalia Bundle Installer" and it did not work for me...at first. The path for starting tor on Vidalia.app launch was set to "tor". Changing this path to "/Applications/Vidalia.app/tor" made the app work. Also I had to add the path "/Applications/Vidalia.app/polipo" to start proxy option.

phobos

January 14, 2009

Permalink

The entire point of the sample vidalia.conf was to avoid the issues with the path in Vidalia.

Just for confirmation, you do have a vidalia.conf in /Applications/Vidalia.app/Contents/Resources/ right?

Anonymous

January 20, 2009

Permalink

Why Polipo instead of Privoxy? Any advantages of one over the other?

TIA

Anonymous

January 20, 2009

Permalink

I looked up Polipo and can see the advantage. I had been using an install that I pieced together or the latest versions of tor, privoxy, and squid(man). Uninstalled all of that. Then installed this Vidalia package.

Got it running fine but when I go to check.torproject.org it says I am not using Tor!

What do I need to do in my Network Settings? Http and Https as 127.0.0.1 or localhost and port 8118 or something else?

How are tor and Polipo chained? Which is first? Are the issues of DNS leaks avoided?

Depends where your polipo is listening.

I use polipo with its default port of 8123, so in my Torbutton preferences I
selected "Use custom proxy settings" and put in localhost 8123 for http and
https proxies, and left localhost 9050 for socks.

You're right that when we switch the packages from including privoxy to
including polipo, we'll want to make sure that the Torbutton that's included
knows what port it should tell Firefox to proxy to.

The easy answer is to configure the polipo we ship so that it listens on port
8118. The only downside is that it will conflict if you have Privoxy installed too.

polipo is set to 8118, just like privoxy used to be. This lets torbutton for firefox work without modification.

I suspect people having problems with the new vidalia config using the wrong directory is because you already have a vidalia.conf in ~/Library/Vidalia/.

I had posted twice as Anonymous.

Unfortunately, at least the last few versions of Vidalia have been unstable on my PowerBook G4/10.5.6. I thrashed this package and installed the latest stable Tor and Polipo. Changed these settings in Polipo's config and the setup works:

socksParentProxy = localhost:9050
diskCacheRoot=""
disableLocalInterface=true

censoredHeaders = from
censorReferer = maybe

Question: Why disable the page caching? Would the setup work faster if caching was on with a limited cache size?

Anyone know why PolipoStatusBar has disappeared? Would be easier to set up with it.

Note: I downloaded Polipo from the Max OS X list of univ binaries on it's site. There was no Leopard version so I downloaded Tiger 1.0.3 and installed it. Had to move the installed files into a single folder. Otherwise good. [Just did not have the time to mess with compiling.]

Anyone else having trouble with Vidalia?

From the post itself, this is experimental. I warned you it might not work, might crash, might sour your milk. It assumed a clean install. if you have a ~/.vidalia or ~/Library/Vidalia directory, it won't work after drag and drop. you will have to change the paths.

As for polipo, diskcache is disabled, otherwise it records every site you've visited through polipo. This is not good for anonymity.

Memory cache is enabled to improve performance.

...do you have these vidalia crashing problems with the stable version of vidalia?

I should have mentioned that I would love nothing better than to simply drag the Vidalia package and have it "work out of the box." However, as some others had to I had to change the path, probably because I had used privoxy, etc before. Bigger headache is that Vidalia becomes unresponsive too often.

I heard from the developer of PolipoStatusBar that his server crashed and he has not found a new "home" for his app. Meanwhile, I came across Dolipo. It is a GUI wrapper for polipo. I installed polipo and am now using tor with Dolipo.

If you are having trouble with this Vidalia package, you may want to take a look at a Dolipo (menu bar based) and Tor setup. In the Dolipo preferences, you can select the Polipo config file and toward the bottom enter localhost:9050 for Socks Parent Proxy. Tweak other settings you like and you are on your way. Only issue is having to manually configure relaying, if you want to do that.

As you can read in the post, I updated these experimental packages with Tor 0.2.1.11-alpha and vidalia 0.2.0-r3467.

Can anyone tell me why Privoxy is missing from the new Zero Install Bundle Tor version for Windows? I don't see the privoxy icon at the right left corner as I used to when I started the old Vidalia. Does this pose a privacy hazard, or is privoxy running in the background, just not visible anymore?

The Tor Browser Bundle actually includes Polipo, not Privoxy. Polipo is a lighter-weight proxy that serves pretty much the same role as Privoxy. It just runs in the background, and Vidalia launches it when everything starts up.

(Privoxy is a little bit better than Polipo at removing dangerous web stuff, but Torbutton 1.2 does a fine job at that, so the fact that Privoxy can do some of it is moot.)

I had installed the "advanced" Tor only package and added polipo with dolipo. Worked out fine as I have described above. However, this weekend I decided to give Privoxy another go.

Much to my surprise, with Tor + Privoxy, Safari is much faster plus has more effective ad blocking.

???

PS Read online that if one is chaining Tor, Privoxy, Squid, the correct order is Squid > Privoxy > Tor but if chaining with Polipo instead, the correct order is Privoxy > Polipo > Tor. Why is that?

My bundle didn't work out of the box, until I discovered that polipo was running its default configuration, rather than the one provided by the Vidalia bundle.

The solution was to open Vidalia's preferences, and under "Proxy Application Arguments" in the General tab to add the following:

 -c /Applications/Vidalia.app/Contents/Resources/polipo.conf

Then everything worked perfectly.

I like the drag and drop. But I dragged the Firefox extension installer to my applications folder too, before I realized I just needed to run it from the intaller location. It could be more clear that only the Vidalia app need be dragged.
thanks for the great software.