• v1.5.0 f6e6a79105

    netwatch 1.5.0 — Blocklists, fleet bans, pending updates
    All checks were successful
    CI / fmt + clippy + test (push) Successful in 3m53s
    Release / build and publish (push) Successful in 8m59s
    Stable

    david released this 2026-10-31 18:11:07 +01:00 | 30 commits to main since this release

    Blocklists, fleet bans and pending updates.

    • The hub downloads Feodo Tracker (recommended), Spamhaus DROP and the Tor exit list daily.
      Feodo and DROP are blocked in both directions on every server that opts in; Tor exits are
      tagged, never blocked. A server that still tries to reach a listed address raises a crit
      alert: the strongest sign netwatch can give that the server is compromised.
    • An SSH auto-ban on one server is copied to every opted-in server, with one push. Unban
      everywhere lifts it on all of them.
    • Each server card shows pending security updates and "reboot required", read hourly by a
      read-only root helper. netwatch never runs apt update or installs anything.
    • Hub bans are opt-in per server: accept_hub_bans = true under [security] in agent.toml.
      The agent's safelist always wins. Turning it off and restarting removes everything the hub
      sent. The README's threat model describes the new worst case.
    • ban_cap defaults to 5000.

    Upgrade the hub first, then each agent, then opt in. Blocklists are tested on Ubuntu 24.04
    (nftables 1.0.9); Debian 12 (nftables 1.0.6) is expected to work but untested.

    netwatch is not affiliated with or endorsed by The Spamhaus Project.

    Downloads