UGIDFW(8)

πŸ“¦ version 15.1, in freebsd 14.5, freebsd 15.1

✨ ugidfw(8) β€” firewall-like access controls for file system objects ✨

okay so bestie, this is the system manager's manual page for ugidfw, and it's literally giving firewall-like access controls for file system objects. no cap, it's a whole vibe. πŸ’…

πŸ’– NAME πŸ’–

ugidfw β€” firewall-like access controls for file system objects

✨ SYNOPSIS ✨

Here's the synopsis vibe check β€” keep the literal spellings exactly as shown, fr fr:

       ugidfw add subject [not] [[!] uid uid | minuid:maxuid] [[!] gid gid |
              mingid:maxgid] [[!] jailid jailid] object [not] [[!] uid uid |
              minuid:maxuid] [[!] gid gid | mingid:maxgid] [[!] filesys path]
              [[!] suid] [[!] sgid] [[!] uid_of_subject] [[!] gid_of_subject]
              [[!] type ardbclsp] mode arswxn
       ugidfw list
       ugidfw set rulenum subject [not] [[!] uid uid | minuid:maxuid] [[!] gid
              gid | mingid:maxgid] [[!] jailid jailid] object [not] [[!] uid
              uid | minuid:maxuid] [[!] gid gid | mingid:maxgid] [[!] filesys
              path] [[!] suid] [[!] sgid] [[!] uid_of_subject] [[!]
              gid_of_subject] [[!] type ardbclsp] mode arswxn
       ugidfw remove rulenum

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so ugidfw gives you an ipfw(8)-like interface to manage access to file system objects by UID and GID, and it's supported by the mac_bsdextended(4) mac(9) policy. iconic.

The arguments are as follows:

  • add subject ... object ... mode arswxn β€” adds a new rule and automatically selects the rule number. See the description of set for syntax information.
  • list β€” produces a list of all the current ugidfw rules in the system. that's it, that's the whole snack.
  • set rulenum subject ... object ... mode arswxn β€” adds a new rule or modifies an existing rule. The arguments are as follows:
    • rulenum β€” rule number. Entries with a lower rule number are applied first; placing the most frequently-matched rules at the beginning of the list (i.e., lower-numbered) will yield a slight performance increase.
    • subject [not] [[!] uid uid | minuid:maxuid] [[!] gid gid | mingid:maxgid] [[!] jailid jailid] β€” subjects performing an operation must match all the conditions given. A leading not means that the subject should not match the remainder of the specification. A condition may be prefixed by ! to indicate that particular condition must not match the subject. The subject can be required to have a particular uid and/or gid. A range of uids/gids can be specified, separated by a colon. The subject can be required to be in a particular jail with the jailid.
    • object [not] [[!] uid uid | minuid:maxuid] [[!] gid gid | mingid:maxgid] [[!] filesys path] [[!] suid] [[!] sgid] [[!] uid_of_subject] [[!] gid_of_subject] [[!] type ardbclsp] β€” the rule will apply only to objects matching all the specified conditions. A leading not means that the object should not match all the remaining conditions. A condition may be prefixed by ! to indicate that particular condition must not match the object. Objects can be required to be owned by the user and/or group specified by uid and/or gid. A range of uids/gids can be specified, separated by a colon. The object can be required to be in a particular filesystem by specifying the filesystem using filesys. Note, if the filesystem is unmounted and remounted, then the rule may need to be reapplied to ensure the correct filesystem id is used. The object can be required to have the suid or sgid bits set. The owner of the object can be required to match the uid_of_subject or the gid_of_subject attempting the operation. The type of the object can be restricted to a subset of the following types.
      • a β€” any file type
      • r β€” a regular file
      • d β€” a directory
      • b β€” a block special device
      • c β€” a character special device
      • l β€” a symbolic link
      • s β€” a unix domain socket
      • p β€” a named pipe (FIFO)
    • mode arswxn β€” similar to chmod(1), each character represents an access mode. If the rule applies, the specified access permissions are enforced for the object. When a character is specified in the rule, the rule will allow for the operation. Conversely, not including it will cause the operation to be denied. The definitions of each character are as follows:
      • a β€” administrative operations
      • r β€” read access
      • s β€” access to file attributes
      • w β€” write access
      • x β€” execute access
      • n β€” none
  • remove rulenum β€” disables and removes the rule with the specified rule number.

🌈 SEE ALSO 🌈

go give these a read, fr fr:

πŸŽ€ HISTORY πŸŽ€

The ugidfw utility first appeared in FreeBSD 5.0. periodt.

πŸ‘‘ AUTHORS πŸ‘‘

This software was contributed to the FreeBSD Project by NAI 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.


πŸ’– that's the whole page, bestie β€” from Debian, dated February 24, 2004. go forth and configure, and remember: rules are just boundaries with main character energy πŸ’…

πŸ“¦ where this page comes from