build: bump Go 1.26.10 + ca-certificates for eMudhra CA distrust

Why

The private keys of eight eMudhra intermediate CAs were disclosed as compromised (2026-10-20). Trust stores are distrusting them.

What

Toolchain / image / CI only — no consensus-affecting code.

  1. Runtime + tooling ca-certificates 20230311+deb12u1 -> 20250419~deb12u2 (bookworm-security, DLA-4845-1) in build/docker/Dockerfile and tools/events/Dockerfile. This is the load-bearing fix: it removes the eMudhra-chaining roots from the container trust store, and Go reads the OS trust store on Linux.
  2. Go 1.26.9 -> 1.26.10 across go.mod toolchain and all build/CI image refs (.gitlab-ci.yml, build/docker/Dockerfile, build/docker/cli/Dockerfile, ci/Dockerfile.{ci-tools,regtest,simtest}, tools/events/Dockerfile). Go 1.26.10 compiles in a crypto/x509 Verify-level block of the eight compromised intermediates, effective on rebuild — defense-in-depth for the thornode/bifrost binaries' own verification.

The pinned bookworm base (debian:bookworm-20260610-slim) pulls ca-certificates from the bookworm-security pocket at build time; if the pin fails to resolve in CI, the base digest will be bumped.

Targets the 3.21.1 release line for 3.21.1-rc2.

Draft until CI is green.

Merge request reports

Loading
Loading