Vesta Control Panel - Forum

ArisC wrote:

Code: Select all

*Error* The path to iptables is either not set or incorrect for IPTABLES [/sbin/           ip6tables] in /etc/csf/csf.conf at /usr/local/csf/lib/ConfigServer/LookUpIP.pm l           ine 26.
Compilation failed in require at /usr/sbin/csf line 20.
BEGIN failed--compilation aborted at /usr/sbin/csf line 20.

https://i.imgur.com/ZyKHm9W.png

SS88 wrote:

ArisC wrote:

Code: Select all

*Error* The path to iptables is either not set or incorrect for IPTABLES [/sbin/           ip6tables] in /etc/csf/csf.conf at /usr/local/csf/lib/ConfigServer/LookUpIP.pm l           ine 26.
Compilation failed in require at /usr/sbin/csf line 20.
BEGIN failed--compilation aborted at /usr/sbin/csf line 20.

https://i.imgur.com/ZyKHm9W.png

CSF needs iptables to run. Please reinstall iptables then it should work. You might have to re-run the installer (but you shouldn't have to).

SS88 wrote:

ServerHost wrote:Hello,

I installed on my vps, but it does not work with Proftpd. Do not block!

How do I block Proftpd?

Change the file /etc/csf/csf.conf and find

Code: Select all

FTPD_LOG = "/var/log/vsftpd.log"

and change to where proftpd log is

Code: Select all

FTPD_LOG = "/path/to/proftpd.log"

ServerHost wrote:

SS88 wrote:

ServerHost wrote:Hello,

I installed on my vps, but it does not work with Proftpd. Do not block!

How do I block Proftpd?

Change the file /etc/csf/csf.conf and find

Code: Select all

FTPD_LOG = "/var/log/vsftpd.log"

and change to where proftpd log is

Code: Select all

FTPD_LOG = "/path/to/proftpd.log"

Thank you.
Worked perfectly on my Centos 6.9 server. However on my Centos 7 server it did not work, it is not blocking proftpd.

Centos 6.9 OK!
Centos 7 Does not work

What could be happening?

SS88 wrote:

ServerHost wrote:

SS88 wrote:
Change the file /etc/csf/csf.conf and find

Code: Select all

FTPD_LOG = "/var/log/vsftpd.log"

and change to where proftpd log is

Code: Select all

FTPD_LOG = "/path/to/proftpd.log"

Thank you.
Worked perfectly on my Centos 6.9 server. However on my Centos 7 server it did not work, it is not blocking proftpd.

Centos 6.9 OK!
Centos 7 Does not work

What could be happening?

I'm not 100% sure. This is a CSF issue.

This post should help you: viewtopic.php?f=20&t=10209&start=80#p57236
but you would need to modify it for proftpd to match the login fails.

ServerHost wrote:

SS88 wrote:

ServerHost wrote:
Thank you.
Worked perfectly on my Centos 6.9 server. However on my Centos 7 server it did not work, it is not blocking proftpd.

Centos 6.9 OK!
Centos 7 Does not work

What could be happening?

I'm not 100% sure. This is a CSF issue.

This post should help you: viewtopic.php?f=20&t=10209&start=80#p57236
but you would need to modify it for proftpd to match the login fails.

Thak you again.

I found these posts but it did not work. :(
https://goo.gl/B6wirA
https://goo.gl/ojpykK

Would you have any ideas or suggestions?

if (($lgfile eq $config{FTPD_LOG}) and ($line =~ /FAIL LOGIN: Client \"(\S+)\"/)) { return ("Failed FTP login from",$1,"vsftpd_ss88","5","20,21","1"); }

#!/usr/bin/perl
###############################################################################
# Copyright 2006-2016, Way to the Web Limited
# URL: http://www.configserver.com
# Email: [email protected]
###############################################################################

sub custom_line {
	my $line = shift;
	my $lgfile = shift;

# Do not edit before this point
###############################################################################
#
# Custom regex matching can be added to this file without it being overwritten
# by csf upgrades. The format is slightly different to regex.pm to cater for
# additional parameters. You need to specify the log file that needs to be
# scanned for log line matches in csf.conf under CUSTOMx_LOG. You can scan up
# to 9 custom logs (CUSTOM1_LOG .. CUSTOM9_LOG)
#
# The regex matches in this file will supercede the matches in regex.pm
#
# Example:
#	if (($globlogs{CUSTOM1_LOG}{$lgfile}) and ($line =~ /^\S+\s+\d+\s+\S+ \S+ pure-ftpd: \(\?\@(\d+\.\d+\.\d+\.\d+)\) \[WARNING\] Authentication failed for user/)) {
#		return ("Failed myftpmatch login from",$1,"myftpmatch","5","20,21","1");
#	}
#
# The return values from this example are as follows:
#
# "Failed myftpmatch login from" = text for custom failure message
# $1 = the offending IP address
# "myftpmatch" = a unique identifier for this custom rule, must be alphanumeric and have no spaces
# "5" = the trigger level for blocking
# "20,21" = the ports to block the IP from in a comma separated list, only used if LF_SELECT enabled. To specify the protocol use 53;udp,53;tcp
# "1" = n/temporary (n = number of seconds to temporarily block) or 1/permanant IP block, only used if LF_TRIGGER is disabled

if (($lgfile eq $config{FTPD_LOG}) and ($line =~ /FAIL LOGIN: Client \"(\S+)\"/)) { return ("Failed FTP login from",$1,"vsftpd_ss88","5","20,21","1"); }

# If the matches in this file are not syntactically correct for perl then lfd
# will fail with an error. You are responsible for the security of any regex
# expressions you use. Remember that log file spoofing can exploit poorly
# constructed regex's
###############################################################################
# Do not edit beyond this point

	return 0;
}

1;

SS88 wrote:

ServerHost wrote:

SS88 wrote:
I'm not 100% sure. This is a CSF issue.

This post should help you: viewtopic.php?f=20&t=10209&start=80#p57236
but you would need to modify it for proftpd to match the login fails.

Thak you again.

I found these posts but it did not work. :(
https://goo.gl/B6wirA
https://goo.gl/ojpykK

Would you have any ideas or suggestions?

Try this instead:

Edit file /etc/csf/regex.custom.pm

Add the following BEFORE return 0;

Code: Select all

if (($lgfile eq $config{FTPD_LOG}) and ($line =~ /FAIL LOGIN: Client \"(\S+)\"/)) { return ("Failed FTP login from",$1,"vsftpd_ss88","5","20,21","1"); }

So your file will look something like this:

Code: Select all

#!/usr/bin/perl
###############################################################################
# Copyright 2006-2016, Way to the Web Limited
# URL: http://www.configserver.com
# Email: [email protected]
###############################################################################

sub custom_line {
	my $line = shift;
	my $lgfile = shift;

# Do not edit before this point
###############################################################################
#
# Custom regex matching can be added to this file without it being overwritten
# by csf upgrades. The format is slightly different to regex.pm to cater for
# additional parameters. You need to specify the log file that needs to be
# scanned for log line matches in csf.conf under CUSTOMx_LOG. You can scan up
# to 9 custom logs (CUSTOM1_LOG .. CUSTOM9_LOG)
#
# The regex matches in this file will supercede the matches in regex.pm
#
# Example:
#	if (($globlogs{CUSTOM1_LOG}{$lgfile}) and ($line =~ /^\S+\s+\d+\s+\S+ \S+ pure-ftpd: \(\?\@(\d+\.\d+\.\d+\.\d+)\) \[WARNING\] Authentication failed for user/)) {
#		return ("Failed myftpmatch login from",$1,"myftpmatch","5","20,21","1");
#	}
#
# The return values from this example are as follows:
#
# "Failed myftpmatch login from" = text for custom failure message
# $1 = the offending IP address
# "myftpmatch" = a unique identifier for this custom rule, must be alphanumeric and have no spaces
# "5" = the trigger level for blocking
# "20,21" = the ports to block the IP from in a comma separated list, only used if LF_SELECT enabled. To specify the protocol use 53;udp,53;tcp
# "1" = n/temporary (n = number of seconds to temporarily block) or 1/permanant IP block, only used if LF_TRIGGER is disabled

if (($lgfile eq $config{FTPD_LOG}) and ($line =~ /FAIL LOGIN: Client \"(\S+)\"/)) { return ("Failed FTP login from",$1,"vsftpd_ss88","5","20,21","1"); }

# If the matches in this file are not syntactically correct for perl then lfd
# will fail with an error. You are responsible for the security of any regex
# expressions you use. Remember that log file spoofing can exploit poorly
# constructed regex's
###############################################################################
# Do not edit beyond this point

	return 0;
}

1;

ServerHost wrote:

SS88 wrote:

ServerHost wrote:

Thak you again.

I found these posts but it did not work. :(
https://goo.gl/B6wirA
https://goo.gl/ojpykK

Would you have any ideas or suggestions?

Try this instead:

Edit file /etc/csf/regex.custom.pm

Add the following BEFORE return 0;

Code: Select all

if (($lgfile eq $config{FTPD_LOG}) and ($line =~ /FAIL LOGIN: Client \"(\S+)\"/)) { return ("Failed FTP login from",$1,"vsftpd_ss88","5","20,21","1"); }

So your file will look something like this:

Code: Select all

#!/usr/bin/perl
###############################################################################
# Copyright 2006-2016, Way to the Web Limited
# URL: http://www.configserver.com
# Email: [email protected]
###############################################################################

sub custom_line {
	my $line = shift;
	my $lgfile = shift;

# Do not edit before this point
###############################################################################
#
# Custom regex matching can be added to this file without it being overwritten
# by csf upgrades. The format is slightly different to regex.pm to cater for
# additional parameters. You need to specify the log file that needs to be
# scanned for log line matches in csf.conf under CUSTOMx_LOG. You can scan up
# to 9 custom logs (CUSTOM1_LOG .. CUSTOM9_LOG)
#
# The regex matches in this file will supercede the matches in regex.pm
#
# Example:
#	if (($globlogs{CUSTOM1_LOG}{$lgfile}) and ($line =~ /^\S+\s+\d+\s+\S+ \S+ pure-ftpd: \(\?\@(\d+\.\d+\.\d+\.\d+)\) \[WARNING\] Authentication failed for user/)) {
#		return ("Failed myftpmatch login from",$1,"myftpmatch","5","20,21","1");
#	}
#
# The return values from this example are as follows:
#
# "Failed myftpmatch login from" = text for custom failure message
# $1 = the offending IP address
# "myftpmatch" = a unique identifier for this custom rule, must be alphanumeric and have no spaces
# "5" = the trigger level for blocking
# "20,21" = the ports to block the IP from in a comma separated list, only used if LF_SELECT enabled. To specify the protocol use 53;udp,53;tcp
# "1" = n/temporary (n = number of seconds to temporarily block) or 1/permanant IP block, only used if LF_TRIGGER is disabled

if (($lgfile eq $config{FTPD_LOG}) and ($line =~ /FAIL LOGIN: Client \"(\S+)\"/)) { return ("Failed FTP login from",$1,"vsftpd_ss88","5","20,21","1"); }

# If the matches in this file are not syntactically correct for perl then lfd
# will fail with an error. You are responsible for the security of any regex
# expressions you use. Remember that log file spoofing can exploit poorly
# constructed regex's
###############################################################################
# Do not edit beyond this point

	return 0;
}

1;

Did not work.

SS88 wrote:

ServerHost wrote:

SS88 wrote:
Try this instead:

Edit file /etc/csf/regex.custom.pm

Add the following BEFORE return 0;

Code: Select all

if (($lgfile eq $config{FTPD_LOG}) and ($line =~ /FAIL LOGIN: Client \"(\S+)\"/)) { return ("Failed FTP login from",$1,"vsftpd_ss88","5","20,21","1"); }

So your file will look something like this:

Code: Select all

#!/usr/bin/perl
###############################################################################
# Copyright 2006-2016, Way to the Web Limited
# URL: http://www.configserver.com
# Email: [email protected]
###############################################################################

sub custom_line {
	my $line = shift;
	my $lgfile = shift;

# Do not edit before this point
###############################################################################
#
# Custom regex matching can be added to this file without it being overwritten
# by csf upgrades. The format is slightly different to regex.pm to cater for
# additional parameters. You need to specify the log file that needs to be
# scanned for log line matches in csf.conf under CUSTOMx_LOG. You can scan up
# to 9 custom logs (CUSTOM1_LOG .. CUSTOM9_LOG)
#
# The regex matches in this file will supercede the matches in regex.pm
#
# Example:
#	if (($globlogs{CUSTOM1_LOG}{$lgfile}) and ($line =~ /^\S+\s+\d+\s+\S+ \S+ pure-ftpd: \(\?\@(\d+\.\d+\.\d+\.\d+)\) \[WARNING\] Authentication failed for user/)) {
#		return ("Failed myftpmatch login from",$1,"myftpmatch","5","20,21","1");
#	}
#
# The return values from this example are as follows:
#
# "Failed myftpmatch login from" = text for custom failure message
# $1 = the offending IP address
# "myftpmatch" = a unique identifier for this custom rule, must be alphanumeric and have no spaces
# "5" = the trigger level for blocking
# "20,21" = the ports to block the IP from in a comma separated list, only used if LF_SELECT enabled. To specify the protocol use 53;udp,53;tcp
# "1" = n/temporary (n = number of seconds to temporarily block) or 1/permanant IP block, only used if LF_TRIGGER is disabled

if (($lgfile eq $config{FTPD_LOG}) and ($line =~ /FAIL LOGIN: Client \"(\S+)\"/)) { return ("Failed FTP login from",$1,"vsftpd_ss88","5","20,21","1"); }

# If the matches in this file are not syntactically correct for perl then lfd
# will fail with an error. You are responsible for the security of any regex
# expressions you use. Remember that log file spoofing can exploit poorly
# constructed regex's
###############################################################################
# Do not edit beyond this point

	return 0;
}

1;

Did not work.

Of sorry, that was for vsftpd. Can you show me the logs of Proftpd which show the login errors and I can make a regular expression to match the ip address.