News for hackers. Stuff that matters.
Re:Do not let your CDN betray you: use subresource integrity... by problems on Wednesday April 05, 2017 @11:33AM (#14042843)
The potential problem I see with this is that it could be abused for a "have you loaded this resource" privacy leak. Simply pick a unique script on a website, if my server doesn't get a hit then I know you went there before.
Re:Do not let your CDN betray you: use subresource integrity... by zrm on Wednesday April 05, 2017 @01:35PM (#14043884)
Possible solution is to have a content hash proxy trusted by the user but shared between multiple users. Then the site can only get the data at the proxy-level rather than the user-level, and not even that if the proxy is large enough to justify crawling the web to pre-cache everything, or is behind a larger cache that does.
Re:Do not let your CDN betray you: use subresource integrity... by nothrabannosir on Wednesday April 05, 2017 @02:07PM (#14044190)
That's not a solution but a work-around. The original privacy issue stands. browsers can't cache hashed content by default. :/
Re:Do not let your CDN betray you: use subresource integrity... by zrm on Wednesday April 05, 2017 @02:45PM (#14044493)
The browser would know if it had a content hash proxy configured and then could use it for all content hashed data. The issue becomes getting people to use one, but partial uptake is better than nothing. You could at least get most corporate and education environments with some equivalent to WPAD[1], and maybe even some consumer-level ISPs the same way if they want to reduce the traffic over their network.

[1] https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Proto...

Re:Do not let your CDN betray you: use subresource integrity... by 3pt14159 on Wednesday April 05, 2017 @02:30PM (#14044388)
We already have that though. Images and HSTS headers.
Re:Do not let your CDN betray you: use subresource integrity... by problems on Wednesday April 05, 2017 @04:40PM (#14045420)
Those are abusable by first party only though aren't they? This abuse isn't just limited to fingerprinting from 1st party sources, but to 3rd party history detection essentially.
Re:Do not let your CDN betray you: use subresource integrity... by 3pt14159 on Thursday April 06, 2017 @08:11AM (#14049822)
Ah, thanks for clarifying. You are 100% right, I misunderstood the use case.
Re:Do not let your CDN betray you: use subresource integrity... by cryptarch on Wednesday April 05, 2017 @12:34PM (#14043342)
Save the load time and simulate it?
Re:Do not let your CDN betray you: use subresource integrity... by cryptarch on Thursday April 06, 2017 @04:44AM (#14048918)
Why do you think this would be a bad idea?
Re:Do not let your CDN betray you: use subresource integrity... by homakov on Wednesday April 05, 2017 @05:38PM (#14045875)
Who cares someone went to X website? Even https is not protecting from that.
Re:Do not let your CDN betray you: use subresource integrity... by staticassertion on Wednesday April 05, 2017 @05:54PM (#14045996)
If I visit website A it should not know that I also visited website B. HTTP or HTTPS is irrelevant - they are totally separate connections and this does not assume anyone is in the middle.

Of course, there are attacks that already work using cache timing, but that isn't a good thing.

Re:Do not let your CDN betray you: use subresource integrity... by homakov on Wednesday April 05, 2017 @06:49PM (#14046396)
I know a handful of attack that work, and a few more vectors that won't be fixed as well. So why bother, exactly? It's neither a big concern nor fixable in current web design.