Sep 02 01:00:18.492 We tried for 15 seconds to connect to '' using exit 'TemporaryName'. Sep 02 01:00:12.499 We tried for 15 seconds to connect to '' using exit 'TemporaryName'. Sep 02 01:00:03.486 We tried for 15 seconds to connect to '' using exit 'TOR1CINIPAC'. Sep 02 00:59:55.490 We tried for 15 seconds to connect to '' using exit 'TOR1CINIPAC'.

Sep 02 00:59:01.579 Tried for 120 seconds to get a connection to :0. Sep 01 19:21:44.331 Tried for 120 seconds to get a connection to :0. Looks like client functionality is working. Sep 01 04:04:53.179 Tor has successfully opened a circuit. Sep 01 04:04:48.039 Bootstrapped 90%: Establishing a Tor circuit. Sep 01 04:04:44.195 Bootstrapped 85%: Finishing handshake with first hop. Sep 01 04:04:44.195 Bootstrapped 80%: Connecting to the Tor network. Sep 01 04:04:44.195 We now have enough directory information to build circuits. Sep 01 04:04:44.195 OpenSSL OpenSSL 0.9.8p looks like version 0.9.8m or later I will try SSL_OP to enable renegotiation Sep 01 04:04:20.148 Initialized libevent version 1.4.14-stable using method win32. (Running on Very recent version of Windows Service Pack 1 ) Hi, I Got this error on TOR yesterday too, is that some kind of that attacks? (in iran) Only thing I had to do myself, was press the 'Tor' button in 'Firefox-Aurora'. My experience is: I took Aurora out of the bundle and started it from my desktop (e.g.), and everything was fine. Just tell us to start 'Vidalia (Tor)' first and 'Aurora' next to browse the net via Tor. So my suggestion is: just give Mac users the opportunity to think and leave it OUTSIDE the 'Tor_Browser_Bundle'. It's NEVER there once you have quit Aurora, for a simple reason: it's located INSIDE the application bundle ,so when you try to start it 'by hand' from there, MacOS X will tell you: 'Sorry, we don't run this program - it could be broken, damaged, etc.'ĪND: poor Mac users, stupid as they are (like me), won't even FIND it. It ALWAYS starts up with Vidalia, even if (like me) you just want to run a relay in the background, so I always have to quit it again.Ģ. I appreciate very much the new Vidalia package for Mac aka 'Tor_Browser_Bundle', but there's 1 thing I'd like to criticize:Īfter Visalia's startup, it automatically loads that Firefox derivate called 'Aurora' which I find very good and appropriate, but there's 2 things that can make it a pita (pain in sth I forgot):ġ. Enable internationalized bundles by adding and changing the.

Update torbrowser.version string in prefs.js to have more information (see #3504).OS X specific: Rebuild 32-bit binaries with backwards compatibility options so TBB works on OSX 10.5 (closes: #3671).

Update Firefox to 6.0.1, with an additional patch to exclude DigiNotar completely.

These three upgrades together allow you to run the Tor Browser Bundle at the same time as a system Tor, or even multiple copies of the Tor Browser Bundle in different directories, by dynamically choosing available ports. In addition to upgrading Firefox, it includes the latest stable release of Tor 0.2.2.32, Vidalia 0.2.14 and Torbutton 1.4.1. Windows users will see the biggest difference between the old stable bundle and the new stable bundle. The new Tor Browser Bundles are much more feature-rich than the previous bundles, but users may still experience unexpected behavior. We'd originally planned to drop support for Firefox 3.6 bundles on September 10th, but this moved up the date a bit. We build all Firefox 6 binaries from source, with our own set of patches, including some specific to the DigiNotar issue. We were using pre-built binaries on some platforms and owing to the recent DigiNotar debacle, we no longer felt comfortable shipping versions of Firefox that we were unable to patch. There are no longer any stable Tor Browser Bundles with the 3.6.x series of Firefox. We have updated the stable Tor Browser Bundles to Firefox 6.

Tor expert bundle download win64