html5 notification permission spam/bomb
Categories
(Firefox :: Site Identity, defect, P2)
Tracking
()
People
(Reporter: felix.bau, Assigned: pbz)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
text/x-phabricator-request
|
pascalc
:
approval-mozilla-beta+
|
Details |
Comment 3•6 years ago
|
||
Comment 5•6 years ago
|
||
Comment 6•6 years ago
|
||
Updated•6 years ago
|
Hi Johann, please comment on this. thanks!
Comment 8•6 years ago
|
||
I don't think this should be changed in DOM land. Extending only the "Never" permission to domain level is a bit ... unprecedented and I'm not sure I have a full grasp of the privacy and compatibility implications at the moment. There are technical challenges with being sub-domain specific for "allow" and domain-specific for "deny" that I personally don't want to shake up at the moment.
"Not Now" is a client-side feature that should prevent the site from asking again immediately until Firefox deems it appropriate. In this case I think we can simply extend the temporary permission check to cover sub-domains, which is much easier.
Considering that Fennec probably won't take this anymore based on its maintenance state I'll claim it for desktop to work on. I'm happy to clone the bug if you'd like to keep it in Fennec land, though.
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 9•6 years ago
|
||
Assignee | ||
Comment 10•6 years ago
|
||
Comment 11•6 years ago
|
||
Comment 12•6 years ago
|
||
Comment 13•6 years ago
|
||
Comment 14•6 years ago
|
||
bugherder |
Comment 15•6 years ago
|
||
We should consider uplifting after this had some bake time. Maybe in a week?
Comment 16•6 years ago
|
||
(In reply to Johann Hofmann [:johannh] from comment #15)
We should consider uplifting after this had some bake time. Maybe in a week?
Johann, do you still want to uplift this?
Comment 17•6 years ago
|
||
Yes, thank you for the reminder, though maybe Paul wants to do the uplift request? :)
Updated•6 years ago
|
Assignee | ||
Comment 18•6 years ago
|
||
Comment on attachment 9056896 [details]
Bug 1492668 - Store temporary site permissions by base domain to mitigate permission notification spam r=johannh
Beta/Release Uplift Approval Request
- Feature/Bug causing the regression: none
- User impact if declined: Websites can abuse notification permission prompts to spam the user.
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: Yes
- If yes, steps to reproduce: Test website: https://evil.pbz.pw/spam/notification-perm-prompt/
- List of other uplifts needed: None
- Risk to taking this patch: Medium
- Why is the change risky/not risky? (and alternatives if risky): Patch is tested and had baketime in nightly.
Medium risk because site permissions has many consumers and there could be side effects we haven't noticed yet. - String changes made/needed:
Assignee | ||
Updated•6 years ago
|
Comment 19•6 years ago
|
||
Let's get it verified on Nightly before uplifting to beta.
Updated•6 years ago
|
Comment 20•6 years ago
|
||
Verified - fixed on latest Nightly 68.0a1 (2019-04-17) (64-bit) on Windows 7/10, Mac OS 10.13 and Ubuntu 16.04
On the https://evil.pbz.pw/spam/notification-perm-prompt/:
- on the notification permission is set to Never Allow, the notification prompt will not be displayed regardless of restarting Nightly, reloading the page in a new or the same tab
- on the https://es-novosti.com/index.php?click_id=3714563925&wmi=1356&lp=5&custom_bg=https://s7.wampi.ru/2018/09/13/PUSLEND.jpg site the notification prompt is instantly blocked and all the sub-domains start loading one by one.
Please let me know if there is anything else that should be checked out.
Comment 21•6 years ago
|
||
Comment on attachment 9056896 [details]
Bug 1492668 - Store temporary site permissions by base domain to mitigate permission notification spam r=johannh
Patch with tests and verified by QA on Nightly, uplift approved for 67 beta 12, thanks
Updated•6 years ago
|
Comment 22•6 years ago
|
||
Setting QE-verify+ flag back as I want it verified on Beta as well.
Comment 23•6 years ago
|
||
bugherder uplift |
Comment 24•6 years ago
|
||
Verified - fixed on latest Beta 67.0b13 (64-bit) on Windows 7/10, Mac OS 10.13 and Ubuntu 16.04
Description
•