rpms/selinux-policy
7
0
Fork 0
Code Issues Pull Requests Releases Activity

fix bad links

Browse Source
This commit is contained in:
Chris PeBenito 2005-06-15 23:09:39 +00:00
parent 9a453ff35d
commit bd113c3a8b
2 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
www/html/getting-started.html
View File

@ -7,7 +7,7 @@ This guide will walk you through the basics of creating a new reference policy m
Modules are the principal organizing component in refpolicy. They are conceptually similar to the source modules in the current strict and targeted policy, but have additional meaning. A module contains the policy for an application or related group of applications, private and shared resources, labeling information, and interfaces that allow other modules access to the modules resources. The majority of the global policy has been eliminated in refpolicy. Certain policy components, like users and object classes, are still global in refpolicy, but almost all TE policy is now contained within a module.
</p>
<p>
Modules should be placed in refpolicy/policy/LAYER, where LAYER is the name of the appropriate layer. The current layers can be seen in the <A href="refpolicy-www/api-docs/">interface documentation</A>. Let's create a new module in the services layer called myapp. This is done by creating three files: myapp.te, mayapp.fc, and myapp.if, all in directory refpolicy/policy/services. The file myapp.te file will contain all of the policy private to this module, including any types or attributes. The file myapp.fc file will contain the file context labeling statement for this module. Finally, the file myapp.if will contain the interfaces for this module (interfaces will be explained below).
Modules should be placed in refpolicy/policy/LAYER, where LAYER is the name of the appropriate layer. The current layers can be seen in the <A href="api-docs/">interface documentation</A>. Let's create a new module in the services layer called myapp. This is done by creating three files: myapp.te, mayapp.fc, and myapp.if, all in directory refpolicy/policy/services. The file myapp.te file will contain all of the policy private to this module, including any types or attributes. The file myapp.fc file will contain the file context labeling statement for this module. Finally, the file myapp.if will contain the interfaces for this module (interfaces will be explained below).
</p>
<h3>Module TE Policy</h3>
<p>

2
www/html/index.html
View File

@ -4,7 +4,7 @@ The SELinux Reference Policy project (refpolicy) is creating a complete SELinux
</p>
<br/>
<p>
Refpolicy is under active development, with support and full time development staff from <a href="http://www.tresys.com">Tresys Technology</a>. The first release is available from the <a href="index.php?page=download">download</a> page. This release is far from complete and is not usable as a drop in replacement for the existing policies. It is for interested policy developers and community members to examine and comment upon. The <a href="index.php?page=status">status</a> page has more details on what is included in the current release. This project is just getting started and we are looking for policy developers interested in <a href="contributing.html">contributing</a>.
Refpolicy is under active development, with support and full time development staff from <a href="http://www.tresys.com">Tresys Technology</a>. The first release is available from the <a href="index.php?page=download">download</a> page. This release is far from complete and is not usable as a drop in replacement for the existing policies. It is for interested policy developers and community members to examine and comment upon. The <a href="index.php?page=status">status</a> page has more details on what is included in the current release. This project is just getting started and we are looking for policy developers interested in <a href="index.php?page=contributing">contributing</a>.
</p>
<br>
<h1>Project Goals</h1>