Track the amount of Captchas caused by fingerprinting protections
Categories
(Core :: Privacy: Anti-Tracking, task)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox135 | --- | fixed |
People
(Reporter: tschuster, Assigned: fkilic)
References
(Blocks 1 open bug)
Details
Attachments
(17 files, 14 obsolete files)
|
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 |
Enabling fingerprinting protections could cause more sites to show captchas before being allowed to access the page, because it makes our users look less unique. We know this happens when enabling RFP, e.g. bug 1909961 for cloudflare.
One idea for being able to track captchas would be to see how often specific canvas fingerprinters are being used, which often happen together.
Comment 1•1 year ago
|
||
Is the canvas fingerprinting only used after the captcha shows up? I would suspect it's before. So, maybe looking into canvas fingerprinting isn't efficient in detecting captchas. Maybe some info only gets read after showing a captcha. We should rely on those instead.
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
| Assignee | ||
Comment 3•1 year ago
|
||
| Assignee | ||
Comment 4•1 year ago
|
||
Note that this patch doesn't create a metrics.yaml or ping.yaml file. It just provides the plumbing required to call Glean API.
| Assignee | ||
Comment 5•1 year ago
|
||
| Assignee | ||
Comment 6•1 year ago
|
||
| Assignee | ||
Comment 7•1 year ago
|
||
| Assignee | ||
Comment 8•1 year ago
|
||
| Assignee | ||
Comment 9•1 year ago
|
||
| Assignee | ||
Comment 10•1 year ago
|
||
| Assignee | ||
Comment 11•1 year ago
|
||
| Assignee | ||
Comment 12•1 year ago
|
||
| Assignee | ||
Comment 13•1 year ago
|
||
| Assignee | ||
Comment 14•1 year ago
|
||
| Assignee | ||
Comment 15•1 year ago
|
||
| Assignee | ||
Comment 16•1 year ago
|
||
| Assignee | ||
Comment 17•1 year ago
|
||
| Assignee | ||
Comment 18•1 year ago
|
||
| Assignee | ||
Comment 19•1 year ago
|
||
| Assignee | ||
Comment 20•1 year ago
|
||
| Assignee | ||
Comment 21•1 year ago
|
||
| Assignee | ||
Comment 22•1 year ago
|
||
| Assignee | ||
Comment 23•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 24•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 25•1 year ago
|
||
The way this patch stack is structured makes it difficult to review from an architectural standpoint because over halfway through the stack (in D226545) you completely change the architecture. This means that many of my comments on the earlier patches become irrelevant. Can you either restructure the stack so this doesn't happen or give me a clean patch to review in one go?
| Assignee | ||
Comment 26•1 year ago
|
||
Sure, I will. The logic doesn't really change I just export stuff to their own classes but I can see how that changes validity of comments in the old patches (like lets say you wanted to say naming is not good here but then I changed naming and all in the new class implementation etc.), sorry. I'll fix it.
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Comment 27•1 year ago
|
||
Alright I updated it. I removed 3 patches including the one with "refactor the whole thing" patch. Also see this document for implementation specifics and notes https://docs.google.com/document/d/1WVEJgYCWXJVhrXQlYWXWSBNumj_xS3dp49B2gZ0mh90/edit
| Assignee | ||
Comment 28•1 year ago
|
||
| Assignee | ||
Comment 29•1 year ago
|
||
| Assignee | ||
Comment 30•1 year ago
|
||
Comment 31•1 year ago
|
||
The following patches are waiting for review from a reviewer who resigned from the review:
| ID | Title | Author | Reviewer Status |
|---|---|---|---|
| D226922 | Bug 1913421: Detect hCaptcha captchas. r?mossop | fkilic | mossop: Resigned from review |
| D227556 | Bug 1913421: Detect Arkose Labs Captchas. r?mossop | fkilic | mossop: Resigned from review |
:fkilic, could you please find another reviewer?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 33•1 year ago
|
||
| Assignee | ||
Comment 34•1 year ago
|
||
| Assignee | ||
Comment 35•1 year ago
|
||
| Assignee | ||
Comment 36•1 year ago
|
||
| Assignee | ||
Comment 37•1 year ago
|
||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Comment 38•1 year ago
|
||
Comment 39•1 year ago
|
||
Backed out for causing mochitests-plain failures in test_arkose_labs.html.
- Backout link
- Push with failures
- Failure Log
- Failure line: TEST-UNEXPECTED-FAIL | toolkit/components/captchadetection/tests/mochitest/test_arkose_labs.html | Test timed out. -
| Assignee | ||
Comment 40•1 year ago
|
||
The issue was about xorigin tests running on .org instead of .com. Hopefully it should be fixed now.
| Assignee | ||
Comment 42•1 year ago
|
||
Hmm really interesting. Some sort of regex matching issue with the urls i listed in matches section of js window actor. I'll try to remove stuff one by one to see what's going on.
Comment 43•1 year ago
|
||
Comment 44•1 year ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/b10761a94df6
https://hg.mozilla.org/mozilla-central/rev/e8bb11c1c410
https://hg.mozilla.org/mozilla-central/rev/17af42850877
https://hg.mozilla.org/mozilla-central/rev/cab976b11ed5
https://hg.mozilla.org/mozilla-central/rev/555ebf268c2b
https://hg.mozilla.org/mozilla-central/rev/da2a230542bd
https://hg.mozilla.org/mozilla-central/rev/e2d6171d2fba
https://hg.mozilla.org/mozilla-central/rev/edd4c0b4d9ea
https://hg.mozilla.org/mozilla-central/rev/4eb23fa7b448
https://hg.mozilla.org/mozilla-central/rev/3803cd174636
https://hg.mozilla.org/mozilla-central/rev/ffd699eaacb9
https://hg.mozilla.org/mozilla-central/rev/511986d815a6
https://hg.mozilla.org/mozilla-central/rev/dabe3c0f9387
https://hg.mozilla.org/mozilla-central/rev/10f9094f4107
https://hg.mozilla.org/mozilla-central/rev/594f6790bc2d
https://hg.mozilla.org/mozilla-central/rev/88ae4861a8ac
https://hg.mozilla.org/mozilla-central/rev/ecdb537a3742
Description
•