From: russell@coker.com.au (Russell Coker)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] login related stuff take 2
Date: Sat, 22 Apr 2017 00:23:24 +1000 [thread overview]
Message-ID: <201704220023.24414.russell@coker.com.au> (raw)
In-Reply-To: <16C6159B-E15B-44E5-AFEC-2FB1FFBA339C@trentalancia.net>
On Fri, 21 Apr 2017 11:47:35 PM Guido Trentalancia via refpolicy wrote:
> I confirm that such auth permission is not needed. It uses shadow directly
> and it already has the appropriate auth_read_shadow() interface call!
>
> I am now checking the details...
The interface auth_login_pgm_domain() does a lot more than providing PAM
access. One could make a case for splitting it into 2 or 3 interfaces that
perform different subsets of it's operations. If you think that is the case
then please submit a patch to the list and we can discuss that.
But I don't think there's much benefit to trying to restrict a domain that can
launch a shell as sysadm_t or unconfined_t.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
next prev parent reply other threads:[~2017-04-21 14:23 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-21 9:10 [refpolicy] [PATCH] login related stuff take 2 Russell Coker
2017-04-21 11:57 ` Christian Göttsche
2017-04-21 12:06 ` Guido Trentalancia
2017-04-21 12:38 ` Russell Coker
2017-04-21 12:42 ` Dominick Grift
2017-04-21 12:48 ` Dominick Grift
2017-04-21 13:33 ` Guido Trentalancia
2017-04-21 13:42 ` Dominick Grift
2017-04-21 13:47 ` Guido Trentalancia
2017-04-21 14:04 ` Dominick Grift
2017-04-21 14:23 ` Russell Coker [this message]
2017-04-21 14:39 ` Guido Trentalancia
2017-04-21 15:00 ` Guido Trentalancia
2017-04-21 15:08 ` Guido Trentalancia
2017-04-21 15:32 ` Guido Trentalancia
2017-04-21 12:20 ` Russell Coker
2017-04-21 12:30 ` Guido Trentalancia
2017-04-21 13:09 ` Russell Coker
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=201704220023.24414.russell@coker.com.au \
--to=russell@coker.com.au \
--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.