all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Laura Lazzati <laura.lazzati.15@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: SELinux log
Date: Mon, 17 Jun 2019 00:32:24 -0300	[thread overview]
Message-ID: <CAPNLzUP_TLg+u4Az9-_RD3bQhhuvCSnDAAbukD5kv2314i7sRw@mail.gmail.com> (raw)
In-Reply-To: <87imt5ouib.fsf@elephly.net>

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

Hi!


* I’m repeating myself here: do *not* use enforcing mode.  Do use
>   permissive mode only.
>
Oh, sorry for this, it was the "easy" way of checking that it didn't work.
I have byobu running  now with a tail -f of the audit log.
My question was more like "I am hardcoding the path to guix -at least
before doing a guix pull -, I cannot understand why that doesn't work, even
if I did it just for trying if it solved partially why guix was not found.
On the other hand, I get:

type=AVC msg=audit(1560741907.590:426): avc:  denied  { search } for
 pid=31810 comm="which" name="gnu" dev="dm-0" ino=931548
scontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
tcontext=unconfined_u:object_r:guix_daemon.guix_store_content_t:s0
tclass=dir permissive=1

Should I add something allowing commands under /usr/bin to operate over
guix? Or am I mixing things too much?


Regards :)
Laura


-- 
> Ricardo
>
>

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

      reply	other threads:[~2019-06-17  3:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-04 21:28 SELinux log Laura Lazzati
2019-06-05  9:39 ` Ricardo Wurmus
2019-06-06 14:24   ` Laura Lazzati
2019-06-06 17:58     ` Ricardo Wurmus
2019-06-07  1:46       ` Laura Lazzati
2019-06-07 20:46         ` Ricardo Wurmus
2019-06-07 23:08           ` Laura Lazzati
2019-06-07 23:10             ` Laura Lazzati
2019-06-07 23:12               ` Laura Lazzati
2019-06-08  7:03                 ` Ricardo Wurmus
2019-06-08 14:36                   ` Laura Lazzati
2019-06-08 14:50                     ` Ricardo Wurmus
2019-06-08 14:57                       ` Laura Lazzati
2019-06-08 16:56                         ` Ricardo Wurmus
2019-06-09 16:29                           ` Laura Lazzati
2019-06-10  2:08                             ` Laura Lazzati
2019-06-10  8:12                               ` Ricardo Wurmus
2019-06-11 10:48                                 ` Laura Lazzati
2019-06-11 12:23                                   ` Ricardo Wurmus
2019-06-12  1:58                                     ` Laura Lazzati
2019-06-12  6:42                                       ` Ricardo Wurmus
2019-06-12 13:27                                         ` Laura Lazzati
2019-06-12 13:34                                           ` Ricardo Wurmus
2019-06-12 14:25                                             ` Laura Lazzati
2019-06-12 20:12                                               ` Ricardo Wurmus
2019-06-12 21:01                                                 ` Laura Lazzati
2019-06-13  6:49                                                   ` Ricardo Wurmus
2019-06-13 17:53                                                     ` Laura Lazzati
2019-06-13 18:52                                                       ` Ricardo Wurmus
2019-06-14 17:24                                                         ` Laura Lazzati
2019-06-16 22:15                                                           ` Laura Lazzati
2019-06-17  1:44                                                             ` Ricardo Wurmus
2019-06-17  3:32                                                               ` Laura Lazzati [this message]

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=CAPNLzUP_TLg+u4Az9-_RD3bQhhuvCSnDAAbukD5kv2314i7sRw@mail.gmail.com \
    --to=laura.lazzati.15@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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.