Move canvas renderings to an actor child from about:fingerprintingprotection
Categories
(Core :: Privacy: Anti-Tracking, task)
Tracking
()
People
(Reporter: fkilic, Assigned: fkilic)
Details
Attachments
(17 files, 1 obsolete file)
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review | |
48 bytes,
text/x-phabricator-request
|
Details | Review |
Hidden browser isn't able get accelerated canvas, so we will move the collection to an actual window.
Assignee | ||
Comment 1•1 month ago
|
||
Updated•1 month ago
|
Assignee | ||
Comment 2•1 month ago
|
||
Updated•29 days ago
|
Assignee | ||
Comment 3•29 days ago
|
||
Assignee | ||
Comment 4•28 days ago
|
||
Assignee | ||
Comment 5•23 days ago
|
||
Assignee | ||
Comment 6•20 days ago
|
||
This can happen if the function that registered the window actor times out
Assignee | ||
Comment 7•19 days ago
|
||
Assignee | ||
Comment 8•19 days ago
|
||
Assignee | ||
Comment 9•19 days ago
|
||
Assignee | ||
Comment 10•19 days ago
|
||
Assignee | ||
Comment 11•19 days ago
|
||
Updated•17 days ago
|
Updated•17 days ago
|
Assignee | ||
Comment 12•17 days ago
|
||
Assignee | ||
Comment 13•17 days ago
|
||
Updated•17 days ago
|
Updated•17 days ago
|
Updated•17 days ago
|
Updated•17 days ago
|
Updated•15 days ago
|
Assignee | ||
Comment 14•15 days ago
|
||
Updated•14 days ago
|
Assignee | ||
Comment 15•14 days ago
•
|
||
DATA REVIEW REQUEST
- What questions will you answer with this data?
How unique is user's webgl info.
More generally: What is the most productive use of engineering time to make fingerprinting an ineffective method of tracking users? As detailed in https://bugzilla.mozilla.org/show_bug.cgi?id=1879151
- Why does Mozilla need to answer these questions? Are there benefits for users?
Do we need this information to address product or business requirements?
We want to improve our fingerprinting defenses. We don't want to guess at what will make an improvement, so we want to make a decision based on data. We also want to know how much of an improvement we have made, so we can state it and know how much further we have to go.
- What alternative methods did you consider to answer these questions?
Why were they not sufficient?
We considered privacy preserving metric collection (DAP), collecting it indirectly (e.g. via hashes of the data), using exisiting (lmited) data we currently collect, not collecting the data at all and using academic literature. These options are detailed in https://docs.google.com/document/d/1m_j0BQEprQleRHZ7tVT7mG-krc8UA171GD5Vl6gZbL0/edit
- Can current instrumentation answer these questions?
As detailed in https://docs.google.com/document/d/1m_j0BQEprQleRHZ7tVT7mG-krc8UA171GD5Vl6gZbL0/edit - some attributes are collected by current instrumentation. However, using this data (and not using the other data we don't collect) will give an incomplete picture that may mislead us into choosing a task that does not make an appreciable change for users. We will also be unable to accurately state the improvement we have made.
- List all proposed measurements and indicate the category of data collection for each
measurement, using the Firefox data collection categories found on the Mozilla wiki.
Measurement Name | Measurement Description | Data Collection Category | Tracking Bug |
---|---|---|---|
characteristics.gl_version_software |
The version of OpenGL supported by the user's system. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_extensions_software |
The list of OpenGL extensions supported by the user's system. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_extensions_raw_software |
The raw list of OpenGL extensions supported by the user's system. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_renderer_software |
The OpenGL renderer string. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_renderer_raw_software |
The raw OpenGL renderer string. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_vendor_software |
The OpenGL vendor string. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_vendor_raw_software |
The raw OpenGL vendor string. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_version_raw_software |
The raw OpenGL version string. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_fragment_shader_software |
Hash of the transformed source of the fragment shader. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_vertex_shader_software |
Hash of the transformed source of the vertex shader. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_minimal_source_software |
Transformed source of the minimal shader. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_params_extensions_software |
The list of GL parameters of the extensions. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_params_v1_software |
The list of GL parameters of GL1. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_params_v2_software |
The list of GL parameters of GL2. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_precision_fragment_software |
Precisions of the fragment shader. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_precision_vertex_software |
Precisions of the vertex shader. | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
- Please provide a link to the documentation for this data collection which
describes the ultimate data set in a public, complete, and accurate way.
This collection is Glean so is documented in the Glean Dictionary.
- How long will this data be collected?
This collection will be collected permanently.
tom@mozilla.com will be responsible for the permanent collections.
- What populations will you measure?
All channels, countries, and locales. No filters.
- If this data collection is default on, what is the opt-out mechanism for users?
These collections are Glean. The opt-out can be found in the product's preferences.
- Please provide a general description of how you will analyze this data.
The general question is "What engineering tasks should we do". To determine that, we will answer sub-questions like:
- How many users are uniquely identifiable via fingerprinting?
- For the users who are not, how large a cohort are they bucketed into?
- What attributes contribute the most to making users unique, or placing them in small buckets
- What attributes correlate with each other, such that we would need to address them in tandem
- Where do you intend to share the results of your analysis?
We hope to publish an academic paper, actually, as this is a significant contribution to the topic of browser fingerprinting. We can also expect to do a blog post. The decisions about what engineering tasks we choose to do to decrease the uniqueness of our users will be filed as Bugzilla Bugs that will contain descriptions of why this is the engineering task to do.
- Is there a third-party tool (i.e. not Glean or Telemetry) that you
are proposing to use for this data collection?
No.
Assignee | ||
Comment 16•14 days ago
|
||
Assignee | ||
Comment 17•14 days ago
•
|
||
DATA REVIEW REQUEST
- What questions will you answer with this data?
How unique is user's webgl info.
More generally: What is the most productive use of engineering time to make fingerprinting an ineffective method of tracking users? As detailed in https://bugzilla.mozilla.org/show_bug.cgi?id=1879151
- Why does Mozilla need to answer these questions? Are there benefits for users?
Do we need this information to address product or business requirements?
We want to improve our fingerprinting defenses. We don't want to guess at what will make an improvement, so we want to make a decision based on data. We also want to know how much of an improvement we have made, so we can state it and know how much further we have to go.
- What alternative methods did you consider to answer these questions?
Why were they not sufficient?
We considered privacy preserving metric collection (DAP), collecting it indirectly (e.g. via hashes of the data), using exisiting (lmited) data we currently collect, not collecting the data at all and using academic literature. These options are detailed in https://docs.google.com/document/d/1m_j0BQEprQleRHZ7tVT7mG-krc8UA171GD5Vl6gZbL0/edit
- Can current instrumentation answer these questions?
As detailed in https://docs.google.com/document/d/1m_j0BQEprQleRHZ7tVT7mG-krc8UA171GD5Vl6gZbL0/edit - some attributes are collected by current instrumentation. However, using this data (and not using the other data we don't collect) will give an incomplete picture that may mislead us into choosing a task that does not make an appreciable change for users. We will also be unable to accurately state the improvement we have made.
- List all proposed measurements and indicate the category of data collection for each
measurement, using the Firefox data collection categories found on the Mozilla wiki.
Measurement Name | Measurement Description | Data Collection Category | Tracking Bug |
---|---|---|---|
characteristics.gl_context_type |
The type of the GL context (EGL, GLX, WGL, etc). | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
characteristics.gl_context_type_software |
The type of the GL context (EGL, GLX, WGL, etc). | technical | https://bugzilla.mozilla.org/show_bug.cgi?id=1922506 |
- Please provide a link to the documentation for this data collection which
describes the ultimate data set in a public, complete, and accurate way.
This collection is Glean so is documented in the Glean Dictionary.
- How long will this data be collected?
This collection will be collected permanently.
tom@mozilla.com will be responsible for the permanent collections.
- What populations will you measure?
All channels, countries, and locales. No filters.
- If this data collection is default on, what is the opt-out mechanism for users?
These collections are Glean. The opt-out can be found in the product's preferences.
- Please provide a general description of how you will analyze this data.
The general question is "What engineering tasks should we do". To determine that, we will answer sub-questions like:
- How many users are uniquely identifiable via fingerprinting?
- For the users who are not, how large a cohort are they bucketed into?
- What attributes contribute the most to making users unique, or placing them in small buckets
- What attributes correlate with each other, such that we would need to address them in tandem
- Where do you intend to share the results of your analysis?
We hope to publish an academic paper, actually, as this is a significant contribution to the topic of browser fingerprinting. We can also expect to do a blog post. The decisions about what engineering tasks we choose to do to decrease the uniqueness of our users will be filed as Bugzilla Bugs that will contain descriptions of why this is the engineering task to do.
- Is there a third-party tool (i.e. not Glean or Telemetry) that you
are proposing to use for this data collection?
No.
Assignee | ||
Comment 18•13 days ago
|
||
WSI_INFO is also very similar to this, but WSI_INFO contains a lot of info that we already collect, also there's a note about old Android devices crashing when queried, see https://searchfox.org/mozilla-central/rev/dca2603d55b5b39d3b8ab8e93c08b42563f5aad8/gfx/gl/GLContextProviderEGL.cpp#581-585
Assignee | ||
Comment 19•13 days ago
|
||
Updated•13 days ago
|
Assignee | ||
Comment 20•14 hours ago
|
||
Updated•14 hours ago
|
Comment 21•14 hours ago
|
||
Comment 22•12 hours ago
|
||
Backed out for causing bustages at WebGLContext.cpp.
Backout link: https://hg.mozilla.org/integration/autoland/rev/b2f54c74b51a776e3ff53494413c4207e61e41ab
Push where failures started: https://treeherder.mozilla.org/jobs?repo=autoland&selectedTaskRun=EIqKre1IRzKiq0yGi5TSqQ.0&resultStatus=testfailed%2Cbusted%2Cexception%2Cretry%2Cusercancel&revision=6207900515021ab89f1175917355114ded03f4d5
Failure log: https://treeherder.mozilla.org/logviewer?job_id=481441863&repo=autoland&lineNumber=19614
Description
•