Repository navigation
fix: verify the Vector tarball checksum before installing it - #105
Merged
Merged
Conversation
|
Released in v1.0.45 -- https://github.com/hyperi-io/dfe-transform-vector/releases/tag/v1.0.45 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The Vector install layer downloaded the release tarball over curl with no integrity check, so a tampered or corrupted download would go straight into the image. The build now verifies the tarball's SHA256 against digests pinned per architecture, sourced from Vector's published SHA256SUMS and cross-checked against the identically-named GitHub release asset, and fails the build on a mismatch.
The Vector version stays pinned at 0.58.0, which is still the newest non-prerelease release (2026-08-26).