Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

aa_getcon(2) [linux man page]

AA_GETCON(2)							     AppArmor							      AA_GETCON(2)

NAME
aa_getprocattr_raw, aa_getprocattr - read and parse procattr data aa_getcon, aa_gettaskcon - get task confinement information aa_getpeercon - get the confinement of a socket's other end (peer) SYNOPSIS
#include <sys/apparmor.h> int aa_getprocattr_raw(pid_t tid, const char *attr, char *buf, int len, char **mode); int aa_getprocattr(pid_t tid, const char *attr, char **buf, char **mode); int aa_gettaskcon(pid_t target, char **con, char **mode); int aa_getcon(char **con, char **mode); int aa_getpeercon(int fd, char **con); Link with -lapparmor when compiling. DESCRIPTION
The aa_getcon function gets the current AppArmor confinement context for the current task. The confinement context is usually just the name of the AppArmor profile restricting the task, but it may include the profile namespace or in some cases a set of profile names (known as a stack of profiles). The returned string *con should be freed using free(). The aa_gettaskcon function is like the aa_getcon function except it will work for any arbitrary task in the system. The aa_getpeercon function is similar to that of aa_gettaskcon except that it returns the confinement information for task on the other end of a socket connection. The aa_getprocattr function is the backend for the aa_getcon and aa_gettaskcon functions and handles the reading and parsing of the confinement data from different arbitrary attr files and returns the processed results in an allocated buffer. The aa_getprocattr_raw() is the backend for the aa_getprocattr function and does not handle buffer allocation. RETURN VALUE
On success size of data placed in the buffer is returned, this includes the mode if present and any terminating characters. On error, -1 is returned, and errno(3) is set appropriately. ERRORS
EINVAL The apparmor kernel module is not loaded or the communication via the /proc/*/attr/file did not conform to protocol. ENOMEM Insufficient kernel memory was available. EACCES Access to the specified file/task was denied. ENOENT The specified file/task does not exist or is not visible. ERANGE The confinement data is to large to fit in the supplied buffer. BUGS
None known. If you find any, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>. SEE ALSO
apparmor(7), apparmor.d(5), apparmor_parser(8), aa_change_profile(2) and <http://wiki.apparmor.net>. AppArmor 2.7.103 2012-06-28 AA_GETCON(2)

Check Out this Related Man Page

AA-EXEC(8)							     AppArmor								AA-EXEC(8)

NAME
aa-exec - confine a program with the specified AppArmor profile SYNOPSIS
aa-exec [options] [--] [<command> ...] DESCRIPTION
aa-exec is used to launch a program confined by the specified profile and or namespace. If both a profile and namespace are specified command will be confined by profile in the new policy namespace. If only a namespace is specified, the profile name of the current confinement will be used. If neither a profile or namespace is specified command will be run using standard profile attachment (ie. as if run without the aa-exec command). If the arguments are to be pasted to the <command> being invoked by aa-exec then -- should be used to separate aa-exec arguments from the command. aa-exec -p profile1 -- ls -l OPTIONS aa-exec accepts the following arguments: -p PROFILE, --profile=PROFILE confine <command> with PROFILE. If the PROFILE is not specified use the current profile name (likely unconfined). -n NAMESPACE, --namespace=NAMESPACE use profiles in NAMESPACE. This will result in confinement transitioning to using the new profile namespace. -f FILE, --file=FILE a file or directory containing profiles to load before confining the program. -i, --immediate transition to PROFILE before doing executing <command>. This subjects the running of <command> to the exec transition rules of the current profile. -v, --verbose show commands being performed -d, --debug show commands and error codes -- Signal the end of options and disables further option processing. Any arguments after the -- are treated as arguments of the command. This is useful when passing arguments to the <command> being invoked by aa-exec. BUGS
If you find any bugs, please report them at <http://https://bugs.launchpad.net/apparmor/+filebug>. SEE ALSO
aa-stack(8), aa-namespace(8), apparmor(7), apparmor.d(5), aa_change_profile(3), aa_change_onexec(3) and <http://wiki.apparmor.net>. AppArmor 2.7.103 2012-06-28 AA-EXEC(8)
Man Page