v2.4.1

Follow-up to 2.4.0's security hardening: a trusted proxy list, a bounded rate limiter, and tests that
were checked to fail when the protection they cover is removed.

Security

• The in-memory rate limiter stays bounded under a flood of distinct clients. Before, once
  200,000 counters were all still running, every request rescanned the whole map (CPU) and new
  clients kept being added (memory). Now it sweeps at most once a second and, while full, doesn't
  track new clients (those already counted stay limited). Found by a test that hung.
• trustedProxy.peers: the addresses (IPs or CIDR ranges) of the proxies allowed to set the
  forwarded-address headers. When it is set, a request from any other address has its headers
  ignored, so a client can't forge its address to dodge rate limits and lockouts; trusted hops are
  skipped from the right. Health warns when headers are trusted but no peers are listed.
• Tests that can fail: the SQL console test expected a 403, which a console that is switched off
  also returns, so it would have passed with the role check removed; it now runs with the console on
  and fails without the check. Backup retries and the file swap of a restore (the old files must
  stay if it fails) are tested too.

Install

• Docker: ghcr.io/ayeshrodz/slonbase:2.4.1
• Debian/Ubuntu: slonbase_2.4.1_amd64.deb / _arm64.deb
• Fedora/RHEL: slonbase-2.4.1-1.x86_64.rpm / .aarch64.rpm
• Binaries: slonbase-2.4.1-linux-{amd64,arm64}.tar.gz

Verify downloads with sha256sum --ignore-missing -c SHA256SUMS. See the installation guide.