Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up

Releases: getsops/sops

v3.9.4

25 Jan 19:46
v3.9.4
This tag was signed with the committer’sverified signature.
felixfontein Felix Fontein
GPG key ID:1E60B8598833B166
Verified
Learn about vigilant mode.
e794c79
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Installation

To installsops, 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 binarycurl -LO https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.linux.amd64# Move the binary in to your PATHmv sops-v3.9.4.linux.amd64 /usr/local/bin/sops# Make the binary executablechmod +x /usr/local/bin/sops

Verify checksums file signature

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

# Download the checksums file, certificate and signaturecurl -LO https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.checksums.txtcurl -LO https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.checksums.pemcurl -LO https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.checksums.sig# Verify the checksums filecosign 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 filesha256sum -c sops-v3.9.4.checksums.txt --ignore-missing

Verify artifact provenance

TheSLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through anin-toto link metadata file namedsops-v3.9.4.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifier tool:

# Download the metadata filecurl -LO  https://github.com/getsops/sops/releases/download/v3.9.4/sops-v3.9.4.intoto.jsonl# Verify the provenance of the artifactslsa-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

Thesops 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 andlinux/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 usingCosign 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 includeSLSA provenance attestations. For more information around the verification of this, please refer to theslsa-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 anSPDX JSON file, formatted as<binary>.spdx.sbom.json.

What's Changed

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

Contributors

  • @felixfontein
  • @dependabot
felixfontein and dependabot
Assets22
nico-arianto and stefanbritting reacted with thumbs up emojiheubeck and gojun077 reacted with hooray emoji
4 people reacted

v3.9.3

31 Dec 12:54
v3.9.3
This tag was signed with the committer’sverified signature.
felixfontein Felix Fontein
GPG key ID:1E60B8598833B166
Verified
Learn about vigilant mode.
3721355
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Installation

To installsops, 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 binarycurl -LO https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.linux.amd64# Move the binary in to your PATHmv sops-v3.9.3.linux.amd64 /usr/local/bin/sops# Make the binary executablechmod +x /usr/local/bin/sops

Verify checksums file signature

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

# Download the checksums file, certificate and signaturecurl -LO https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.checksums.txtcurl -LO https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.checksums.pemcurl -LO https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.checksums.sig# Verify the checksums filecosign 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 filesha256sum -c sops-v3.9.3.checksums.txt --ignore-missing

Verify artifact provenance

TheSLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through anin-toto link metadata file namedsops-v3.9.3.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifier tool:

# Download the metadata filecurl -LO  https://github.com/getsops/sops/releases/download/v3.9.3/sops-v3.9.3.intoto.jsonl# Verify the provenance of the artifactslsa-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

Thesops 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 andlinux/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 usingCosign 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 includeSLSA provenance attestations. For more information around the verification of this, please refer to theslsa-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 anSPDX JSON file, formatted as<binary>.spdx.sbom.json.

What's Changed

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

Contributors

  • @felixfontein
  • @dependabot
felixfontein and dependabot
Loading
nico-arianto and hendriknielaender reacted with thumbs up emoji
2 people reacted

v3.9.2

02 Dec 20:21
v3.9.2
This tag was signed with the committer’sverified signature.
felixfontein Felix Fontein
GPG key ID:1E60B8598833B166
Verified
Learn about vigilant mode.
bb710f3
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Installation

To installsops, 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 binarycurl -LO https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.linux.amd64# Move the binary in to your PATHmv sops-v3.9.2.linux.amd64 /usr/local/bin/sops# Make the binary executablechmod +x /usr/local/bin/sops

Verify checksums file signature

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

# Download the checksums file, certificate and signaturecurl -LO https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.checksums.txtcurl -LO https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.checksums.pemcurl -LO https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.checksums.sig# Verify the checksums filecosign 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 filesha256sum -c sops-v3.9.2.checksums.txt --ignore-missing

Verify artifact provenance

TheSLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through anin-toto link metadata file namedsops-v3.9.2.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifier tool:

# Download the metadata filecurl -LO  https://github.com/getsops/sops/releases/download/v3.9.2/sops-v3.9.2.intoto.jsonl# Verify the provenance of the artifactslsa-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

Thesops 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 andlinux/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 usingCosign 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 includeSLSA provenance attestations. For more information around the verification of this, please refer to theslsa-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 anSPDX JSON file, formatted as<binary>.spdx.sbom.json.

What's Changed

New Contributors

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

Contributors

  • @sEpt0r
  • @felixfontein
  • @nicklasfrahm
  • @dependabot
sEpt0r, felixfontein, and 2 other contributors
Loading
croissong and vin01 reacted with rocket emoji
2 people reacted

v3.9.1

04 Oct 05:14
v3.9.1
This tag was signed with the committer’sverified signature.
felixfontein Felix Fontein
GPG key ID:1E60B8598833B166
Verified
Learn about vigilant mode.
d50fda2
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Installation

To installsops, 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 binarycurl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.linux.amd64# Move the binary in to your PATHmv sops-v3.9.1.linux.amd64 /usr/local/bin/sops# Make the binary executablechmod +x /usr/local/bin/sops

Verify checksums file signature

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

# Download the checksums file, certificate and signaturecurl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.checksums.txtcurl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.checksums.pemcurl -LO https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.checksums.sig# Verify the checksums filecosign 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 filesha256sum -c sops-v3.9.1.checksums.txt --ignore-missing

Verify artifact provenance

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

# Download the metadata filecurl -LO  https://github.com/getsops/sops/releases/download/v3.9.1/sops-v3.9.1.intoto.jsonl# Verify the provenance of the artifactslsa-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

Thesops 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 andlinux/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 usingCosign 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 includeSLSA provenance attestations. For more information around the verification of this, please refer to theslsa-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 anSPDX JSON file, formatted as<binary>.spdx.sbom.json.

What's Changed

Read more

Contributors

  • @lopter
  • @t3hmrman
  • @ErraticMaker
  • @duthils
  • @felixfontein
  • @dependabot
  • @reneleonhardt
lopter, t3hmrman, and 5 other contributors
Loading
nico-arianto, hendriknielaender, willianpaixao, FortuneBoxRepo, onedr0p, and dosu-customer-success reacted with thumbs up emojiheubeck, willianpaixao, and onedr0p reacted with hooray emojibartvdbraak, hendriknielaender, fabidick22, willianpaixao, sedna99, onedr0p, and dosu-customer-success reacted with heart emoji
10 people reacted

v3.9.0

28 Jun 06:14
v3.9.0
This tag was signed with the committer’sverified signature.
felixfontein Felix Fontein
GPG key ID:1E60B8598833B166
Verified
Learn about vigilant mode.
1925952
This commit was created on GitHub.com and signed with GitHub’sverified signature.
GPG key ID:B5690EEEBB952194
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Installation

To installsops, 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 binarycurl -LO https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.linux.amd64# Move the binary in to your PATHmv sops-v3.9.0.linux.amd64 /usr/local/bin/sops# Make the binary executablechmod +x /usr/local/bin/sops

Verify checksums file signature

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

# Download the checksums file, certificate and signaturecurl -LO https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.checksums.txtcurl -LO https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.checksums.pemcurl -LO https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.checksums.sig# Verify the checksums filecosign 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 filesha256sum -c sops-v3.9.0.checksums.txt --ignore-missing

Verify artifact provenance

TheSLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through anin-toto link metadata file namedsops-v3.9.0.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifier tool:

# Download the metadata filecurl -LO  https://github.com/getsops/sops/releases/download/v3.9.0/sops-v3.9.0.intoto.jsonl# Verify the provenance of the artifactslsa-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

Thesops 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 andlinux/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 usingCosign 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 includeSLSA provenance attestations. For more information around the verification of this, please refer to theslsa-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 anSPDX JSON file, formatted as<binary>.spdx.sbom.json.

What's Changed

Read more

Contributors

  • @lancerushing
  • @endorama
  • @mitar
  • @bkreitch
  • @e-nikolov
  • @b-dean
  • @duthils
  • @Ph0tonic
  • @felixfontein
  • @sj14
  • @TheoBrigitte
  • @Kouzukii
  • @jonasbadstuebner
  • @stormentt
  • @dependabot
  • @tomaszduda23
  • @rjeczkow
  • @pullmerge
lancerushing, endorama, and 16 other contributors
Loading
dmpe, BackSpace54, DamyrFr, gaby, nico-arianto, danielmartins-hotmart, fabidick22, djgoku, emerconn, hemanth-at-beehyv, and 3 more reacted with thumbs up emojisedlund, BackSpace54, gustav-b, 0xfeeddeadbeef, nikaro, konradmalik, mavogel, almereyda, gaby, croissong, and 7 more reacted with hooray emojifabidick22, emerconn, diegorafael, and igor-policee reacted with heart emoji
25 people reacted

v3.8.1

11 Oct 15:25
v3.8.1
This tag was signed with the committer’sverified signature.
hiddeco Hidde Beydals
GPG key ID:979F380FC2341744
Verified
Learn about vigilant mode.
b6d3c97
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

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 toCHANGELOG.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 usego.mozilla.org/sops/v3 as a library, going forward, import the Go Module usinggithub.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 installsops, 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 binarycurl -LO https://github.com/getsops/sops/releases/download/v3.8.1/sops-v3.8.1.linux.amd64# Move the binary in to your PATHmv sops-v3.8.1.linux.amd64 /usr/local/bin/sops# Make the binary executablechmod +x /usr/local/bin/sops

Verify checksums file signature

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

# Download the checksums file, certificate and signaturecurl -LO https://github.com/getsops/sops/releases/download/v3.8.1/sops-v3.8.1.checksums.txtcurl -LO https://github.com/getsops/sops/releases/download/v3.8.1/sops-v3.8.1.checksums.pemcurl -LO https://github.com/getsops/sops/releases/download/v3.8.1/sops-v3.8.1.checksums.sig# Verify the checksums filecosign 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 filesha256sum -c sops-v3.8.1.checksums.txt --ignore-missing

Verify artifact provenance

TheSLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through anin-toto link metadata file namedsops-v3.8.1.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifier tool:

# Download the metadata filecurl -LO  https://github.com/getsops/sops/releases/download/v3.8.1/sops-v3.8.1.intoto.jsonl# Verify the provenance of the artifactslsa-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

Thesops 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 andlinux/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 usingCosign 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 includeSLSA provenance attestations. For more information around the verification of this, please refer to theslsa-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 anSPDX JSON file, formatted as<binary>.spdx.sbom.json.

What's Changed

New Contributors

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

Contributors

  • @alrs
  • @holiman
  • @makkes
  • @mitar
  • @felixfontein
  • @nsantiago2719
  • @hiddeco
  • @dependabot
alrs, holiman, and 6 other contributors
Loading
anthr76, hiddeco, TiLogic, nico-arianto, pjbgf, 1doce8, gakonst, bb-Ricardo, KingMichaelPark, bhavikbhavsar, and 6 more reacted with hooray emojiwillianpaixao, wallind, and onedr0p reacted with heart emojidorkamotorka, 1doce8, willianpaixao, and onedr0p reacted with rocket emoji
18 people reacted

v3.8.0

15 Sep 13:52
v3.8.0
This tag was signed with the committer’sverified signature.
hiddeco Hidde Beydals
GPG key ID:979F380FC2341744
Verified
Learn about vigilant mode.
a750d72
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Note from the Maintainers

We are extremely happy to introduce this new minor release of SOPS, now aCNCF Sandbox project under the stewardship of a newgroup 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 toCHANGELOG.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 usego.mozilla.org/sops/v3 as a library, going forward, import the Go Module usinggithub.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 installsops, 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 binarycurl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.linux.amd64# Move the binary in to your PATHmv sops-v3.8.0.linux.amd64 /usr/local/bin/sops# Make the binary executablechmod +x /usr/local/bin/sops

Verify checksums file signature

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

# Download the checksums file, certificate and signaturecurl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.txtcurl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.pemcurl -LO https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.checksums.sig# Verify the checksums filecosign 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 filesha256sum -c sops-v3.8.0.checksums.txt --ignore-missing

Verify artifact provenance

TheSLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through anin-toto link metadata file namedsops-v3.8.0.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifier tool:

# Download the metadata filecurl -LO  https://github.com/getsops/sops/releases/download/v3.8.0/sops-v3.8.0.intoto.jsonl# Verify the provenance of the artifactslsa-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

Thesops 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 andlinux/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 usingCosign 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 includeSLSA provenance attestations. For more information around the verification of this, please refer to theslsa-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 anSPDX JSON file, formatted as<binary>.spdx.sbom.json.

What's Changed

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

Contributors

  • @hiddeco
  • @dependabot
hiddeco and dependabot
Loading
nico-arianto, szymonpk, and vaskulikov1983 reacted with thumbs up emojiZebradil, onedr0p, laghoule, felixfontein, MrOwen, hiddeco, buroa, nclv, rxbn, lucasfcnunes, and 9 more reacted with hooray emojiPumba98, devstein, szymonpk, strgalt-t, jshawl, and beddari reacted with heart emojialmereyda, dorkamotorka, and szymonpk reacted with rocket emoji
27 people reacted

v3.8.0-rc.1

25 Aug 11:33
v3.8.0-rc.1
This tag was signed with the committer’sverified signature.
hiddeco Hidde Beydals
GPG key ID:979F380FC2341744
Verified
Learn about vigilant mode.
7b3a032
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading
v3.8.0-rc.1Pre-release
Pre-release

Note from the Maintainers

We're thrilled to introduce thev3.8.0-rc.1 release candidate of SOPS, now aCNCF Sandbox project under the stewardship of a newgroup of maintainers.

This release involved significant effort in rewriting and enhancing key source implementations. Notably, we've modernized the code and updated all SDKs, including updating to AWS SDK v2. Some of these implementations had been neglected, lacking support for newer features. Now, they should be good for extended service.

Moreover, we've completely revamped the release process. Beyond delivering binaries and packages, it now provides enhanced assurance by publishing SBOMs (Software Bill of Materials),SLSA3 provenance attestation, and a Cosign signed checksums file as GitHub release artifacts.

Additionally, the Darwin binary is now distributed as a"fat binary", making it executable on both AMD64 and ARM64 machines.

The goal of this release candidate is primarily to validate our new release process and the quite impactful changes mentioned above. Take it for a spin andshare your thoughts, your feedback is much appreciated!

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 usego.mozilla.org/sops/v3 as a library, going forward, import the Go Module usinggithub.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 installsops, 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 binarycurl -LO https://github.com/getsops/sops/releases/download/v3.8.0-rc.1/sops-v3.8.0-rc.1.linux.amd64# Move the binary in to your PATHmv sops-v3.8.0-rc.1.linux.amd64 /usr/local/bin/sops# Make the binary executablechmod +x /usr/local/bin/sops

Verify checksums file signature

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

# Download the checksums file, certificate and signaturecurl -LO https://github.com/getsops/sops/releases/download/v3.8.0-rc.1/sops-v3.8.0-rc.1.checksums.txtcurl -LO https://github.com/getsops/sops/releases/download/v3.8.0-rc.1/sops-v3.8.0-rc.1.checksums.pemcurl -LO https://github.com/getsops/sops/releases/download/v3.8.0-rc.1/sops-v3.8.0-rc.1.checksums.sig# Verify the checksums filecosign verify-blob sops-v3.8.0-rc.1.checksums.txt \  --certificate sops-v3.8.0-rc.1.checksums.pem \  --signature sops-v3.8.0-rc.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 filesha256sum -c sops-v3.8.0-rc.1.checksums.txt --ignore-missing

Verify artifact provenance

TheSLSA provenance of the binaries, packages, and SBOMs can be found within the artifacts associated with this release. It is presented through anin-toto link metadata file namedprovenance.intoto.jsonl. To verify the provenance of an artifact, you can utilize theslsa-verifier tool:

# Download the metadata filecurl -LO  https://github.com/getsops/sops/releases/download/v3.8.0-rc.1/provenance.intoto.jsonl# Verify the provenance of the artifactslsa-verifier verify-artifact<artifact> \  --provenance-path provenance.intoto.jsonl \  --source-uri github.com/getsops/sops \  --source-tag v3.8.0-rc.1

Container Images

Thesops 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 andlinux/arm64.

GitHub Container Registry

  • ghcr.io/getsops/sops:v3.8.0-rc.1
  • ghcr.io/getsops/sops:v3.8.0-rc.1-alpine

Quay.io

  • quay.io/getsops/sops:v3.8.0-rc.1
  • quay.io/getsops/sops:v3.8.0-rc.1-alpine

Verify container image signature

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

cosign verify ghcr.io/getsops/sops:v3.8.0-rc.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 includeSLSA provenance attestations. For more information around the verification of this, please refer to theslsa-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 anSPDX JSON file, formatted as<binary>.spdx.sbom.json.

What's Changed

Read more

Contributors

  • @vbehar
  • @stoned
  • @daurnimator
  • @Gobd
  • @hrobertson
  • @edofic
  • @ajvb
  • @flx5
  • @felixfontein
  • @hiddeco
  • @dependabot
  • @hramberger
vbehar, stoned, and 10 other contributors
Loading
crenshaw-dev, stefanprodan, discosultan, Pumba98, phoban01, CathalMullan, fabidick22, MrOwen, felixfontein, chulkilee, and 15 more reacted with hooray emojiMrOwen, stehessel, budimanjojo, and mrcarter7 reacted with rocket emojiMoskovych reacted with eyes emoji
26 people reacted

v3.7.3

09 May 17:37
e1edc05
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Changes:

  • Upgrade dependencies (#1024,#1045)
  • Build alpine container in CI (#1018,#1032,#1025)
  • keyservice: accept KeyServiceServer in LocalClient (#1035)
  • Add support for GCP Service Account withinGOOGLE_CREDENTIALS (#953)

Bug fixes:

  • Upload the correct binary for the linux amd64 build (#1026)
  • Fix bug when specifying multiple age recipients (#966)
  • Allow for empty yaml maps (#908)

Commits

  • [75cd389]: Add a test to reproduce#907 (ikedam)#908
  • [108b211]: Allow empty maps for yaml (#907) (ikedam)#908
  • [ea8b3bb]: support gcp credentials as env var (Kaplinsky, Joshua B)#953
  • [c0dc484]: Update keysource.go (Josh Kaplinsky)#953
  • [63fa89c]: Merge remote-tracking branch 'remotes/origin/develop' into feature/907_FixEmptyYaml (ikedam)#908
  • [b926cf9]: Build alpine container in CI (#870) (ikedam)#1018
  • [234bf9f]: Upgrade all dependencies (AJ Bahnken)#1024
  • [4277de4]: Remove duplicated stage from Dockerfile.alpine (Shouichi Kamiya)#1025
  • [605fb27]: Explicitly build linux amd64 binary (Janis Peisenieks)#1026
  • [7ebee3d]: This fixes a bug with age encryption when specifying multiple age recipients (Cedric Kienzler)#966
  • [b5f5f28]: MakemasterKeyFromRecipient private (Cedric Kienzler)#966
  • [1dc90ad]: Add tests for single key (Cedric Kienzler)#966
  • [3875b00]: Use latest dockerd in CI to allow build alpine image (#870) (ikedam)#1032
  • accept KeyServiceServer in LocalClient#1035 (Hidde Beydals)
  • [1bb30e2]: Limit role session name length to 64 characters. (AJ Bahnken)#1037
  • [a01208c]: Update golang.org/x/crypto (Hidde Beydals)#1045
  • [e128fa2]: Update keyservice implementation dependencies (Hidde Beydals)#1045
  • [220b652]: Update golang.org/x/{net,oauth2,sys} dependencies (Hidde Beydals)#1045
  • [477b61f]: Update remaining dependencies (Hidde Beydals)#1045
  • [25817ed]: Replace x/crypto/openpgp with ProtonMail/go-crypto (Hidde Beydals)#1045
  • [07aea97]: Merge remote-tracking branch 'upstream/develop' into develop (Josh Kaplinsky)#953
  • [4ffb54c]: Use custom GOOGLE_CREDENTIALS or fallback to default (Josh Kaplinsky)#953
  • [17fb03f]: Merge remote-tracking branch 'upstream/develop' into develop (Josh Kaplinsky)#953
  • [15583bd]: prep for v3.7.3 (AJ Bahnken)#1053
Loading
multani, svengreb, tonsV2, tetafro, dbustamanteSimtlix, sara4dev, tz-torchai, camanducci, GylSky, luckypenny, and 28 more reacted with thumbs up emojizachzoref, Thalita-ribeiro, and BrenoCarvalho reacted with laugh emojimultani, engin, 0xfeeddeadbeef, tonsV2, croissong, tz-torchai, luckypenny, bujosa, marianbendik, benjaminspringer98, and 8 more reacted with hooray emojimultani, pesarkhobeee, tonsV2, khacnha, jm-janzen, tz-torchai, luckypenny, bujosa, littlekath25, angel-94, and 9 more reacted with heart emojimultani, danisvaliev001, Sandra-I, loa, tz-torchai, luckypenny, bujosa, mabotn, angel-94, benjaminspringer98, and 6 more reacted with rocket emojimultani, pi-cparkins, luckypenny, bujosa, ethanbienstock, benjaminspringer98, TkPegatron, tal-ayalon, Thalita-ribeiro, melotik, and BrenoCarvalho reacted with eyes emoji
68 people reacted

v3.7.2

09 Mar 19:26
86f500d
This commit was created on GitHub.com and signed with GitHub’sverified signature. The key has expired.
GPG key ID:4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
Loading

Changes:

Bug Fixes

  • Make sure comments in yaml files are not duplicated (#866)
  • Make sure configuration file paths work correctly relative to the config file in us (#853)

Commits

  • [e98451e]: Remove unused age code (Hidde Beydals)#842
  • [2395f07]: small release workflow fix (AJ Bahnken)
  • [c5b1298]: Match file path relative to config file's directory (2) (#853) (Paulo Lieuthier)#853
  • [7626399]: fix missing argument in encrypting with age section (#860) (Damien Léger)#860
  • [3acf53e]: Correct path to age keys.txt in documentation (#861) (Alexey Odinokov)#861
  • [5af8e63]: Prevent comment duplication. (#866) (Felix Fontein)#866
  • [688fa22]: Remove SOPS_GPG_KEYSERVER reference in README.rst (Enrico204)#883
  • [02d57ca]: Tests should not fail fast (ikedam)#909
  • [6130ffe]: Use the key ofrelease@mozilla.com for the unit test (#882) (#906) (ikedam)#906
  • [56bbf84]: Added support for go 1.16 and darwin-arm64 (Nikola Milojević)#911
  • [f6e9891]: fix a typo (brant4test)#967
  • [086c11d]: Support SOPS_AGE_KEY environment variable (Christian Hoffmeister)#1006
  • [a98768b]: Fix flakey test run on OSX (Alex Castle)#1008
  • [6bfd72d]: Merge remote-tracking branch 'origin/develop' into sops-age-key-env (Christian Hoffmeister)#1006
  • [dc2267e]: Upgrade to go 1.17 (AJ Bahnken)#1012
  • [076f295]: rm extra whitespace in CircleCI config (AJ Bahnken)#1012
  • [7f503bc]: Upgrade release job to go 1.17 (AJ Bahnken)#1012
  • [4bd3e5a]: Update pip package name in Dockerfile (AJ Bahnken)#1012
  • [b7c58e4]: Move age environment variable names to constants (Christian Hoffmeister)#1006
  • [684d338]: Merge branch 'develop' ofhttps://github.com/mozilla/sops into mozilla-develop (Nikola Milojević)#911
  • [0cfcae6]: Merge branch 'mozilla-develop' into develop (Nikola Milojević)#911
  • [dff9c31]: Merge branch 'develop' into sops-age-key-env (AJ Bahnken)#1006
  • [c586534]: Change labeling and upload linux arm64 (AJ Bahnken)#1014
  • [d6bc216]: README and author tweaks (AJ Bahnken)#1016
  • [822ce48]: Add arm64 .deb and .rpm builds (Janis Peisenieks)#891
  • [baec2a5]: Merge branch 'develop' into feature/testsSholdNotFailFast (ikedam)#909
  • [035672f]: prep v3.7.2 (AJ Bahnken)#1020
  • [b67c7a7]: Fixed CHANGELOG formatting (AJ Bahnken)#1020
Loading
svengreb, onedr0p, danielcompton, miguel-ortiz-e, replacewithname, bartmanus, tomislater, ricmatsui, mschuett, cbanciu667, and 10 more reacted with hooray emojibboynton97, Debzou, miljanic, and Intellectual777 reacted with heart emojigouglhupf, nklmilojevic, svengreb, onedr0p, miguel-ortiz-e, croissong, tomislater, ricmatsui, bboynton97, and nickkeyzer reacted with rocket emoji
25 people reacted
Previous13
Previous

[8]ページ先頭

©2009-2025 Movatter.jp