From: Ricardo Wurmus <rekado@elephly.net>
To: "Gábor Boskovits" <boskovits@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 16:58:10 +0100 [thread overview]
Message-ID: <8737216i5p.fsf@elephly.net> (raw)
In-Reply-To: <CAE4v=pgfqABfti+827pxeBowvFFRq+mhbgy2fJ9Sw27=AWCM4w@mail.gmail.com>
Gábor Boskovits <boskovits@gmail.com> writes:
>> > 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?
Indeed. I didn’t know about the reference policy. We could take parts
of it and define an SELinux system service that applies it on boot.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2018-02-16 15:58 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
2018-02-16 15:58 ` Ricardo Wurmus [this message]
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=8737216i5p.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=boskovits@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 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).