Blueforce-Linux/config/systemd/blueforce-enroll.service
emirhanmamak-blueforce ef102b9657 feat(field-os): provisioning layer, real ISO build, offline contracts
Adds the Blueforce Field OS provisioning stack on top of the existing fleet
architecture, without rewriting the working systems (installer, diagnostics,
Ansible, WireGuard/SSH/xRDP/RustDesk, Docker policies, monitoring, Docusaurus).

ISO build (the previous builder was a skeleton that produced no medium):
- boot layout is read from the base ISO at build time via
  `xorriso -report_el_torito as_mkisofs` and rebuilt with `-as mkisofs`;
  `-boot_image any replay` cannot work on Ubuntu live ISOs because the GRUB2
  MBR lives in the source image's first 16 sectors and the EFI system partition
  is an appended partition, neither of which is a file in the ISO9660 tree
- preflight now asserts El Torito boot metadata positively: xorriso exits 0 on
  a non-ISO input, which previously let an arbitrary file pass --check
- artifact produced and verified: dist/Blueforce-Field-OS-1.0.0-amd64.iso,
  6 481 917 952 bytes, SHA256 cb0cc56f...d431296, BIOS+UEFI entries preserved,
  /autoinstall.yaml at the media root, casper/minimal.squashfs byte-identical
  to the base
- recorded baseline deviation: the verified medium on the build host is the
  Desktop flavour, so the manifest carries a baseline_deviation block instead
  of hiding it; Server remains one flag away

Offline and identity:
- offline APT contract with concrete package requirements, pin format and an
  audit table; builds fail closed while pins are UNPINNED
- autoinstall keeps interactive-sections: [storage]: the operator confirms the
  target disk, and no automatic wipe is ever performed
- firstboot terminal wizard for the 8-digit dealer id, three-state lifecycle
  (PROVISIONED_OFFLINE -> ENROLLED -> READY) with fail-closed gates, so a
  missing internet link or WireGuard handshake cannot fail provisioning but can
  never produce a false READY

Fleet and migration:
- five read-only Ansible playbooks for Field OS version, provisioning,
  enrollment, remote channels and offline readiness, all wave-scoped with a
  separate production override
- Windows pre-migration inventory and data export extended to the full brief
  scope, read-only, never collecting credentials

Tests: tests/run-all.sh -> 8/8 pass, exit 0. Boot acceptance (UEFI, Legacy
BIOS, Secure Boot), air-gapped install, real enrollment endpoint and Windows
rollback remain LAB work and are listed in IMPLEMENTATION-REPORT.md.
2026-09-16 11:14:42 +03:00

45 lines
2.1 KiB
Desktop File

# Blueforce enrollment controlled attempt: PROVISIONED_OFFLINE -> ENROLLED.
#
# Behaviour (docs/29-DEVICE-ENROLLMENT.md, provisioning/enrollment/README.md):
# * One bounded attempt per start. The unit never reboots the device and never
# loops: a device without internet or without a staged token prints PENDING,
# exits 0 and stays PROVISIONED_OFFLINE.
# * When a one-time token has been staged (bf-enroll --token-stdin --stage,
# mode 0600, TTL bounded) the attempt enrolls by itself as soon as central is
# reachable. RestartSec plus the StartLimit below cap that at six attempts
# per hour and then leave the cadence to blueforce-enroll.timer, so a device
# that stays offline for weeks is never hammered.
# * No credential lives in this unit: bf-enroll reads the staged root-only
# token once and deletes it on success or on a definitive rejection.
# * Restart= is on-failure only, so a successful run, a READY device and an
# unprovisioned device are never retried.
# * Trigger: blueforce-enroll.timer (OnBootSec=10min, then daily). An operator
# can also run `bf-enroll-now` interactively at any time.
[Unit]
Description=Blueforce enrollment controlled attempt (bounded retries, never reboots)
After=network-online.target
Wants=network-online.target
StartLimitIntervalSec=1h
StartLimitBurst=6
[Service]
Type=exec
# Central control plane endpoint and timing, delivered by central configuration.
# Optional on purpose: the attempt reports PENDING when it is not configured yet.
EnvironmentFile=-/etc/blueforce/enrollment.env
ExecStart=/usr/local/bin/bf-enroll --systemd
# Bounded retry: enough to join automatically when connectivity returns, never
# aggressive while the device is offline (systemd holds the next attempt for
# RestartSec instead of spinning).
Restart=on-failure
RestartSec=5min
TimeoutStartSec=180
User=root
UMask=0077
NoNewPrivileges=yes
PrivateTmp=yes
ProtectSystem=strict
ProtectHome=yes
# Writable paths only: lifecycle state plus staged token, WireGuard configuration
# (including the wg-quick enable symlink) and central configuration.
ReadWritePaths=/var/lib/blueforce /etc/wireguard /etc/blueforce /etc/systemd/system