Skip to content

v3.81.0: Verified agent enrollment and customer-side rollout checks - #21

Merged
agit8or1 merged 1 commit into
mainfrom
feature/3.81.0-enrollment-client-checks
Nov 10, 2026
Merged

agit8or1 merged 1 commit into
mainfrom
feature/3.81.0-enrollment-client-checks

Conversation

@agit8or1

Copy link
Copy Markdown
Owner

Clean-install enrollment

A fresh clone had no agent package (downloads/ is gitignored) yet showed the install command, which then failed on the firewall with a 404.

  • release.yml builds the OPNsense agent from plugin/os-opnmanager-agent/ (twice, bytes must match), signs a release record with the key pinned in config/agent_release_keys.pub, verifies it as a clean manager would, and attaches both files to the release.
  • scripts/stage_agent_package.php downloads and verifies the package (--import for offline managers, --build-local, --status). Missing, corrupted, tampered, untrusted, wrong-version, pfSense and too-new packages are each refused with a fix.
  • Install commands are shown only for a verified, staged package and carry OPNMGR_AGENT_SHA256. The installer verifies before changing anything on the firewall.
  • Packages are never replaced. A pre-3.81.0 package is adopted only if it is byte-identical to the source build.

Customer-side checks on update rings

  • Tenant-scoped probes (tools/opnmgr-probe, a standalone Python script, or Rem0te running it) run three narrow checks: internal DNS, TCP across the VPN, HTTPS to a public host.
  • Per-campaign opt-in, off by default. A required check that fails or goes stale holds the next ring and the second CARP member, and the campaign names the failing path. Manual progression stays, with an audited override.
  • Migration 0035; schema.sql regenerated.

Testing

No OPNsense device was used. The clean manager → first firewall test is real up to the installer, which runs in verify-only mode. The rollout scenarios (healthy, offline probe, failed client path, CARP pair) use DB fixtures. The probe end-to-end test runs the real probe against a local manager.

Upgrade note: run php scripts/stage_agent_package.php right after deploying.

🤖 Generated with Claude Code

Clean-install enrollment
- The release workflow builds the OPNsense agent from plugin/os-opnmanager-agent/
  (twice, bytes must match), signs a release record with the project key pinned
  in config/agent_release_keys.pub, and attaches both to the GitHub release.
- scripts/stage_agent_package.php verifies and stages the matching package:
  download, --import (offline), --build-local, --status; a pre-3.81.0 package is
  adopted only if byte-identical to the tracked source. Nothing is replaced.
- Settings, Add Firewall and the reinstall panel show an install command only for
  a verified, staged package, otherwise the reason and the fix. Add Firewall can
  stage an uploaded package + record. Commands carry OPNMGR_AGENT_SHA256 and the
  installer verifies before changing anything (OPNMGR_VERIFY_ONLY=1 to stop there).

Customer-side checks on update rings
- Tenant-scoped probes (tools/opnmgr-probe, standalone Python, or Rem0te running
  it) test internal DNS, TCP to a private address across the VPN and HTTPS to a
  public host; nothing else.
- Campaigns opt in (default off). A required check that fails or goes stale holds
  the next ring and the second CARP member; the campaign names the failing path.
  Manual progression stays, with an audited override reason.
- Migration 0035; schema.sql regenerated.

Tests: agent_release_staging, clean_install_enrollment, customer_checks,
customer_probe_e2e, probe unit tests. No OPNsense device was used.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@agit8or1
agit8or1 merged commit 1816e5c into main Nov 10, 2026
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants