chore(deps): update dependency gojue/ecapture to v0.9.5

[uniget-bot]

This PR contains the following updates:

Package	Update	Change
gojue/ecapture	patch	0.9.4 -> 0.9.5

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

gojue/ecapture (gojue/ecapture)

v0.9.5

Compare Source

What's Changed

Full Changelog: gojue/ecapture@v0.9.4...v0.9.5

---

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[nicholasdille-bot]

Auto-approved because label type/renovate is present.

[github-actions]

🔍 Vulnerabilities of ghcr.io/uniget-org/tools/ecapture:0.9.5

📦 Image Reference ghcr.io/uniget-org/tools/ecapture:0.9.5

digest	sha256:61759513d1592b337fa56aa3faace3d203ba4378dbad290ae4fd2d1f9f3a4211
vulnerabilities
platform	linux/amd64
size	29 MB
packages	41

golang.org/x/crypto 0.31.0 (golang) pkg:golang/golang.org/x/crypto@0.31.0 Affected range <0.35.0 Fixed version 0.35.0 Description SSH servers which implement file transfer protocols are vulnerable to a denial of service attack from clients which complete the key exchange slowly, or not at all, causing pending content to be read into memory, but never transmitted.

stdlib 1.22.10 (golang) pkg:golang/stdlib@1.22.10 Affected range <1.22.11 Fixed version 1.22.11 Description A certificate with a URI which has a IPv6 address with a zone ID may incorrectly satisfy a URI name constraint that applies to the certificate chain. Certificates containing URIs are not permitted in the web PKI, so this only affects users of private PKIs which make use of URIs. Affected range <1.22.11 Fixed version 1.22.11 Description The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2. Affected range <1.22.12 Fixed version 1.22.12 Description Due to the usage of a variable time instruction in the assembly implementation of an internal function, a small number of bits of secret scalars are leaked on the ppc64le architecture. Due to the way this function is used, we do not believe this leakage is enough to allow recovery of the private key when P-256 is used in any well known protocols.

[github-actions]

Attempting automerge. See https://github.com/uniget-org/tools/actions/runs/13739471526.

[github-actions]

PR has unknown mergeable_state (unstable) and can not be merged. See https://github.com/uniget-org/tools/actions/runs/13739471526.