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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200701291344.45299.oliver@neukum.name>
Date:	Mon, 29 Jan 2007 13:44:42 +0100 (MET)
From:	Oliver Neukum <oliver@...kum.name>
To:	Jan Engelhardt <jengelh@...ux01.gwdg.de>
Cc:	Gerd Hoffmann <kraxel@...e.de>, linux-kernel@...r.kernel.org
Subject: Re: blacklist kernel boot option

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?

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