On Tue, 30 Sep 2008 21:19:27 +0900 Charles Plessy <plessy@debian.org> wrote: > the idea looks intersting, but in the end the consequence is that the > administrators have to learn one more tool, that looks very complex, Any admin who does not understand 'chroot' should not be an admin. Anyway, why the need for an admin? Create a chroot on your own system. > whereas one of the goals of letting the user installing packages in his > home directory is to not bother the admins. Also, as giving schroot > access means giving opportunity to get root priviledges, Absolute TOSH. The whole point of schroot is that, once the chroot is created, users do not need root access. If the admin is half-sensible, the admin creates the chroot in /jails/foo/ and users use schroot. There is no way that a user can escape a chroot and retain root access. There is no way that root access within a chroot can affect the rest of the system - that is the point of a jail. > it is something > that definitely sounds scary even in trusted environments. It is asolutely not scary - that is why it is supported on Debian machines. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgpvbrKX1iS7q.pgp
Description: PGP signature