mozilla/sops
### [`v3.8.0`](https://togithub.com/getsops/sops/releases/tag/v3.8.0)
[Compare Source](https://togithub.com/mozilla/sops/compare/v3.7.3...v3.8.0)
##### Note from the Maintainers
We are extremely happy to introduce this new minor release of SOPS, now a [CNCF](https://cncf.io) Sandbox project under the stewardship of a new [group of maintainers](https://togithub.com/getsops/community/blob/main/MAINTAINERS.md).
This release involved significant effort in rewriting and enhancing key source implementations, and includes a number of bug fixes which people had been patiently waiting on for a long period of time. In addition, the release process has been built up from scratch, and now now provides enhanced assurance by publishing SBOMs (Software Bill of Materials), [SLSA3 provenance attestations](https://slsa.dev/spec/v0.1/provenance) and a Cosign signed checksums file as release artifacts.
For a comprehensive list of changes, please refer to [`CHANGELOG.rst`](https://togithub.com/getsops/sops/blob/v3.8.0/CHANGELOG.rst).
##### Important Information for SOPS SDK Users
With the project transitioning from the Mozilla Foundation to the CNCF, the Go module path has been updated to reflect this change in ownership. If you use `go.mozilla.org/sops/v3` as a library, going forward, import the Go Module using `github.com/getsops/sops/v3`. Apart from this small adjustment, the SDK's API remains fully backward compatible.
For a one-liner to quickly implement this change throughout your codebase, please refer to: [https://github.com/getsops/sops/issues/1246#issuecomment-1625526429](https://togithub.com/getsops/sops/issues/1246#issuecomment-1625526429)
##### 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:
```shell
##### Download the binary
curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.linux.amd64
##### Move the binary in to your PATH
mv sops-v3.8.0.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](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of this file, run the following commands:
```shell
##### Download the checksums file, certificate and signature
curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.sig
##### Verify the checksums file
cosign verify-blob sops-v3.8.0.checksums.txt \
--certificate sops-v3.8.0.checksums.pem \
--signature sops-v3.8.0.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:
```shell
##### Verify the binary using the checksums file
sha256sum -c sops-v3.8.0.checksums.txt --ignore-missing
```
##### Verify artifact provenance
The [SLSA provenance](https://slsa.dev/provenance/v0.2) of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an [in-toto](https://in-toto.io/) link metadata file named `sops-v3.8.0.intoto.jsonl`. To verify the provenance of an artifact, you can utilize the [`slsa-verifier`](https://togithub.com/slsa-framework/slsa-verifier#artifacts) tool:
```shell
##### Download the metadata file
curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.intoto.jsonl
##### Verify the provenance of the artifact
slsa-verifier verify-artifact \
--provenance-path sops-v3.8.0.intoto.jsonl \
--source-uri github.com/getsops/sops \
--source-tag v3.8.0
```
##### 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.8.0`
- `ghcr.io/getsops/sops:v3.8.0-alpine`
##### Quay.io
- `quay.io/getsops/sops:v3.8.0`
- `quay.io/getsops/sops:v3.8.0-alpine`
##### Verify container image signature
The container images are signed using [Cosign](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of an image, run the following command:
```shell
cosign verify ghcr.io/getsops/sops:v3.8.0 \
--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](https://slsa.dev/provenance/v0.2) attestations. For more information around the verification of this, please refer to the [`slsa-verifier` documentation](https://togithub.com/slsa-framework/slsa-verifier#containers).
##### 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](https://spdx.dev/) JSON file, formatted as `.spdx.sbom.json`.
##### What's Changed
- chore: update dependencies by [@hiddeco](https://togithub.com/hiddeco) in [https://github.com/getsops/sops/pull/1275](https://togithub.com/getsops/sops/pull/1275)
- build: pin actions to full length commit SHA and add CodeQL by [@hiddeco](https://togithub.com/hiddeco) in [https://github.com/getsops/sops/pull/1276](https://togithub.com/getsops/sops/pull/1276)
- Enable Dependabot for Docker, GitHub Actions and Go Mod by [@hiddeco](https://togithub.com/hiddeco) in [https://github.com/getsops/sops/pull/1277](https://togithub.com/getsops/sops/pull/1277)
- build(deps): Bump the go group with 2 updates by [@dependabot](https://togithub.com/dependabot) in [https://github.com/getsops/sops/pull/1280](https://togithub.com/getsops/sops/pull/1280)
- build(deps): Bump the ci group with 6 updates by [@dependabot](https://togithub.com/dependabot) in [https://github.com/getsops/sops/pull/1279](https://togithub.com/getsops/sops/pull/1279)
- release: generate versioned `.intoto.jsonl` by [@hiddeco](https://togithub.com/hiddeco) in [https://github.com/getsops/sops/pull/1278](https://togithub.com/getsops/sops/pull/1278)
- pgp: remove `DisableAgent` option by [@hiddeco](https://togithub.com/hiddeco) in [https://github.com/getsops/sops/pull/1282](https://togithub.com/getsops/sops/pull/1282)
- keyservices: address logging regression by [@hiddeco](https://togithub.com/hiddeco) in [https://github.com/getsops/sops/pull/1281](https://togithub.com/getsops/sops/pull/1281)
- chore: update dependencies by [@hiddeco](https://togithub.com/hiddeco) in [https://github.com/getsops/sops/pull/1283](https://togithub.com/getsops/sops/pull/1283)
- Prepare v3.8.0 by [@hiddeco](https://togithub.com/hiddeco) in [https://github.com/getsops/sops/pull/1284](https://togithub.com/getsops/sops/pull/1284)
**Full Changelog**: https://github.com/getsops/sops/compare/v3.8.0-rc.1...v3.8.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
v3.7.3->v3.8.0Release Notes
mozilla/sops
### [`v3.8.0`](https://togithub.com/getsops/sops/releases/tag/v3.8.0) [Compare Source](https://togithub.com/mozilla/sops/compare/v3.7.3...v3.8.0) ##### Note from the Maintainers We are extremely happy to introduce this new minor release of SOPS, now a [CNCF](https://cncf.io) Sandbox project under the stewardship of a new [group of maintainers](https://togithub.com/getsops/community/blob/main/MAINTAINERS.md). This release involved significant effort in rewriting and enhancing key source implementations, and includes a number of bug fixes which people had been patiently waiting on for a long period of time. In addition, the release process has been built up from scratch, and now now provides enhanced assurance by publishing SBOMs (Software Bill of Materials), [SLSA3 provenance attestations](https://slsa.dev/spec/v0.1/provenance) and a Cosign signed checksums file as release artifacts. For a comprehensive list of changes, please refer to [`CHANGELOG.rst`](https://togithub.com/getsops/sops/blob/v3.8.0/CHANGELOG.rst). ##### Important Information for SOPS SDK Users With the project transitioning from the Mozilla Foundation to the CNCF, the Go module path has been updated to reflect this change in ownership. If you use `go.mozilla.org/sops/v3` as a library, going forward, import the Go Module using `github.com/getsops/sops/v3`. Apart from this small adjustment, the SDK's API remains fully backward compatible. For a one-liner to quickly implement this change throughout your codebase, please refer to: [https://github.com/getsops/sops/issues/1246#issuecomment-1625526429](https://togithub.com/getsops/sops/issues/1246#issuecomment-1625526429) ##### 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: ```shell ##### Download the binary curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.linux.amd64 ##### Move the binary in to your PATH mv sops-v3.8.0.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](https://docs.sigstore.dev/cosign/overview/) with GitHub OIDC. To validate the signature of this file, run the following commands: ```shell ##### Download the checksums file, certificate and signature curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.txt curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.pem curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.sig ##### Verify the checksums file cosign verify-blob sops-v3.8.0.checksums.txt \ --certificate sops-v3.8.0.checksums.pem \ --signature sops-v3.8.0.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: ```shell ##### Verify the binary using the checksums file sha256sum -c sops-v3.8.0.checksums.txt --ignore-missing ``` ##### Verify artifact provenance The [SLSA provenance](https://slsa.dev/provenance/v0.2) of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through an [in-toto](https://in-toto.io/) link metadata file named `sops-v3.8.0.intoto.jsonl`. To verify the provenance of an artifact, you can utilize the [`slsa-verifier`](https://togithub.com/slsa-framework/slsa-verifier#artifacts) tool: ```shell ##### Download the metadata file curl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.intoto.jsonl ##### Verify the provenance of the artifact slsa-verifier verify-artifactConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
â™» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.