Remove WindowServer access from renderer proceses |
||
Issue descriptionWe should attempt to remove access to the WindowServer from renderer processes. Now that we've shipped the v2 sandbox, this should just be a matter of removing the sandbox allow rule, rather than changing any warmup code.
,
Sep 14
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/0a50aa030d7ba3ba6714263aaef7ce24daca6918 commit 0a50aa030d7ba3ba6714263aaef7ce24daca6918 Author: Alex Gaynor <agaynor@mozilla.com> Date: Fri Sep 14 21:12:04 2018 Verify that there are no open connections to the macOS WindowServer A disassembly of CGSSetDenyWindowServerConnections indicates that it only actually does anything when there are no currently open WindowServer connections. There should be no open connections, so we call it and verify that we succeeded. Bug: 880886 Change-Id: I59bce619d1e684da1fc9356a89c129f990c8e91c Reviewed-on: https://chromium-review.googlesource.com/1150668 Commit-Queue: Robert Sesek <rsesek@chromium.org> Reviewed-by: Robert Sesek <rsesek@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Cr-Commit-Position: refs/heads/master@{#591473} [modify] https://crrev.com/0a50aa030d7ba3ba6714263aaef7ce24daca6918/content/renderer/renderer_main_platform_delegate_mac.mm
,
Oct 12
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Sep 6