Skip to content

New package: RedEyeNetworks.LogivoreForVeeam version 0.12.1#374866

Closed
beadams987 wants to merge 3 commits into
microsoft:masterfrom
beadams987:RedEyeNetworks.LogivoreForVeeam-0.12.1-20260515031323
Closed

New package: RedEyeNetworks.LogivoreForVeeam version 0.12.1#374866
beadams987 wants to merge 3 commits into
microsoft:masterfrom
beadams987:RedEyeNetworks.LogivoreForVeeam-0.12.1-20260515031323

Conversation

@beadams987
Copy link
Copy Markdown
Contributor

@beadams987 beadams987 commented May 15, 2026

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 stamping 0.10.2-rc.1 into its assembly version (a SemVer-stamping bug fixed in redeyenetworks/logivore PR #268 / commit d9e567f, included in v0.12.1). With the version-stamping fix in place, the installed package now displays the correct 0.12.1 version, 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 base RedEyeNetworks.Logivore package 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.md for 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.yml reusable workflow — verdict-link section is appended to each GitHub Release body.

Microsoft Reviewers: Open in CodeFlow

@wingetbot
Copy link
Copy Markdown
Collaborator

Validation Pipeline Run WinGetSvc-Validation-142-374866-20260515-1

@wingetbot wingetbot added New-Package Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. Validation-Completed Validation passed labels May 15, 2026
@microsoft-github-policy-service microsoft-github-policy-service Bot enabled auto-merge (squash) May 15, 2026 04:34
@beadams987
Copy link
Copy Markdown
Contributor Author

Closing — superseded by #374962 (New package: RedEyeNetworks.LogivoreForVeeam version 0.12.3), which carries the corrected version-stamping fix. See #374865 for the same context on the Base SKU.

@beadams987 beadams987 closed this May 15, 2026
auto-merge was automatically disabled May 15, 2026 08:24

Pull request was closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Azure-Pipeline-Passed Validation pipeline passed. There may still be manual validation requirements. New-Package Validation-Completed Validation passed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants