|author||Rusty Russell <email@example.com>||2012-09-26 10:09:40 +0100|
|committer||Rusty Russell <firstname.lastname@example.org>||2012-10-10 20:00:55 +1030|
|parent||X.509: Add a crypto key parser for binary (DER) X.509 certificates (diff)|
module: signature checking hook
We do a very simple search for a particular string appended to the module (which is cache-hot and about to be SHA'd anyway). There's both a config option and a boot parameter which control whether we accept or fail with unsigned modules and modules that are signed with an unknown key. If module signing is enabled, the kernel will be tainted if a module is loaded that is unsigned or has a signature for which we don't have the key. (Useful feedback and tweaks by David Howells <email@example.com>) Signed-off-by: Rusty Russell <firstname.lastname@example.org> Signed-off-by: David Howells <email@example.com> Signed-off-by: Rusty Russell <firstname.lastname@example.org>
Diffstat (limited to 'init')
1 files changed, 14 insertions, 0 deletions
diff --git a/init/Kconfig b/init/Kconfig
index 66cc885abbc6..fa8ccad1ea43 100644
@@ -1585,6 +1585,20 @@ config MODULE_SRCVERSION_ALL
the version). With this option, such a "srcversion" field
will be created for all modules. If unsure, say N.
+ bool "Module signature verification"
+ depends on MODULES
+ Check modules for valid signatures upon load: the signature
+ is simply appended to the module. For more information see
+ bool "Require modules to be validly signed"
+ depends on MODULE_SIG
+ Reject unsigned modules or signed modules for which we don't have a
+ key. Without this, such modules will simply taint the kernel.
endif # MODULES