All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jason Opperisano <opie@817west.com>
To: netfilter@lists.netfilter.org
Subject: Re: Possibility to lock iptables rules.
Date: Wed, 20 Apr 2005 18:01:23 -0400	[thread overview]
Message-ID: <20050420220123.GA25652@bender.817west.com> (raw)
In-Reply-To: <20050420184753.GA25069@bender.817west.com>

On Wed, Apr 20, 2005 at 02:47:53PM -0400, Jason Opperisano wrote:
> i'm guessing you're thinking about how the *BSD's have a concept of
> kern.securelevel, and certain things (like firewall rules) become
> immutable; even by root, at certain levels.
> 
> i'm not a kernel programmer, but i can tell you that the linux kernel
> doesn't have anything like kern.securelevel; and without it, i don't
> believe what you're asking for is possible.  i'd also figure that
> implementing kern.securelevel in the linux kernel would be beyond the
> scope of what the netfilter developers are responsible for.

after pondering this further (post-post, natch)...i had a thought 
(yes--it hurt).  you could probably use SELinux to achieve this.  the
minimal benefits that others have pointed out, and the overly complex
nature of SELinux probably yields a pretty low benefit/cost ratio,
though.

just a thought...

-j

--
"Peter: Wow, is that really the blood of Christ?
 Preacher: Yes, it is.
 Peter: Holy crap, that guy must've been wasted 24 hours a day."
        --Family Guy


  reply	other threads:[~2005-04-20 22:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-20 10:49 Possibility to lock iptables rules Anders Fugmann
2005-04-20 16:40 ` Taylor, Grant
2005-04-20 20:56   ` Anders Peter Fugmann
2005-04-20 22:13     ` Taylor, Grant
2005-04-21 13:53     ` Jozsef Kadlecsik
2005-04-20 18:47 ` Jason Opperisano
2005-04-20 22:01   ` Jason Opperisano [this message]
2005-04-20 22:16     ` Taylor, Grant
2005-04-20 21:02 ` R. DuFresne

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=20050420220123.GA25652@bender.817west.com \
    --to=opie@817west.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 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.