selinux-policy/www/html/status.html
2006-05-02 19:45:47 +00:00

227 lines
6.6 KiB
HTML

<h1>Status</h1>
<strong>Current Version: 20060307</strong>
<p>
See <a href="index.php?page=download">download</a> for download
information. Details of this release are part of the <a href="html/Changelog.txt">changelog</a>.
This release focused on improving the consistency of interface names
in an effort to stabilize the Reference Policy interfaces.
Currently both strict and targeted policies can
be built. MLS policies can be built, but the policy is still undergoing
testing on running systems.
</p>
<p>&nbsp;</p>
<h2>Status and Tasks</h2>
<table border="1" cellspacing="0" cellpadding="3">
<tr>
<th class="title" colspan="3">Reference Policy Status</th>
</tr>
<tr>
<td class="header">Task/Component</td><td class="header">Status</td><td class="header">Description</td>
</tr>
<tr>
<td>Policy Structure</td>
<td>Complete</td>
<td>The policy is converted over to new Reference Policy structure</td>
</tr>
<tr>
<td>TE Policy</td>
<td>Conversion Ongoing</td>
<td>Conversion of old policy to Reference Policy modules is ongoing</td>
</tr>
<tr>
<td>Loadable Policy Modules</td>
<td>Major improvements</td>
<td>Infrastructure is in place to support both source policy and
loadable policy modules. Makefile support completed.</td>
</tr>
<tr>
<td>Documentation Infrastructure</td>
<td>Interfaces, templates, Booleans, and tunables complete</td>
<td>Tools to create webpages from the module interface and
template documentation is complete. Global Booleans and
tunables are supported. Booleans and tunables local to
policies are planned.</td>
</tr>
<tr>
<td>Policy Documentation</td>
<td>Ongoing</td>
<td>Most modules are documented.</td>
</tr>
<tr>
<td>Unused Modules</td>
<td>Complete</td>
<td>Modules can be disabled by using modules.conf.</td>
</tr>
<tr>
<td>MLS Infrastructure</td>
<td>Minor improvements</td>
<td>MLS infrastructure added to support easy conversion between
MLS and non-MLS policy. Policy is compilable, but
only lightly tested.</td>
</tr>
<tr>
<td>MCS Support</td>
<td>Minor improvements</td>
<td>MLS infrastructure has been extended to support MCS
categories in users and all contexts. MCS constraints
have been added. Policy has been tested in the
targeted-mcs policy configuration.</td>
</tr>
<tr>
<td>Network Infrastructure</td>
<td>Minor improvements</td>
<td>All network ports, nodes, and interfaces moved to
corenetwork module, interfaces generated automatically.
Plan to add more infrastructure for configuration of
ports, nodes, and interfaces.</td>
</tr>
<tr>
<td>User domains and roles</td>
<td>Minor improvements</td>
<td>Some infrastructure added to support per-user domain policy,
e.g., to create types and policy for ssh,
for each user. Plan to add infrastructure to easily
configure userdomains and roles.</td>
</tr>
<tr>
<td>Labeling</td>
<td>Minor improvements</td>
<td>All labeling moved to modules, consistent with Reference
Policy structure. Levels can be added to the labels
without changes to the policy.</td>
</tr>
<tr>
<td>Tunables</td>
<td>Minor improvements</td>
<td>Tunables are documented and included in the webpage policy
documentation.</td>
</tr>
<tr>
<td>Users</td>
<td>Unchanged</td>
<td>Assignment of users to roles.</td>
</tr>
<tr>
<td>Constraints</td>
<td>Unchanged</td>
<td>Plan to split up into relevant modules when loadable modules
support this. There are ordering problems with source
policies.</td>
</tr>
<tr>
<td>Flask</td>
<td>Unchanged</td>
<td>Headers for the policy, describing object classes, and
their permissions. No planned changes.</td>
</tr>
</table>
<p>&nbsp;</p>
<!--
<h2>Roadmap</h2>
<table cellpadding="3" cellspacing="0" border="1">
<tbody>
<tr>
<th colspan="3" class="title">Reference Policy Roadmap</th>
</tr>
<tr>
<td class="header">Version</td>
<td class="header">Date</td>
<td class="header">Description</td>
</tr>
<tr>
<td>0.1</td>
<td>June 2005</td>
<td>Initial public release, basic policy restructuring, some infrastructure, few modules, and minimal documentation.</td>
</tr>
<tr>
<td>0.2</td>
<td>July 2005</td>
<td>Restructuring complete, additional modules, and improved infrastructure.</td>
</tr>
<tr>
<td>0.3</td>
<td>August 2005</td>
<td>Additional modules, documentation, and base module configuration support.</td>
</tr>
<tr>
<td>0.4</td>
<td>September 2005</td>
<td>Additional modules, documentation, and tested loadable module support.</td>
</tr>
<tr>
<td>0.5</td>
<td>October 2005</td>
<td>Additional modules, documentation, targeted policy, and tested MLS support</td>
</tr>
<tr>
<td>0.6</td>
<td>December 2005</td>
<td>Additional modules, documentation, and module variations</td>
</tr>
</tbody>
</table>
<p>&nbsp;</p>
-->
<h2>Policy Conversion</h2>
<p>
This phase of reference policy development involves the conversion of policies
from the example policy. Please use the current NSA example policy
in <a href="http://cvs.sourceforge.net/viewcvs.py/selinux/nsa/selinux-usr/policy/">
NSA SourceForge CVS</a>.
For those who wish to contribute, here is a listing of modules which need to be
converted:
</p>
<table cellpadding="3" cellspacing="0" border="1">
<tbody>
<tr>
<th colspan="3" class="title">Policy Module Status</th>
</tr>
<tr>
<td class="header">Module Name</td>
<td class="header">Previous Policy Files</td>
<td class="header">Assigned To</td>
</tr>
<tr>
<td>afs</td>
<td>afs.te afs.fc</td>
<td></td>
</tr>
<tr>
<td>dcc</td>
<td>dcc.te dcc.fc</td>
<td></td>
</tr>
<tr>
<td>gnome</td>
<td>gnome.te gnome.fc gnome_macros.te gnome_vfs.te gnome_vfs.fc gnome_vfs_macros.te gnome-pty-helper.te gnome-pty-helper.fc gph_macros.te bonobo.te bonobo.fc bonobo_macros.te gconf.te gconf.fc gconf_macros.te orbit.te orbit.fc orbit_macros.te</td>
<td>Tresys</td>
</tr>
<tr>
<td>nx</td>
<td>nx_server.te nx_server.fc</td>
<td></td>
</tr>
<tr>
<td>portslave</td>
<td>portslave.te portslave.fc</td>
<td></td>
</tr>
<tr>
<td>pyzor</td>
<td>pyzor.te pyzor.fc pyzor_macros.te</td>
<td>Dan Walsh</td>
</tr>
<tr>
<td>razor</td>
<td>razor.te razor.fc razor_macros.te</td>
<td></td>
</tr>
</tbody>
</table>
<h2>Testing Status</h2>
<p>
Reference policy is used as the basis of all of the Fedora Core 5 policies.
</p>