Documentation TODO

From SELinux Wiki

(Difference between revisions)
Jump to: navigation, search
Revision as of 12:51, 17 June 2008 (edit)
StephenSmalley (Talk | contribs)

← Previous diff
Revision as of 14:08, 17 June 2008 (edit) (undo)
JamesMorris (Talk | contribs)

Next diff →
Line 5: Line 5:
* Write a HOWTO for writing simple policy modules. * Write a HOWTO for writing simple policy modules.
* Write a HOWTO for how to iteratively generate policy using audit2allow and permissive domains. * Write a HOWTO for how to iteratively generate policy using audit2allow and permissive domains.
 +* A brief high-level user-oriented overview of SELinux which people can use to understand what SELinux does, how it's part of a defense in depth approach, the value it provides and what is involved in using it effectively (e.g. set expectations of benefit/cost).

Revision as of 14:08, 17 June 2008

  • How to upgrade a system from a previously SELinux-disabled system (e.g. how to ensure any restored data like /home is correctly labeled)
  • Update and organize the Fedora SELinux FAQ.
  • Explain how and when to use semanage fcontext, port, login and user.
  • Explain how to interpret an AVC message and how to get additional information via SYSCALL audit, including how to add a simple syscall audit filter to enable collection of PATH information.
  • Write a HOWTO for writing simple policy modules.
  • Write a HOWTO for how to iteratively generate policy using audit2allow and permissive domains.
  • A brief high-level user-oriented overview of SELinux which people can use to understand what SELinux does, how it's part of a defense in depth approach, the value it provides and what is involved in using it effectively (e.g. set expectations of benefit/cost).
Personal tools