lkml.org 
[lkml]   [2014]   [Nov]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[PATCH] Document correct module signature kernel parameter
Date
The parameter is module.sig_enforce, not enforcemodulesig. The latter
appears to be from before this functionality was merged into mainline.

Signed-off-by: Michael Marineau <michael.marineau@coreos.com>
---
Documentation/module-signing.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/module-signing.txt b/Documentation/module-signing.txt
index 09c2382..6e5262e 100644
--- a/Documentation/module-signing.txt
+++ b/Documentation/module-signing.txt
@@ -222,7 +222,7 @@ signature checking is all done within the kernel.
NON-VALID SIGNATURES AND UNSIGNED MODULES
=========================================

-If CONFIG_MODULE_SIG_FORCE is enabled or enforcemodulesig=1 is supplied on
+If CONFIG_MODULE_SIG_FORCE is enabled or module.sig_enforce=1 is supplied on
the kernel command line, the kernel will only load validly signed modules
for which it has a public key. Otherwise, it will also load modules that are
unsigned. Any module for which the kernel has a key, but which proves to have
--
2.0.4


\
 
 \ /
  Last update: 2014-11-07 05:41    [W:0.020 / U:1.040 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site