Re: chroot(2) and bind mounts as non-root

[Colin Walters <walters@verbum.org>]

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.