From: Dominick Grift <dac.override@gmail.com>
To: selinux@tycho.nsa.gov
Subject: Re: [PATCH] selinux: enable per-file labeling for debugfs files.
Date: Wed, 20 May 2015 17:51:37 +0200 [thread overview]
Message-ID: <20150520155135.GA30612@x131e> (raw)
In-Reply-To: <1432064766-30354-1-git-send-email-sds@tycho.nsa.gov>
[-- Attachment #1: Type: text/plain, Size: 956 bytes --]
On Tue, May 19, 2015 at 03:46:06PM -0400, Stephen Smalley wrote:
> Add support for per-file labeling of debugfs files so that
> we can distinguish them in policy. This is particularly
> important in Android where certain debugfs files have to be writable
> by apps and therefore the debugfs directory tree can be read and
> searched by all.
>
> Since debugfs is entirely kernel-generated, the directory tree is
> immutable by userspace, and the inodes are pinned in memory, we can
> simply use the same approach as with proc and label the inodes from
> policy based on pathname from the root of the debugfs filesystem.
> Generalize the existing labeling support used for proc and reuse it
> for debugfs too.
Was there a compelling reason not to implement something similar for /sys?
--
02DFF788
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
http://keys.gnupg.net/pks/lookup?op=vindex&search=0x314883A202DFF788
Dominick Grift
[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]
next prev parent reply other threads:[~2015-05-20 15:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-19 19:46 [PATCH] selinux: enable per-file labeling for debugfs files Stephen Smalley
2015-05-20 15:51 ` Dominick Grift [this message]
2015-05-20 15:59 ` Stephen Smalley
2015-05-20 16:04 ` Dominick Grift
2015-05-20 16:13 ` Stephen Smalley
2015-05-20 16:20 ` Dominick Grift
2015-05-20 16:24 ` Stephen Smalley
2015-05-20 16:28 ` Dominick Grift
2015-05-20 17:25 ` Stephen Smalley
2015-05-20 17:44 ` Dominick Grift
2015-05-21 15:36 ` 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=20150520155135.GA30612@x131e \
--to=dac.override@gmail.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.