6016e1b4ea
Phase 2. "Distro-agnostic" was a claim with no packaging behind it. .deb and AppImage are both built and tested here; the rpm spec and PKGBUILD are written but not yet built, since neither rpmbuild nor makepkg exists on this machine. The AppImage is deliberately not a packaged daemon. An AppImage is unprivileged by design — no install, no root, no systemd — so the execution gate cannot exist in one, and pretending otherwise would be worse than saying so. What it is instead is the try-before-you-install build: on-demand scanning, quarantine under the user's own data dir, rootkit and supply-chain checks, all with nothing left behind. Asking it for the gate prints why it cannot and how to get it. Verified with an isolated HOME: status, scan, EICAR caught, gate refusal. Two packaging bugs caught by looking rather than assuming: * mktemp -d creates 0700 and dpkg applies the staging root's mode to "/". Installing that package would have chmodded the root directory to 0700 and broken the machine. * AppRun wrote its log before creating the directory, and built a socket path that can exceed sun_path (108 bytes) when XDG_RUNTIME_DIR is long. Both fixed; the socket falls back rather than failing with an error nobody can act on. The systemd unit is hardened as far as this daemon can be. Notably ProtectSystem=strict is WRONG here and is left off on purpose: it remounts everything read-only, and quarantine has to remove a threat from wherever it landed. ProtectHome is off for the same reason. The CapabilityBoundingSet mirrors what caps.rs drops to, so the machine is protected even if the binary is replaced by one that does not reduce itself. App icon: the mark in white on a periwinkle tile, per Joe. Small sizes are not the same artwork scaled down — the mark is line-weight, so at 16px a 62% inset leaves about a pixel and a half of stroke and the head turns to mush. Each size is authored with its own inset and corner radius, and the ground goes flat below 32px because a gradient across 16 pixels is just noise. The tray ladder is untouched: those glyphs stay transparent and re-tint per state so they can sit on any panel colour. Package installs are NOT enabled by default beyond the daemon itself — exec_gate stays off until the operator turns it on, in every packaging format. 99 tests pass. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
70 lines
2.3 KiB
RPMSpec
70 lines
2.3 KiB
RPMSpec
Name: hound
|
|
Version: 0.1.0
|
|
Release: 1%{?dist}
|
|
Summary: Hound Antivirus for Linux
|
|
License: Apache-2.0
|
|
URL: https://houndav.com
|
|
Source0: %{name}-%{version}.tar.gz
|
|
BuildRequires: rust >= 1.91, cargo, systemd-rpm-macros
|
|
Requires: systemd
|
|
Recommends: clamd
|
|
|
|
%description
|
|
Endpoint and supply-chain protection built for the distributions people
|
|
actually run. Scanning is yara-x in process; real-time protection uses
|
|
fanotify, so a binary can be refused at execve rather than reported after
|
|
it has already run.
|
|
|
|
The execution gate is installed switched OFF. It needs CAP_SYS_ADMIN and
|
|
covers the whole root filesystem, so enabling it is the operator's call:
|
|
hound settings set exec_gate true
|
|
|
|
%prep
|
|
%autosetup
|
|
|
|
%build
|
|
cargo build --release -p houndd -p hound
|
|
|
|
%install
|
|
install -Dm755 target/release/houndd %{buildroot}%{_bindir}/houndd
|
|
install -Dm755 target/release/hound %{buildroot}%{_bindir}/hound
|
|
install -Dm644 packaging/systemd/houndd.service \
|
|
%{buildroot}%{_unitdir}/houndd.service
|
|
install -Dm644 crates/houndd/rules/hound-builtin.yar \
|
|
%{buildroot}%{_datadir}/hound/rules/hound-builtin.yar
|
|
install -dm755 %{buildroot}%{_sharedstatedir}/hound/rules
|
|
install -dm700 %{buildroot}%{_sharedstatedir}/hound/vault
|
|
for s in 16 22 24 32 48 64 128 256 512; do
|
|
install -Dm644 assets/icons/app-${s}.png \
|
|
%{buildroot}%{_datadir}/icons/hicolor/${s}x${s}/apps/hound.png
|
|
done
|
|
install -Dm644 assets/icons/hound-app.svg \
|
|
%{buildroot}%{_datadir}/icons/hicolor/scalable/apps/hound.svg
|
|
|
|
%post
|
|
# Seed the built-in rules so an offline install still detects something.
|
|
cp -n %{_datadir}/hound/rules/hound-builtin.yar \
|
|
%{_sharedstatedir}/hound/rules/ 2>/dev/null || :
|
|
%systemd_post houndd.service
|
|
|
|
%preun
|
|
%systemd_preun houndd.service
|
|
|
|
%postun
|
|
%systemd_postun_with_restart houndd.service
|
|
|
|
%files
|
|
%{_bindir}/houndd
|
|
%{_bindir}/hound
|
|
%{_unitdir}/houndd.service
|
|
%{_datadir}/hound/rules/hound-builtin.yar
|
|
%{_datadir}/icons/hicolor/*/apps/hound.png
|
|
%{_datadir}/icons/hicolor/scalable/apps/hound.svg
|
|
%dir %{_sharedstatedir}/hound
|
|
%dir %{_sharedstatedir}/hound/rules
|
|
# The vault holds live malware: root-only, never world-readable.
|
|
%attr(0700,root,root) %dir %{_sharedstatedir}/hound/vault
|
|
|
|
%changelog
|
|
* Fri Aug 21 2026 Hound <support@houndav.com> - 0.1.0-1
|
|
- yara-x engine in process; fanotify execution gate
|