summaryrefslogtreecommitdiffstats
path: root/recipes-security/fail2ban/files
Commit message (Collapse)AuthorAgeFilesLines
* fail2ban: fix runtime errorArmin Kuster2020-01-221-4/+4
| | | | | | use success/failure calls in initd/function Signed-off-by: Armin Kuster <akuster808@gmail.com>
* python3-fail2ban: Fix build error of xrange.leimaohui2019-05-211-0/+28
| | | | | | | NameError: name 'xrange' is not defined Signed-off-by: Lei Maohui <leimaohui@cn.fujitsu.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
* fail2ban: add ptestArmin Kuster2018-10-311-0/+3
| | | | Signed-off-by: Armin Kuster <akuster808@gmail.com>
* fail2Ban: Add new packageArmin Kuster2017-09-012-0/+273
Fail2Ban scans log files like /var/log/auth.log and bans IP addresses having too many failed login attempts. It does this by updating system firewall rules to reject new connections from those IP addresses, for a configurable amount of time. Fail2Ban comes out-of-the-box ready to read many standard log files, such as those for sshd and Apache, and is easy to configure to read any log file you choose, for any error you choose. Though Fail2Ban is able to reduce the rate of incorrect authentications attempts, it cannot eliminate the risk that weak authentication presents. Configure services to use only two factor or public/private authentication mechanisms if you really want to protect services. Signed-off-by: Armin Kuster <akuster808@gmail.com>