apk/signature: remove support for creating new SHA1 signatures #1496
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Remove support for creating new SHA1 signatures.
Verification of SHA1 signatures remains until after Alpine migrates to
SHA256.
Using current melange, adding replace in go.mod to use this apko, and use the bypass environment variable to worse SHA1 signatures results in this runtime error:
And similarly during package build
Thus any users of this public API will too get a nice error in case they are still trying to use SHA1 signatures.