Re: ssh brute force

From: Simon *** (simond_at_irrelevant.org)
Date: 07/26/05

  • Next message: Bill Vermillion: "Re: preventing a user to start a process" 
    To: Andrew McNaughton <andrew@scoop.co.nz>
Date: Tue, 26 Jul 2005 09:33:27 +0100

    On Tue, 2005-07-26 at 17:52 +1200, Andrew McNaughton wrote:
    > 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.

    security/swatch perhaps? 

    -- 
Simon *** <simond@irrelevant.org>
_______________________________________________
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"
  • Next message: Bill Vermillion: "Re: preventing a user to start a process"