Update Go dependencies in hook-bootkit; add resilience to kernel download and verify: #281
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.
Description
The hook-bootkit dependency updates resolve some security issues.
Use backup locations for kernel downloads. It happened that today the latest point releases for the 5.x and 6.x kernels were in the https://www.kernel.org/releases.json but not in corresponding sha256sum.asc file, https://www.kernel.org/pub/linux/kernel/v6.x/sha256sums.asc for example. Interestingly enough, the kernels were in https://cdn.kernel.org/pub/linux/kernel/v6.x/sha256sums.asc. The difference being https://www.kernel.org vs https://cdn.kernel.org. This new script will try against www.kernel.org and fall back to cdn.kernel.org.
Why is this needed
Fixes: #
How Has This Been Tested?
How are existing users impacted? What migration steps/scripts do we need?
Checklist:
I have: