What’s Next for Multi-Process Firefox

Re:What’s Next for Multi-Process Firefox by drdaeman on Tuesday August 02, 2016 @07:58PM (#12214384)

> Which are ...?

seccomp.

Local code execution doesn't mean a thing (except for wasted CPU cycles and/or memory) if number of syscalls the process can do is limited to the bare minimum.

[ Parent | on HN ]

Re:What’s Next for Multi-Process Firefox by ryuuchin on Tuesday August 02, 2016 @10:16PM (#12215109)

And the Windows equivalent (win32k lockdown)[1]. This restricts a number of win32k syscalls including all GDI ones. Chrome already uses this mitigation for renderer processes and has support for PPAPI plugin processes on their dev/beta channels.

[1] https://msdn.microsoft.com/en-us/library/windows/desktop/hh8...

[ Parent | on HN ]