someone trying to hack me?

fotoguy · 07-19-2008, 07:52 PM

I have a little script that I use to scan my log files for people trying to log in to ssh, once they get to a limit of attempts, I then use iptables to block them permantely.

Code:

#!/bin/sh
HOSTSDENY="/etc/hosts.deny"
BADCOUNT="1"
IPTABLES=`which iptables`

cat /var/log/messages | grep "user not found" | tr -c '.[:digit:]' '\n' | grep '^[^.][^.]*\.[^.][^.]*\.[^.][^.]*\.[^.][^.]*$' | sort | uniq -c | sort -n | while read i
do
	# read number of failed attempts
	count=`echo $i | cut -d" " -f1`

	# read ip address from failed attempt
	ip=`echo $i | cut -d" " -f2`

	#check hostdeny file to see if IP already exist
	already=`grep $ip $HOSTSDENY`

	#if IP does not exist add it to hostdeny file
	if [ -z $already ]; then
		if [ $count -ge $BADCOUNT ]; then
			echo "$ip" >> $HOSTSDENY

			# add a rule to iptables to drop
			CHECK_IPTABLES=`$IPTABLES -L -n | grep "$ip"` # check first to see if a rule already exists

			if [ -z $CHECK_IPTABLES ]; then
				$IPTABLES -I INPUT -s $ip -j DROP
			fi
		fi
	fi
done

Hangdog42 · 07-20-2008, 07:15 AM

Quote:

Originally Posted by /dev/me

Would it be safe to assume btw that anyone who has the knowledge to move ssh to a different port also has the knowledge to appreciate the value of long and complicated passwords and out-of-the-ordinary login names??

You would think this is true, but I've seen way too many people think that moving the ssh port is all the "security" they need to actually believe it. Most people with this problem are only concerned because of the scary entries in their log files. Once those go away, they make the grand leap to the assumption that they are therefore secure. I've also seen people who should know better argue ferociously that moving the ssh port is all that is needed.