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

SHA-3/Keccak #11

Open
smarts opened this issue Oct 28, 2015 · 2 comments

Comments

Projects
None yet
6 participants
@smarts
Copy link

commented Oct 28, 2015

SHA-3 has been published. Why not require (or strongly suggest) support for it as well?

@fmarier

This comment has been minimized.

Copy link
Contributor

commented Oct 28, 2015

Why not require (or strongly suggest) support for it as well?

That's certainly something we should add to V2. Adding this requirement to V1 at this point would move us away from having our two shipping compliant implementations.

@dveditz dveditz added the SRI-next label Oct 28, 2015

@metromoxie metromoxie added this to the v2 milestone Oct 28, 2015

@fmarier fmarier removed the SRI-next label Oct 29, 2015

@hillbrad hillbrad modified the milestone: v2 Jan 22, 2016

@smarts

This comment has been minimized.

Copy link
Author

commented Mar 19, 2016

Why was this removed from the v2 milestone?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.