Repository navigation
v3.81.0: Verified agent enrollment and customer-side rollout checks - #21
Merged
Merged
Conversation
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.ymlbuilds the OPNsense agent fromplugin/os-opnmanager-agent/(twice, bytes must match), signs a release record with the key pinned inconfig/agent_release_keys.pub, verifies it as a clean manager would, and attaches both files to the release.scripts/stage_agent_package.phpdownloads and verifies the package (--importfor offline managers,--build-local,--status). Missing, corrupted, tampered, untrusted, wrong-version, pfSense and too-new packages are each refused with a fix.OPNMGR_AGENT_SHA256. The installer verifies before changing anything on the firewall.Customer-side checks on update rings
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.schema.sqlregenerated.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.phpright after deploying.🤖 Generated with Claude Code