From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Catonano <catonano@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] Add SELinux policy for guix-daemon.
Date: Sun, 11 Feb 2018 14:40:47 +0100 [thread overview]
Message-ID: <87zi4fiqzk.fsf@mdc-berlin.de> (raw)
In-Reply-To: <CAJ98PDzivagAJeofZ4++-ULFwiX+FXtvgFQ7010wbKyQJ+P9bQ@mail.gmail.com>
Catonano <catonano@gmail.com> writes:
>> If you want to test this on Fedora, set SELinux to permissive, and make
>> sure to configure Guix properly (i.e. set localstatedir, prefix, and
>> sysconfdir). Then install the policy with “sudo semodule -i
>> etc/guix-daemon.cil”. Then relabel the filesystem (at least /gnu,
>> $localstatedir, $sysconfdir, and $prefix) with something like this:
>>
>> sudo restorecon -R /gnu $localstatedir $sysconfdir $prefix
>>
>
> can I do this with the binary installation made with Sharlatan's script ?
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.
> $localstatedir is /var, I suppose
>
> But I don' t know about $sysconfdir and $prefix
/etc and /. But you’d be better off just relabeling everything. On
Fedora you can touch a certain file and have everything relabeled on
reboot. Takes a long time, though.
--
Ricardo
next prev parent reply other threads:[~2018-02-11 13:41 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 [this message]
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
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=87zi4fiqzk.fsf@mdc-berlin.de \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=catonano@gmail.com \
--cc=guix-devel@gnu.org \
/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).