lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  PHC 
Open Source and information security mailing list archives
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 22 Jul 2014 15:11:27 -0700
From:	"Luis R. Rodriguez" <>
To:	Kees Cook <>
Cc:	LKML <>,
	Ming Lei <>,
	Greg Kroah-Hartman <>,
	James Morris <>,
	David Howells <>,
	"" <>,
	linux-security-module <>,,
	linux-wireless <>
Subject: Re: [PATCH 3/7] security: introduce kernel_fw_from_file hook

On Tue, Jul 22, 2014 at 1:55 PM, Kees Cook <> wrote:
> On Tue, Jul 22, 2014 at 12:39 PM, Luis R. Rodriguez <> wrote:
>> On Mon, Jul 14, 2014 at 3:31 PM, Kees Cook <> wrote:
>>> Yup, with this and the module hook, adding a similar hook for kexec
>>> makes sense as well. A paranoid kernel doesn't want to trust anything
>>> it's loading from userspace. :)
>> Well I'm actually wondering if we could generalize requiring hooks or
>> not for LSM as part of the general kobject definition. Then we
>> wouldn't need to keep growing hooks for modules, firmware, kexec
>> images, etc, but instead using the interfaces for kobjects and who
>> depend on them. How that would actually look -- I'm not sure, but just
>> a thought.
> Yeah, there does seem to be a repeated "get a thing from userspace"
> method here, but the interfaces have been rather scattered so far. I
> haven't seen an obvious way to consolidate them yet.

If we are going to be adding a new system call for each type of
userspace object to help LSMs with requirements I wonder if its a
worthy endeavor to review. This series didn't add one but you had
mentioned finit_module() for example, are we going to want one for
finit_firmware() finit_kexec_image(), etc?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists