Al Viro wrote:
Oh, for fsck sake... Folks, it's standard-required behaviour. Ability to chroot() implies the ability to break out of it. Could we please add that (along with reference to SuS) to l-k FAQ and be done with that nonsense?
I'm pretty confident that it's only standard behavior for Linux. Every other unix says it's not allowed.
- 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/
- Follow-Ups:
- Re: sys_chroot+sys_fchdir Fix
- From: Christer Weinigel <christer@weinigel.se>
- Re: sys_chroot+sys_fchdir Fix
- From: Al Viro <viro@ftp.linux.org.uk>
- Re: sys_chroot+sys_fchdir Fix
- From: Alan Cox <alan@lxorguk.ukuu.org.uk>
- Re: sys_chroot+sys_fchdir Fix
- References:
- sys_chroot+sys_fchdir Fix
- From: majkls <majkls@prepere.com>
- Re: sys_chroot+sys_fchdir Fix
- From: Alan Cox <alan@lxorguk.ukuu.org.uk>
- Re: sys_chroot+sys_fchdir Fix
- From: Bill Davidsen <davidsen@tmr.com>
- Re: sys_chroot+sys_fchdir Fix
- From: Alan Cox <alan@lxorguk.ukuu.org.uk>
- Re: sys_chroot+sys_fchdir Fix
- From: David Newall <david@davidnewall.com>
- Re: sys_chroot+sys_fchdir Fix
- From: Phillip Susi <psusi@cfl.rr.com>
- Re: sys_chroot+sys_fchdir Fix
- From: Alan Cox <alan@lxorguk.ukuu.org.uk>
- Re: sys_chroot+sys_fchdir Fix
- From: Phillip Susi <psusi@cfl.rr.com>
- Re: sys_chroot+sys_fchdir Fix
- From: Al Viro <viro@ftp.linux.org.uk>
- sys_chroot+sys_fchdir Fix
- Prev by Date: Re: Chroot bug
- Next by Date: [PATCH] Since we have counters in __u64 format we have to print them with %llu macros.
- Previous by thread: Re: sys_chroot+sys_fchdir Fix
- Next by thread: Re: sys_chroot+sys_fchdir Fix
- Index(es):
 |