| Name | Modified | Size | Downloads / Week |
|---|---|---|---|
| Parent folder | |||
| NetSentinel.exe | 2026-11-01 | 81.6 MB | |
| NetSentinel.exe.sha256 | 2026-11-01 | 83 Bytes | |
| NetSentinel.exe.sig | 2026-11-01 | 215 Bytes | |
| NetSentinel v1.10.0 source code.tar.gz | 2026-11-01 | 1.0 MB | |
| NetSentinel v1.10.0 source code.zip | 2026-11-01 | 1.1 MB | |
| README.md | 2026-11-01 | 1.7 kB | |
| Totals: 6 Items | 83.7 MB | 0 | |
2169 unit tests plus 14 integration checks. Earlier versions have no updater, so moving to this one is a manual download, the last one; later releases install from the Update button.
- One-click updates. NetSentinel asks GitHub for a newer release at start and once a day, sending only its version (Settings → Updates turns this off). An Update button then appears in the status bar, with the release notes. Install and restart:
- checks the release's signed manifest (Ed25519, against a key built in);
- downloads the exe and checks its SHA-256 against the signed one, and
against the published
.sha256; - hands over to the new exe, which waits for this one to exit, puts itself in
place (the old one is kept as
NetSentinel.exe.olduntil the next start) and starts with the same arguments, monitoring if it was.
A signature that does not verify, a version older than the running one, or a download that is not the signed file installs nothing. Run from source, NetSentinel only says a new version is out. The browser dashboard shows the new version but cannot install it.
- Releases are signed for the updater:
tools/sign_release.py, run by the release workflow with theNETSENTINEL_SIGNING_KEYsecret. A tag built without the secret fails rather than ship a release the updater cannot check.
Installing. Install Npcap first (tick "WinPcap API-compatible
mode"), then run NetSentinel.exe. It asks for administrator rights because packet
capture needs them. NetSentinel.exe.sha256 holds the checksum to verify the download,
and NetSentinel.exe.sig the signature the built-in updater checks before installing.