From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Possibility to lock iptables rules.
Date: Wed, 20 Apr 2005 17:16:00 -0500 [thread overview]
Message-ID: <4266D4A0.2000706@riverviewtech.net> (raw)
In-Reply-To: <20050420220123.GA25652@bender.817west.com>
> 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.
<smart a$$ comment>Want some ice?</smart a$$ comment>
Eh, the benefit / cost ratio might be low, but we are hackers and we do what we do for the challenge / fun / bragging rights of it.
Grant. . . .
next prev parent reply other threads:[~2005-04-20 22:16 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
2005-04-20 22:16 ` Taylor, Grant [this message]
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=4266D4A0.2000706@riverviewtech.net \
--to=gtaylor@riverviewtech.net \
--cc=netfilter@lists.netfilter.org \
--cc=opie@817west.com \
/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