![]() This means that simply extracting a 4.0 Tor Browser over a 3.6.6 Tor Browser will not work. This release also features an in-browser updater, and a completely reorganized bundle directory structure to make this updater possible. Note though that we still need to improve meek's performance to match other transports, though. In fact, we believe that both meek-amazon and meek-azure will work in China today, without the need to obtain bridge addresses. More importantly for censored users who were using 3.6, the 4.0 series also features the addition of three versions of the meek pluggable transport. The primary user-facing change since the 3.6 series is the transition to Firefox 31-ESR. Additionally, due to the POODLE attack, we have also disabled SSLv3 in this release. This release features important security updates to Firefox. The first release of the 4.0 series is available from the Tor Browser Project page and also from our distribution directory. Ticket numbers are now listed in the post. ![]() Update (Oct 16 20:35 UTC): The meek transport still needs performance tuning before it matches other more conventional transports. Update (Oct 25 02:32 UTC): If you are unhappy with the new Firefox 31 UI, please check out Classic Theme Restorer. ![]() This is a workaround reported to help while the investigation is still on-going. Update (Oct 22 13:15 UTC): Windows users that are affected by Tor Browser crashes might try to avoid this problem by opening "about:config" and setting the preference "" to "false". ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |