linux-kernel - Re: blacklist kernel boot option

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]

Date:	Mon, 29 Jan 2007 14:23:13 +0100 (MET)
From:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
To:	Oliver Neukum <oliver@...kum.name>
cc:	Gerd Hoffmann <kraxel@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: blacklist kernel boot option

On Jan 29 2007 13:44, Oliver Neukum wrote:
>Am Montag, 29. Januar 2007 13:40 schrieb Jan Engelhardt:
>> >Is that an real-live issue, with distro kernels being shipped with
>> >almost everything compiled as module these days?
>> 
>> For me it was. FC6 has at least CONFIG_MD=y, and SUSE also has
>> some =y that could be =m with the help of module autoload rules,
>> and some =y that could truly be =m. Those being =y cannot be
>> blacklisted.
>
>What use is it to modularly compile something that almost everybody needs?

[correction: meant CONFIG_BLK_DEV_MD, because CONFIG_MD itself does
not generate any code]

So just because almost everyone needs CONFIG_SCSI (SATA, usb_storage,
you name it), you're going to compile that in as well? It's just
another 180 KB [BLK_DEV_MD: ~100K] so let's compile it in!

There is a reason initramfs exists, and it's not only for firmware
loading or running custom scripts.
-
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/