<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: HowTo: Find SSH Hackers IP&#8217;s in a jiffy</title>
	<atom:link href="http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/feed/" rel="self" type="application/rss+xml" />
	<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/</link>
	<description>return of the men in black</description>
	<pubDate>Thu, 11 Mar 2010 15:58:54 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Techs Or More &#187; HowTo: Find SSH Hackers&#8217; IPs Fast</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-7814</link>
		<dc:creator>Techs Or More &#187; HowTo: Find SSH Hackers&#8217; IPs Fast</dc:creator>
		<pubDate>Tue, 06 Nov 2007 15:42:27 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-7814</guid>
		<description>[...] read more &#124; digg story [...]</description>
		<content:encoded><![CDATA[<p>[...] read more | digg story [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: krkosska</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-55</link>
		<dc:creator>krkosska</dc:creator>
		<pubDate>Sat, 14 Oct 2006 20:36:20 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-55</guid>
		<description>I firewall port 22 and use a variant of popauth to open that port to specific users when they successfully check email. Of course, the server doesn't have to accept mail for them...</description>
		<content:encoded><![CDATA[<p>I firewall port 22 and use a variant of popauth to open that port to specific users when they successfully check email. Of course, the server doesn&#8217;t have to accept mail for them&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Loren</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-54</link>
		<dc:creator>Loren</dc:creator>
		<pubDate>Sat, 14 Oct 2006 17:30:04 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-54</guid>
		<description>You could also shorten that 'awk' command to:
awk '/failed/{print $9}' /var/log/auth.log</description>
		<content:encoded><![CDATA[<p>You could also shorten that &#8216;awk&#8217; command to:<br />
awk &#8216;/failed/{print $9}&#8217; /var/log/auth.log</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-53</link>
		<dc:creator>James</dc:creator>
		<pubDate>Sat, 14 Oct 2006 16:26:33 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-53</guid>
		<description>Or, a better way is to to strict iptables firewall rules on rate limiting, and/or source/dest and if at all possible implement a port knocker.

Example of iptables script that drops new connections after 7 attempts in 30 seconds(this is off memory, sorry if it doesn't work...look @ manpage for more info):
iptables -A INPUT -p tcp -m tcp --dport 22 -m state --state NEW -m recent --set --name DEFAULT --rsource
iptables -A INPUT -p tcp -m tcp --dport 22 -m state --state NEW -m recent --update --seconds 30 --hitcount 7 --name DEFAULT --rsource -j DROP


Some articles on port knocking:
http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/
http://gentoo-wiki.com/HOWTO_autossh_and_knockd</description>
		<content:encoded><![CDATA[<p>Or, a better way is to to strict iptables firewall rules on rate limiting, and/or source/dest and if at all possible implement a port knocker.</p>
<p>Example of iptables script that drops new connections after 7 attempts in 30 seconds(this is off memory, sorry if it doesn&#8217;t work&#8230;look @ manpage for more info):<br />
iptables -A INPUT -p tcp -m tcp &#8211;dport 22 -m state &#8211;state NEW -m recent &#8211;set &#8211;name DEFAULT &#8211;rsource<br />
iptables -A INPUT -p tcp -m tcp &#8211;dport 22 -m state &#8211;state NEW -m recent &#8211;update &#8211;seconds 30 &#8211;hitcount 7 &#8211;name DEFAULT &#8211;rsource -j DROP</p>
<p>Some articles on port knocking:<br />
<a href="http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/" rel="nofollow">http://www.ducea.com/2006/07/05/how-to-safely-connect-from-anywhere-to-your-closed-linux-firewall/</a><br />
<a href="http://gentoo-wiki.com/HOWTO_autossh_and_knockd" rel="nofollow">http://gentoo-wiki.com/HOWTO_autossh_and_knockd</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: harl</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-51</link>
		<dc:creator>harl</dc:creator>
		<pubDate>Sat, 14 Oct 2006 13:39:02 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-51</guid>
		<description>Have a look at denyhosts and forget about it: http://denyhosts.sourceforge.net/

Works out-of-the-box for most distributions.</description>
		<content:encoded><![CDATA[<p>Have a look at denyhosts and forget about it: <a href="http://denyhosts.sourceforge.net/" rel="nofollow">http://denyhosts.sourceforge.net/</a></p>
<p>Works out-of-the-box for most distributions.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: converter</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-49</link>
		<dc:creator>converter</dc:creator>
		<pubDate>Sat, 14 Oct 2006 12:18:43 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-49</guid>
		<description>Five point penalty for unnecessary use of cat. :)

zegrep refused auth.log*

cat(1) is for concatenating text files:

cat file1 file2 file3 &gt; file4

and etc.

Most of the standard unix text processing utilities will open and read from one or more files passed on the command line (just like cat does), iterating over their lines as if they were a single file.

What's the point? Even though the time and energy I've just devoted to this post may suggest otherwise, I hate unnecessary typing, and one less cat process means slightly lower resource usage.</description>
		<content:encoded><![CDATA[<p>Five point penalty for unnecessary use of cat. <img src='http://azio.org/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>zegrep refused auth.log*</p>
<p>cat(1) is for concatenating text files:</p>
<p>cat file1 file2 file3 &gt; file4</p>
<p>and etc.</p>
<p>Most of the standard unix text processing utilities will open and read from one or more files passed on the command line (just like cat does), iterating over their lines as if they were a single file.</p>
<p>What&#8217;s the point? Even though the time and energy I&#8217;ve just devoted to this post may suggest otherwise, I hate unnecessary typing, and one less cat process means slightly lower resource usage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lizer</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-48</link>
		<dc:creator>Lizer</dc:creator>
		<pubDate>Sat, 14 Oct 2006 10:10:25 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-48</guid>
		<description>I wrote two scripts that do something similar some time ago:

http://lizer.syslinx.org/temporary/failog
http://lizer.syslinx.org/temporary/lognames

Usage:
zcat /var/log/authlog*gz &#124; cat - /var/log/authlog &#124; ./failog [date&#124;host]
Counts the failed logins grouped by date/attacker ip.

zcat /var/log/authlog*gz &#124; cat - /var/log/authlog &#124; ./lognames
Lists the login names and how often each has tried.</description>
		<content:encoded><![CDATA[<p>I wrote two scripts that do something similar some time ago:</p>
<p><a href="http://lizer.syslinx.org/temporary/failog" rel="nofollow">http://lizer.syslinx.org/temporary/failog</a><br />
<a href="http://lizer.syslinx.org/temporary/lognames" rel="nofollow">http://lizer.syslinx.org/temporary/lognames</a></p>
<p>Usage:<br />
zcat /var/log/authlog*gz | cat - /var/log/authlog | ./failog [date|host]<br />
Counts the failed logins grouped by date/attacker ip.</p>
<p>zcat /var/log/authlog*gz | cat - /var/log/authlog | ./lognames<br />
Lists the login names and how often each has tried.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Icheb</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-46</link>
		<dc:creator>Icheb</dc:creator>
		<pubDate>Sat, 14 Oct 2006 09:10:30 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-46</guid>
		<description>You can find a script capable of adding iptables entries for found ssh attacks at http://blinkeye.ch/mediawiki/index.php/SSH_Blocking.

I've used this on a few hosts, it's relatively easy to install, although you sometimes have to change the detection a bit (find another word, ip address being just another word...). But it runs very well ;).

Furthermore you can also change your SSH port if you hate receiving large logwatch e-mails, or you can deinstall logwatch...</description>
		<content:encoded><![CDATA[<p>You can find a script capable of adding iptables entries for found ssh attacks at <a href="http://blinkeye.ch/mediawiki/index.php/SSH_Blocking" rel="nofollow">http://blinkeye.ch/mediawiki/index.php/SSH_Blocking</a>.</p>
<p>I&#8217;ve used this on a few hosts, it&#8217;s relatively easy to install, although you sometimes have to change the detection a bit (find another word, ip address being just another word&#8230;). But it runs very well ;).</p>
<p>Furthermore you can also change your SSH port if you hate receiving large logwatch e-mails, or you can deinstall logwatch&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: aaron</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-45</link>
		<dc:creator>aaron</dc:creator>
		<pubDate>Sat, 14 Oct 2006 08:36:21 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-45</guid>
		<description>Neat article.  Try DenyHosts, it basically does the same thing but automatically forwards all sshd hackers to your hosts.deny file. See http://denyhosts.sourceforge.net/</description>
		<content:encoded><![CDATA[<p>Neat article.  Try DenyHosts, it basically does the same thing but automatically forwards all sshd hackers to your hosts.deny file. See <a href="http://denyhosts.sourceforge.net/" rel="nofollow">http://denyhosts.sourceforge.net/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christian</title>
		<link>http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/comment-page-1/#comment-44</link>
		<dc:creator>Christian</dc:creator>
		<pubDate>Sat, 14 Oct 2006 08:08:00 +0000</pubDate>
		<guid isPermaLink="false">http://azio.org/2006/10/13/howto-find-ssh-hackers-ips-in-a-jiffy/#comment-44</guid>
		<description>Funny that "root" isn't in the list. That's the account I'd go for... :&gt;</description>
		<content:encoded><![CDATA[<p>Funny that &#8220;root&#8221; isn&#8217;t in the list. That&#8217;s the account I&#8217;d go for&#8230; :&gt;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
