HardenedBSD/etc/mtree
Simon J. Gerraty 1554ba03b6 Add mac_grantbylabel
This module allows controlled privilege escallation via mac labels
securely associated with a process via mac_veriexec.

There are over 700 PRIV_* but we can compress many of them into
a single GBL_* thus constraining the size of gbl labels.

The goal is to allow a daemon to run as an unprivileged process while
still being able a set of privileged operations needed.

We add APIs to libveriexec so that userland processes can check labels
and an exec_script API that allows a suitably labeled process to run
something like a python interpreter directly if necessary;
overcomming the 'indirect' flag applied to the interpreter.

Add -l option to sbin/veriexec to report labels.

Reviewed by:	stevek
Sponsored by:	Juniper Networks, Inc.
Differential Revision:	https://reviews.freebsd.org/D41431
2023-08-24 17:42:11 -07:00
..
BSD.debug.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.include.dist Add mac_grantbylabel 2023-08-24 17:42:11 -07:00
BSD.lib32.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.release.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.root.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.sendmail.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.tests.dist syslogd: Add some basic regression tests 2023-08-23 12:17:40 -04:00
BSD.usr.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
BSD.var.dist Remove $FreeBSD$: one-line sh pattern 2023-08-16 11:55:03 -06:00
Makefile etc: remove leftover leading empty comments, blank lines 2023-08-22 13:03:28 -05:00
README etc: remove leftover leading empty comments, blank lines 2023-08-22 13:03:28 -05:00

Note: If you modify these files, please keep hier(7) updated!

These files are used to create empty file hierarchies for building the
system into.  Some notes about working with them are placed here to try
and keep them in good working order.

    a)  The files use 4 space indentation, and other than in the header
        comments, should not contain any tabs.  An indentation of 4 is
        preferable to the standard indentation of 8 because the indentation
        of levels in these files can become quite deep causing the line to
        overflow 80 characters.

        This also matches with the files generated when using the
        mtree -c option, which was implemented that way for the same reason.

    b)  Only directories should be listed here.

    c)  The listing should be kept in filename sorted order.

    d)  Sanity checking changes to these files can be done by following
        this procedure (the sed -e is ugly, but fixing mtree -c to
        not emit the trailing white space would be even uglier):

            mkdir /tmp/MTREE
            mtree -deU -f BSD.X.dist -p /tmp/MTREE
            mtree -cdin -k uname,gname,mode -p /tmp/MTREE | \
		sed -e 's/ *$//' >BSD.X.new
            diff -u BSD.X.dist BSD.X.new
            rm -r /tmp/MTREE

        Note that you will get some differences about /set lines,
        and uname= gname= on certain directory areas, mainly man page
        sections.  This is caused by mtree not having a look ahead
        mechanism for making better selections for these as it
        traverses the hierarchy.

        The BSD.X.new file should NOT be committed, as it will be missing
        the correct header, and important keywords like ``nochange''.
        Simply use the diff for a sanity check to make sure things are in
        the correct order and correctly indented.

    e)  Further sanity checking of the system builds with DESTDIR=/someplace
        are more complicated, but can often catch missing entries in these
        files.  I tend to run this more complete sanity check shortly after
        the target date for a new release is announced.

        If you want details on it bug me about it via email to
        rgrimes@FreeBSD.org.