From: Michael Rash <mbr@cipherdyne.org>
To: netfilter@vger.kernel.org
Subject: psad-2.1 release + book announcement
Date: Thu, 25 Oct 2007 00:27:00 -0400 [thread overview]
Message-ID: <20071025042700.GC16759@minastirith> (raw)
Hi -
psad-2.1 has been released:
http://www.cipherdyne.org/psad/download/
This release finishes off the 2.0.x development series with a few bug
fixes and feature enhancements. For example, one bug was fixed in how psad
handles the options portion of the TCP header; it was previously possible
to force psad into an infinite loop with a specially crafted set of options
(logged by iptables with the --log-tcp-options command line argument when
building a LOG rule).
Here is the complete ChangeLog:
http://trac.cipherdyne.org/trac/psad/browser/psad/tags/psad-2.1/ChangeLog
Also, I have finished writing the book "Linux Firewalls: Attack Detection
and Response" for No Starch Press. It is available for a decent discount
off the Amazon.com price if you go through the No Starch site:
http://www.nostarch.com/frameset.php?startat=firewalls_mr
This book is as much about intrusion detection as it is about iptables,
and treats the two subjects in a unified fashion. There are lot of
books out there about intrusion detection, and lots more about firewalls,
but none that I'm aware of that really concentrate on the combination of
the two technologies. In this respect, it is my hope that this book is
unique.
There is also an online site for the book here:
http://www.cipherdyne.org/LinuxFirewalls/
For example, visualizations of iptables Honeynet log data can be viewed
(along with the parsed data sets produced by psad) here:
http://www.cipherdyne.org/LinuxFirewalls/ch14/
Thanks,
--
Michael Rash
http://www.cipherdyne.org/
Key fingerprint = 53EA 13EA 472E 3771 894F AC69 95D8 5D6B A742 839F
reply other threads:[~2007-10-25 4:27 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=20071025042700.GC16759@minastirith \
--to=mbr@cipherdyne.org \
--cc=netfilter@vger.kernel.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