A joke security tool that changes your SSH server's listening port every 30 seconds using TOTP codes.
totp-ssh-fluxer is a joke security tool that dynamically changes a server's SSH port every 30 seconds using Time-based One-Time Password (TOTP) codes. It uses iptables rules to redirect traffic to the current port, making it extremely difficult for automated bots to find the SSH service. The project is presented as a humorous experiment rather than a serious security solution.
Security researchers, system administrators, and developers interested in unconventional network security experiments or educational demonstrations about port obfuscation.
It provides an extreme, automated implementation of port obfuscation that highlights the limitations of security-through-obscurity. The project is unique for its creative use of TOTP codes for port selection and its clear stance as a joke rather than a production tool.
Take security by obscurity to the next level (this is a bad idea, don't really use this please)
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Automatically changes the SSH port every 30 seconds using TOTP codes, effectively hiding the service from automated bots as demonstrated in the README.
Leverages iptables PREROUTING rules to keep established SSH connections alive even after port changes, preventing disruptions.
Generates a TOTP key on first run and saves it to /etc/ssh-flux-key, simplifying client configuration without manual key creation.
Serves as a tongue-in-cheek example to critique security-through-obscurity, making it useful for learning about network security concepts.
The author explicitly states it was written as a joke and warns against running it seriously, indicating a lack of reliability and support.
Must run as root to edit iptables, which introduces security risks and limits deployment in restricted environments.
Manual insertion and removal of iptables rules can conflict with existing firewall setups and may not survive system reboots.
Users must manually input TOTP codes into SSH clients for each connection, lacking automation and increasing usability friction.