Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #837
Difficulty: Medium
SOAP was designed as an object-addressing protocol in 1998,
True or False?
Linux & Unix Commands - Search Man Pages

mac_prepare_process_label(3) [freebsd man page]

MAC_PREPARE(3)						   BSD Library Functions Manual 					    MAC_PREPARE(3)

NAME
mac_prepare, mac_prepare_type, mac_prepare_file_label, mac_prepare_ifnet_label, mac_prepare_process_label -- allocate appropriate storage for mac_t SYNOPSIS
#include <sys/mac.h> int mac_prepare(mac_t *mac, const char *elements); int mac_prepare_type(mac_t *mac, const char *name); int mac_prepare_file_label(mac_t *mac); int mac_prepare_ifnet_label(mac_t *mac); int mac_prepare_process_label(mac_t *mac); DESCRIPTION
The mac_prepare family of functions allocates the appropriate amount of storage and initializes *mac for use by mac_get(3). When the result- ing label is passed into the mac_get(3) functions, the kernel will attempt to fill in the label elements specified when the label was pre- pared. Elements are specified in a nul-terminated string, using commas to delimit fields. Element names may be prefixed with the '?' char- acter to indicate that a failure by the kernel to retrieve that element should not be considered fatal. The mac_prepare() function accepts a list of policy names as a parameter, and allocates the storage to fit those label elements accordingly. The remaining functions in the family make use of system defaults defined in mac.conf(5) instead of an explicit elements argument, deriving the default from the specified object type. mac_prepare_type() allocates the storage to fit an object label of the type specified by the name argument. The mac_prepare_file_label(), mac_prepare_ifnet_label(), and mac_prepare_process_label() functions are equivalent to invocations of mac_prepare_type() with arguments of "file", "ifnet", and "process" respectively. RETURN VALUES
Upon successful completion, the value 0 is returned; otherwise the value -1 is returned and the global variable errno is set to indicate the error. SEE ALSO
mac(3), mac_free(3), mac_get(3), mac_is_present(3), mac_set(3), mac(4), mac.conf(5), maclabel(7) STANDARDS
POSIX.1e is described in IEEE POSIX.1e draft 17. Discussion of the draft continues on the cross-platform POSIX.1e implementation mailing list. To join this list, see the FreeBSD POSIX.1e implementation page for more information. HISTORY
Support for Mandatory Access Control was introduced in FreeBSD 5.0 as part of the TrustedBSD Project. Support for generic object types first appeared in FreeBSD 5.2. BSD
August 22, 2003 BSD

Check Out this Related Man Page

MAC(3)							   BSD Library Functions Manual 						    MAC(3)

NAME
mac -- introduction to the MAC security API LIBRARY
Standard C Library (libc, -lc) SYNOPSIS
#include <sys/mac.h> In the kernel configuration file: options MAC DESCRIPTION
Mandatory Access Control labels describe confidentiality, integrity, and other security attributes of operating system objects, overriding discretionary access control. Not all system objects support MAC labeling, and MAC policies must be explicitly enabled by the administrator. This API, based on POSIX.1e, includes routines to retrieve, manipulate, set, and convert to and from text the MAC labels on files and pro- cesses. MAC labels consist of a set of (name, value) tuples, representing security attributes from MAC policies. For example, this label contains security labels defined by two policies, mac_biba(4) and mac_mls(4): biba/low,mls/low Further syntax and semantics of MAC labels may be found in maclabel(7). Applications operate on labels stored in mac_t, but can convert between this internal format and a text format for the purposes of presenta- tion to uses or external storage. When querying a label on an object, a mac_t must first be prepared using the interfaces described in mac_prepare(3), allowing the application to declare which policies it wishes to interrogate. The application writer can also rely on default label names declared in mac.conf(5). When finished with a mac_t, the application must call mac_free(3) to release its storage. The following functions are defined: mac_is_present() This function, described in mac_is_present(3), allows applications to test whether MAC is configured, as well as whether specific policies are configured. mac_get_fd(), mac_get_file(), mac_get_link(), mac_get_peer() These functions, described in mac_get(3), retrieve the MAC labels associated with file descriptors, files, and socket peers. mac_get_pid(), mac_get_proc() These functions, described in mac_get(3), retrieve the MAC labels associated with processes. mac_set_fd(), mac_set_file(), mac_set_link() These functions, described in mac_set(3), set the MAC labels associated with file descriptors and files. mac_set_proc() This function, described in mac_set(3), sets the MAC label associated with the current process. mac_free() This function, described in mac_free(3), frees working MAC label storage. mac_from_text() This function, described in mac_text(3), converts a text-form MAC label into working MAC label storage, mac_t. mac_prepare(), mac_prepare_file_label(), mac_prepare_ifnet_label(), mac_prepare_process_label(), mac_prepare_type() These functions, described in mac_prepare(3), allocate working storage for MAC label operations. mac_prepare(3) prepares a label based on caller-specified label names; the other calls rely on the default configuration specified in mac.conf(5). mac_to_text() This function is described in mac_text(3), and may be used to convert a mac_t into a text-form MAC label. FILES
/etc/mac.conf MAC library configuration file, documented in mac.conf(5). Provides default behavior for applications aware of MAC labels on system objects, but without policy-specific knowledge. SEE ALSO
mac_free(3), mac_get(3), mac_is_present(3), mac_prepare(3), mac_set(3), mac_text(3), posix1e(3), mac(4), mac.conf(5), mac(9) STANDARDS
These APIs are loosely based on the APIs described in POSIX.1e, as described in IEEE POSIX.1e draft 17. However, the resemblance of these APIs to the POSIX APIs is loose, as the POSIX APIs were unable to express some notions required for flexible and extensible access control. 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
August 7, 2009 BSD

Featured Tech Videos