-
Notifications
You must be signed in to change notification settings - Fork 173
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
Do not use sha1 #1148
Comments
@Araq What should be done about this? |
Use a better checksum algorithm? |
Alright, I'll work on that. I'm just scared that this might break stuff downstream. Hopefully, it won't. :P |
The biggest problem is migrating pre-existing installed libraries. We'll have to go through everything in the packages directory, scan everything, compute new SHA-2 hashes, move these files to new directories with the updated hash. Or, alternatively, we can let SHA-1 exist as legacy stuff, and add a new |
SHA1 is broken. Many things are broken in Nimble but this is easy to fix.
The text was updated successfully, but these errors were encountered: