New Pluggable Transports bundles 0.2.4.11-alpha (flashproxy + obfsproxy)
We've updated the Pluggable Transports Tor Browser Bundles with Firefox 17.0.4esr and Tor 0.2.4.11-alpha. These releases have numerous bug fixes and a new Torbutton as well.
Like the previous bundles, these contain Flashproxy and the Python version of Obfsproxy.
Flash proxy is a transport that uses proxies running in web browsers as access points into Tor. Obfsproxy is a pluggable transport that makes network traffic look unlike normal Tor traffic. Both of these technologies make it harder to block access to Tor. If you previously used the obfsproxy bundle, please upgrade to this bundle, which in addition to flash proxy has new obfsproxy bridges.
Flash proxy works differently from other pluggable transports, and you need to take extra steps to make it work. In particular, you will probably need to configure port forwarding in order to receive connections from browser proxies. There are instructions and hints on how to do that at this page: flash proxy howto.
These bundles contain the same hardcoded obfs2 bridge addresses as the previous bundles which may work for some jurisdictions but you are strongly advised to get new bridge addresses from BridgeDB: https://bridges.torproject.org/?transport=obfs2.
There are other ways you can help beyond testing the bundles. One is to run a bridge with pyobfsproxy. Another is to put the flash proxy badge on your web site or blog, or add it to your Wikipedia profile. If you want your browser to continue to be a proxy after a switch to an opt-in model, click the “Yes” button on the options page.
I have the same problem. Tor (flashproxy) doesn`t work in PC running win xp , however it works in PC runnig win vista.
Same error here, on a Win7 64bit PC:
2013-03-23 13:34:46 flashproxy-reg-email: Failed to register: [Errno 1] _ssl.c:504: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
2013-03-23 13:34:46 flashproxy-reg-email exited with status 1.
Anybody knows what's the culprit?
Using Tor Browser out of the the latest pluggable transports bundle or w/ additional port forwarding result in same situation.