[ nostrfi/relay ] fix(deploy): pin the Caddy image to 2.11.9 by digest (#68)
The TLS overlay used the floating `caddy:2-alpine` tag, which only
updates when the host pulls again. A long-lived host could therefore keep
a Caddy older than 2.11.5, which leaks hop-by-hop headers on WebSocket
upgrades served over HTTP/2 or HTTP/3 (CVE-2026-55458). WebSocket upgrades
are most of the relay's traffic.
Pin `caddy:2.11.9-alpine` to its multi-arch index digest and document how
to re-pull and check the running version. The bundled proxy is Caddy, not
https://github.com/nostrfi/relay/commit/8e6abcb2942d40b03…
The TLS overlay used the floating `caddy:2-alpine` tag, which only
updates when the host pulls again. A long-lived host could therefore keep
a Caddy older than 2.11.5, which leaks hop-by-hop headers on WebSocket
upgrades served over HTTP/2 or HTTP/3 (CVE-2026-55458). WebSocket upgrades
are most of the relay's traffic.
Pin `caddy:2.11.9-alpine` to its multi-arch index digest and document how
to re-pull and check the running version. The bundled proxy is Caddy, not
https://github.com/nostrfi/relay/commit/8e6abcb2942d40b03…