Until the fix is available, I've been able to get it running until the
next system reboot by doing the following:
# setenforce 0
# systemctl start fail2ban
... wait a minute ...
# setenforce 1
Tom
On 5/3/2024 12:39 PM, Patrick O'Callaghan wrote:
On Fri, 2024-05-03 at 06:45 -0500, Richard Shaw wrote:
On Fri, May 3, 2024 at 6:31 AM Patrick O'Callaghan
<pocallaghan@xxxxxxxxx>
wrote:
F40 fully updated.
Try a `dnf --refresh update`. The fix just went to stable last night.
That just gets the same update I already tried.
poc
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
