Open Bug 1685123 Opened 5 years ago Updated 3 months ago

implement manifest sandbox support

Categories

(WebExtensions :: General, enhancement, P3)

enhancement

Tracking

(Not tracked)

ASSIGNED

People

(Reporter: mixedpuppy, Assigned: robwu)

References

(Blocks 2 open bugs)

Details

(Whiteboard: [design-decision-needed])

Attachments

(1 file, 3 obsolete files)

with manifest v3 csp changes, the sandbox functionality becomes important as a way to allow extensions to continue using javascript frameworks that still use eval or other eval-like constructs. We should support sandbox for those use cases.

https://developer.chrome.com/docs/extensions/mv3/manifest/sandbox/

Assignee: nobody → mixedpuppy
No longer blocks: 1594235
Attachment #9196189 - Attachment is obsolete: true

This bug is going on hold for now, we will revisit whether we want to support sandbox sometime down the road. part 1 might be something we split out to its own bug.

Priority: P2 → P3
Depends on: 1700762

Comment on attachment 9195509 [details]
Bug 1685123 part 1: sandboxed extensions pages are allowed to load their own resources

Revision D100834 was moved to bug 1700762. Setting attachment 9195509 [details] to obsolete.

Attachment #9195509 - Attachment is obsolete: true
Attachment #9196187 - Attachment description: Bug 1685123 part 2: add sandbox to extension manifest and policy → Bug 1685123 add sandbox to extension manifest and policy
Attachment #9196188 - Attachment description: Bug 1685123 part 3: apply sandbox base csp to sandboxed pages → Bug 1685123 apply sandbox base csp to sandboxed pages
Duplicate of this bug: 1798460
Whiteboard: [design-decision-needed]

Would this sandbox allow for extensions that do browser automation, i.e. extensions that can execute Javascript received from a (trusted) native application? It is currently possible to have a native application send Javascript code for an extension to execute, which is mighty useful. It is code existing on the user's computer, sent to the Firefox extension by a native application that already has local execution privileges, so there is no real escalation of privileges by the extension's ability to do eval, as I understand it. (Eval is currently needed for that in combination with native messaging.)

Assignee: mixedpuppy → nobody
See Also: → 1896824
See Also: → 1901967
Assignee: nobody → rob
Status: NEW → ASSIGNED
Attachment #9196187 - Attachment is obsolete: true
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: