From owner-p4-projects Mon Jan 20 21:23:25 2003 Delivered-To: p4-projects@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 32767) id 7A46337B405; Mon, 20 Jan 2003 21:23:20 -0800 (PST) Delivered-To: perforce@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 28E1237B401 for ; Mon, 20 Jan 2003 21:23:20 -0800 (PST) Received: from repoman.freebsd.org (repoman.freebsd.org [216.136.204.115]) by mx1.FreeBSD.org (Postfix) with ESMTP id A697943F18 for ; Mon, 20 Jan 2003 21:23:19 -0800 (PST) (envelope-from chris@freebsd.org) Received: from repoman.freebsd.org (localhost [127.0.0.1]) by repoman.freebsd.org (8.12.6/8.12.6) with ESMTP id h0L5NJbv063103 for ; Mon, 20 Jan 2003 21:23:19 -0800 (PST) (envelope-from chris@freebsd.org) Received: (from perforce@localhost) by repoman.freebsd.org (8.12.6/8.12.6/Submit) id h0L5NJ84063100 for perforce@freebsd.org; Mon, 20 Jan 2003 21:23:19 -0800 (PST) Date: Mon, 20 Jan 2003 21:23:19 -0800 (PST) Message-Id: <200301210523.h0L5NJ84063100@repoman.freebsd.org> X-Authentication-Warning: repoman.freebsd.org: perforce set sender to chris@freebsd.org using -f From: Chris Costello Subject: PERFORCE change 24012 for review To: Perforce Change Reviews Sender: owner-p4-projects@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG http://perforce.freebsd.org/chv.cgi?CH=24012 Change 24012 by chris@chris_holly on 2003/01/20 21:22:40 Break the chapters into individual files. Update the security definition as prompted by Wayne Morrison . By not singling out privacy policies as being somehow more important than others and by expanding on well-being is, the risk of the reader thinking that privacy policies are the most common kind (they are not, FWIW, but that doesn't matter). Affected files ... .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/Makefile#2 edit .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/book.sgml#5 edit .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/chapter.decl#1 add .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/chapters.ent#2 edit .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/introduction/security-defined.sgml#1 add .. //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/introduction/security-definitions.sgml#1 add Differences ... ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/Makefile#2 (text+ko) ==== @@ -32,7 +32,7 @@ MAINTAINER= chris@FreeBSD.org DOC?= book -FORMATS?= html-split +FORMATS?= html-split html INSTALL_COMPRESSED?= gz ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/book.sgml#5 (text+ko) ==== @@ -157,7 +157,7 @@ Preface -
+
This Book's Audience This book is primarily targeted at system developers in an @@ -169,6 +169,12 @@ &man.sprog.7; manual page is intended to serve that purpose.
+ +
+ Organization of this Book + + ... +
@@ -184,93 +190,8 @@ FreeBSD security architecture. - - Security Defined - - System security is often looked at as having the quality - of being inaccessible by unauthorized users. Application - security is looked at as having the quality of being able to - handle any sort of input, regardless of validity. Network - security is considered as having a fortress-like - impenetrability from the perspective of an outside - observer. - - The common thread in all of these definitions is - essentially that security is the state of functioning as - intended. Those that should have access to various files in - the system do, and those that should not do not. Those that - should have access to the network have it, and those that - should not do not. - - Security, therefore, is defined as the - enforcement of the appropriate use of system - resources. The implementation may enforce this - arbitrarily and may have its own ideas on what - appropriate is, but generally, - appropriate means that resources are protected - in a manner favoring privacy and the overall well-being of the - system. - - - - Security-Related Definitions - - Aside from security, this document will - make reference to other terms which must be clearly defined. - These terms will be used in the strictest sense of the - definitions set forth below. - -
- Security Policy - - While security is defined as - the enforcement of the appropriate use of system - resources, security policy is - defined as the set of rules that determine what - constitutes appropriate. These - rules can usually be laid out in a similar fashion to a - standard or RFC document: this resource MUST be used - in this fashion only, this resource MUST - NOT be used in this fashion, etc. - - The FreeBSD operating system does not specify one single - security policy. Rather, a conglomeration of policies - specially tailored to specific classes - of resources, such as network-related resources, virtual - memory resources, file system resources, and system uses, - comes together to form the overall FreeBSD security - architecture. - - Security policies are found in a variety of forms. - DAC, on file system objects, - MAC, on all system subjects and - objects. -
- -
- Resource Classifications - - This document classifies system resources into - subjects and - objects. Most simply, a - subject is something that performs some - action. Examples of subjects might be processes, sockets, - and pipes. Logically, an object is - something that has some action performed on it. Examples of - objects might be file system objects, devices, network - interfaces, processes, and processes. - - The overlap in the examples for subjects and objects is - intentional—it emphasizes the point that due to the - principle that subjects might perform some action on one - another, then in having some action performed on it, that - subject must then be an object. It is advised that the - reader does not make the mistake of equating - subject with - person. -
- + &chap.introduction.security-defined; + &chap.introduction.security-definitions; ==== //depot/projects/trustedbsd/doc/en_US.ISO8859-1/books/sec-arch/chapters.ent#2 (text+ko) ==== @@ -1,5 +1,2 @@ - - - - - + + To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe p4-projects" in the body of the message