New Stable Version 0.2.1.24 released

by phobos | March 3, 2010

Tor 0.2.1.23 fixes a huge client-side performance bug, makes Tor work again on the latest OS X, and updates the location of a directory authority.

Tor 0.2.1.24 makes Tor work again on the latest OS X -- this time for sure!

The Windows and OS X bundles also come with a newer version of Polipo that fixes some stability and security problems.

People using Tor as a client should upgrade:
https://sedvblmbog.tudasnich.de/easy-download

Changes in version 0.2.1.23 - 2010-02-13
Major bugfixes (performance):

We were selecting our guards uniformly at random, and then weighting which of our guards we'd use uniformly at random. This imbalance meant that Tor clients were severely limited on throughput (and probably latency too) by the first hop in their circuit. Now we select guards weighted by currently advertised bandwidth. We also automatically discard guards picked using the old algorithm. Fixes bug 1217; bugfix on 0.2.1.3-alpha. Found by Mike Perry.

Major bugfixes:

Make Tor work again on the latest OS X: when deciding whether to use strange flags to turn TLS renegotiation on, detect the OpenSSL version at run-time, not compile time. We need to do this because Apple doesn't update its dev-tools headers when it updates its libraries in a security patch.
Fix a potential buffer overflow in lookup_last_hid_serv_request() that could happen on 32-bit platforms with 64-bit time_t. Also fix a memory leak when requesting a hidden service descriptor we've requested before. Fixes bug 1242, bugfix on 0.2.0.18-alpha. Found by aakova.

Minor bugfixes:

Refactor resolve_my_address() to not use gethostbyname() anymore. Fixes bug 1244; bugfix on 0.0.2pre25. Reported by Mike Mestnik.

Minor features:

Avoid a mad rush at the beginning of each month when each client rotates half of its guards. Instead we spread the rotation out throughout the month, but we still avoid leaving a precise timestamp in the state file about when we first picked the guard. Improves over the behavior introduced in 0.1.2.17.

Changes in version 0.2.1.24 - 2010-02-21
Minor bugfixes:

Work correctly out-of-the-box with even more vendor-patched versions of OpenSSL. In particular, make it so Debian and OS X don't need customized patches to run/build.

Comments

Please note that the comment area below has been archived.

Anyone besides me having

Anyone besides me having trouble installing it? I keep getting an error msg saying that I don't have permission to access some of the items.

How do I uninstall the old one so that I can install the new one?

http://sedvblmbog.tudasnich.de/faq

http://sedvblmbog.tudasnich.de/faq#HowUninstallTor

When's this going to make

When's this going to make its way into the Debian/Ubuntu repositories? What's the usual lag time between a release, and a new package being added to the repos?

You want to use our

You want to use our deb.torproject.org repo. Ubuntu is literally 18-36 months behind releases.

Debian is generally within a few weeks. Or, keep up to date with http://sedvblmbog.tudasnich.de/docs/debian.html.en

Hi, First thanks for the

Hi,
First thanks for the effort in helping others access internet freely.

I tried the new version 0.2.1.24 both stable and alpha. Sadly it only works once every after reboot, and even that it stop in the middle of bootstrapping process around 60-70%. After that I experienced the same error/warning messages as before:

Mar 04 15:00:06.556 [Notice] Opening Socks listener on 127.0.0.1:9050
Mar 04 15:00:06.556 [Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Mar 04 15:00:06.556 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Mar 04 15:00:06.557 [Error] Reading config failed--see warnings above.

I am using Macbook OS X 10.6.2 with the Security Update 2010-001 ver 1.0.
Do you have any insight or idea of what might be the cause?

Thanks

you already have tor

you already have tor running, it tells you right here:
"[Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?"

You are right. It is really

You are right.
It is really weird, I just assumed because the it said "Tor is not running" on the control panel/icon it is not running; while it is running.

Thanks

I'm having the same problem.

I'm having the same problem. But I can't seem to get Tor to stop running ... assuming that is the problem.

I uninstalled Tor; reinstalled it; I restarted my mac and the first app I started was Vidalia and still got this: ****

Mar 05 18:51:42.863 [Notice] Tor v0.2.2.9-alpha (git-2e159967c9871477). This is experimental software. Do not rely on it for strong anonymity. (Running on Darwin i386)
Mar 05 18:51:42.866 [Notice] Initialized libevent version 1.4.13-stable using method kqueue. Good.
Mar 05 18:51:42.868 [Notice] Opening Socks listener on 127.0.0.1:9050
Mar 05 18:51:42.869 [Warning] Could not bind to 127.0.0.1:9050: Address already in use. Is Tor already running?
Mar 05 18:51:42.869 [Warning] Failed to parse/validate config: Failed to bind one of the listener ports.
Mar 05 18:51:42.870 [Error] Reading config failed--see warnings above. *****

If Tor is already running, how do I get it to stop so that I can reconnect using it?

LoboSolo

Don't where to post this -

Don't where to post this - the certificate for ocewjwkdco.tudasnich.de expired yesterday - give or take a few time zones.

Thanks for installing a new

Thanks for installing a new certificate.

Had to wipe my hard drive

Had to wipe my hard drive today and do a reinstall of OS X (10.4.11) Tiger, and when I installed the new Tor bundle with Firefox 3.6, Tor fails. When I test the settings, I get this error:

Tor proxy test: Local HTTP Proxy is unreachable. Is Polipo running properly?

Am I missing something? There was no old versions, everything was completely wiped.

My logs say:

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 Crashed:
0 libSystem.B.dylib 0x9010c456 _malloc_initialize + 36
1 libSystem.B.dylib 0x9000737c calloc + 29
2 polipo 0x00006373 0x1000 + 21363
3 polipo 0x0000e1d0 0x1000 + 53712
4 polipo 0x00001a36 0x1000 + 2614

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x9010c443 ecx: 0x90000b18 edx: 0x00000008
edi: 0x00000000 esi: 0x00000000 ebp: 0xbffffc28 esp: 0xbffffb90
ss: 0x0000001f efl: 0x00010286 eip: 0x9010c456 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:
0x1000 - 0x2ffff polipo /polipo
0x8fe00000 - 0x8fe4afff dyld 46.16 /usr/lib/dyld
0x90000000 - 0x90171fff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x901c1000 - 0x901c3fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x90bd2000 - 0x90bd9fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib

further note, it looks like

further note, it looks like polipo is crashing when i start vidalia.

i am having an identical

i am having an identical problem with polipo crashing, and therefore unable to connect to local proxy. please post any fixes if you find them.

HI ,mates, i am having the

HI ,mates, i am having the same problem , when i install the vidalia-bundle-0.2.1.25-0.2.7 it work perfect in my Windows Vista Home and Firefox 3.5.6 but when i restart the windows system them Polipo is not started and i get this target:

"Tor proxy test: Local HTTP Proxy is unreachable. Is Polipo running properly?"

and

" DNS: couldn't open /etc/resolv.conf: No such file or directory
Disabling disk cache: No such file or directory
Disabling local tree: No such file or directory
Established listening socket on port 8123. "

and i can not to connect Firefox with Polipo.

How to can i fix it ?

Thank you very much and sorry for my basic english.

I have the same problem. I

I have the same problem. I installed vidalia-bundle-0.2.1.25-0.2.7 and it was working perfecty into my Windows Vista HOme and Firefox 3.5.6 but when i restarted my laptop them Polipo do not executed and i get this target when try to connect firefox with Tor and Polipo:

Tor proxy test: Local HTTP Proxy is unreachable. Is Polipo running properly?

and when i try to execute polipo.exe i get this target:

DNS: couldn't open /etc/resolv.conf: No such file or directory
Disabling disk cache: No such file or directory
Disabling local tree: No such file or directory
Established listening socket on port 8123.

How can i fix this problem??

Thank you and sorry for my basic english.

i am inquiring whether using

i am inquiring whether using bandwidth-based selection will lead evil exit node to get higher probability by rising it bandwidth?

In fact,the Tor doesn't work

In fact,the Tor doesn't work recently,even i use the bridges.i'm a Chinese programer,i think the GFW find a way to block the bridges.maybe they can get the bridges as i did,and forbiden the address.i'm so sad

Where is the comments

Where is the comments section for Tor v0.2.2.9-alpha?

gentle men i need help in

gentle men i need help in the last version 1.3.3

In the beginning it works well

Then the Firefox browser works but the pidgin stopped working !!!

Even it doesn't appear any more.

this is the message that appear to me each time i start the tor 1.3.3

(( vidalia was unable to start the configured IM client ))

I removed it and re install it again and still the same problem .

would you please help me :(

Version1.3.3 = <== is the

Version1.3.3 = <== is the name of downloaded package. what i mean is i downloaded the last Version 0.2.1.24

just to make my message clear .

FYI: I couldn't get Vidallia

FYI: I couldn't get Vidallia to work at first on OS 10.6.2 I noticed in the Console that it had trouble figuring out whether to use the QT Framework inside the bundle or the one in /Library/Frameworks then it would crash with a bad access error.

I removed it from the Vidalia bundle and it then worked. Thought you should know

OK my friend. would you

OK my friend.

would you please write the exact name of the file that i should remove.

just for reminding the problem is the pidgin doesn't work before and this is the message that appear each time i started the program

(( vidalia was unable to start the configured IM client ))

:( this is strange . it was working perfectly !! i didn't miss use with the inner files ever.

just the start icon. what cause of all this :( ??

I am a chinese netizen,my

I am a chinese netizen,my tor doesn't work ,i can't get new valid bridges,help me

Yes, I run a bridge and

Yes, I run a bridge and noticed the block. My message to bridge operators is to reconfigure ip and/or port to beat it, and users need to learn the new connection details.

OK my friend. would you

OK my friend. would you please write the exact name of the file that i should remove. just for reminding the problem is the pidgin doesn't work before and this is the message that appear each time i started the program (( vidalia was unable to start the configured IM client )) :( this is strange . it was working perfectly !! i didn't miss use with the inner files ever. just the start icon. what cause of all this :( ??

I have had various sorts of

I have had various sorts of problems with tor on several different computers with several different Linux OSes with several different versions of kernel and several different browsers.

Currently, I have tor working on only one setup here:

OS: Linux Mint 7 Gloria - X64 Edition
Kernel: 2.6.28-11-generic #42 Ubuntu SMP
Browser: Firefox 3.0.10
TORbutton: 1.2.3
Hardware: AMD64 X2 5600+ CPU

The system that I am trying to get TOR working on is a Toshiba laptop which has this setup:

OS: Kubuntu 9.10 Karmic Koala
Kernel: 2.6.31-14-generic #48 Ubuntu SMP
Browser: Firefox 3.5.7
TORbutton: 1.2.3

I have also tried unsuccessfully to install TOR and get it working on other desktop H/W and S/W. For now, I have given up trying to install and configure TOR, since the result fails in a variety of ways. I am out of time, due to pressing schedule issues with my work.

Can someone recommend any distro which has TOR ALREADY installed and configured to work with an installed and configured browser?

Thanx so much

Angelo

AutoUpdate。AutoUpdate。Aut

AutoUpdate。AutoUpdate。AutoUpdate。AutoUpdate。AutoUpdate。AutoUpdate。AutoUpdate。AutoUpdate。AutoUpdate

Have installed TOR along

Have installed TOR along with the Firefox add-on Torbutton. It says I'm connected and the Vidalia onion turns green, etc. I'm operating a IMac OS 10.5. Though when I go to do the Tor Check it says I'm not connected and when I go to identify my IP, it comes up as my actual IP. What have I missed in terms of my configuration?

Each time i start tor 2.1.14

Each time i start tor 2.1.14 on mandrake 2009 (RPM install) i get a 100% CPU load even if i put ulimit -n 4096 or put ulimit -n 8096 before message: [warn] Failing because we have 1012 connections already. Please raise your ulimit -n.

how can i avoid that 100% CPU LOAD ?

TOP:
Mem: 1009752k total, 968212k used, 41540k free, 129364k buffers
Swap: 3470000k total, 88k used, 3469912k free, 386064k cached
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
27724 toruser 20 0 85332 71m 13m R 100 7.3 231:52.07 tor
3823 mysql 20 0 109m 14m 3752 S 0 1.5 0:35.01

[root@25adsl tor]# netstat -antp | grep -c 9001
1040
[root@25adsl tor]# ulimit -n 4096

service tor start
[root@25adsl tor]# tail -f /var/log/tor/notices.log
Apr 21 12:33:32.392 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor.
Apr 21 12:34:56.989 [notice] Performing bandwidth self-test...done.
Apr 21 14:32:51.877 [warn] Cannot seed RNG -- no entropy source found.
Apr 21 15:32:52.967 [warn] Cannot seed RNG -- no entropy source found.
Apr 21 16:32:53.091 [warn] Cannot seed RNG -- no entropy source found.
Apr 21 17:32:54.259 [warn] Cannot seed RNG -- no entropy source found.
service tor stop
Apr 21 17:41:58.653 [notice] Catching signal TERM, exiting cleanly.

do you see something wrong in my configuration file ?

my uncomented /etc/tro/torrc lines are:

SocksPort 9050 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost
SocksListenAddress 192.168.1.1:9100 # listen on this IP:port also
SocksPolicy accept 192.168.1.1/16
/tor/notices.log
Log notice file /var/log/tor/notices.log.
#RunAsDaemon 1
DataDirectory /var/lib/tor
RelayBandwidthRate 300 KBytes # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 600 KBytes # But allow bursts up to 200KB/s (1600Kbps)
ContactInfo falcon@wanadoo.fr
ExitPolicy reject *:* # no exits allowed
ExitPolicy reject *:*

THANK for answer !

i got very often on mandriva

i got very often on mandriva 2009 with tor 2.1.13 (mandriva rpm install) a 100% CPU load (on 1 of my 4 cpu) and the message rise your ulimit

so i decide to try to install TOR 2.1.25 (tar.gz first time i did that kind of install it seems to succed) et rise my ulimit but i get get again :
-[warn] Failing because we have 991 connections already. !!
-100% CPU load !!!

see below:

history
1053 tar -xzvf tor-0.2.1.25.tar.gz
1054 ls
1055 cd tor-0.2.1.25/
1056 ./configure && make && src/or/tor
1057 updatedb
1058 locate 0.2.1.25
1059 locate 0.2.1.25 | grep bin
1060 locate tor | grep bin
1061 cd /usr/bin/tor/
1062 /usr/bin/tor --version
1063 ls /etc/tor
1064 ls -l /etc/tor/torrc*
1065 service tor start
1066 ulimit -n 8096
1067 tail -50 /var/log/tor/notices.log

[root@25adsl tor-0.2.1.25]# tail -50 /var/log/tor/notices.log
Apr 22 17:32:53.778 [notice] Tor 0.2.1.25 opening new log file.
Apr 22 17:32:53.798 [notice] Parsing GEOIP file.
Apr 22 17:32:54.026 [notice] OpenSSL OpenSSL 0.9.8h 28 May 2008 [90808f] looks like it's older than 0.9.8l, but some vendors have b
ackported 0.9.8l's renegotiation code to earlier versions. I'll set SSL3_FLAGS just to be safe.
Apr 22 17:32:54.111 [notice] Your Tor server's identity key fingerprint is 'Falcontor 02E2CF2C2AD9B09629D05791B7D739160D75C68F'
Apr 22 17:32:56.945 [notice] I learned some more directory information, but not enough to build a circuit: We have no recent networ
k-status consensus.
Apr 22 17:32:57.904 [notice] Bootstrapped 45%: Asking for relay descriptors.
Apr 22 17:32:57.904 [notice] I learned some more directory information, but not enough to build a circuit: We have only 0/1428 usab
le descriptors.
Apr 22 17:32:58.557 [notice] Bootstrapped 57%: Loading relay descriptors.
Apr 22 17:32:58.557 [notice] I learned some more directory information, but not enough to build a circuit: We have only 94/1426 usa
ble descriptors.
Apr 22 17:32:58.697 [notice] Bootstrapped 65%: Loading relay descriptors.
Apr 22 17:32:58.697 [notice] I learned some more directory information, but not enough to build a circuit: We have only 190/1426 us
able descriptors.
Apr 22 17:32:58.796 [notice] Bootstrapped 73%: Loading relay descriptors.
Apr 22 17:32:58.796 [notice] I learned some more directory information, but not enough to build a circuit: We have only 286/1426 us
able descriptors.
Apr 22 17:32:58.992 [notice] We now have enough directory information to build circuits.
Apr 22 17:32:58.992 [notice] Bootstrapped 80%: Connecting to the Tor network.
Apr 22 17:32:59.047 [notice] Bootstrapped 85%: Finishing handshake with first hop.
Apr 22 17:32:59.357 [notice] Bootstrapped 90%: Establishing a Tor circuit.
Apr 22 17:33:02.079 [notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Apr 22 17:33:02.079 [notice] Bootstrapped 100%: Done.
Apr 22 17:33:02.079 [notice] Now checking whether ORPort 82.216.X.X:9001 and DirPort 82.216.X.X:9030 are reachable... (this m
ay take up to 20 minutes -- look for log messages indicating success)
Apr 22 17:33:11.126 [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descrip
tor.
Apr 22 17:33:17.553 [notice] Performing bandwidth self-test...done.
Apr 22 17:35:12.866 [notice] Self-testing indicates your DirPort is reachable from the outside. Excellent.

Apr 22 18:39:17.887 [warn] Failing because we have 991 connections already.

Please raise your ulimit -n.
[root@25adsl tor-0.2.1.25]# ulimit -n 8096
[root@25adsl tor-0.2.1.25]#
[root@25adsl tor-0.2.1.25]# netstat -antp | grep -c 9001
1188

Tasks: 136 total, 6 running, 130 sleeping, 0 stopped, 0 zombie
Cpu(s): 10.1%us, 15.1%sy, 74.6%ni, 0.0%id, 0.0%wa, 0.2%hi, 0.1%si, 0.0%st
Mem: 1009752k total, 902524k used, 107228k free, 206916k buffers
Swap: 3470000k total, 88k used, 3469912k free, 300104k cached

again 100% CPU load:

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
18444 toruser 20 0 96064 73m 12m R 100 7.5 13:50.73 tor <--WRONG CPU LOAD
18539 kg 39 19 64544 44m 1300 R 99 4.5 74:08.12 AK_V8_linux32_s
19514 kg 39 19 64540 44m 1300 R 79 4.5 35:27.51 AK_V8_linux32_s
19611 kg 39 19 64536 44m 1300 R 67 4.5 24:17.13 AK_V8_linux32_s
18346 kg 39 19 64516 44m 1300 R 54 4.5 80:39.71 AK_V8_linux32_s
18592 kg 20 0 26644 11m 7876 S 1 1.2 0:29.77 gkrellm
4779 kg 20 0 22820 19m 2764 S 0 2.0 6:29.32 boinc

[root@25adsl tor-0.2.1.25]# service tor reload
Rechargement de torÂ : [ÃCHEC ]
[root@25adsl tor-0.2.1.25]# service tor status
tor est mort, mais le sous-systÃ¨me reste verrouillÃ©
[root@25adsl tor-0.2.1.25]# service tor stop
ArrÃªt de torÂ : [ OK ]
[root@25adsl tor-0.2.1.25]# service tor start
Lancement de torÂ : Apr 22 18:57:13.615 [notice] Tor v0.2.1.25. This is experimental software. Do not rely on it for strong anonymity. (Running on Linux i686)
Apr 22 18:57:13.616 [notice] Initialized libevent version 1.4.7-stable using method epoll. Good.
Apr 22 18:57:13.616 [notice] Opening OR listener on 0.0.0.0:9001
Apr 22 18:57:13.616 [notice] Opening Directory listener on 0.0.0.0:9030
Apr 22 18:57:13.616 [notice] Opening Socks listener on 127.0.0.1:9050
Apr 22 18:57:13.617 [notice] Opening Socks listener on 192.168.1.1:9100
[ OK ]

[root@25adsl tor-0.2.1.25]# netstat -antp | grep -c 9001
249
[root@25adsl tor-0.2.1.25]#

Tasks: 136 total, 6 running, 130 sleeping, 0 stopped, 0 zombie
Cpu(s): 1.1%us, 1.8%sy, 96.9%ni, 0.1%id, 0.0%wa, 0.0%hi, 0.1%si, 0.0%st
Mem: 1009752k total, 865648k used, 144104k free, 207548k buffers
Swap: 3470000k total, 88k used, 3469912k free, 297120k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
19514 kg 39 19 64540 44m 1300 R 101 4.5 40:38.18 AK_V8_linux32_s
18346 kg 39 19 64516 44m 1300 R 99 4.5 85:57.63 AK_V8_linux32_s
19611 kg 39 19 64536 44m 1300 R 99 4.5 29:03.09 AK_V8_linux32_s
18539 kg 39 19 64544 44m 1300 R 89 4.5 80:06.54 AK_V8_linux32_s
19969 toruser 20 0 57500 42m 13m S 12 4.3 0:11.84 tor

[root@25adsl tor-0.2.1.25]# netstat -antp | grep -c 9001
3701
[root@25adsl tor-0.2.1.25]# ulimit -n 16096

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
18346 kg 39 19 64516 44m 1300 R 101 4.5 118:15.71 AK_V8_linux32_s
19611 kg 39 19 64536 44m 1300 R 101 4.5 60:22.69 AK_V8_linux32_s
19514 kg 39 19 64540 44m 1300 R 99 4.5 72:48.35 AK_V8_linux32_s
18539 kg 39 19 64544 44m 1300 R 91 4.5 110:48.68 AK_V8_linux32_s
19969 toruser 20 0 222m 192m 13m R 6 19.5 2:38.35 tor

as my previous attempts even if i rise "ulimit -n 16000" i got a 100% CPU load !!
my bandwith is
50Mbit/S down
5Mbits/s up

my uncomented line in torrc configuration file are:
(i don't kwon why is still version 2.1.14 instead of 2.1.25)

[root@25adsl ~]# cat /etc/tor/torrc
## Last updated 12 April 2009 for Tor 0.2.1.14-rc
SocksPort 9050 # what port to open for local application connections
SocksListenAddress 127.0.0.1 # accept connections only from localhost
SocksListenAddress 192.168.1.1:9100 # listen on this IP:port also
SocksPolicy accept 192.168.1.1/16
Log notice file /var/log/tor/notices.log
#RunAsDaemon 1
DataDirectory /var/lib/tor
ORPort 9001
Nickname xxxxxxxxxx
RelayBandwidthRate 300 KBytes # Throttle traffic to 100KB/s (800Kbps)
RelayBandwidthBurst 600 KBytes # But allow bursts up to 200KB/s (1600Kbps)
ContactInfo power.falcon@wanadoo.fr
DirPort 9030 # what port to advertise for directory connections
ExitPolicy reject *:* # no exits allowed
ExitPolicy reject *:*

CAN YOU PLEASE HELP ME !!

it seem that i succed to

it seem that i succed to avoid:
-[warn] Failing because we have 4098 connections already. Please raise your ulimit -n.
-followed by anoying 100% CPU load

by using following crontab:
crontab -l
14 * * * * ulimit -n 16000
29 * * * * ulimit -n 16000
44 * * * * ulimit -n 16000
59 * * * * ulimit -n 16000

OS Version: 10.4.11

OS Version: 10.4.11 (Build 8S2167)
Report Version: 4

Command: polipo
Path: /Applications/Vidalia.app/Contents/MacOS/polipo
Parent: Vidalia [5714]

Version: 0.2.9 (0.2.9)

PID: 5716
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x9010c443 ecx: 0x90000b18 edx: 0x00000008
edi: 0x00000000 esi: 0x00000000 ebp: 0xbffffc08 esp: 0xbffffb70
ss: 0x0000001f efl: 0x00010282 eip: 0x9010c456 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:
0x1000 - 0x2ffff polipo /Applications/Vidalia.app/Contents/MacOS/polipo
0x8fe00000 - 0x8fe4afff dyld 46.16 /usr/lib/dyld
0x90000000 - 0x90171fff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x901c1000 - 0x901c3fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
0x90bd2000 - 0x90bd9fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib

I'm a newb, and what is this?

This is a fine bug report,

This is a fine bug report, https://trac.torproject.org/projects/tor/ticket/1572. Now created for you.