linux-kernel - [PATCH] Documentation: cover CONFIG_BINFMT

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>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAN3tLtJruJKYOmyg_XQqRW+fXQegXfxpBLg4HL1dx9e2jvjmqA@mail.gmail.com>
Date:	Thu, 30 May 2013 13:24:15 -0600
From:	Kris Rusocki <kszysiu@...xis.org>
To:	linux-doc@...r.kernel.org, andi@...as.de
Cc:	rob@...dley.net, linux-kernel@...r.kernel.org
Subject: [PATCH] Documentation: cover CONFIG_BINFMT_SCRIPT in init.txt

From: Kris Rusocki <kszysiu@...xis.org>

Now that binfmt_script is configurable, explain yet another possible
cause of boot failure (a script w/CONFIG_BINFMT_SCRIPT != y).

Signed-off-by: Kris Rusocki <kszysiu@...xis.org>
---
 Documentation/init.txt |    5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/Documentation/init.txt b/Documentation/init.txt
index 535ad5e..8c6af4f 100644
--- a/Documentation/init.txt
+++ b/Documentation/init.txt
@@ -29,8 +29,9 @@
 E) make sure the binary's architecture matches your hardware.
    E.g. i386 vs. x86_64 mismatch, or trying to load x86 on ARM hardware.
    In case you tried loading a non-binary file here (shell script?),
-   you should make sure that the script specifies an interpreter in its shebang
-   header line (#!/...) that is fully working (including its library
+   you should make sure that your kernel supports script execution
+   (CONFIG_BINFMT_SCRIPT=y) and the script specifies an interpreter in its
+   shebang header line (#!/...) that is fully working (including its library
    dependencies). And before tackling scripts, better first test a simple
    non-script binary such as /bin/sh and confirm its successful execution.
    To find out more, add code to init/main.c to display kernel_execve()s
--
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/