From 74922f7491c5dfb64a75746a14a736c5284902a1 Mon Sep 17 00:00:00 2001 From: Ilker Manap Date: Thu, 29 Oct 2026 22:42:42 +0100 Subject: [PATCH] docs: BMC certificate pinning Co-Authored-By: Claude Opus 5.5 --- CHANGELOG.md | 3 +++ README.md | 13 +++++++++++++ 2 files changed, 16 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index 2f3bac8..479f56c 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -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`. diff --git a/README.md b/README.md index 3255c93..15ff537 100644 --- a/README.md +++ b/README.md @@ -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.