all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
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: Fri, 16 Feb 2018 13:54:21 +0100	[thread overview]
Message-ID: <CAE4v=pgfqABfti+827pxeBowvFFRq+mhbgy2fJ9Sw27=AWCM4w@mail.gmail.com> (raw)
In-Reply-To: <87inaxl6hc.fsf@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2393 bytes --]

2018-02-16 8:49 GMT+01:00 Alex Vong <alexvong1995@gmail.com>:

> Ricardo Wurmus <rekado@elephly.net> writes:
>
> > 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 looked around a little, and it seems, that at least Fedora and Debian
has their base policies originated from SELinux reference policy:
https://github.com/TresysTechnology/refpolicy/wiki

I guess it would be nice to investigate how we could adopt this to GuixSD.
WDYT?

>
> >> 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.
> >
> I will have to read the colour book when I have time to understand what
> do you mean!
>
> > --
> > Ricardo
> >
> > GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
> > https://elephly.net
>
>

[-- Attachment #2: Type: text/html, Size: 3730 bytes --]

  reply	other threads:[~2018-02-16 12:54 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
2018-02-16  7:46           ` Alex Vong
2018-02-16  7:49         ` Alex Vong
2018-02-16 12:54           ` Gábor Boskovits [this message]
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='CAE4v=pgfqABfti+827pxeBowvFFRq+mhbgy2fJ9Sw27=AWCM4w@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --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.