All of lore.kernel.org
 help / color / mirror / Atom feed
From: dominick.grift@gmail.com (Dominick Grift)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] RFC: kernel_t exec rights on cgroup_t files
Date: Tue, 12 Feb 2013 22:12:54 +0100	[thread overview]
Message-ID: <1360703574.2559.50.camel@d30> (raw)
In-Reply-To: <20130212214744.5c799dc9@gentp.lnet>

On Tue, 2013-02-12 at 21:47 +0100, aranea at aixah.de wrote:
> 
> The problem is that there are no denial messages, even if I disable the dontaudit rules.
> But I'm absolutely sure SELinux is causing the problem, as everything works in permissive mode.
> 

Did you also look for them in dmesg? But yes with these early boot
things logging may be an issue.

Kind of hard to troubleshoot without any AVC denials

Is that script in initramfs? Maybe there is a way for whatever runs it
to be more verbose.

> 
> Regards, Luis Ressel
> _______________________________________________
> refpolicy mailing list
> refpolicy at oss.tresys.com
> http://oss.tresys.com/mailman/listinfo/refpolicy

  reply	other threads:[~2013-02-12 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-12 20:31 [refpolicy] RFC: kernel_t exec rights on cgroup_t files aranea at aixah.de
2013-02-12 20:34 ` Dominick Grift
2013-02-12 20:47   ` aranea at aixah.de
2013-02-12 21:12     ` Dominick Grift [this message]
2013-02-12 21:25       ` aranea at aixah.de
2013-02-12 21:32         ` aranea at aixah.de
2013-02-12 21:51           ` aranea at aixah.de
2013-02-15 21:12             ` Luis Ressel
  -- strict thread matches above, loose matches on Subject: below --
2013-02-12 19:47 Sven Vermeulen
2013-02-12 20:00 ` Dominick Grift

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=1360703574.2559.50.camel@d30 \
    --to=dominick.grift@gmail.com \
    --cc=refpolicy@oss.tresys.com \
    /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. 
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.