v3.10.2

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.10.2/sops-v3.10.2.linux.amd64

# Move the binary in to your PATH
mv sops-v3.10.2.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.10.2/sops-v3.10.2.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.10.2/sops-v3.10.2.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.10.2/sops-v3.10.2.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.10.2.checksums.txt \
  --certificate sops-v3.10.2.checksums.pem \
  --signature sops-v3.10.2.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.10.2.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.10.2.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.10.2/sops-v3.10.2.intoto.jsonl

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

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.10.2
• ghcr.io/getsops/sops:v3.10.2-alpine

Quay.io

• quay.io/getsops/sops:v3.10.2
• quay.io/getsops/sops:v3.10.2-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.10.2 \
  --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

• build(deps): Bump the go group with 13 updates by @dependabot in #1834
• Use latest 1.24 Go version for release build by @hiddeco in #1836
• Remove reserved keyword check from YAML store's LoadPlainFile() by @felixfontein in #1829
• build(deps): Bump the go group with 9 updates by @dependabot in #1839
• build(deps): Bump github/codeql-action from 3.28.13 to 3.28.15 in the ci group by @dependabot in #1840
• Release 3.10.2 release by @felixfontein in #1841

Full Changelog: v3.10.1...v3.10.2

v3.10.1

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.10.1/sops-v3.10.1.linux.amd64

# Move the binary in to your PATH
mv sops-v3.10.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.10.1/sops-v3.10.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.10.1/sops-v3.10.1.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.10.1/sops-v3.10.1.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.10.1.checksums.txt \
  --certificate sops-v3.10.1.checksums.pem \
  --signature sops-v3.10.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.10.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.10.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.10.1/sops-v3.10.1.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.10.1.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.10.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.10.1
• ghcr.io/getsops/sops:v3.10.1-alpine

Quay.io

• quay.io/getsops/sops:v3.10.1
• quay.io/getsops/sops:v3.10.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.10.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

• build(deps): Bump the ci group with 2 updates by @dependabot in #1826
• Release 3.10.1 by @felixfontein in #1827

Full Changelog: v3.10.0...v3.10.1

v3.10.0

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.10.0/sops-v3.10.0.linux.amd64

# Move the binary in to your PATH
mv sops-v3.10.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 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.10.0/sops-v3.10.0.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.10.0/sops-v3.10.0.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.10.0/sops-v3.10.0.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.10.0.checksums.txt \
  --certificate sops-v3.10.0.checksums.pem \
  --signature sops-v3.10.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:

# Verify the binary using the checksums file
sha256sum -c sops-v3.10.0.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.10.0.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.10.0/sops-v3.10.0.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.10.0.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.10.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.10.0
• ghcr.io/getsops/sops:v3.10.0-alpine

Quay.io

• quay.io/getsops/sops:v3.10.0
• quay.io/getsops/sops:v3.10.0-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.10.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 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

• build(deps): Bump alpine from 3.18 to 3.21 in /.release in the docker group across 1 directory by @dependabot in #1700
• Convert changelog to MarkDown by @felixfontein in #1741
• build(deps): Bump the go group with 7 updates by @dependabot in #1743
• build(deps): Bump the go group with 9 updates by @dependabot in #1745
• build(deps): Bump the rust group in /functional-tests with 2 updates by @dependabot in #1744
• build(deps): Bump github/codeql-action from 3.28.5 to 3.28.8 in the ci group by @dependabot in #1746
• build(deps): Bump the go group with 12 updates by @dependabot in #1751
• build(deps): Bump the ci group with 4 updates by @dependabot in #1750
• Add --input-type option for filestatus subcommand by @felixfontein in #1601
• Use SOPS_EDITOR before EDITOR by @felixfontein in #1611
• Allow users to disable version check via environment variable by @nicklasfrahm in #1684
• add duplicate section support to ini store by @reindlt in #1452
• stores: test for duplicate keys, reserve keyword (yaml only now) by @holiman in #1203
• Add same process option for exec-env by @ricmatsui in #880
• outputs: add trailing newline at the end of JSON files by @duthils in #1476
• set subcommand: add --idempotent flag that will not write the file if no change happened by @felixfontein in #1754
• Encrypt and decrypt time.Time objects by @felixfontein in #1759
• build(deps): Bump the go group with 8 updates by @dependabot in #1763
• build(deps): Bump tempfile from 3.16.0 to 3.17.0 in /functional-tests in the rust group by @dependabot in #1762
• build(deps): Bump goreleaser/goreleaser-action from 6.1.0 to 6.2.1 in the ci group by @dependabot in #1761
• fix(docs): typo in README.rst by @Paredev in #1765
• Add SSH support for age by @haoqixu in #1692
• make sure that tests do not pick keys.txt from user's HOME dir by @tomaszduda23 in #1766
• support for age identity with passphrase by @tomaszduda23 in #1400
• build(deps): Bump the rust group in /functional-tests with 4 updates by @dependabot in #1768
• build(deps): Bump the go group with 12 updates by @dependabot in #1769
• build(deps): Bump the ci group with 4 updates by @dependabot in #1770
• build(deps): Bump github.com/go-jose/go-jose/v4 from 4.0.4 to 4.0.5 by @dependabot in #1773
• feat: add age plugin support by @brianmcgee in #1641
• Check GnuPG decryption result for non-empty size by @felixfontein in #1776
• vendored age code: consolidate passphrase reading functionality by @felixfontein in #1775
• Allow to encrypt and decrypt from stdin by @felixfontein in #1690
• build(deps): Bump the go group with 11 updates by @dependabot in #1784
• build(deps): Bump the ci group with 5 updates by @dependabot in #1782
• build(deps): Bump serde_json from 1.0.139 to 1.0.140 in /functional-tests in the rust group; bump Rust to 1.85.0 by @dependabot in #1783
• build(deps): Bump the go group with 13 updates by @dependabot in #1797
• build(deps): Bump the rust group in /functional-tests with 3 updates by @dependabot in #1796
• build(deps): Bump github/codeql-action from 3.28.10 to 3.28.11 in the ci group by @dependabot in #1795
• build(deps): Bump the go group with 6 updates by @dependabot in #1802
• build(deps): Bump tempfile from 3.18.0 to 3.19.0 in /functional-tests in the rust group by @dependabot in #1800
• build(deps): Bump docker/login-action from 3.3.0 to 3.4.0 in the ci group by @dependabot in #1801
• build(deps): Bump github.com/golang-jwt/jwt/v5 from 5.2.1 to 5.2.2 by @dependabot in #1806
• goreleaser: add windows arm64 by @duthils in #1791
• Add a way to set sops config location via envvar by @sledzikowy in #1701
• build(deps): Bump the go group with 3 updates by @dependabot in #1809
• build(deps): Bump the ci group with 5 updates by @dependabot in #1808
• build(deps): Bump tempfile from 3.19.0 to 3.19.1 in /functional-tests in the rust group by @dependabot in #1807
• Support --config option in publish subcommand by @felixfontein in #1779
• Fix caching of Metadata.DataKey by @felixfontein in #1781
• Lint by @felixfontein in #1780
• updatekeys subcommand: rename...

v3.9.4

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.4/sops-v3.9.4.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.4.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.4/sops-v3.9.4.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.4.checksums.txt \
  --certificate sops-v3.9.4.checksums.pem \
  --signature sops-v3.9.4.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.4.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.4.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.4/sops-v3.9.4.intoto.jsonl

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

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.4
• ghcr.io/getsops/sops:v3.9.4-alpine

Quay.io

• quay.io/getsops/sops:v3.9.4
• quay.io/getsops/sops:v3.9.4-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.4 \
  --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

• build(deps): Bump the go group with 5 updates by @dependabot in #1727
• build(deps): Bump tempfile from 3.14.0 to 3.15.0 in /functional-tests in the rust group by @dependabot in #1728
• build(deps): Bump the go group with 16 updates by @dependabot in #1732
• build(deps): Bump the ci group with 3 updates by @dependabot in #1730
• build(deps): Bump serde_json from 1.0.134 to 1.0.135 in /functional-tests in the rust group by @dependabot in #1731
• build(deps): Bump the go group with 12 updates by @dependabot in #1734
• build(deps): Bump serde_json from 1.0.135 to 1.0.137 in /functional-tests in the rust group by @dependabot in #1735
• Fix ToString for AWS KMS to include role, context, and profile by @felixfontein in #1733
• build(deps): Bump the ci group with 3 updates by @dependabot in #1738
• build(deps): Bump the go group with 6 updates by @dependabot in #1739
• Release 3.9.4 by @felixfontein in #1740

Full Changelog: v3.9.3...v3.9.4

v3.9.3

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.3/sops-v3.9.3.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.3.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.3/sops-v3.9.3.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.3.checksums.txt \
  --certificate sops-v3.9.3.checksums.pem \
  --signature sops-v3.9.3.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.3.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.3.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.3/sops-v3.9.3.intoto.jsonl

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

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.3
• ghcr.io/getsops/sops:v3.9.3-alpine

Quay.io

• quay.io/getsops/sops:v3.9.3
• quay.io/getsops/sops:v3.9.3-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.3 \
  --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

• build(deps): Bump the go group with 10 updates by @dependabot in #1699
• build(deps): Bump the ci group with 2 updates by @dependabot in #1698
• build(deps): Bump golang.org/x/crypto from 0.30.0 to 0.31.0 by @dependabot in #1703
• build(deps): Bump the ci group with 4 updates by @dependabot in #1708
• build(deps): Bump the rust group in /functional-tests with 2 updates by @dependabot in #1707
• CI: add 'persist-credentials: false' to checkout actions by @felixfontein in #1704
• build(deps): Bump filippo.io/age from 1.2.0 to 1.2.1 by @dependabot in #1710
• Bump golang.org/x/net to 0.33.0 to address CVE-2024-45338 by @felixfontein in #1714
• build(deps): Bump the go group across 1 directory with 13 updates by @dependabot in #1715
• build(deps): Bump serde_json from 1.0.133 to 1.0.134 in /functional-tests in the rust group by @dependabot in #1716
• build(deps): Bump the ci group with 2 updates by @dependabot in #1717
• GnuPG: do not incorrectly trim fingerprint in presence of exclamation marks for specfic subkey selection by @felixfontein in #1720
• Tests: use container images from https://github.com/getsops/ci-container-images by @felixfontein in #1722
• updatekeys subcommand: fix input-type CLI flag being ignored by @felixfontein in #1721
• Update all Go dependencies by @felixfontein in #1723
• build(deps): Bump the rust group in /functional-tests with 2 updates by @dependabot in #1725
• Release 3.9.3 by @felixfontein in #1724

Full Changelog: v3.9.2...v3.9.3

v3.9.2

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.2/sops-v3.9.2.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.2.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.2/sops-v3.9.2.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.2.checksums.txt \
  --certificate sops-v3.9.2.checksums.pem \
  --signature sops-v3.9.2.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.2.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.2.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.2/sops-v3.9.2.intoto.jsonl

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

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.2
• ghcr.io/getsops/sops:v3.9.2-alpine

Quay.io

• quay.io/getsops/sops:v3.9.2
• quay.io/getsops/sops:v3.9.2-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.2 \
  --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

• build(deps): Bump the go group with 11 updates by @dependabot in #1645
• build(deps): Bump the ci group with 4 updates by @dependabot in #1644
• build(deps): Bump the go group with 12 updates by @dependabot in #1649
• build(deps): Bump the ci group with 5 updates by @dependabot in #1648
• build(deps): Bump the go group with 6 updates by @dependabot in #1653
• build(deps): Bump the ci group with 2 updates by @dependabot in #1654
• build(deps): Bump serde_json from 1.0.128 to 1.0.132 in /functional-tests in the rust group by @dependabot in #1655
• fix(azkv): handle whitespace in Azure Key Vault URLs by @sEpt0r in #1652
• build(deps): Bump the go group with 7 updates by @dependabot in #1662
• build(deps): Bump the ci group with 5 updates by @dependabot in #1664
• build(deps): Bump the rust group in /functional-tests with 2 updates by @dependabot in #1663
• build(deps): Bump the ci group across 1 directory with 3 updates by @dependabot in #1673
• build(deps): Bump the rust group in /functional-tests with 2 updates by @dependabot in #1670
• build(deps): Bump github/codeql-action from 3.27.1 to 3.27.4 in the ci group by @dependabot in #1677
• build(deps): Bump the rust group in /functional-tests with 3 updates by @dependabot in #1676
• build(deps): Bump the ci group with 2 updates by @dependabot in #1685
• build(deps): Bump the go group across 1 directory with 18 updates by @dependabot in #1686
• Correctly handle comments during JSON serialization by @felixfontein in #1647
• Update Rust dependencies by @felixfontein in #1689
• fix(config): remove unused variables and align error casing by @nicklasfrahm in #1687
• keyservice: update protobuf to a recent release, and make go code generation reproducible by @felixfontein in #1688
• build(deps): Bump the go group with 8 updates by @dependabot in #1693
• Release 3.9.2 by @felixfontein in #1691

New Contributors

• @sEpt0r made their first contribution in #1652
• @nicklasfrahm made their first contribution in #1687

Full Changelog: v3.9.1...v3.9.2

v3.9.1

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

• Explicitly mark goreleaser's version, to avoid confusion with the Go version by @felixfontein in #1548
• build(deps): Bump the go group with 8 updates by @dependabot in #1550
• build(deps): Bump github/codeql-action from 3.25.10 to 3.25.11 in the ci group by @dependabot in #1551
• Fix the URL used for determining the latest SOPS version by @felixfontein in #1553
• build(deps): Bump the ci group with 4 updates by @dependabot in #1555
• build(deps): Bump the go group with 11 updates by @dependabot in #1554
• build(deps): Bump the go group with 10 updates by @dependabot in #1558
• build(deps): Bump the ci group with 3 updates by @dependabot in #1559
• build(deps): Bump the go group with 5 updates by @dependabot in #1562
• build(deps): Bump the ci group across 1 directory with 5 updates by @dependabot in #1564
• build(deps): Bump the go group with 4 updates by @dependabot in #1565
• build(deps): Bump github/codeql-action from 3.25.13 to 3.25.15 in the ci group by @dependabot in #1566
• build(deps): Bump github.com/docker/docker from 27.0.1+incompatible to 27.1.0+incompatible by @dependabot in #1568
• build(deps): Bump the go group with 5 updates by @dependabot in #1575
• build(deps): Bump the ci group with 2 updates by @dependabot in #1574
• build(deps): Bump github.com/docker/docker from 27.1.0+incompatible to 27.1.1+incompatible by @dependabot in #1581
• build(deps): Bump the ci group with 3 updates by @dependabot in #1584
• Note on the name of the configuration file by @ErraticMaker in #1569
• build(deps): Bump the ci group with 2 updates by @dependabot in #1586
• build(deps): Bump the go group across 1 directory with 15 updates by @dependabot in #1589
• build(deps): Bump the ci group with 2 updates by @dependabot in #1590
• build(deps): Bump the go group with 7 updates by @dependabot in #1593
• build(deps): Bump the ci group with 2 updates by @dependabot in #1592
• tests: ignore env var SOPS_AGE_KEY_FILE by @duthils in #1595
• build(deps): Bump the go group with 12 updates by @dependabot in #1602
• build(deps): Bump github.com/opencontainers/runc from 1.1.13 to 1.1.14 by @dependabot in #1603
• updatekeys subcommand: actually use option --shamir-secret-sharing-threshold by @felixfontein in #1608
• Added example of having age recipients in .sops.yaml by @felixfontein in #1607
• GitHub Actions linter for Rust formatting by @duthils in #1604
• github actions: set rust version globally by @duthils in #1612
• Fix --config being ignored by loadConfig by @lopter in #1613
• build(deps): Bump the go group with 4 updates by @dependabot in #1618
• build(deps): Bump github/codeql-action from 3.26.6 to 3.26.7 in the ci group by @dependabot in #1619
• unit tests: add coverage for unset by @duthils in #1617
• sops_test: homogenize use of asserts by @duthils in #1622
• sops_test: add more tests on errors by @duthils in #1624
• Add 'check' task to CI that makes sure everything is green by @felixfontein in #1621
• build(deps): Bump the go group with 10 updates by @dependabot in #1629
• build(deps): Bump github/codeql-action from 3.26.7 to 3.26.8 in the ci group by @dependabot in #1628
• refactor: specify missing file in error message by @t3hmrman in #1625
• CI: Build with Go 1.22 and 1.23; update Vault to 1.14 by @reneleonhardt in #1531
• Allow edit subcommand to create files by @felixfontein in #1596
• Build release with Go 1.22.x by @felixfontein in #1615
• GHA: fix checkout action version by @felixfontein in #1630
• Do not encrypt if a key group is empty, or there are no key groups by @felixfontein in #1600
• updatekeys subcommand: show changes in shamir_threshold by @felixfontein in #1609
• Dependabot: fix config for Docker, add config for Rust/Cargo by @felixfontein in #1632
• build(deps): Bump the ci group with 2 updates by @dependabot in #1634
• build(deps): Bump the go group with 7 updates by @dependabot in #1635
• Add Cargo.lock for better reproducability of functional tests by @felixfontein in #1637
• build(deps): Bump the go group with 7 updates by @dependabot in #1639
• build(deps...

v3.9.0

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.0/sops-v3.9.0.linux.amd64

# Move the binary in to your PATH
mv sops-v3.9.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 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.0/sops-v3.9.0.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.9.0.checksums.txt \
  --certificate sops-v3.9.0.checksums.pem \
  --signature sops-v3.9.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:

# Verify the binary using the checksums file
sha256sum -c sops-v3.9.0.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.0.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.0/sops-v3.9.0.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.9.0.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.9.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.9.0
• ghcr.io/getsops/sops:v3.9.0-alpine

Quay.io

• quay.io/getsops/sops:v3.9.0
• quay.io/getsops/sops:v3.9.0-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.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 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

• Respect aws_profile from Keygroup Config by @Kouzukii in #1049
• build(deps): Bump the go group with 6 updates by @dependabot in #1327
• build(deps): Bump the go group with 3 updates by @dependabot in #1328
• build(deps): Bump the go group with 1 update by @dependabot in #1330
• build(deps): Bump github.com/docker/docker from 20.10.24+incompatible to 24.0.7+incompatible by @dependabot in #1336
• build(deps): Bump the go group with 3 updates by @dependabot in #1334
• Improve README.rst by @Ph0tonic in #1339
• Fix typos by @felixfontein in #1337
• build(deps): Bump the go group with 7 updates by @dependabot in #1344
• Add --mac-only-encrypted to compute MAC only over values which end up encrypted by @mitar in #973
• build(deps): Bump the ci group with 1 update by @dependabot in #1347
• build(deps): Bump the go group with 7 updates by @dependabot in #1348
• README: Correctly tag code as yaml-stream by @felixfontein in #1350
• build(deps): Bump the go group with 5 updates by @dependabot in #1354
• use getUserConfigDir also in tests by @bkreitch in #1346
• Overwrite home dir in vault test by @bkreitch in #1349
• Allow configuration of indentation for YAML and JSON stores by @Ph0tonic in #1273
• build(deps): Bump github.com/go-jose/go-jose/v3 from 3.0.0 to 3.0.1 by @dependabot in #1357
• build(deps): Bump the go group with 4 updates by @dependabot in #1360
• build(deps): Bump the ci group with 1 update by @dependabot in #1359
• Fix TestGnuPGHome_Validate by @stormentt in #1370
• build(deps): Bump the go group with 6 updates by @dependabot in #1373
• build(deps): Bump the ci group with 2 updates by @dependabot in #1376
• Docs: indent is used both for encryption and decryption by @felixfontein in #1372
• fix a bug where not having a config results in a panic by @stormentt in #1371
• Polish the 'sops help' output a bit by @felixfontein in #1341
• introduce a --pristine flag to sops exec-env by @e-nikolov in #912
• Allow to pass multiple paths to 'updatekeys' by @sj14 in #1274
• Warn/fail if the wrong number of arguments is provided by @felixfontein in #1342
• Allow to override fileName with different value by @felixfontein in #1332
• Sort masterkeys according to decryption-order by @bkreitch in #1345
• build(deps): Bump the ci group with 4 updates by @dependabot in #1382
• build(deps): Bump the go group with 5 updates by @dependabot in #1381
• Deprecate the --background option to exec-env and exec-file by @felixfontein in #1379
• build(deps): Bump golang.org/x/crypto from 0.16.0 to 0.17.0 by @dependabot in #1383
• build(deps): Bump the ci group with 1 update by @dependabot in #1386
• build(deps): Bump the go group with 5 updates by @dependabot in #1385
• Consolidate Flatten/Unflatten pre/post processing by @lancerushing in #1356
• INI, DotEnv stores: shamir_threshold is an integer by @felixfontein in #1394
• Improve integration tests: reformat test code, make sure exit codes are always checked by @felixfontein in #1390
• Make check whether file contains invalid keys for encryption dependent on output store by @felixfontein in #1393
• Create a constant for the 'sops' metadata key by @felixfontein in #1398
• build(deps): Bump github.com/cloudflare/circl from 1.3.3 to 1.3.7 by @dependabot in #1408
• build(deps): Bump the ci group with 4 updates by @dependabot in #1425
• build(deps): Bump github.com/opencontainers/runc from 1.1.5 to 1.1.12 by @dependabot in #1428
• build(deps): Bump the go group with 10 updates by @dependabot in #1429
• build(deps): Bump the ci group with 4 updates by @dependabot in #1432
• Warn if more than one command is used by @felixfontein in #1388
• Move extraction of encryption and rotation options to separate functions by @felixfontein in #1389
• Add separate subcommands for encryption, decryption, rotating, editing, and setting values by @felixfontein in #1391
• Add basic tests for exec-env and exec-file by @felixfontein in #1396
• build with go 1.21 and update dependencies by @b-dean in #1427
• build(deps): Bump the go group with ...

v3.8.1

Note from the Maintainers

In this release of SOPS, we have focused on landing a variety of bug fixes to improve the overall user experience.

For a comprehensive list of changes, please refer to 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: #1246 (comment)

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.8.1/sops-v3.8.1.linux.amd64

# Move the binary in to your PATH
mv sops-v3.8.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.8.1/sops-v3.8.1.checksums.txt
curl -LO https://github.com/getsops/sops/releases/download/v3.8.1/sops-v3.8.1.checksums.pem
curl -LO https://github.com/getsops/sops/releases/download/v3.8.1/sops-v3.8.1.checksums.sig

# Verify the checksums file
cosign verify-blob sops-v3.8.1.checksums.txt \
  --certificate sops-v3.8.1.checksums.pem \
  --signature sops-v3.8.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.8.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.8.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.8.1/sops-v3.8.1.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <artifact> \
  --provenance-path sops-v3.8.1.intoto.jsonl \
  --source-uri github.com/getsops/sops \
  --source-tag v3.8.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.8.1
• ghcr.io/getsops/sops:v3.8.1-alpine

Quay.io

• quay.io/getsops/sops:v3.8.1
• quay.io/getsops/sops:v3.8.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.8.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

• build(deps): Bump the ci group with 3 updates by @dependabot in #1295
• pgp: improve handling of GnuPG home dir by @hiddeco in #1298
• Delete sops encrypted file we don't have keys for by @felixfontein in #1288
• Improve handling of errors when binary store handles bad data by @felixfontein in #1289
• On macOS, prefer XDG_CONFIG_HOME over os.UserConfigDir() by @felixfontein in #1291
• Do not crash if an empty YAML file is encrypted by @felixfontein in #1290
• Fix descriptions of unencrypted-regex and encrypted-regex flags, and ensure unencrypted_regex is considered in config validation by @mitar in #1300
• build(deps): Bump the go group with 4 updates by @dependabot in #1306
• build(deps): Bump the ci group with 1 update by @dependabot in #1301
• Handle return values of dec.Token() to improve error messages by @felixfontein in #1307
• pgp: make error the last return value by @felixfontein in #1310
• pgp: do not require abs path for SopsGpgExecEnv by @holiman in #1309
• decrypt: fix dropped error by @alrs in #1304
• Handle errors by @felixfontein in #1311
• Report key rotation errors by @felixfontein in #1317
• cmd/sops/main.go: make sure to wrap raw errors with toExitError() by @felixfontein in #1318
• build(deps): Bump the go group with 7 updates by @dependabot in #1319
• Enrich AWS authentication documentation by @nsantiago2719 in #1272
• Better error reporting for missing gpg binary by @makkes in #1286
• Improve RST and MD files by @felixfontein in #1320
• Add linting for RST and MD files by @felixfontein in #1287
• Update dependencies by @hiddeco in #1325
• Prepare v3.8.1 by @hiddeco in #1324

New Contributors

• @mitar made their first contribution in #1300
• @holiman made their first contribution in #1309
• @alrs made their first contribution in #1304
• @nsantiago2719 made their first contribution in #1272
• @makkes made their first contribution in #1286

Full Changelog: v3.8.0...v3.8.1

v3.8.0

Note from the Maintainers

We are extremely happy to introduce this new minor release of SOPS, now a CNCF Sandbox project under the stewardship of a new group of maintainers.

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 and a Cosign signed checksums file as release artifacts.

For a comprehensive list of changes, please refer to 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: #1246 (comment)

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.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 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.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:

# Verify the binary using the checksums file
sha256sum -c sops-v3.8.0.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.8.0.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.8.0/sops-v3.8.0.intoto.jsonl

# Verify the provenance of the artifact
slsa-verifier verify-artifact <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 with GitHub OIDC. To validate the signature of an image, run the following command:

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 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

• chore: update dependencies by @hiddeco in #1275
• build: pin actions to full length commit SHA and add CodeQL by @hiddeco in #1276
• Enable Dependabot for Docker, GitHub Actions and Go Mod by @hiddeco in #1277
• build(deps): Bump the go group with 2 updates by @dependabot in #1280
• build(deps): Bump the ci group with 6 updates by @dependabot in #1279
• release: generate versioned .intoto.jsonl by @hiddeco in #1278
• pgp: remove DisableAgent option by @hiddeco in #1282
• keyservices: address logging regression by @hiddeco in #1281
• chore: update dependencies by @hiddeco in #1283
• Prepare v3.8.0 by @hiddeco in #1284

Full Changelog: v3.8.0-rc.1...v3.8.0