Failed 2 Ban

[SomeDamFool]

In F13 I had to disable fail2ban because it caused SELinux to go spastic and would overheat my laptop cpu. I've had F14 for a bit so I tried enabling fail2ban again, but got the same result.

I had 7 SELinux errors and filed bug reports on all of them. However 5 of them were duplicates that pointed to an original bug that was marked STATUS: CANTFIX. Hmm.. that doesn't sound good. So does this mean fail2ban is dead in the water?

Mike

[bodhi.zazen]

Originally Posted by SomeDamFool

In F13 I had to disable fail2ban because it caused SELinux to go spastic and would overheat my laptop cpu. I've had F14 for a bit so I tried enabling fail2ban again, but got the same result.

I had 7 SELinux errors and filed bug reports on all of them. However 5 of them were duplicates that pointed to an original bug that was marked STATUS: CANTFIX. Hmm.. that doesn't sound good. So does this mean fail2ban is dead in the water?

Mike

From your description sounds like it.

Not what you want to hear, but, honestly, I advise you learn iptables. You can accomplish essentially the same effect, but without the need to install any additional packages.

In general, less packages and less daemons is better security.

[SomeDamFool]

Thanks. I'll get back to IP tables and see what I can learn.
A while back I did play with IP tables a bit, then found fail2ban and got lazy.
Mike