shelltrap.com

There are no unauthenticated package links, and there never will be. Packages are served by the licence service against a valid key, and the key goes to that service directly — the shelltrap.com website never sees or stores it. The service logs the key prefix, never the key.

Getting the packages

Use the form on the download page with your key, or take the links and the current checksums from the client area, where your key and your activated servers are listed as well. The index of available versions is public, so a page can display the current release; the package files themselves are not.

Verify before installing

Every release directory carries a SHA256SUMS file next to the packages, and the same checksums are shown in the client area:

sha256sum -c --ignore-missing SHA256SUMS
dpkg-deb --info shelltrap_0.2.3_amd64.deb      # Debian/Ubuntu
rpm -qip shelltrap-0.2.3-1.x86_64.rpm          # AlmaLinux/RHEL

Detached OpenPGP signatures and an apt/dnf repository are planned for a later release and are deliberately not advertised here until they exist.

Which files you need

Two packages per host, both from the same version: shelltrap (the scanner) and shelltrap-cyberpanel (the panel integration, optional).

Upgrading

Before an upgrade, note the current feed state and back up the configuration, audit and quarantine data:

shelltrap feeds list
shelltrap health

Then upgrade with the native package manager:

sudo apt-get install --only-upgrade shelltrap
sudo dnf upgrade shelltrap

Because shelltrap.toml is a conffile, an upgrade on a host with a modified configuration should keep your version explicitly:

apt-get -o Dpkg::Options::=--force-confold install ./shelltrap_<version>_amd64.deb

Otherwise the package can be left in install ok unpacked while the old daemon keeps running — and a mixed version is worse than either, because an old daemon starting new worker binaries hits a strict protocol decoder that rejects unknown fields, and workers die until the restart.

After the upgrade

shelltrap health
shelltrap status
shelltrap feeds list

After a CyberPanel upgrade, re-run the packaged repair path for the plugin, because a panel upgrade can rewrite the core files the plugin patched:

sudo /usr/share/shelltrap-cyberpanel/install.sh

The broker and the CLI must keep working even when the panel UI is broken.

If something goes wrong

Feed generations can be rolled back while the broker is running, and the packages can be reinstalled from the same verified files. Do not mix versions of shelltrap and shelltrap-cyberpanel.