lkml.org 
[lkml]   [2001]   [Jun]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH] User chroot
hpa@zytor.com (H. Peter Anvin)  wrote on 27.06.01 in <9hd7pl$86f$1@cesium.transmeta.com>:

> By author: kaih@khms.westfalen.de (Kai Henningsen)

> > jc@lysator.liu.se (Jorgen Cederlof) wrote on 27.06.01 in
> > <20010627014534.B2654@ondska>:
> >
> > > If we only allow user chroots for processes that have never been
> > > chrooted before, and if the suid/sgid bits won't have any effect under
> > > the new root, it should be perfectly safe to allow any user to chroot.
> >
> > Hmm. Dos this work with initrd and root pivoting?
> >
>
> At the moment, yes. Once Viro gets his root-changes in, this breaks,
> since ALL processes will be chrooted.

About what I expected. So you'd really want this flag to be resettable by
root, if you go that way at all. Beginning to look a little too compley, I
think.

The last time, ISTR we discussed some other, similar-but-different
syscalls that made for more secure jails. I don't quite remember the
details, though.


MfG Kai
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 12:55    [W:0.070 / U:0.368 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site