Please test experimental bundles with meek transport (3.5.2.1-meek-1)
(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/tbb... David Fifield
Testing: TorBrowserBundle-3.5.2-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) ISP: Telenet (Belgium) TBB Launches successfully: yes Connects to the Tor network: yes Browser toolbars and menus work, tab dragging works: yes All extensions are present and functional: yes - HTTPS-Everywhere 3.4.5 - NoScript 2.6.8.13 - TorButton 1.6.6.0 - TorLauncher 0.2.4.4 WebBrowsing works as expected - HTTP, HTTPS, .onion browsing works (http://duskgytldkxiuqc6.onion/) - HTML5 videos work on http://videojs.com/ and YouTube - http://ip-check.info/?lang=en - ok - https://panopticlick.eff.org/ - only one in 1,291,815 , 20.3 bits of identifying information - html5demos.com/web-socket - Not Connected / Socket Closed SOCKS/external apps work as expected: yes (Torbirdy) No crashes at all or unexpected behavior. Noticeably slower while starting up and browsing. Tor Log: 2/18/14, 17:48:20.797 [NOTICE] Bootstrapped 5%: Connecting to directory server. 2/18/14, 17:48:20.797 [NOTICE] Bootstrapped 10%: Finishing handshake with directory server. 2/18/14, 17:48:48.163 [NOTICE] Learned fingerprint 86FA348B038B6A04F2F50135BF84BB74EF63485B for bridge 0.0.2.0:1 (with transport 'meek'). 2/18/14, 17:48:48.163 [NOTICE] Bootstrapped 15%: Establishing an encrypted directory connection. 2/18/14, 17:48:49.840 [NOTICE] Bootstrapped 20%: Asking for networkstatus consensus. 2/18/14, 17:48:49.391 [NOTICE] Bootstrapped 50%: Loading relay descriptors. 2/18/14, 17:48:50.190 [NOTICE] Bridge '3VXRyxz67OeRoqHn' has both an IPv4 and an IPv6 address. Will prefer using its IPv4 address (0.0.2.0:1). 2/18/14, 17:48:50.190 [NOTICE] new bridge descriptor '3VXRyxz67OeRoqHn' (fresh): $86FA348B038B6A04F2F50135BF84BB74EF63485B~3VXRyxz67OeRoqHn at 0.0.2.0 2/18/14, 17:48:50.190 [NOTICE] I learned some more directory information, but not enough to build a circuit: We have no usable consensus. 2/18/14, 17:49:08.833 [NOTICE] Application request when we haven't used client functionality lately. Optimistically trying directory fetches again. 2/18/14, 17:49:18.641 [NOTICE] We now have enough directory information to build circuits. 2/18/14, 17:49:18.641 [NOTICE] Bootstrapped 80%: Connecting to the Tor network. 2/18/14, 17:49:18.808 [NOTICE] Bootstrapped 90%: Establishing a Tor circuit. 2/18/14, 17:49:47.146 [NOTICE] Tor has successfully opened a circuit. Looks like client functionality is working. 2/18/14, 17:49:47.146 [NOTICE] Bootstrapped 100%: Done. 2/18/14, 17:49:47.905 [NOTICE] New control connection opened. 2/18/14, 18:48:52.626 [NOTICE] Bridge '3VXRyxz67OeRoqHn' has both an IPv4 and an IPv6 address. Will prefer using its IPv4 address (0.0.2.0:1). 2/18/14, 18:48:52.626 [NOTICE] new bridge descriptor '3VXRyxz67OeRoqHn' (fresh): $86FA348B038B6A04F2F50135BF84BB74EF63485B~3VXRyxz67OeRoqHn at 0.0.2.0 David Fifield:
(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/tbb...
David Fifield _______________________________________________ tor-qa mailing list tor-qa@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
-- GPG: 0xac5a18281b054e0c
On Tue, Feb 18, 2014 at 07:25:58PM +0000, Wilton Gorske wrote:
Testing: TorBrowserBundle-3.5.2-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) ISP: Telenet (Belgium)
TBB Launches successfully: yes Connects to the Tor network: yes Browser toolbars and menus work, tab dragging works: yes
All extensions are present and functional: yes - HTTPS-Everywhere 3.4.5 - NoScript 2.6.8.13 - TorButton 1.6.6.0 - TorLauncher 0.2.4.4
WebBrowsing works as expected - HTTP, HTTPS, .onion browsing works (http://duskgytldkxiuqc6.onion/) - HTML5 videos work on http://videojs.com/ and YouTube - http://ip-check.info/?lang=en - ok - https://panopticlick.eff.org/ - only one in 1,291,815 , 20.3 bits of identifying information - html5demos.com/web-socket - Not Connected / Socket Closed
SOCKS/external apps work as expected: yes (Torbirdy)
No crashes at all or unexpected behavior. Noticeably slower while starting up and browsing.
Thanks for testing it. The slowness you observe has at least two causes. First is that every 64 KB or less gets wrapped up in an HTTP request, which is first sent to Google and then to the bridge. The second is that HTTP requests and responses are serialized, so if you have something to send right now, you can't send it until you receive a response to your most recent request. Doing it this way is slower, but it's simple to implement and correct. We can imagine having multiple requests outstanding, each with different parts of the byte stream. Then we would need to start worrying about what happens if requests arrive out of order, or a request fails. A benefit of the more complicated model, apart from performance, is that being resilient to dropped requests, it would allow us to keep a Tor circuit alive even after an HTTP failure (which failures are happening to me a few times a day). David Fifield
On 18/02/14 10:44 AM, David Fifield wrote:
(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/tbb...
David Fifield _______________________________________________ tor-qa mailing list tor-qa@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
Testing: tor-browser-linux64-3.5.2.1-meek-1_en-US.tar.xz 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.1f All extensions are present and functional - OK - HTTPS-Everywhere 3.4.5 - NoScript 2.6.8.13 - Torbutton 1.6.6.0 - TorLauncher 0.2.4.4 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) - phoul.github.io - websocket enabled Other Notes: - Trac 10383 (accelerated curve support) - Transport seems to work great, congrats to all involved! [1]: https://trac.torproject.org/projects/tor/ticket/10383 -- -Phoul
participants (3)
-
Colin C. -
David Fifield -
Wilton Gorske