Docs/Drafts/SELinux

From FedoraProject

< Docs | Drafts(Difference between revisions)
Jump to: navigation, search
m (1 revision(s))
m (Fixed templates)
Line 1: Line 1:
<pre>#!html
+
{{Draft}}
<font size="+1"></pre>
+
{{Message/warning2 | '''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 =
 
= SELinux Guide =
<pre>#!html
 
</font></pre>
 
  
{| border="1"
+
{{Message/notice | '''Contributions are welcomed!'''}}
|-
+
| {{Template:Warning}} '''THIS IS A DRAFT ONLY, FOR USE BY DOCUMENTATION WRITERS AND EDITORS. DO NOT RELY ON IT FOR ANY ADVICE UNTIL THIS NOTICE DISAPPEARS AND THE DOCUMENT IS PUBLISHED AS FINAL.'''
+
|}
+
 
+
{| border="1"
+
|-
+
| '''Contributions are welcomed!'''
+
|}
+
 
+
{| border="1"
+
|-
+
| {{Template:Warning}} '''TRANSLATORS: Please do not translate this document until it is checked into CVS. This document is undergoing very large changes in structure and content'''
+
|}
+
 
+
--------
+
'''Documentation Summary:'''
+
  
 +
==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.
 
''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:
 
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
+
# 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
+
# 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
+
# Determine, set, and understand the operational mode of SELinux in a Fedora system
4. Determine, set, and understand object and file labels
+
# Determine, set, and understand object and file labels
5. Understand how to perform an automatic relabeling of a file system
+
# Understand how to perform an automatic relabeling of a file system
  
  

Revision as of 17:24, 30 May 2008

Warning (medium size).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

Contents

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:

Lead Writer:

Writers: MarcWiriadisastra



Fedora SELinux Guide DRAFT

Table of Contents