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

proposition: generate MD5 Checksum for each release #6

Open
alexfoias opened this issue Jul 8, 2020 · 2 comments
Open

proposition: generate MD5 Checksum for each release #6

alexfoias opened this issue Jul 8, 2020 · 2 comments

Comments

@alexfoias
Copy link
Contributor

Maybe it's a good idea to have the md5 hash of the source file with the release in order to check if the users have the complete zip file. Not sure if GH already offers this feature.

@kousu
Copy link
Contributor

kousu commented Aug 17, 2020

This is a good idea! @zougloub was thinking about this in distriploy.

git-annex offers this feature by making every commit ID the hash of its contents, and the contents of the images themselves named after the hash of their contents. They use SHA256 though, which is much stronger and safer than md5.

@jcohenadad jcohenadad transferred this issue from spine-generic/data-single-subject_DO-NOT-USE Sep 11, 2020
@kousu
Copy link
Contributor

kousu commented Nov 10, 2020

We've migrated to git-annex now, so this should be handled better that way. git-annex uses sha256 hashes which are stronger, too.

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

2 participants