[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAGXu5jKV4jmsXqv=YhzL-8LAWNs76HNeMu93qLY6AmaeXv8f5g@mail.gmail.com>
Date: Wed, 12 Sep 2012 07:38:19 -0700
From: Kees Cook <keescook@...omium.org>
To: Rusty Russell <rusty@...tcorp.com.au>
Cc: "H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
Serge Hallyn <serge.hallyn@...onical.com>,
James Morris <james.l.morris@...cle.com>,
Al Viro <viro@...iv.linux.org.uk>,
Eric Paris <eparis@...hat.com>, Jiri Kosina <jkosina@...e.cz>,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH 1/2] module: add syscall to load module from fd
On Wed, Sep 12, 2012 at 12:34 AM, Rusty Russell <rusty@...tcorp.com.au> wrote:
> "H. Peter Anvin" <hpa@...or.com> writes:
>
>> 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.
>> finit_module()).
>
> Good point; I just did a replace here.
Ah, yes. Thanks!
-Kees
--
Kees Cook
Chrome OS Security
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists