step-ca: stop offering acme-ca, so public names are certified by public-acme #234

Merged

jschoubben merged 1 commits from fix/step-ca-is-not-the-public-acme-ca into main

2026-10-03 08:57:25 +00:00

Author	SHA1	Message	Date
jschoubben	0778f8f0ae	step-ca: stop offering acme-ca, so public names are certified by public-acme step-ca and public-acme both offered acme-ca on novox, and route-proxy's pin names a node, not a module — so which one certified the public names depended on provider order. After the controller restart on 2026-10-03 it came out as step-ca, and every public site served a certificate no browser trusts. step-ca's own names are already certified through internal-acme-ca; acme-ca is the public authority's alone.	2026-10-03 10:54:43 +02:00

Author

SHA1

Message

Date

jschoubben

0778f8f0ae

step-ca: stop offering acme-ca, so public names are certified by public-acme

step-ca and public-acme both offered acme-ca on novox, and route-proxy's pin names a node, not
a module — so which one certified the public names depended on provider order. After the
controller restart on 2026-10-03 it came out as step-ca, and every public site served a
certificate no browser trusts. step-ca's own names are already certified through
internal-acme-ca; acme-ca is the public authority's alone.

2026-10-03 10:54:43 +02:00