abrahamjuliot / creepjs

Creepy device and browser fingerprinting
MIT License
1.47k stars 188 forks source link

Collect resources #52

Closed abrahamjuliot closed 3 years ago

abrahamjuliot commented 4 years ago

Papers

Articles

Talks

Researchers

Test Sites

Test Suites

Stats

API Documentation

abrahamjuliot commented 4 years ago

use js to detect and omit broken links

Thorin-Oakenpants commented 4 years ago

https://arxiv.org/pdf/1811.07153.pdf wasn't in my collection

abrahamjuliot commented 4 years ago

Sweet! Added it

Thorin-Oakenpants commented 4 years ago

here's what a top moz sec dev said about it to me in Dec 2018

This one kind of sucks. There are no reasonable countermeasures. Page coloring looked interesting, but AFAICT that was an idea from the early 2000s that hasn't been revisited?

The 100ms resolution helps; but it isn't the complete answer (and I want to reduce it anyway if we can achieve the same security boundary using fuzzyfox.)

Maybe the answer is something more complicated? Degrading it dynamically (throttling) if we detect repeated calls and throw a permission prompt (with or without the doorhanger)?

Thorin-Oakenpants commented 4 years ago

2020: https://lukaszolejnik.com/SheddingLightWebPrivacyImpactAssessmentIWPE20.pdf blog: https://blog.lukaszolejnik.com/shedding-light-on-designing-web-features-with-privacy-risks-impact-assessments-case-study/

Thorin-Oakenpants commented 3 years ago

2018 - Clock Around the Clock - 10.1145-3243734.3243796.pdf

abrahamjuliot commented 3 years ago

I moved this to a repo. Feel free to join and update (and/or open issues) I plan to add small code samples too.