freebsd-skq/share/man/man4/mac_seeotheruids.4
chris e02dd1a368 Document the following MAC policies:
o ifoff: Interface silencing policy
o partition: Process partitioning policy

Add associated Makefile entries and man page cross-references.

Obtained from:	TrustedBSD Project
Sponsored by:	DARPA, Network Associates Labs
Approved by:	re (blanket)
2002-12-11 01:02:26 +00:00

116 lines
3.7 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 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.
.\"
.\" 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 8, 2002
.Os
.Dt MAC_SEEOTHERUIDS 4
.Sh NAME
.Nm mac_seeotheruids
.Nd simple policy controlling whether users see other users
.Sh SYNOPSIS
To compile the mac_seeotheruids
policy into your kernel, place the following lines in your kernel
configuration file:
.Cd "options MAC"
.Cd "options MAC_SEEOTHERUIDS"
.Pp
Alternately, to load the 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_seeotheruids_load= Ns \&"YES"
.Sh DESCRIPTION
The
.Nm
policy module, when enabled, denies users to see processes or sockets owned
by other users.
.Pp
To enable
.Nm ,
set the sysctl OID
.Va security.mac.seeotheruids.enabled
to
.Li 1 .
.Pp
To allow users to see processes and sockets owned by the same primary group,
set the sysctl OID
.Va security.mac.seeotheruids.primarygroup_enabled
to
.Li 1 .
.Pp
To allow processes with a specific group ID to be exempt from the policy,
set the sysctl OID
.Va security.mac.seeotheruids.specificgid_enabled
to
.Li 1 ,
and
.Va security.mac.seeotheruids.specificgid
to the gid to be exempted.
.Ss Label Format
No labels are defined for
.Nm .
.Sh SEE ALSO
.Xr mac_biba 4 ,
.Xr mac_bsdextended 4 ,
.Xr mac_ifoff 4 ,
.Xr mac_mls 4 ,
.Xr mac_partition 4 ,
.Xr mac_none 4 ,
.Xr mac_test 4 ,
.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.