On 08/10/10 21:24, Michael Corliss wrote:
I use an RSA key for SSH and Fail2Ban with iptables
for everything,
which seems to work well. I followed a setup guide created by another
Bitfolk user:
http://www.robertgauld.co.uk/omwb/2010apr~vps-setup-guide I decided
to install fail2ban today but get the following warnings on my
VPS (Debian Lenny). Google didn't come up with a solution. The strange
thing is that all the (many) failed SSH login attempts seem to have
disappeared in auth.log, although I see myself login if I tail auth.log
I see the reload in fail2ban.log, but no other activity
Any thoughts - here's the reload...
vs1:~# fail2ban-client reload
WARNING 'findtime' not defined in 'apache-noscript'. Using default value
WARNING 'findtime' not defined in 'pam-generic'. Using default value
WARNING 'findtime' not defined in 'vsftpd'. Using default value
WARNING 'findtime' not defined in 'xinetd-fail'. Using default value
WARNING 'findtime' not defined in 'named-refused-udp'. Using default
value
WARNING 'findtime' not defined in 'ssh-ddos'. Using default value
WARNING 'findtime' not defined in 'apache-multiport'. Using default value
WARNING 'findtime' not defined in 'apache-overflows'. Using default value
WARNING 'findtime' not defined in 'couriersmtp'. Using default value
WARNING 'findtime' not defined in 'wuftpd'. Using default value
WARNING 'findtime' not defined in 'ssh'. Using default value
WARNING 'findtime' not defined in 'postfix'. Using default value
WARNING 'findtime' not defined in 'sasl'. Using default value
WARNING 'findtime' not defined in 'apache'. Using default value
WARNING 'findtime' not defined in 'courierauth'. Using default value
WARNING 'findtime' not defined in 'proftpd'. Using default value
WARNING 'findtime' not defined in 'named-refused-tcp'. Using default
value
Regards,
Martin