[systemd-devel] SELinux labels on unix sockets
dac.override at gmail.com
Wed Mar 25 14:44:41 PDT 2015
On Wed, Mar 25, 2015 at 10:31:41PM +0100, Dominick Grift wrote:
> For the sock *file*, i would argue, that indeed the "setfscreatecon" is not strictly needed, and that the labeling for this can be taken care of by using type transition rules in the security policy as suggested.
> However for the "socket" classes associated with the process type, "setsockcreatecon" is required
> The socket activation selinux related aspect has two parts:
> 1. the socket associated with the process (setsockcreatecon())
> 2. the actual socket file (setfscreatecon())
> The latter (2) can, and should *probably* be removed.
> The setsockcreatecon() stuff should stay, and the setfscreatecon() stuff should *probably* go.
Actually, come to think about it, it is not that simple and things should probably stay as they are.
For multi level security configurations the proper security level must be associated with the sock file, and that cannot be specified with a type transition rule.
It should stay the way it currently is.
> 4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
> Dominick Grift
4D30 903A 1CF3 B756 FB48 1514 3148 83A2 02DF F788
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 648 bytes
Desc: not available
More information about the systemd-devel