taskgated(8) [mojave man page]

taskgated(8)						    BSD System Manager's Manual 					      taskgated(8)

NAME

     taskgated -- task_for_pid access control daemon

SYNOPSIS

     taskgated [-s] [-t timeout] [-i pid]

DESCRIPTION

     taskgated is a system daemon that implements a policy for the task_for_pid system service.  When the kernel is asked for the task port of a
     process, and preliminary access control checks pass, it invokes this daemon (via launchd) to make the decision.

OPTIONS

     -t timeout
	      The daemon will quit after that many seconds of inactivity. It will be relaunched by launchd as needed. A timeout of zero can be
	      specified to make the daemon quit after servicing each request, but a small positive timeout is better for performance.

     -i pid   Inject the service port of taskgated into the process with the given pid, rather than relying on launchd to install it system-wide.
	      This is for testing only, and requires the launchd configuration for taskgated to be removed.

AUTHORIZATION RIGHTS

     system.privilege.taskport	Authorization right used to check access of allowed (but not safe) callers.

INFO KEYS

     SecTaskAccess  A value of "allowed" is required for any program that wants access to task ports. A value of "safe" bypasses authorization
		    checks if so configured.  Code must be signed by any system-trusted signing authority.

FILES

     /etc/authorization  to configure the authorization used.
     /System/Library/LaunchDaemons/com.apple.taskgated
			 startup configuration file for taskgated

SEE ALSO

     security(1), launchd(8)

HISTORY

     taskgated was first introduced in Mac OS 10.5 (Leopard).

     Procmod and procview support (-p) was removed in 10.11.

     Certain software updates of Mac OS 10.4 (Tiger) introduced the convention requiring membership in the procmod or procview groups to control
     task port access. Before that, any process could obtain the task port of any other process with the same user-id.

Darwin								   June 1, 2019 							    Darwin

launchd(8)						    BSD System Manager's Manual 						launchd(8)

NAME

     launchd -- System wide and per-user daemon/agent manager

DESCRIPTION

     launchd manages processes, both for the system as a whole and for individual users.

     The primary and preferred interface to launchd is via the launchctl(1) tool which (among other options) allows the user or administrator to
     load and unload jobs. Where possible, it is preferable for jobs to launch on demand based on criteria specified in their respective configu-
     ration files.

     launchd also manages XPC services that are bundled within applications and frameworks on the system.

     During boot launchd is invoked by the kernel to run as the first process on the system and to further bootstrap the rest of the system.

     You cannot invoke launchd directly.

NOTES

     On Darwin operating systems, the canonical way to launch a daemon is through launchd as opposed to traditional POSIX and POSIX-like mecha-
     nisms or mechanisms provided in earlier versions of OS X. These alternate methods should be considered deprecated and not suitable for new
     projects.

     In the launchd lexicon, a daemon is, by definition, a system-wide service of which there is one instance for all clients. An agent is a ser-
     vice that runs on a per-user basis.  Daemons should not attempt to display UI or interact directly with a user's login session. Any and all
     work that involves interacting with a user should be done through agents.

     XPC services which are marked with a ServiceType of System are functionally equivalent to daemons and run in the same environment, sharing
     the same Mach bootstrap namespace. XPC services which are marked with a ServiceType of User are equivalent to agents with the LimitLoadToSes-
     sionType key specifying the Background session and run in the same environment, sharing the same Mach bootstrap namespace. See
     launchd.plist(5) for more information about user sessions.

     On Darwin platforms, a user environment includes a specific Mach bootstrap subset, audit session and other characteristics not recognized by
     POSIX.  Therefore, making the appropriate setuid(2) and setgid(2) system calls is not sufficient to completely assume the identity for a
     given user. Running a service as a launchd agent or a per-user XPC service is the only way to run a process with a complete identity of that
     user.

FILES

     ~/Library/LaunchAgents	    Per-user agents provided by the user.
     /Library/LaunchAgents	    Per-user agents provided by the administrator.
     /Library/LaunchDaemons	    System-wide daemons provided by the administrator.
     /System/Library/LaunchAgents   Per-user agents provided by Apple.
     /System/Library/LaunchDaemons  System-wide daemons provided by Apple.

SEE ALSO

     launchctl(1), launchd.plist(5),

DEVELOPER DOCUMENTATION

     The Daemons and Services Programming Guide can be found at the following URL:

     https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPSystemStartup/Chapters/Introduction.html

Darwin								 25 November, 2013							    Darwin