Closed Bug 1415874 Opened 8 years ago Closed 8 years ago

Add the canvas/extractData permission to SitePermissions.jsm when privacy.resistFingerprinting is set to true

Categories

(Firefox :: Site Identity, defect, P3)

Product:
Firefox
Component:
Site Identity
Type:
defect

Tracking

()

Status:
RESOLVED DUPLICATE of bug 1413780
Tracking Flags:
Tracking Status
firefox57 --- wontfix
firefox58 --- affected

People

(Reporter: johannh, Unassigned)

References

Details

(Whiteboard: [fingerprinting])

Reviewing the patch in bug 967895 I said it's fine to ignore exposing canvas permission settings in the UI for now, since the feature is behind the privacy.resistFingerprinting pref. Unfortunately, the Firefox - Tor integration in general and this feature specifically has been advertised in numerous articles around the web, so that we now have users with problems like this one: https://www.reddit.com/r/firefox/comments/7bmmhp/how_do_you_accesschange_permissions_to_canvas/ I'd really like to prevent more people from sharing code that manipulates permissions.sqlite directly (or, even worse, executes chrome-privileged code in the browser toolbox). So it would be great if we could give everyone a way to reset this permission soon.
This can probably live in the front-end component.
status-firefox57: --- → wontfix
status-firefox58: --- → affected
Component: Canvas: 2D → Site Identity and Permission Panels
Flags: qe-verify+
Priority: -- → P3
Product: Core → Firefox
Whiteboard: [fingerprinting]
I think this is a duplicate of Bug 1413780 ?
Flags: needinfo?(jhofmann)
Oh, yes, but it's in the wrong component :) I'll move it, thank you!
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(jhofmann)
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.