[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xense-devel] Labeling in XSM/Flask


  • To: xense-devel@xxxxxxxxxxxxxxxxxxx
  • From: "Hayawardh V" <hayawardh@xxxxxxxxx>
  • Date: Fri, 4 Jul 2008 17:11:25 -0400
  • Delivery-date: Fri, 04 Jul 2008 14:11:31 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type; b=gYbpnNopLfVOlnI5KQfIxD/gN/CnMKjJ/hHfjvbZ7lOyDfTOIk1Afx1+q5oR+l2KbA IzkJpHVC2Cns9H4kI2qk3436eO0/ThXlBKf0qOZvN6ScFC2E9DLwo+BikuyabqkjQWMP BNAkS+pro7fxqyoYIIyCBp/48J93pZr3PkBSw=
  • List-id: "A discussion list for those developing security enhancements for Xen." <xense-devel.lists.xensource.com>

Hi George,

I applied the patch update-xsm-061908-xen-17826.diff to Xen and specified
(xsm_module_name flask)

in xend-config.

I am now able to boot into dom0 in enforcing mode.

However, when I boot a domU, it has not been labeled, and does not create.

1. How do I add labels to objects in XSM/Flask? Where will the labels be stored (like SELinux stores them in extended attributes in the file system) ?

2. The avc denial when I try to boot a domU is:
(XEN) avc:  denied  { create } for domid=0
(XEN) scontext=system_u:system_r:dom0_t tcontext=system_u:system_r:unlabeled_t
(XEN) tclass=domain

(It has type unlabeled_t).

3. Should the initial context have been system_u:system_r:xen_t? If yes, how did it transition to system_u:system_r:dom0_t?

4. When dom0 boots, there is a denial :
(XEN) avc:  denied  { firmware } for domid=0
(XEN) scontext=system_u:system_r:dom0_t tcontext=system_u:system_r:xen_t
(XEN) tclass=xen

Thanks and regards,
Hayawardh

_______________________________________________
Xense-devel mailing list
Xense-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xense-devel

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.