From d1d898993f732ec1ff765c4b87ce4de2d98c3000 Mon Sep 17 00:00:00 2001 From: Vishal Rana Date: Sun, 8 Nov 2026 07:17:48 -0800 Subject: [PATCH] docs(tls): warn against sharing a probe certificate CA across hosts The health-check guidance suggests issuing the probe certificate from the Authenticated Origin Pulls CA. When several hosts trust that CA, a stolen probe key passes the client certificate check on all of them, so point those deployments at a private CA per host. --- site/src/content/docs/docs/guides/tls.mdx | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/site/src/content/docs/docs/guides/tls.mdx b/site/src/content/docs/docs/guides/tls.mdx index dee85d84..8f088bf8 100644 --- a/site/src/content/docs/docs/guides/tls.mdx +++ b/site/src/content/docs/docs/guides/tls.mdx @@ -74,11 +74,17 @@ export FANOUT_HEALTHCHECK_CERT_FILE=/etc/fanout/tls/healthcheck.pem export FANOUT_HEALTHCHECK_KEY_FILE=/etc/fanout/tls/healthcheck-key.pem ``` -If you uploaded your own CA's certificate for Authenticated Origin Pulls, issue -the probe certificate from that same CA; the bundle already trusts it. -Otherwise, issue it from a private CA you control and append that CA to the -bundle. Keep any CA you append dedicated to Fanout clients: the listener -accepts every certificate it issues. +Issue the probe certificate from a private CA used only by this host, and append +that CA to this host's `FANOUT_TLS_CLIENT_CA_FILE` bundle next to your +Authenticated Origin Pulls CA. Keep any CA you append dedicated to Fanout +clients: the listener accepts every certificate it issues. Reusing the +Authenticated Origin Pulls CA for the probe is acceptable only if this is the +sole host that trusts it. + +:::caution +A probe key from a CA that several hosts trust would pass the client certificate +check on all of them. +::: The probe presents the pair only on its derived HTTPS check of `FANOUT_ADDR`; an explicit `fanout healthcheck ` does not. Both settings need