6 ms·
There are two solutions I see. 1) Regulation. Maybe it'll happen, I don't have much hope of it being done intelligently. 2) Feed them garbage data. We just n
by shkkmo 12y ago
There are two solutions I see.
1) Regulation. Maybe it'll happen, I don't have much hope of it being done intelligently.
2) Feed them garbage data.
We just need a database of live UIDH numbers and a browser extension to inject a random UIDH number from that list into the header.
- discardorama 12y agoor 3) Contact some of Turn's biggest clients and shame them publicly.
- MBlume 12y agoThis is fantastic and I'd install it in a heartbeat
- x0x0 12y agoverizon overrides; I'm not a web engineer but (I think) ssl protects tcp headers. if so, it's probably the only technical solution is either ssl everywhere or an ssl proxy run by users
- dllthomas 12y agoI interpreted the suggestion as for those not using Verizon to inject fake UIDH. Of course, this could be filtered by making sure the traffic is actually coming from Verizon's networks...
- hackuser 12y ago> 1) Regulation. Maybe it'll happen, I don't have much hope of it being done intelligently Why so hopeless? My water is clean, airplanes and roads are safe, retail banks don't lose their customer's savings, etc. Not all regulation works, but this one is pretty straightforward.
- JadeNB 12y ago> Why so hopeless? Because the current US political climate is not in favour of regulations. It is true that we have all the regulations you describe, but each was fought tooth and nail when introduced! EDIT: Original post had slightly more pointed political language.
- rubbingalcohol 12y agoStep 1: Site operators install backend library to detect uid cookies and send them via API to a central database Step 2: Privacy-minded activists install a browser extension that reads the uids from central database and spoofs HTTP headers with them. Extension could even cycle through uids on a daily basis to cause more mayhem. Result: with just a few big sites running this, a few thousand people with the extension could irreparably corrupt the uid header's "uniqueness" and it could no longer be relied upon to respawn a lost cookie session. Because Turn wouldn't know whether it's a real mobile Verizon user, or a jackass with an extension. Shameless plug: I've already written a browser extension http://flagger.io http://flagger.io that spoofs HTTP headers in Chrome and Firefox. Would be easy to add this functionality if people can help on the backend side (writing libraries for node/python/ruby/php/etc.)
- No1 12y agoStep 3: Turn ignores UIDH headers originating from non-Verizon IPs and Verizon replaces any user-generated UIDH header. Your solution is not going to fool anyone.
- rubbingalcohol 12y agoReading through the original report, I'd doesn't seem that Turn's handling of the header is very sophisticated, in fact they just dumbly accept whatever header you give them. (Interestingly unless they take extra precautions, this exposes them to a CSP sandboxing vulnerability) Turn needs to handle these headers basically in realtime, and while I'm not saying it would be impossible to do IP filtering on a header, it would be expensive. If outsmarting them became a cat and mouse game and people stay ahead of them at any point, that would be good enough to make third party companies that rely on Turn's zombie cookies to lose confidence. Unless turn publishes more info about how they circumvent the circumvention, and this would implicate them further politically and legally. What they are doing is immoral and probably illegal.
- richardwhiuk 12y agoIP filtering compared to checking a HTTP header is trivial - it isn't going to be expensive.
- nl 12y agoYou can't feed them garbage. Verizon operates at the network layer - if you are on their network presumably they will copy the real value over your garbage value. If you aren't on their network then they can check IP address and ignore values not from the Verizon subnets. There are a couple of other solutions you haven't mentions: VPNs: Annoying and currently too hard for most people. Perhaps it is time for device (PC and mobile) manufactures to consider offering VPNs integrated with their devices. Competition: If the US had a more competitive broadband market then people could choose other providers. Legal action: If Verizon was sued and lost over this then it could have a cautionary effect. However, the loss would have to be huge for it to have an impact, and large financial settlements generally require proof of significant harm. That's going to be hard in this case.
- JohnTHaller 12y agoTrue, but an enterprising individual could write an extension to cause non-Verizon users to start feeding fake unique identifiers into their own streams. Heck, you may even be able to hijack a website login using it.
- julianj 12y agosomething like this? https://github.com/lightswitch05/Bogus_X-UIDH https://github.com/lightswitch05/Bogus_X-UIDH
- JohnTHaller 12y agoExactly. But instead of using it to try to change your UIDH within Verizon, it should encourage non-Verizon customers to just pollute the space with random UIDH values from all over the place.
- nl 12y agoAnd (as I previously noted) all Verizon has to do is *check the IP address of the client(!). They know the IPs they own. Assuming that your adversary is dumb as well as malicious is a mistake.
- msabalau 12y agoRegarding regulation, if, as the EFF suggests may be the case, Turn is causing the companies they do business with to violate their stated privacy policies, it would seem that the FTC could take enforcement action without new regulation being needed. An indirect way of kicking in Turn's teeth, but perhaps one that would work.
- pdkl95 12y agoHmm... garbage doesn't work beause they override the UIDH as a MitM. So maybe this fact could be exploited in the opposite direction: Start using the X-UIDH: header for some prominent but non-mission-critical feature in a format that is obviously not related to this tracking number. When Verizon rewrites the header, that feature breaks, and you can make a fuss about it in the media or sue Verizon for breaking your webpage. (it sounds good on paper; this may not work in practice)