2 ms·
Until proven otherwise, I think Chrome remains the most secure browser. From what I've seen, FF57 only uses one content process by default (at least when you u
by mtgx 9y ago
Until proven otherwise, I think Chrome remains the most secure browser.
From what I've seen, FF57 only uses one content process by default (at least when you upgrade it from FF56), although you can enable up to 7 in settings ( I wish they gave higher numbers, too, like 50, or have a custom field).
Also, Rust is still a small portion of the browser. I'm not sure how big of a portion is of the rendering parts, which are usually the ones causing security issues.
We'll see how it fares at the next Pwn2Own and perhaps in new papers comparing browsers' security over the coming year.
That said, I am excited that Tor will soon use FF59, which should include all of these improvements (but hopefully customized to have improved hardening by default compared to regular Firefox, on all operating systems).
- arghwhat 9y agoFF57 has a relatively small amount of Rust (~160k lines of C++ replaced with ~80k lines of 10x faster Rust). Chrome is "pure" C++, though. More content processes wouldn't do much difference. It doesn't reduce the attack surface (potentially increasing it due to complexity), but only reduce amount of data per process in case you gain read-only access to its memory (which I can't currently think of as being an interesting attack). I would imagine that more content processes is about stability, rather than security. However, splitting larger processes into smaller ones can yield great benefit on the security front. EDIT: FF57 defaults to four content processes.