Tor 0.2.1.20 Released

by phobos | November 13, 2009

Tor 0.2.1.20 fixes a crash bug when you're accessing many hidden services
at once, prepares for more performance improvements, and fixes a bunch
of smaller bugs.

The Windows and OS X bundles also include a more recent Vidalia, and
switch from Privoxy to Polipo.

The OS X installers are now drag and drop. It's best to un-install
Tor/Vidalia and then install this new bundle, rather than upgrade. If
you want to upgrade, you'll need to update the paths for Tor and Polipo
in the Vidalia Settings window.

https://www.torproject.org/easy-download

Changes in version 0.2.1.20 - 2009-10-15
o Major bugfixes:

- Send circuit or stream sendme cells when our window has decreased
by 100 cells, not when it has decreased by 101 cells. Bug uncovered
by Karsten when testing the "reduce circuit window" performance
patch. Bugfix on the 54th commit on Tor -- from July 2002,
before the release of Tor 0.0.0. This is the new winner of the
oldest-bug prize.
- Fix a remotely triggerable memory leak when a consensus document
contains more than one signature from the same voter. Bugfix on
0.2.0.3-alpha.
- Avoid segfault in rare cases when finishing an introduction circuit
as a client and finding out that we don't have an introduction key
for it. Fixes bug 1073. Reported by Aaron Swartz.

o Major features:

- Tor now reads the "circwindow" parameter out of the consensus,
and uses that value for its circuit package window rather than the
default of 1000 cells. Begins the implementation of proposal 168.

o New directory authorities:

- Set up urras (run by Jacob Appelbaum) as the seventh v3 directory
authority.
- Move moria1 and tonga to alternate IP addresses.

o Minor bugfixes:

- Fix a signed/unsigned compile warning in 0.2.1.19.
- Fix possible segmentation fault on directory authorities. Bugfix on
0.2.1.14-rc.
- Fix an extremely rare infinite recursion bug that could occur if
we tried to log a message after shutting down the log subsystem.
Found by Matt Edman. Bugfix on 0.2.0.16-alpha.
- Fix an obscure bug where hidden services on 64-bit big-endian
systems might mis-read the timestamp in v3 introduce cells, and
refuse to connect back to the client. Discovered by "rotor".
Bugfix on 0.2.1.6-alpha.
- We were triggering a CLOCK_SKEW controller status event whenever
we connect via the v2 connection protocol to any relay that has
a wrong clock. Instead, we should only inform the controller when
it's a trusted authority that claims our clock is wrong. Bugfix
on 0.2.0.20-rc; starts to fix bug 1074. Reported by SwissTorExit.
- We were telling the controller about CHECKING_REACHABILITY and
REACHABILITY_FAILED status events whenever we launch a testing
circuit or notice that one has failed. Instead, only tell the
controller when we want to inform the user of overall success or
overall failure. Bugfix on 0.1.2.6-alpha. Fixes bug 1075. Reported
by SwissTorExit.
- Don't warn when we're using a circuit that ends with a node
excluded in ExcludeExitNodes, but the circuit is not used to access
the outside world. This should help fix bug 1090. Bugfix on
0.2.1.6-alpha.
- Work around a small memory leak in some versions of OpenSSL that
stopped the memory used by the hostname TLS extension from being
freed.

o Minor features:

- Add a "getinfo status/accepted-server-descriptor" controller
command, which is the recommended way for controllers to learn
whether our server descriptor has been successfully received by at
least on directory authority. Un-recommend good-server-descriptor
getinfo and status events until we have a better design for them.

Comments

Please note that the comment area below has been archived.

SwissTorExit (not verified) said:

November 13, 2009

Permalink

Hello guys,

I am really happy that Tor 0.2.1.20 are released as stable, now it will interesting to see the new performance of the network since the new "circuit windows" are implemented :)

I recommend to everyone to upgrade your client ...

Well done Torproject :P

Best Regards

SwissTorExit

Anonymous (not verified) said:

November 13, 2009

Permalink

FAIL. Polipo does not allow downloads of files bigger than 30 megabytes. Back to the drawing board.

Anonymous (not verified) said:

November 13, 2009

Permalink

I liked Privoxy. The log window was helpful.

Your captcha here is ridiculous...

yeah, the captcha is ridiculous, my bot can't parse it to spam the blog so I can get paid and not eat three week old rice. please drop the captcha

Anonymous (not verified) said:

November 13, 2009

Permalink

Yeah Privoxy rocks!! Simple conf, for better anonymity:
{ \
+change-x-forwarded-for{block} \
+client-header-filter{hide-tor-exit-notation} \
+crunch-if-none-match \
+hide-if-modified-since{-60} \
+hide-from-header{block} \
+hide-referrer{conditional-block} \
+hide-user-agent{Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.5) Gecko/20091102 Firefox/3.5.5} \
+limit-connect{1-} \
+overwrite-last-modified{randomize} \
+set-image-blocker{pattern} \
}
/

Ron (not verified) said:

November 13, 2009

Permalink

I had to uninstall polwhatever and go back to privoxy from the previous package. I wasted an hour on it. Changing two ports in it configuration renders it a dead duck. It listens on them but doesn't forward to tor. Maybe the ports are hardcoded in the binary? I disabled firewall, ran Wireshark, nothing going on.

SwissTorExit (not verified) said:

November 14, 2009

Permalink

hello,

About polipo, i have the same problem, if i load a few pages in same time, it hang on or really slow..

From privoxy 3.0.13 , i never have performance problem, no more timeout or like early, no more message thatŝ it can't open a page.
I don't see any advantage with polipo actually. Anyway all must free to use what there like :)

Actually i don't like the idea of polipo as preferred proxy for Tor since privoxy are more quick and don't do problem..

It will interesting to really compare both product but only from recent version and see if polipo are really better. All my tests put privoxy up the list ;)

Best regards

Anonymous (not verified) said:

November 14, 2009

Permalink

The reason why Privoxy was used wasn't anonymity?
Developers please give a statetment why it is save not to use Privoxy any more.
(Or add Privoxy back again)

If it's just performance what you want, simply don't use Tor! ;-)

privoxy and polipo have nothing to do with anonymity, merely work arounds to broken firefox socks layer,http://archives.seul.org/or/talk/Aug-2009/msg00188.html

Andrew has stated at least THREE TIMES that if firefox socks wasn't broken, tor wouldn't ship polipo or privoxy. firefox memory cache works just fine, including polipo and privoxy are KLUDGES to FIREFOX'S CRAPPY CODE.

maybe chrome is better, or maybe chrome is laden with google spyware

Good to see that open source is just like closed source. Bugs as old as time are left in with nobody to fix them. lol... Although, I guess those with some programming skillz should send in a patch because Mozilla sure as hell ain't gonna fix it.

Some people have submitted patches over the years. Mozilla hasn't included them or accepted the patches for various reasons. If we start to compile our own firefox, then we'll include the socks layer patches. However, maintaining our own version of firefox isn't a task we can take on right now.

Anonymous (not verified) said:

November 20, 2009

Permalink

Well, that blows. Somebody is fixing your buggy software for free and they reject the offer? Unless the code sucks, I see no reason why they would do this. Better yet, if they don't like the submitted fixes, why don't they just fix it themselves? Sends a bad message that they don't care about security. Well, I kinda figure that since they allowed some addons to install without user intervention...

Anonymous (not verified) said:

November 14, 2009

Permalink

How about an option to do away with the "basic" tab in the new Vidalia?

I'm getting multiple time errors such as this.

"Your Computer's Clock is Potentially Incorrect - Tor has determined that your computer's clock may be set to 1865 seconds in the past compared to the source "DIRSERV:81.169.183.122:9001".

I update with pool.ntp.org so I think it's DIRSERV that has the problem, not me.

Strider (not verified) said:

November 15, 2009

Permalink

Whatever you have done to TOR you have broken it. I installed the new version with Polipo and let it run for several hours and it never connected to TOR. I replaced the cache files with the ones from my old installation and it finally connected. But I could not reach any hidden services other than the core.onion. Half the time it could not find an exit node. I uninstalled and reinstalled the older version with Privoxy and it connected with no problem

Ever since the release, even the older version of TOR has problems finding hidden services, and exit nodes. Plus it is slow to the point of useless now. My guess is that it's because you moved the directory/rendezvous servers, but I'm not a programmer so that's just a guess.

I realize that it's free, but some of us have come to depend on it, and now are in a bind because it doesn't work any more.

I've used TOR for many years now, and for the first time I'm very disappointed in it.

Anonymous (not verified) said:

November 15, 2009

Permalink

perhaps you missed "It's best to un-install
Tor/Vidalia and then install this new bundle, rather than upgrade. If
you want to upgrade, you'll need to update the paths for Tor and Polipo
in the Vidalia Settings window."

We make Tor. I don't know what is TOR. Our testing of the network from various clients shows Tor is getting faster with each release of 0.2.1.x and 0.2.2.x-alpha. Perhaps you had a poor circuit.

And for the record, I do 99.9% of my internet access through Tor, so I get to experience anything going wrong firsthand.

If you disable the proxy, and simply went through browser to Tor directly, do you still have the same problems?

Anonymous (not verified) said:

December 13, 2009

Permalink

I have the exact same issue. I've tried it on 2 Mac computers, one running 10.4 and one 10.5. I drop the package in after doing a full uninstall (even deleted .tor from my home folder), and I get absolutely nothing going on.

Also, the Tor Firefox plugin doesn't seem to know about polipo's new port, which I guess has changed to 8123?

layman (not verified) said:

November 15, 2009

Permalink

The issue where our computers time may be off is shown to be known with the program's auto announcement of it. I have never found my computer's time to be off so what does the problem tell the layman to do?

What do I do and when does the announced possible tor will not work happen?

Thanks for what you do.

If your computer's time is correct, it's possible one of the relays has incorrect time and is causing the error to show up. If you know your time is correct, ignore the warning.

Please define better.

privoxy and polipo serve two different purposes. As someone else commented, if firefox socks layer worked correctly, we wouldn't need a proxy at all.

still testing all of the changes that are going into 1.2.10, including openssl 0.9.8l

Anonymous (not verified) said:

November 20, 2009

Permalink

I've installed 0.2.1.20 cleanly on a brand new laptop.
What bothers me is kind of strange behavior which I never experienced with the earlier versions.
All the routs start with only 2 nodes. When you changed route, the nodes stayed the same.
If I excluded these nodes and re-started Tor, the same picture could be observed with other two: routes changed but the entry guards are stay the same.
Somehow, if I wiped out Tor cache (C:\Documents and Settings\%username%\Application Data\Tor\ or C:\Users\%username%\AppData\Roaming\Tor\), it's reinitialized normally.
What is it? Why 0.2.1.20 works such differently than previous version?

Anonymous (not verified) said:

November 20, 2009

Permalink

I thought the new Tor bundle was broken since I could no longer connect after installing it. It turned out that the problem were the bridges. I had to many bridges (7 out of 10 total) that were unreachable. After I removed the unreachable bridges, Tor worked again.
So, before you add a bridge, better do a ping before.

Anonymous (not verified) said:

November 24, 2009

Permalink

Hello,

I installed the latest stable Vidalia bundle on mac os 10.6.2,
Tor starts but Torbutton's test fails.

polipo is listening on port 8123, so i did replace 8118 by 8123 in Torbutton prefs, to no avail. Does it ring a bell ?

Same... uninstalled the old version, verified that no files existed from the old version, installed new version clean. Torbutton test fails, torproject test page says I'm not using TOR, cannot reach any hidden services. whatsmyipaddress.com shows that my ip address is changing, so it appears that traffic is going through the TOR network.

Phobos, is this a known issue? Is this a config option that we need to change? Is it just me? Come on you guys, help us!

Anonymous (not verified) said:

November 26, 2009

Permalink

(I'm the OP)

This reply covered my problem:

I had leftovers from a previous version. Maybe it's important not to forget to remove ~/.tor and ~/.vidalia

Ugh, I'm having the same problems. I've removed those directories, the .app, and even did a find / -name '*Tor*' and find / -name 'tor*' (plus the same for privoxy) to get rid of the cruft. The drop-in application bundle still isn't working for me at all.

Anonymous (not verified) said:

November 27, 2009

Permalink

This might not be the place for this, but I can't exclude nodes with ExcludeNodes or ExcludeExitNodes in torrc. My tor just won't do what it's told.
This comes up in the vidalia message log:

[Warning] Requested exit node x is in ExcludeNodes or ExcludeExitNodes.. Using anyway.

I think I've seen other ppl with this problem too. Do you know what causes this and are you doing something about it?

That is certainly not an exclusive 0.2.1.20 issue. I remain on 0.2.1.19 for now and experience this using ExcludeExitNodes. I believe it to go back much further (forever maybe). I suspect that there is logic that Tor will only honor this request if enough nodes exists outside the excluded zones for it to carry on its normal business. Having said that, it +appears+ to me that the result is some prioritization, i.e., fewer nodes in the excluded zones utilized than without the argument, but that could be wishful thinking. If nothing else, it gives me an easy to read list in the message log showing me which nodes that I have tried to exclude are used, and that could ultimately have some value.

Anonymous (not verified) said:

November 28, 2009

Permalink

I had downloaded and installed Tor Windows bundles before but the bundles always ran slower than Tor and Privoxy unbundled ( on my computer ). I uninstalled Tor ver.19 and downloaded and installed ver.20 but kept my Privoxy ver.12. No problems with Tor ver.20 with Privoxy ver.12, actually seems to run slightly faster than Tor ver.19. Privoxy hasn't had a new stable version since ver.12. Versions .13,.14 and .15 have all been betas. I have no complaints with Privoxy, but makes me wonder why so many betas and no new stable version? I run Tor on Win XP Pro. sp 3, using Firefox 3.5.5 and K-Meleon 1.5.3.

Anonymous (not verified) said:

January 08, 2010

Permalink

I downloaded TOR, the bundled version with Polipo, which I then uninstalled Polipo and installed Privoxy v 3.0.15. on Windows Server 2008 Enterprise edition. TOR starts and is successful creating a circuit. Firefox 3.5 page shows TOR as enabled, but when I check my TOR configuration at www.check.torproject.org, it reads: " You Are Not Using TOR". When I test the settings in the options of the TOR button I get " Local HTTP Proxy is unreachable. Is Polipo running properly? " I have Privoxy specified to start when TOR starts with the application directory path in the Vidalia interface settings. I've tried everything that I won't attempt to publish here and still no luck. What am I missing here?
Any feedback is greatly appreciated!

Anonymous (not verified) said:

January 08, 2010

Permalink

Here are the ingredients : Privoxy v3.0.15, TOR 0.2.1.21 and FireFox 3.5.6 being configured on Windows. Has anyone tried this recipe and if so, what addtl' spices are required to make this cook?
Are these ingredients any good or do I need to go back to the supermarket.

Anonymous (not verified) said:

November 29, 2009

Permalink

Can someone from the development team explain in technical terms why the proxy server (Privoxy or anyother) is/was needed to be used with tor? I remember it had something to do with the DNS request leaks, correct? Is it still a problem? If other than Firefox browser is used, let's say Opera, is it still necessary to use proxy server (Privoxy, Polipo, etc.) to maintain true anonymity? Sorry, I could not find the definitive answer in the documentation.

An http proxy is not needed between a web browser and Tor for functionality. It's there to work around bugs in the Firefox SOCKS layer. In modern firefox 3.0 and newer, there is an option called "network.proxy.socks_remote_dns" that is set by torbutton. This forces dns lookups over the configured socks proxy server, which with torbutton, is Tor.

Other apps may leak dns requests, these can be captured by setting a DNSPort or iptables tricks, or using a proxy between the app and tor.

Polipo and Privoxy can be used to work around the hardcoded timeouts in the firefox socks layers. If you don't use firefox, then feel free to configure your browser to talk directly to tor as a socks 5 proxy. Just test to see if the browser leaks dns requests.

Anonymous (not verified) said:

November 30, 2009

Permalink

Is the socks layer problem particular to only Firefox? Or is it a problem with any browser that uses the Gecko Runtime Engine ( Seamonkey, K-Meleon, Flock, Camino, Lunascape, etc. )?

Unsure. From what I understand of Gecko, no. Gecko handles the html parsing, not the network interaction. I may be wrong, feel free to correct me.

Uluru (not verified) said:

December 05, 2009

Permalink

I have used the Tor Macosx bundle for two years+. I am
an ordinary user. I thank the Tor project managers for
ceaselessly trying to make this excellent software simpler
and usable by people like me. I try to learn about it all the
time by constantly referring to its documentation but I do
not understand the technical aspect of it.

I am having difficulties with the latest bundle which has
replaced Privoxy with Polipo. At the moment I have Polipo,
tor, Vidalia located in Vidalia.app/Contents. I also have
Vidalia, tor, Torbutton, Privoxy folders in Macintosh HD/
Library. The tor version is 0.2.1.20, Qt 4.3.5. Vidalia 0.2.5.

The Torbutton (excellent extension!) works well with Privoxy
- no problems but when I change to 'new proxy' by replacing
Port 8118 to 8123 (Polipo's port) to try it, tor does not work
because when I check my IP it is my real IP with info on my
default browser etc! When I use the Test Button in Torbutton
Preferences I get an 'Internal Error' or sometimes 'Test failed'.
It seems that the requests I make are not going tor.

My OS is osx 10.5.8. I thank in advance anyone who is able to
help me try this new proxy - Polipo.

My current 'tor settings' are:
/Applications/Vidalia.app/Contents/MacOS/tor
/Applications/Vidalia.app/Contents/MacOs/polipo

and yet Torbutton is configured to use Privoxy.....and
it is working OK!

Thanks again

Uluru

If you are using our packages, we reconfigure polipo to work on port 8118. Look at the polipo config file installed on your system.

Anonymous (not verified) said:

December 15, 2009

Permalink

thanx Tor team for your hard working to maintain the best for Tor as you can.

i just download new version, but after reading these many complain comments, i will Install it later.

Actaully iam clasic man and don't like speed change in my life. So i will stay with Privoxy.

Anonymous (not verified) said:

December 15, 2009

Permalink

Date/Time: 2009-12-15 14:05:03.869 -0800
OS Version: 10.4.11 (Build 8S2167)
Report Version: 4

Command: Vidalia
Installed the new bundle and this is what I get. Broken tor.

Isnt this a problem from a year ago?

Path: /Applications/Vidalia.app/Contents/MacOS/Vidalia
Parent: WindowServer [65]

Version: 0.2.6 (0.2.6)

PID: 268
Thread: Unknown

Link (dyld) error:

Library not loaded: /usr/lib/libiconv.2.dylib
Referenced from: /Applications/Vidalia.app/Contents/MacOS/Vidalia
Reason: Incompatible library version: Vidalia requires version 7.0.0 or later, but libiconv.2.dylib provides version 5.0.0

Anonymous (not verified) said:

December 18, 2009

Permalink

hi,This is from china.
The new tor , which was realeased on Oct 10th,vidalia-bundle-0.2.1.20-0.2.5.exe, can not run in my pc. It seams that the browser can not connect to any web site. so, I had to use the outdated one(version 0.2.0.34) .

P.S. Thanks very much for what torproject.org have done. :)

Anonymous (not verified) said:

December 18, 2009

Permalink

The same with me (Windows Vista Home Basic, Internet Explorer 8). The settings for the proxy server in Options are 127.0.0.1, port 8118, but I cannot connect to any site. The previous version works fine. It's the second time I'm trying to start working with the new version of Tor, the first time I have uninstalled it and returned to the previous version. Help, please.

Anonymous (not verified) said:

December 19, 2009

Permalink

I am realy upset about there is no reason pointed by the developers why privoxy is removed. that policrap didn t work by default installation.
thx for nothing...

We've responded at least 5 times as to why we switched. Polipo is caching, supports http 1.1 pipelining, and is currently maintained.

If you don't like polipo, don't use it. Setup Firefox or your favorite browser to point directly at localhost:9050. The default configuration is well-tested. Sorry it didn't work for you as you expected.

Anonymous (not verified) said:

December 22, 2009

Permalink

Serious Problem: Tor 0.2.1.20 and Mac OSX 10.4.11

I've been using the Tor bundle for the last year with no problem. A couple of days ago I was prompted to upgrade to the the new version of the package. I duly did the upgrade and replaced the existing Vidalia package with the new version in my Applications folder. When I clicked to open the package, nothing at all happened. I then read that it was better to uninstall the package before downloading the new one. So I followed the uninstall instructions on the torproject website, deleting all trace of Tor, Vidalie etc on my system (applications, library). I then downloaded the new version of the package again. I dragged the package into the applications folder and then tried to open it. Very briefly the onion icon flashed up on the dock but then immediately disappeared. Then nothing else. I cannot make the package work. Can anyone help? I live in a country where many normal websites are blocked including the BBC. So without Tor I am cut off. Thanks.

Anonymous (not verified) said:

December 27, 2009

Permalink

Regression: Tor 0.2.1.20 on OS X 10.6.2

I had been using Tor 0.2.19 for more than half a year and it worked well. Then I upgraded to Tor 0.2.1.20 early this month. And then 0.2.1.20 worked fine for a while. Then it always failed with "Problem bootstrapping. Stuck at 10%: Finishing handshake with directory server." Then I downgraded to 0.2.1.19 by reinstalling the old package, and everything works again. Then I reinstall 0.2.1.20 and this time it works well for about three days and then "Stuck at 10%" again.

Now I downgraded to 0.2.1.19 again and I think I am stuck with it until the problem is fixed in some later version.

Supplement: When I was and am using 0.2.1.19, I using bridges because of ISP's blocking of Tor. When I switched to 0.2.1.20 and during its normal first two or three days, it worked regardless whether the bridges are configured or not. So I suspect maybe some misconfiguration in 0.2.1.20 package (or Vidalia) make the bridge configuration disabled even when it is configured on the UI.

Anonymous (not verified) said:

January 04, 2010

Permalink

No, it seems irrelative to the location, because everything on my MacBook Pro are the same except Tor version. I mean, the same environment, when upgrade to 0.2.1.20, fail, downgrade to 0.2.1.19, success. There are the same bridges, and the result is different by different Tor versions. It's hardly the problem of blocking.

I am experencing the same problem. I don't think it has anything to do with the tor bridge, since i have the same configuration of tor bridges on both my pc and mac. Tor works well on my pc (0.2.1.19) with bridges, but does not on my mac (0.2.1.21 or 0.2.1.22) with the same bridges set. I believe it's a bug in 0.2.1.20 and any newer versions of tor (mac osx)

Anonymous (not verified) said:

January 09, 2010

Permalink

I downloaded TOR, the bundled version with Polipo, which I then uninstalled Polipo and installed Privoxy v 3.0.15. on Windows Server 2008 Enterprise edition. TOR starts and is successful creating a circuit. Firefox 3.5 browser page shows that TOR is enabled, but when I check my TOR configuration at www.check.torproject.org, it reads, " You Are Not Using TOR". When I test the settings in the options of the TOR button I get "Local HTTP Proxy is unreachable. Is Polipo running properly?". I have Privoxy specified to start when TOR starts via the directory path in the Vidalia interface settings. I'm not sure why it keeps referring to Polipo.I'm not sure why TOR seems to being working but is not being used by my browser. When I check the status of Privoxy, it checks out as successful.What am I missing here? Any feedback is greatly appreciated!

Anonymous (not verified) said:

February 01, 2010

Permalink

Hi,
I am a brand new Tor user; I just downloaded and installed the Browser bundle for Firefox with Polipo.
I admit that I am quite ignorant of how it all works, but so far, It works excellent for me in all my browsing. Impressive and Fascinating to say the least!

I am running Win XP home and of course the Firefox included in the bundle.
When I log on MyBrowserInfo.com, it reads my UserAgent String, although the IP address is random (So cool!)
Just one question: hopefully a simple one due to my ignorance:
How can I configure to hide my UserAgent String?

Thanks for a Great Network and for an answer...

Anonymous (not verified) said:

June 09, 2010

Permalink

Oops, I broke it!

So there are people that really know what they're doing, and then on the other side, there's me. :/ I installed Tor and Polipo in an attempt to attain some privacy. Specifically, I wanted to appear to have a different IP each time I visited a particular site (most votes win, IP tracking in use). Anyhow, I don't think I achieved what I was after and so I uninstalled both Tor and Polipo. I reinstalled privoxy and thought life would be back to normal. Now, my browser is incredibly slow. REALLY slow. So now I am humbled and am sheepishly asking for help as I realize I was medling where I didn't belong. Any suggestions toward restoring my previous browser speed would be very appreciated. Thanks

Anonymous (not verified) said:

June 20, 2010

Permalink

I tried to use proxifier with TOR but it will always report "Potentially dangerous..." and i cant download a file completely from my mediafire because it will always close the connection. Pls what did i do wrong? Thank you

Anonymous (not verified) said:

July 15, 2010

Permalink

I installed Opera and TOR bundled, with Polipo included in the download archive. Installation required just one click on a button, was incredibly easy and OPERA & TOR began working immediately without any problems, unlike Firefox & TOR which just gave an http error message and stopped with a blank screen.

Good luck then. The Tor Browser Bundle is designed to work the same way. We're working on bringing this to all operating systems. Microsoft Windows and Linuxes already exist.

Anonymous (not verified) said:

July 28, 2010

Permalink

Polipo doesn`t support downloading more than 30mb.the reason i use tor is to enable downloading above 150mb which is blcoked in our firewall.Please reconsider about this and develop privoxy instead of polipo. now i am back to old version with privoxy.Hoping a good response in next update

Polipo supports downloading gigabytes of data. There's a bug where polipo will fill up the memory cache and stop the download, rather than continue on. I've been able to download 10GBs of linux isos through polipo just fine. It seems the bug shows up on Windows more than not. Privoxy is too slow and doesn't support http 1.1 for two reasons why we switched. The real question is why do we need a http proxy at all? See https://trac.torproject.org/projects/tor/wiki/TheOnionRouter/TorFAQ#Why…

Anonymous (not verified) said:

August 21, 2010

Permalink

Hello, I am running Tor v.0.2.1.22 with firefox 3.0.19 and Torbutton 1.2.5. I have been able to browse/download/upload fine with Tor enabled up until today, when I get firefox message 'proxy server refused connection'. Tor is able to establish circuit through c-prompt. Firefox connection setting is set to 'No Proxy'. I have tried changing this to 'auto-detect proxy', no difference. I have tried changing the Torbutton setting to 'use custom proxy settings' that did not work. I am fairly certain the only thing that could have changed was an updating of firefox. Any recommendations would be greatly appreciated. Thx.

Anonymous (not verified) said:

October 07, 2010

Permalink

Hello ,
I am new to tor and i really need some help i downloaded the bundle for windows and i did all the steps but tor does not appear on the start menu and when i want to open it i go to the tor browser folder and click on the onion and i can not see torcc.

Thanks for your prompt reply

what exactly did you download, the tor browser bundle or the vidalia bundle? the tor browser bundle doesn't install anything, it's self-contained. Just click "Start Tor Browser" and everything else works by default.