aa at google.com
Mon Jun 15 19:59:16 PDT 2009
2009/6/15 Ian Fette (イアンフェッティ) <ifette at google.com>:
> In the event of a collision there would be huge issues - imagine running
> someone else's script in your application. Basically XSS - someone could
> take over your app, steal passwords, do bank transactions on your behalf,
> Collisions are made easier in plain text than in certs given that your input
> is not constrained.
I think the idea was for browser vendors to select and include these
libraries in the browser. So there isn't an obvious (to me) way for an
attacker to use hash collisions to create an XSS.
That said, I don't think content hashes are the right identifier.
Using a sha-1 of a specific jquery version would prevent anyone from
ever fixing critical bugs in it. There's be all this legacy content
out there referring to an outdated version.
More information about the whatwg