From: Joshua Brindle <method@manicmethod.com>
To: Paul Moore <paul.moore@hp.com>
Cc: vyekkirala@TrustedCS.com, KaiGai Kohei <kaigai@kaigai.gr.jp>,
KaiGai Kohei <kaigai@ak.jp.nec.com>,
Stephen Smalley <sds@tycho.nsa.gov>, Joe Nall <joe@nall.com>,
SELinux Mail List <selinux@tycho.nsa.gov>,
ewalsh@tycho.nsa.gov
Subject: Re: generic fallbacks of getpeercon (Re: [redhat-lspp] Labeling an interface)
Date: Wed, 06 Jun 2007 17:19:26 -0400 [thread overview]
Message-ID: <466724DE.4010302@manicmethod.com> (raw)
In-Reply-To: <200706061648.37402.paul.moore@hp.com>
Paul Moore wrote:
> On Wednesday, June 6 2007 4:31:51 pm Joshua Brindle wrote:
>
>>> The proposal here is to introduce a static external label for single
>>> label networks where the remote domain is not explicitly labeling it's
>>> network traffic. This is a common request from people with existing
>>> trusted OS installations and would be a nice compliment to the existing
>>> labeling mechanisms, both internal and external.
>>>
>> Is this info going to be stored in the policy ala ocontexts? How are you
>> planning to manage it? Adding it to libsemanage and semanage seems like
>> the best route to take here.
>>
>
> As I envision it right now this new static external label would be managed via
> NetLabel (it is a framework after all, not just CIPSO) so we wouldn't need to
> introduce any more per-packet access checks, similar to how
> iptables/netfilter manages the SECMARK labels. The impact to the SELinux
> kernel code should be quite minimal using this approach.
>
> Policy integration is still open in my mind, although considering the lessons
> learned from integrating the SECMARK iptables commands into policy I wonder
> if we are best off leaving the labeling details out of the policy itself and
> leaving it in the hands of the NetLabel tools and perhaps libsemanage.
>
I'm fine with that, I didn't even think about the netlabel tools
handling it (possibly because I never used them ;) )
The unfortunate part is that we are going to have all these systems for
managing different kinds of external labels, it would be nice if there
was a centralized management system, even if the backends are spread all
over the place. I don't mean a GUI here either (not that a GUI would be
bad) but more along the lines of a central management library that can
handle it all that a GUI could later use. I'm not sure if libsemanage is
the place for this either, particularly with ipsec where management
really means updating SPD entries to have contexts, I don't know how
people currently manage SPD entries so I'm not sure where we can
interject ourselves without disturbing users..
--
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-06-06 21:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <C32347D4-3E32-4741-B847-6826EED3BB7A@nall.com>
[not found] ` <1180631739.3340.309.camel@moss-spartans.epoch.ncsc.mil>
2007-06-02 17:46 ` generic fallbacks of getpeercon (Re: [redhat-lspp] Labeling an interface) KaiGai Kohei
2007-06-04 10:52 ` KaiGai Kohei
2007-06-04 14:17 ` Stephen Smalley
2007-06-04 19:28 ` Paul Moore
2007-06-06 3:12 ` KaiGai Kohei
2007-06-06 11:45 ` Paul Moore
2007-06-06 13:38 ` Venkat Yekkirala
2007-06-06 13:47 ` Paul Moore
2007-06-06 14:28 ` Stephen Smalley
2007-06-06 17:25 ` KaiGai Kohei
2007-06-06 17:34 ` Stephen Smalley
2007-06-06 17:52 ` KaiGai Kohei
2007-06-06 18:01 ` Stephen Smalley
2007-06-06 18:37 ` Venkat Yekkirala
2007-06-06 18:47 ` Stephen Smalley
2007-06-06 17:23 ` KaiGai Kohei
2007-06-06 17:42 ` Paul Moore
2007-06-06 18:32 ` Venkat Yekkirala
2007-06-06 19:37 ` Paul Moore
2007-06-06 20:31 ` Joshua Brindle
2007-06-06 20:48 ` Paul Moore
2007-06-06 21:19 ` Joshua Brindle [this message]
2007-06-06 21:34 ` Paul Moore
2007-06-06 21:39 ` Eamon Walsh
2007-06-07 6:55 ` KaiGai Kohei
2007-06-07 7:42 ` KaiGai Kohei
2007-06-07 11:51 ` Paul Moore
2007-06-07 14:10 ` KaiGai Kohei
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=466724DE.4010302@manicmethod.com \
--to=method@manicmethod.com \
--cc=ewalsh@tycho.nsa.gov \
--cc=joe@nall.com \
--cc=kaigai@ak.jp.nec.com \
--cc=kaigai@kaigai.gr.jp \
--cc=paul.moore@hp.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.