Bump the go-deps group across 1 directory with 5 updates

[dependabot]

Bumps the go-deps group with 4 updates in the / directory: filippo.io/age, github.com/cyphar/filepath-securejoin, github.com/getsops/sops/v3 and github.com/onsi/gomega.

Updates filippo.io/age from 1.1.1 to 1.2.0

Release notes

Sourced from filippo.io/age's releases.

age v1.2.0

A small release to build the release binaries with a more recent Go toolchain, and to fix a couple CLI edge cases (FiloSottile/age#491, FiloSottile/age#555).

The Go module now exposes a plugin package that provides an age plugin client. That is, Recipient and Identity implementations that invoke a plugin binary, allowing the use of age plugins in Go programs.

Finally, Recipients can now return a set of "labels" by implementing RecipientWithLabels. This allows replicating the special behavior of the scrypt Recipient in third-party Recipients, or applying policy useful for authenticated or post-quantum Recipients.

// RecipientWithLabels can be optionally implemented by a Recipient, in which
// case Encrypt will use WrapWithLabels instead of Wrap.
//
// Encrypt will succeed only if the labels returned by all the recipients
// (assuming the empty set for those that don't implement RecipientWithLabels)
// are the same.
//
// This can be used to ensure a recipient is only used with other recipients
// with equivalent properties (for example by setting a "postquantum" label) or
// to ensure a recipient is always used alone (by returning a random label, for
// example to preserve its authentication properties).
type RecipientWithLabels interface {
	WrapWithLabels(fileKey []byte) (s []*Stanza, labels []string, err error)
}

Commits

• bbe6ce5 .github/workflows: update artifacts Actions
• 1e1bada .github/workflows: go-version stable, not latest
• 2293a9a .github/workflows: use latest Go for bootstrap
• 01fe9cd README: add pkgx installation instructions
• bd0511b cmd/age: detect output/input file reuse when possible
• febaade cmd/age: create file for empty decryptions
• 0a40718 doc: regenerate groff and html man pages
• 7ed4868 .github/workflows: apparently setup-go has no defaults
• 2a761fc .github/workflows: update GitHub Actions
• 98e7afc all: upgrade dependencies
• Additional commits viewable in compare view

Updates github.com/cyphar/filepath-securejoin from 0.2.5 to 0.3.1

Release notes

Sourced from github.com/cyphar/filepath-securejoin's releases.

v0.3.1

• By allowing Open(at)InRoot to opt-out of the extra work done by MkdirAll to do the necessary "partial lookups", Open(at)InRoot now does less work for both implementations (resulting in a many-fold decrease in the number of operations for openat2, and a modest improvement for non-openat2) and is far more guaranteed to match the correct openat2(RESOLVE_IN_ROOT) behaviour.

• We now use readlinkat(fd, "") where possible. For Open(at)InRoot this effectively just means that we no longer risk getting spurious errors during rename races. However, for our hardened procfs handler, this in theory should prevent mount attacks from tricking us when doing magic-link readlinks (even when using the unsafe host /proc handle). Unfortunately Reopen is still potentially vulnerable to those kinds of somewhat-esoteric attacks.

  Technically this will only work on post-2.6.39 kernels but it seems incredibly unlikely anyone is using filepath-securejoin on a pre-2011 kernel.

• Several improvements were made to the errors returned by Open(at)InRoot and MkdirAll when dealing with invalid paths under the emulated (ie. non-openat2) implementation. Previously, some paths would return the wrong error (ENOENT when the last component was a non-directory), and other paths would be returned as though they were acceptable (trailing-slash components after a non-directory would be ignored by Open(at)InRoot).

  These changes were done to match openat2's behaviour and purely is a consistency fix (most users are going to be using openat2 anyway).

Signed-off-by: Aleksa Sarai cyphar@cyphar.com

v0.3.0

This release contains no changes to SecureJoin.

However, it does introduce a new *os.File-based API which is much safer to use for most usecases. These are adapted from [libpathrs][1] and are the bare minimum to be able to operate more safely on an untrusted rootfs where an attacker has write access (something that SecureJoin cannot protect against). The new APIs are:

• OpenInRoot, which resolves a path inside a rootfs and returns an *os.File handle to the path. Note that the file handle returned by OpenInRoot is an O_PATH handle, which cannot be used for reading or writing (as well as some other operations -- see open(2) for more details).

• Reopen, which takes an O_PATH file handle and safely re-opens it to "upgrade" it to a regular handle.

... (truncated)

Changelog

Sourced from github.com/cyphar/filepath-securejoin's changelog.

[0.3.1] - 2024-07-23

Changed

• By allowing Open(at)InRoot to opt-out of the extra work done by MkdirAll to do the necessary "partial lookups", Open(at)InRoot now does less work for both implementations (resulting in a many-fold decrease in the number of operations for openat2, and a modest improvement for non-openat2) and is far more guaranteed to match the correct openat2(RESOLVE_IN_ROOT) behaviour.

• We now use readlinkat(fd, "") where possible. For Open(at)InRoot this effectively just means that we no longer risk getting spurious errors during rename races. However, for our hardened procfs handler, this in theory should prevent mount attacks from tricking us when doing magic-link readlinks (even when using the unsafe host /proc handle). Unfortunately Reopen is still potentially vulnerable to those kinds of somewhat-esoteric attacks.

  Technically this will only work on post-2.6.39 kernels but it seems incredibly unlikely anyone is using filepath-securejoin on a pre-2011 kernel.

Fixed

• Several improvements were made to the errors returned by Open(at)InRoot and MkdirAll when dealing with invalid paths under the emulated (ie. non-openat2) implementation. Previously, some paths would return the wrong error (ENOENT when the last component was a non-directory), and other paths would be returned as though they were acceptable (trailing-slash components after a non-directory would be ignored by Open(at)InRoot).

  These changes were done to match openat2's behaviour and purely is a consistency fix (most users are going to be using openat2 anyway).

[0.3.0] - 2024-07-11

Added

• A new set of *os.File-based APIs have been added. These are adapted from [libpathrs][] and we strongly suggest using them if possible (as they provide far more protection against attacks than SecureJoin):

  • Open(at)InRoot resolves a path inside a rootfs and returns an *os.File handle to the path. Note that the handle returned is an O_PATH handle, which cannot be used for reading or writing (as well as some other operations -- [see open(2) for more details][open.2])

  • Reopen takes an O_PATH file handle and safely re-opens it to upgrade it to a regular handle. This can also be used with non-O_PATH handles, but O_PATH is the most obvious application.

  • MkdirAll is an implementation of os.MkdirAll that is safe to use to

... (truncated)

Commits

• ce7b28a VERSION: release v0.3.1
• a2c14f8 CHANGELOG: add readlinkat(fd, "") shout-out
• 4ea279f merge #22 into cyphar/filepath-securejoin:main
• 16e1bec CHANGELOG: add initial changelog with current history
• 2404ffb merge #21 into cyphar/filepath-securejoin:main
• f29b7a4 lookup: handle // and trailing slash components correctly
• ecd61ca merge #19 into cyphar/filepath-securejoin:main
• 38b1220 procfs: refactor statx mnt_id logic
• 45c4415 procfs: use readlink(fd, "") for magic-links
• edab538 merge #17 into cyphar/filepath-securejoin:main
• Additional commits viewable in compare view

Updates github.com/getsops/sops/v3 from 3.8.1 to 3.9.0

Release notes

Sourced from github.com/getsops/sops/v3's releases.

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:

</tr></table> 

... (truncated)

Changelog

Sourced from github.com/getsops/sops/v3's changelog.

3.9.0

Features:

• Add --mac-only-encrypted to compute MAC only over values which end up encrypted (#973)
• Allow configuration of indentation for YAML and JSON stores (#1273, #1372)
• Introduce a --pristine flag to sops exec-env (#912)
• Allow to pass multiple paths to sops updatekeys (#1274)
• Allow to override fileName with different value (#1332)
• Sort masterkeys according to --decryption-order (#1345)
• Add separate subcommands for encryption, decryption, rotating, editing, and setting values (#1391)
• Add filestatus command (#545)
• Add command unset (#1475)
• Merge key for key groups and make keys unique (#1493)
• Support using comments to select parts to encrypt (#974, #1392)

Deprecations:

• Deprecate the --background option to exec-env and exec-file (#1379)

Improvements:

• Warn/fail if the wrong number of arguments is provided (#1342)
• Warn if more than one command is used (#1388)
• Dependency updates (#1327, #1328, #1330, #1336, #1334, #1344, #1348, #1354, #1357, #1360, #1373, #1381, #1383, #1385, #1408, #1428, #1429, #1427, #1439, #1454, #1460, #1466, #1489, #1519, #1525, #1528, #1540, #1543, #1545)
• Build with Go 1.21 (#1427)
• Improve README.rst (#1339, #1399, #1350)
• Fix typos (#1337, #1477, #1484)
• Polish the sops help output a bit (#1341, #1544)
• Improve and fix tests (#1346, #1349, #1370, #1390, #1396, #1492)
• Create a constant for the sops metadata key (#1398)
• Refactoring: move extraction of encryption and rotation options to separate functions (#1389)

Bug fixes:

• Respect aws_profile from keygroup config (#1049)
• Fix a bug where not having a config results in a panic (#1371)
• Consolidate Flatten/Unflatten pre/post processing (#1356)
• INI and DotEnv stores: shamir_threshold is an integer (#1394)
• Make check whether file contains invalid keys for encryption dependent on output store (#1393)
• Do not panic if updatekeys is used with a config that has no creation rules defined (#1506)
• exec-file: if --filename is used, use the provided filename without random suffix (#1474)
• Do not use DotEnv store for exec-env, but specialized environment serializing code (#1436)
• Decryption: do not fail if no matching creation_rule is present in config file (#1434)

Project changes:

• CI dependency updates (#1347, #1359, #1376, #1382, #1386, #1425, #1432, #1498, #1503, #1508, #1510, #1516, #1521, #1492, #1534)
• Adjust Makefile to new goreleaser 6.0.0 release (#1526)

Commits

• 1925952 Merge pull request #1546 from felixfontein/release-3.9.0
• 3264874 Bump version to 3.9.0.
• c5650fd Add 3.9.0 changelog.
• 61a8d6d Merge pull request #1545 from felixfontein/deps
• 822b5cc Update all go deps with 'go get -t -u ./...'.
• 72b7d5b Merge pull request #1493 from jonasbadstuebner/feature-merge-key-groups
• a1738b7 feat(config): merge key_groups
• aa800f1 Merge pull request #1392 from felixfontein/pr-974-continue
• 6cfb8ed Update documentation.
• f6ece99 Add check to avoid that UnencryptedCommentRegex matches encrypted comments.
• Additional commits viewable in compare view

Updates github.com/onsi/gomega from 1.33.1 to 1.34.1

Release notes

Sourced from github.com/onsi/gomega's releases.

v1.34.1

1.34.1

Maintenance

• Use slices from exp/slices to keep golang 1.20 compat [5e71dcd]

v1.34.0

1.34.0

Features

• Add RoundTripper method to ghttp.Server [c549e0d]

Fixes

• fix incorrect handling of nil slices in HaveExactElements (fixes #771) [878940c]
• issue_765 - fixed bug in Hopcroft-Karp algorithm [ebadb67]

Maintenance

• bump ginkgo [8af2ece]
• Fix typo in docs [123a071]
• Bump github.com/onsi/ginkgo/v2 from 2.17.2 to 2.17.3 (#756) [0e69083]
• Bump google.golang.org/protobuf from 1.33.0 to 1.34.1 (#755) [2675796]
• Bump golang.org/x/net from 0.24.0 to 0.25.0 (#754) [4160c0f]
• Bump github-pages from 230 to 231 in /docs (#748) [892c303]

Changelog

Sourced from github.com/onsi/gomega's changelog.

1.34.1

Maintenance

• Use slices from exp/slices to keep golang 1.20 compat [5e71dcd]

1.34.0

Features

• Add RoundTripper method to ghttp.Server [c549e0d]

Fixes

• fix incorrect handling of nil slices in HaveExactElements (fixes #771) [878940c]
• issue_765 - fixed bug in Hopcroft-Karp algorithm [ebadb67]

Maintenance

• bump ginkgo [8af2ece]
• Fix typo in docs [123a071]
• Bump github.com/onsi/ginkgo/v2 from 2.17.2 to 2.17.3 (#756) [0e69083]
• Bump google.golang.org/protobuf from 1.33.0 to 1.34.1 (#755) [2675796]
• Bump golang.org/x/net from 0.24.0 to 0.25.0 (#754) [4160c0f]
• Bump github-pages from 230 to 231 in /docs (#748) [892c303]

Commits

• fa057b8 v1.34.1
• 5e71dcd Use slices from exp/slices to keep golang 1.20 compat
• 32e5498 v1.34.0
• cb3fa6a run go mod tidy and wonder why go get doesnt just run it for me in the first ...
• 8af2ece bump ginkgo
• 878940c fix incorrect handling of nil slices in HaveExactElements (fixes #771)
• f5bec80 clean up bipartitegraph tests
• ebadb67 issue_765 - fixed bug in Hopcroft-Karp algorithm
• 123a071 Fix typo in docs
• c549e0d Add RoundTripper method to ghttp.Server
• Additional commits viewable in compare view

Updates golang.org/x/net from 0.24.0 to 0.27.0

Commits

• e2310ae go.mod: update golang.org/x dependencies
• 77708f7 quic: skip tests which depend on unimplemented UDP functions on Plan 9
• 9617c63 http2: avoid Transport hang with Connection: close and AllowHTTP
• 66e838c go.mod: update golang.org/x dependencies
• 6249541 http2: avoid race in server handler SetReadDeadine/SetWriteDeadline
• 603e3e6 quic: disable X25519Kyber768Draft00 in tests
• 67e8d0c http2: report an error if goroutines outlive serverTester tests
• 5608279 http2: avoid corruption in priority write scheduler
• 0d515a5 http2: factor out frame read/write test functions
• 9f5b79b http2: drop unused retry function
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.