Repository navigation
Release v4.0.13 - #533
Merged
Merged
Release v4.0.13#533
Conversation
Warhammer4000
enabled auto-merge
November 17, 2026 10:18
|
Warning Review limit reachedYou'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. View limit details
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. |
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.
Merging this PR tags
v4.0.13onmainand publishes the release with these notes fromCHANGELOG.md.Edit the notes by pushing to this branch before it merges.
Added
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/sentinelgoand noconfig.json(the agent enrolls from MDM managed preferences), and installs and starts the launchd job withsentinelgo -install. When theMACOS_INSTALLER_P12secret holds a Developer ID Installer certificate, the package is signed, notarized and stapled, and listed insentinelgo-installers.jsonfor 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.pemodule (YARA: pe / elf / macho module support #419). Rules withimport "pe"used to be skipped asunsupported_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,machoanddotnetare still unsupported.APPLE_NOTARY_KEY_P8,APPLE_NOTARY_KEY_IDandAPPLE_NOTARY_ISSUER_IDsecrets hold an App Store Connect API key, the release submits both binaries withnotarytoolafter 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_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.scan_progressevent 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.<exe>.backupand writesupdate_marker.jsonnext to the config. Before replacing the binary, it starts a watchdog: a copy of the old binary runningsentinelgo 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 toupdate_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.allow_downgradeon theget_latest_agent_releaserow 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 theagent-updatetask (push now) all follow this rule. The agent logsRolling back: vA -> vB (server-approved downgrade).files.deep_inspection.uninspectable_countscounts 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: overmax_file_bytes).uninspectable_hostslists 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
engine_version0.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 bothbase64andbase64wide. On v0.10.0, 5,051 of its 5,089 rules compile (99.3%).perules see them. It takes as long as a first scan.com.brainstation-23.sentinelgo, the App ID registered with Apple, instead ofcom.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 staycom.sentinelgo.agent.Fixed
executable.pe(YARA: pe / elf / macho module support #419), soperules see the whole file (signatures, checksum, resources) and thefiletypeexternal 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 asexecutable.petoo, nottext.utf16le.scan_progressis sent at most every 2 minutes whatever the bundle asks (YARA: scan_progress events while a scan runs #498); a shorterinterval_secondswas 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.