|
|
|
|
|
by techntoke
2162 days ago
|
|
If they would just use a container sandbox and AppArmor/Seccomp/etc we wouldn't be stuck on this JavaScript monster we've created that still allows companies to spy on every mouse movement and track you around the web by default, but now requires 100s of unvetted JavaScript modules and dependencies for a framework to do the most simple tasks that should be included by default in HTML. |
|
A) It's not a good idea. The Chrome sandbox is arguably a lot stronger than Apparmor/ Seccomp. A native program in Apparmor or SELinux can still make virtually arbitrary system calls, whereas an attacker who has compromised a Javascript renderer can not. Further, The attacker would have to own the renderer first, whereas you're talking about just giving native execution rights. Further than that, you can just Apparmor/seccomp chrome? So just go do that? I've done it myself.
B) The attacks described in the post have nothing to do with code execution on your system. They're talking about attacks like XSS, which would exist in any language that provides the ability to manipulate the DOM with strings - so, any of the ones that would be useful.