Skip to content

Conversation

duthils
Copy link
Contributor

@duthils duthils commented Oct 7, 2024

This PR is open as an alternative to the PR #1588 to fix the issue #1539.

Changes in this PR imply the following downsides:

  • any automated integrity checks for sops releases that are based on checksums.txt will stop working in the next release
  • there is no documentation to verify integrity while being offline
    • it is possible, but it must be documented if deemed important enough
    • For the record, a command like this can be used for offline checksum verification:
    jq -r .payload sops-v*.intoto.jsonl | base64 -d | jq -r '.subject[] | .digest.sha256 + " " + .name' | sha256sum -c --ignore-missing

Why:

* SLSA verification implies integrity verification, making the checksums file
  redundant
* The checksums file is lacking entries for package files

Signed-off-by: Sebastien Duthil <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant