[tor-qa] 2.4.17-beta-2-obfs-flash1 (obfuscated flash proxy) bundles

[Colin C.]

On 28/10/13 09:46 PM, David Fifield wrote:
> Hello testers,
> 
> I have here a first test release of new "obfs-flash" bundles. What's
> different about these is that when you use flash proxy in these bundles,
> the payloads of the WebSocket messages will be obfuscated with obfs3
> (you will see it called "obfs3_flashproxy" in torrc). It's part of a big
> project we've had to combine different transports together, one you can
> read about in ticket #7167.
> 
> https://people.torproject.org/~dcf/pt-bundle/2.4.17-beta-2-obfs-flash1/
> 
> There is a known problem with this set of bundles on Windows. On
> Windows, some transport processes (obfsproxy.exe and
> flashproxy-client.exe) will continue running after you exit Tor and
> Vidalia. You have to open the Task Manager and kill those processes
> before running the bundle again. Read more about it here and in
> following comments:
> https://trac.torproject.org/projects/tor/ticket/10006#comment:5
> This problem was unexpected and will take some time to fix, but we are
> working on it. If you are testing on Windows, remember to kill any
> remaining obfsproxy.exe and flashproxy-client.exe processes after
> exiting the bundle. GNU/Linux and Mac OS X should work fine.
> 
> Because of the problem in the previous paragraph, this build isn't going
> to be released except to testers. But since GNU/Linux and Mac OS X
> should work, we are interested in getting some early feedback.
> 
> The bundles are configured to start obfs2, obfs3, and obfs3_flashproxy
> transports. obfs2 and obfs3 are the same as in previous releases and
> don't need any special testing. If you want to test obfs3_flashproxy
> specifically, you should comment out all the
> 	Bridge obfs2
> 	Bridge obfs3
> lines, and leave the one line
> 	Bridge obfs3_flashproxy
> 
> David Fifield
> _______________________________________________
> tor-qa mailing list
> tor-qa at lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-qa
> 
Testing:
tor-pluggable-transports-browser-gnu-linux-x86_64-2.4.17-beta-2-obfs-flash1-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 -  OK
 - HTTPS-Everywhere 4.0development.12
 - NoScript 2.6.7.1
 - Torbutton 1.5.2

WebBrowsing works as expected - OK
 - HTTP, HTTPS, .onion browsing works
 - HTML5 videos work
 - ip-check.info - OK
 - samy.pl/evercookie - Unable to perform new identity check, see "other
notes".
 - html5demos.com/web-socket - Not Connected / Socket Closed

Other notes:
 - Vidalia's message log remains empty unless you enable the info/debug
log levels.
 - HTTPS-Everywhere and NoScript auto-update after first launch.
 - TorButton's "New identity" is grayed out.

-- 
-Phoul