This repository is the official Ansible Collection for POSIX system administration, providing a suite of modules, action plugins, callback plugins, and shell plugins that manage core Unix/Linux operations. The collection includes modules for managing mount points, SELinux policies, firewalld rules, ACLs, authorized SSH keys, system patches, file synchronization via rsync, sysctl parameters, cron-like at jobs, and RPM-OSTree upgrades. It also offers callback plugins for profiling task execution times, formatting output as JSON/JSONL, and debugging, as well as shell plugins for csh and fish. The architecture follows the standard Ansible collection layout with plugins organized by type (modules, actions, callbacks, shells) and shared module utilities for version comparison, firewalld transactions, and system interpreter fallback. The codebase is well-structured, extensively tested across multiple Ansible core versions (2.16–2.22) and operating systems (Linux, FreeBSD, macOS, AIX), and actively maintained with regular releases and security fixes.
This is a configuration-only infrastructure repository: it extends fail2ban so that a banned IP is not simply blocked, but has its SSH traffic redirected to a local endlessh tarpit on port 2222. The repository ships two fail2ban action definitions and one jail snippet. The iptables action inserts a NAT PREROUTING REDIRECT rule for the banned source IP on port 22; the firewalld action uses firewall-cmd rich rules with forward-port to the same effect. A jail.d config attaches the default endlessh action to the sshd jail. There is no application code, test suite, build system, or packaging; the artifact is three drop-in configuration files meant to be copied into /etc/fail2ban. This makes the project extremely simple and dependency-light, relying only on fail2ban and either iptables or firewalld. The core idea is clever and portable: instead of dropping malicious traffic, the system wastes an attacker's time against a tarpit. The two firewall backends give useful coverage across common Linux distributions. As a codebase it is minimal, and the craftsmanship lies in the choice of firewall rules rather than in software architecture. The files are clean, follow fail2ban's action and jail conventions, and are directly reusable by anyone already running endlessh on port 2222.