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

[dependabot]

Bumps the go-deps group with 2 updates in the / directory: github.com/ProtonMail/go-crypto and github.com/cyphar/filepath-securejoin.

Updates github.com/ProtonMail/go-crypto from 1.1.0-alpha.5-proton to 1.1.0-beta.0-proton

Release notes

Sourced from github.com/ProtonMail/go-crypto's releases.

v1.1.0-beta.0-proton

This pre-release is v1.1.0-beta.0 with support for symmetric keys and automatic forwarding, both of which are not standardized yet.

v1.1.0-beta.0

What's Changed

• Allow Salted S2K for high-entropy passphrases by @​twiss in ProtonMail/go-crypto#219
• fix data race in getEd25519Sk by @​DmitriyMV in ProtonMail/go-crypto#220
• Add back crypto.Signer support for ECDSA signing keys. by @​doryiii in ProtonMail/go-crypto#227
• Add support for keyserver preferences and preferred keyserver (closes #206) by @​andrewgdotcom in ProtonMail/go-crypto#232
• Fix ECDH using v6 keys by @​twiss in ProtonMail/go-crypto#233
• No v6 ECC keys with legacy OIDs by @​lubux in ProtonMail/go-crypto#234

Full Changelog: ProtonMail/go-crypto@v1.1.0-alpha.5...v1.1.0-beta.0

Commits

• b04e354 Fix HMAC generation (#204)
• 85bc845 Replace ioutil.ReadAll with io.ReadAll
• 5f49c73 fix(v2): Adapt NewForwardingEntity to refactored NewEntity
• 9aa010a fix(v2): Do not allow encrpytion with a forwarding key
• 91c2e9e feat: Add symmetric keys to v2
• 3f6d02a fix: Address warnings
• da0a0cf feat: Add forwarding to v2 api
• 0e6a359 fix: Address rebase on version 2 issues
• c602a74 Use fingerprints instead of KeyIDs
• 348b81d Create a copy of the encrypted key when forwarding
• Additional commits viewable in compare view

Updates github.com/cyphar/filepath-securejoin from 0.3.2 to 0.3.3

Release notes

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

v0.3.3

This release primarily includes fixes for spurious errors we hit when checking that directories created by MkdirAll "look right". Upon further consideration, these checks were fundamentally buggy and didn't offer any practical protection anyway.

• The mode and owner verification logic in MkdirAll has been removed. This was originally intended to protect against some theoretical attacks but upon further consideration these protections don't actually buy us anything and they were causing spurious errors with more complicated filesystem setups.
• The "is the created directory empty" logic in MkdirAll has also been removed. This was not causing us issues yet, but some pseudofilesystems (such as cgroup) create non-empty directories and so this logic would've been wrong for such cases.

Thanks to all of the contributors who made this release possible:

• Aleksa Sarai cyphar@cyphar.com
• Kir Kolyshkin kolyshkin@gmail.com

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

Changelog

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

[0.3.3] - 2024-09-30

Fixed

• The mode and owner verification logic in MkdirAll has been removed. This was originally intended to protect against some theoretical attacks but upon further consideration these protections don't actually buy us anything and they were causing spurious errors with more complicated filesystem setups.
• The "is the created directory empty" logic in MkdirAll has also been removed. This was not causing us issues yet, but some pseudofilesystems (such as cgroup) create non-empty directories and so this logic would've been wrong for such cases.

Commits

• 93cff46 VERSION: release v0.3.3
• 2b3d97d merge #26 into cyphar/filepath-securejoin:main
• 09afcf2 OpenInRoot: add CVE link to godoc
• 5b5a7a4 Add cross-links to godoc
• daead99 Remove osVFS methods documentation
• 208ded3 tests: don't panic if the fd is closed
• 626b5a5 merge #29 into cyphar/filepath-securejoin:main
• 92b699d mkdir: don't check that the directory is empty
• 90adf5c mkdir: do not return errors for incorrect directory modes or owners
• 3bf6419 merge #30 into cyphar/filepath-securejoin:main
• 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]

Superseded by #767.