<?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: Stopping SSH &amp; FTP brute force attacks with IPFW</title>
	<atom:link href="http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/</link>
	<description>Real Solutions to real FreeBSD problems.</description>
	<lastBuildDate>Tue, 04 Aug 2009 21:57:14 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
	<item>
		<title>By: Chris</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-49</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Tue, 21 Jul 2009 17:02:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-49</guid>
		<description>Glad to hear it. :)</description>
		<content:encoded><![CDATA[<p>Glad to hear it. :)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SoniXAnT</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-48</link>
		<dc:creator>SoniXAnT</dc:creator>
		<pubDate>Tue, 21 Jul 2009 08:30:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-48</guid>
		<description>Yessss, now it works!! The bruteblock line must be put at the top of syslog.conf as you said...strange issue nevertheless.</description>
		<content:encoded><![CDATA[<p>Yessss, now it works!! The bruteblock line must be put at the top of syslog.conf as you said&#8230;strange issue nevertheless.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-47</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Mon, 20 Jul 2009 16:49:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-47</guid>
		<description>Great tip, I couldn&#039;t have said it better myself. I found that putting the bruteblock line up the top of your syslog.conf file guarantees it will start correctly. Let me know how this goes for you.</description>
		<content:encoded><![CDATA[<p>Great tip, I couldn&#8217;t have said it better myself. I found that putting the bruteblock line up the top of your syslog.conf file guarantees it will start correctly. Let me know how this goes for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SoniXAnT</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-46</link>
		<dc:creator>SoniXAnT</dc:creator>
		<pubDate>Sun, 19 Jul 2009 20:06:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-46</guid>
		<description>Oops, sorry I meant:
tail -F -n1 /var/log/auth.log &#124; exec /usr/local/sbin/bruteblock -f /usr/local/etc/bruteblock/ssh.conf &amp;

do not forget the final \&amp;\ or else init will be stuck in the tail command from the next reboot</description>
		<content:encoded><![CDATA[<p>Oops, sorry I meant:<br />
tail -F -n1 /var/log/auth.log | exec /usr/local/sbin/bruteblock -f /usr/local/etc/bruteblock/ssh.conf &amp;</p>
<p>do not forget the final \&amp;\ or else init will be stuck in the tail command from the next reboot</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SoniXAnT</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-44</link>
		<dc:creator>SoniXAnT</dc:creator>
		<pubDate>Sun, 19 Jul 2009 19:59:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-44</guid>
		<description>Two tips for bruteblock:
1) ipfw acts as a &quot;firts match first win&quot; firewall so add the deny rule BEFORE any other ruleset
2) I can&#039;t understand why my syslogd doesn&#039;t recognize bruteblock from my syslog.conf, if this is your case, here is a workaround:
just add the following line to your /etc/rc.local

echo &quot;tail -F -n1 /var/log/auth.log &#124; exec /usr/local/sbin/bruteblock -f /usr/local/etc/bruteblock/ssh.conf &amp;&quot; &gt;&gt; /etc/rc.local

and reboot

hope this helps!</description>
		<content:encoded><![CDATA[<p>Two tips for bruteblock:<br />
1) ipfw acts as a &#8220;firts match first win&#8221; firewall so add the deny rule BEFORE any other ruleset<br />
2) I can&#8217;t understand why my syslogd doesn&#8217;t recognize bruteblock from my syslog.conf, if this is your case, here is a workaround:<br />
just add the following line to your /etc/rc.local</p>
<p>echo &#8220;tail -F -n1 /var/log/auth.log | exec /usr/local/sbin/bruteblock -f /usr/local/etc/bruteblock/ssh.conf &amp;&#8221; &gt;&gt; /etc/rc.local</p>
<p>and reboot</p>
<p>hope this helps!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chris</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-39</link>
		<dc:creator>Chris</dc:creator>
		<pubDate>Fri, 03 Jul 2009 06:52:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-39</guid>
		<description>Send me your ssh.conf (bruteblock), rc.firewall (ipfw) and you syslog.conf (syslogd) and I&#039;ll take a look for you. chris [at] reallfreebsdtips [dot] com</description>
		<content:encoded><![CDATA[<p>Send me your ssh.conf (bruteblock), rc.firewall (ipfw) and you syslog.conf (syslogd) and I&#8217;ll take a look for you. chris [at] reallfreebsdtips [dot] com</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James S</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-38</link>
		<dc:creator>James S</dc:creator>
		<pubDate>Fri, 03 Jul 2009 01:44:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-38</guid>
		<description>I&#039;m not familiar with ipfw, since I don&#039;t need or want a firewall for any other reason than to use BruteBlock.  I keep getting a:

bruteblock[1083]: Blocking failed for (my test attacking IP)

I am running firewall_type=&quot;OPEN&quot;, because as I said, I really don&#039;t want to have IPFW interfering with anything else.  If I do a: ipfw table 1 list, I do see the same test IP listed, but it is not being blocked.

I&#039;d appreciate a clue or two...if I need to run the firewall differently, how best to do that as simply as possible.

Thanks!</description>
		<content:encoded><![CDATA[<p>I&#8217;m not familiar with ipfw, since I don&#8217;t need or want a firewall for any other reason than to use BruteBlock.  I keep getting a:</p>
<p>bruteblock[1083]: Blocking failed for (my test attacking IP)</p>
<p>I am running firewall_type=&#8221;OPEN&#8221;, because as I said, I really don&#8217;t want to have IPFW interfering with anything else.  If I do a: ipfw table 1 list, I do see the same test IP listed, but it is not being blocked.</p>
<p>I&#8217;d appreciate a clue or two&#8230;if I need to run the firewall differently, how best to do that as simply as possible.</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: KC</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-37</link>
		<dc:creator>KC</dc:creator>
		<pubDate>Fri, 17 Apr 2009 10:10:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-37</guid>
		<description>Thanks for the information! It helps a lot!</description>
		<content:encoded><![CDATA[<p>Thanks for the information! It helps a lot!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: dr.hoffman</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-33</link>
		<dc:creator>dr.hoffman</dc:creator>
		<pubDate>Fri, 27 Mar 2009 08:45:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-33</guid>
		<description>*Please, Disregard previous post*
Great article - Thanx!
Very Helpful! 
Please, note that string:
add deny ip from table(1) to any  
Should look like: 
add deny ip from table\(1\ )to any   
-- with reverse slashes</description>
		<content:encoded><![CDATA[<p>*Please, Disregard previous post*<br />
Great article &#8211; Thanx!<br />
Very Helpful!<br />
Please, note that string:<br />
add deny ip from table(1) to any<br />
Should look like:<br />
add deny ip from table\(1\ )to any<br />
&#8211; with reverse slashes</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kevin</title>
		<link>http://www.realfreebsdtips.com/security/stopping-ssh-ftp-brute-force-attacks-with-ipfw/comment-page-1/#comment-30</link>
		<dc:creator>Kevin</dc:creator>
		<pubDate>Thu, 12 Mar 2009 21:21:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.realfreebsdtips.com/?p=6#comment-30</guid>
		<description>I&#039;m using a different method: change ports for ssh/ftp (make it over 8000), also configure:
net.inet.tcp.blackhole=2
net.inet.udp.blackhole=1
in /etc/sysctl.conf

The automate scans are completely eliminated.

I have blogged it, you can search the posts on my blog.</description>
		<content:encoded><![CDATA[<p>I&#8217;m using a different method: change ports for ssh/ftp (make it over 8000), also configure:<br />
net.inet.tcp.blackhole=2<br />
net.inet.udp.blackhole=1<br />
in /etc/sysctl.conf</p>
<p>The automate scans are completely eliminated.</p>
<p>I have blogged it, you can search the posts on my blog.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
