Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Dimitri Yioulos <dyioulos@firstbhph.com>
To: netfilter@lists.netfilter.org
Subject: Re: Looking for automation scripts
Date: Fri, 5 Jan 2007 14:48:29 -0500	[thread overview]
Message-ID: <200701051448.30522.dyioulos@firstbhph.com> (raw)
In-Reply-To: <LJELKDOLLLOLLEFCCMCFAEGHEIAA.tim@heagarty.com>

On Friday 05 January 2007 2:44 pm, Tim Heagarty wrote:
> I've seen a few references here to scripts that monitor attacks and
> dynamically update iptables rules to knock down the attacks. Can anyone
> provide some good research starting points or sample scripts that they use?
> I've found a few things with google but respect the collective out here
> much more.
>
>
> Thank you,
>
> Tim Heagarty, CISSP, CISA, MCSE
> http://www.TheaSecure.com/
> (928) 533-9690
> "There are 10 kinds of people in the world; those that understand binary,
> and those that don't."
>
> --
> No virus found in this outgoing message.
> Checked by AVG Free Edition.
> Version: 7.5.432 / Virus Database: 268.16.5/616 - Release Date: 1/4/2007
> 1:34 PM

Something like psad (www.cipherdyne.com/psad/)?

Dimitri

-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.



  reply	other threads:[~2007-01-05 19:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-05 19:44 Looking for automation scripts Tim Heagarty
2007-01-05 19:48 ` Dimitri Yioulos [this message]
2007-01-05 21:20   ` Jan Engelhardt
2007-01-06  5:05 ` markee
2007-01-06  7:00   ` Andrew
2007-01-06 14:35   ` Jan Engelhardt
2007-01-06 15:27     ` Michael Rash
     [not found]       ` <0dd44240578edb703165547e121ceb7c@afm-koeln.de>
2007-01-06 23:20         ` William Perry
  -- strict thread matches above, loose matches on Subject: below --
2007-01-06 14:55 Tim Evans

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200701051448.30522.dyioulos@firstbhph.com \
    --to=dyioulos@firstbhph.com \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox