Re:What a one line change did to the Chrome sandbox
by ocdtrekkie on Thursday April 23, 2020 @09:21AM
(#22955616)
Edge would both have all the security work of Chrome (as it's a fairly close fork) but all of the security improvements that Google refuses to add, such as blocking third party tracking scripts and cookies. The latter part is where you're most likely to find malware, so a browser that refuses to act on it is not a secure browser. Firefox, Safari, Edge, and basically everyone but Chrome have implemented significant blocking on third party scripting that Google refuses to build into their browser.
Bear in mind, browser security comes from many levels. A sandbox escape first requires that someone has gotten malicious code to execute in your browser. And the first line of defense is blocking a lot of extraneous and harmful code from running in the first place.
Re:What a one line change did to the Chrome sandbox
by jedimastert on Thursday April 23, 2020 @10:50AM
(#22956628)
Can you talk abou wha kind of malware comes from JS scripts?
Re:What a one line change did to the Chrome sandbox
by woodrowbarlow on Thursday April 23, 2020 @11:19AM
(#22956970)
here is a detailed look at one particular example:
https://securelist.com/chrome-0-day-exploit-cve-2019-13720-u...
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.
Re:What a one line change did to the Chrome sandbox
by snazz on Thursday April 23, 2020 @09:03AM
(#22955447)
Assuming the "customizers" haven't messed up the sandbox, any Chromium-based browser is well-protected. You can visit chrome://sandbox to see which features are enabled. If you're talking about the new Edge, I think that includes the same sandboxing as regular Chrome.
Re:What a one line change did to the Chrome sandbox
by floatingatoll on Thursday April 23, 2020 @01:14PM
(#22958279)
This post does not offer evidence that could either support or contradict your question.
Thx