3 ms·

You realise this only blocks connections from the abusive address, not all connections? If so, please enlighten me about how this enables a DOS.

• zAy0LfpBZLC8mAC 13y ago
  There is no such thing as an "abusive address". There are only "abusive attackers", but what you are blocking are addresses, not attackers. Blocking attackers would require authenticating them. Which is impossible, because attackers usually won't cooperate in authenticating them. Which is why we usually authenticate legitimate users instead. Which is what the sshd would do if you just let it do its job. What you do instead is to offer a service which anyone without any authentication can use to block any address they like from accessing your ssh server by sending three packets where they put the address they wish to block into the source address field, with different source ports so as to make netfilter consider them NEW flows. Such functionality that allows anyone to reduce the availability of a service, especially when it takes as little effort as three packets, is what is commonly called a Denial of Service vulnerability.
  • foxylad 13y ago
    Thanks for the explanation - I see your point and it would wise to consider this possibility when looking at this technique. For my use case though, this reduces load on my server (and prevents clogging my auth log files) by stopping incessant password brute-forcing attempts. I must admit to quickly adding an over-riding ALLOW for the handful of IP addresses that should have access, though!
• blueskin_ 13y ago
  Because source IPs really aren't easy to spoof, right? </s>