From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] login related stuff take 2
Date: Fri, 21 Apr 2017 14:42:46 +0200 [thread overview]
Message-ID: <20170421124246.GA2335@julius> (raw)
In-Reply-To: <201704212238.06684.russell@coker.com.au>
On Fri, Apr 21, 2017 at 10:38:06PM +1000, Russell Coker via refpolicy wrote:
> On Fri, 21 Apr 2017 10:06:29 PM Guido Trentalancia via refpolicy wrote:
> > > auth_read_shadow(sulogin_t)
> > >
> > >+auth_login_pgm_domain(sulogin_t)
> > >+kernel_read_crypto_sysctls(sulogin_t)
> > >+selinux_set_generic_booleans(sulogin_t)
> > >
> > >What usage need this access?
> >
> > They are dangerous permissions, especially the one that allows to set the
> > SELinux booleans!
> >
> > Only the system administrator should be permitted to set the booleans
> > interactively through the application...
>
> Sulogin only runs at the console when something goes wrong in the early boot
> process, and the first thing it does is ask for a root password.
>
> It's simply impossible for sulogin to do what it does without the first line,
> it is a login program.
I don't think its a login program from an authlogin perspective. It has no pam config here on fedora. There are no default contexts for sulogin
>
> The second is used by exim_t, lpr_t, boinc_t, mailman_cgi_t, and
> user_mail_domain among others. If we need to restrict access to that then
> exim_t, lpr_t, boinc_t, mailman_cgi_t, and user_mail_domain all deal with
> untrusted data. The domains exim_t, boinc_t, and mailman_cgi_t are exposed to
> data from the Internet and have that access.
>
> The policy currently has sysadm_shell_domtrans(sulogin_t) which allows sulogin
> to execute "bash -c setsebool" or similar. So allowing it to set booleans
> directly doesn't really change much.
>
> There is simply no possibility to allow sulogin to do what it is intended to
> do without granting it access to destroy things (at least indirectly). If you
> don't want that then the only option is to remove sulogin. I guess you could
> submit a patch with a boolean to deny executing sulogin_exec_t for init if
> that's what you want.
>
> --
> My Main Blog http://etbe.coker.com.au/
> My Documents Blog http://doc.coker.com.au/
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy
--
Key fingerprint = 5F4D 3CDB D3F8 3652 FBD8 02D5 3B6C 5F1D 2C7B 6B02
https://sks-keyservers.net/pks/lookup?op=get&search=0x3B6C5F1D2C7B6B02
Dominick Grift
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20170421/a69154c2/attachment.bin
next prev parent reply other threads:[~2017-04-21 12:42 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 [this message]
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
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=20170421124246.GA2335@julius \
--to=dac.override@gmail.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.