Page MenuHomeFreeBSD

mac(4): update the references to MAC modules
ClosedPublic

Authored by mhorne on Jun 10 2023, 2:17 PM.
Tags
None
Referenced Files
F87220591: D40483.id123124.diff
Sun, Jun 30, 10:53 AM
Unknown Object (File)
Mon, Jun 10, 10:48 PM
Unknown Object (File)
Sat, Jun 8, 10:01 AM
Unknown Object (File)
May 31 2024, 8:56 AM
Unknown Object (File)
Jan 18 2024, 9:27 AM
Unknown Object (File)
Dec 20 2023, 7:02 AM
Unknown Object (File)
Dec 13 2023, 3:34 AM
Unknown Object (File)
Nov 25 2023, 9:30 PM

Details

Summary

Add entries for mac_ntpd(4) and mac_priority(4) to the table of MAC
modules.

Drop the entry for mac_none(4), but retain the cross-reference in SEE
ALSO. This module has no functional impact and is of minimal interest to
users. Add a new cross-reference to the similar mac_stub(4), with the
same reasoning.

Diff Detail

Repository
rG FreeBSD src repository
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

mhorne created this revision.

looks we're missing some more here.
the question then is: do we need this in mac(9) too?

share/man/man4/mac.4
211

just going by the directory listing, https://github.com/freebsd/freebsd-src/tree/main/sys/security

we are also missing:

  • priority
  • pimd
  • stub
  • veriexec, and
  • veriexec_parser
mhorne added inline comments.
share/man/man4/mac.4
211

I will add an entry for mac_priority(4).

mac_pimd is missing a man page and is intended for a utility that exists outside the base system. I guess it is okay to leave it as is.

mac_stub(4) is exactly what it sounds like, similar to mac_none(4). I think these two should be referenced in SEE ALSO, but they really don't need entries in the main table, as neither has a functional impact.

The veriexec bits are not included in FreeBSD by default, so we need to leave them be.

Add entry for mac_priority(4).

mhorne retitled this revision from mac(4): add references to mac_ntpd(4) to mac(4): update the references to MAC modules.Jun 10 2023, 5:00 PM
mhorne edited the summary of this revision. (Show Details)
This revision is now accepted and ready to land.Jun 12 2023, 12:34 AM
This revision was automatically updated to reflect the committed changes.