From: edward_at_paradigm4.com.au
Date: Tue 05 Feb 2002 - 07:52:49 GMT
I still don't understand why we need chmod 0 tricks.
Isn't the following good enough?
/* chroot call - still leaves the cwd pointing outside vserver */
if(chroot(root_dir)) { perror("chroot failed"); exit(1) };
/* fix the cwd */
if(chdir("/") { perror("chdir failed"); exit(1) };
/* it should be safe at this point, right? */
/* and of course, now you can also */
/* drop the CAP_SYS_CHROOT for the truly paranoid */
Ed
On Monday, 4 February 2002 at 23:47, Jacques Gelinas wrote:
> On Mon, 4 Feb 2002 23:56:12 -0500, Ron Arts wrote
>
> > I experience the same problem on a plain redhat-7.2 distribution and
> > 2.4.17ctx6. Also straced useradd, and came to the same conclusion: umask(0777)
> > gives problems when creating files. I don't think its an application
> > problem.
>
> I confirmed this was a ctx-6 issue today. I will do ctx-7 tomorrow.
>
>
> ---------------------------------------------------------
> Jacques Gelinas <jack_at_solucorp.qc.ca>
> vserver: run general purpose virtual servers on one box, full speed!
> http://www.solucorp.qc.ca/miscprj/s_context.hc
>