Vidalia 0.2.9 Released

by phobos | May 27, 2010

On May 20, we released Vidalia 0.2.9. Fixes include Qt 4.6.2 compatibility, new cert, and some new translations.

You can download it at https://www.torproject.org/vidalia/. Packages are slowly being updated to include this version of Vidalia.

The full changelog is:

Remove the GoDaddy CA certificate bundle since we changed the certificate used to authenticate connections to geoips.vidalia-project.net for downloading GeoIP information from a commercial GoDaddy certificate to a free CACert certificate.
Define -D_WIN32_WINNT=0x0501 on Windows builds so that MiniUPnPc will build with the latest versions of MinGW.
Modify miniupnpc.c from MiniUPnPc's source so that it will build on Mac OS X 10.4.
Work around Qt's new behavior for the QT_WA macro so that Vidalia will
work correctly again on Windows with Qt >= 4.6.
Force CMake to include the *_RELEASE versions of Qt libraries when building a .dmg on Mac OS X, so that it will work with CMake >= 2.8 as well.
Explicitly link zlib into src/common to avoid link errors on some older versions of Mac OS X.
Add Danish, Brazilian Portguese and Vietnamese translations.

releases

Comments

Please note that the comment area below has been archived.

Awesome! I would love to see

Awesome! I would love to see a new TBB with updated Vidalia and Tor!

It seems that all tor links from China have been cut off by "Great Firewall"! I tried frequently in the past weeks with newly retrieved bridges, and no luck at all. It's possible that the GFW could be able to tell TOR traffic by some kind of protocol signatures. Is there any possible way to fight it?

Thanks!
Waterson

Our research shows they are

Our research shows they are blocking IP address:port combinations, nothing more fancy than that.

Yes,just a "blocking IP

Yes,just a "blocking IP address:port"with an extending "black list",and nothing more.We can still use Tor in the mainland China,only the connection becomes a more slow progress. And most bridges cease to be effective.

Sorry for posting my

Sorry for posting my question here, but i could find the answer anywhere else.

Is it possible to run multiple instances of Tor (client) on one machine ?

At program start Tor opens a socks listener on port 9050 so when i try to run another instance Tor fails to connect. I don't know how to overcome this.

You need to have multiple

You need to have multiple torrc files, each with unique ports, data directories, and log files configured.

polipo not working, Mac

polipo not working, Mac 10.4.11 :(
even with older version .
So torbutton is useless, so, what can I do ???
on mac firewall, I have allowed ports for 8118 and 9050.
Vidalia say it is connected to TOR !!! SO how can I use it ?
Thanks a lot,

What happens when you

What happens when you restart vidalia? Vidalia should start polipo. You don't need to allow any ports on the mac firewall, as you aren't accepting traffic from outside.

Hi, I am a different user

Hi,
I am a different user from OP, a bit of NuB here, but generally highly fluent in o.s. tech.
I am likewise seeing problems as OP mentioned. I am on OSX 10.5.8. I do not run a firewall.
Firefox and Camino both state seeing a problem with the proxy when enabled.
My Firefox has the Torbutton installed from the official app pkg for Mac–Intel.
For Camino I have Vidalia.app launched from same app pkg, and inserted user_pref lines into its js files.
btw Over at the wget mail-list, we have found that OSX 10.5 and 10.4 have older openssl provided by Apple (let’s not get into why they won’t upgrade it). Indeed the log for vidalia+tor mentions the back-level on my machine:
> […]
> Jun 15 07:28:07.549 [Notice] OpenSSL OpenSSL 0.9.7l 28 Sep 2006 [9070cf] looks like it's older than 0.9.8l, but some vendors have backported 0.9.8l's renegotiation code to earlier versions, and some have backported the code from 0.9.8m or 0.9.8n. I'll set both SSL3_FLAGS and SSL_OP just to be safe.
> […]
Also the local web-browsers can’t access port 9051 (control panel). I specifically set “none” and un-check the random password setting. I verified by looking at the various conf files et al. But the browser ends up displaying a plain–text message saying Authentification Required.
> […]
> Jun 15 07:28:07.168 [Warning] ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That's bad! You should upgrade your Tor controller as soon as possible.
> […]
I think I am going to need to compile from src tarball, as I have some of the requisite pkgs (OpenSSL–1.0.0a on the wget problem for ex), and I do have enough X11/glib/gtk+ to run Pan news-reader (plain *ix type apps). But I do hate dealing with Qt etc on a OSX platform. ;)
Anyway, would these problems be candidates to file into the tor bug system?
Thank you.

You've misconfigured your

You've misconfigured your tor. Tor works around the OS X openssl nonsense and uses it correctly. You don't need to upgrade openssl to use tor.

Web browsers and other applications want to use 127.0.0.1:9050. 9051 is the control port to allow other control applications to configure your Tor, like vidalia. You definitely want to have a password or cookie authentication enabled, otherwise malicious websites can reconfigure your tor for you.

Always crashing at Bootstrapped 10%, cannot connect to directory server.

pls how can tor work in

pls how can tor work in Nigeria

From what we've heard from

From what we've heard from others in Nigeria, it works fine. Open a ticket, trac.torproject.org with your issue.