New Stable released, Tor 0.2.1.21

by phobos | December 30, 2009

Tor 0.2.1.21 fixes an incompatibility with the most recent OpenSSL
library. If you use Tor on Linux / Unix and you're getting SSL
renegotiation errors, upgrading should help. We also recommend an
upgrade if you're an exit relay.

https://decvnxytmk.oedi.net/easy-download

Changes in version 0.2.1.21 - 2009-12-21
Major bugfixes:

  • Work around a security feature in OpenSSL 0.9.8l that prevents our
    handshake from working unless we explicitly tell OpenSSL that we
    are using SSL renegotiation safely. We are, of course, but OpenSSL
    0.9.8l won't work unless we say we are.
  • Avoid crashing if the client is trying to upload many bytes and the
    circuit gets torn down at the same time, or if the flip side
    happens on the exit relay. Bugfix on 0.2.0.1-alpha; fixes bug 1150.

Minor bugfixes:

  • Do not refuse to learn about authority certs and v2 networkstatus
    documents that are older than the latest consensus. This bug might
    have degraded client bootstrapping. Bugfix on 0.2.0.10-alpha.
    Spotted and fixed by xmux.
  • Fix a couple of very-hard-to-trigger memory leaks, and one hard-to-
    trigger platform-specific option misparsing case found by Coverity
    Scan.
  • Fix a compilation warning on Fedora 12 by removing an impossible-to-
    trigger assert. Fixes bug 1173.

The original announcement can be found at http://archives.seul.org/or/announce/Dec-2009/msg00000.html

Comments

Please note that the comment area below has been archived.

Anonymous (not verified) said:

December 30, 2009

Permalink

Will there be an update for tor-devel/alpha users? Should I wait for this or should I change from alpha to stable?

Anonymous (not verified) said:

January 01, 2010

Permalink

Downloaded and installed v 0.2.1.21 (only Tor, no bundle). Starts and runs faster than version .20. Thanks for the improvement! Running Win XP Pro sp3 with Privoxy 3.0.12 (stable).

It still comes with polipo for me :(
Did you install have privoxy and they changed it later? or you already have privoxy from previous version?
polipo sucks.

The bundles we produce all come with polipo. If you don't like polipo, don't install it. You can use torbutton in firefox directly with tor. you'll receive lots of "network errors", but it does work most of the time.

Anonymous (not verified) said:

January 04, 2010

Permalink

I think you guys made a big mistake putting polipo on the release version without even testing it in beta first.

Polipo doesn't work properly with some sites. always blank pages and missing images, never had that problem with privoxy, i could even privoxy to auto-retry broken connection so all pages always load perfectly.

Polipo looks good and fast at first look, but after a while using it you start to see the little things where it fails.

Firefox already has caching (that actually works properly), polipo doesn't do anything for increasing speed that increasing the memory cache size in firefox cant match.

Everything is tested in alpha first, then beta, then release. Polipo has been in the tor browser bundles for 3 years. It may have some problems, but overall it is fast, reliable and supports newer features like http 1.1 and pipelining.

As I've stated numerous times, if the firefox socks layer worked correctly, we wouldn't use an http proxy in between tor and the browser at all.

Anonymous (not verified) said:

January 09, 2010

Permalink

ژانويه 09 23:44:30.343 [Notice] Tor v0.2.1.21. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
ژانويه 09 23:44:30.453 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
ژانويه 09 23:44:30.453 [Notice] Opening Socks listener on 127.0.0.1:9050
ژانويه 09 23:44:30.562 [Notice] Opening Control listener on 127.0.0.1:9051
ژانويه 09 23:44:30.671 [Notice] Parsing GEOIP file.
ژانويه 09 23:44:35.062 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
ژانويه 09 23:44:35.093 [Notice] No current certificate known for authority moria1; launching request.
ژانويه 09 23:44:35.093 [Notice] No current certificate known for authority tor26; launching request.
ژانويه 09 23:44:35.093 [Notice] No current certificate known for authority dizum; launching request.
ژانويه 09 23:44:35.093 [Notice] No current certificate known for authority ides; launching request.
ژانويه 09 23:44:35.093 [Notice] No current certificate known for authority gabelmoo; launching request.
ژانويه 09 23:44:35.093 [Notice] No current certificate known for authority dannenberg; launching request.
ژانويه 09 23:44:35.093 [Notice] No current certificate known for authority urras; launching request.
ژانويه 09 23:44:35.328 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
ژانويه 09 23:44:35.546 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
ژانويه 09 23:45:18.781 [Notice] Renaming old configuration file to "C:\Documents and Settings\BytePtr\Application Data\Vidalia\torrc.orig.1"
ژانويه 09 23:45:20.609 [Notice] Tor v0.2.1.21. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
ژانويه 09 23:45:20.609 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
ژانويه 09 23:45:20.609 [Notice] Opening Socks listener on 127.0.0.1:9050
ژانويه 09 23:45:20.718 [Notice] Opening Control listener on 127.0.0.1:9051
ژانويه 09 23:45:20.718 [Notice] Parsing GEOIP file.
ژانويه 09 23:45:23.968 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
ژانويه 09 23:45:24.031 [Notice] No current certificate known for authority moria1; launching request.
ژانويه 09 23:45:24.031 [Notice] No current certificate known for authority tor26; launching request.
ژانويه 09 23:45:24.031 [Notice] No current certificate known for authority dizum; launching request.
ژانويه 09 23:45:24.031 [Notice] No current certificate known for authority ides; launching request.
ژانويه 09 23:45:24.031 [Notice] No current certificate known for authority gabelmoo; launching request.
ژانويه 09 23:45:24.031 [Notice] No current certificate known for authority dannenberg; launching request.
ژانويه 09 23:45:24.031 [Notice] No current certificate known for authority urras; launching request.
ژانويه 09 23:45:24.312 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
ژانويه 09 23:45:24.328 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
ژانويه 09 23:45:50.125 [Notice] Tor v0.2.1.21. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
ژانويه 09 23:45:50.234 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
ژانويه 09 23:45:50.234 [Notice] Opening Socks listener on 127.0.0.1:9050
ژانويه 09 23:45:50.234 [Notice] Opening Control listener on 127.0.0.1:9051
ژانويه 09 23:45:50.234 [Notice] Parsing GEOIP file.
ژانويه 09 23:45:54.234 [Warning] Problem bootstrapping. Stuck at 5%: Connecting to directory server. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)

Anonymous (not verified) said:

January 16, 2010

Permalink

Jan 14 10:25:14.921 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)

Jan 14 10:33:03.578 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)

Jan 14 10:37:07.093 [Notice] Tor v0.2.1.21. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
Jan 14 10:37:07.093 [Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
Jan 14 10:37:07.093 [Notice] Opening Socks listener on 127.0.0.1:9050
Jan 14 10:37:07.093 [Notice] Opening Control listener on 127.0.0.1:9051
Jan 14 10:37:07.093 [Notice] Parsing GEOIP file.
Jan 14 10:37:30.921 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 1; recommendation warn)
Jan 14 10:37:31.031 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 2; recommendation warn)
Jan 14 10:37:34.859 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 3; recommendation warn)
Jan 14 10:37:34.875 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 4; recommendation warn)
Jan 14 10:37:35.078 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 5; recommendation warn)
Jan 14 10:37:36.078 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 6; recommendation warn)
Jan 14 10:37:37.078 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 7; recommendation warn)
Jan 14 10:37:38.078 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 8; recommendation warn)
Jan 14 10:37:39.078 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 9; recommendation warn)
Jan 14 10:38:01.000 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 10; recommendation warn)
Jan 14 10:38:02.968 [Warning] Problem bootstrapping. Stuck at 80%: Connecting to the Tor network. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 11; recommendation warn)
Jan 14 10:38:04.109 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
Jan 14 10:38:32.031 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 12; recommendation warn)
Jan 14 10:40:21.953 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 13; recommendation warn)
Jan 14 10:40:23.156 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 14; recommendation warn)
Jan 14 10:40:25.015 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 15; recommendation warn)
Jan 14 10:40:37.046 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jan 14 10:40:45.140 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 16; recommendation warn)
Jan 14 10:40:46.015 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 17; recommendation warn)
Jan 14 10:41:07.109 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 18; recommendation warn)
Jan 14 10:41:09.078 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 19; recommendation warn)
Jan 14 10:41:28.984 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 20; recommendation warn)
Jan 14 10:41:31.062 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 21; recommendation warn)
Jan 14 10:41:49.984 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 22; recommendation warn)
Jan 14 10:41:53.046 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 23; recommendation warn)
Jan 14 10:42:10.984 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 24; recommendation warn)
Jan 14 10:42:14.156 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 25; recommendation warn)
Jan 14 10:42:31.984 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 26; recommendation warn)
Jan 14 10:42:36.031 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 27; recommendation warn)
Jan 14 10:42:59.875 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 28; recommendation warn)
Jan 14 10:42:59.953 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 29; recommendation warn)
Jan 14 10:42:59.953 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 30; recommendation warn)
Jan 14 10:42:59.953 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 31; recommendation warn)
Jan 14 10:42:59.968 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 32; recommendation warn)
Jan 14 10:43:00.078 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 33; recommendation warn)
Jan 14 10:43:01.093 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 34; recommendation warn)
Jan 14 10:43:22.078 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 35; recommendation warn)
Jan 14 10:43:23.093 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 36; recommendation warn)
Jan 14 10:43:24.078 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 37; recommendation warn)
Jan 14 10:43:25.093 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 38; recommendation warn)
Jan 14 10:43:26.093 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 39; recommendation warn)
Jan 14 10:43:27.093 [Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (No route to host [WSAEHOSTUNREACH ]; NOROUTE; count 40; recommendation warn)

Sounds like you need a bridge to get access to the rest of the world, or your local network is disconnecting you for some reason.

Windows also has a problem where if it runs out of sockets, it needs a reboot to let Tor work again.

Anonymous (not verified) said:

January 16, 2010

Permalink

Is it possible that the Chinese or Iranians are jamming TOR relays ? Your Captcha is almost unreadable :(

China is blocking the public relays. One has to use bridges to get access to the rest of the Tor network and then on to the open internet.

Iran seems to be just throttling all ssl to make everything slower.

The captcha seems readable by a ton of automated spam bots. It's green on black. If you're green colorblind, that could be a problem.

Anonymous (not verified) said:

January 16, 2010

Permalink

It seems possible that a denial of service attack could be the reason for the connection problems. TOR is definitely an issue for repressive regimes, and they do have plenty of resources to stage such attacks.

Anonymous (not verified) said:

January 20, 2010

Permalink

According to the debug log the [WSAENOTCONN ] message means that the software is failing to connect to the network properly, which isn't a local problem. It's a networking problem that will be addressed soon hopefully. Some of us feel that captchas are simply a way to prevent people from using the internet, since they seem to directly affect users of TOR.

Anonymous (not verified) said:

January 20, 2010

Permalink

Am I the only one having connect problems to the network? I get 'Establishing a Tor circuit failed (done)'. Was working fine up to 2 days ago (Monday).

Or is it the guys 'over there'?

Thanks.

Anonymous (not verified) said:

January 21, 2010

Permalink

It appears that the Mac OS X Security Update 2010-001 (Snow Leopard) disables renegotiation in openssl - breaks current release of Tor (Vidalia) with version 0.2.1.22 of the TOR executable. I thought this problem had been addressed already, but the new update seems to break even the latest version.

http://support.apple.com/kb/HT4004

I'm also experiencing this problem on OS X 10.6.2 with the security update applied running Tor 0.2.1.22. The following appears in the log: [Warning] TLS error: unexpected close while renegotiating. Makes sense if renegotiation has been disabled, but I thought this was fixed with the latest version of Tor since this is now the default behavior of OpenSSL 0.9.8l. I don't understand the complete change in the openssl codebase, but I wouldn't be surprised if Apple did something different in their update.

Yea, apple disabled SSL renegotiation in its entirety. I've spent all night trying to re-enable it. No luck, I don't understand OpenSSL well enough. Guess we have to wait for Apple on this one.

Same problem here. Installed latest sec. update yesterday. Since then: TLS renegotiation error.
Apple support page: no word on "Tor".
Please let me know when this is solved. (Twitter @Whizzbizz)
I'll try to post here, when I get a solution.

yes, everyone knows Apple did not really fixed the OpenSSL issue but made a "by-pass" fix. In fact, this is a mistake, as we can see it with Tor: it does not work anymore. Damn, why? why?
How to disable or uninstall this Apple security fix?

I have met the same error with 10.5.8 after installing the damn SecUpdate 2010-001. I can believe that how apple dare make a such fix. Hope this problem would be solved soon.
I wasted a whole morning for changing bridges!

Anonymous (not verified) said:

January 22, 2010

Permalink

http://archives.seul.org/or/talk/Jan-2010/msg00161.html

"You should upgrade to Tor 0.2.1.22 or 0.2.2.7-alpha:
https://decvnxytmk.oedi.net/download.html.en

In early January we discovered that two of the seven directory
authorities were compromised (moria1 and gabelmoo), along with
metrics.torproject.org, a new server we'd recently set up to serve
metrics data and graphs. The three servers have since been reinstalled
with service migrated to other servers.

We made fresh identity keys for the two directory authorities, which is
why you need to upgrade."

Anonymous (not verified) said:

January 23, 2010

Permalink

0.2.2.7-alpha still has the stuck during bootstrapping problem, but it seems to be much less frequent.

Anonymous (not verified) said:

January 24, 2010

Permalink

I too have the Apple completely disabled OpenSSL renegociation problem with latest tor. Wouldn't it be possible to build a statically linked tor binary for OS X with a less restrictive OpenSSL? If the system OpenSSL breaks you just don't use it.

Anonymous (not verified) said:

January 24, 2010

Permalink

OK, so I compiled tor 0.2.1.22 manually linking it to the /opt/local libevent/libssl (the MacPorts versions) and now it works fine. I tried making a static version but apparently compiling static binaries on OS X is a PIA if not impossible.

Install MacPorts if you don't already have it,
install libevent and openssl,
get the tor src
CPPFLAGS="-I/opt/local/include" LDFLAGS="-L/opt/local/lib" ./configure
make all
sudo cp src/or/tor /Applications/Vidalia.app/Contents/MacOS/tor

  • MacPorts if you don't already have it
  • install libevent and openssl
  • get the tor src
  • CPPFLAGS="-I/opt/local/include" LDFLAGS="-L/opt/local/lib" ./configure
  • make all
  • sudo cp src/or/tor /Applications/Vidalia.app/Contents/MacOS/tor

Tks very much for providing a solution. However, with litter computer knowledge, I can not totally understand your description. Would you please show some illustrating pictures. I would appreciate it if you do me a favor to mail me the download link of necessary software and instructions to xianyu185@gmail.com.

Yup it works. Here's a more detailed description

  • Download MacPorts (www.macports.org) & the existing Tor Vidalia if you don't already have it
  • Install libevent and openssl by typing sudo port install libevent and sudo port install openssl in a Terminal (If you don't know what a Terminal is, google it)
  • Download the "Source Tarballs" in the "Available Linux/Unix Downloads" Page
  • In your Terminal, change into the folder(directory) to where you downloaded and uncompressed the source. If you downloaded into Downloads, it is most likely to be in /Users/username/Downloads/tor-version.
    To do this type: cd /Users/username/Downloads/tor-0.2.1.22
  • Then type the following codes:
    • CPPFLAGS="-I/opt/local/include" LDFLAGS="-L/opt/local/lib" ./configure
    • make all
    • sudo cp src/or/tor /Applications/Vidalia.app/Contents/MacOS/tor

You don't have to do all that. You can just run 2 commands

sudo port install tor;  

sudo cp /opt/local/bin/tor /Applications/Vidalia.app/Contents/MacOS/tor

Anonymous (not verified) said:

January 25, 2010

Permalink

my mac powerpc vidalia is not connecting anymore since the recent security update either. has anyone got a fix or workaround for me please

Anonymous (not verified) said:

January 26, 2010

Permalink

I installed openssl and libevent from mac ports, instead of compiling from source I then installed the mac ports version of tor and linked vidala to the new binary in /opt/local/bin/tor

Seems to work so far...

Anonymous (not verified) said:

January 27, 2010

Permalink

PLEASE CREATE A PROPER FIX for MAC OS X asap please.
The new security update has locked me out!!

Anonymous (not verified) said:

January 28, 2010

Permalink

I'm trying to do the fix and I've installed Mac Ports on my macbook running 10.5.8, but I don't exactly understand how to

get the tor src
CPPFLAGS="-I/opt/local/include" LDFLAGS="-L/opt/local/lib" ./configure
make all
sudo cp src/or/tor /Applications/Vidalia.app/Contents/MacOS/tor

just a little more explanation would be helpful. Thanks!

Anonymous (not verified) said:

January 30, 2010

Permalink

On Mac OS 10.5.8 I had the same problems as described above. With fink I did
fink install tor
Then in Vidalia I changed the Tor-Application to
/sw/bin/tor
Now everything is fine, Tor works again.

Anonymous (not verified) said:

January 31, 2010

Permalink

I tried to use the above fix, but when I tried to install libevent I got the following eror. Any ideas?

Error: Target org.macports.configure returned: configure failure: shell command " cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_libevent/work/libevent-1.4.13-stable" && ./configure --prefix=/opt/local --mandir=/opt/local/share/man " returned error 77
Command output: checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... no
checking for mawk... no
checking for nawk... no
checking for awk... awk
checking whether make sets $(MAKE)... no
checking for gcc... /usr/bin/gcc-4.0
checking for C compiler default output file name...
configure: error: in `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_ports_devel_libevent/work/libevent-1.4.13-stable':
configure: error: C compiler cannot create executables
See `config.log' for more details.

Error: Status 1 encountered during processing.

Anonymous (not verified) said:

February 11, 2010

Permalink

You really make it seem so easy with your presentation but I find this topic to be really something which I think I would never understand. It seems too complicated and very broad for me. I am looking forward for your next post, I will try to get the hang of it!
Reverse Phone Lookup

Anonymous (not verified) said:

February 16, 2010

Permalink

Having the exact same problem here.
Macports server also seems to be down, can anyone provide an alternate source?

Anonymous (not verified) said:

August 07, 2010

Permalink

vidalia-bundle-0.2.1.26-0.2.9.exe

do any of you actually use tor with polipo on windows ? (windows server 2003).

if you are going to advise us to use polipo then maybe you should visit the polipo website and see what a mess windows installation of polipo is.
e.g. there are several folders that need to be created for polipo to actually run in the first place, usr etc var (with subfolders) and create the resolv.conf file.

When those folders are in place the first thing vidalia does when starting is advise "connecting to the tor network failed (no route to host).

I though the idea of vidalia bundle was to be able to download it, run it under windows and startup tor. That is to be able to run tor without having to set up polipo.

Anonymous (not verified) said:

October 23, 2010

Permalink

i have a problem in installing my tor in red hat 5 linux

this is what the problem is

checking for u_int64_t... yes
checking for u_int32_t... yes
checking for u_int16_t... yes
checking for u_int8_t... yes
checking for libevent directory... (system)
checking whether we need extra options to link libevent... configure: error: Found linkable libevent in (system), but it does not seem to run, even with -R. Maybe specify another using --with-libevent-dir}
[sam@dhcpc0 tor-0.2.2.17-alpha]#

can u give me the solution please .. :(

my email id is pwdumpcracker@ymail.com

Anonymous (not verified) said:

November 12, 2010

Permalink

Hello, everybody!
I want to use tor browser, but can't do it on my job.
Here you can find "Massage log" without bridge and then with it.
---------------------
[Notice] Tor v0.2.1.26. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
[Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
[Notice] Opening Socks listener on 127.0.0.1:9050
[Notice] Opening Control listener on 127.0.0.1:9051
[Notice] Parsing GEOIP file.
[Notice] OpenSSL OpenSSL 0.9.8l 5 Nov 2009 looks like version 0.9.8l; I will try SSL3_FLAGS to enable renegotation.
[Notice] We now have enough directory information to build circuits.
[Notice] Bootstrapped 80%: Connecting to the Tor network.
[Notice] Bootstrapped 85%: Finishing handshake with first hop.
[Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 10; recommendation warn)
[Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 11; recommendation warn)
[Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 12; recommendation warn)
[Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 13; recommendation warn)
[Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 14; recommendation warn)
[Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (DONE; DONE; count 15; recommendation warn)
------------------------------
[Notice] Tor v0.2.1.26. This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation] {terminal services, single user})
[Notice] Initialized libevent version 1.4.13-stable using method win32. Good.
[Notice] Opening Socks listener on 127.0.0.1:9050
[Notice] Opening Control listener on 127.0.0.1:9051
[Notice] Parsing GEOIP file.
[Notice] OpenSSL OpenSSL 0.9.8l 5 Nov 2009 looks like version 0.9.8l; I will try SSL3_FLAGS to enable renegotation.
[Notice] new bridge descriptor 'Unnamed' (cached)
[Notice] Bootstrapped 5%: Connecting to directory server.
[Notice] new bridge descriptor 'unknow' (cached)
[Notice] new bridge descriptor 'PimPamLacasitos' (cached)
[Notice] We now have enough directory information to build circuits.
[Notice] Bootstrapped 80%: Connecting to the Tor network.
[Notice] Bootstrapped 85%: Finishing handshake with first hop.
[Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 4; recommendation warn)
[Warning] Problem bootstrapping. Stuck at 85%: Finishing handshake with first hop. (Socket is not connected [WSAENOTCONN ]; NOROUTE; count 5; recommendation warn)
[Notice] no known bridge descriptors running yet; stalling
[Notice] Our directory information is no longer up-to-date enough to build circuits: No live bridge descriptors.
---------------------------
If somebody knows what the problem is, or what i should do, please let me know here or palyanitsyn@ya.ru
Thanks!