From: Russell Coker <russell@coker.com.au>
To: Chris PeBenito <pebenito@ieee.org>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] some little stuff
Date: Tue, 15 Jan 2019 18:47:13 +1100 [thread overview]
Message-ID: <2480376.JRpnWL4ehX@liv> (raw)
In-Reply-To: <4df64def-6cfe-af47-5c2a-dcdbf0d507e4@ieee.org>
On Sunday, 13 January 2019 6:28:35 AM AEDT Chris PeBenito wrote:
> > Index: refpolicy-2.20180701/policy/modules/system/systemd.te
> > ===================================================================
> > --- refpolicy-2.20180701.orig/policy/modules/system/systemd.te
> > +++ refpolicy-2.20180701/policy/modules/system/systemd.te
> > @@ -337,6 +337,10 @@ optional_policy(`
> > networkmanager_dbus_chat(systemd_hostnamed_t)
> > ')
> >
> > +optional_policy(`
> > + unconfined_dbus_send(systemd_hostnamed_t)
> > +')
>
> This comment:
>
> https://github.com/SELinuxProject/refpolicy/issues/18#issuecomment-452316615
>
> makes me rethink all dbus sends to unconfined domains, especially
> unconfined_t. This here isn't all confined domains, but I want more
> consideration for the perm.
That comment is about allowing all domains to send to unconfined_t. Allowing
specific domains like systemd_hostnamed_t to send to unconfined_t doesn't seem
like a problem. It doesn't seem likely that an attack via dbus would start
with a systemd domain, especially not one like systemd_hostnamed_t.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2019-01-15 7:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-11 10:30 [PATCH] some little stuff Russell Coker
2019-01-12 19:28 ` Chris PeBenito
2019-01-15 7:47 ` Russell Coker [this message]
2019-01-15 8:36 ` Dominick Grift
2019-01-16 23:04 ` 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=2480376.JRpnWL4ehX@liv \
--to=russell@coker.com.au \
--cc=pebenito@ieee.org \
--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.