From: dac.override@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] systemd
Date: Sun, 2 Nov 2014 16:46:07 +0100 [thread overview]
Message-ID: <20141102154606.GA5614@e145.network2> (raw)
In-Reply-To: <20141102134435.345e38f0@fornost.bigon.be>
On Sun, Nov 02, 2014 at 01:44:35PM +0100, Laurent Bigonville wrote:
>
> The bus_unit_method_kill() function seem to use the "stop" AV instead
> of a "kill" one. And the for the "load" one I'm not even sure to what
> it is/was referring to.
>
Unfortunate though that kill does not have its own av permission, as the kill option with systemctl can be used to send signals to the running daemon.
Some daemons take custom signals (SIGUSR etc) to do special things ( like for example auditd, and rotating logs )
I suppose for some reason it was not practical to implement a kill av permission for this
--
Dominick Grift
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 648 bytes
Desc: not available
Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20141102/222f7f36/attachment.bin
next prev parent reply other threads:[~2014-11-02 15:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 14:34 [refpolicy] systemd Christopher J. PeBenito
2014-10-31 16:00 ` Dominick Grift
2014-11-03 14:48 ` Christopher J. PeBenito
2014-11-03 15:16 ` Dominick Grift
2014-11-03 15:42 ` Dominick Grift
2014-11-02 12:44 ` Laurent Bigonville
2014-11-02 15:46 ` Dominick Grift [this message]
2014-11-03 14:32 ` Christopher J. PeBenito
2014-11-03 21:50 ` Laurent Bigonville
2014-11-04 13:01 ` Christopher J. PeBenito
2014-11-15 23:06 ` Laurent Bigonville
2014-11-17 14:13 ` Christopher J. 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=20141102154606.GA5614@e145.network2 \
--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.