Closed Bug 1706345 Opened 4 years ago Closed 4 years ago

Telemetry for IPC vetting should account for manual testing where chrome-debugging is enabled

Categories

(Core :: DOM: Security, task, P1)

Product:
Core
Component:
DOM: Security
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
90 Branch
Tracking Flags:
Tracking Status
firefox90 --- fixed

People

(Reporter: freddy, Assigned: ckerschb)

References

Details

(Whiteboard: [domsecurity-active])

Attachments

(1 file)

Bug 1706345: Do not report Telemetry for IPC based Principal vetting if chrome debugging is enabled
(deleted), text/x-phabricator-request
Details

Our IPC blog post encourages security testing with faked principals. Would be good if deliberate security testing wouldn't count for our measurements.

Severity: -- → S2
Status: NEW → ASSIGNED
Priority: -- → P1
Whiteboard: [domsecurity-active]
Pushed by mozilla@christophkerschbaumer.com: https://hg.mozilla.org/integration/autoland/rev/38e917aedf96 Do not report Telemetry for IPC based Principal vetting if chrome debugging is enabled r=freddyb,Honza,jdescottes

https://hg.mozilla.org/mozilla-central/rev/38e917aedf96

Status: ASSIGNED → RESOLVED
Closed: 4 years ago
status-firefox90: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 90 Branch
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: