"/run/fail2ban(/.*)?" is usually how it is done, so I was wondering if
restorecon didn't like current form for some reason. However, as you
mentioned in the other email, it works on a fresh system, so this is not
the problem.
On 5/4/24 14:58, Richard Shaw wrote:
On Sat, May 4, 2024 at 4:49 PM
I don't think the problem is the "fc" file, but the fact that the file
in /run/fail2ban didn't get relabeled when the users updated, or the
selinux subpackage didn't get updated at all. That explains why it works
on a fresh system.
The specificity of "/run/fail2ban(/.*)?" is better and safer,
I'm trying to reproduce the problem on the Fedora rawhide test machine but
it's running without error!
$ sudo systemctl status fail2ban.service
● fail2ban.service - Fail2Ban Service
Loaded: loaded (/usr/lib/systemd/system/fail2ban.service; disabled;
preset: disabled)
Drop-In:
On 5/4/24 2:58 PM, Richard Shaw wrote:
On Sat, May 4, 2024 at 4:49 PM Carlos Rodriguez-Fernandez
mailto:carlosrodrifernan...@gmail.com>>
wrote:
The suggestion for one of the comments of using `/run/fail2ban(/.*)?`
instead of `/run/fail2ban.*` doesn't work?
I try to be very careful
On Sat, May 4, 2024 at 4:49 PM Carlos Rodriguez-Fernandez <
carlosrodrifernan...@gmail.com> wrote:
> The suggestion for one of the comments of using `/run/fail2ban(/.*)?`
> instead of `/run/fail2ban.*` doesn't work?
>
I try to be very careful with making changes in SELinux and I don't know
what
The suggestion for one of the comments of using `/run/fail2ban(/.*)?`
instead of `/run/fail2ban.*` doesn't work?
On 5/4/24 13:05, Richard Shaw wrote:
I still don't understand SELinux and would appreciate an assist!
fail2ban-server is unable to create the socket file
On 5/4/24 1:05 PM, Richard Shaw wrote:
I still don't understand SELinux and would appreciate an assist!
fail2ban-server is unable to create the socket file
/run/fail2ban/fail2ban.sock
There's a lot of custom SELinux policies and I'm unable to figure out
what needs to change.
I made a PR.
I still don't understand SELinux and would appreciate an assist!
fail2ban-server is unable to create the socket file
/run/fail2ban/fail2ban.sock
There's a lot of custom SELinux policies and I'm unable to figure out what
needs to change.
https://bugzilla.redhat.com/show_bug.cgi?id=2279054
