CHANGELOG: token binding, BMC hints, rack renewal
CI / agent (push) Successful in 3s
CI / site (push) Successful in 2s
CI / go (push) Successful in 40s

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:29:19 +01:00
1 parent dc093391a5
commit 24730d03d1
1 file changed
+9
+9
View File
@@ -83,6 +83,15 @@ region and `deploy/install-rack.sh` on rack hosts (new dnsmasq layout, signed ra
- The BMC password is not kept in the fallback inventory file.
- **Redfish.** Requests stay on the BMC and under `/redfish/`: paths the BMC returns cannot send the
credentials elsewhere, and `scheme://` addresses are reduced to scheme and host.
- **Machine tokens.** Job and node tokens are readable from the TFTP pxelinux files. They are now
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 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`.
Renewed certificates now go atomically to `/var/lib/rollcall/rack-cert`, the previous serial is
accepted for 7 days after a renewal, and `rollcall rack renew` renews on demand.
- **Defaults and limits.**
- `admin_http` defaults to `loopback`.
- Request bodies are capped (commissioning 4 MB, all 16 MB), with read and idle timeouts.