lists.openwall.net   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  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Message-Id: <1415333847-14543-1-git-send-email-michael.marineau@coreos.com>
Date:	Thu,  6 Nov 2014 20:17:27 -0800
From:	Michael Marineau <michael.marineau@...eos.com>
To:	linux-kernel@...r.kernel.org
Cc:	Michael Marineau <michael.marineau@...eos.com>,
	David Howells <dhowells@...hat.com>,
	James Solner <solner@...atel-lucent.com>
Subject: [PATCH] Document correct module signature kernel parameter

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@...eos.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

--
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

Powered by Openwall GNU/*/Linux Powered by OpenVZ