From: Dominick Grift <dominick.grift@gmail.com>
To: James Carter <jwcart2@tycho.nsa.gov>
Cc: SELinux List <selinux@tycho.nsa.gov>,
Steve Lawrence <slawrence@tresys.com>,
Richard Haines <richard_c_haines@btinternet.com>
Subject: Re: Update to CIL
Date: Fri, 25 Oct 2013 20:55:23 +0200 [thread overview]
Message-ID: <1382727323.3041.176.camel@d30> (raw)
In-Reply-To: <526ABB18.2070008@tycho.nsa.gov>
On Fri, 2013-10-25 at 14:40 -0400, James Carter wrote:
>
> This looks correct and the branch is enabled. I don't know why it is not
> working. I will take a look.
>
> >> # ausearch -m user_avc,avc,selinux_err -ts 19:35 -i | grep sys_module | audit2why
> >> type=AVC msg=audit(10/25/2013 19:35:43.392:140) : avc: denied { sys_module } for pid=494 comm=modprobe capability=sys_module scontext=system_u:system_r:kernel_t:s0 tcontext=system_u:system_r:kernel_t:s0 tclass=capability
> >>
> >> Was caused by:
> >> The boolean secure_mode_policyload was set incorrectly.
> >> Description:
> >> Allow secure to mode policyload
> >>
> >> Allow access by executing:
> >> # setsebool -P secure_mode_policyload 1
By the way look at that audit2why output, its talking about a whole
different boolean there since its not secure_mode_policyload, but rather
secure_mode_insmod...
The point is that i am getting this avc denial at boot, and audit2allow
say's it would have been allowed by current policy.
Almost just like my other dbus issue, very strange (showing avc denials
for things that are allowed in policy)
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2013-10-25 18:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 18:20 Update to CIL James Carter
2013-10-18 20:02 ` Dominick Grift
2013-10-19 13:32 ` Dominick Grift
2013-10-19 18:03 ` Dominick Grift
2013-10-20 14:25 ` Dominick Grift
2013-10-21 13:25 ` Steve Lawrence
2013-10-21 18:56 ` James Carter
2013-10-21 12:35 ` Steve Lawrence
2013-10-19 16:23 ` Richard Haines
2013-10-21 13:36 ` Steve Lawrence
2013-10-21 14:22 ` Richard Haines
2013-10-21 14:46 ` Steve Lawrence
2013-10-21 15:49 ` Request for a new CIL statement Richard Haines
2013-10-21 19:14 ` Update to CIL James Carter
2013-10-23 13:59 ` Dominick Grift
2013-10-23 14:29 ` James Carter
2013-10-23 15:15 ` Dominick Grift
2013-10-23 15:58 ` James Carter
2013-10-23 17:00 ` James Carter
2013-10-23 17:27 ` Dominick Grift
2013-10-24 20:16 ` Dominick Grift
2013-10-25 17:53 ` Dominick Grift
2013-10-25 18:40 ` James Carter
2013-10-25 18:55 ` Dominick Grift [this message]
2013-10-25 18:40 ` Dominick Grift
2013-10-26 11:58 ` Dominick Grift
2013-10-31 9:45 ` 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=1382727323.3041.176.camel@d30 \
--to=dominick.grift@gmail.com \
--cc=jwcart2@tycho.nsa.gov \
--cc=richard_c_haines@btinternet.com \
--cc=selinux@tycho.nsa.gov \
--cc=slawrence@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.