From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Doug Goldstein <cardoe@cardoe.com>
Cc: Daniel De Graaf <dgdegra@tycho.nsa.gov>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: XSM denials with 4.7.0 RC1
Date: Wed, 4 May 2016 15:39:55 -0400 [thread overview]
Message-ID: <20160504193955.GE7494@char.us.oracle.com> (raw)
In-Reply-To: <9da3149a-30a6-6fbf-fe53-b24d2dc788ec@cardoe.com>
>
> Well it turns out yes I was using a bad policy. I grabbed the policy
> updates from master and not from 4.7.0-rc1 when I merged them with my
> policy. So yes the above are incorrect and noise on my part. master
> wasn't (and still isn't) at the same point that 4.7.0-rc1 was at.
>
> >
> >> (XEN) avc: denied { xen_commandline } for domid=1
> >> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> >> tclass=version
> >> (XEN) avc: denied { xen_build_id } for domid=1
> >> scontext=system_u:system_r:domU_t tcontext=system_u:system_r:xen_t
> >> tclass=version
> >
> > If these show up for domUs in normal operation (and I think using
> > "xl devd" probably qualifies for that), then they probably need
> > dontaudit rules.
> >
>
> These are still happening for any domD running "xl devd".
Is 'domD' not part of domain_type?
As in the policy has:
allow domain_type xen_t:version {
xen_extraversion xen_compile_info xen_capabilities
xen_changeset xen_pagesize xen_guest_handle
};
Is domD under a different type? In which case it sounds as if you
are using a non-default XSM policy?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-05-04 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 13:52 XSM denials with 4.7.0 RC1 Doug Goldstein
2016-05-04 13:58 ` Jan Beulich
2016-05-04 14:00 ` Doug Goldstein
2016-05-04 14:05 ` Wei Liu
2016-05-04 15:33 ` Konrad Rzeszutek Wilk
2016-05-04 17:20 ` Daniel De Graaf
2016-05-04 19:35 ` Doug Goldstein
2016-05-04 19:39 ` Konrad Rzeszutek Wilk [this message]
2016-05-04 19:43 ` Doug Goldstein
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=20160504193955.GE7494@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=cardoe@cardoe.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=xen-devel@lists.xen.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.
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.