|| ||"H. Peter Anvin" <hpa-AT-zytor.com> |
|| ||Kees Cook <keescook-AT-chromium.org> |
|| ||Re: [PATCH 1/2] module: add syscall to load module from fd |
|| ||Tue, 11 Sep 2012 21:15:24 -0700|
Rusty Russell <rusty-AT-rustcorp.com.au>,
Serge Hallyn <serge.hallyn-AT-canonical.com>,
James Morris <james.l.morris-AT-oracle.com>,
Al Viro <viro-AT-zeniv.linux.org.uk>,
Eric Paris <eparis-AT-redhat.com>, Jiri Kosina <jkosina-AT-suse.cz>,
|| ||Article, Thread
On 09/06/2012 11:13 AM, Kees Cook wrote:
> Instead of (or in addition to) kernel module signing, being able to reason
> about the origin of a kernel module would be valuable in situations
> where an OS already trusts a specific file system, file, etc, due to
> things like security labels or an existing root of trust to a partition
> through things like dm-verity.
> This introduces a new syscall (currently only on x86), similar to
> init_module, that has only two arguments. The first argument is used as
> a file descriptor to the module and the second argument is a pointer to
> the NULL terminated string of module arguments.
Please use the standard naming convention, which is an f- prefix (i.e.
H. Peter Anvin, Intel Open Source Technology Center
I work for Intel. I don't speak on their behalf.
to post comments)