linux-kernel - Re: kernel.org status: hints on how to check your machine for intrusion

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20111001.141343.2293070262147973147.davem@davemloft.net>
Date:	Sat, 01 Oct 2011 14:13:43 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	rostedt@...dmis.org
Cc:	w@....eu, greg@...ah.com, linux-kernel@...r.kernel.org
Subject: Re: kernel.org status: hints on how to check your machine for
 intrusion

From: Steven Rostedt <rostedt@...dmis.org>
Date: Sat, 1 Oct 2011 14:06:41 -0400

> For my machine that is connected to the outside world, I have a script
> that runs every night that checks for attacks. As bots constantly look
> for port 22 and 80, they find my machine without issue. When my script
> detects a bunch of ssh login attempts that fail, it will add that ip
> address to the iptables DROP chain:

By running sshd on a different port, you'll avoid the login attempts
as well as the overhead of the successful connection attempts.

I haven't allowed sshd to run on port 22 in more than 10 years.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/