tor-qa

tor-qa@lists.torproject.org

545 discussions

Re: [tor-qa] Pre-build announcement for 3.6-beta-1
by Matt 13 Mar '14

13 Mar '14

On Mon, 10 Mar 2014 08:34:44 +0000 Georg Koppen <gk(a)torproject.org> wrote: > Mike Perry: > > Once we get confirmation on reproducibility (earlier commits were > > fine, so we should be good), we'll begin testing. Probably > > Monday/Tuesday. > > I got matching builds with the bundles you find on: > > https://people.torproject.org/~mikeperry/builds/3.6-beta-1/ > > Thus, happy testing! > > Georg > If tor fails, an error message says "Tor unexpectedly exited" and the browser stays open. You can tell the browser to visit new pages, but you get a proxy error page. In previous versions, if Tor fails, the browser closes, and you can't do browser stuff anymore. I'm not sure if this change is good or bad.

2 1

Test bundle for ibus issue on Linux systems
by Georg Koppen 28 Feb '14

28 Feb '14

Hi, recently, a nice fellow posted a fix for the long annoying ibus issue on some Linux systems (see #9353 in general and comment 64 for the proposed fix). I made a test bundle to let people verify whether that really fixes their woes (while not breaking things). It is basically a 3.5.2.1 bundle + an updated start-tor-browser.sh: https://people.torproject.org/~gk/testbuilds/tor-browser-linux64-3.5.2.1_93… https://people.torproject.org/~gk/testbuilds/tor-browser-linux64-3.5.2.1_93… Georg

2 1

Please test experimental bundles with meek transport (3.5.2.1-meek-1)
by David Fifield 20 Feb '14

20 Feb '14

(Devs are in Iceland, post bundles.) Here are experimental bundles featuring the meek transport. I'm interested in hearing how well it works for you. You don't need to configure a bridge address; just click Connect. https://people.torproject.org/~dcf/pt-bundle/3.5.2.1-meek-1/ Here's some more on how it works. In short, your traffic gets routed through a web service in a way that is hard to block. In my opinion, this transport is turbo-sexy and is going to work for a lot of people. But don't take my word for it, see for yourself. https://trac.torproject.org/projects/tor/wiki/doc/meek https://lists.torproject.org/pipermail/tor-dev/2014-January/006159.html I've been using this transport for all my own Tor use for the last 10 days. It feels a little bit slower than ordinary Tor, but you can still watch YouTube on it. On App Engine you pay for your bandwidth ($0.12/GB). There's $50 in the app account; so far it's cost $0.06. (You get 1 GB free each day, and only twice I exceeded that.) Part of my reason for exposing the transport to testers is to estimate how much it will cost to operate on an ongoing basis. If it's successful here, next we'll try tor-dev, then tor-talk, then the world. This is the branch from which the bundles were built: https://gitweb.torproject.org/user/dcf/tor-browser-bundle.git/shortlog/refs… https://gitweb.torproject.org/user/dcf/tor-browser-bundle.git/commitdiff/tb… David Fifield

3 3

Experimental 3.5.2 bundles with tor-fw-helper (automatic port forwarding)
by David Fifield 15 Feb '14

15 Feb '14

Please test these experimental bundles that have tor-fw-helper included. You may know that flash proxy requires people to set up port forwarding (https://trac.torproject.org/projects/tor/wiki/FlashProxyHowto). tor-fw-helper is a tool that uses UPnP or NAT-PMP to forward a port automatically. I'm interested in finding out how likely it is to work. https://people.torproject.org/~dcf/pt-bundle/3.5.2-fwhelper-1/ The bundles are configured to run flash proxy and tor-fw-helper. You just have to click "Connect" and wait up to 60 seconds. You don't have to do any special tests; just see whether it bootstraps or not. If you want to see more of what's going on, look at the file flashproxy-client.log that will be created inside the bundle. When tor-fw-helper fails, it looks like this: 2014-02-09 01:15:52 Running port forwarding command: ./tor-fw-helper -p 49334:49334 2014-02-09 01:16:00 tor-fw-helper: tor-fw-helper tcp-forward 49334 49334 FAIL All port forwarding backends (natpmp) failed. 2014-02-09 01:16:00 tor-fw-helper: E: upnpDiscover returned: NULL 2014-02-09 01:16:00 tor-fw-helper: V: natpmp initialized... 2014-02-09 01:16:00 tor-fw-helper: tor-fw-helper: 1 NAT traversal helper(s) loaded 2014-02-09 01:16:00 tor-fw-helper: E: readnatpmpresponseorretry failed -7 2014-02-09 01:16:00 tor-fw-helper: E: errno=61 'Connection refused' 2014-02-09 01:16:00 tor-fw-helper: E: NAT-PMP It appears that something went wrong: -7 2014-02-09 01:16:00 tor-fw-helper: tor-fw-helper: tor_fw_add_port backend natpmp returned: -7 2014-02-09 01:16:00 tor-fw-helper exited with status 1. This is the branch from which the bundles are built. The second link shows what's different in the branch relative to the TBB 3.5.2 release. https://gitweb.torproject.org/user/dcf/tor-browser-bundle.git/shortlog/refs… https://gitweb.torproject.org/user/dcf/tor-browser-bundle.git/commitdiff/3.… David Fifield

3 7

3.5.2.1 Build #2
by Mike Perry 14 Feb '14

14 Feb '14

Ok, these builds should *really* fix that localization issue (turns out the version string needs to remove the esr suffix, too): https://people.torproject.org/~mikeperry/builds/3.5.2.1/ Windows testing is especially appreciated. -- Mike Perry

3 2

3.5.2.1 (localization fixes)
by Mike Perry 14 Feb '14

14 Feb '14

It turns out 3.5.2 had an issue where we did not pick up the proper Firefox release version from Mozilla's new git mirror. Unfortunately, Mozilla is no longer exporting release branches to this mirror, which means all their "release" commits in the esr24 branch still have a "pre" suffix on the Firefox version. This caused the 3.5.2 release to be incompatible with the 24.3.0esr langpacks (bug 10895), and none of our non-English bundles were functional. Here's the new build (please test non-english builds, they work for me on Linux, but who knows about elsewhere): https://people.torproject.org/~linus/builds/3.5.2.1/ Windows testing is also useful, because we merged a size reduction fix in between this release and 3.5.2. Here's the changelog: * All Platforms * Bug 10895: Fix broken localized bundles * Windows: * Bug 10323: Remove unneeded gcc/libstdc++ libraries from dist -- Mike Perry

3 2

Re: [tor-qa] Experimental 3.5.2 bundles with tor-fw-helper (automatic port forwarding)
by Matt 13 Feb '14

13 Feb '14

On Sun, 9 Feb 2014 08:55:36 -0800 David Fifield <david(a)bamsoftware.com> wrote: > Please test these experimental bundles that have tor-fw-helper > included. You may know that flash proxy requires people to set up > port forwarding > (https://trac.torproject.org/projects/tor/wiki/FlashProxyHowto). > tor-fw-helper is a tool that uses UPnP or NAT-PMP to forward a port > automatically. I'm interested in finding out how likely it is to work. > > https://people.torproject.org/~dcf/pt-bundle/3.5.2-fwhelper-1/ > I've suggested this bundle to several people who have trouble connecting through obfs3, for whatever reason. One person, who reportedly lives in a country where Tor is blocked, told me that this bundle works great.

1 0

Re: [tor-qa] Experimental 3.5.2 bundles with tor-fw-helper (automatic port forwarding)
by Wilton Gorske 10 Feb '14

10 Feb '14

>Thank you for testing! It looks like tor-fw-helper doesn't work for you. > What do you see in the flashproxy-client.log? (Command-click on the > application icon, and choose "Show Package Contents".) No problem! Here's the log file: -------------------------------- 2014-02-09 21:37:01 VERSION 1 2014-02-09 21:37:01 Listening remote on 0.0.0.0:64365. 2014-02-09 21:37:01 Listening remote on [::]:64366. 2014-02-09 21:37:01 Listening local on 127.0.0.1:64367. 2014-02-09 21:37:01 CMETHOD flashproxy socks4 127.0.0.1:64367 2014-02-09 21:37:01 CMETHODS DONE 2014-02-09 21:37:01 Not forwarding to [::]:64366 because it is not an IPv4 address. 2014-02-09 21:37:01 Running port forwarding command: ./tor-fw-helper -p 64365:64365 2014-02-09 21:37:09 tor-fw-helper: tor-fw-helper tcp-forward 64365 64365 FAIL All port forwarding backends (natpmp) failed. 2014-02-09 21:37:09 tor-fw-helper: E: upnpDiscover returned: NULL 2014-02-09 21:37:09 tor-fw-helper: V: natpmp initialized... 2014-02-09 21:37:09 tor-fw-helper: tor-fw-helper: 1 NAT traversal helper(s) loaded 2014-02-09 21:37:09 tor-fw-helper: E: readnatpmpresponseorretry failed -7 2014-02-09 21:37:09 tor-fw-helper: E: errno=61 'Connection refused' 2014-02-09 21:37:09 tor-fw-helper: E: NAT-PMP It appears that something went wrong: -7 2014-02-09 21:37:09 tor-fw-helper: tor-fw-helper: tor_fw_add_port backend natpmp returned: -7 2014-02-09 21:37:09 tor-fw-helper exited with status 1. 2014-02-09 21:37:09 Trying to register ":64365". 2014-02-09 21:37:09 Local connection from [scrubbed]. 2014-02-09 21:37:09 Running command: /Users/**********/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :64365 2014-02-09 21:37:09 SOCKS request from [scrubbed]. 2014-02-09 21:37:09 Got SOCKS request for [scrubbed]. 2014-02-09 21:37:09 locals (1): ['[scrubbed]'] 2014-02-09 21:37:09 remotes (0): [] 2014-02-09 21:37:09 Data from unlinked local [scrubbed] (271 bytes). 2014-02-09 21:37:09 locals (1): ['[scrubbed]'] 2014-02-09 21:37:09 remotes (0): [] 2014-02-09 21:37:15 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-09 21:37:15 Trying to register ":64365". 2014-02-09 21:37:15 Running command: /Users/***********/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :64365 2014-02-09 21:37:16 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-09 21:38:30 VERSION 1 2014-02-09 21:38:30 Listening remote on 0.0.0.0:64377. 2014-02-09 21:38:30 Listening remote on [::]:64378. 2014-02-09 21:38:30 Listening local on 127.0.0.1:64379. 2014-02-09 21:38:30 CMETHOD flashproxy socks4 127.0.0.1:64379 2014-02-09 21:38:30 CMETHODS DONE 2014-02-09 21:38:30 Not forwarding to [::]:64378 because it is not an IPv4 address. 2014-02-09 21:38:30 Running port forwarding command: ./tor-fw-helper -p 64377:64377 2014-02-09 21:38:39 tor-fw-helper: tor-fw-helper tcp-forward 64377 64377 FAIL All port forwarding backends (natpmp) failed. 2014-02-09 21:38:39 tor-fw-helper: E: upnpDiscover returned: NULL 2014-02-09 21:38:39 tor-fw-helper: V: natpmp initialized... 2014-02-09 21:38:39 tor-fw-helper: tor-fw-helper: 1 NAT traversal helper(s) loaded 2014-02-09 21:38:39 tor-fw-helper: E: readnatpmpresponseorretry failed -7 2014-02-09 21:38:39 tor-fw-helper: E: errno=61 'Connection refused' 2014-02-09 21:38:39 tor-fw-helper: E: NAT-PMP It appears that something went wrong: -7 2014-02-09 21:38:39 tor-fw-helper: tor-fw-helper: tor_fw_add_port backend natpmp returned: -7 2014-02-09 21:38:39 tor-fw-helper exited with status 1. 2014-02-09 21:38:39 Trying to register ":64377". 2014-02-09 21:38:39 Running command: /Users/********/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :64377 2014-02-09 21:38:39 Local connection from [scrubbed]. 2014-02-09 21:38:39 SOCKS request from [scrubbed]. 2014-02-09 21:38:39 Got SOCKS request for [scrubbed]. 2014-02-09 21:38:39 locals (1): ['[scrubbed]'] 2014-02-09 21:38:39 remotes (0): [] 2014-02-09 21:38:39 Data from unlinked local [scrubbed] (252 bytes). 2014-02-09 21:38:39 locals (1): ['[scrubbed]'] 2014-02-09 21:38:39 remotes (0): [] 2014-02-09 21:38:41 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-09 21:38:41 Trying to register ":64377". 2014-02-09 21:38:41 Running command: /Users/*********/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :64377 2014-02-09 21:38:43 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-09 21:40:14 VERSION 1 2014-02-09 21:40:14 Listening remote on 0.0.0.0:64401. 2014-02-09 21:40:14 Listening remote on [::]:64402. 2014-02-09 21:40:14 Listening local on 127.0.0.1:64403. 2014-02-09 21:40:14 CMETHOD flashproxy socks4 127.0.0.1:64403 2014-02-09 21:40:14 CMETHODS DONE 2014-02-09 21:40:14 Not forwarding to [::]:64402 because it is not an IPv4 address. 2014-02-09 21:40:14 Running port forwarding command: ./tor-fw-helper -p 64401:64401 2014-02-09 21:40:22 tor-fw-helper: tor-fw-helper tcp-forward 64401 64401 FAIL All port forwarding backends (natpmp) failed. 2014-02-09 21:40:22 tor-fw-helper: E: upnpDiscover returned: NULL 2014-02-09 21:40:22 tor-fw-helper: V: natpmp initialized... 2014-02-09 21:40:22 tor-fw-helper: tor-fw-helper: 1 NAT traversal helper(s) loaded 2014-02-09 21:40:22 tor-fw-helper: E: readnatpmpresponseorretry failed -7 2014-02-09 21:40:22 tor-fw-helper: E: errno=61 'Connection refused' 2014-02-09 21:40:22 tor-fw-helper: E: NAT-PMP It appears that something went wrong: -7 2014-02-09 21:40:22 tor-fw-helper: tor-fw-helper: tor_fw_add_port backend natpmp returned: -7 2014-02-09 21:40:22 tor-fw-helper exited with status 1. 2014-02-09 21:40:22 Trying to register ":64401". 2014-02-09 21:40:22 Running command: /Users/**********/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :64401 2014-02-09 21:40:22 Local connection from [scrubbed]. 2014-02-09 21:40:22 SOCKS request from [scrubbed]. 2014-02-09 21:40:22 Got SOCKS request for [scrubbed]. 2014-02-09 21:40:22 locals (1): ['[scrubbed]'] 2014-02-09 21:40:22 remotes (0): [] 2014-02-09 21:40:22 Data from unlinked local [scrubbed] (252 bytes). 2014-02-09 21:40:22 locals (1): ['[scrubbed]'] 2014-02-09 21:40:22 remotes (0): [] 2014-02-09 21:40:25 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-09 21:40:25 Trying to register ":64401". 2014-02-09 21:40:25 Running command: /Users/************/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :64401 2014-02-09 21:40:28 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-09 21:43:33 VERSION 1 2014-02-09 21:43:33 Listening remote on 0.0.0.0:64422. 2014-02-09 21:43:33 Listening remote on [::]:64423. 2014-02-09 21:43:33 Listening local on 127.0.0.1:64424. 2014-02-09 21:43:33 CMETHOD flashproxy socks4 127.0.0.1:64424 2014-02-09 21:43:33 CMETHODS DONE 2014-02-09 21:43:33 Not forwarding to [::]:64423 because it is not an IPv4 address. 2014-02-09 21:43:33 Running port forwarding command: ./tor-fw-helper -p 64422:64422 2014-02-09 21:43:41 tor-fw-helper: tor-fw-helper tcp-forward 64422 64422 FAIL All port forwarding backends (natpmp) failed. 2014-02-09 21:43:41 tor-fw-helper: E: upnpDiscover returned: NULL 2014-02-09 21:43:41 tor-fw-helper: V: natpmp initialized... 2014-02-09 21:43:41 tor-fw-helper: tor-fw-helper: 1 NAT traversal helper(s) loaded 2014-02-09 21:43:41 tor-fw-helper: E: readnatpmpresponseorretry failed -7 2014-02-09 21:43:41 tor-fw-helper: E: errno=61 'Connection refused' 2014-02-09 21:43:41 tor-fw-helper: E: NAT-PMP It appears that something went wrong: -7 2014-02-09 21:43:41 tor-fw-helper: tor-fw-helper: tor_fw_add_port backend natpmp returned: -7 2014-02-09 21:43:41 tor-fw-helper exited with status 1. 2014-02-09 21:43:41 Trying to register ":64422". 2014-02-09 21:43:41 Running command: /Users/***********Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :64422 2014-02-09 21:43:41 Local connection from [scrubbed]. 2014-02-09 21:43:41 SOCKS request from [scrubbed]. 2014-02-09 21:43:41 Got SOCKS request for [scrubbed]. 2014-02-09 21:43:41 locals (1): ['[scrubbed]'] 2014-02-09 21:43:41 remotes (0): [] 2014-02-09 21:43:41 Data from unlinked local [scrubbed] (263 bytes). 2014-02-09 21:43:41 locals (1): ['[scrubbed]'] 2014-02-09 21:43:41 remotes (0): [] 2014-02-09 21:43:43 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-09 21:43:43 Trying to register ":64422". 2014-02-09 21:43:43 Running command: /Users/*********/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :64422 2014-02-09 21:43:45 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-09 21:56:07 VERSION 1 2014-02-09 21:56:07 Listening remote on 0.0.0.0:64566. 2014-02-09 21:56:07 Listening remote on [::]:64567. 2014-02-09 21:56:07 Listening local on 127.0.0.1:64568. 2014-02-09 21:56:07 CMETHOD flashproxy socks4 127.0.0.1:64568 2014-02-09 21:56:07 CMETHODS DONE 2014-02-09 21:56:07 Not forwarding to [::]:64567 because it is not an IPv4 address. 2014-02-09 21:56:07 Running port forwarding command: ./tor-fw-helper -p 64566:64566 2014-02-10 18:03:09 VERSION 1 2014-02-10 18:03:09 Listening remote on 0.0.0.0:53215. 2014-02-10 18:03:09 Listening remote on [::]:53216. 2014-02-10 18:03:09 Listening local on 127.0.0.1:53217. 2014-02-10 18:03:09 CMETHOD flashproxy socks4 127.0.0.1:53217 2014-02-10 18:03:09 CMETHODS DONE 2014-02-10 18:03:09 Not forwarding to [::]:53216 because it is not an IPv4 address. 2014-02-10 18:03:09 Running port forwarding command: ./tor-fw-helper -p 53215:53215 2014-02-10 18:03:17 tor-fw-helper: tor-fw-helper tcp-forward 53215 53215 FAIL All port forwarding backends (natpmp) failed. 2014-02-10 18:03:17 tor-fw-helper: E: upnpDiscover returned: NULL 2014-02-10 18:03:17 tor-fw-helper: V: natpmp initialized... 2014-02-10 18:03:17 tor-fw-helper: tor-fw-helper: 1 NAT traversal helper(s) loaded 2014-02-10 18:03:17 tor-fw-helper: E: readnatpmpresponseorretry failed -7 2014-02-10 18:03:17 tor-fw-helper: E: errno=61 'Connection refused' 2014-02-10 18:03:17 tor-fw-helper: E: NAT-PMP It appears that something went wrong: -7 2014-02-10 18:03:17 tor-fw-helper: tor-fw-helper: tor_fw_add_port backend natpmp returned: -7 2014-02-10 18:03:17 tor-fw-helper exited with status 1. 2014-02-10 18:03:17 Trying to register ":53215". 2014-02-10 18:03:17 Running command: /Users/*********/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :53215 2014-02-10 18:03:17 Local connection from [scrubbed]. 2014-02-10 18:03:17 SOCKS request from [scrubbed]. 2014-02-10 18:03:17 Got SOCKS request for [scrubbed]. 2014-02-10 18:03:17 locals (1): ['[scrubbed]'] 2014-02-10 18:03:17 remotes (0): [] 2014-02-10 18:03:17 Data from unlinked local [scrubbed] (261 bytes). 2014-02-10 18:03:17 locals (1): ['[scrubbed]'] 2014-02-10 18:03:17 remotes (0): [] 2014-02-10 18:03:19 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. 2014-02-10 18:03:19 Trying to register ":53215". 2014-02-10 18:03:19 Running command: /Users/**********/Downloads/TorBrowserBundle_en-US 2.app/Tor/PluggableTransports/flashproxy-reg-appspot --transport websocket :53215 2014-02-10 18:03:20 flashproxy-reg-appspot: Registered "[scrubbed]" with fp-reg-a.appspot.com. -------------------------------- David Fifield: > On Mon, Feb 10, 2014 at 05:07:08PM +0000, Wilton Gorske wrote: >> Testing: TorBrowserBundle-3.5.2-fwhelper-1-osx32_en-US.zip >> Platform: Mac OS X 10.9.1 (13B3116) >> Processor: 2.3GHz Intel Core i7 >> Memory: 16 GB 1600 MHz DDR3 >> Graphics: NVIDIA GeForce GT 750M 2048 MB >> Display: 15-inch (2880 x 1800 Retina) >> >> TBB Launches successfully: yes >> * Connects to the Tor network: no * >> Browser toolbars and menus work, tab dragging works: ? > > Thank you for testing! It looks like tor-fw-helper doesn't work for you. > What do you see in the flashproxy-client.log? (Command-click on the > application icon, and choose "Show Package Contents".) > >> The Tor Log: >> 2/9/14, 21:38:30.395 [NOTICE] Opening Socks listener on 127.0.0.1:9150 >> 2/9/14, 21:38:30.395 [WARN] Pluggable transport proxy (obfs2,obfs3 exec PluggableTransports/obfsproxy.bin managed) does not provide any needed transports and will not be launched. >> 2/9/14, 21:38:32.859 [NOTICE] Bootstrapped 5%: Connecting to directory server. >> 2/9/14, 21:38:32.859 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server. > > This is what I would expect to see if tor-fw-helper didn't work. Your > computer was not able to receive a connection from a flash proxy, so it > couldn't get past 10%. > >> Launches but gets stuck “Finishing handshake with directory >> server”. Only outbound connects to t2.gstatic.com and google.com? > > The outbound connections are the rendezvous mechanism. > https://gitweb.torproject.org/flashproxy.git/blob/HEAD:/flashproxy-reg-apps… > In the flash proxy system, your computer needs to tell the facilitator > that it needs service. We found a way to do it that looks like you are > doing a Google search, more or less. > > David Fifield > -- Wilton GPG: 0xac5a18281b054e0c

1 0

TBB 3.5.2 ready for testing
by Mike Perry 08 Feb '14

08 Feb '14

Candidate builds are at: https://people.torproject.org/~linus/builds/3.5.2/ Additional signatures are at: https://people.torproject.org/~gk/builds/3.5.2/sha256sums.txt.asc https://people.torproject.org/~mikeperry/builds/3.5.2/sha256sums.txt.asc This is a security release, and contains the new Firefox 24.3.0ESR fixes. We're especially looking for anyone on MacOS 10.9 report back. Someone told me that they are experiencing intermittent crashes on 10.9 since TBB 3.5 (TBB 3.0 was fine for them). They suspect Retina support in FF24ESR to be the culprit, though official Firefox builds do not crash. I have not experienced crashes on MacOS 10.6. Here's the ChangeLog: * Rebase Tor Browser to Firefox 24.3.0ESR * Bug 10419: Block content window connections to localhost * Update Torbutton to 1.6.0 * Bug 10800: Prevent findbox exception and popup in New Identity * Bug 10640: Fix about:tor's update pointer position for RTL languages. * Bug 10095: Fix some cases where resolution is not a multiple of 200x100 * Bug 10285: Clear site permissions on New Identity * Bug 9738: Fix for auto-maximizing on browser start * Bug 10682: Workaround to really disable updates for Torbutton * Bug 10419: Don't allow connections to localhost if Torbutton is toggled * Bug 10140: Move Japanese to extra locales (not part of TBB dist) * Bug 10687: Add Basque (eu) to extra locales (not part of TBB dist) * Update Tor Launcher to 0.2.4.4 * Bug 10682: Workaround to really disable updates for Tor Launcher * Update NoScript to 2.6.8.13 -- Mike Perry

5 4

WebSockets
by Colin C. 31 Jan '14

31 Jan '14

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, It appears that html5demos.com/web-socket is no longer reporting correct information in regards to websockets (thanks Sherief), so this should no longer be used as a test. The current TBB has websockets enabled, as can be seen by checking websocketstest.com and other test services. I'm hoping to get a Selenium test written in the next couple days that will check multiple sources for websockets, so hopefully this issue does not occur again. I apologize for not noticing that html5demos was not functional, thanks again to Sherief for pointing this out. - -- - -Phoul -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJS6wKsAAoJEJ01Zvx7KO7YgAcP/jLoQgGWAkVtTaYAEr3TaBYX okd1nIUJEQJul0k8jNJzqOqGvRpJH+Tx5Zl10a2MMtAGhZ0b3xH/mQCeofV7d3yZ vn+Uois0s2phi2xyz6twtJKhl8mozS2JTJACeeRWkmA+uE3xyiJ+wKQls+iltJs+ vCF/rCc0irobEtI76OvZBDYYDQf76Ohm0xLYztBlSK30E5r5G3h9lONAvl2CX92o zrKOY2NJ2KHIWQfwacmfmMY5oWcjyLqTz9q74phF7Ha9crXn8VIEugo0dHfArine 75TFnC/VnE9dNTOSaMXhKhdaX8u1w9mVdYPtznKiOEGUF7juh9ynjoiiSQIXsaU+ T/JHsQgEDMCUJ2VM0o6shxnMGRpBn7gbWUbIRiF3YC8JJ9MYAEwxVD3I3dHOSnit z3BwNBYOciuEKNHrJAhSskg4Hlp4kcEws1ucZKzQlQ/Sn5RBqHoR1CeC3GdVsJOy TmBtPasxPATM5zoQIB42TNu62ndONq93rRd+TY4LU7bnCkBZA/WnenJOlm0B3VzT cCtH37xanaCML5MgG2jm+uMq5Kdnf9SElH96GjRwBe9QSDKIbF3K6Osal74zbhck oxYzhKrz9G6Fm3WcX+mgrglFYRsbtmX1zjWR5yr3248xXDRzGv9JO6l/4DRABqRc OSndbUDdzv4IJcyrm23c =JotL -----END PGP SIGNATURE-----

3 3

← Newer
1
...
45
46
47
48
49
50
51
...
55
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

tor-qa