Closed
Bug 1759998
Opened 3 years ago
Closed 3 years ago
Remove accepting non-local connections (including the "remote.force-local" preference)
Categories
(Remote Protocol :: Agent, task, P2)
Remote Protocol
Agent
Tracking
(firefox101 fixed)
RESOLVED
FIXED
101 Branch
Tracking | Status | |
---|---|---|
firefox101 | --- | fixed |
People
(Reporter: whimboo, Assigned: whimboo)
References
Details
(Whiteboard: [bidi-m3-mvp])
Attachments
(1 file)
This preference is basically unused and also redundant with the opt-in host list. As such any trace should be removed.
Assignee | ||
Updated•3 years ago
|
Points: --- → 1
Comment 1•3 years ago
|
||
As mentioned in Bug 1722090, we might also want to remove the ability to start the RemoteAgent on anything but localhost for now and remove the related browser chrome mochitests which exercise this feature.
Assignee | ||
Comment 2•3 years ago
|
||
Updating the summary based on the steps that need to be done here.
Summary: Remove usage of the "remote.force-local" preference → Remove accepting non-local connections (including the "remote.force-local" preference)
Assignee | ||
Comment 3•3 years ago
|
||
Updated•3 years ago
|
Assignee: nobody → hskupin
Status: NEW → ASSIGNED
Updated•3 years ago
|
Priority: P3 → P2
Pushed by hskupin@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/0ae0675d4bcd
[remote] Only accept system-local loopback WebSocket connections for clients. r=webdriver-reviewers,jdescottes
Comment 5•3 years ago
|
||
bugherder |
Status: ASSIGNED → RESOLVED
Closed: 3 years ago
status-firefox101:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 101 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•