Tor Browser Bundle 3.0alpha3 Released
The third alpha release in the 3.0 series of the Tor Browser Bundle is now available from the Tor Package Archive:
This release includes important security updates to Firefox. Here is the complete ChangeLog:
- All Platforms:
- Update Firefox to 17.0.8esr
- Update Tor to 0.2.4.15-rc
- Update HTTPS-Everywhere to 3.3.1
- Update NoScript to 184.108.40.206
- Improve build input fetching and authentication
- Bug #9283: Update NoScript prefs for usability.
- Bug #6152 (partial): Disable JSCtypes support at compile time
- Update Torbutton to 1.6.1
- Bug 8478: Change when window resize code fires to avoid rounding errors
- Bug 9331: Hack a correct download URL for the next TBB release
- Bug 9144: Change an aboutTor.dtd string so transifex will accept it
- Update Tor-Launcher to 0.2.1-alpha
- Bug #9128: Remove dependency on JSCtypes
- Bug #9195: Disable download manager AV scanning (to prevent cloud
reporting+scanning of downloaded files)
- Bug #9173 (partial): Launch firefox-bin on MacOS instead of TorBrowser.app
(improves dock behavior).
As usual these binaries should be exactly reproducible by anyone with Ubuntu and KVM support (though there are some issues in LXC).
To build your own identical copies of these bundles from source code, check out the official repository and use git tag [geshifilter-code]<a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/tag/22456…] (commit [geshifilter-code]<a href="https://gitweb.torproject.org/builders/tor-browser-bundle.git/commit/49…]).
These instructions should explain things from there. If you notice any differences from the official bundles, I would love to hear about it!
are you gonna answer this or is beyond you?
I'm hoping somebody else will pipe up here.
In the mean time, the usual questions: Is this repeatable? What can other people do to repeat it?
i didnt launched tor again after this message was shown in red. i have no idea of what any of that code means, all i wanted to know is if anything looks dangerous. or what does it mean at all.
I have seen this before, and no it is not repeatable.
This error message appears often, but not always, in conjunction with the "The proxy server is refusing connections" error.
I speculate that the "XML Parsing Error: unexpected parser state" error is caused by a timeout exception that is not caught in upstream Mozilla code. But I repeat: it is undeterministic and therefore not repeatable.
On a side-note: I believe that I have found the root cause to the "The proxy server is refusing connections" error and posted it here: