Le 26/02/2020 à 13:05, Nicolas Kovacs a écrit :
Weirdly enough, when I follow this suggestion, generate the module and then
empty audit.log and restart my server, I still get the exact same error again.
Which makes Fail2ban unusable with SELinux in enforcing mode in the current state.
Looks like this is clearly a bug. I made some more testing.
Installed vanilla CentOS 7 on an Internet-facing sandbox server.
Configured NetworkManager.
Configured FirewallD.
Installed fail2ban-server and fail2ban-firewalld.
Put this in /etc/fail2ban/jail.d/sshd.local
[sshd]
enabled = true
Started Fail2ban.
I get the same SELinux error than the one described in the initial message to
the list.
And when I follow the advice displayed by SEalert, the same error occurs again.
Which leaves me clueless.
Any suggestions ?
Niki Kovacs
--
Microlinux - Solutions informatiques durables
7, place de l'église - 30730 Montpezat
Site : https://www.microlinux.fr
Mail : info@xxxxxxxxxxxxx
Tél. : 04 66 63 10 32
Mob. : 06 51 80 12 12
_______________________________________________
epel-devel mailing list -- epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to epel-devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/epel-devel@xxxxxxxxxxxxxxxxxxxxxxx
