From: domg472@gmail.com (Dominick Grift) Date: Mon, 22 Sep 2008 23:00:47 +0200 Subject: [refpolicy] SELinux policy In-Reply-To: References: Message-ID: <1222117247.11466.11.camel@sulphur.notebook.internal> To: refpolicy@oss.tresys.com List-Id: refpolicy.oss.tresys.com Writing a policy is not really that hard to do. The book selinux by example goes into it, although it is bit old. Tresys reference policy is full of examples and can help you get started as well. Also google for SElinux might yield interesting results. What is more interesting in my view is implement a access control extension to some program for example apache or another project. dwalsh recently talked about some of this: http://danwalsh.livejournal.com/23118.html nsa.gov website has documentation on how to implement ACE for applications. existing examples are XACE , SEBDUS, nscd , sepostgesql etc I will gladly answer any questions i can about writing policy. But again writing a policy is, in my view, not really ambitious for a master degree project. Many of us you can also find on IRC.freenode.org in either #selinux , #fedora-selinux or both. Stop by and have a chat if you want to have a talk about writing policy. On Mon, 2008-09-22 at 22:19 +0200, Konrad Azzopardi wrote: > Hi all, > > I am interested as part of my Masters Degree in Information Security > to contribute in some way by writing a policy for some application. I > am still in research phase and any suggestions would be very helpful. > > I thank you in advance > Konrad > _______________________________________________ > refpolicy mailing list > refpolicy at oss.tresys.com > http://oss.tresys.com/mailman/listinfo/refpolicy -- Dominick Grift -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 197 bytes Desc: This is a digitally signed message part Url : http://oss.tresys.com/pipermail/refpolicy/attachments/20080922/4d9a44c7/attachment.bin