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: OpenSSH -- a way to block recurrent login failures? |
|---|---|
| Date: | Tue, 21 Sep 2004 20:15:55 -0400 |
So you want to block an IP address as opposed to locking a particular account, right? I don't know of any easy method to accomplish what you are trying to do other than something similar to what you described... Automating stuff like that is playing with fire though, for not a whole lot of benefit. Why not monitor the logs and have it page you when a certain number of login failures occur from a certain IP? That way you can log in and verify that the IP should be blocked, then you could do something like add a null route to the host, which is more effective than adding it to hosts.deny anyway... On Tue, 21 Sep 2004 10:02:22 -0400 (EDT), Victor Danilchenko <danilche@cs.umass.edu> wrote:
Hi,
We are looking for a way to temporarily block hosts from which
we receive a given number of sequential failed login attempts, not
necessarily within the same SSH session (so MaxAuthTries is not enough).
The best solution I could come up with so far would be to run OpenSSH
through TCPWrappers, and set up a log watcher daemon which would edit
/etc/hosts.deny on the fly based on the tracked number of failed logins
for each logged host.
Is there a better solution known for the sort of problems we
have been plagued with lately -- repeated brute-force crack attempts
from remote hosts? I looked on FreshMeat and I searched the mailing
lists, only to come up empty-handed.
Thanks in advance,
--
| Victor Danilchenko +---------------------+
| danilche@cs.umass.edu | He who laughs last, |
| CSCF | 5-4231 | thinks slowest. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Replacing User Authentication Method (with version), Greg Waltz |
|---|---|
| Next by Date: | Re: SSH hanging, Robert Hajime Lanning |
| Previous by Thread: | Re: OpenSSH -- a way to block recurrent login failures?, Alpt |
| Next by Thread: | Re: OpenSSH -- a way to block recurrent login failures?, Javier Sanchez |
| Indexes: | [Date] [Thread] [Top] [All Lists] |