From: Dominick Grift <dominick.grift@defensec.nl>
To: Chris PeBenito <chpebeni@linux.microsoft.com>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: [refpolicy3 RFC] Drop suffixes?
Date: Fri, 24 Mar 2023 19:31:39 +0100 [thread overview]
Message-ID: <87zg82atmc.fsf@defensec.nl> (raw)
In-Reply-To: <c0e600cf-b724-8fa9-fb9e-be847f807a22@linux.microsoft.com> (Chris PeBenito's message of "Fri, 24 Mar 2023 14:10:10 -0400")
Chris PeBenito <chpebeni@linux.microsoft.com> writes:
> I am considering dropping the suffixes from users, roles, and
> types. init_t would become init, user_r would become user, etc.
>
> Thoughts?
One thought I have is: might this in some cases conflict with keywords?
i.e. is it technically possible?
If the suffixes have no real use then I would probably drop them, provided
that it is technically possible.
I use suffixes in my policy but they are used for templates and they are
generally also more descriptive.
--
gpg --locate-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6 E0FF DA7E 521F 10F6 4098
Dominick Grift
next prev parent reply other threads:[~2023-03-24 18:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 18:10 [refpolicy3 RFC] Drop suffixes? Chris PeBenito
2023-03-24 18:31 ` Dominick Grift [this message]
2023-03-25 9:15 ` Russell Coker
2023-03-27 12:32 ` Chris PeBenito
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=87zg82atmc.fsf@defensec.nl \
--to=dominick.grift@defensec.nl \
--cc=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 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.