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  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 21 Jul 2014 09:43:57 +1000 (EST)
From:	James Morris <>
To:	Kees Cook <>
cc:	LKML <>,
	Ming Lei <>,
	"Luis R. Rodriguez" <>,
	Greg Kroah-Hartman <>,
	James Morris <>,
	David Howells <>,
	"" <>,
	linux-security-module <>,,
	linux-wireless <>
Subject: Re: [PATCH 4/7] firmware_class: perform new LSM checks

On Sat, 19 Jul 2014, Kees Cook wrote:


> With the patch series, the LSM hook sees the userspace-touching loads:
> - from kernel built-in: no LSM hook (nonsense to check the static list)
> - direct from filesystem: called with file struct
> - via uevent /sys "loading"/"data" interface: called with NULL file struct
> - via uevent /sys "fd" interface: called with file struct

Thanks for the overview.  Can we get this documented in the LSM code?

> The reason the "fd" interface was added was because otherwise there's
> no way for systems that use the uevent handler to communicate to the
> kernel where the bytes being shoved into the "data" interface are
> coming from.


I gather folks have also thought about signing firmware?

James Morris

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