[1.1] bump libseccomp to v2.5.4, check tarball sha #3481
Merged
Conversation
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
kolyshkin
added
backport/1.1-pr
This comment was marked as outdated.
This comment was marked as outdated.
kolyshkin
changed the title
kolyshkin
changed the title
kolyshkin
force-pushed
the
1.1-bump-libseccomp
branch
from
eded0c5 to
f7a29b4
Compare
Merged
kolyshkin
force-pushed
the
1.1-bump-libseccomp
branch
from
f7a29b4 to
1011bfd
Compare
AkihiroSuda
approved these changes
May 27, 2022
Release notes: https://github.com/seccomp/libseccomp/releases/tag/v2.5.4 This affects the released static binaries (as they are statically linked against libseccomp). Signed-off-by: Kir Kolyshkin <[email protected]> (cherry picked from commit f7b07fd) Signed-off-by: Kir Kolyshkin <[email protected]>
Add checking of downloaded tarball checksum.
In case it doesn't match the hardcoded value, the error is like this:
libseccomp-2.5.4.tar.gz: FAILED
sha256sum: WARNING: 1 computed checksum did NOT match
In case the checksum for a particular version is not specified in the
script, the error will look like this:
./script/seccomp.sh: line 29: SECCOMP_SHA256[${ver}]: unbound variable
In case the the hardcoded value in the file is of wrong format/length,
we'll get:
sha256sum: 'standard input': no properly formatted SHA256 checksum lines found
In any of these cases, the script aborts (due to set -e).
Signed-off-by: Kir Kolyshkin <[email protected]>
(cherry picked from commit 95f1e2e18872de54a17d64b2d808255463ee3d93)
Signed-off-by: Kir Kolyshkin <[email protected]>
cyphar
force-pushed
the
1.1-bump-libseccomp
branch
from
1011bfd to
8242c05
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Release notes: https://github.com/seccomp/libseccomp/releases/tag/v2.5.4
This affects the released static binaries (as they are statically linked
against libseccomp).
This is a backport of #3480 and #3482.