From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Nik Trevallyn-Jones <nik@designer.com.au>
Cc: netfilter@lists.netfilter.org
Subject: Re: active firewall
Date: Tue, 23 Sep 2003 09:32:26 -0400 [thread overview]
Message-ID: <3F704B6A.7010905@chrisbrenton.org> (raw)
In-Reply-To: 03092320103102.01185@slinky.exmosys.com
Nik Trevallyn-Jones wrote:
>
> As a result of experiences deploying PortSentry behind an ipchains
> firewall recently, I started considering how iptables could be used to deploy
> a dynamic firewall which would be able to modify itself in response to
> predefined events.
Be very careful with this. I've seen savvy attackers spoof attacks from
the root name servers in order to make the firewall DoS the local
environment. :(
> Q: Has anyone considered or suggested this before?
Yup, and the feature is built into many commercial firewalls (FW-1, PIX,
etc.). I know Bill Stearns was working on this at one point. You might
be able to find more info at:
http://www.stearns.org
> 1 two new targets: ENLIST, DELIST
> These targets effectively cause one or more new rules to be automatically
> added/removed to/from the firewall in response to matching the associated
> rule.
Depending on your IDS, you can script this as well. I seem to remember a
paper floating around at one point that shows how to set this up with
Snort and iptables.
> I would like to write a rule which asserts: "BLACKLIST any host that sends a
> SYN packet to any ports between 1025-50000 unless there is a socket listening
> to the port at the time the packet arrives".
Hummm, so if I back door your system the firewall will happily update
the ruleset to permit me access to that port. That's very polite of it. ;-)
HTH,
C
next prev parent reply other threads:[~2003-09-23 13:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-23 13:26 active firewall Nik Trevallyn-Jones
2003-09-23 13:32 ` Chris Brenton [this message]
2003-09-23 14:07 ` Nik Trevallyn-Jones
2003-09-23 15:11 ` Mark Vevers
2003-09-23 21:19 ` Nik Trevallyn-Jones
2003-09-24 1:18 ` Jim Carter
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=3F704B6A.7010905@chrisbrenton.org \
--to=cbrenton@chrisbrenton.org \
--cc=netfilter@lists.netfilter.org \
--cc=nik@designer.com.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.