Login or Register to Ask a Question and Join Our Community

Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

aa_getcon(2) [debian 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_FIND_MOUNTPOINT(2)						     AppArmor						     AA_FIND_MOUNTPOINT(2)

NAME

       aa_is_enabled - determine if apparmor is available

       aa_find_mountpoint - find where the apparmor interface filesystem is mounted

SYNOPSIS

       #include <sys/apparmor.h>

       int aa_is_enabled(void);

       int aa_find_mountpoint(char **mnt);

       Link with -lapparmor when compiling.

DESCRIPTION

       The aa_is_enabled function returns true (1) if apparmor is enabled.  If it isn't it sets the errno(3) to reflect the reason it is not
       enabled and returns 0.

       The aa_find_mountpoint function finds where the apparmor filesystem is mounted on the system, and returns a string containing the mount
       path.  It is the caller's responsibility to free(3) the returned path.

RETURN VALUE

       aa_is_enabled On success 1 is returned. On error, 0 is returned, and errno(3) is set appropriately.

       aa_find_mountpoint On success zero is returned. On error, -1 is returned, and errno(3) is set appropriately.

ERRORS

       aa_is_enabled

       ENOSYS
	   AppArmor extensions to the system are not available.

       ECANCELED
	   AppArmor is available on the system but has been disabled at boot.

       ENOENT
	   AppArmor is available (and maybe even enforcing policy) but the interface is not available.

       ENOMEM
	   Insufficient memory was available.

       EPERM
	   Did not have sufficient permissions to determine if AppArmor is enabled.

       EACCES
	   Did not have sufficient permissions to determine if AppArmor is enabled.

       aa_find_mountpoint

       ENOMEM
	   Insufficient memory was available.

       EACCES
	   Access to the required paths was denied.

       ENOENT
	   The apparmor filesystem mount could not be found

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), and <http://wiki.apparmor.net>.

AppArmor 2.7.103						    2012-06-28						     AA_FIND_MOUNTPOINT(2)
Man Page