2

I know that when I use "sudo" an application can run under root, or if a window appears saying "Application wants to make changes to the system, enter your password for this", they will also run under root.

Processes cannot always run under root, which is why there are, for example, LaunchDaemons and LaunchAgents, which run the processes under root after the system is started.

Are there other ways that processes always run root (after approval via sudo or with the Make Change window), for example if they are started manually?

Or better: Does it say somewhere that you have permission for root so that you always start as root?

Please correct me if I said anything wrong.

Improve this question
1

The setuid bit could be set on an executable.

When the setuid or setgid attributes are set on an executable file, then any users able to execute the file will automatically execute the file with the privileges of the file's owner (commonly root)

https://en.wikipedia.org/wiki/Setuid

If setuid is applied and the binary is owned by root (and on macOS the entire directory hierarchy to that file is also owned by root), then the binary executes as root regardless of the current user.

You can find all setuid & root binaries using

find /path/to/search -user root -perm -4000
Improve this answer
1
  • Very well explained! Thanks alot – Darwin OS X Jan 1 at 17:54

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .