From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: SELinux log Date: Wed, 12 Jun 2019 08:42:49 +0200 Message-ID: <87h88v9udy.fsf@elephly.net> References: <87sgsocqx5.fsf@elephly.net> <87k1dyk33n.fsf@elephly.net> <87ef4586oh.fsf@elephly.net> <87a7es8spi.fsf@elephly.net> <87r284cer2.fsf@elephly.net> <87muisc8x8.fsf@elephly.net> <87ef41dfkc.fsf@elephly.net> <87tvcw9upi.fsf@elephly.net> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38810) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hawyP-0000Lc-Ca for guix-devel@gnu.org; Wed, 12 Jun 2019 02:43:06 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hawyL-0005wL-7l for guix-devel@gnu.org; Wed, 12 Jun 2019 02:43:03 -0400 Received: from sender4-of-o53.zoho.com ([136.143.188.53]:21322) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1hawyJ-0005t3-Gw for guix-devel@gnu.org; Wed, 12 Jun 2019 02:43:00 -0400 In-reply-to: List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: Laura Lazzati Cc: Guix-devel Laura Lazzati writes: > I added the lines to a copy of guix-daemon.cil which I got from cloning > guix and placed it in root's home. Which lines? All of the changes I described were not necessarily ready for inclusion. They were all untested. > Since everything was messy (/gnu had d?????????? as permissions as well = as > all the fields listed with `ls -l`, and could not solve it, even trying to > delete it ), I restored my VM to the point prior to adding the policy and > loading the module. > There i ran semodule, using the new file, created the .autorelabel file > and rebooted. It labeled everything, but I still can't run guix, and /gnu > dir again ended with these weird permisions: > d?????????? ? ? ? ? ? gnu This probably just means that there is no context permissions for =E2=80=9C= ls=E2=80=9D to access /gnu. Another =E2=80=9Callow=E2=80=9D rule may be required to pe= rmit read-only access on /gnu to any process. -- Ricardo