Closed Bug 1177889 Opened 11 years ago Closed 11 years ago

Investigate the URL prefs TelemetryEnvironment records by value

Categories

(Toolkit :: Telemetry, defect)

Product:
Toolkit
Component:
Telemetry
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME
Tracking Flags:
Tracking Status
firefox42 --- affected

People

(Reporter: gfritzsche, Unassigned)

Details

TelemetryEnvironment records the preference values for 8 different prefs that contain URLs: https://hg.mozilla.org/mozilla-central/annotate/56e207dbb3bd/toolkit/components/telemetry/TelemetryEnvironment.jsm#l83 This seems pretty privacy-sensitive, i wonder if there is a use-case for all of those or whether we shouldn't just record their "default" state instead of the full value.
ni?ally for potential investigation.
Flags: needinfo?(ally)
I made this by value intentionally: we don't expose these "preferences" in the browser UI, and really they should never have a non-default value. If there is a non-default value, it has been hijacked by some extension or other attacker and we want to know what the hijacked value is. So I believe that this is WFM unless there is some additional backstory.
Ben, IIRC the question is whether this belongs in FHR over telemetry.
Flags: needinfo?(ally) → needinfo?(benjamin)
Yes. We want hijacking to show up in the environment which will be available to FHR/self-support as well as SUMO.
Status: NEW → RESOLVED
Closed: 11 years ago
Flags: needinfo?(benjamin)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.