New package: RedEyeNetworks.LogivoreForVeeam version 0.12.1#374866
Closed
beadams987 wants to merge 3 commits into
Closed
New package: RedEyeNetworks.LogivoreForVeeam version 0.12.1#374866beadams987 wants to merge 3 commits into
beadams987 wants to merge 3 commits into
Conversation
Collaborator
|
Validation Pipeline Run WinGetSvc-Validation-142-374866-20260515-1 |
Contributor
Author
auto-merge was automatically disabled
May 15, 2026 08:24
Pull request was closed
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.
Logivore for Veeam v0.12.1 — first stable submission of the Veeam-centric SKU, separated from the base Logivore package per the v0.11.0 SKU split.
The previous
New package:PR (#373316, v0.11.0) was closed as stale because the v0.11.0 build was incorrectly stamping0.10.2-rc.1into its assembly version (a SemVer-stamping bug fixed in redeyenetworks/logivore PR #268 / commitd9e567f, included in v0.12.1). With the version-stamping fix in place, the installed package now displays the correct0.12.1version, matching the manifest.LogivoreForVeeam ships as a distinct WinGet package (
RedEyeNetworks.LogivoreForVeeam) with its own settings folder (%APPDATA%\LogivoreForVeeam\), credential namespace (LogivoreForVeeam:), install directory, and Argus appcast endpoint (/v1/appcast/logivore-for-veeam) so it can coexist with the baseRedEyeNetworks.Logivorepackage on the same machine. Distinct Inno Setup AppIds (B7A2E4C1 for Base, D9F2A8B3 for Veeam) per the Microsoft moderator guidance from #373316.Mirror of the base RedEyeNetworks.Logivore 4-installer shape (user-scope + machine-scope × x64 + arm64), each Inno Setup EXE wrapped around a multi-file self-contained .NET 9 publish that includes Microsoft.PowerShell.SDK for the Advanced Veeam Mode runspace. Multi-file shape (PowerToys / Notepad++ pattern) defeats the packed-binary ML signature on PAN WildFire that has been quarantining the Base SKU's monolithic EXE on Cortex XDR endpoints — extra-important for the Veeam SKU because it embeds the PSH SDK at ~200 MB total.
The driver for splitting the SKU in the first place was Cortex XDR / CrowdStrike behavioral-detection on the embedded PowerShell SDK + self-extract + auto-launch combo; isolating the higher-risk shape to the ~5% Veeam audience keeps the Base ~80 MB SKU clean for the ~95% audience that doesn't need PSH. See redeyenetworks/logivore
docs/edr-reputation-playbook.mdfor the full rationale.Azure Trusted Signing on every binary (12 EXEs: 4 portable + 4 user-scope + 4 machine-scope across Base + Veeam × x64 + arm64).
Pre-submitted to VirusTotal, WildFire (PAN), and Hybrid Analysis (CrowdStrike-owned) on every stable tag via redeyenetworks/Argus's
release-malware-submission.ymlreusable workflow — verdict-link section is appended to each GitHub Release body.Microsoft Reviewers: Open in CodeFlow