From: Dominick Grift <dominick.grift@defensec.nl>
To: Russell Coker <russell@coker.com.au>
Cc: selinux-refpolicy@vger.kernel.org
Subject: Re: [PATCH] misc apps and admin patches
Date: Wed, 20 Jan 2021 16:06:25 +0100 [thread overview]
Message-ID: <ypjlh7nblkb2.fsf@defensec.nl> (raw)
In-Reply-To: <10140498.mdnUOP6vMp@liv> (Russell Coker's message of "Thu, 21 Jan 2021 00:36:04 +1100")
Russell Coker <russell@coker.com.au> writes:
> On Thursday, 21 January 2021 12:28:49 AM AEDT Dominick Grift wrote:
>> > optional_policy(`
>> > + init_dbus_chat(sysadm_t)
>>
>> Can you explain why you added this?
>
> Apart from the obvious that some program wanted it, no. I'll remove that bit
> and add it again with a note if it's necessary. Did you like the rest of that
> patch?
Yes and thats my beef with this. "some program wanted it". sysadm_t is a
shell domain. Any programs that need this should, in my view, ideally be
targeted. If you dont want that then use unconfined_t instead and be
done.
I dont want sysadm_t to become a "drunken unconfined_t".
--
gpg --locate-keys dominick.grift@defensec.nl
Key fingerprint = FCD2 3660 5D6B 9D27 7FC6 E0FF DA7E 521F 10F6 4098
https://sks-keyservers.net/pks/lookup?op=get&search=0xDA7E521F10F64098
Dominick Grift
next prev parent reply other threads:[~2021-01-20 15:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 10:12 [PATCH] misc apps and admin patches Russell Coker
2021-01-20 13:28 ` Dominick Grift
2021-01-20 13:36 ` Russell Coker
2021-01-20 15:03 ` Dominick Grift
2021-01-20 15:06 ` Dominick Grift [this message]
2021-01-20 15:08 ` Dominick Grift
2021-01-20 23:18 ` Russell Coker
2021-02-02 14:55 Russell Coker
2021-02-02 18:33 ` 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=ypjlh7nblkb2.fsf@defensec.nl \
--to=dominick.grift@defensec.nl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).