-
v0.3.0
Stablereleased this
2026-10-31 09:20:36 +01:00 | 25 commits to main since this releaseThird release: working with a site's existing network services (DNS provider, fixed leases on
Kea and OpenWrt, NetBox device sync, Infoblox), Redfish across vendors with firmware updates,
UEFI Secure Boot, agents over HTTPS, and a security review of the whole code base. Upgrading:
rerundeploy/install.shon the region anddeploy/install-rack.shon rack hosts.Added
- Proxy DHCP: a VLAN in
proxymode (rollcall vlan add ... -proxy-dhcp, web UI,bootstrap.sh --proxy-dhcp) leaves addresses to the site's DHCP server and only answers PXE; machines keep DHCP
unless a static range is set aside; doctor and discover know the mode. - DNS provider:
dnsinconfig.jsonwrites machines' A/AAAA records into the site's DNS, through
the PowerDNS API (ownership by RRset comment) or RFC 2136 dynamic update with TSIG (ownership by a
_rollcall.<name>TXT marker and update prerequisites, so foreign records are never overwritten;
drift is detected by querying).rollcall dns,rollcall dns sync [-dry], a doctor check. - NetBox device sync (
ipam.device_sync): machines become dcim devices with serial, device type,
role, status, interfaces with MAC objects, assigned addresses and primary IP. Site, location and
rack are matched by name from the machine's location and never created; ownership by tag and
rollcall_machineas for addresses, foreign devices of the same name are conflicts. - Infoblox WAPI driver for the IPAM authority (
ipam.provider: infoblox): one host record per
address (DNS-published indns_view, or IPAM-only), ownership by therollcall_machineextensible
attribute (kept withextattrs+), leases, fixed addresses and ranges count as taken, delegated
networks by therollcallattribute. Not tested against a real grid yet. - The release workflow builds the tag's commissioning image on the PXE server and publishes it as
commissioning-*assets. - Lab NetBox (
lab/netbox/install.sh): a container on the lab segment for the NetBox drivers. - Fixed leases on the site's DHCP server for proxy-mode VLANs (
dhcp_reservations), for Kea with
host_cmds(Kea 3.0+) and OpenWrt (rpcd). Rollcall's own leases are reconciled; foreign ones are
reported.rollcall reservations. - Firmware updates over Redfish. A package repository on the region (
rollcall firmware import
from a file or URL, served to BMCs through rack controllers) and each machine's firmware inventory.- Update jobs: hand-over, task watch through BMC restarts, optional power cycle, version check
against the inventory. They resume after a region restart. - Vendor plans from documentation or vendor tools: Dell, HPE (
.fwpkgunpacked), Lenovo,
Supermicro, GIGABYTE/AMI/ASRock Rack, OpenBMC, xFusion, KAYTUS, Fujitsu iRMC. Cisco CIMC is
refused (SCP only). fw_method,fw_paramsandfirmware_baseon the BMC record.- CLI
rollcall firmware, a Firmware tab and repository in the web UI.
- Update jobs: hand-over, task watch through BMC restarts, optional power cycle, version check
- Redfish vendor profiles: one standard driver plus per-vendor behaviour from public documentation,
for Dell iDRAC, HPE iLO, Lenovo XCC, Supermicro, xFusion/Huawei iBMC, KAYTUS/Inspur, Fujitsu iRMC,
Cisco CIMC, GIGABYTE, ASRock Rack, OpenBMC and AMI MegaRAC.- Boot mode kept, omitted or tried per vendor.
- If-Match with 412/428 handling; future-state (
/SD) and@Redfish.Settingstargets. - Busy retries and task following.
- Chassis reset fallback and an emulated power cycle.
- Session login (
auth=session). - Probe results (reset types, boot targets, boot mode, profile) are kept on the BMC and shown in
the UI, and the UI's driver list comes from the server.
Security
A review of the whole code base; the fixes below. Upgrading: rerun
deploy/install.shon the
region anddeploy/install-rack.shon rack hosts (new dnsmasq layout, signed rack updates).- Root SSH keys in published images.
agent/build-image.shtook
the build user'sauthorized_keysunless told otherwise, so the images published with v0.2.0 and
v0.2.1 let three lab keys (the maintainer's laptop, the CI deploy key, the lab hypervisor) log in as
root to machines while they commission. Keys are now opt-in (AUTHKEYS=, the lab deploy sets it),
and the release workflow builds the image of the tag itself and refuses one withauthorized_keys. - Region file read (critical). A rack controller could read any file on the region (CA key,
config) through/api/v1/rack/binary?arch=../...archis now a known architecture. - Path traversal. In
/api/v1/render/...(admin) as well. - Machine-reported MACs. A MAC could be a path, letting a PXE-booting host make the rack write
outside the TFTP directory. Only real hardware addresses are accepted. Rack controllers write only
01-xx-..file names. - Delegated intermediates. An ACME intermediate could mint admin or rack certificates (name
constraints do not cover the CN), and IP addresses when only a domain was permitted.- Admin and rack identities must now be signed by the root itself.
- Intermediates carry a ServerAuth-only EKU, and the unconstrained name type is closed.
- Rack certificates. These were ServerAuth certificates for any address the rack reported, so
one rack could pose as the region.- They are now client-only with no names.
- Racks accept only the region's own certificate.
rack joinchecks the returned CA against the fingerprint in the code.- An unbound join code cannot take over an existing rack's name.
- Job results are accepted only from the rack that took the job.
- Rack self-update. The root unit ran a binary the unprivileged rack user staged.
- The region now signs each binary with its CA key.
- The root unit verifies the signature against the CA from
rack join, in a root-owned directory,
without following links.
- dnsmasq as root. dnsmasq (root) read configuration the rollcall user writes, and the reload
script copied files through links in rollcall's directory.- It now reads a checked copy in
/var/lib/rollcall-dnsmasq. - The copy may hold only the options Rollcall generates: nothing that runs a program or includes
a file.
- It now reads a checked copy in
- Machine record takeover. Any host on the provisioning network could overwrite a deployed
machine's record (and BMC) by reporting its UUID.- Known machines are re-commissioned only when
ready,recommissionor failed. - A MAC another machine owns keeps its boot file.
- The rack controller of a ready machine is not changed by whoever reports it.
- Known machines are re-commissioned only when
- Injection into dnsmasq, cloud-init, PXE menus, udev rules and DNS updates. Subnet domain and
gateway, host names, NIC names, reservation names and machine-reported identity strings are now
validated or reduced to one line. Machine IDs are letters and digits only. - Web UI.
- Escaping is fixed for machine-reported inventory fields (stored XSS).
- A Content-Security-Policy,
frame-ancestors 'none', nosniff and no-referrer are set. - Cross-origin state-changing requests are refused (
http.CrossOriginProtection), so a page
elsewhere cannot use a browser's admin certificate. ?token=is no longer logged.
- Deploy agent.
- The image URL no longer goes into a shell command; the checksum is taken over the bytes written.
- Seed files cannot leave the target root.
- 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, andscheme://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-Forentry counts. A machine without a fixed address binds a job to its first user.
agent_source_check: falseturns this off. - Agents over HTTPS. Rack controllers get a server certificate for their own host and serve
the agents' endpoints and images on 443. Agents accept the CA by the fingerprint on the PXE
command line and do not fall back to HTTP. Old agents keep working over HTTP. The commissioning
image has to be rebuilt to get the new agents.- The stateless overlay client works the same way (rebuild stateless images).
- UEFI and Secure Boot. UEFI machines PXE-boot through Debian's signed shim and GRUB, so machines
with Secure Boot on can boot at all; before, the firmware refused the unsignedsyslinux.efi.- GRUB menus are made from the pxelinux ones.
- The local disk is booted by chainloading the installed OS's signed loader.
- Secure Boot verifies the kernel; the initrd and squashfs are not covered.
- 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-hintno 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, androllcall rack renewrenews on demand. - Defaults and limits.
admin_httpdefaults toloopback.- Request bodies are capped (commissioning 4 MB, all 16 MB), with read and idle timeouts.
bootstrap.shandpublish-image.shkeep the database password and API tokens off command
lines.
Fixed
- IPAM: a reconcile running during an allocation could delete the record just reserved in NetBox.
- IPAM and DNS sync: one failing record no longer stops the rest of the pass, deletes included.
Reservations are stored in one spelling. - The job watchdog could fail a job that had just started.
- Release without
-diskwiped the smallest disk, not the one the OS was deployed to. Automatic
disk choice skips SAN LUNs (iSCSI, FC, SRP). - RFC 2136 lookups follow the request context. The marker is not removed when the database cannot
say whether other records need it. - Smaller fixes:
seqin templates is capped.- Layout selector
ib:-1no longer panics. - Redfish detection no longer runs on a machine that cannot be read.
- dnsmasq busy loop in proxy mode (a dnsmasq bug with tagged proxy ranges, found with gdb): proxy
ranges are untagged, PXE services limited by interface;dhcp-boot/dhcp-matchonly for served
subnets, nodhcp-hostlines for proxied ones.
Commits: v0.2.1...v0.3.0
- Release 0.3.0
- Release builds the tag's commissioning image, without SSH keys
- Infoblox WAPI driver for the IPAM authority
- INSTALL: point at NetBox device sync and the lab NetBox
- Location changes kick the IPAM reconcile
- rollcall ipam sync: print the device report
- Device sync: v6 primary IP, DMI placeholders, CLI report
- NetBox device sync; lab NetBox container
- docs: fixed leases on the site's DHCP server
- Kea: reservations in memory when there is no hosts database
- DHCP reservations on the site's DHCP server: Kea and OpenWrt
- GRUB keeps the firmware's text console; phone-home back to HTTP
- GRUB local boot chainloads the disk's signed loader; image sums
- UEFI PXE through signed shim and GRUB (Secure Boot)
- CHANGELOG: stateless overlays and phone-home over HTTPS [image]
- gofmt rackctl.go
- HTTPS for stateless overlays and phone-home
- docs: agents over HTTPS
- CD: ship all of deploy/ and agent/
- Agents over HTTPS: rack server certificates, fingerprinted CA
- docs: BMC certificate pinning
- Power: say why a BMC command failed (CLI, UI); certificate changes are events
- BMC certificates pinned on first use (Redfish, Proxmox)
- CHANGELOG: token binding, BMC hints, rack renewal
- Machine tokens only from the machine's own address
- BMC hints: the password stays on the region
- Rack certificate renewal: rack-owned state, atomic, grace period
- Firmware: docs; lab emulator keeps state (StateDirectory)
- Firmware updates over Redfish, per vendor
- rack update: work directory on /var/lib (/run is noexec)
- Redfish vendor profiles from public documentation
- Security review: fix traversal, identity, injection and takeover paths
- License under GPLv3
- DNS provider: PowerDNS API and RFC 2136 with TSIG
- Upstream report for the dnsmasq proxy-DHCP busy loop (report, reproducer, patch)
- Proxy DHCP for networks whose DHCP server stays in charge
- INSTALL: example release v0.2.1
Downloads
- Proxy DHCP: a VLAN in