Closed Bug 1164090 Opened 10 years ago Closed 10 years ago

BHR reports full file paths

Categories

(Toolkit :: Telemetry, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla41
Tracking Status
firefox41 --- fixed

People

(Reporter: vladan, Assigned: jchen)

References

Details

Attachments

(1 file)

The following BHR hang from my about:telemetry page contains a full file path, including the username. This is a privacy risk. It looks like it might be a bug in how max-length truncation is done. Gecko-Hang-13 Startup::XRE_Main nsInputStreamPump::OnInputStreamReady nsInputStreamPump::OnStateStop nsHttpChannel::OnStopRequest nsXMLHttpRequest::OnStopRequest EventDispatcher::Dispatch testpilot/modules/remote-experiment-loader.js:32 testpilot/modules/setup.js:742 C:\Users\workvladan\AppData\Roaming\Mozilla\Firefox\Profiles\r4yfabeb.aurora1\TestPilotExperimentFiles\heartbeat-response-tp-ex testpilot/modules/setup.js:751 testpilot/modules/experiment_data_store.js:27 testpilot/modules/dbutils.js:25 mozStorageConnection::initialize 1 samples, average = 0, sum = 0
Flags: needinfo?(nchen)
Yeah, it looks like a bug from a combination of using a file directory (not resource:// or chrome://) and using the Windows path separator ('\')
Flags: needinfo?(nchen)
This patch makes us check for Windows path separators too, and if we find it, we use that to derive the path basename.
Attachment #8604787 - Flags: review?(snorp)
Attachment #8604787 - Flags: review?(snorp) → review+
Assignee: nobody → nchen
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla41
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: