From: Stephen Smalley <sds@tycho.nsa.gov>
To: peter enderborg <peter.enderborg@sonymobile.com>,
"selinux@tycho.nsa.gov" <selinux@tycho.nsa.gov>
Subject: Re: Missing security labels for socket objects?
Date: Tue, 04 Nov 2014 09:01:27 -0500 [thread overview]
Message-ID: <5458DC37.50903@tycho.nsa.gov> (raw)
In-Reply-To: <54588F41.9050507@sonymobile.com>
On 11/04/2014 03:33 AM, peter enderborg wrote:
> Is there any work going on the make it more granular? I did not see
> it in the "Remaning Work" backlog. It is a generic problem and should
> have a generic solution.
It is on the new kernel to-do list, at the bottom of new items on:
https://github.com/SELinuxProject/selinux/wiki/Kernel-Todo
However, I'm not sure what the general solution would look like. I
don't think we want to write policies on socket (domain, type, protocol)
triples or introduce unique security classes for every such triple. The
security class abstraction in SELinux (and its underlying Flask
architecture) is intended to provide a higher level abstraction for
security policy writers.
next prev parent reply other threads:[~2014-11-04 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-30 16:37 Missing security labels for socket objects? peter enderborg
2014-10-30 17:06 ` Stephen Smalley
2014-11-04 8:33 ` peter enderborg
2014-11-04 14:01 ` Stephen Smalley [this message]
2014-11-04 14:28 ` peter enderborg
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=5458DC37.50903@tycho.nsa.gov \
--to=sds@tycho.nsa.gov \
--cc=peter.enderborg@sonymobile.com \
--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.