View source for SELinux Policy Analysis

= SELinux Policy Analysis =
<!-- Replace "Project Name" with the actual name of the project in the line above. -->

== Project Description ==
The SELinux policy has never been reviewed to determine best practices for policy in a general-distribution context such as Fedora. This project provides such a policy review. It will also propose a packaged SELinux policy for an application that does not yet have one.
<!-- Description should be no longer than a paragraph.  Include links to any relevant on-line resources.  For example, [http://fedoraproject.org/wiki] or [http://developer.mozilla.org MDC]. -->

<sub></sub> Project Leader(s): '''Peter Valerio''' <br /> 
Wiki Page: [[User:Pvalerio]]<br />
IRC: pvalerio<br />

= Project Contributor(s) ==

<!-- Name(s) of people casually working on the project, or who have contributed significant help.  Include links to personal pages within wiki. Adding the names of your contributors here is a nice way to thank them.

NOTE: only Project Leader(s) should add names here.  You should not add your own name to the Contributor list. -->

== Project Details ==

<!-- Provides more depth than the Project Description.  This is the place for technical discussions, project specs, or other details.  If this gets very long, you might consider breaking this part into multiple pages and linking to them. -->

== Project Plan ==

Tracking mechanism (bugzilla, trac, github, ...):

Key contacts:
<!-- Add links to any mentors or key participants in the community. -->

Goals for each release and plans for reaching those goals:
<!-- Note: each contributor is expected to have unique goals. These goals may be ''related'' to other students' work, but must be ''distinct'' and ''attainable'' regardless of the state of the other students' work. For example, under the umbrella of one project title, one student may work on packaging a piece of software and another may work on documentation, or one may work on solving one bug and another on solving another bug, but two students must not work on the same bug or depend on the other students' work in order to be able to complete their own project. -->
* 0.1
Download and install the source rpm for the SELinux policy and study the policy source file. Look at the policy source code used by Fedora 17 and report on
(a) what domains, file contexts and SELinux users have been defined
(b) classification of each domain
(c) what applications, system services, etc had been confined by SELinux policy on Fedora 17

Link to source rpm: http://koji.fedoraproject.org/koji/buildinfo?buildID=363460

* 0.2
Investigate and report on the steps Fedora takes to add new policy modules to newer Fedora releases.
* 0.3
Attempt to write and package an SELinux policy for an application that does not yet have one. (SQLite)

== Communication ==

=== Mailing Lists ===
<!-- Add any appropriate mailing lists to which you are subscribed (e.g., see http://lists.fedoraproject.org -->

=== Upsteam Wiki and Web ===
<!-- Links to upstream wiki/web pages -->

=== Links/Bugs/Tracking ===
SElinux download: [http://koji.fedoraproject.org/koji/buildinfo?buildID=363460]

=== Source Code Control ===
<!-- Add a link to source code URLs, including git/mercurial/svn/cvs repositories -->

=== Blogs ===
<!-- Links to the blogs of people involved, both inside and outside Seneca -->

==== Seneca Particpants ====

==== Non-Seneca Participants ====
<!-- Links to the blogs of any non-Seneca participants in this project -->

==== Planets ====
<!-- Links to any planets related to this project -->

== Project News ==

<!-- This is where a permanent record of your releases and updates will go.  In these you should discuss the status or your work, your interactions with other members of the community (e.g., Seneca and Mozilla), problems you have encountered, etc. -->