2
edits
Fingerprinting: Difference between revisions
Jump to navigation
Jump to search
→Extra credit: canvas fix
(→Extra credit: about canvas pixels fingerprinting) |
(→Extra credit: canvas fix) |
||
| Line 91: | Line 91: | ||
Examples: | Examples: | ||
== Other data acquired via plugins == | == Other data acquired via plugins == | ||
| Line 134: | Line 133: | ||
Things like geolocation, database access and such require the user to grant permission for a given site. For geolocation, this is done with an infobar. We should do everything we can to make it clear to users what they're providing, and give them centralized control of those permissions in the privacy panel. This is what the UX privacy proposals seek to do. | Things like geolocation, database access and such require the user to grant permission for a given site. For geolocation, this is done with an infobar. We should do everything we can to make it clear to users what they're providing, and give them centralized control of those permissions in the privacy panel. This is what the UX privacy proposals seek to do. | ||
== HTML5 Canvas == | |||
"After plugins and plugin-provided information, we believe that the HTML5 Canvas is the single largest fingerprinting threat browsers face today." - Tor Project. | |||
Original research: [http://cseweb.ucsd.edu/~hovav/dist/canvas.pdf Pixel Perfect: Fingerprinting Canvas in HTML5], demo: [https://www.browserleaks.com/canvas HTML5 Canvas Fingerprinting]. | |||