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

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]

Date:	Sun, 18 Dec 2011 10:19:12 -0500
From:	Colin Walters <walters@...bum.org>
To:	"Andrew G. Morgan" <morgan@...nel.org>
Cc:	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>, serue@...ibm.com,
	dhowells@...hat.com, kzak@...hat.com
Subject: Re: chroot(2) and bind mounts as non-root

On Sat, 2011-12-17 at 17:22 -0800, Andrew G. Morgan wrote:

> I don't read any issues with this in your original post. What I read
> there is that you want to run a build in a chroot environment. Are you
> also implying that the user gets to build this chroot filesystem from
> nothing - without any privileges - 

Yes.  The filesystem is owned by the user.  

> If the former, then yes I think you are going to have a very hard
> time.

Well, it already works with the setuid program I attached earlier.
So...what are we trying to accomplish in this discussion? 

If you think there's a way to allow users to chroot *without* cutting
off setuid binaries, I am definitely interested in that.  However I'm
very, very skeptical.


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