From: "Gábor Boskovits" <boskovits@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>,
Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: [PATCH] Add SELinux policy for guix-daemon.
Date: Fri, 16 Feb 2018 07:50:35 +0100 [thread overview]
Message-ID: <CAE4v=pj-F=oUDbi_BR_duf2LtkoOUtNcKSDG=s_uSLy=7q1Kyw@mail.gmail.com> (raw)
In-Reply-To: <87inay6zgt.fsf@elephly.net>
[-- Attachment #1: Type: text/plain, Size: 2164 bytes --]
2018-02-15 16:32 GMT+01:00 Ricardo Wurmus <rekado@elephly.net>:
>
> 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.
>
>
I would be interested in doing that. It would be great if we could use
SELinux on GuixSD. I also like the apparmor idea. These would be
great enablers for me. Do we have any policy how we do these, or
should I check how it is done on other distros?
> > 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
>
>
>
>
[-- Attachment #2: Type: text/html, Size: 3091 bytes --]
next prev parent reply other threads:[~2018-02-16 6:50 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
2018-02-16 6:50 ` Gábor Boskovits [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAE4v=pj-F=oUDbi_BR_duf2LtkoOUtNcKSDG=s_uSLy=7q1Kyw@mail.gmail.com' \
--to=boskovits@gmail.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).