120 lines
3.9 KiB
Groff
120 lines
3.9 KiB
Groff
.\" Copyright (c) 2002 Networks Associates Technology, Inc.
|
|
.\" All rights reserved.
|
|
.\"
|
|
.\" This software was developed for the FreeBSD Project by Chris Costello
|
|
.\" at Safeport Network Services and Network Associates Laboratories, the
|
|
.\" Security Research Division of Network Associates, Inc. under
|
|
.\" DARPA/SPAWAR contract N66001-01-C-8035 ("CBOSS"), as part of the
|
|
.\" DARPA CHATS research program.
|
|
.\"
|
|
.\" Redistribution and use in source and binary forms, with or without
|
|
.\" modification, are permitted provided that the following conditions
|
|
.\" are met:
|
|
.\" 1. Redistributions of source code must retain the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer.
|
|
.\" 2. Redistributions in binary form must reproduce the above copyright
|
|
.\" notice, this list of conditions and the following disclaimer in the
|
|
.\" documentation and/or other materials provided with the distribution.
|
|
.\"
|
|
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHORS AND CONTRIBUTORS ``AS IS'' AND
|
|
.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
|
|
.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
|
|
.\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHORS OR CONTRIBUTORS BE LIABLE
|
|
.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
|
|
.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
|
|
.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
|
|
.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
|
|
.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
|
|
.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
|
|
.\" SUCH DAMAGE.
|
|
.\"
|
|
.\" $FreeBSD$
|
|
.Dd DECEMBER 9, 2002
|
|
.Os
|
|
.Dt MAC_PARTITION 4
|
|
.Sh NAME
|
|
.Nm mac_partition
|
|
.Nd process partition policy
|
|
.Sh SYNOPSIS
|
|
To compile the process partition policy into your kernel,
|
|
place the following lines in your kernel
|
|
configuration file:
|
|
.Cd "options MAC"
|
|
.Cd "options MAC_PARTITION"
|
|
.Pp
|
|
Alternately, to load the process partition module at boot time,
|
|
place the following line in your kernel configuration file:
|
|
.Cd "options MAC"
|
|
.Pp
|
|
and in
|
|
.Xr loader.conf 5 :
|
|
.Cd mac_partition_load= Ns \&"YES"
|
|
.Sh DESCRIPTION
|
|
The
|
|
.Nm
|
|
policy module implements a process partition policy,
|
|
which allows administrators to place running processes into
|
|
.Dq partitions,
|
|
based on their numeric process partition
|
|
(specified in the process's MAC label).
|
|
Processes with a specified partition can only see processes that are in the
|
|
same partition.
|
|
If no partition is specified for a process, it can see all other processes
|
|
in the system
|
|
(subject to other MAC policy restrictions not defined in this man page).
|
|
No provisions for placing processes into multiple partitions is available.
|
|
.Ss Label Format
|
|
Partition labels take on the following format:
|
|
.Pp
|
|
.Dl partition/ Ns Sy value
|
|
.Pp
|
|
Where
|
|
.Sy value
|
|
can be any integer value or
|
|
.Dq none .
|
|
For example:
|
|
.Pp
|
|
.Bd -literal -offset indent
|
|
partition/1
|
|
partition/20
|
|
partition/none
|
|
.Ed
|
|
.Sh SEE ALSO
|
|
.Xr lomac 4 ,
|
|
.Xr mac 4 ,
|
|
.Xr mac_biba 4 ,
|
|
.Xr mac_bsdextended 4 ,
|
|
.Xr mac_ifoff 4 ,
|
|
.Xr mac_lomac 4 ,
|
|
.Xr mac_mls 4 ,
|
|
.Xr mac_none 4 ,
|
|
.Xr mac_seeotheruids 4 ,
|
|
.Xr mac_test 4 ,
|
|
.Xr maclabel 7 ,
|
|
.Xr mac 9
|
|
.Sh HISTORY
|
|
The
|
|
.Nm
|
|
policy module first appeared in
|
|
.Fx 5.0
|
|
and was developed by the TrustedBSD Project.
|
|
.Sh AUTHORS
|
|
This software was contributed to the
|
|
.Fx
|
|
Project by Network Associates Labs,
|
|
the Security Research Division of Network Associates
|
|
Inc. under DARPA/SPAWAR contract N66001-01-C-8035 ("CBOSS"),
|
|
as part of the DARPA CHATS research program.
|
|
.Sh BUGS
|
|
See
|
|
.Xr mac 9
|
|
concerning appropriateness for production use.
|
|
The TrustedBSD MAC Framework is considered experimental in
|
|
.Fx .
|
|
.Pp
|
|
While the MAC Framework design is intended to support the containment of
|
|
the root user, not all attack channels are currently protected by entry
|
|
point checks.
|
|
As such, MAC Framework policies should not be relied on, in isolation,
|
|
to protect against a malicious privileged user.
|