Fwd: new stable TBBs available for testing

---------- Forwarded message ---------- From: Erinn Clark <erinn@torproject.org> Date: Mon, Aug 27, 2012 at 9:55 AM Subject: new stable TBBs available for testing To: Mike Perry <mikeperry@torproject.org> Cc: runa@torproject.org, tor-assistants@lists.torproject.org Notable updates are Firefox (10.0.7esr) and libevent (2.0.20-stable). I don't know if we have any Windows testers -- when I last looked at the QA list it was all Linux testers -- but if we do they might want to pay more attention since this version of Libevent fixes some Windows-specific bugs (changelog here: https://raw.github.com/libevent/libevent/release-2.0.20-stable/ChangeLog) Please also make sure that the right version of Libevent is included and running in every bundle, since there is Makefile magic that tells Tor to rebuild against new versions of Libevent and OpenSSL automatically. Testers can verify this in the Message Log of Vidalia. Packages here: https://people.torproject.org/~erinn/qa/stable/ Shasums here: https://people.torproject.org/~erinn/qa/stable/shasums-0.2.2.38-2.txt.asc Turnaround time: I don't expect any major problems and plan to release within the next 24 hours. Feel free to just forward this wholesale to the list or rewrite portions, especially you, Mike, in case you have specific Firefox-related issues. Thanks! Erinn

On Mon, Aug 27, 2012 at 4:32 PM, Runa A. Sandvik <runa@torproject.org> wrote:
Two users tested this on Windows XP: The Tor Browser starts up, check.tpo says "There is a security update available for the Tor Browser", but TBB works just fine. Even when stopped/started a number of times. Correct version of Firefox, Tor, Libevent etc. -- Runa A. Sandvik

Testing: tor-browser-gnu-linux-x86_64-2.2.38-2-dev-en-US.tar.gz Platform: Fedora 17 Processor: Intel(R) Core(TM) i5-2450M CPU @ 2.50GHz Libevent - 2.0.20-stable TBB Launches successfully - OK Connects to the Tor network - OK Browser toolbars and menus work. Tab dragging works. - OK DNS - No leaks observed (wireshark) All extensions are present and functional - OK - HTTPS-Everywhere 2.2.1 - NoScript 2.5.2 - TorButton 1.4.6 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 issues - None On Mon, Aug 27, 2012 at 1:08 PM, Runa A. Sandvik <runa@torproject.org>wrote:
-- - Phoul

Verified.
Testing: tor-browser-gnu-linux-x86_64-2.2.38-2-dev-en-US.tar.gz Platform: Debian 6.0.5 Processor: Intel(R) Pentium(R) CPU B950 @ 2.10GHz TBB Launches successfully - OK Connects to the Tor network - OK Browser toolbars and menus work. Tab dragging works - OK All extensions are present and functional - OK - HTTPS-Everywhere 2.2.1 - NoScript 2.5.2 - TorButton 1.4.6 WebBrowsing works as expected - Mostly - HTTP, HTTPS, .onion browsing works - HTML5 videos DO NOT work (YouTube, "This video is currently unavailable") (Mind you, I switched back to the former version and had the same problem, so this may be a YouTube thing.) - http://ip-check.info/?lang=en - OK - https://panopticlick.eff.org/ - one in 55,414, 15.76 bits of identifying information Vidalia settings - Use static control/SOCKS port - OK Could NOT reproduce tagnaq's problem. -- kat

Just as an addition to that, if you only want to return HTML5 compatible videos on your searches try adding &webm=1 to the search in the address bar. The other thing that may be happening if the video is HTML5 compatible and still comes up as unavailable is NoScript blocking the page "Object". On Wed, Aug 29, 2012 at 4:49 PM, Runa A. Sandvik <runa@torproject.org>wrote:
-- - Phoul

"Colin C.":
Yes, used to that one but I can still usually get it to work ... Runa A. Sandvik:
OK, that makes sense. Just tried http://videojs.com/ - working fine. Thanks all. -- kat

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 testing: tor-browser-gnu-linux-x86_64-2.2.38-2-dev-en-US.tar.gz I run into the situation where after hitting "New Identity" (TorButton) TorBrowser used 100% CPU and did not respond to any clicks any more. I was able to reproduce it once more but after trying 10-times I stopped testing. Here is what I did (maybe you are luckier): - - open https://trac.torproject.org/projects/tor/wiki/doc/build/BuildSignoff#Documen... - - open the 5 URLs in the 'Test Pages to Use' section in tabs. - - on the evercookie page: click "Click to create an evercookie" - - "Click to rediscover cookies" - - Torbutton "New Identity" - - 100% CPU (TorBrowser is not responding) -----BEGIN PGP SIGNATURE----- iF4EAREKAAYFAlA7xVoACgkQyM26BSNOM7Z4ugD/c5/+i5vh9a7+Dq2xa+7JBYB6 /Hhovnl6uqvTGgPzdXwBAKnmXIghckgazVvooMLHZuj5st/pUlb6YSnxVPFTTeEN =tuZr -----END PGP SIGNATURE-----
participants (4)
-
Colin C.
-
Katya Titov
-
Runa A. Sandvik
-
tagnaq