| 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
| ||
|
Message-ID: <Pine.LNX.4.58.0707141629510.5288@be1.lrz> Date: Sat, 14 Jul 2007 17:20:04 +0200 (CEST) From: Bodo Eggert <7eggert@....de> To: "H. Peter Anvin" <hpa@...or.com> cc: Bodo Eggert <7eggert@....de>, linux-kernel@...r.kernel.org Subject: Re: [PATCH 0/3][try 1] init: enable system-on-initramfs On Fri, 13 Jul 2007, H. Peter Anvin wrote: > Bodo Eggert wrote: > > On Fri, 13 Jul 2007, H. Peter Anvin wrote: > >> Bodo Eggert wrote: > >>> I toyed with setting up a diskless system in initramfs. In the process, I > >>> came across some things: > >>> > >>> 1) There is no way to have the kernel not mount a filesystem, > >>> unless you use /init or rdinit=. > >> And? Just use rdinit=/sbin/init and no patch is needed. > > > > rdinit is supposed to do a different job from /sbin/init, therefore it > > will not do the security callbacks the original code would do. > > > > And besides that, it feels like turning the wrong knob for that task. > > No, it is exactly the right knob for the task. Setting the name of the rdinit process to the name of the init process in order to select the root device should not be the right knob. > The fact that the security callbacks don't get invoked when using an > initramfs *AT ALL* is the real problem. It's one more problem. -- Interchangeable parts aren't. - 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