News for hackers. Stuff that matters.
Re:What a one line change did to the Chrome sandbox by amenod on Thursday April 23, 2020 @09:09AM (#22955482)
Not necessarily. Firefox has its own set of protections and even introduced a new language (Rust) to deal with common security vulnerabilities without sacrifising speed.

But the takeaway from this post is more that perfect safety is difficult / impossible to achieve.

Re:What a one line change did to the Chrome sandbox by ta1771 on Thursday April 23, 2020 @10:51AM (#22956638)
Firefox runs multiple sites in a single process, its sandboxing doesn't come close.
Re:What a one line change did to the Chrome sandbox by cmeacham98 on Thursday April 23, 2020 @11:11AM (#22956882)
This hasn't been true for years (https://wiki.mozilla.org/Electrolysis)
Re:What a one line change did to the Chrome sandbox by sciurus on Thursday April 23, 2020 @02:18PM (#22959116)
Actually, it is still true. Electroloysis split up Firefox into multiple processes, but not every site gets its own process. Work is underway to change this and achieve full site isolation in https://wiki.mozilla.org/Project_Fission.

(Disclosure: I work for Mozilla, but not on this)

Re:What a one line change did to the Chrome sandbox by Drdrdrq on Thursday April 23, 2020 @11:08AM (#22956842)
Afaik, it uses Chromium's sandboxing?

That said, safety is about much more than just sandboxing.