docs: BMC certificate pinning
CI / agent (push) Successful in 2s
CI / site (push) Successful in 2s
CI / go (push) Successful in 39s

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Ilker ManapandClaude Opus 5.5 committed 2026-10-29 22:42:42 +01:00
1 parent d0ea29d2a9
commit 74922f7491
2 files changed
+16

No files matched your search

+3
View File
@@ -87,6 +87,9 @@ region and `deploy/install-rack.sh` on rack hosts (new dnsmasq layout, signed ra
accepted only from the machine's own address (its static lease); through a rack, the rack's
`X-Forwarded-For` entry counts. A machine without a fixed address binds a job to its first user.
`agent_source_check: false` turns this off.
- **BMC certificates.** HTTPS BMCs (Redfish, Proxmox) are pinned on first use. The certificate
is read in a handshake that carries no credentials, and a changed certificate gets none
(`tls_fingerprint`; cleared on an address change or a BMC firmware update by Rollcall).
- **BMC hints.** `bmc-hint` no longer returns the password. The region attaches the configured
credentials itself and checks the BMC from the rack controller.
- **Rack certificate renewal.** Renewal could not overwrite the root-owned files from `rack join`.
+13
View File
@@ -556,6 +556,19 @@ Every profile is tested against a fake service that behaves as its sources
describe (`redfish_test.go`). The profiles have not yet run against the real
machines.
**HTTPS BMCs (Redfish, Proxmox) are trusted by their certificate.** Before
credentials first go to such a BMC, the rack controller reads its
certificate with a TLS handshake that sends nothing. The region pins the
SHA-256 on the BMC record as `extra tls_fingerprint`. A later connection
showing a different certificate sends no credentials: the command fails
with both fingerprints, and the machine gets the event
`bmc certificate changed`.
To trust a replaced BMC, clear the pin with `rollcall bmc ID -set
tls_fingerprint=`. Changing the address does the same, and so does a BMC
firmware update run by Rollcall. To check against the system's CAs
instead, set `verify_tls=true`.
After commissioning, a BMC still on IPMI is asked whether it speaks Redfish
with the same account; if it does, the driver for its vendor takes over
(event `bmc driver`). An operator's choice is never overridden.