From: Kelly Setzer <Kelly.Setzer@placemark.com>
To: netfilter@lists.netfilter.org
Subject: iptables immutable
Date: Thu, 6 Feb 2003 19:44:37 -0600 [thread overview]
Message-ID: <20030207014437.GC28004@placemark.com> (raw)
We are in the process of implementing a firewall based on iptables.
Our basic implementation is laid out, and now we are searching for
every scrap that might improve security. One thing I'd like is the
ability to "lock" the iptables configuration so that no further
changes can be made (without rebooting).
I don't see that iptables supports that directly. I would be willing
to put my effort into such a project, although it's at the limits of
my expertise. I have been trying to think of a way to emulate this
behavior.
The only reasonable idea I've had is using Linux Capabilities:
http://www.kernel.org/pub/linux/libs/security/linux-privs/kernel-2.4/capfaq-0.2.txt
However, I'm not even sure how I'd apply that to iptables to prevent
changes to the iptables chains.
Thoughts?
Kelly
next reply other threads:[~2003-02-07 1:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 1:44 Kelly Setzer [this message]
2003-02-10 7:42 ` iptables immutable Cedric Blancher
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=20030207014437.GC28004@placemark.com \
--to=kelly.setzer@placemark.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