[tor-qa] New stable & alpha bundles with Firefox 17.0.6esr

[Colin C.]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

On 12/05/13 10:14 PM, Erinn Clark wrote:
> Hello lovely testers,
> 
> Sorry to send new bundles so soon but just as I was preparing to
> release the last ones, there was a new Firefox release. Not much
> has changed here -- I updated the stable HTTPS Everywhere to 3.2
> and the alpha version of NoScript, along with Firefox in both. I
> suspect just a quick once over is enough, but making sure Firefox
> is still not crashy is probably a good idea.
> 
> stable ------- Packages:
> https://people.torproject.org/~erinn/qa/stable/2.3.25-8/ 
> sha256sums:
> https://people.torproject.org/~erinn/qa/stable/2.3.25-8/sha256sums-2.3.25-8.txt.asc
>
> 
Turnaround: 24h
> 
> alpha ------- Packages:
> https://people.torproject.org/~erinn/qa/alpha/2.4.12-alpha-2/ 
> sha256sums:
> https://people.torproject.org/~erinn/qa/alpha/2.4.12-alpha-2/sha256sums-2.4.12-alpha-2.txt.asc
>
> 
Turnaround: 24h
> 
> Thank you!
> 
> Erinn
> 
> 
> 
> _______________________________________________ tor-qa mailing
> list tor-qa at lists.torproject.org 
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
Testing: tor-browser-gnu-linux-x86_64-2.4.12-alpha-2-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.1e (See "Other Notes")

All extensions are present and functional -  OK
 - HTTPS-Everywhere 4.0development.6
 - NoScript 2.6.6.1
 - TorButton 1.5.2
 - PDF Viewer 0.8.1

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 OpenSSL version 1.0.0k

Message Log: [Notice] We were built to run on a 64-bit CPU, with
OpenSSL 1.0.1 or later, but with a version of OpenSSL that apparently
lacks accelerated support for the NIST P-224 and P-256 groups.
Building openssl with such support (using the
enable-ec_nistp_64_gcc_128 option when configuring it) would make ECDH
much faster.

- -- 
- -Phoul
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRkV8iAAoJEJ01Zvx7KO7Yf8wP/ApyD2c0oFDFHq5LrXFgrSma
nwYD+mxe38/vNDi4fE8Hg3tqvSjVim9lWiGGjm8KvQlEk9Cdw7FL0xqB2ztxF2da
Ej4B9beITROjgZssMWFGKubuUCWCML3faaDX0cBa1FzMzuwYpi+oM+7wIpZ/ocme
f1FV7CNzpUU8W8nxKnphNlAdww4NaUx9X6Rd8quA+7tJaxCbJ/CK4P+mVO7hIVrx
iCCaQ8ZptP+y58visWYxHx7cDROA57LpOSrJyZz2GvA4hjNFn5iH5+7WGYpZ+AoR
Eue52KMEr+Q6q/HRGPSoes6G1+SFMLkUutgJW1wT6H0RE3ZBbY9dXt7MEzq8HWmN
KTm4coevJKdmIjyNOqMzM/R0zmtwwUMuV59v3/oq9/vM9VzOJn6qc7KhVEtXzzif
HZMcsVUg20AEbf/7brxj2pryATy4LRAVvg6aOdK5Dmkxf1BE+ABUP8tSDuM4G/Pg
jX0CcM0TT/5FAg0nI0/Opcud9dqNrVv3E57DROAsxuyDlDdJPGjimW0OxDQVLi2z
5dWKjZfiAA1d4cp9r34tqhpWpzETG6ek7o8j7puGvjnCdb54pCXu8GFNMYBtR8PH
YgkZNrULkNX4yD2n3tsbf2/B/EUArixGqSl8nd6l69K4mFXeAWq7YbeBaFEHHUO6
2/lSth969JmyQ5Hbl5dZ
=mSJy
-----END PGP SIGNATURE-----