linux-kernel - Re: [PATCH] allow kernel module exclusion on load

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

Message-ID: <464759BF.5050505@msgid.tls.msk.ru>
Date:	Sun, 13 May 2007 22:32:31 +0400
From:	Michael Tokarev <mjt@....msk.ru>
To:	Dan Aloni <da-x@...atomic.org>
CC:	Stephen Hemminger <shemminger@...ux-foundation.org>,
	Linux Kernel List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] allow kernel module exclusion on load

Dan Aloni wrote:
[]
> Yes, I guess a shell script can always look at /proc/cmdline with
> relatively minimal complexity.
> 
> Anyway, it all boils down to whether there's a developer demand 
> for a userspace-independent way of blacklisting modules. Let's see 
> if more people post their opinion so we can determine.

The real problem here - again IMHO - is the complete lack of more-or-less
standard boot sequence.  Every distro invents their own intramfs with
unique recognized command-line arguments.

And kinit/klibc doesn't really help here, because it's too low-level.

/mjt

P.S.  I wonder why certain emails are duplicated on LKML.  An example
is my previous email in this thread - I received two copies of it
from linux-kernel-owner@...r.
-
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/