<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to 5: LogCheck: Perform action</title><link>https://sourceforge.net/p/sentrytools/feature-requests/5/</link><description>Recent changes to 5: LogCheck: Perform action</description><atom:link href="https://sourceforge.net/p/sentrytools/feature-requests/5/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 02 May 2007 15:33:34 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/sentrytools/feature-requests/5/feed.rss" rel="self" type="application/rss+xml"/><item><title>LogCheck: Perform action</title><link>https://sourceforge.net/p/sentrytools/feature-requests/5/</link><description>&lt;div class="markdown_content"&gt;&lt;p&gt;Some blatent hacking attempts picked up by Logcheck would be best served by pulling some of the blackhole aspects from portsentry and having LogCheck automaticaly blackhole IP addresses.  Threshold would be nice, but in general I am willing to blackhole anyone who fatfingers a ssh password to keep out the ssh scanners.&lt;/p&gt;
&lt;p&gt;sshd[18015]: Failed password for invalid user webmaster from 83.166.32.126 port 34357 ssh2&lt;/p&gt;
&lt;p&gt;mulitiple the above by 100 or so with different users and that would be what I want to blackhole&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Wed, 02 May 2007 15:33:34 -0000</pubDate><guid>https://sourceforge.net94c9f189d3c49ec85289d4de215ef8192fb14e83</guid></item></channel></rss>