Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sops 3.9.1 #192798

Merged
merged 2 commits into from
Oct 4, 2024
Merged

sops 3.9.1 #192798

merged 2 commits into from
Oct 4, 2024

Conversation

BrewTestBot
Copy link
Member

Created by brew bump

Created with brew bump-formula-pr.

release notes 
## Installation

To install sops, download one of the pre-built binaries provided for your platform from the artifacts attached to this release.


For instance, if you are using Linux on an AMD64 architecture:


# Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.1.linux.amd64 /usr/local/bin/sops

# Make the binary executable
chmod +x /usr/local/bin/sops


Verify checksums file signature


The checksums file provided within the artifacts attached to this release is signed using Cosign with GitHub OIDC. To validate the signature of this file, run the following commands:


# Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.1.checksums.txt \
  --certificate sops-v3.9.1.checksums.pem \
  --signature sops-v3.9.1.checksums.sig \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com


Verify binary integrity


To verify the integrity of the downloaded binary, you can utilize the checksums file after having validated its signature:


# Verify the binary using the checksums file
sha256sum -c sops-v3.9.1.checksums.txt --ignore-missing


Verify artifact provenance


The SLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an in-toto link metadata file named sops-v3.9.1.intoto.jsonl. To verify the provenance of an artifact, you can utilize the slsa-verifier tool:


# Download the metadata file
curl -LO  https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.9.1.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.9.1


Container Images


The sops binaries are also available as container images, based on Debian (slim) and Alpine Linux. The Debian-based container images include any dependencies which may be required to make use of certain key services, such as GnuPG, AWS KMS, Azure Key Vault, and Google Cloud KMS. The Alpine-based container images are smaller in size, but do not include these dependencies.


These container images are available for the following architectures: linux/amd64 and linux/arm64.


GitHub Container Registry


    

  • ghcr.io/getsops/sops:v3.9.1
    • 

  • ghcr.io/getsops/sops:v3.9.1-alpine
    • 



Quay.io


    

  • quay.io/getsops/sops:v3.9.1
    • 

  • quay.io/getsops/sops:v3.9.1-alpine
    • 



Verify container image signature


The container images are signed using Cosign with GitHub OIDC. To validate the signature of an image, run the following command:


cosign verify ghcr.io/getsops/sops:v3.9.1 \
  --certificate-identity-regexp=https://github.com/getsops \
  --certificate-oidc-issuer=https://token.actions.githubusercontent.com \
  -o text


Verify container image provenance


The container images include SLSA provenance attestations. For more information around the verification of this, please refer to the slsa-verifier documentation.


Software Bill of Materials


The Software Bill of Materials (SBOM) for each binary is accessible within the artifacts enclosed with this release. It is presented as an SPDX JSON file, formatted as <binary>.spdx.sbom.json.


What's Changed



New Contributors



Full Changelog: getsops/sops@v3.9.0...v3.9.1

@github-actions github-actions bot added go Go use is a significant feature of the PR or issue bump-formula-pr PR was created using `brew bump-formula-pr` labels Oct 4, 2024
@github-actions GitHub Actions
Copy link
Contributor

github-actions bot commented Oct 4, 2024

🤖 An automated task has requested bottles to be published to this PR.

@github-actions github-actions bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Oct 4, 2024
@BrewTestBot BrewTestBot added this pull request to the merge queue Oct 4, 2024
Merged via the queue into master with commit 97ff9f4 Oct 4, 2024
15 checks passed
@BrewTestBot BrewTestBot deleted the bump-sops-3.9.1 branch October 4, 2024 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@github-actions github-actions[bot] github-actions[bot] approved these changes

@carlocab carlocab carlocab approved these changes

Assignees
No one assigned
Labels
bump-formula-pr PR was created using `brew bump-formula-pr` CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. go Go use is a significant feature of the PR or issue
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@BrewTestBot @carlocab