From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] systemd
Date: Mon, 3 Nov 2014 09:32:35 -0500 [thread overview]
Message-ID: <54579203.5010902@tresys.com> (raw)
In-Reply-To: <20141102134435.345e38f0@fornost.bigon.be>
On 11/2/2014 7:44 AM, Laurent Bigonville wrote:
> Le Fri, 31 Oct 2014 10:34:37 -0400,
> "Christopher J. PeBenito" <cpebenito@tresys.com> a ?crit :
>
>> One big shortcoming that refpolicy has had lately is missing a
>> complete systemd policy. Since no one has upstreamed the policy,
>> I've decided to start writing one, as the Fedora version cannot be
>> upstreamed with out significant refactoring.
>
> Thanks for working on this!
>
> Russel already made some patched for the refpolicy using the fedora one
> as base for a systemd policy, see:
> http://anonscm.debian.org/cgit/selinux/refpolicy.git/tree/debian/patches
>
> The policy is not 100% complete, some new tools have been added in the
> latest releases.
>
> But it could be maybe interesting to keep the same types name to
> minimize the delta with the fedora policy?
I'll try to keep as compatible of possible, but I can't guarantee it.
> As Dominick already commented on github, the service security class
> seems to have 2 AV that are not used (anymore?).
>
> The bus_unit_method_kill() function seem to use the "stop" AV instead
> of a "kill" one. And the for the "load" one I'm not even sure to what
> it is/was referring to.
>
> As said in one of my previous mail, by greping the source for the
> "mac_selinux_unit_access_check()" function in git HEAD, I'm arriving
> to the following list:
>
> +class service
> +{
> + start
> + stop
> + status
> + reload
> + enable
> + disable
> +}
Thanks for looking at the source to doublecheck the permissions. Are
the extra (incorrect) permissions in the system object class still there?
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-11-03 14:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 14:34 [refpolicy] systemd Christopher J. PeBenito
2014-10-31 16:00 ` Dominick Grift
2014-11-03 14:48 ` Christopher J. PeBenito
2014-11-03 15:16 ` Dominick Grift
2014-11-03 15:42 ` Dominick Grift
2014-11-02 12:44 ` Laurent Bigonville
2014-11-02 15:46 ` Dominick Grift
2014-11-03 14:32 ` Christopher J. PeBenito [this message]
2014-11-03 21:50 ` Laurent Bigonville
2014-11-04 13:01 ` Christopher J. PeBenito
2014-11-15 23:06 ` Laurent Bigonville
2014-11-17 14:13 ` Christopher J. 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=54579203.5010902@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.com \
/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.