Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: Banning SSH attackers |
|---|---|
| Date: | Fri, 21 Oct 2005 12:12:09 -0700 |
On Thu, Oct 20, 2005 at 11:42:24AM -0600, Paul Berube wrote:
What I'd like is a system configuration where I just drop all packets from hosts that cause one of these messages for the next, say, 5 min. This way, a login failure from a legitimate user is not a catastrophic event for them, but greatly limits the ability of attackers to hammer on
I didn't find anything to do this either, so I wrote it a while back. Meant to post it on freshmeat but didn't get time to. The firewall rules are written for linux/iptables, so you can easily adjust them for other systems, feel free to send me patches. -nate
tailauth_dist.pl
Description: Text Data
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Banning SSH attackers, Raphaël Marichez |
|---|---|
| Next by Date: | Re: Banning SSH attackers, calvin |
| Previous by Thread: | Re: Banning SSH attackers, Raphaël Marichez |
| Next by Thread: | Re: Banning SSH attackers, calvin |
| Indexes: | [Date] [Thread] [Top] [All Lists] |