Open
Bug 1687771
Opened 4 years ago
Updated 2 years ago
evaluate proxy api remote code use
Categories
(WebExtensions :: Request Handling, task, P5)
WebExtensions
Request Handling
Tracking
(Not tracked)
NEW
People
(Reporter: mixedpuppy, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: mv3:future [mv3-future] )
Passing a script as a string to proxy.settings is not uncommon, we will need to consider potential changes for MV3
|
Reporter | |
Updated•3 years ago
|
Whiteboard: mv3:m2
|
|
Reporter | |
Updated•3 years ago
|
Whiteboard: mv3:m2 → mv3:m1
|
|
Reporter | |
Updated•3 years ago
|
Whiteboard: mv3:m1 → mv3:m1 [mv3-m1]
|
||
Updated•3 years ago
|
See Also: → https://jira.mozilla.com/browse/WEBEXT-16
|
|
Reporter | |
Comment 1•3 years ago
|
||
In terms of remote code execution we wont make any change to the proxy api. We should probably consider some minor level of compatibility with the chrome proxy api, but that would be far future. Using the Proxy.PacScript format however, may be a good improvement to make for handling code in strings.
https://developer.chrome.com/docs/extensions/reference/proxy/#type-PacScript
Priority: -- → P5
Whiteboard: mv3:m1 [mv3-m1] → mv3:future [mv3-future]
|
|
||
Updated•3 years ago
|
Points: --- → 3
|
|
||
Updated•2 years ago
|
Whiteboard: mv3:future [mv3-future] → mv3:future [mv3-future]
You need to log in
before you can comment on or make changes to this bug.
Description
•