News for hackers. Stuff that matters.
Re:Chrome deploys deep-linking in latest build despite priva... by maxrmk on Friday February 21, 2020 @03:30PM (#22386413)
Yeah -- it's frustrating that the privacy concerns brought up in the article are just blantantly wrong. Especially because there a legitimately interesting issues in the security write-up [1].

On the other hand, I suspect they probably won't get the mitigations for those real issues right the first time. It's a complicated system they're building, and I think someone will find a clever way to break it.

[1] https://docs.google.com/document/u/0/d/1YHcl1-vE_ZnZ0kL2alme...

Re:Chrome deploys deep-linking in latest build despite priva... by femto113 on Friday February 21, 2020 @03:44PM (#22386515)
This sentence from the doc referenced sums it up well I think:

> A naive implementation of this feature may allow an attacker to determine the existence of textual content across an origin boundary.

Security & privacy implications of that seem obvious, e.g. extracting an account number (or other sensitive information) from a page by searching for successive prefixes.

Re:Chrome deploys deep-linking in latest build despite priva... by maxrmk on Friday February 21, 2020 @04:01PM (#22386691)
Just to clarify, I do think there are real privacy concerns with a naive implement of this feature. Allowing sites to search across origin boundaries would be a huge issue!

I just don't think that the DNS query issue mentioned in the article is the thing to be worried about. It's just so much less severe than the fact that DNS isn't encrypted, and requires essentially the same fix.