Open Bug 1381019 (win32k-lockdown) Opened 3 years ago Updated 2 days ago
[meta] Remove win32k access from content process
This is a meta bug for work towards removing win32k usage from the content process, and using the windows8+ mitigation policy to disable access to it. This work is currently in the research/scoping phase - it is known that we make use of win32k APIs in the content process and we need to establish where and come up with a plan for dealing with all of them.
You need to log in before you can comment on or make changes to this bug.