On 10/06/13 07:39 PM, Erinn Clark wrote:
Hey everyone!
We have a crash bug which we believe is fixed by disabling optimization in the Firefox builds on 64-bit Linux. First of all, were any of you using the 2.3.25-8 stable 64-bit Linux builds? Did you notice any crashes?
Either way, updated bundles are here: Packages: https://people.torproject.org/~erinn/qa/stable/2.3.25-9/ sha256sums: https://people.torproject.org/~erinn/qa/stable/2.3.25-9/sha256sums-2.3.25-9.... Turnaround: ASAP, would love to get these out by tomorrow afternoon
Thanks! Erinn
tor-qa mailing list tor-qa@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
Testing: tor-browser-gnu-linux-x86_64-2.3.25-9-dev-en-US.tar.gz Platform: Debian Wheezy Processor: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz
TBB Launches successfully - OK Connects to the Tor network - OK Browser toolbars and menus work. Tab dragging works. - OK DNS - No leaks observed (wireshark)
OpenSSL - 1.0.0k
All extensions are present and functional - See "Other Notes" - HTTPS-Everywhere 3.2 - NoScript 2.6.6.2 - TorButton 1.5.2
WebBrowsing works as expected - OK - HTTP, HTTPS, .onion browsing works - HTML5 videos work - ip-check.info - OK - samy.pl/evercookie - OK (new identity clears cookie) - html5demos.com/web-socket - Not Connected / Socket Closed
Other Notes: - Docs/README-TorBrowserBundle lists NoScript version 2.6.6.1 - HTTPS-Everywhere automatically updates to 3.2.2 - No crashes observed during Tor Browser stress test