Visit Our UNIX and Linux User Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #692
Difficulty: Medium
In 1995, the Santa Cruz Operation (SCO) acquired UnixWare from Novell.
True or False?
Linux & Unix Commands - Search Man Pages

mac.conf(5) [freebsd man page]

MAC.CONF(5)						      BSD File Formats Manual						       MAC.CONF(5)

mac.conf -- format of the MAC library configuration file DESCRIPTION
The mac.conf file configures the default label elements to be used by policy-agnostic applications that operate on MAC labels. A file con- tains a series of default label sets specified by object class, in addition to blank lines and comments preceded by a '#' symbol. Currently, the implementation supports two syntax styles for label element declaration. The old (deprecated) syntax consists of a single line with two fields separated by white space: the object class name, and a list of label elements as used by the mac_prepare(3) library calls prior to an application invocation of a function from mac_get(3). The newer more preferred syntax consists of three fields separated by white space: the label group, object class name and a list of label elements. Label element names may optionally begin with a '?' symbol to indicate that a failure to retrieve the label element for an object should be silently ignored, and improves usability if the set of MAC policies may change over time. FILES
/etc/mac.conf MAC library configuration file. EXAMPLES
The following example configures user applications to operate with four MAC policies: mac_biba(4), mac_mls(4), SEBSD, and mac_partition(4). # # Default label set to be used by simple MAC applications default_labels file ?biba,?lomac,?mls,?sebsd default_labels ifnet ?biba,?lomac,?mls,?sebsd default_labels process ?biba,?lomac,?mls,?partition,?sebsd default_labels socket ?biba,?lomac,?mls # # Deprecated (old) syntax default_file_labels ?biba,?mls,?sebsd default_ifnet_labels ?biba,?mls,?sebsd default_process_labels ?biba,?mls,partition,?sebsd In this example, userland applications will attempt to retrieve Biba, MLS, and SEBSD labels for all object classes; for processes, they will additionally attempt to retrieve a Partition identifier. In all cases except the Partition identifier, failure to retrieve a label due to the respective policy not being present will be ignored. SEE ALSO
mac(3), mac_get(3), mac_prepare(3), mac(4), mac(9) HISTORY
Support for Mandatory Access Control was introduced in FreeBSD 5.0 as part of the TrustedBSD Project. BUGS
The TrustedBSD MAC Framework and associated policies, interfaces, and applications are considered to be an experimental feature in FreeBSD. Sites considering production deployment should keep the experimental status of these services in mind during any deployment process. See also mac(9) for related considerations regarding the kernel framework. BSD
April 19, 2003 BSD

Check Out this Related Man Page

MAC_PARTITION(4)					   BSD Kernel Interfaces Manual 					  MAC_PARTITION(4)

mac_partition -- process partition policy SYNOPSIS
To compile the process partition policy into your kernel, place the following lines in your kernel configuration file: options MAC options MAC_PARTITION Alternately, to load the process partition module at boot time, place the following line in your kernel configuration file: options MAC and in loader.conf(5): mac_partition_load="YES" DESCRIPTION
The mac_partition policy module implements a process partition policy, which allows administrators to place running processes into ``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 are available. Label Format Partition labels take on the following format: partition/value Where value can be any integer value or ``none''. For example: partition/1 partition/20 partition/none SEE ALSO
mac(4), mac_biba(4), mac_bsdextended(4), mac_ifoff(4), mac_lomac(4), mac_mls(4), mac_none(4), mac_portacl(4), mac_seeotheruids(4), mac_test(4), maclabel(7), mac(9) HISTORY
The mac_partition policy module first appeared in FreeBSD 5.0 and was developed by the TrustedBSD Project. AUTHORS
This software was contributed to the FreeBSD 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. BUGS
See mac(9) concerning appropriateness for production use. The TrustedBSD MAC Framework is considered experimental in FreeBSD. 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. BSD
December 9, 2002 BSD

Featured Tech Videos