Hacker News new | past | comments | ask | show | jobs | submit login

This probably got downvoted for snark, but it's true. The worst Chrome might do is help Google target ads better (if you don't change the defaults).

The worst Firefox might do is get your machine pwned.




> The worst Chrome might do is help Google target ads better (if you don't change the defaults).

Chrome is the one running any x86 binary the website presents it with, only trying to run a static verification that it won't do anything evil.

Chrome is far more at risk of pwning you (and NaCl sandbox breakouts have been quite common).


You mean "the website" which is accessed over HTTPS and more likely than not has its key pinned internally?

Point is, Chrome falls every year at Pwn2Own just like every other browser, but only Firefox has been excluded because it's too easy.


> You mean "the website" which is accessed over HTTPS and more likely than not has its key pinned internally?

Any website can run NaCl code, you realize that? Even TIDAL uses it on its site for native playback.

Even pages only accessed over HTTP.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: