From 9f945bcc2df0f293e74c4a5fce8b59027897c794 Mon Sep 17 00:00:00 2001 From: Karl MacMillan Date: Wed, 15 Jun 2005 01:14:09 +0000 Subject: [PATCH] Various updates. --- www/html/documentation.html | 1 + www/html/index.html | 72 ++++++++++++++++++------------------- www/html/menu.html | 8 ++--- www/html/status.html | 5 +++ www/libs.inc.php | 2 +- www/style.css | 56 +++++++++++++++++++++++++++-- 6 files changed, 99 insertions(+), 45 deletions(-) diff --git a/www/html/documentation.html b/www/html/documentation.html index e69de29b..da830652 100644 --- a/www/html/documentation.html +++ b/www/html/documentation.html @@ -0,0 +1 @@ +

Documentation

\ No newline at end of file diff --git a/www/html/index.html b/www/html/index.html index c63cfe20..0cdd0cc9 100644 --- a/www/html/index.html +++ b/www/html/index.html @@ -1,46 +1,44 @@

Project Overview

-The SELinux Reference Policy project (refpolicy) is creating a complete SELinux policy as an alternative to the existing strict and targeted policies. What will set refpolicy apart? - +The SELinux Reference Policy project (refpolicy) is creating a complete SELinux policy as an alternative to the existing strict and targeted policies available from Tresys Technology. We are looking for policy developers interested in contributing. +

+Refpolicy is under active development, with support and full time development staff from Tresys Technology. We are looking for policy developers interested in contributing.

+

Background

-

-The purpose of this document is to serve as a blueprint to policy developers -and serves as the initial means for communicating the motivations, approach and -goals of the SELinux Reference Policy development project. This document -is intended for SELinux policy developers and other members of the SELinux -development community interested in building a secure foundation upon which to -build high-assurance solutions using SELinux. The reference policy will provide -a carefully designed and consistent system security policy that can be used as -a basis for developing secure solutions using SELinux. -

+

Roadmap

-

Background and Motivation

-

-One of the key motivations for this project is the drive to get SELinux -mainstreamed into commercial products. True, SELinux is currently being -incorporated into various commercial distributions, but clearly, widespread -adoption of SELinux as a commercial product eventually will require the -operating system to be certified. Efforts are already underway by IBM for -SELinux to undergo a Common Criteria evaluation under the Labeled Security -Protection Profile (LSPP). Furthermore, SELinux needs a more robust policy -structure upon which to build high-assurance solutions, such as intrusion -detection systems (IDS), cross-domain solutions, etc., particularly for -government and DoD security-critical missions. -

+ + + + -

-Unfortunately, the current "strict" policy for SELinux does not meet the -requirements of high security systems. The policy chooses functionality over -security, with the implicit goal of not breaking legacy application behavior. -Additionally, it has no clear security goals and those that exist are not -rigorously followed or are ignored to preserve functionality. Furthermore, -complexity is increasing in the policy and the situation is not improving. -

+ + + + + + + + + + + + + + + + + + + + + + diff --git a/www/html/menu.html b/www/html/menu.html index 81a0ca93..38fa64bd 100644 --- a/www/html/menu.html +++ b/www/html/menu.html @@ -1,7 +1,7 @@ - Home
- Documentation -
- Status -
- Contributing -
+ Reference Policy
+ Documentation -
+ Status -
+ Contributing -
Download -
SourceForge.net Logo diff --git a/www/html/status.html b/www/html/status.html index e69de29b..88711ddd 100644 --- a/www/html/status.html +++ b/www/html/status.html @@ -0,0 +1,5 @@ +

Status

+

Version .1

+

+Version .1 of refpolicy was released on June 14, 2005. See download for download information. This release focused on infrastructure, organization, and initial design rather than comprehensive policy coverage or security improvements. +

\ No newline at end of file diff --git a/www/libs.inc.php b/www/libs.inc.php index 26130e87..1d1e3d0e 100644 --- a/www/libs.inc.php +++ b/www/libs.inc.php @@ -9,7 +9,7 @@ require_once (SMARTY_DIR."Smarty.class.php"); $smarty = new Smarty; - $smarty->compile_dir = "/home/groups/s/se/sepolicy-server/t_c"; + $smarty->compile_dir = "/home/groups/s/se/serefpolicy/t_c"; $smarty->template_dir = "$fixpath/html"; $smarty->assign("border", "0"); diff --git a/www/style.css b/www/style.css index 4897e49b..9f1b9b16 100644 --- a/www/style.css +++ b/www/style.css @@ -13,19 +13,50 @@ h1 { font-weight:900; color:#ccc; } +h2 { + font-size:100%; + } h3 { font-size:75%; } +h4 { + font-size:67%; + } li { font:11px/20px verdana, arial, helvetica, sans-serif; margin:0px 0px 0px 0px; padding:0px; } p { + /* normal */ font:11px/20px verdana, arial, helvetica, sans-serif; margin:0px 0px 16px 0px; padding:0px; } + +tt { + /* inline code */ + font-family: monospace; + } + +table { + background-color: white; + color: black; + text-align: left; + font:11px/20px verdana, arial, helvetica, sans-serif; + margin-left: 10%; + margin-right: 10%; +} + +th { + background-color: #ccccff; + text-align: center; +} + +td.header { + font-weight: bold; +} + #Content>p {margin:0px;} #Content>p+p {text-indent:30px;} a { @@ -57,6 +88,25 @@ pre { text-decoration:none; font-family:courier; } +pre.codeblock { + /* code block (bordered, slight gray background) */ + border-style:solid; + border-color:black; + border-width:1px 1px 1px 1px; + background-color:#f8f8f8; + margin-left: 10%; + margin-right: 10%; +} +dl { + /* definition text block */ + font:11px/20px verdana, arial, helvetica, sans-serif; + margin:0px 0px 16px 0px; + padding:0px; + } +dt { + /* definition term */ + font-weight: bold; + } #Header { margin:50px 0px 10px 0px; @@ -83,7 +133,7 @@ body>#Header {height:14px;} position:absolute; top:100px; left:20px; - width:152px; + width:162px; padding:10px; background-color:#eee; border:1px dashed #999; @@ -91,6 +141,6 @@ body>#Header {height:14px;} text-align:right; voice-family: "\"}\""; voice-family:inherit; - width:150px; + width:160px; } -body>#Menu {width:150px;} +body>#Menu {width:160px;}
Reference Policy Roadmap
VersionDateDescription
0.1June 14, 2005Initial public release, basic policy restructuring, minimal modules
0.2July 2005Restructuring complete, additional modules, improved infrastructure, and incorporated community feedback
0.3August 2005Additional modules, basic role infrastructure, and tested loadable module support
0.4September 2005Additional modules and complete role infrastructure and role separation
0.5October 2005Additional modules, targeted policy, and tested MLS support
0.6December 2005Additional modules and module variations