From: Colin Walters <walters@verbum.org>
To: John Stoffel <john@stoffel.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: chroot(2) and bind mounts as non-root
Date: Fri, 09 Dec 2011 10:06:10 -0500 [thread overview]
Message-ID: <1323443171.6008.11.camel@lenny> (raw)
In-Reply-To: <20194.8535.854625.466329@quad.stoffel.home>
On Fri, 2011-12-09 at 09:55 -0500, John Stoffel wrote:
> I can see that, but maybe you can still fix this in userspace using
> the schroot tool others have mentioned.
No, because it requires root to edit /etc/schroot/schroot.conf. I've
already said this. What is not being understood?
Again, the design constraint I have is that you should be able to get a
plain regular Unix account on say some classical timesharing server (in
the cloud if you like, or your university's RHEL instance), and do the
build.
This is also advantageous even in the "building on personal laptop case"
in that there is *no* instance of a user process being in direct or
indirect control over processes started as root - much less chance one
of those random postinst scripts that run as root not noticing they're
in a chroot and screwing your system.
If you allow the a user to upload .debs to the URL in schroot.conf, all
you have created in the end is a very elaborate chmod u+s /bin/sh for
them.
Does that make sense? Stop telling me about schroot, I knew about it
even before I posted here, and I've already replied about it.
next prev parent reply other threads:[~2011-12-09 15:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 17:54 chroot(2) and bind mounts as non-root Colin Walters
2011-12-07 19:36 ` John Stoffel
2011-12-08 16:10 ` Colin Walters
2011-12-08 18:14 ` John Stoffel
2011-12-08 18:26 ` Colin Walters
2011-12-09 0:49 ` Sven-Haegar Koch
2011-12-09 14:55 ` John Stoffel
2011-12-09 15:06 ` Colin Walters [this message]
2011-12-08 17:04 ` Arnd Bergmann
2011-12-08 17:15 ` Colin Walters
2011-12-07 19:40 ` Andy Lutomirski
2011-12-08 16:58 ` Colin Walters
2011-12-07 20:34 ` H. Peter Anvin
2011-12-07 20:54 ` Alan Cox
2011-12-15 18:55 ` Andrew G. Morgan
2011-12-16 15:44 ` Colin Walters
2011-12-18 1:22 ` Andrew G. Morgan
2011-12-18 15:19 ` Colin Walters
2011-12-10 5:29 ` Serge E. Hallyn
2011-12-12 16:41 ` Colin Walters
2011-12-12 23:11 ` Serge E. Hallyn
2011-12-15 20:56 ` Colin Walters
2011-12-16 6:14 ` Eric W. Biederman
2011-12-18 16:01 ` Colin Walters
2011-12-19 0:55 ` Eric W. Biederman
2011-12-19 4:06 ` Serge E. Hallyn
2011-12-19 9:22 ` Eric W. Biederman
2011-12-20 16:49 ` Colin Walters
2011-12-20 21:23 ` Colin Walters
2011-12-21 18:15 ` Steve Grubb
2012-01-03 23:13 ` Eric W. Biederman
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=1323443171.6008.11.camel@lenny \
--to=walters@verbum.org \
--cc=john@stoffel.org \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.