SELinux

Fedora SELinux Project Pages

• Understanding SELinux
• Discussion of Policies
• Troubleshooting SELinux
• Multi Category Security/MCS
• Multi Level Security/MLS
• Loadable Modules
• Policy Generation Tools
• Troubleshoot Tool
• Shipping custom policy modules

Topics

• New SELinux features in FC5
• SELinux Commands
• Confined Domains

Other related links

• Toward robust Linux sandbox

Documentation

• FAQs
• Fedora 22 - SELinux User's and Administrator's Guide
• Fedora 13 - Security-Enhanced Linux User Guide
• Fedora 13 - SELinux FAQ
• Fedora 13 - Managing Confined Services Guide
• Fedora 12 - Security-Enhanced Linux User Guide
• Fedora 12 - SELinux FAQ
• Fedora 11 - Managing Confined Services Guide
• Red Hat Enterprise Linux 7: SELinux User's and Administrator's Guide
• Red Hat Enterprise Linux 6 - SELinux Guide
• Red Hat Enterprise Linux 4 - SELinux Guide
• Red Hat Magazine: What is Security-Enhanced Linux? (November 2004)
• Red Hat Magazine: Taking advantage of SELinux in Red Hat® Enterprise Linux (April 2005)
• What’s new in SELinux for Red Hat Enterprise Linux 5? (May 2007)
• SELinux: Past, Present And Future (Daniel Walsh, Red Hat SELinux developer)
• - Dan Walsh's Blog - continous discourse on understanding and using SELinux
• Five ways SELinux may surprise you (May 2007)
• SELinux Policy IDE (SLIDE) - by Tresys Technology
• Security-Enhanced Linux (nsa.gov)
• 2013 Red Hat Summit: SELinux for Mere Mortals (2013, video)
  • Security Enhanced Linux for Mere Mortals (2014, PDF)
• Grammar for policy language

If you want to work on formal documentation, you can use the Docs/Drafts/SELinux namespace. When you are done editing the draft, it can migrate to Docs/SELinux . Doing this lends an air of formality and provides higher immutability and accountability in the wiki, as only the DocWritersGroup can edit the Docs/ namespace