From: Christopher Soghoian <chris@dubfire.net>
To: netfilter-devel@lists.netfilter.org
Subject: Netfilter logging from the kernel
Date: Wed, 14 Jul 2004 13:21:28 +0100 [thread overview]
Message-ID: <20040714132128.A30620@sphinx.mythic-beasts.com> (raw)
Hi all,
We're working on a project here @ IBM Zurich, that will most likely
involve some netfilter stuff.
We're interested in locking down machines, in an attempt to
limit what a hacker can do if he is able to break into them.
All of these machines will have a iptables firewall in place,
limiting the outbound traffic.
Thus, the first thing an attacker would do after breaking in
would be to attempt to remove the firewall rules.
While we cannot defend against this, assuming he has gained root
access, we would at least like to make the machine tamper evident.
Initially, we thought that we could modify the iptables binary to
print out something to syslog every time a change to the rules
is made - however, it would be easy enough for the attacker to
copy over a virgin copy of iptables.
Thus, the logging code must be in the kernel, and not in the
iptables binary.
We would ideally like to see a log message sent to the
syslog every time an iptables rule is added/modified/removed.
Does anyone know if there is anything in place right now that
would allow this?
If nothing exists, how difficult would it be to whip something
like this up? Could you point me to the right part of the code
where I'd need to add my additional functionality.
Cheers,
Chris
next reply other threads:[~2004-07-14 12:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-14 12:21 Christopher Soghoian [this message]
2004-07-15 22:10 ` Netfilter logging from the kernel Roberto Nibali
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=20040714132128.A30620@sphinx.mythic-beasts.com \
--to=chris@dubfire.net \
--cc=netfilter-devel@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 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.