On Thu, 16 Nov 2000, jesse wrote: > But the problem is because you can call chroot when you're already chrooted. It's a non-problem. chroot()ing again may also be used to de-escalate privileges, and if you want to prevent breaking out of a chroot, drop root privileges, since chroot is a privileged call. And DO USE setuid, not seteuid or something (otherwise the saved set-uid will bite you). -- Matthias Andree - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] Please read the FAQ at http://www.tux.org/lkml/
- Re: Linux 2.2.18pre21 Matthias Andree
- Re: Linux 2.2.18pre21 Andrea Arcangeli
- Re: Linux 2.2.18pre21 jesse
- chroot [Was: Re: Linux 2.2.18pre21] Kurt Roeckx
- Re: Linux 2.2.18pre21 Alan Cox
- Re: Linux 2.2.18pre21 Rogier Wolff
- Re: Linux 2.2.18pre21 kuznet
- Re: Linux 2.2.18pre21 Rogier Wolff
- Re: Linux 2.2.18pre21 kuznet
- Re: Linux 2.2.18pre21 Rogier Wolff
- Re: Linux 2.2.18pre21 Matthias Andree
- Re: Linux 2.2.18pre21 Peter Samuelson
- Re: Linux 2.2.18pre21 H. Peter Anvin
- Re: Linux 2.2.18pre21 Peter Samuelson
- Re: Linux 2.2.18pre21 H. Peter Anvin
- Re: Linux 2.2.18pre21 Matthias Andree
- Re: Linux 2.2.18pre21 jesse
- Re: Linux 2.2.18pre21 Pavel Machek
- Re: Linux 2.2.18pre21 Nix
- Re: Linux 2.2.18pre21 Peter Samuelson
- Re: Linux 2.2.18pre21 willy tarreau