Skip to content
Witen

Linux deployment

Warden automation and packaging

Automate a verified installation once you have reviewed the host’s logs, firewall, and recovery access.

For a manual installation, start with the Warden quickstart.

Public downloads for package managers

These HTTPS endpoints work without cookies, tokens, or a signed-in browser. The latest version is 0.1.50. Enrollment is a separate step after you install.

curl -fsS https://www.witenlabs.com/api/releases/warden/version
curl -fsS https://www.witenlabs.com/api/releases/warden
curl -fLO https://www.witenlabs.com/api/releases/warden/artifacts/witen-warden-0.1.50-linux-amd64-glibc.tar.gz

Use the manifest to find available packages and compare the checksum before installing. Keep a verified copy of any package you need for rollback. Signed statements for retired releases remain available in the release log.

Gentoo overlay

Install Warden with Portage from the witen overlay as net-analyzer/witen-warden-bin. New releases arrive with your normal sync, and Portage checks each download against the overlay's Manifest, which pins the hashes of the signed release. After an upgrade the package restarts Warden if it is running; a stopped Warden stays stopped. It installs both the OpenRC service and the systemd unit, for amd64 (glibc or musl) and 32-bit x86 (glibc). You need Portage 3.0.66 or later.

sudo mkdir -p /etc/portage/repos.conf /etc/portage/package.license
printf '[witen]\nlocation = /var/db/repos/witen\nsync-type = zipfile\nsync-uri = https://www.witenlabs.com/gentoo/witen.zip\n' | sudo tee /etc/portage/repos.conf/witen.conf
echo "net-analyzer/witen-warden-bin Witen-Warden" | sudo tee /etc/portage/package.license/witen-warden-bin
sudo emerge --sync witen
sudo emerge --ask net-analyzer/witen-warden-bin

The second line adds the overlay. The third accepts Warden's license, which Portage asks for because it is not a free software license. If /etc/portage/repos.conf or /etc/portage/package.license is a file on your system rather than a directory, add the line to that file instead.

Then start Warden. With OpenRC, the Gentoo default:

sudo rc-update add witen-warden default
sudo rc-service witen-warden start

With systemd:

sudo systemctl enable --now witen-warden

To update Warden on its own (it also updates with emerge --update @world):

sudo emerge --sync
sudo emerge --ask --update net-analyzer/witen-warden-bin

Moving from install.sh or your own ebuild. Your configuration in /etc/witen and state in /var/lib/witen stay. If you wrote your own ebuild, remove it first with sudo emerge --unmerge and its name. If you used install.sh, run sudo rm /usr/local/bin/warden, install the package, then run sudo etc-update and accept the new /etc/init.d/witen-warden and /etc/conf.d/witen-warden. Finish with sudo rc-service witen-warden restart, or sudo systemctl restart witen-warden on systemd.

Let an agent install Warden

Give your coding or operations agent SSH access to one host, a Warden artifact, its published SHA-256 checksum, and a fresh setup code. Do not paste your account key into an agent session.

Install and enroll Witen Warden on [SSH HOST] as [SSH USER].

Inputs:
- Local Warden artifact: [LOCAL PATH]
- Expected SHA-256: [SHA256]
- Asset name: [UNIQUE HOST NAME]
- Single-use enrollment token: [PROVIDE PRIVATELY]
- Management address/CIDR that must never be blocked: [IP OR CIDR]

Requirements:
1. Inspect the remote OS, architecture, libc, init system, firewall manager, and available SSH/web/Cockpit log sources before changing anything.
2. Select only the matching supported DEB, RPM, APK, glibc portable, musl portable, or legacy 386 build. Verify the artifact with sha256sum before installing it. Stop on any mismatch.
3. Do not print, log, commit, or leave the enrollment token in shell history. Do not expose any resulting sensor credential.
4. Preserve /var/lib/witen. Back up an existing /etc/witen/warden.toml before editing it, and do not alter unrelated services or firewall policy.
5. Set server_name in the existing [server] section and the single-use enrollment_token in the existing [warden] section, editing those lines in place; never add a second [server] or [warden] header. Keep credential_file = "/var/lib/witen/sensor-credential". Configure detected log sources and never_block for my management address. Warden defaults to https://collector.witenlabs.com; set collector_url only if I explicitly provide a different collector.
6. Run sudo warden validate --config /etc/witen/warden.toml before starting or restarting. On firewalld hosts, also run sudo firewall-cmd --check-config. Check the firewall_manager_compatibility result and confirm Warden’s rules are present. Stop and ask before any change that could interrupt SSH, DNS, the active firewall manager, or another production service.
7. Enable and start the appropriate systemd or OpenRC service. Confirm its version, service health, source health, firewall backend, enrollment, and reporting in Witen. Remove the consumed enrollment token from the configuration after the sensor credential exists, then validate again.
8. Report the exact package version, checksum, files changed, tests performed, and rollback steps without revealing secrets. If a check fails, preserve evidence and restore the prior configuration rather than improvising a destructive fix.
  • Use a short-lived setup code generated for this one server.
  • Keep your current management IP or network in never_block before enforcement starts.
  • Require checksum, configuration validation, service, source, firewall, and website reporting checks.
  • Keep /var/lib/witen during upgrades and rollback; it holds Warden’s state and its Witen credential.