Availability
GURDN is in release qualification
The product is built and tested, and it is not released. Until its release gate passes this page offers nothing to install, because a security tool handed out before it has been validated is the opposite of the point.
No downloadVersion 0.2.0 is a development version. It is not signed for release and has not completed validation on a clean Windows machine.
01Conditions
What has to be true before GURDN is offered here
These are the conditions the product checks itself. It refuses to describe a build as ready until all of them hold.
Built cleanly
From a clean checkout on a machine that can produce a release build, so what you install can be tied to source that can be reviewed.
Signed for release
Every binary signed by a certificate that a stranger’s machine will trust. Development signing does not count, and the gate does not accept it.
Digests published after signing
Signing rewrites the bytes, so the hashes offered beside a download are generated afterwards. A pre-signing hash beside a signed file is a mismatch you could not diagnose.
Installer validated
Install, repair, upgrade and uninstall each verified by reading the machine back rather than by trusting the installer’s own report.
Validated on a clean machine
A build that has only worked where it was developed has not been tested. That means Windows that has never had GURDN on it.
Live service checks
Service registration, the restricted endpoint, file permissions and the firewall changes confirmed on a real elevated Windows machine.
Update path proven both ways
A good package accepted, and a tampered, revoked, downgraded or unsigned one refused.
02Meanwhile
What you can read now
The architecture, the security model and the boundaries are documented, and they are the parts worth examining before any download exists.