Bug 3022

Due to limitations in Windows, the CreateProcess() API accepts anonymous pipes for the stdin, stdout, and stderr handles.  However, buried in the MSDN docs is information that states that anonymous pipes cannot be made non-blocking.  This creates a situation where two processes can deadlock (e.g. one process is blocking on stdin while another process is blocking on stdout or stderr).

There are two known fixes for this on Windows:  Use multiple threads (one thread for each pipe) or use a little-known mode of CreateProcess() and pass connected TCP/IP socket handles for each of the pipes to the target process instead of anonymous pipes.  Not all languages support multithreading and using a thread per pipe is kind of wasteful of system resources.  Of course, establishing a TCP/IP connection per pipe is also wasteful but enables single-threaded, non-blocking code to work without deadlocking both processes.  Most processes work fine with TCP/IP stdout/stderr (TCP/IP stdin is a bit more iffy and depends on how the underlying C library works).

OpenSSH calls dup() in ssh.c and then bails out with the error message "dup() in/out/err failed" when it can't duplicate socket handle(s).  The connection then terminates.