Re: ssh brute force
From: Andrew McNaughton (andrew_at_scoop.co.nz)
Date: 07/26/05
- Previous message: mdff: "RE: preventing a user to start a process"
- In reply to: Andreas Pettersson: "Re: ssh brute force"
- Next in thread: Simon ***: "Re: ssh brute force"
- Reply: Simon ***: "Re: ssh brute force"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 26 Jul 2005 17:52:14 +1200 (NZST) To: Andreas Pettersson <andpet@telia.com>
On Mon, 25 Jul 2005, Andreas Pettersson wrote:
> Daniel Gerzo wrote:
>
> And here is another one, similar to Daniel's, but this one uses ipfw instead,
> AND another neat thing is that a block isn't permanent. There's a janitor
> cleaning up ipfw rules after a specified time.
>
> http://anp.ath.cx/s***/
>
> I made it the other day, so I haven't had time to hardcore test it.
> Let me know if it's not working, or if it is ;-)
>
Rather than having a whole bunch of processes running doing this sort of
thing, at least some of which are important enough to need monitoring
themselves (eg in my case pop based smtp authentication), it would be nice
to have a single process monitoring log activity, with some sort of plugin
system for adding various functionality for monitoring different things
and taking various actions.
Anyone know of such a beast? Perl preferred.
Andrew McNaughton
_______________________________________________
freebsd-isp@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-isp
To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"
- Previous message: mdff: "RE: preventing a user to start a process"
- In reply to: Andreas Pettersson: "Re: ssh brute force"
- Next in thread: Simon ***: "Re: ssh brute force"
- Reply: Simon ***: "Re: ssh brute force"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]