From: Ricardo Wurmus <rekado@elephly.net>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: [PATCH] Add SELinux policy for guix-daemon.
Date: Thu, 15 Feb 2018 16:32:02 +0100 [thread overview]
Message-ID: <87inay6zgt.fsf@elephly.net> (raw)
In-Reply-To: <87k1ve2w0o.fsf@gmail.com>
Alex Vong <alexvong1995@gmail.com> writes:
>> No, the script won’t install the SELinux policy. It wouldn’t work on
>> all systems, only on those where a suitable SELinux base policy is
>> available.
>>
> So it won't work on Debian? I think Debian and Fedora uses different
> base policy, right?
I don’t know much about SELinux on Debian, I’m afraid.
> If this is the case, should we also include an
> apparmor profile?
That’s unrelated, but sure, why not.
I would suggest writing a minimal base policy. SELinux is not an
all-or-nothing affair. That base policy only needs to provide the few
types that we care about for the guix-daemon. It wouldn’t be too hard.
The resulting policy could then be used on GuixSD or any other system
that doesn’t have a full SELinux configuration.
> Which paths does guix-daemon need to have r/w access
> to? From your SELinux profile, we know the following is needed:
>
> @guix_sysconfdir@/guix(/.*)?
> @guix_localstatedir@/guix(/.*)?
> @guix_localstatedir@/guix/profiles(/.*)?
> /gnu
> @storedir@(/.+)?
> @storedir@/[^/]+/.+
> @prefix@/bin/guix-daemon
> @storedir@/.+-(guix-.+|profile)/bin/guix-daemon
> @storedir@/.+-(guix-.+|profile)/libexec/guix-authenticate
> @storedir@/.+-(guix-.+|profile)/libexec/guix/(.*)?
> @guix_localstatedir@/guix/daemon-socket/socket
These are not things that the daemon needs to have access to. These are
paths that are to be labeled. The daemon is executed in a certain
context, and processes in that context may have certain permissions on
some of the files that have been labeled.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-15 15:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-25 16:17 [PATCH] Add SELinux policy for guix-daemon Ricardo Wurmus
2018-01-25 17:14 ` Ludovic Courtès
2018-01-26 11:18 ` Catonano
2018-01-26 14:47 ` Ricardo Wurmus
2018-02-11 12:39 ` Catonano
2018-02-11 13:40 ` Ricardo Wurmus
2018-02-15 14:00 ` Alex Vong
2018-02-15 15:32 ` Ricardo Wurmus [this message]
2018-02-16 6:50 ` Gábor Boskovits
2018-02-16 7:46 ` Alex Vong
2018-02-16 7:49 ` Alex Vong
2018-02-16 12:54 ` Gábor Boskovits
2018-02-16 15:58 ` Ricardo Wurmus
2018-02-16 16:00 ` Ricardo Wurmus
2018-02-13 15:30 ` Catonano
2018-02-13 16:29 ` Ricardo Wurmus
2018-02-13 19:46 ` Efraim Flashner
2018-02-13 19:53 ` Leo Famulari
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=87inay6zgt.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ricardo.wurmus@mdc-berlin.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.