<?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"
	>
<channel>
	<title>Comments on: Security Tip: Defending against brute force ssh attacks</title>
	<atom:link href="http://fatpenguinblog.com/weinerdoodz/security-tip-defending-against-brute-force-ssh-attacks/feed/" rel="self" type="application/rss+xml" />
	<link>http://fatpenguinblog.com/weinerdoodz/security-tip-defending-against-brute-force-ssh-attacks/</link>
	<description>Donkies Bloggin' for Donkies</description>
	<pubDate>Sat, 11 Oct 2008 14:41:14 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Scott Rippee</title>
		<link>http://fatpenguinblog.com/weinerdoodz/security-tip-defending-against-brute-force-ssh-attacks/#comment-10538</link>
		<dc:creator>Scott Rippee</dc:creator>
		<pubDate>Fri, 08 Jun 2007 07:33:31 +0000</pubDate>
		<guid isPermaLink="false">http://fatpenguinblog.com/weinerdoodz/security-tip-defending-against-brute-force-ssh-attacks/#comment-10538</guid>
		<description>Ahhhh very interesting.  I especially like the knockd trick.

I can't believe that they didn't mention:

1. Never run sshd on port 22.  Autonomous bots will always find you and run through large sets of passwords trying to break in.  I've seen my server logging hundreds upon hundreds of these a day.  Every client allows port specification, so take advantage of it.

2.  There is no reason to leave sshd and other personal services sitting out there visible to the public.  Setup a VPN, it's not so tough.  Bind your non public services to only the VPN address.</description>
		<content:encoded><![CDATA[<p>Ahhhh very interesting.  I especially like the knockd trick.</p>
<p>I can&#8217;t believe that they didn&#8217;t mention:</p>
<p>1. Never run sshd on port 22.  Autonomous bots will always find you and run through large sets of passwords trying to break in.  I&#8217;ve seen my server logging hundreds upon hundreds of these a day.  Every client allows port specification, so take advantage of it.</p>
<p>2.  There is no reason to leave sshd and other personal services sitting out there visible to the public.  Setup a VPN, it&#8217;s not so tough.  Bind your non public services to only the VPN address.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
