From Fedora Project Wiki

< Docs‎ | Drafts

Line 41: Line 41:
# [[SELinux/PolicyGenTools|Policy Generation Tools]]
# [[SELinux/PolicyGenTools|Policy Generation Tools]]
# [[Selinux_grammar|SELinux Policy Grammar language]]
# [[Selinux_grammar|SELinux Policy Grammar language]]
 
# [http://www.lurking-grue.org/writingselinuxpolicyHOWTO.html Writing SE Linux policy HOWTO]
Recommended Textbook -
Recommended Textbook -



Revision as of 05:49, 27 December 2010

Warning.png
This page is a draft only
It is still under construction and content may change. Do not rely on the information on this page.
Stop (medium size).png
TRANSLATORS
Please do not translate this document until it is checked into CVS. This document is undergoing very large changes in structure and content

SELinux Guide

Idea.png
Contributions are welcomed!

Documentation Summary:

Purpose: How to accomplish specific tasks with SELinux in the desktop environment. This requires a major expansion of the content beyond the SELinux FAQ which will be amalgamated into this guide in use case scenarios.

A user who finishes reading this guide should be able to:

  1. Understand how the Linux kernel, policy, and user tools work together to implement SELinux in Fedora
  2. Understand the differences and interactions between legacy UNIX access controls and SELinux
  3. Determine, set, and understand the operational mode of SELinux in a Fedora system
  4. Determine, set, and understand object and file labels
  5. Understand how to perform an automatic relabeling of a file system

Audience: Individuals who are unfamiliar with SELinux and who need to learn how to function in an environment with SELinux enabled.

Approach: This document explains basic principles by explaining one principle at a time. The document assumes some familiarity with Linux/UNIX-specific terminology or concepts. Functionality is also compared, where appropriate, to what the reader may know from other OSes, particularly Microsoft Windows.

Assumptions: The reader has a standard Desktop class installation of Fedora with, including a user account with the default settings. The reader does have access to the root password. (We changed this "non-root access" assumption so that we can include more coverage of regular software updates and the installation of alternate packages and desktops.)

Related Documents:

  1. SETroubleShoot
  2. Troubleshoot Tool
  3. Troubleshooting SELinux
  • FAQs -
  1. SELinux FAQs
  2. Fedora 13 - Security-Enhanced Linux User Guide
  3. Fedora 13 - SELinux FAQ
  4. Fedora 13 - Managing Confined Services Guide
  1. Discussion of Policies
  2. Policy Generation Tools
  3. SELinux Policy Grammar language
  4. Writing SE Linux policy HOWTO

Recommended Textbook -

Additional Web Site References -

NSA References -

Possibly Dated Content References -

Lead Writer:

Writers: MarcWiriadisastra


Fedora SELinux Guide DRAFT

Table of Contents