From: Dominick Grift <dominick.grift@defensec.nl>
To: selinux-refpolicy@vger.kernel.org
Subject: [refpolicy3 RFC] Split broad file contexts
Date: Thu, 23 Mar 2023 16:06:09 +0100 [thread overview]
Message-ID: <87bkkjcxsu.fsf@defensec.nl> (raw)
I agree with Metthew.
In dssp5-debian I take this even further and I generally prefer to use
extend over optional where possible.
I only use optional if both module do not depend on eachother.
I do this for various reasons (aside from what Matthew mentioned)
* Keeps the output of semodule -vvv cleaner if you disable modules
* I try to avoid optional because of its limitations
* Keeps the policy and file_contexts cleaner/more efficient when you disable modules
--
gpg --locate-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6 E0FF DA7E 521F 10F6 4098
Dominick Grift
next reply other threads:[~2023-03-23 15:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 15:06 Dominick Grift [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-09 16:09 [refpolicy3 RFC] Split broad file contexts Chris PeBenito
2022-12-09 16:29 ` Matthew Sheets
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=87bkkjcxsu.fsf@defensec.nl \
--to=dominick.grift@defensec.nl \
--cc=d83ef10f-ae8b-08d2-55b7-66f2cf12ed9a@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).