I also use “Fail2Ban” as this can be configured to block an IP after a set number of login failures against a given port or ports.
Be warned… bad configuration will lock you out of your own system if you don’t watch out :-)
By default, I think it resets the iptables after a set period so not a total failure when you get locked out.
Works well for me.
Regards
Andy Brittain G0HXT g0hxt@greatbrittain.co.uk
On 8 Jan 2015, at 15:45, Brian n1uro@n1uro.ampr.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ Maiko;
On Thu, 2015-01-08 at 09:37 -0600, Maiko Langelaar wrote:
Is it just my system ?
Would it comfort you if I said it was just your system? If so, then yes ;-)
I'm seeing many many login attempts as root on telnet. Are they targetting just 44 ?
I see them pretty consistently on my system as well, and those I remote admin. The tool iptables is your friend here.
-- If Microsoft intended Windows to be for ham usage, they would have incorporated our protocols into their kernel.
73 de Brian Rogers - N1URO email: n1uro@n1uro.ampr.org Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net