On Wed, 26 Sep 2007, Miloslav Semler wrote: > so there is no discussion about mount & others. I think, if you have > CAP_SYS_MOUNT/CAP_SYS_ADMIN, you need not solve chroot() and how to > break it. CAP_SYS_PTRACE allows you to break out of chroot in a pretty trivial way too. -- Jiri Kosina - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- References:
- Re: sys_chroot+sys_fchdir Fix
- From: David Newall <[email protected]>
- Re: sys_chroot+sys_fchdir Fix
- From: "Serge E. Hallyn" <[email protected]>
- Re: sys_chroot+sys_fchdir Fix
- From: David Newall <[email protected]>
- Re: sys_chroot+sys_fchdir Fix
- From: "Serge E. Hallyn" <[email protected]>
- Re: sys_chroot+sys_fchdir Fix
- From: David Newall <[email protected]>
- Chroot bug (was: sys_chroot+sys_fchdir Fix)
- From: David Newall <[email protected]>
- Re: Chroot bug (was: sys_chroot+sys_fchdir Fix)
- From: Alan Cox <[email protected]>
- Re: Chroot bug
- From: David Newall <[email protected]>
- Re: Chroot bug
- From: Alan Cox <[email protected]>
- Re: Chroot bug
- From: David Newall <[email protected]>
- Re: Chroot bug
- From: Adrian Bunk <[email protected]>
- Re: Chroot bug
- From: Kyle Moffett <[email protected]>
- Re: Chroot bug
- From: David Newall <[email protected]>
- Re: Chroot bug
- From: Kyle Moffett <[email protected]>
- Re: Chroot bug
- From: Miloslav Semler <[email protected]>
- Re: Chroot bug
- From: Kyle Moffett <[email protected]>
- Re: Chroot bug
- From: Miloslav Semler <[email protected]>
- Re: sys_chroot+sys_fchdir Fix
- Prev by Date: Re: kernel Oops in ext3 code
- Next by Date: Re: lockdep wierdness...
- Previous by thread: Re: Chroot bug
- Next by thread: Re: Chroot bug
- Index(es):
 |