Searched hist:"5 d5182cae40115c03933989473288e54afb39c7c" (Results 1 – 7 of 7) sorted by relevance
| /openbmc/linux/security/apparmor/include/ |
| H A D | policy_ns.h | diff 5d5182cae40115c03933989473288e54afb39c7c Tue May 09 02:08:41 CDT 2017 John Johansen <john.johansen@canonical.com> apparmor: move to per loaddata files, instead of replicating in profiles
The loaddata sets cover more than just a single profile and should
be tracked at the ns level. Move the load data files under the namespace
and reference the files from the profiles via a symlink.
Signed-off-by: John Johansen <john.johansen@canonical.com>
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
|
| H A D | apparmorfs.h | diff 5d5182cae40115c03933989473288e54afb39c7c Tue May 09 02:08:41 CDT 2017 John Johansen <john.johansen@canonical.com> apparmor: move to per loaddata files, instead of replicating in profiles
The loaddata sets cover more than just a single profile and should
be tracked at the ns level. Move the load data files under the namespace
and reference the files from the profiles via a symlink.
Signed-off-by: John Johansen <john.johansen@canonical.com>
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
|
| H A D | policy_unpack.h | diff 5d5182cae40115c03933989473288e54afb39c7c Tue May 09 02:08:41 CDT 2017 John Johansen <john.johansen@canonical.com> apparmor: move to per loaddata files, instead of replicating in profiles
The loaddata sets cover more than just a single profile and should
be tracked at the ns level. Move the load data files under the namespace
and reference the files from the profiles via a symlink.
Signed-off-by: John Johansen <john.johansen@canonical.com>
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
|
| /openbmc/linux/security/apparmor/ |
| H A D | policy_ns.c | diff 5d5182cae40115c03933989473288e54afb39c7c Tue May 09 02:08:41 CDT 2017 John Johansen <john.johansen@canonical.com> apparmor: move to per loaddata files, instead of replicating in profiles
The loaddata sets cover more than just a single profile and should
be tracked at the ns level. Move the load data files under the namespace
and reference the files from the profiles via a symlink.
Signed-off-by: John Johansen <john.johansen@canonical.com>
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
|
| H A D | policy_unpack.c | diff 5d5182cae40115c03933989473288e54afb39c7c Tue May 09 02:08:41 CDT 2017 John Johansen <john.johansen@canonical.com> apparmor: move to per loaddata files, instead of replicating in profiles
The loaddata sets cover more than just a single profile and should
be tracked at the ns level. Move the load data files under the namespace
and reference the files from the profiles via a symlink.
Signed-off-by: John Johansen <john.johansen@canonical.com>
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
|
| H A D | policy.c | diff 5d5182cae40115c03933989473288e54afb39c7c Tue May 09 02:08:41 CDT 2017 John Johansen <john.johansen@canonical.com> apparmor: move to per loaddata files, instead of replicating in profiles
The loaddata sets cover more than just a single profile and should
be tracked at the ns level. Move the load data files under the namespace
and reference the files from the profiles via a symlink.
Signed-off-by: John Johansen <john.johansen@canonical.com>
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
|
| H A D | apparmorfs.c | diff 5d5182cae40115c03933989473288e54afb39c7c Tue May 09 02:08:41 CDT 2017 John Johansen <john.johansen@canonical.com> apparmor: move to per loaddata files, instead of replicating in profiles
The loaddata sets cover more than just a single profile and should
be tracked at the ns level. Move the load data files under the namespace
and reference the files from the profiles via a symlink.
Signed-off-by: John Johansen <john.johansen@canonical.com>
Reviewed-by: Seth Arnold <seth.arnold@canonical.com>
Reviewed-by: Kees Cook <keescook@chromium.org>
|