linux-kernel - Re: [PATCH] chroot= as a new kernel parameter

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: <3d8471ca0803020800m6ef56c7enc5e9b28852266c9f@mail.gmail.com>
Date:	Sun, 2 Mar 2008 17:00:35 +0100
From:	"Guillaume Chazarain" <guichaz@...il.com>
To:	"Pawel Plociennik" <paplociennik@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] chroot= as a new kernel parameter

On Sat, Mar 1, 2008 at 8:09 PM, Pawel Plociennik <paplociennik@...il.com> wrote:
>  In the short this patch has added a new chroot= kernel parameter which can be used
>  to changing a chroot of an init process before it will has been runed.

Wouldn't booting with 'init=/usr/sbin/chroot /path /sbin/init' achieve
the same effect?
Haven't tested it, just wondering.

>  +       if(chroot_str) {
>  +               if(sys_chroot(chroot_str) < 0)
>  +                       printk("chroot=%s failed\n", chroot_str);
>  +               else
>  +                       printk("chroot=%s successed\n",chroot_str);
>  +       }

Continuing booting normally when the chroot failed sounds like a
security issue to me.

Regards.

-- 
Guillaume
--
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/