I have private custom ipset-managed blocklists on my system that get wiped out whenever csf is restarted,because, of course, csf is unaware of them. This poses a management problem.
Is there some way to inform csf of the existence of these ipsets? I am only aware of the support in /etc/csf/csf.blocklists, which is geared entirely to public lists dowloaded from external URLs.
CSF is great but I'm missing a LF_TEMPBLOCK_ALERT = x option.
You can use the LF_EMAIL_ALERT or LF_PERMBLOCK_ALERT options, but since permblocks won't be automatically removed (normally) and I do want to be alerted about other options (which I guess more people would like), the tempblock option is missing.
Temblocks will be removed automatically and generate a lot of email alerts, which in a...
We're 2 years further now and with Centos 8 this is really starting to get interesting.
In fact it lies in the netfilter's idea's to in time replace iptables with nftables.
Are there any plans from configserver to create a CSF firewall which works with nftables? Any insights on this?
These are from exim_mainlog:
2020-02-26 17:50:18 dovecot_login authenticator failed for ( ) :49078: 535 Incorrect authentication data
2020-02-26 17:50:20 dovecot_login authenticator failed for ( ) :43772: 535 Incorrect authentication data
2020-02-26 17:50:24 dovecot_login authenticator failed for ( ) :19374: 535 Incorrect authentication data
2020-02-26...
Vesta CP - Support added in CSF v13.05 ( changelog )
Hestia CP - Support will be added in which CSF version?
I was able to get CSF working on Hestia CP using the following simple sed snippet (from within the install directory):
find . -type f -exec sed -i 's/VESTA/HESTIA/g' {} + && \
find . -type f -exec sed -i 's/Vesta/Hestia/g' {} + && \
find . -type f -exec...
Hi fan of the product and thanks for offering it for free !
I had just a question/suggestion is it possible to list the ports separate from the config.
Or a port per line?
To have to go into the whole config to open ports is a bit confusing and the overview is lost since there is no order in the text line it allows for easy mistakes.
It's not a biggie just wondering if it can be formatted...
I think it would great if we could use cPanel API tokens to have servers share their deny/allow rules or deny IP list with others servers in a cluster of servers since attacks often travel along IP ranges and what not.
Maybe a caching system that you can set the frequency of deny IP sharing.
I think it will be a long time before counties are assigned IP blocks :) so you may want to change the spelling to 'Country's' on the config file for CSF:
An example would be to list port 21 here then counties listed in
CC_DENY_PORTS cannot access FTP
Tried to find something that allowed checking of IPs against AbuseIPDB and then if found then block, but couldn't find anything out there.
Hence writing this up.
We are using the csf RELAYHOSTS setting to prevent lfd from creating temporary firewall entries for customers who successfully check email. We are not on cPanel, so the setting isn't normally there, but it works perfectly once added. We have a separate daemon that maintains /etc/relayhosts with the IPs of recent successful connections.
The problem is that during a csf upgrade it seems to strip...
It seems my server is getting a lot of failed SASL auth attempts via the maillog lately. This doesn't seem to be part of CSF's default configuration, so a lot of bad attempts got through!
I added a custom rule for LFD to ban these bad SASL people, but I highly suggest you make it part of the default csf.conf
Here is the tutorial I followed to implement the custom rules on my own...
The directadmin installation suggests that CSF config should be managed by the directadmin and we have to set some bruteforce settings to 0 or disable them. By doing this, the CSF will trigger few warning messages.
From what I've known, CSF use a special installation config file for directadmin called csf.directadmin.conf and it contains a generic variable DIRECTADMIN=1
After working av week trying to make CSF Messenger work in a usable manner, we must conlude that at current time it is not usable for us. Here is a list over problems and bugs we experienced:
Our system: We are running DirectAdmin and CSF 14.01. We have both CentOS 7 and CentOS 8 servers (the below list apply to both). We are using ipset:
- On DirectAdmin is it needed to change default path in...
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