Skip to content

Release v4.0.13 - #533

Merged
Warhammer4000 merged 1 commit into
mainfrom
release/v4.0.13
Nov 17, 2026
Merged

Warhammer4000 merged 1 commit into
mainfrom
release/v4.0.13

Conversation

@Warhammer4000

@Warhammer4000 Warhammer4000 commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Merging this PR tags v4.0.13 on main and publishes the release with these notes from CHANGELOG.md.
Edit the notes by pushing to this branch before it merges.


Added

  • macOS: releases include sentinelgo-darwin-universal.pkg, a generic installer package for MDM (macOS release signing: Developer ID–signed, notarized agent binary and generic distribution .pkg #352). It holds one universal binary at /opt/sentinelgo/sentinelgo and no config.json (the agent enrolls from MDM managed preferences), and installs and starts the launchd job with sentinelgo -install. When the MACOS_INSTALLER_P12 secret holds a Developer ID Installer certificate, the package is signed, notarized and stapled, and listed in sentinelgo-installers.json for the backend's MDM mirror. Until then it ships unsigned and isn't listed, since MDM can't install it. CI builds and test-installs the package on every pull request.
  • YARA: rules can use the pe module (YARA: pe / elf / macho module support #419). Rules with import "pe" used to be skipped as unsupported_module:pe. They now compile and match Windows executables on headers, sections, imports, exports, imphash, Rich header, resources, version info and Authenticode signature metadata. An executable up to 64 MiB is read whole so fields at the end of the file (signatures, checksum) work. Larger ones stream, and those fields stay undefined. elf, macho and dotnet are still unsupported.
  • macOS: releases notarize the agent binaries with Apple (Apple Developer ID: certificates, notarization key and provisioning profile (step-by-step) #491). When the binaries are signed with a Developer ID certificate and the APPLE_NOTARY_KEY_P8, APPLE_NOTARY_KEY_ID and APPLE_NOTARY_ISSUER_ID secrets hold an App Store Connect API key, the release submits both binaries with notarytool after code signing. Developer ID signatures now carry Apple's secure timestamp, which notarization requires. If Apple rejects the binaries the release stops; if Apple doesn't answer within 30 minutes the release goes out signed, with a warning. Signatures from an internal CA are signed as before and not notarized.
  • YARA: scan summaries say why files weren't scanned and why a scan stopped (contract v1.2, YARA contract v1.2: scan report with skip/error reasons, end reason, scope, rule counts and problem files #497; capability yara_scan_report_v1). They now carry skips and errors by reason (too large, timed out, access denied, locked, listing failed, …), the end reason (time or file limit, cancelled, threat hunting turned off, worker failure, shutdown), the bytes read, the time paused for the CPU budget or battery, the scope (folders, exclusions, limits, ruleset revisions) and up to 200 problem files with the OS error text. In hashed path mode their paths are hashed like match paths. A stopped scheduled scan keeps the breakdown when it resumes. All fields are optional, so older servers ignore them.
  • YARA: a running scan reports its progress (YARA: scan_progress events while a scan runs #498). Scheduled and on-demand scans send a scan_progress event with the files scanned, skipped and failed so far, the matches, which folder of how many it is in and how long it has run, at most every 2 minutes. No paths are sent. Only the latest progress waits in the queue while the device is offline. The agent sends it only when the server's bundle asks for it, so older servers never receive it.
  • Updates: an upgrade rolls back on its own when the new version doesn't work (Self-update: keep the backup until the new binary is healthy, restore it from a watchdog #503). The agent keeps <exe>.backup and writes update_marker.json next to the config. Before replacing the binary, it starts a watchdog: a copy of the old binary running sentinelgo update-watchdog, as a transient systemd unit on Linux, in its own session on macOS, or as a detached process on Windows. If the watchdog can't start, the update doesn't go ahead. The new version starts its own watchdog if none is running, for example after a reboot. It is healthy once it has signed in and the server accepted its agent info, and then it deletes the marker and the backup. Confirming and rolling back share a lock, so only one of them happens. Otherwise, 10 minutes after its latest start or after more than 3 starts, the watchdog restores the backup and restarts the service. A new version that is running but offline, while the watchdog can't reach the server either, gets more time, for up to 24 hours. Every version rolled back on the device is skipped until the server offers another one. That holds even if the rollback record can't be written, and after 24 hours for an update that never stayed installed. The restored agent logs the rollback, so it shows up in the uploaded agent log, and the watchdog logs to update_watchdog.log. While an upgrade waits for its health check, the agent doesn't start another one. Server-approved downgrades (Self-update: downgrade when the server marks an older release as latest (emergency rollback) #505) aren't watched.
  • Updates: agents roll back to an older release when the console marks it as latest for an emergency rollback (Self-update: downgrade when the server marks an older release as latest (emergency rollback) #505). The server sets allow_downgrade on the get_latest_agent_release row only during an admin-initiated rollback. Without it an older release is still ignored, and equal versions never reinstall. The SHA-256 and signature checks still apply. Scheduled checks, the startup check and the agent-update task (push now) all follow this rule. The agent logs Rolling back: vA -> vB (server-approved downgrade).
  • Self-update: while an update waits for its health check, a boot job starts the update watchdog after a reboot (Self-update: a reboot during the health window leaves an early-crashing update with no watchdog #516): a systemd unit on Linux, a LaunchDaemon on macOS, a scheduled task on Windows. Before, the watchdog didn't survive a reboot, so an update that crashed before its health check started after a reboot was never rolled back. The boot job runs the watchdog copy of the previous release, never the new binary, and is removed once the update is confirmed healthy or rolled back. After a reboot the new binary gets a full 10 minutes to start; if it hasn't by then, the update is rolled back.
  • File DLP: the upload inspection status reports uploads to listed sites that the proxy couldn't inspect (File DLP upload proxy: report uploads it can't inspect, with a reason #527). files.deep_inspection.uninspectable_counts counts them by reason (tls_untrusted: an app refused the inspection certificate, so it pins certificates or doesn't trust the device CA; websocket: a WebSocket connection, relayed but not read; too_large: over max_file_bytes). uninspectable_hosts lists up to 20 hosts with reason, count and first/last time, the host only. Admins can now tell "inspected and clean" from "never inspected". They aren't sent as DLP events yet, because the server doesn't accept them.

Changed

  • YARA: the engine is go-yara v0.10.0 (was v0.9.0), and the status reports engine_version 0.10.0 (YARA: pe / elf / macho module support #419). The current YARA Forge core set (20261115) failed to compile as a whole on v0.9.0, because v0.9.0 rejects rules that use both base64 and base64wide. On v0.10.0, 5,051 of its 5,089 rules compile (99.3%).
  • Build: Go 1.27 or newer is required (go-yara v0.10.0 needs it), and CI lints with golangci-lint v2.15.0.
  • YARA: the scan skip cache and checkpoints are keyed by engine version too (YARA: pe / elf / macho module support #419). After this update, the first scheduled scan rescans files already found clean, so the newly enabled pe rules see them. It takes as long as a first scan.
  • macOS: code-signed agent binaries now use the identifier com.brainstation-23.sentinelgo, the App ID registered with Apple, instead of com.sentinelgo.agent (Apple Developer ID: certificates, notarization key and provisioning profile (step-by-step) #491). No release has been signed yet, so nothing on devices changes. The launchd label and the managed-preferences domain stay com.sentinelgo.agent.

Fixed

  • YARA: a Windows executable whose first bytes look like UTF-16 text is still typed executable.pe (YARA: pe / elf / macho module support #419), so pe rules see the whole file (signatures, checksum, resources) and the filetype external is right. This includes executables whose PE header starts past the first 8 KiB: the engine confirms those from the whole file (up to 64 MiB), whatever the ruleset imports. DLP evidence reports these files as executable.pe too, not text.utf16le.
  • YARA: an on-write report window belongs to the bundle that opened it (YARA contract v1.2: scan report with skip/error reasons, end reason, scope, rule counts and problem files #497). After an evidence-mode change (full to hashed paths), a scan that started under the old bundle no longer reopens an old window, and new files never land in a window with the old mode, so a hashed-mode summary never carries a plain path. The dropped result isn't stored in the skip cache either, so a match it found is reported by the next scan instead of being skipped.
  • YARA: scan_progress is sent at most every 2 minutes whatever the bundle asks (YARA: scan_progress events while a scan runs #498); a shorter interval_seconds was honoured down to 1 minute. Re-queuing a progress event that is still queued no longer moves it behind newer events, so the queue cap keeps dropping the oldest first.

Devin Review

@coderabbitai

coderabbitai Bot commented Nov 17, 2026

Copy link
Copy Markdown

Warning

Review limit reached

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Next included review available in 20 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: Repository UI (base), Organization UI (inherited)
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 5c58c41d-8478-45ad-b98a-f0c7ab7ac9ff
Commits

Reviewing files that changed from the base of the PR and between 3464180 and fc7ac1a.

Files selected for processing: 15

  • CHANGELOG.md
  • changelog.d/352-macos-pkg.added.md
  • changelog.d/419-go-yara-0-10.changed.md
  • changelog.d/419-pe-sniff-before-text.fixed.md
  • changelog.d/419-yara-pe-module.added.md
  • changelog.d/491-macos-notarization.added.md
  • changelog.d/491-macos-signing-identifier.changed.md
  • changelog.d/497-onwrite-window-owner.fixed.md
  • changelog.d/497-yara-scan-report.added.md
  • changelog.d/498-progress-interval-and-order.fixed.md
  • changelog.d/498-yara-scan-progress.added.md
  • changelog.d/503-update-health-rollback.added.md
  • changelog.d/505-server-approved-downgrade.added.md
  • changelog.d/516-boot-watchdog.added.md
  • changelog.d/527-uninspectable-uploads.added.md
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

Share

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Devin Review

@Warhammer4000
Warhammer4000 merged commit 1404181 into main Nov 17, 2026
23 checks passed
@Warhammer4000
Warhammer4000 deleted the release/v4.0.13 branch November 17, 2026 10:23
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.

1 participant