[v7](go): Bump the dependencies group with 8 updates

[dependabot]

Bumps the dependencies group with 8 updates:

Package	From	To
code.cloudfoundry.org/bytefmt	0.24.0	0.25.0
code.cloudfoundry.org/clock	1.27.0	1.28.0
code.cloudfoundry.org/lager/v3	3.21.0	3.22.0
code.cloudfoundry.org/tlsconfig	0.14.0	0.15.0
github.com/cyphar/filepath-securejoin	0.3.6	0.4.0
github.com/mattn/go-colorable	0.1.13	0.1.14
golang.org/x/crypto	0.31.0	0.32.0
golang.org/x/net	0.33.0	0.34.0

Updates code.cloudfoundry.org/bytefmt from 0.24.0 to 0.25.0

Commits

• 00cdfd1 Update go.mod dependencies
• See full diff in compare view

Updates code.cloudfoundry.org/clock from 1.27.0 to 1.28.0

Commits

• facb55a Update go.mod dependencies
• See full diff in compare view

Updates code.cloudfoundry.org/lager/v3 from 3.21.0 to 3.22.0

Commits

• 374f9d7 Update go.mod dependencies
• See full diff in compare view

Updates code.cloudfoundry.org/tlsconfig from 0.14.0 to 0.15.0

Commits

• 69392bb Update go.mod dependencies
• See full diff in compare view

Updates github.com/cyphar/filepath-securejoin from 0.3.6 to 0.4.0

Release notes

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

v0.4.0

This release primarily includes a few minor breaking changes to make the MkdirAll and SecureJoin interfaces more robust against accidental misuse.

• SecureJoin(VFS) will now return an error if the provided root is not a filepath.Clean'd path.

  While it is ultimately the responsibility of the caller to ensure the root is a safe path to use, passing a path like /symlink/.. as a root would result in the SecureJoin'd path being placed in / even though /symlink/.. might be a different directory, and so we should more strongly discourage such usage.

  All major users of securejoin.SecureJoin already ensure that the paths they provide are safe (and this is ultimately a question of user error), but removing this foot-gun is probably a good idea. Of course, this is necessarily a breaking API change (though we expect no real users to be affected by it).

  Thanks to Erik Sjölund, who initially reported this issue as a possible security issue.

• MkdirAll and MkdirHandle now take an os.FileMode-style mode argument instead of a raw unix.S_*-style mode argument, which may cause compile-time type errors depending on how you use filepath-securejoin. For most users, there will be no change in behaviour aside from the type change (as the bottom 0o777 bits are the same in both formats, and most users are probably only using those bits).

  However, if you were using unix.S_ISVTX to set the sticky bit with MkdirAll(Handle) you will need to switch to os.ModeSticky otherwise you will get a runtime error with this update. In addition, the error message you will get from passing unix.S_ISUID and unix.S_ISGID will be different as they are treated as invalid bits now (note that previously passing said bits was also an error).

Thanks to the following contributors for helping make this release possible:

• Aleksa Sarai [email protected]
• Erik Sjölund [email protected]

Signed-off-by: Aleksa Sarai [email protected]

Changelog

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

[0.4.0] - 2025-01-13

Breaking

• SecureJoin(VFS) will now return an error if the provided root is not a filepath.Clean'd path.

  While it is ultimately the responsibility of the caller to ensure the root is a safe path to use, passing a path like /symlink/.. as a root would result in the SecureJoin'd path being placed in / even though /symlink/.. might be a different directory, and so we should more strongly discourage such usage.

  All major users of securejoin.SecureJoin already ensure that the paths they provide are safe (and this is ultimately a question of user error), but removing this foot-gun is probably a good idea. Of course, this is necessarily a breaking API change (though we expect no real users to be affected by it).

  Thanks to Erik Sjölund, who initially reported this issue as a possible security issue.

• MkdirAll and MkdirHandle now take an os.FileMode-style mode argument instead of a raw unix.S_*-style mode argument, which may cause compile-time type errors depending on how you use filepath-securejoin. For most users, there will be no change in behaviour aside from the type change (as the bottom 0o777 bits are the same in both formats, and most users are probably only using those bits).

  However, if you were using unix.S_ISVTX to set the sticky bit with MkdirAll(Handle) you will need to switch to os.ModeSticky otherwise you will get a runtime error with this update. In addition, the error message you will get from passing unix.S_ISUID and unix.S_ISGID will be different as they are treated as invalid bits now (note that previously passing said bits was also an error).

Commits

• 9a17e6b VERSION: release v0.4.0
• e410d4a merge #44 into cyphar/filepath-securejoin:main
• ea4e5b6 gha: add GOARCH=386 build check
• 0c2fbe6 mkdirall: switch to os.FileMode argument
• f3a512c merge #43 into cyphar/filepath-securejoin:main
• bc750ad join: return an error if root is unclean path
• 1be4136 gha: always check for latest Go release
• b498783 merge #38 into cyphar/filepath-securejoin:main
• 682d3ad VERSION: back to development
• See full diff in compare view

Updates github.com/mattn/go-colorable from 0.1.13 to 0.1.14

Commits

• 1f71342 update deps
• 4503567 Merge pull request #73 from whereswaldon/patch-1
• 40e70a5 [Windows] harden system DLL loading
• 603fb50 Merge pull request #71 from hymkor/fork-20241118
• 664d917 Fix: ESC[E and ESC[F with no arguments did not move the cursor on the legacy ...
• 2b733b5 Merge pull request #69 from dolmen-go/merge-appengine-into-others
• 9473000 Merge pull request #68 from dolmen-go/do-not-expose-Windows-Writer
• 3cc8472 Merge pull request #67 from dolmen-go/ci-go1.20
• d9a68d5 Merge colorable_appengine.go into colorable_others.go
• 8e4a944 Windows: do not export Writer
• Additional commits viewable in compare view

Updates golang.org/x/crypto from 0.31.0 to 0.32.0

Commits

• 8929309 go.mod: update golang.org/x dependencies
• 4a75ba5 all: make function and struct comments match the names
• See full diff in compare view

Updates golang.org/x/net from 0.33.0 to 0.34.0

Commits

• 8da7ed1 go.mod: update golang.org/x dependencies
• 2124140 all: make function and struct comments match the names
• e9d95ba http2: do not surface errors from a conn's idle timer expiring
• c2be992 quic: remember which remote connection IDs have been retired
• See full diff 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

[joaopapereira]

@dependabot rebase