From: Chris Brenton <cbrenton@chrisbrenton.org>
To: netfilter <netfilter@lists.netfilter.org>
Subject: excellent rule archive
Date: Mon, 22 Dec 2003 07:37:42 -0500 [thread overview]
Message-ID: <1072096662.2076.323.camel@grendel> (raw)
Greets all,
I figure Bill is too shy to point out all the excellent work he's done,
but I thought list members would find it interesting. ;-)
Check out Bill's firebrick project:
http://www.stearns.org/firebricks/
Firebrick is a set of independent modules that are designed to plug-in
to an iptables firewall. Some of the cooler modules:
* Filter legal but unallocated source IPs (common in spoof attacks)
* Identify probing based on inbound scan patters as well as outbound
unreachables
* Check/record/drop odd packet sizes (like non-terminal fragments
smaller than 512 bytes).
* Filter out all loose and strict source route packets
* When suspicious patterns are detected, drop and log all traffic from
that IP for 30 seconds
* Log SSH traffic using non-stand ports (other than 22/TCP)
* Record internal servers by monitoring outbound SYN/ACKs
There are others, but you get the idea. IMHO there are some extremely
useful tweaks up there that people can use.
HTH,
C
reply other threads:[~2003-12-22 12:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1072096662.2076.323.camel@grendel \
--to=cbrenton@chrisbrenton.org \
--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