Re:FBI Exploits Tor Browser Bundle to Target Child Pornograp...
by coderzach on Tuesday August 05, 2014 @01:54PM
(#8138290)
Sandboxed processes. There are limits to what code running in chrome can do. AFAIK firefox provides no such guarantees.
Re:FBI Exploits Tor Browser Bundle to Target Child Pornograp...
by Freaky on Tuesday August 05, 2014 @03:56PM
(#8138974)
Firefox is moving in that direction at least: https://wiki.mozilla.org/Electrolysis
Re:FBI Exploits Tor Browser Bundle to Target Child Pornograp...
by comex on Tuesday August 05, 2014 @03:15PM
(#8138738)
It's certainly true that using NoScript prevents most browser exploits (though not all), and that if you're strongly concerned about privacy, you should use it. And make sure not to disable it for any trusted darknet sites, since as this article reminds, they have a habit of being compromised... I'm not trying to be sarcastic - this is totally reasonable for many use cases.
But the default browser bundle leaves JavaScript enabled by default for good reasons[1], and if you want higher security with JavaScript enabled and/or against non-JS exploits, Chrome's process sandbox is a big deal, and will probably keep it significantly more secure than Firefox for a good amount of time.
Re:FBI Exploits Tor Browser Bundle to Target Child Pornograp...
by debux on Tuesday August 05, 2014 @01:51PM
(#8138260)
NoScript equivalent for Chrome is "HTTP Switchboard"
Re:FBI Exploits Tor Browser Bundle to Target Child Pornograp...
by wtallis on Tuesday August 05, 2014 @01:56PM
(#8138307)
Only superficially, and even then, they're not really equivalent. HTTP Switchboard has some blocking features that NoScript users need to use things like AdBlock Plus and RequestPolicy to get. NoScript's features aside from script and plugin blocking are completely beyond the scope of HTTP Switchboard, and some of them are completely unique to NoScript.
(Aside from the process-per-tab model, what's Chromium got out of the box that Firefox still lacks?)