Example: User has jquery cached from googles CDN, jquery will not be loaded from microsofts cdn because it has the same hash.
http://www.chromestatus.com/features/6183089948590080 http://status.modern.ie/subresourceintegrity
> 3.2.1 Agility: the user agent will choose the strongest hash function in the list
Aside from the fact this contradicts the next section (Priority), it also would discourage browser vendors from adding better (slower) hashing functions as then they would be "forced" to utilise them.
Instead the standard should be: The "the fastest hash function which the browser finds secure." So if SHA-256 and SHA-512 were available, it would use SHA-256 until it was found insecure, then the browser would use SHA-512.
> Validation using unsupported hash functions always fails (see the “Does resource match metadataList” algorithm below). Authors are therefore encouraged to use strong hash functions, and to begin migrating to stronger hash functions as they become available.
No. Just no. If Chrome was the first to market with e.g. SHA-9999, I'd be unable to utilise that until literally every single browser on the market supported it (as it was fail by default).
Imagine if this standard existed in the IE6 days, today if you tried to use SHA-512 (which, let's assume, IE6 didn't support) the resources would fail to load every time (and you'd wind up having half a dozen different hashes just to hit something that was supported).
It should just ignore unknown hash functions, not fail. If the integrity attribute only had one hash function and it was unsupported then the entire attribute should be discarded.
Fail by default isn't even the HTML way. Ignore by default is.
Your proposal would make the hash attribute advisory. If I put a hash attribute on there, should I be able to count on it, and know that browsers won't load unless they can verify it? Or is it just advisory, and browsers may choose to ignore it, and I can't actually count on browsers only loading if hash matches?
Of course, I guess the fact that older browsers will always exist that ignore it (and that all browsers are essentially untrusted software, as far as the developer is concerned) may point to "you'd best consider it advisory only" anyway, I suppose.
https://codereview.chromium.org/566083003/
The tests show how simple the code is:
https://codereview.chromium.org/566083003/patch/120001/13000...
Just don't trust so many third parties with your site's security: Host jQuery (and other things) yourself.
Even if we ignore the hash suggestion, you don't want to have some dev on the other side of the planet suddenly update one of your libraries on your live website.
That should never be a thing in the first place, so it won't be a problem.
No, they will release a new version with a new URL.
But I don't think it will ever get much traction. Believe it or not, it's too far beyond the organizational and technical capacities of the people behind too many sites. The benefit, aside from slightly improved caching, will be minimal.
And if you're careful and meticulous you aren't doing braindead things like hotlinking javascript in the first place.
We are responsible for quite a lot of copy and paste script includes these days and could potentially push people in this direction.
If anyone is serious about investigating hash'ed includes shoot me an email with your thoughts, my email can be found on my HN profile.
It's an interesting problem nevertheless, and could be extended to any link or src attributes in tags.
In case the hash and the file dont match,the browser wouldnt load that file.
But there's an easy way to fix it. Browsers should support a hash attribute for <script> tags, so instead of
sites could instead say This would also significantly reduce the risks from use of http instead of https, and from weaknesses in https itself.