3 ms·
Looks like the Firefox-based Tor Browser plans to lag a day behind, on an update for a critical vulnerability that's disclosed by the Mozilla update, like they
by neilv 7y ago
Looks like the Firefox-based Tor Browser plans to lag a day behind, on an update for a critical vulnerability that's disclosed by the Mozilla update, like they did the last time. (Does that lag leave a substantial window for second-tier actors to compromise some security-sensitive dissidents and journalists?)
Also, a bit less concerning to me, the Debian package of `firefox-esr` still hasn't been released, as I type this, hours later.
Of course this is a tricky problem, but should there be more coordination on such updates, in the spirit of responsible disclosure?
- Yoric 7y agoI suspect that the ~1 day delay is just the time needed to run automated tests, rebuild packages, retest them, upload them on the various channels, turn updates on, etc. I've worked with people who work on release engineering. Many things can go wrong by accident and silently, so you take your time to avoid distributing a broken binary that you could not upgrade.
- neilv 7y agoOf course, but perhaps that can be coordinated better?
- ASalazarMX 7y agoDoesn't Tor Browser disable JavaScript by default?
- neilv 7y agoYes. In practice, users will selectively enable JS, both intentionally (because so many sites require JS, to be minimally usable), and accidentally because the particular JS-disabling add-on that TB currently uses still has a complicated UI (though it's much improved from earlier). (I made one of the early tracker-blocking rulesets, and, for the last few years, as a side project, have been building a new practical dataset of specific sites' JS dependencies and third-party requests. I'm up to over 10,000 necessary whitelist rules, which I add to throughout each day, in my own normal use. That 10,000 doesn't include blanket whitelisting of many popular JS CDN URLs, for all domains, which I eventually had to do because of current tool support, and most sites needed them, and there's something privacy&security-friendly that could be done in the browser about those URLs in particular.)