* Fix grammar mistakes and redundant clauses in the first paragraph.

* Remove 'as more features are added, they will be added here'.  That
  goes without saying for the entire Handbook.
* Break up a list of disagreeing clauses into two separate sentences.
* Replace a colon with a semicolon.
* Remove colorful language describing some users as irrational in
  favor of more succinct exposition.
This commit is contained in:
Murray Stokely 2004-07-09 09:27:11 +00:00
parent 56ad6abd0c
commit 4cd0c55b13
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=21408

View file

@ -22,11 +22,9 @@
<indexterm><primary>MAC</primary></indexterm>
<indexterm><primary>Mandatory Access Controls</primary></indexterm>
<para>With security requirements on a rise throughout much of the
world, the demand for a more secure environment has
increased. It is from this demand that the TrustedBSD project
was founded with nothing more than security in mind. The
TrustedBSD project aims at developing userland utilities and
<para>The TrustedBSD project was founded to meet the rising
security requirements of modern operating systems. This project
aims at developing userland utilities and
kernel interfaces, based on the &posix;.1e draft, and merging
them back to &os;&nbsp;5.X. While still in the development
stage, many of the features are nearing production stability.
@ -47,8 +45,7 @@
<para>This entire chapter will focus primarily on the
Mandatory Access Control framework, hereon referred to simply as
<acronym>MAC</acronym>, features. As more features are
brought into &os;&nbsp;5.X, they will be added here.</para>
<acronym>MAC</acronym>, features.</para>
<para>After reading this chapter, you will know:</para>
@ -108,15 +105,15 @@
</itemizedlist>
<warning>
<para>Please take notice that the improper use of the
<para>Please note that the improper use of the
following information may cause loss of access to the system,
aggravation of users, inability to access the features
provided by &xfree86;, and should not
aggravation of users, or inability to access the features
provided by &xfree86;. Most importantly, <acronym>MAC</acronym> should not
be believed to completely secure a system. The
<acronym>MAC</acronym> framework only augments
security: without a good security policy and regular
security checks, believing the system to be totally secure
would be completely irrational.</para>
existing security policy; without sound security practices and
regular security checks, the system will never be completely
secure.</para>
<para>It should also be noted that the examples contained
within this chapter are just that, examples. It is not