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.
When the deny_ip_limit limit is exceeded, and an additional csf -d command is run, the IPs are removed from csf.deny, but they still seem to be active in iptables. Is this the expected behavior? I would have thought they would be removed from iptables with csf -dr automatically so csf.deny is in sync with iptables.
Using csf v4.58. On restarting LFD, I would get an error Can't locate IP/Countries.pm in @INC (@INC contains: blah blah . Looking at /etc/csf, I can see a collection of Perl modules that are used by CSF and LFD, but not IP/Countries.pm . On line 124 of /usr/sbin/lfd, the module IP:Countries.pm is called, and it does not exist in /etc/csf. I believe the correct include should be...
I've noticed something while playing with CSF that I guess could be considered as a bug. First, let me put you in situation.
- Standard CSF v5.13 installation through sh ./install.sh no Web interfaces just pure text.
- OpenSSH server on ports 22 and 6022. This is configured with following lines on sshd_config:
Port 22
Port 6022
- csf.allow with following content...
We use a central LDAP server for authentication on our servers and we've been getting these errors for a while.
Dec 1 17:27:03 server cessing: nss_ldap: could not search LDAP server - Server is unavailable
Dec 1 17:29:03 server cessing: nss_ldap: could not get LDAP result - Can't contact LDAP server
Dec 1 17:29:03 server cessing: nss_ldap: could not get LDAP result - Can't contact LDAP server...
I understand the need to move away from colons (:) as a separator for denying and allowing rules due to upcoming IPv6. Just wondering why pipe (|) was chosen as the alternative? I believe this was introduced in version 5.04.
Reason being, to add a rule to the csf.deny file via the command line you can use the:
I'm getting the following warning:
IPv6 appears to be enabled . If ip6tables is installed, you should enable the csf IPv6 firewall (IPV6 in csf.conf). To disable IPv6 on RHEL/CentOS you should follow this link
Yet if I set IPv6_SPI to 1 I get a cron Warning email:
*WARNING* Kernel 2.6.18-164.15.1.el5PAE may not support an ip6tables SPI firewall. You should set IPV6_SPI to 1 in /etc/csf/csf.conf...
Just to mention that with latest version csf v5.04, when uprading from v5.03 on a
CentOS release 4.8 (Final) 32-bit system, I got these error (?) messages :
open3: exec of /sbin/ip6tables -v -A OUTPUT -o ! lo -p udp -m state --state NEW --dport 53 -j ACCEPT failed at /etc/csf/csf.pl line 2881
open3: exec of /sbin/ip6tables -v -A OUTPUT -o ! lo -p udp -m state --state NEW --dport 113 -j...
Hi, I have found a unique problem within Webmin version 1.480 and CSF 4.75 on Firefox 3.0.11. I had a staff member block themselves and their IP address was entered into the Firewall IP Deny list on Webmin. When I removed the entry and restarted CSF/LFD I found that it did not save my changes. It required me to manually edit the csf.deny file and remove the IP address.
I believe I may have fixed a minor bug in the Check Server Security script. On my server at least, the Check proftpd weak SSL/TLS Ciphers test was giving a false positive. I managed to track down the issue to the regexp on line 645 of servercheck.pm.
/TLSCipherSuite\s+(.*)$/
on my server, works better as:
/TLSCipherSuite:\s+(.*)$/
Note the added colon. Without it the $ciphers var never...
I usually login as a normal user via ssh on a non-standard port then su to root sometimes, but I only get the alert for the initial normal user login and not the switch to root. Is that normal behavoir?
I have a problem CSF using the latest version installed on cpanel. And on this server are 2 network card, eth0, eth1.
This server is used as rounter linux and such is necessary to allow traffic on eth1.
Unfortunately if chear
ETH_DEVICE = eth0
ETH_DEVICE_SKIP = eth1
Still not allow traffic on eth1, so all sv behind eth1 not running on the internet.
What can be done?
I am running csf+lfd in production environment and I am overall very happy with it. It is easy to manage while powerful enough to supposedly do what I need.
I installed it to prevent SYN_RECV floooding at first, and it does the job.
But with the public release of slowloris, I see an increase in attempts to DoS my sites.
On the servers we have upgraded to versions greater than 4.60, lfd has stopped sending email alerts (including latest version). Servers with versions less than 4.61 continue to send email alerts. All servers are RHEL5/cetnOS5 32 bit servers. csf.conf settings all appear correct.
As another test, we took a csf 4.23 server, triggered a block that sent an email, removed the IP from the block list,...
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum