sshd: fork of unprivileged child failed

2006-06-04 Thread Robin Walker
I have a system with Cygwin sshd installed that refuses to accept connections. sshd is running and listening on port 22. In the Windows Application Log there are, for each failed connection attempt, entries of the form: sshd: PID : fatal: fork of unprivileged child failed. In sshd.log t

Re: sshd: fork of unprivileged child failed

2006-06-04 Thread René Berber
Robin Walker wrote: > I have a system with Cygwin sshd installed that refuses to accept > connections. sshd is running and listening on port 22. > > In the Windows Application Log there are, for each failed connection > attempt, entries of the form: > > sshd: PID : fatal: fork of unprivileg

Re: sshd: fork of unprivileged child failed

2006-06-04 Thread Robin Walker
--On 04 June 2006 16:27 -0500 René Berber <[EMAIL PROTECTED]> wrote: Robin Walker wrote: I have a system with Cygwin sshd installed that refuses to accept connections. sshd is running and listening on port 22. In the Windows Application Log there are, for each failed connection attempt, entr

Re: sshd: fork of unprivileged child failed

2006-06-04 Thread Larry Hall (Cygwin)
Robin Walker wrote: I have a system with Cygwin sshd installed that refuses to accept connections. sshd is running and listening on port 22. In the Windows Application Log there are, for each failed connection attempt, entries of the form: sshd: PID : fatal: fork of unprivileged child f

Re: sshd: fork of unprivileged child failed

2006-06-04 Thread René Berber
Robin Walker wrote: > --On 04 June 2006 16:27 -0500 René Berber wrote: Please sanitize the responses, we don't want our e-mail addresses in the open. >> Robin Walker wrote: >> >>> I have a system with Cygwin sshd installed that refuses to accept >>> connections. sshd is running and listening on

Re: sshd: fork of unprivileged child failed

2006-06-05 Thread Robin Walker
--On 04 June 2006 19:06 -0500 René Berber wrote: Robin Walker wrote: --On 04 June 2006 16:27 -0500 René Berber wrote: Robin Walker wrote: In the Windows Application Log there are, for each failed connection attempt, entries of the form: sshd: PID : fatal: fork of unprivileged child fail

Re: sshd: fork of unprivileged child failed

2006-06-05 Thread Robin Walker
--On 04 June 2006 18:18 -0400 "Larry Hall (Cygwin)" wrote: Robin Walker wrote: In the Windows Application Log there are, for each failed connection attempt, entries of the form: sshd: PID : fatal: fork of unprivileged child failed. Did you try a recent snapshot? If, by "snapshot", you

Re: sshd: fork of unprivileged child failed

2006-06-05 Thread Larry Hall (Cygwin)
Robin Walker wrote: --On 04 June 2006 18:18 -0400 "Larry Hall (Cygwin)" wrote: Robin Walker wrote: In the Windows Application Log there are, for each failed connection attempt, entries of the form: sshd: PID : fatal: fork of unprivileged child failed. Did you try a recent snapshot? If

Re: sshd: fork of unprivileged child failed

2006-06-05 Thread Robin Walker
--On 05 June 2006 08:23 -0400 "Larry Hall (Cygwin)" wrote: Robin Walker wrote: --On 04 June 2006 18:18 -0400 "Larry Hall (Cygwin)" wrote: Robin Walker wrote: In the Windows Application Log there are, for each failed connection attempt, entries of the form: sshd: PID : fatal: fork of unp

Re: sshd: fork of unprivileged child failed

2006-06-05 Thread Larry Hall (Cygwin)
Robin Walker wrote: --On 05 June 2006 08:23 -0400 "Larry Hall (Cygwin)" wrote: Robin Walker wrote: --On 04 June 2006 18:18 -0400 "Larry Hall (Cygwin)" wrote: Robin Walker wrote: In the Windows Application Log there are, for each failed connection attempt, entries of the form: sshd: PID xxx

Re: sshd: fork of unprivileged child failed

2006-06-05 Thread Robin Walker
--On 05 June 2006 14:23 +0100 Robin Walker wrote: Instant success with 20060604 version of cygwin1.dll I spoke too soon. When I restored "UsePrivilegeSeparation yes" and restarted Windows, ssh connections failed again. This time the client log was: C:\Documents and Settings\rdhw>ssh -vv