4 ms·

Here's a good list of reasons: https://www.opencve.io/cve?vendor=fail2ban https://www.opencve.io/cve?vendor=fail2ban Parsing log files not intended to be read

• 15457345234 3y ago
  That's a very very small list of vulnerabilities for such a widely used piece of software. Using fail2ban with SSH is very widely done and is thoroughly recommended. It increases security and is objectively a good idea.
  • rlpb 3y ago
    > That's a very very small list of vulnerabilities for such a widely used piece of software. They are schoolboy errors in a relatively trivial piece of software that very well demonstrate the fundamental security flaw in its design. > is thoroughly recommended Recommended by whom? The Internet, or prominent experts in the field?
    • 15457345234 3y ago
      > They are schoolboy errors in a relatively trivial piece of software that very well demonstrate the fundamental security flaw in its design. I read through the CVEs and they're not 'schoolboy errors' at all - in fact, the first one doesn't even refer to fail2ban itself but to a program being called by fail2ban. There's no fundamental security flaw in its design. > Recommended by whom? The Internet, or prominent experts in the field? It's recommended in several linux/unix books - physical books, written by experts - and in many blogs. So, both.