Enable wasm sandboxing on all remaining platforms on automation
Categories
(Core :: Security: Process Sandboxing, task, P1)
Tracking
()
People
(Reporter: glandium, Assigned: glandium)
References
(Blocks 1 open bug)
Details
Attachments
(1 obsolete file)
|
Assignee | |
Comment 1•3 years ago
|
||
|
||
Updated•3 years ago
|
|
||
Comment 3•3 years ago
|
||
Backed out for conflicting with the backout of bug 1727266
Backout link: https://hg.mozilla.org/integration/autoland/rev/7cdffac9fa99cb13b363a037e927ef6bd219a961
|
|
Assignee | |
Updated•3 years ago
|
|
||
Comment 5•3 years ago
|
||
| bugherder | ||
can you please tell which compile switch is needed to enable the wasm sandboxing at configure?
--with-wasm-sandboxed-libraries is not working for me (many python errors in mozbuild)
if thats the correct approach please let me know, so I can open a bug
|
||
Comment 7•3 years ago
|
||
| backout | ||
This was backed out from Beta94 alongside bug 1727266 to resolve some new crashes.
https://hg.mozilla.org/releases/mozilla-beta/rev/04b1d2fd4dda49ded61dad1efa552c784da87cbb
|
|
||
Updated•3 years ago
|
|
|
||
Comment 8•3 years ago
|
||
Misunderstanding, this is still enabled in central.
|
||
Updated•3 years ago
|
|
|
Assignee | |
Comment 9•3 years ago
|
||
(In reply to tt_1 from comment #6)
can you please tell which compile switch is needed to enable the wasm sandboxing at configure?
--with-wasm-sandboxed-libraries is not working for me (many python errors in mozbuild)
if thats the correct approach please let me know, so I can open a bug
It's now enabled by default as of bug 1737911.
Description
•