Closed
Bug 1547713
Opened 5 years ago
Closed 5 years ago
Remove chrometask_chromescript from eval()-whitelist
Categories
(Core :: DOM: Security, enhancement, P3)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
mozilla68
| Tracking | Status | |
|---|---|---|
| firefox68 | --- | fixed |
People
(Reporter: jallmann, Assigned: jallmann)
References
(Blocks 1 open bug)
Details
(Whiteboard: [domsecurity-backlog1])
Attachments
(1 file)
This occurence of eval() in a file used only for testing (and only for a single test, as it seems) triggers our eval()-Assertion:
https://searchfox.org/mozilla-central/source/testing/mochitest/tests/SimpleTest/ChromeTask.js#62
Under the given circumstances, it seems easiest to flip the eval-exception pref for this case.
|
Assignee | |
Comment 1•5 years ago
|
||
Flip pref to allow the use of eval() in this purely test-related case.
|
|
Assignee | |
Updated•5 years ago
|
Keywords: checkin-needed
Pushed by nbeleuzu@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/45cb80d21409
Remove chrometask_chromescript from eval()-whitelist, r=ckerschb
Keywords: checkin-needed
|
||
Comment 3•5 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
status-firefox68:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla68
You need to log in
before you can comment on or make changes to this bug.
Description
•