Closed
Bug 1766828
Opened 3 years ago
Closed 3 years ago
Ship external protocol sandbox restrictions
Categories
(Core :: DOM: Security, task, P3)
Core
DOM: Security
Tracking
()
RESOLVED
FIXED
102 Branch
| Tracking | Status | |
|---|---|---|
| firefox102 | --- | fixed |
People
(Reporter: pbz, Assigned: pbz)
References
()
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
Bug 1735746 added sandbox restrictions for external protocols in Nightly. This bug is for enabling the changes in release.
Feature status in Chrome: https://chromestatus.com/feature/5680742077038592
They are planning to ship this in 103. I suggest we align with that timeline.
Currently the sandbox restriction still breaks Microsoft teams. They are planning to add the new "allow-top-navigation-to-custom-protocols" sandbox flag to fix this.
|
Assignee | |
Comment 1•3 years ago
|
||
|
||
Updated•3 years ago
|
Severity: -- → S3
Priority: -- → P3
Whiteboard: [domsecurity-active]
Pushed by pzuhlcke@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/c3f8f1bdd5cb
Enable external protocol sandbox restrictions in release config. r=ckerschb,annevk
|
||
Comment 3•3 years ago
|
||
| bugherder | ||
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox102:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 102 Branch
|
||
Updated•3 years ago
|
Blocks: CVE-2022-34474
You need to log in
before you can comment on or make changes to this bug.
Description
•