Closed
Bug 1434276
Opened 7 years ago
Closed 7 years ago
Use MITIGATION_EXTENSION_POINT_DISABLE flag for GMP process.
Categories
(Core :: Security: Process Sandboxing, enhancement, P1)
Tracking
()
RESOLVED
FIXED
mozilla60
| Tracking | Status | |
|---|---|---|
| firefox60 | --- | fixed |
People
(Reporter: bobowen, Assigned: bobowen)
Details
Attachments
(1 file)
|
1.27 KB,
patch
|
jimm
:
review+
|
Details | Diff | Splinter Review |
No description provided.
|
Assignee | |
Comment 1•7 years ago
|
||
|
|
Assignee | |
Comment 2•7 years ago
|
||
Attachment #8946672 -
Flags: review?(jmathies)
|
|
Assignee | |
Comment 3•7 years ago
|
||
Hi Chris - just to let you know that I'm going to add this mitigation to GMP.
Chrome already has this turned on and we have it turned on for content, so I don't expect any issues.
Flags: needinfo?(cpearce)
|
||
Updated•7 years ago
|
Attachment #8946672 -
Flags: review?(jmathies) → review+
Pushed by bobowencode@gmail.com:
https://hg.mozilla.org/integration/mozilla-inbound/rev/64ad3bc4dc26
Use MITIGATION_EXTENSION_POINT_DISABLE flag for GMP process. r=jimm
|
||
Comment 6•7 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
status-firefox60:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla60
You need to log in
before you can comment on or make changes to this bug.
Description
•