Shkarko SysManager 1.136.164

[1.136.164] - 2026-11-10
File Shredder refuses files on network shares, and removes only the file it overwrote.
Security
- The refusal of Windows' own folders compared paths in their drive-letter form, and a path through a network share
kept its share form at every step, so \\localhost\C$\Program Files\..., this PC's own folders under another name,
passed it. A file on a network share is now refused before the share is reached, and again when the path, or the
file the overwrite holds open, turns out to lead to one through a link or a mapped drive. An overwrite sent over the
network is not a secure one anyway: the computer that holds the share decides where it lands and can keep copies.
- The overwrite holds one exclusive handle from the check of what it opened to the truncate, and the file was then
deleted by its name once that handle had closed, so the delete acted on whatever the path led to by then. The
file's named streams are now overwritten while that handle is still held, and the file is removed through a handle
checked to be open on the file that was overwritten. When the name leads to another file, nothing is removed, and
the tab says the contents were overwritten and the name stayed.
Verify the download
Get-FileHash .\SysManager-v1.136.164.exe -Algorithm SHA256
Expected SHA256: 136E66A887DD0DCAFB871146E80456C5D437508C56CD866CBD8280DC8C752EA8
This build is not code-signed, so Windows will warn on first launch. That is
expected for a small independent app: see what the warning says and what to
click.
Code signing is planned through the SignPath Foundation,
which provides free certificates to open-source projects, with signing performed by
SignPath.io. Until then, the SHA256 above and the build
attestation below are what establish that a download is the genuine build.
Code signing policy
This release is not code-signed. The team roles, release-approval process and
privacy policy required by the SignPath Foundation programme
are documented in advance under Code signing
policy. That
documentation is a prerequisite for applying, not evidence of a certificate. The
attribution line naming SignPath as the signing provider will appear here once a
certificate is actually issued.
This program will not transfer any information to other networked systems unless
specifically requested by the user or the person installing or operating it. Two checks
run on their own when SysManager starts: the version check against the GitHub Releases
API, at most once a day, and the Dashboard's app-updates alert, which asks winget. The
About tab can switch off either. Everything else that uses the network runs only when you
use it. Full
privacy policy.
Verify where this binary came from
This exe was built by GitHub Actions from this public source, and the build is
recorded in the Sigstore public transparency log. With the
GitHub CLI:
gh attestation verify .\SysManager-v1.136.164.exe --repo laurentiu021/SystemManager
That proves which commit and workflow produced this exact binary, something the
SHA256 file cannot show, since it is published alongside the exe it describes.
Each release also ships SysManager-v1.136.164.sbom.json, a CycloneDX inventory of
every dependency resolved for this build, and THIRD-PARTY-NOTICES.txt, the
licenses and notices of the open-source components the exe carries, which About
also opens from the exe itself.