-
Notifications
You must be signed in to change notification settings - Fork 18
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
Support SHA512 for buildpack dependencies #221
Comments
There should already be support for I am not sure that we do support |
Hey @ryanmoran thanks for replying. Firstly, I assumed sha512 is not supported (and md5 is) after going through these unit tests: https://github.com/paketo-buildpacks/packit/blob/v2/cargo/checksum_test.go Secondly, my issue is that when using Cheksum syntax 'sha512:...' (same way you shared) my logs say:
so SHA512 doesn't seem to be used for caching (nor for validating if the collected package is safe). |
I think the issue is that the buildpack in question isn't using
So I think this issue should be moved to the |
thanks @robdimsdale you are probably right, nice catch! |
@dmikusa do you have permissions to transfer this issue to https://github.com/paketo-buildpacks/libpak ? |
Transferred. I haven't looked at what it will take to implement this for libpak. My guess is that we'll do this as part of v2 (hopefully libcnb v2 is to be released soon, so then we can get working on libpack v2). That said, if someone wants to look into this and it can be done in a non-breaking way, we could add it to v1 as well. |
Describe the Enhancement
Make it possible to define checksum = "sha512:..." in the buildpack.toml metadata.dependencies (instead of just {sha256,md5})
Possible Solution
Motivation
Some dependency providers (in our case Apache Spark collected from archive FTP) publish sha512 only, in such case it's not a trival task to use it in buidlpacks.
The text was updated successfully, but these errors were encountered: