Blueforce-Linux/config/wireguard/wg0.conf.example
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

24 lines
1.2 KiB
Text

# Purpose: Reference spoke config for field devices joining the hub.
# Scope: Peer name bf-<ID> with fixed tunnel IP; hub values come from inventory.
# Safety: Example only; replace every <REPLACE> placeholder before installing to /etc/wireguard/.
# Ref: docs/08-WIREGUARD-AND-NETWORK.md, K-05; peer naming K-12.
[Interface]
# Tunnel address from inventory (one fixed /32 per device, hub is 10.8.0.1).
Address = 10.8.0.15/32
# Device private key. <REPLACE> with the real key; never commit it.
PrivateKey = <REPLACE_DEVICE_PRIVATE_KEY>
# Open management ports on the tunnel interface when it comes up.
PostUp = ufw allow in on wg0 to any port 22 proto tcp; ufw allow in on wg0 to any port 3389 proto tcp
# Remove tunnel-scoped management rules when the tunnel goes down.
PostDown = ufw delete allow in on wg0 to any port 22 proto tcp; ufw delete allow in on wg0 to any port 3389 proto tcp
[Peer]
# Hub public key. <REPLACE> with the real hub key.
PublicKey = <REPLACE_HUB_PUBLIC_KEY>
# Hub endpoint. <REPLACE> with the real hub address.
Endpoint = <REPLACE_HUB_HOST>:51820
# Return traffic is limited to the tunnel subnet.
AllowedIPs = 10.8.0.0/16
# Keep the NAT/CGNAT mapping alive behind mobile networks.
PersistentKeepalive = 25