csf ldf not blocking failed login triggers

This forum is only for reproducible bugs with csf and lfd (i.e. not iptables problems, lack of understanding how to use a feature, etc). Posts must be accompanied with full technical details of the problem and how it can be recreated. Any posts not adhering to this, or not considered bugs, will be moved to the General Discussion (csf) forum.
Post Reply
wolf
Junior Member
Posts: 51
Joined: 13 Jul 2007, 14:19
Contact:

csf ldf not blocking failed login triggers

Post by wolf »

Since the update to csf v 3.30 csf does not block failed login attempts to any service. here is an example of one of the 87 emails I found this morning.

Time: Mon May 19 03:09:16 2008
IP: user (Unknown)
Failures: 6 (pop3d)
Interval: 240 seconds
Blocked: Yes

Log entries:

May 19 03:09:08 server pop3d: LOGIN FAILED, user=user, ip=[::ffff:88.159.165.22]
May 19 03:09:09 server pop3d: LOGIN FAILED, user=user, ip=[::ffff:88.159.165.22]
May 19 03:09:10 server pop3d: LOGIN FAILED, user=user, ip=[::ffff:88.159.165.22]
May 19 03:09:13 server pop3d: LOGIN FAILED, user=user, ip=[::ffff:88.159.165.22]
May 19 03:09:15 server pop3d: LOGIN FAILED, user=user, ip=[::ffff:88.159.165.22]
May 19 03:09:15 server pop3d: LOGIN FAILED, user=user, ip=[::ffff:88.159.165.22]


all blocking has and always was set to permanantly block any failed login attempts but now seems to be broken since the last update.

WHM 11.15.0 cPanel 11.18.6-S24255
CENTOS Enterprise 4.6 i686 on standard - WHM X v3.1.0

any one else experiencing anything similar ?
chirpy
Moderator
Posts: 3537
Joined: 09 Dec 2006, 18:13

Post by chirpy »

regex.pm is picking up the wrong return string for pop3 and imap logins - should have a fix out for it soon.
wolf
Junior Member
Posts: 51
Joined: 13 Jul 2007, 14:19
Contact:

Post by wolf »

fixed in version 3.31
thanks :)
Post Reply