From: Paul Moore <paul.moore@hp.com>
To: Chad Hanson <chanson@TrustedCS.com>
Cc: James Morris <jmorris@namei.org>,
Venkat Yekkirala <vyekkirala@TrustedCS.com>,
Stephen Smalley <sds@tycho.nsa.gov>,
selinux@tycho.nsa.gov,
Karl MacMillan <kmacmillan@mentalrootkit.com>,
Joshua Brindle <method@manicmethod.com>
Subject: Re: [RFC] [PATCH 4/4] SELinux changes
Date: Thu, 20 Sep 2007 14:58:29 -0400 [thread overview]
Message-ID: <200709201458.29269.paul.moore@hp.com> (raw)
In-Reply-To: <27C0723414C58546B4084C2F17BE052A36655B@chaos.tcs.tcs-sec.com>
On Thursday, September 20 2007 2:50:55 pm Chad Hanson wrote:
> I agree performance could be an issue. I would suggest these checks are
> performed based on value /counter instead of the presence of labeled
> networking.
Personally I like the idea of using a counter/flag/toggle/etc to
enable/disable the checks but I believe there might be push back due to the
added user configuration burden (even though it would be rather small).
--
paul moore
linux security @ hp
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2007-09-20 18:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 18:50 [RFC] [PATCH 4/4] SELinux changes Chad Hanson
2007-09-20 18:58 ` Paul Moore [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-09-18 17:32 Venkat Yekkirala
2007-09-19 14:18 ` Stephen Smalley
2007-09-19 21:12 ` James Morris
2007-09-19 21:22 ` Venkatesh Yekkirala
2007-09-19 21:40 ` Paul Moore
2007-09-19 22:52 ` James Morris
2007-09-19 23:20 ` Paul Moore
2007-09-20 14:42 ` Venkatesh Yekkirala
2007-09-20 15:31 ` Paul Moore
2007-09-20 18:30 ` Paul Moore
2007-09-19 21:20 ` Venkatesh Yekkirala
2007-09-19 21:51 ` Paul Moore
2007-09-21 20:14 ` Paul Moore
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=200709201458.29269.paul.moore@hp.com \
--to=paul.moore@hp.com \
--cc=chanson@TrustedCS.com \
--cc=jmorris@namei.org \
--cc=kmacmillan@mentalrootkit.com \
--cc=method@manicmethod.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
--cc=vyekkirala@TrustedCS.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 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.