NSClient++ 0.24.1 ڈاؤن لوڈ

# NSCANgClient leaves the Windows installer after antivirus detections

0.24.1 is a small follow-up to 0.24.0 with one change: the Windows installer
no longer ships `NSCANgClient`, because a few antivirus engines report its DLL
as malware and made the whole MSI look infected. The module is still in the
Windows zip, still signed, and is copied into place by hand.

This release is **only a workaround** for what are most likely false positives,
not a fix: the module's code is the same as in 0.24.0, and nothing else
changed. **If you use `NSCANgClient` on Windows, stay on (or install) the
0.24.0 build instead**, which still ships the module in the installer.

## ✨ Highlights

- ⚠️ **Only a workaround: `NSCANgClient` users should use 0.24.0.** 0.24.1
changes nothing but the packaging of this one module. If you submit results
over NSCA-NG from Windows, the 0.24.0 installer gives you the same module
without the manual copy.

- 📦 **`NSCANgClient` is no longer in the Windows MSI.** Four antivirus engines
on VirusTotal flag `NSCANgClient.dll` from 0.24.0 with generic
machine-learning verdicts. Until the vendors have analysed it, the module
ships in the Windows zip only. Linux and macOS packages are unchanged. (#1615)
- 🔒 **A security notice on what the detections do and do not mean.** The
verdicts are likely false positives but unconfirmed, and the release's
signature, attestation and checksums show the file was not altered after the
build, not that the build itself was clean. The notice and FAQ 1.12 spell out
both.
- 🪟 **The DLL stays signed in the zip.** The signing list is read from the
installer sources, so leaving the module out of the MSI would have dropped it
from signing too; it is now kept on the list explicitly.

## ⚠️ Upgrade notes

- **Windows, `NSCANgClient` users: use 0.24.0 instead.** 0.24.1 is only a
workaround for the antivirus detections and has nothing else in it, so
staying on 0.24.0 keeps the module installed and managed by the MSI. If you
upgrade anyway: an MSI upgrade removes the copy an earlier
installer put there, and the service then logs that the module was not found.
Copy `modules\NSCANgClient.dll` from the matching zip into the `modules`
folder after upgrading, and again after every later upgrade: the installer
does not own a file copied this way, so it never replaces it. Check the file
first as FAQ 1.12 shows. Nothing to do if you do not use NSCA-NG on Windows,
or on Linux and macOS.

**Full Changelog**: https://github.com/mickem/nscp/compare/0.24.0...0.24.1