mirror of
https://gitlab.com/apparmor/apparmor.git
synced 2025-03-04 08:24:42 +01:00
Two patches in one:
From: Kees Cook <kees@ubuntu.com> This is a trivial manpage fix that makes pod2man stop yelling at me. Acked-By: Steve Beattie <sbeattie@ubuntu.com> From: Steve Beattie <sbeattie@ubuntu.com> This patch adds --stderr to pod2man to make it report errors, as well as fixes a few other minor text issues I noticed. Acked-by: Kees Cook <kees@ubuntu.com>
This commit is contained in:
parent
4d406621ee
commit
fb55e9cddc
4 changed files with 13 additions and 7 deletions
|
@ -16,4 +16,5 @@ BUILT_SOURCES = $(man_MANS)
|
|||
--section=2 \
|
||||
--release="AppArmor $(VERSION)" \
|
||||
--center="AppArmor" \
|
||||
--stderr \
|
||||
$< > $@
|
||||
|
|
|
@ -170,6 +170,7 @@ The output when run:
|
|||
|
||||
If /tmp/change_p is to be confined as well, then the following profile can be
|
||||
used (in addition to the one for 'i_cant_be_trusted_anymore', above):
|
||||
|
||||
# Confine change_p to be able to read /etc/passwd and aa_change_profile()
|
||||
# to the 'i_cant_be_trusted_anymore' profile.
|
||||
/tmp/change_p {
|
||||
|
|
|
@ -38,8 +38,9 @@ Link with B<-lapparmor> when compiling.
|
|||
|
||||
=head1 DESCRIPTION
|
||||
|
||||
The aa_is_enabled function returns true (1) if apparmor is enabled. If it
|
||||
isn't it sets the errno to reflect the reason it is not enabled and returns 0.
|
||||
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
|
||||
|
@ -57,10 +58,10 @@ appropriately.
|
|||
|
||||
=head1 ERRORS
|
||||
|
||||
=over 4
|
||||
|
||||
B<aa_is_enabled>
|
||||
|
||||
=over 4
|
||||
|
||||
=item B<ENOSYS>
|
||||
|
||||
AppArmor extensions to the system are not available.
|
||||
|
@ -84,18 +85,21 @@ Did not have sufficient permissions to determine if AppArmor is enabled.
|
|||
|
||||
=item B<EACCES>
|
||||
|
||||
+Did not have sufficient permissions to determine if AppArmor is enabled.
|
||||
Did not have sufficient permissions to determine if AppArmor is enabled.
|
||||
|
||||
=back
|
||||
|
||||
B<aa_find_mountpoint>
|
||||
|
||||
=over 4
|
||||
|
||||
=item B<ENOMEM>
|
||||
|
||||
Insufficient memory was available.
|
||||
|
||||
=item B<EACCES>
|
||||
|
||||
Access to the the required paths was denied.
|
||||
Access to the required paths was denied.
|
||||
|
||||
=item B<ENOENT>
|
||||
|
||||
|
|
|
@ -50,7 +50,7 @@ Link with B<-lapparmor> when compiling.
|
|||
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()>.
|
||||
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.
|
||||
|
|
Loading…
Add table
Reference in a new issue