From: Daniel Burgener <dburgener@linux.microsoft.com>
To: Russell Coker <russell@coker.com.au>, selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] strict policy patches
Date: Mon, 11 Oct 2021 12:12:42 -0400 [thread overview]
Message-ID: <a0ff06f4-4fd2-376c-e749-fbcf2677218c@linux.microsoft.com> (raw)
In-Reply-To: <YWFpTPHEZiydqBOq@xev.coker.com.au>
> ===================================================================
> --- refpolicy-2.20210908.orig/policy/modules/system/systemd.te
> +++ refpolicy-2.20210908/policy/modules/system/systemd.te
> @@ -65,10 +65,6 @@ type systemd_activate_t;
> type systemd_activate_exec_t;
> init_system_domain(systemd_activate_t, systemd_activate_exec_t)
>
> -type systemd_analyze_t;
> -type systemd_analyze_exec_t;
> -init_daemon_domain(systemd_analyze_t, systemd_analyze_exec_t)
> -
> type systemd_backlight_t;
> type systemd_backlight_exec_t;
> init_system_domain(systemd_backlight_t, systemd_backlight_exec_t)
I proposed a similar change last year here and the consensus in the PR
discussion was that it would make more sense to add policy for the
systemd_analyze_t domain for cases that wanted a transition there, but
keeping the general approach of running in the parent domain.
https://github.com/SELinuxProject/refpolicy/pull/321
Of course, no one has actually submitted systemd_analyze_t policy yet,
so maybe the demand for such a use case isn't all that high?
-Daniel
next prev parent reply other threads:[~2021-10-11 16:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-09 10:05 [PATCH] strict policy patches Russell Coker
2021-10-11 16:12 ` Daniel Burgener [this message]
2021-10-11 16:32 ` Dominick Grift
2021-10-27 13:09 ` 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=a0ff06f4-4fd2-376c-e749-fbcf2677218c@linux.microsoft.com \
--to=dburgener@linux.microsoft.com \
--cc=russell@coker.com.au \
--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.