From mboxrd@z Thu Jan 1 00:00:00 1970 From: rfkrocktk@gmail.com (Naftuli Tzvi Kay) Date: Mon, 22 Aug 2016 10:52:46 -0700 Subject: [refpolicy] Testing in the Reference Policy Message-ID: To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com I'm currently working on a reference policy addition to restrict access for a given application. Up until now, I've been testing my application on a Fedora 24 Vagrant VM, compiling a non-base module and loading it into the kernel, running, testing, auditing, etc. What I found is that I ended up using a lot of RedHat specific downstream macros, which aren't supported here upstream. Is there a recommended way of testing reference policy code? How can I alter my Fedora Vagrant VM setup to cover the use case I'm after? Should I just compile the reference policy in my VM, relabel the filesystem, and then reboot and load the reference policy into the kernel? My host OS is running Ubuntu 14.04, so it's not very useful for debugging SELinux things; I once tried getting SELinux running on my desktop , but X wouldn't start, etc. and I imagine the policy is pretty out of date. How can I create an environment in which I can test my policy against the program I'm aiming to constrain? (Syncthing) -------------- next part -------------- An HTML attachment was scrubbed... URL: http://oss.tresys.com/pipermail/refpolicy/attachments/20160822/467268ed/attachment.html