From: "Guillaume Chazarain" <guichaz@gmail.com>
To: "Pawel Plociennik" <paplociennik@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] chroot= as a new kernel parameter
Date: Sun, 2 Mar 2008 17:00:35 +0100 [thread overview]
Message-ID: <3d8471ca0803020800m6ef56c7enc5e9b28852266c9f@mail.gmail.com> (raw)
In-Reply-To: <200803011409.59526.paplociennik@gmail.com>
On Sat, Mar 1, 2008 at 8:09 PM, Pawel Plociennik <paplociennik@gmail.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
next prev parent reply other threads:[~2008-03-02 16:00 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 19:09 [PATCH] chroot= as a new kernel parameter Pawel Plociennik
2008-03-01 18:47 ` Alexandre Oliva
2008-03-01 19:44 ` Stefan Hellermann
2008-03-02 11:17 ` Kasper Sandberg
2008-03-02 15:35 ` Pavel Machek
2008-03-02 15:53 ` Filippo Zangheri
2008-03-02 16:00 ` Guillaume Chazarain [this message]
2008-03-02 23:59 ` Pawel Plociennik
2008-03-02 18:05 ` Guillaume Chazarain
2008-03-03 1:09 ` Pawel Plociennik
2008-03-03 14:12 ` Pavel Machek
2008-03-03 15:19 ` Guillaume Chazarain
2008-03-05 13:38 ` Pawel Plociennik
2008-03-05 8:10 ` Pavel Machek
2008-03-05 13:23 ` Guillaume Chazarain
2008-03-06 4:51 ` Pawel Plociennik
2008-03-06 4:54 ` Pawel Plociennik
2008-03-06 4:59 ` Pawel Plociennik
2008-03-02 19:05 ` Alan Cox
2008-03-03 14:11 ` Pavel Machek
[not found] <a2zNf-7rl-7@gated-at.bofh.it>
[not found] ` <a2YVo-4N6-27@gated-at.bofh.it>
[not found] ` <a3k9B-4Cf-43@gated-at.bofh.it>
2008-03-03 16:08 ` Bodo Eggert
[not found] ` <a3k9y-4Cf-35@gated-at.bofh.it>
[not found] ` <a3kMn-5Jb-25@gated-at.bofh.it>
[not found] ` <a3Wop-6Xn-15@gated-at.bofh.it>
[not found] ` <a41Rb-7mN-9@gated-at.bofh.it>
2008-03-06 0:16 ` Bodo Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d8471ca0803020800m6ef56c7enc5e9b28852266c9f@mail.gmail.com \
--to=guichaz@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paplociennik@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).