From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: SELinux <selinux@tycho.nsa.gov>
Subject: Re: As we move to systemd, we are loosing some functionality from init scripts.
Date: Wed, 13 Jul 2011 09:33:09 -0400 [thread overview]
Message-ID: <4E1D9E95.5020206@tresys.com> (raw)
In-Reply-To: <4E1CB8A5.2010707@redhat.com>
On 07/12/11 17:12, Daniel J Walsh wrote:
> Currently we can setup certain domains to be allowed to execute labeled
> init scripts. If we go away from init scripts we will need a mechanism
> for init to look at the calling program label to figure out if it is
> allowed to start/stop certain domains.
>
> Can webadm_t start/stop mysqld_t? Can webadm_t start/stop httpd_t?
>
> # id -Z
> staff_u:webadm_r:webadm_t:s0-s0:c0.c1023
> # systemctl start httpd.service
> # systemctl stop httpd.service
>
> Another option would be just whether label
> /lib/systemd/system/mysqld.service something that webadm_t is not
> allowed to read.
>
> Ideas?
Does your suggestion really make it impossible to send a command to
systemd to start/stop a service if you cant read that file (eg
mysqld.service)? I don't know what the implementation is, but I would
guess that systemctl connects to systemd over a unix socket or fifo to
give commands? If so, it would seem better for systemd to have some
SELinux awareness on its incoming commands.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2011-07-13 13:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 21:12 As we move to systemd, we are loosing some functionality from init scripts Daniel J Walsh
2011-07-13 13:33 ` Christopher J. PeBenito [this message]
2011-07-13 13:38 ` Daniel J Walsh
2011-07-13 17:20 ` Matthew Ife
2011-07-13 17:45 ` Daniel J Walsh
2011-07-14 12:51 ` Stephen Smalley
2011-07-14 13:23 ` Russell Coker
2011-07-14 13:41 ` Stephen Smalley
2011-07-15 17:10 ` Daniel J Walsh
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=4E1D9E95.5020206@tresys.com \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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.