> spiped looks like netcat with symmetric encryption True. But to be more specific, it does symmetric encryption and authentication. > If your SSH server has

> spiped looks like netcat with symmetric encryption True. But to be more specific, it does symmetric encryption and authentication. > If your SSH server has password auth disabled, then all you're doing is moving the attack surface from one thing to another. I get what you're saying. But I see spiped as port-knocking with a 256bits combination. So basically, you are reducing the attack surface. In order for the attacker to get through, they need a vulnerability in spiped and in openssh-server. (If these probabilities are 50-50 each, that means the overall probability is 0.25) At the end of the day, spiped should run in a chroot, as a user, so the attack surface of spiped is really low. If it gets compromised, the only thing the attacker can do is "be able to try to establish a connection to the SSH server". The goal of spiped for me is to eliminate the need for constant monitoring of openssh vulnerabilities, and for installing fail2ban/blacklistd (which can lock legitimate users out)