Closed Bug 1959735 Opened 1 year ago Closed 1 year ago

Use WorkerCSPContext for EvalAllowed/WasmEvalAllowed queries

Categories

(Core :: DOM: Workers, task)

task

Tracking

()

RESOLVED FIXED
140 Branch
Tracking Status
firefox140 --- fixed

People

(Reporter: tschuster, Assigned: tschuster)

References

Details

Attachments

(1 file)

We currently cache some CSP enforcement information like mEvalAllowed or mWasmEvalAllowed on the WorkerLoadInfo. It probably makes sense to add WorkerCSPContext::GetAllowsEval/GetAllowsWasmEval (similar to nsCSPContext::GetAllowsEval) instead.

Currently we have pretty bad test coverage of WorkerCSPContext because it's only used for one trusted type check, leading to mistakes like bug 1962090. I think the extended test coverage from using the WorkerCSPContext more broadly for eval should be enough justification for doing this work.

Assignee: nobody → tschuster
See Also: → 1770909
Attachment #9480918 - Attachment description: WIP: Bug 1959735 - Use WorkerCSPContext for eval/wasm-eval queries → Bug 1959735 - Use WorkerCSPContext for eval/wasm-eval queries. r?smaug
Pushed by tschuster@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/8806de01bc76 Use WorkerCSPContext for eval/wasm-eval queries. r=smaug
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
Target Milestone: --- → 140 Branch
QA Whiteboard: [qa-triage-done-c141/b140]
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: