Tor Browser 4.0.2 is released
Here is the changelog since 4.0.1:
- All Platforms
- Update Firefox to 31.3.0esr
- Update NoScript to 22.214.171.124
- Update HTTPS Everywhere to 4.0.2
- Update Torbutton to 126.96.36.199
- Bug 13019: Synchronize locale spoofing pref with our Firefox patch
- Bug 13746: Properly link Torbutton UI to thirdparty pref.
- Bug 13742: Fix domain isolation for content cache and disk-enabled
- Bug 5926: Prevent JS engine locale leaks (by setting the C library
- Bug 13504: Remove unreliable/unreachable non-public bridges
- Bug 13435: Remove our custom POODLE fix (fixed by Mozilla in 31.3.0esr)
- Bug 13443: Fix DirectShow-related crash with mingw patch.
- Bug 13558: Fix crash on Windows XP during download folder changing
- Bug 13594: Fix update failure for Windows XP users
Not sure what is going on, honestly, as I have never seen this behavior. It might be the best to start over with a fresh new bundle and check whether the update to the next Tor Browser version behaves the same which might indicate that there is indeed a bug that is not detected yet.
The new update did block everything on my PC. I could not open Tor anymore. Something is wrong with this update. I had to delete it. After I took it of my PC everything worked fine again.
The Autoupdate functionality is seriously borked. Even though it is supposed to be an option, I have just been downloading the TBB bundle and doing the old 'manual upgrade' route because of the horror stories I have read on the internet.
An auto-updating secure browser sounds good in theory but in practice, considering the number of locations where people might put it? It just does not work.