From: Chris PeBenito <chpebeni@linux.microsoft.com>
To: SELinux Reference Policy mailing list
<selinux-refpolicy@vger.kernel.org>
Subject: [refpolicy3 RFC] Split broad file contexts
Date: Fri, 9 Dec 2022 11:09:10 -0500 [thread overview]
Message-ID: <d83ef10f-ae8b-08d2-55b7-66f2cf12ed9a@linux.microsoft.com> (raw)
In refpolicy2, we have several types, such as bin_t, that have file
contexts related to other modules, e.g.:
/etc/acpi/actions(/.*)? gen_context(system_u:object_r:bin_t,s0)
/usr/lib/mailman/bin(/.*)? gen_context(system_u:object_r:bin_t,s0)
/var/mailman/bin(/.*)? gen_context(system_u:object_r:bin_t,s0)
relate to acpi and mailman.
Should we continue to put all of the bin_t labeling in files.cas or
should we split it back to the individual modules? This was originally
done in refpolicy2 so users could look in a single place for everything
about bin_t for encapsulation. This is nice for users, but not so nice
for maintenance and version control.
Since cascade has the "extend" feature, we can split up the labeling
among relevant modules, and tooling can construct a single unified view
of the file contexts of bin_t and the like.
For example, instead of this in file.cas:
resource bin_t inherits executable {
...many fcs...
file_context(/etc/acpi/actions(/.*)?, any);
}
we have this in acpi.cas:
extend bin_t {
file_context(/etc/acpi/actions(/.*)?, any);
}
Thoughts?
--
Chris PeBenito
next reply other threads:[~2022-12-09 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 16:09 Chris PeBenito [this message]
2022-12-09 16:29 ` [refpolicy3 RFC] Split broad file contexts Matthew Sheets
-- strict thread matches above, loose matches on Subject: below --
2023-03-23 15:06 Dominick Grift
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=d83ef10f-ae8b-08d2-55b7-66f2cf12ed9a@linux.microsoft.com \
--to=chpebeni@linux.microsoft.com \
--cc=selinux-refpolicy@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).