Open Bug 1687771 Opened 4 years ago Updated 2 years ago

evaluate proxy api remote code use

Categories

(WebExtensions :: Request Handling, task, P5)

Product:
WebExtensions
Component:
Request Handling
Type:
task
Points:
3

Tracking

(Not tracked)

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

Whiteboard: mv3:m2
Whiteboard: mv3:m2 → mv3:m1
Whiteboard: mv3:m1 → mv3:m1 [mv3-m1]

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]
Points: --- → 3
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.