Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only recommending collision resistance #107

Open
martinthomson opened this issue Sep 14, 2021 · 0 comments
Open

Only recommending collision resistance #107

martinthomson opened this issue Sep 14, 2021 · 0 comments

Comments

@martinthomson
Copy link
Member

The spec only uses "SHOULD" to recommend collision resistance:

User agents [...] SHOULD restrict supported hashing functions to those known to be collision-resistant.

The security guarantees that SRI provides do not hold if the hash function is not collision (and second preimage) resistant. The specification can use "MUST" when it comes to properties that are essential to its function.

The same only partly applies to the SHOULD on the other arm of this sentence. SHA-1 and MD5 do not have (published) second preimage attacks, which are the ones that really matter in terms of real attacks. I would be supportive of a "MUST" there as well though, if only to preempt advances in cryptanalysis. Maybe if no one implements these, that wouldn't be a big deal anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant