Thread (49 messages) 49 messages, 11 authors, 2017-11-30

Re: [PATCH v5 next 0/5] Improve Module autoloading infrastructure

From: James Morris <hidden>
Date: 2017-11-27 23:46:13
Also in: linux-security-module, lkml

On Mon, 27 Nov 2017, Kees Cook wrote:
quoted
        if (WARN_ON_ONCE(!capable(CAP_SYS_MODULE) ||
                         !capable(CAP_SYS_ADMIN) ||
                         !capable(CAP_NET_ADMIN) ||
                         !unprivileged_autoload(module_name)))
(Side note: the capable() calls would ideally come after the whitelist 
check).
We have some of this already with the module prefixes. Doing this
per-module would need to be exported to userspace, I think. It'd be
way too fragile sitting in the kernel.
What about writing a whitelist to /proc (per-task) or /sys/fs (global) ?

The per-task whitelist is inherited from the global one by default, or 
from a parent process if it's been modified in the parent.


-- 
James Morris
[off-list ref]
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help