4 ms·
I noticed that Plausible claims to measure traffic without being able to persistently identify users, but https://plausible.io/data-policy https://plausible.io/
by Sephr 6y ago
I noticed that Plausible claims to measure traffic without being able to persistently identify users, but https://plausible.io/data-policy https://plausible.io/data-policy states that they store the following:
hash(daily_salt + website_domain + ip_address + user_agent)
There are optimizations that can help brute-force the enumeration of customer domains, browser UAs, and IP addresses (e.g. in some cases you could enumerate only residential ISPs).
Update: I mis-interpreted "rotating salt" to mean something that could be re-computed on Plausible's backend. It appears that the salt is random[1] and generated on the client-side, which makes this hash much more secure.
1. https://github.com/plausible/analytics/blob/master/lib/plausible/session/salts.ex#L45 https://github.com/plausible/analytics/blob/master/lib/plaus...
- turtle99 6y agoHow can you know if an IP adress is residential or not? Are there API / list of know IP ranges?
- jan6 6y agoI'd think you can see who owns the IP range and check if it's some ISP... probably some api somewhere also... oooor just check the reverse dns and see if it's dyn.someISP
- Sephr 6y agoIt is possible to optimization enumeration of residential ISPs by subtracting datacenter IP addresses (among other tricks I would imagine). I've targeted residential ISPs before in this project: https://eligrey.com/blog/zerodrop/ https://eligrey.com/blog/zerodrop/