Antivirus/gui
dev c3417e5f75 0.1.5: say what Hound cannot see, and put the vault where it belongs
Every serious bug found in desktop testing had one shape: Hound
reporting success it had not achieved. A build script that said "built"
without building. A window showing "Protected" while its front-end had
failed to load. A rootkit check calling 988 processes hidden when it
was the one that had been blinded. A settings write refused while the
switch stayed where the user put it. A visible error is something a
person can act on; a false green is not.

`hound selfcheck` asks the question directly — what can this
installation not currently do? — and the daemon prints anything wrong
at startup rather than waiting for it to be inferred from behaviour.
The states are ok, degraded, and blind; the last is the one that
matters, because blind means a detector is running and cannot see. It
exits non-zero when blind, so it can be wired into monitoring.

It earned its place within a minute of existing, by reporting the vault
as /root/.local/share/hound/quarantine. The daemon runs as root, root
has a home directory, and the XDG rules therefore sent the system vault
into root's dotfiles — while the installer created and hardened
/var/lib/hound/vault, which sat empty, and the desktop app read the
user's own vault. Three vaults, none agreeing, which is exactly why the
Quarantine tab reported "vault is empty" beside two quarantined files.
Root now uses the system vault; an unprivileged daemon keeps its own,
since a developer running houndd by hand must not need /var/lib.

Also: `hound update` restarts the desktop app itself after installing.
The app can notice its own package being replaced, but only from the
version that learned how — updating from an older one leaves the stale
process showing the old front-end, which is indistinguishable from an
update that did nothing. The updater matches processes on the
executable rather than a command line anyone could imitate, and
relaunches each as its own owner with the session environment it was
already using: DISPLAY, Wayland socket and bus address are taken from
the running process, because guessing them breaks on Wayland or a
second seat.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
2026-08-21 12:52:17 -05:00
..
dist 0.1.4: settings apply when you change them, and the app reopens itself 2026-08-21 12:40:59 -05:00
src-tauri 0.1.5: say what Hound cannot see, and put the vault where it belongs 2026-08-21 12:52:17 -05:00
.gitignore Engine seam (ScanEngine trait) + Tauri GUI 2026-08-20 17:55:40 -05:00
package-lock.json 0.1.5: say what Hound cannot see, and put the vault where it belongs 2026-08-21 12:52:17 -05:00
package.json 0.1.5: say what Hound cannot see, and put the vault where it belongs 2026-08-21 12:52:17 -05:00