News for hackers. Stuff that matters.
Re:How Verizon and Turn Defeat Browser Privacy Protections by noonespecial on Wednesday January 14, 2015 @11:06PM (#8890835)
How about:

Because your mobile device really belongs to the carrier and not to you, whenever you browse the web with it, they know who you are no matter what. They are now refusing to keep that information secret even if you want them to, instead selling it to advertisers without your consent (even despite your obvious non-consent).

They do this by sabotaging your mobile browser so it can't really delete certain cookies. When you try, they put them right back the next time you use the browser. They also have a way (called a UIDH header) to tell other sites that its you (so they can track your visits) even if you don't have a cookie in your browser.

Re:How Verizon and Turn Defeat Browser Privacy Protections by nl on Thursday January 15, 2015 @07:01AM (#8892055)
That's a terrible synopsis. It doesn't have anything to do with the device at all, and that's the whole point!

No matter what you do to attempt to avoid this you can't if you use the Verizon communication layer. The only way around it is to use counter measures to avoid the Verizon software seeing your connection (ie, a VPN).

Re:How Verizon and Turn Defeat Browser Privacy Protections by im2w1l on Thursday January 15, 2015 @09:22AM (#8892569)
"Whenever you request a web page, Verizon stamps it with a beastly mark, a name-number to give you offers to buy goods."
Re:How Verizon and Turn Defeat Browser Privacy Protections by guelo on Thursday January 15, 2015 @01:49AM (#8891235)
It doesn't have anything to do with who owns the device.
Re:How Verizon and Turn Defeat Browser Privacy Protections by noonespecial on Thursday January 15, 2015 @05:04AM (#8891708)
Sure it does. If my verizon iphone wasn't 3 months into a locked two year contract I'd just put in a different sim and forget the whole thing.
Re:How Verizon and Turn Defeat Browser Privacy Protections by Shivetya on Thursday January 15, 2015 @10:21AM (#8892892)
but cannot phones simply be tracked by their own id regardless of carrier. Say you swap from Verizon, if you hit one of their towers they could theoretically use that information even if your not a direct customer.

We know the FBI is reading the traffic so I am wondering why someone is surprised a company does it. Its not right for either party

Re:How Verizon and Turn Defeat Browser Privacy Protections by gcb0 on Thursday January 15, 2015 @12:16PM (#8893761)
they could also follow you non stop on the street and enter every store you go and take note of all your purchases by looking over your shoulder. and i don't think much of it is illegal unless you can prove it distress you but I'm not a layer (I'm a productive member of society :)
Re:How Verizon and Turn Defeat Browser Privacy Protections by nhstanley on Thursday January 15, 2015 @05:40AM (#8891812)
Naive follow up question: Can doing something like routing through a VPN help with this? I assume not, since a forced cookie on your browser will make you always identifiable to the person on the other end, correct?
Re:How Verizon and Turn Defeat Browser Privacy Protections by jleight on Thursday January 15, 2015 @07:26AM (#8892150)
Using a VPN would encrypt your traffic, preventing Verizon from injecting a UIDH header. You could then clear your cookies and websites would not be able to re-add them via the UIDH header since it isn't being sent.

This isn't to say that the websites can't identify you via some other means, just that they no longer have the guaranteed UIDH header to identify you.

Re:How Verizon and Turn Defeat Browser Privacy Protections by 01Michael10 on Thursday January 15, 2015 @09:56AM (#8892729)
Another question? Would FF+Adblock Plus+Ghostery stop this UIDH header injection without a VPN?
Re:How Verizon and Turn Defeat Browser Privacy Protections by MichaelGG on Thursday January 15, 2015 @10:59AM (#8893175)
No the header injection happens after the request leaves your browser. However, adblock can prevent the request going to Turn and other ad sites in the first place. But then the website owner (eg Facebook) can work with the ad network to pass your info to them on the server side, although I'm not sure how widespread this is.
Re:How Verizon and Turn Defeat Browser Privacy Protections by bashinator on Thursday January 15, 2015 @05:07PM (#8895727)
How about if I wanted to actively subvert the header? Would there be a way to beat Verizon's network to the punch by injecting the same header myself and populating it with garbage data?
Re:How Verizon and Turn Defeat Browser Privacy Protections by MichaelGG on Thursday January 15, 2015 @11:03PM (#8897205)
No, they simply overwrite it.

The only way around that would be to take advantage of bugs in their parser. HTTP is a moronic spec, and it allows inane things. For instance, these are valid HTTP headers:

  X-LineWrap: Hi my name is
       Header Boy
The value of X-LineWrap should be "Hi my name is Header Boy". Edit: Actually I'm not sure if the space before the comment counts or not. Terrible text protocol formats FTW.

  X-Comment: This is the value (but this is a comment!)
The value of X-Comment should be "This is the value".

  X-MoreFun: I don't recall (offhand) how
    this header value should
    (really, the spec is a mess)
    be interpreted.
The value of X-MoreFun should be (I think): "I don't recall how this header value should be interpreted.".

So, you might get lucky if they have a non-compliant parser and the target site has a compliant parser. In that case:

   X-UIDH: garbage1
      garbage2
Might get turned into:

   X-UIDH: verizontrackingvalue
      garbage2
In which case, a compliant HTTP parser would read the value as "verizontrackingvalue garbage2", which might be enough to mess up their tracking.

Also, HTTP has special handling of headers that are "comma separated lists". This should only apply to special-cased built-in headers. But you could try sending multiple X-UIDH headers, with commas in the values, to trick an overly ambitious parser. Maybe.

Anyways, this all depends on bugs in HTTP parsers, which probably exist. (Can you tell I despise the HTTP format?) But if exploited enough to matter, they'd simply patch them.