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://www.torproject.org/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

Tags
stable release
bug fixes
openssl fixes
exit relays
Anonymous

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

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

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!