MAC_PARTITION(4)

πŸ’– MAC_PARTITION πŸ’–

okay bestie, so this is the manual page for mac_partition in section 4 of the kernel interfaces manual β€” it's giving process partition policy energy and honestly? it eats. ✨


🌸 NAME 🌸

mac_partition β€” the process partition policy, no cap πŸ’…


πŸ¦‹ SYNOPSIS πŸ¦‹

so to compile the process partition policy into your kernel, you literally drop these lines into your kernel configuration file:

options MAC
options MAC_PARTITION

orrr, alternate route bestie: to load the process partition module at boot time, put this line in your kernel configuration file:

options MAC

and then in loader.conf(5):

mac_partition_load="YES"

like, pick your fighter. both work. πŸŽ€


✨ DESCRIPTION ✨

okay so the mac_partition policy module implements a process partition policy, which lets administrators place running processes into "partitions", based on their numeric process partition (which is specified in the process's MAC label). 🫢

processes with a specified partition can only see processes that are in the same partition. that's it. that's the vibe check. πŸ”₯

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, iykyk).

and no β€” there are literally no provisions for placing processes into multiple partitions. not a thing. don't ask. πŸ’€

πŸŽ€ Label Format πŸŽ€

partition labels take on this format, bestie:

partition/value

where value can be any integer value or "none". for example:

partition/1
partition/20
partition/none

iconic, right? πŸ¦‹


🌈 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. a little legend behavior, honestly. πŸ‘‘


πŸ‘‘ 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. slay. πŸ’œ


πŸ’€ BUGS πŸ’€

okay so real talk, not me being dramatic: 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. fr fr, please don't skip this part. πŸ™ˆ

and that's the whole page, bestie πŸ’– this one's from Debian, dated July 25, 2015 β€” MAC_PARTITION(4), mwah, go partition responsibly πŸ§šβœ¨πŸ“

πŸ“¦ where this page comes from