* systemd_generator_t vs systemd_generator_type
@ 2020-04-11 3:02 Russell Coker
2020-04-14 15:06 ` Chris PeBenito
0 siblings, 1 reply; 2+ messages in thread
From: Russell Coker @ 2020-04-11 3:02 UTC (permalink / raw)
To: selinux-refpolicy
This combination of names is confusing. As a general rule I think we
shouldn't have a type name be a substring of an attribute name. Having an
attribute name as a substring of a type name is less of an issue but still
best avoided.
/lib/systemd/system-generators/systemd-bless-boot-generator
/lib/systemd/system-generators/systemd-cryptsetup-generator
/lib/systemd/system-generators/systemd-debug-generator
/lib/systemd/system-generators/systemd-getty-generator
/lib/systemd/system-generators/systemd-hibernate-resume-generator
/lib/systemd/system-generators/systemd-rc-local-generator
/lib/systemd/system-generators/systemd-run-generator
/lib/systemd/system-generators/systemd-system-update-generator
/lib/systemd/system-generators/systemd-veritysetup-generator
/usr/lib/systemd/user-environment-generators/30-systemd-environment-d-
generator
Above are the generators on my system that run as systemd_generator_t. Would
systemd_generator_generic_t/systemd_generator_generic_exec_t be an OK name?
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: systemd_generator_t vs systemd_generator_type
2020-04-11 3:02 systemd_generator_t vs systemd_generator_type Russell Coker
@ 2020-04-14 15:06 ` Chris PeBenito
0 siblings, 0 replies; 2+ messages in thread
From: Chris PeBenito @ 2020-04-14 15:06 UTC (permalink / raw)
To: Russell Coker, selinux-refpolicy
On 4/10/20 11:02 PM, Russell Coker wrote:
> This combination of names is confusing. As a general rule I think we
> shouldn't have a type name be a substring of an attribute name. Having an
> attribute name as a substring of a type name is less of an issue but still
> best avoided.
>
> /lib/systemd/system-generators/systemd-bless-boot-generator
> /lib/systemd/system-generators/systemd-cryptsetup-generator
> /lib/systemd/system-generators/systemd-debug-generator
> /lib/systemd/system-generators/systemd-getty-generator
> /lib/systemd/system-generators/systemd-hibernate-resume-generator
> /lib/systemd/system-generators/systemd-rc-local-generator
> /lib/systemd/system-generators/systemd-run-generator
> /lib/systemd/system-generators/systemd-system-update-generator
> /lib/systemd/system-generators/systemd-veritysetup-generator
> /usr/lib/systemd/user-environment-generators/30-systemd-environment-d-
> generator
>
> Above are the generators on my system that run as systemd_generator_t. Would
> systemd_generator_generic_t/systemd_generator_generic_exec_t be an OK name?
I'd accept a patch for this.
--
Chris PeBenito
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, back to index
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-11 3:02 systemd_generator_t vs systemd_generator_type Russell Coker
2020-04-14 15:06 ` Chris PeBenito
SELinux-Refpolicy Archive on lore.kernel.org
Archives are clonable:
git clone --mirror https://lore.kernel.org/selinux-refpolicy/0 selinux-refpolicy/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 selinux-refpolicy selinux-refpolicy/ https://lore.kernel.org/selinux-refpolicy \
selinux-refpolicy@vger.kernel.org
public-inbox-index selinux-refpolicy
Example config snippet for mirrors
Newsgroup available over NNTP:
nntp://nntp.lore.kernel.org/org.kernel.vger.selinux-refpolicy
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git