This is the mail archive of the
mailing list for the Cygwin project.
Re: [Patch] Fixing the PROCESS_DUP_HANDLE security hole.
On Thu, Dec 23, 2004 at 11:59:59PM -0500, Pierre A. Humblet wrote:
>At 11:35 PM 12/23/2004 -0500, Christopher Faylor wrote:
>>I don't think you need it. You just need to tell a process which is
>>about to exec after having been execed to make sure that its
>>wr_proc_pipe is valid.
>Yes, that's the key. So the question is only about method. Either the parent
>guarantees that the child has a valid handle, or the child must check
>that it already has a valid handle or wait until it does.
I have just implemented code which causes an execed child to wait for the
parent to fill in its wr_proc_pipe if it is going to exec again. It uses
a busy loop but I think it's unlikely that the loop will be exercised too
I'm testing it now.