remote-systemd-toggle 1.1.0 is now available.
This release focuses on two areas: better operational hardening with fail2ban support and a significantly improved README with clearer documentation, configuration examples, security notes, and tradeoffs.
🛡️ fail2ban Support
Version 1.1.0 adds log output intended for fail2ban integration.
The main goal is to help protect the server against repeated connection attempts with missing, invalid, or unauthorized client certificates. While mTLS already rejects these clients, the server still has to handle the incoming TCP/TLS handshake.
With fail2ban, repeated certificate-related failures can be detected in the logs and blocked at the firewall level before they keep reaching the application.
This adds another (optional) layer of protection (especially against DoS attacks) without making the application protocol more complex.
📚 Improved Documentation
The README has been heavily improved and now provides clearer information about:
- installation
- usage
- configuration
- certificate handling
- systemd integration
- tradeoffs
- Windows binary
- fail2ban integration
The goal is to make the project easier to understand, easier to install, and easier to review.
🔐 Same Small Scope
remote-systemd-toggle still deliberately does one small thing:
one mTLS-protected TCP connection, one password-authenticated command, one response, and no shell, file transfer, tunneling, or arbitrary command execution.
Small scope. Clear behavior. Less magic.