linux-toradex.git/security/apparmor/include/file.h, branch v4.12-rc4

apparmor: change aad apparmor_audit_data macro to a fn macro

2017-01-16T09:18:47+00:00

The aad macro can replace aad strings when it is not intended to. Switch
to a fn macro so it is only applied when intended.

Also at the same time cleanup audit_data initialization by putting
common boiler plate behind a macro, and dropping the gfp_t parameter
which will become useless.

Signed-off-by: John Johansen

apparmor: change op from int to const char *

2017-01-16T09:18:46+00:00

Having ops be an integer that is an index into an op name table is
awkward and brittle. Every op change requires an edit for both the
op constant and a string in the table. Instead switch to using const
strings directly, eliminating the need for the table that needs to
be kept in sync.

Signed-off-by: John Johansen

apparmor: constify aa_path_link()

2016-03-28T04:47:26+00:00

Signed-off-by: Al Viro

[apparmor] constify struct path * in a bunch of helpers

2016-03-28T03:48:14+00:00

Signed-off-by: Al Viro

apparmor: fix sparse warnings

2013-04-28T07:39:35+00:00

Fix a couple of warning reported by sparse

Signed-off-by: John Johansen

userns: Convert apparmor to use kuid and kgid where appropriate

2012-09-21T10:13:21+00:00

Cc: John Johansen 
Acked-by: Serge Hallyn 
Signed-off-by: Eric W. Biederman

AppArmor: Fix underflow in xindex calculation

2012-02-27T19:38:21+00:00

If the xindex value stored in the accept tables is 0, the extraction of
that value will result in an underflow (0 - 4).

In properly compiled policy this should not happen for file rules but
it may be possible for other rule types in the future.

To exploit this underflow a user would have to be able to load a corrupt
policy, which requires CAP_MAC_ADMIN, overwrite system policy in kernel
memory or know of a compiler error resulting in the flaw being present
for loaded policy (no such flaw is known at this time).

Signed-off-by: John Johansen 
Acked-by: Kees Cook

headers: path.h redux

2011-01-10T16:51:44+00:00

Remove path.h from sched.h and other files.

Signed-off-by: Alexey Dobriyan 
Signed-off-by: Linus Torvalds

AppArmor: file enforcement routines

2010-08-02T05:35:14+00:00

AppArmor does files enforcement via pathname matching.  Matching is done
at file open using a dfa match engine.  Permission is against the final
file object not parent directories, ie. the traversal of directories
as part of the file match is implicitly allowed.  In the case of nonexistant
files (creation) permissions are checked against the target file not the
directory.  eg. In case of creating the file /dir/new, permissions are
checked against the match /dir/new not against /dir/.

The permissions for matches are currently stored in the dfa accept table,
but this will change to allow for dfa reuse and also to allow for sharing
of wider accept states.

Signed-off-by: John Johansen 
Signed-off-by: James Morris