From: Paul Moore <paul.moore@hp.com>
To: Brian Sniffen <bsniffen@mitre.org>
Cc: selinux@tycho.nsa.gov
Subject: Re: Network access controls (resolving xfrm, secmark, and NetLabel)
Date: Tue, 09 May 2006 11:59:19 -0400 [thread overview]
Message-ID: <4460BC57.5020608@hp.com> (raw)
In-Reply-To: <m2zmhr5i6o.fsf@raven-king.mitre.org>
Brian Sniffen wrote:
> Paul Moore <paul.moore@hp.com> writes:
>>If we could do everything in netfilter then I agree with you
>>completely.
>
> Agree with me? I didn't think I was making a point yet.
Then perhaps I simply read too much into your mail, although I suspect it
doesn't matter too much for the discussion at hand.
> I'm just curious how many degrees of freedom NetLabel has, and what costs will
> be borne elsewhere in the system. From this sort of answer, should I
> assume that the costs will be high---but necessary for CIPSO and
> similar complexities?
I'm assuming when you say "cost" you are talking about the amount of time and
effort needed to understand the implementation so that a certain level of
assurance can be reached? If that is the case, then yes, I believe there is a
relatively higher cost involved with something like CIPSO due to it's very
nature. To some extent NetLabel may inherit some of this cost as a framework
designed to handle more complex labeling mechanisms.
As for the cost itself, I can only speak in relative terms and only from a
developer's point of view. Based on your email address and your presentations I
suspect you have quite a bit of background in this area; I encourage you to not
assume to much from my answers here but to look at the patch itself. Any
comments you may have about how to increase the ease at which higher levels of
assurance might be achieved would be very welcome.
--
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.
prev parent reply other threads:[~2006-05-09 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 16:27 Network access controls (resolving xfrm, secmark, and NetLabel) Paul Moore
2006-05-09 14:35 ` Brian Sniffen
2006-05-09 15:10 ` Paul Moore
2006-05-09 15:30 ` Brian Sniffen
2006-05-09 15:59 ` Paul Moore [this message]
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=4460BC57.5020608@hp.com \
--to=paul.moore@hp.com \
--cc=bsniffen@mitre.org \
--cc=selinux@tycho.nsa.gov \
/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.