New Tor Browser Bundles

We have updated the stable Tor Browser Bundles to Firefox 6.

There are no longer any stable Tor Browser Bundles with the 3.6.x series of Firefox. 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. We build all Firefox 6 binaries from source, with our own set of patches, including some specific to the DigiNotar issue.

We'd originally planned to drop support for Firefox 3.6 bundles on September 10th, but this moved up the date a bit. The new Tor Browser Bundles are much more feature-rich than the previous bundles, but users may still experience unexpected behavior. Please report all bugs to https://trac.torproject.org/.

Windows users will see the biggest difference between the old stable bundle and the new stable bundle. 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. 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.

https://www.torproject.org/download

Tor Browser Bundle (2.2.32-2)

khled.8@hotmai.com

September 01, 2011

Permalink

There seems to be a bug in the Windows version: starting the included Firefox fails. Vidalia complains about not being able to start the browser. When trying to start FirefoxPortable, it complains about a misssing App\Firefox\firefox.exe.

Test was on Win XP.

Yes, SP3 is installed. I also installed some missing security updates and checked again, bit still get that error. Is there any other useful information I could provide?

Thanks for your help.

Could you try editing the FirefoxPortable\FirefoxPortable.ini file mentioned below, and changing 'firefox.exe' to 'tbb-firefox.exe' and then relaunching? Does that do anything (good or bad)?

Changing firefox.exe to tbb-firefox.exe in FirefoxPortable\FirefoxPortable.ini does not have any effect. After renaming tbb-firefox.exe to firefox.exe in FirefoxPortable\App\Firefox I see a start attempt in my Process Monitor after launching FirefoxPortable.exe, but firefox.exe terminates itself soon afterwards.

I have a portable Firefox 6 here running fine. It just did an update to 6.0.1 when I opened it. The version usually in use here is not the one by PortableApps.com (John T. Haller) you are including , but this (German page): http://stadt-bremerhaven.de/mozilla-veroeffentlicht-firefox-6-0-portabl… . Both portable editions work on this machine.

Thanks for checking.

I've confirmed the breakage on a fresh WinXP Home install, and am currently installing SP3 (because I am actually missing system dlls at this point). Could you download http://www.dependencywalker.com/depends22_x86.zip and open the tbb-firefox.exe (or firefox.exe, depending on what you've named it) and tell me if any dlls are missing, and if so, which ones? I have a suspicion that it wants some of the MSVC dlls since we began building from source, but it will take me a bit to confirm.

Thanks for your patience and help in debugging thus far -- I think we will have it fixed soon.

Can you (or anyone else with this problem) please try the test package I have put up here? I have added missing runtime dlls which I believe fix the problem. They did for me.

https://archive.torproject.org/tor-package-archive/technology-preview/t…
https://archive.torproject.org/tor-package-archive/technology-preview/t…

If they work for y'all, I will make new official ones.

While I have no idea what might cause it to work for some and not others, I notice there is a possibly related reference to a "firefox.exe" in FirefoxPortable\FirefoxPortable.ini. I assume this setting is normally ignored, as the correct executable is tbb-firefox.exe.

Thanks for mentioning this. That setting should be ignored, but it's worth changing to see if it fixes anything.

This is the worst version of TOR yet. You can no longer click the "Stop TOR" button and then "Start TOR". You can but this is what happens. TOR connects to the server but when you try to go to a website, you are no longer connected to the internet. The only remedy is to close TOR completely and restart it. This means retrieving all your websites over again. Where is the LAST version of TOR?

WinXP, Service Pack 2 - Vidalia complains about not being able to start the browser. Tor Browser Bundle v.1.3.28 work fine.

Please upgrade to Service Pack 3 and let me know if the problem persists. (I want to make sure you and the user above are using the same sets of installed updates.)

I appreciate very much the new Vidalia package for Mac aka "Tor_Browser_Bundle", but there's 1 thing I'd like to criticize:

After 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):

1. 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.

2. 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..."

AND: poor Mac users, stupid as they are (like me), won't even FIND it.

So my suggestion is: just give Mac users the opportunity to think and leave it OUTSIDE the "Tor_Browser_Bundle".

Just tell us to start "Vidalia (Tor)" first and "Aurora" next to browse the net via Tor .

My experience is: I took Aurora out of the bundle and started it from my desktop (e.g.), and everything was fine. Only thing I had to do myself, was press the "Tor" button in "Firefox-Aurora".

The Tor Browser Bundle is supposed to run a browser, pre-configured to be safe to use. Users often accidentally configure their browsers incorrectly in ways that can de-anonymize them, forget to toggle their Tor state with Torbutton, and various other potentially harmful things. If you only want to run a relay, or you want to run a browser separately from your Tor instance, the Tor Browser Bundle is not the right application to be using -- you might prefer to use the Vidalia bundle mentioned on our download page.

As for running Tor only, without Vidalia, on OSX, we don't currently have any packages for that. For most users, Vidalia is necessary for configuring other options, such as adding bridges when they are unable to access the normal Tor network (because of firewalls or some other reason). If you want to learn more about setting up Tor by itself without Vidalia, let me know and I'll try to help.

I get along well using Vidalia to configure "Tor". Thanks you for your offer.

Hi, I Got this error on TOR yesterday too, is that some kind of that attacks? (in iran)

Sep 01 17:46:19.526 [Warning] Tried connecting to router at 194.204.30.253:9001, but identity key was not as expected: wanted 70C9CA9DCB85CC13B7861CB33228997B13F2C745 but got CF47ABECBF0D29C25444BF0C2497AD73DEE67AFD.

full source below
++++++++++++++++++
Sep 01 04:04:20.039 [Notice] Tor v0.2.1.30. This is experimental software. Do not rely on it for strong anonymity. (Running on Very recent version of Windows [major=6,minor=1] Service Pack 1 [workstation] {terminal services, single user})
Sep 01 04:04:20.148 [Notice] Initialized libevent version 1.4.14-stable using method win32. Good.
Sep 01 04:04:20.148 [Notice] Opening Socks listener on 127.0.0.1:9050
Sep 01 04:04:20.148 [Notice] Opening Control listener on 127.0.0.1:9051
Sep 01 04:04:20.148 [Notice] Parsing GEOIP file.
Sep 01 04:04:44.195 [Notice] OpenSSL OpenSSL 0.9.8p 16 Nov 2010 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Sep 01 04:04:44.195 [Notice] We now have enough directory information to build circuits.
Sep 01 04:04:44.195 [Notice] Bootstrapped 80%: Connecting to the Tor network.
Sep 01 04:04:44.195 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
Sep 01 04:04:48.039 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
Sep 01 04:04:53.179 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Sep 01 04:04:53.179 [Notice] Bootstrapped 100%: Done.
Sep 01 17:46:19.526 [Warning] Tried connecting to router at 194.204.30.253:9001, but identity key was not as expected: wanted 70C9CA9DCB85CC13B7861CB33228997B13F2C745 but got CF47ABECBF0D29C25444BF0C2497AD73DEE67AFD.
Sep 01 19:21:44.331 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)
Sep 02 00:59:01.579 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)
Sep 02 00:59:55.490 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'TOR1CINIPAC'. Retrying on a new circuit.
Sep 02 01:00:03.486 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'TOR1CINIPAC'. Retrying on a new circuit.
Sep 02 01:00:12.499 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'TemporaryName'. Retrying on a new circuit.
Sep 02 01:00:18.492 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'TemporaryName'. Retrying on a new circuit.
Sep 02 01:00:27.514 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Amunet4'. Retrying on a new circuit.
Sep 02 01:00:33.506 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Amunet4'. Retrying on a new circuit.
Sep 02 01:00:45.518 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'chomsky'. Retrying on a new circuit.
Sep 02 01:00:48.513 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'chomsky'. Retrying on a new circuit.
Sep 02 01:01:00.526 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'bach'. Retrying on a new circuit.
Sep 02 01:01:03.520 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'bach'. Retrying on a new circuit.
Sep 02 01:01:19.537 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Amunet5'. Retrying on a new circuit.
Sep 02 01:01:19.537 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Amunet5'. Retrying on a new circuit.
Sep 02 01:01:34.557 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'tordienet'. Retrying on a new circuit.
Sep 02 01:01:34.558 [Notice] Tried for 134 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 02 01:01:34.558 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'tordienet'. Retrying on a new circuit.
Sep 02 01:01:34.559 [Notice] Tried for 126 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 02 01:02:11.569 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Amunet6'. Retrying on a new circuit.
Sep 02 01:02:26.592 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Amunet9'. Retrying on a new circuit.
Sep 02 01:02:41.570 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'TOR1CINIPAC'. Retrying on a new circuit.
Sep 02 01:02:56.581 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 02 01:03:11.589 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'rainbowwarrior'. Retrying on a new circuit.
Sep 02 01:03:26.599 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Hermes42'. Retrying on a new circuit.
Sep 02 01:03:30.592 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'Hermes42'. Retrying on a new circuit.
Sep 02 01:03:41.606 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 02 01:03:41.606 [Notice] Tried for 127 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 02 01:03:45.601 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 02 01:04:00.611 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'raskin'. Retrying on a new circuit.
Sep 02 01:04:15.615 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'desync'. Retrying on a new circuit.
Sep 02 01:04:30.617 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'chaoscomputerclub13'. Retrying on a new circuit.
Sep 02 01:04:45.619 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'gpfTOR7'. Retrying on a new circuit.
Sep 02 01:05:00.636 [Notice] We tried for 15 seconds to connect to '[scrubbed]' using exit 'jipsee'. Retrying on a new circuit.
Sep 02 01:05:00.636 [Notice] Tried for 125 seconds to get a connection to [scrubbed]:80. Giving up.
Sep 02 01:25:52.193 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)
Sep 02 01:30:05.283 [Notice] Tried for 120 seconds to get a connection to [scrubbed]:0. Giving up. (waiting for socks info)

Good question. I don't think it's an attack. You can see on https://metrics.torproject.org/relay-search.html?search=194.204.30.253+… that the relay changed its identity key during the course of the day (WaMjf6... later in the day vs z0er7L8N... earlier in the day).

As for all your timeouts, you might enjoy upgrading to Tor 0.2.2.32. :)

Same problem as Anonymous on XP. I have SP3 and all security updates installed.

Can you try what I suggested above, and edit the FirefoxPortable\FirefoxPortable.ini to change 'firefox.exe' to 'tbb-firefox.exe'?

If that doesn't work, can you try renaming FirefoxPortable\App\Firefox\tbb-firefox.exe to firefox.exe and tell me if you are able to run just FirefoxPortable? (Once you do that, you should be able to double click on FirefoxPortable.exe in the main FirefoxPortable directory.)

I extracted Tor Browser Bundle for Windows and I can use it quite good in XP (SP3). There is no problem.
But I installed (the same in Windows XP, SP3) Tor Bridge Bundle and It start automatically with system start, so, I don't understand how it function, I checked for any Danish Flag in Tor Browser Bundle (settings-->Network Map) and I found only one but it was not my PC. I thought I will be part of Tor Network when I install Tor Bridge Bundle, but I think I am wrong. But when I try to Exit, I get question: You are currently running relay and terminating will interrupt any open connection from client, would you like to shutdown gracefully and give time to client to find new relay?
So, what is purpose of Tor Bridge Bundle? And what should I do to become part of Tor Network? I use University computer, so I hope it is not problem, it is working only during the day.

I have one more question, Tails Linux is part of Tor project, as I understood, so, I use Tails Live CD and USB, will they update Tails because you published new Tor bundles? I don't understand if Iceweasel is the same as Firefox and if we have Firefox 6.0.1, and new Tor bundles, I suppose Tails iso file should be updated.

Okay, I read more in the meantime and I understood that Bridge Bundle means that my IP will not be listed publicly in Map of Tor Network, bridges are hidden relays, but after 2 days, I don't see that anyone used my bridge, it means I am not contributing to Tor Network.
At other side, if I become part of public Tor Network, my IP is listed publicly and I use university PC, it means I can get problem with administrator. so, I would be more happy if I can be public relay (public Tor Network) but with hidden IP address. I don't know if it is possible? Beside it, is it possible to hide from admin (of university computer network) that I use university PC for Tor Network?
So, I am interested to contribute to public tor network, to be public relay, but to hide my IP address (and to protect myself from administrator at university).

First: I'm NOT an expert, but I've been running Tor for nearly two years now, so I can tell you: be a little patient. You will be named in the list after 1 hour or so. Don't expect to find your name there immediately after having started Tor.
If you get this message ("You're currently running a relay"...etc.) when quitting, you're in fact running "Tor" and running a Tor relay. But this list is not updated at once. It takes some time...

I've experience the same issues with this release.

Tor will not be able to connect at all. The Bootstrapping works fine according to the log, but from that it just sits at the "Connecting" stage according to the loading bar.

Apart from that I've noticed that Firefox isn't even configured to be run after Tor connects to the network successfully.

I've tried this on 3 Windows 7 Systems, fully patched. The 3.6 Firefox included version worked fine, I could have just sticked with that and manually removed the compromised Certs.

Update on my situation.

I've disabled the automatic Port configuration via Vidalia. And Tor was able to connect properly.

The machine is using a Application based Firewall. Giving Tor temporary access to WAN allowed it to Bootstrap but couldn't go forward.

After disabling:

Tor bootstraps like before, and it can finally establish a connection to the Tor network. But now Firefox won't connect properly.

The Proxy settings are wrong. Firefox is missing the HTTP and SSL information that was present in the previous versions. I assume this is why it won't work correctly unpacked.

I hope you guys still offer a archive of previous versions because this is completely unusable now without tinkering after deployment.

I'm not the OP, but I had the same problem, and the Firefox in your test package works just fine.

I'm the OP.

I've tried using it, and some testing gave me a clear indication on what the problem is.

When you extract Tor Browser for the first time and run it, you need to be sure Vidalia/Tor can connect using any port it wants. Else you will get a error saying that the file with the Port that Tor uses is missing.

From that moment on, Tor will be unable to connect on some occasions, and Firefox will 99% of the time be unable to connect as well.

I've tried this out, works by the book everytime. Firewall on, if you don't allow Tor to connect with it's choosen port: Boom, everything goes wrong.

Firewall off: Tor will connect normally, Firefox will connect via Tor just fine.

The reason why I didn't notice this before is because I wasn't doing Clean runs (Delete previous extract, extract again).

Could I use Geolock to change the country of my exit node in Tor ? It's safe? http://code.google.com/p/geolock/

The code appears to be safe and isn't sending any personal information anywhere except for your local machine. The logging functionality might be a concern if you aren't encrypting files on your computer.

In my opinion, periodically switching identities/exit nodes can enhance anonymity. This code seems to essentially be just an automated way of switching identities based on your preferences and your currently obtainable IP address. It appears to be obtaining your exit node IP address the same way that https://torcheck.xenobite.eu/ does.

Designs like geolock are really harmful to the Tor network. Tor makes a new circuit shorter after you use a current one -- if you don't use it, it won't make a new one. Your geolock constantly "ruins" every circuit it builds, so Tor is constantly making new ones, putting unnecessary load on the network.

You'll be way happier (and the Tor network will be too!) if you just specify the exit country in your torrc config file, as https://www.torproject.org/docs/faq#ChooseEntryExit suggests.

I would agree...However, I've noticed that specifying Entry/Exit nodes (even with StrictExitNodes set to 1) doesn't always seem to work. For example, setting ExcludeExitNodes {us} and StrictExitNodes 1 will still result in an occasional ExitNode in the United States. Perhaps if Tor/Vidalia paid more attention to the torrc file then there wouldn't be a need for programs like GeoLock

Same problem as above. FRESH INSTALL sp3 and security updates. Firefox 6 works fine. Vidalia can't start firefox. No other software installed!

Changing filenames and so forth does nothing.

This is a pretty serious bug. It may have something to do with lacking run-time libraries such as visual c or what have you, as I have none installed. (fresh install).

Yes, it was lacking some runtime libraries. I have added them, can you please tell me if the fix works for you?

https://archive.torproject.org/tor-package-archive/technology-preview/t…
https://archive.torproject.org/tor-package-archive/technology-preview/t…

Thanks!

This release solved the problem. Excellent work! I like the new features.

if im running 3.6 on windows 7 your saying i should upgrade to firefox 6 with tor? i thought 3.6 was more secure and anonymous because of firefox 6 browser fingerprinting? and what about tails running older version of tor is that still safe? thank you.

I don't understand if I can I use Geolock to change the country of my exit node in Tor. It's safe? Here is the code: http://code.google.com/p/geolock/ . I'll appreciate your answer.

WinXP, Service Pack2. tor-browser-2.2.32-UNOFFICIAL_en-US.exe work fine. Thanks!

Hi! Only a question. What happen with Polipo? It Isn't in this version, right? Thanks.

Correct. We no longer ship polipo.

I like to run TBB alongside my relay running as a Windows (XP) service, connecting to the existing process. I do this because TBB is all preconfigured and stuff and seems to be the lowest common denominator anonymity-set-wise, not to mention the recent direction of supporting the "toggle model" less and a separate browser more (https://blog.torproject.org/blog/toggle-or-not-toggle-end-torbutton). On the other hand, I use the NT service functionality so I can open Vidalia only occasionally when needed to change config, look at the bandwidth graph etc., then close it afterwards, which apparently isn't possible when using a regular Tor process.

This certainly doesn't feel like a very supported configuration, though, at least when it comes to user-friendliness - I've had lots of troubles getting it to work fine. Kind of a shame: I reckon even non-exit relays running on desktop PCs would be most welcome, but it seems extra hard to run BOTH a secure browser and a minimal, non-intrusive relay on the background. Or am I asking for too much? Everything works when running Tor as a regular process - I just don't see much sense in 1) either having Vidalia run all the time or not being able to use it at all to control the relay; and 2) having two Tor processes running at the same time, when only one is needed for client functionality.

For the record, so far I've found the easiest way to do the service installation part (from scratch) to be:
1) Install Vidalia Bundle (check Tor and Vidalia)
2) Manually create an empty torrc in LocalService\Application Data\tor BEFORE installing the service, then point Vidalia to that torrc
3) Configure the relay through Vidalia and manually set a control password (perhaps necessary to start once to update the torrc?)
4) Install the service ("tor --service install")
In my experience, other methods require stuff like manually finding out the hash of a password and editing configs, possibly figuring out a custom path for torrc and using nearly undocumented command line options ("-install -options", not in manual, taken from Tor wiki). It easily gets confusing.

On to the point, a bug with my setup:
In previous versions, TBB's Vidalia recognized the running service and asked for the control password that was set up in advance. The settings dialog acquired the right settings from the service. No problems.

With the new 2.2.32-2 TBB, however, starting with the default config (and the service running) results in the error message:
Vidalia can't find out how to talk to Tor because it can't access this file: ./Data/Tor/port.conf

Here's the last error message:
No such file or directory

Clicking "Retry" in the dialog lets you enter the password, but that just gives the same error message again.

Removing the line "AutoControl=true" from Data\Vidalia\vidalia.conf fixes it.

When first trying 2.2.32-2, I instead unticked "Configure ControlPort automatically" from TBB's Vidalia and restarted. It let me connect to the running Tor service. In that case, though, Vidalia apparently replaces the previous settings (!) in LocalService\Application Data\tor\torrc with its own defaults (e.g. run as client only). Not too desirable.

Some general paths to consider to simplify things for Joe Desktop Relay (who possibly doesn't want to clutter his systray, process list or memory with unnecessary things):
1) Support/test the NT service functionality better, at least so that TBB (by default) bypasses the running service, as it would when using a regular Tor process
2) Make it possible to use Vidalia to connect to a running non-service Tor process and close it without closing Tor
3) Modularize the TBB so that there's a separate downloadable Tor Browser (or maybe just a Firefox profile) that's just like in TBB, but without Vidalia and Tor
4) Something else

This is an evolving area, so I'm really happy to hear your feedback and ideas.

Right now we see a major split between our users: there are generally those who wish to run relays and those who wish to be clients, and not a lot of overlap, so indeed your use case is not well-supported. We've begun pushing TBB as our primary supported client software because we trust ourselves more with browser anonymity/privacy features and also because it is just simpler: as you say, the anonymity set is larger and people are less likely to forget to toggle Torbutton or accidentally behave in de-anonymizing ways.

Vidalia recently got the AutoControl feature which rules in some ways -- e.g., if you're on a random system you don't have to trust the unknown binary calling itself 'tor', you can trust your TBB one instead -- but the behavior for expert users such as yourself is hard to change in a way that doesn't involve going in and editing config files before running things. However, since we are now going to be splitting the types of packages we offer into two distinct models (client and server), we are discussing changing Vidalia to also have a client mode with more of a user-centric UI, and a server mode, which is more minimal / easier to "disappear" but also gives more access to configuration options. I would like to hear your ideas in this area because although I do the Windows packaging, I'm still learning about Windows and things like 'services' are mysterious to me. :)

It sounds like you have a few ideas, and have witnessed a few bugs. Could you please post to https://trac.torproject.org (on the front page you will find a 'group' login so you don't have to make an account, though if you use your own account you can get updates via email too). We can piece them out into separate subtickets afterwards, and hopefully find a good compromise for users such as yourself.

Thanks!

I run a Relay (I guess I am in the "Joe Six Pack" group) and also use Tor to browse the Internet. The issue in my case is terminating Tor accidentally by closing either Vidalia or the portable browser unintentionally. It's pretty easy to do, so I have to be careful. I prefer using Tor with the portable Firefox because the requirements of browsing Tor and browsing the regular Internet with broadband are different. For example, with my regular Firefox I have the addon "Adblock Plus" which slows the browser down not insignificantly. However, with Tor's portable Firefox, it's unnecessary because Flash is not installed. One suggestion I would make is Vidalia tell the user before closing itself the user has 5 (or 10) seconds to hit a key to stop Vidalia from closing. This way accidental closure of Tor would be preventable. In addition, there should be a way to re-launch the portable Firefox in case of accidental closure of Firefox, maybe with a button or option in Vidalia.

After upgrade, can not connect to any hidden service. I know the services are not down because I tried tor2web, and they work. Very frustrating.

I always use the "JonDonym Anonymity test" page with new Tor Browser bundles.

The new Torbrowser default profile in its current version ("tor-browser-2.2.32-2") is *far* more insecure than the default profile of the older version(s) like "tor-browser-1.3.27".

Check it out for yourself!

Test it here: http://ip-check.info/?lang=en

Tor Problem on Errin's blog - 2011-09-04

I have a problem very similiar to some of the others. I have Windows XP Pro with SP3 and all of the most recent Windows updates.

I downloaded the "UNOFFICIAL" update, and the problem remained the same. I even changed "'firefox.exe' to 'tbb-firefox.exe' and then relaunching," but I still got the same results, which you can see below:

============================
Sep 04 13:18:53.765 [Notice] Tor v0.2.2.32 (git-877e17749725ab88). This is experimental software. Do not rely on it for strong anonymity. (Running on Windows XP Service Pack 3 [workstation])
Sep 04 13:18:53.765 [Notice] Initialized libevent version 2.0.14-stable using method win32. Good.
Sep 04 13:18:53.765 [Notice] Opening Socks listener on 127.0.0.1:0
Sep 04 13:18:53.765 [Notice] Socks listener listening on port 1321.
Sep 04 13:18:53.765 [Notice] Opening Control listener on 127.0.0.1:0
Sep 04 13:18:53.875 [Notice] Control listener listening on port 1322.
Sep 04 13:18:53.875 [Notice] Parsing GEOIP file .\Data\Tor\geoip.
Sep 04 13:18:57.921 [Notice] OpenSSL OpenSSL 1.0.0d 8 Feb 2011 looks like version 0.9.8m or later; I will try SSL_OP to enable renegotiation
Sep 04 13:19:00.218 [Notice] We now have enough directory information to build circuits.
Sep 04 13:19:00.218 [Notice] Bootstrapped 80%: Connecting to the Tor network.
Sep 04 13:19:01.421 [Notice] Bootstrapped 85%: Finishing handshake with first hop.
Sep 04 13:19:02.515 [Notice] Bootstrapped 90%: Establishing a Tor circuit.
Sep 04 13:19:04.484 [Notice] Tor has successfully opened a circuit. Looks like client functionality is working.
Sep 04 13:19:04.484 [Notice] Bootstrapped 100%: Done.
============================

Before this time, on and off, I was able to get on the Tor network with the following two editions:

First: tor-browser-1.3.28_en-US
Second: tor-browser-2.2.31-1-alpha_en-US

When I installed the "First" one on top of an earlier edition of the Tor Browser (stable) Bundle, in order to keep my Bookmarks, which I cannot copy from one to another because they are no longer "html" files, but "json" files (what a drag!!!), I was able to get on the Tor network, and the same for the Second.

HOWEVER, when I installed tor-browser-2.2.32-2_en-US on top of the First one, I had this problem, and when I tried to load tor-browser-2.2.32-2_en-US-2011-09-03 by itself, I still had the same problem, and that is when I tried the so-called "UNOFFICIAL" solution plus the Firefox name change that were suggested, and that did not work. I have had similiar problems before on my Desktop PC running Windows XP Home, and on my Netbook running Windows XP Pro as well as on Ubuntu, PCLinuxOS, and Puppy.

I will check back for an answer.

Thank for any help that you can offer.