I guess I just don't understand your complaint. The author makes it pretty clear that this is an additional layer on top of already-good security. So it only de

I guess I just don't understand your complaint. The author makes it pretty clear that this is an additional layer on top of already-good security. So it only delays a sophisticated attacker for a few minutes, maybe, but maybe that's enough delay to get that attacker to move onto an easier target. In any case, I don't think this is meant specifically for sophisticated attackers targeting your machine specifically. The author also posted some data: "I configured my SSH daemon to listen on port 24 in addition to its regular port of 22 so I could see the difference in attempts to connect to each (the connections are usually password guessing attempts). My expected result is far fewer attempts to access SSH on port 24 than port 22, which I equate to less risk to my, or any, SSH daemon. [ Setup for the testing was easy: I added a Port 24 line to my sshd_config file, and then added some logging to my firewall rules for ports 22 and 24. ] I ran with this configuration for a single weekend, and received over eighteen thousand (18,000) connections to port 22, and five (5) to port 24."