Windows Server 2012R2 64bit and 32bit Cygwin sshd

Achim Gratz Stromeko@NexGo.DE
Tue Aug 19 13:37:00 GMT 2014

Achim Gratz <Stromeko <at>> writes:
> I'm not making progress on this, but I've come to the conclusion that it
> is highly unlikely that the existence of the second (64bit) Cygwin
> installation has anything to do with the problem, first reported here:
> Meanwhile I've tried to make sure that the two installations don't
> interact by creating a separate privileged user for both of them, but
> that's not made a difference.
> So let me re-phrase the question, given:
> - Windows Server 2012R2 64bit running on hardware
> - Cygwin 32bit (latest snapshot from 2014-08-18 w/ AD integration)
> can anybody confirm they have gotten sshd successfully running?  As far
> as I can debug this, the sshd I have installed goes through all the
> motions of checking and setting up the environment, but any process it
> then spawns to actually run my command or shell immediately exits.

I've run strace on both the 32bit and the 64bit sshd and here's the
difference between the two, right after sshd gets an exception 5 from the DC:

--- Process 5820, exception 00000005 at 75BF1D4D
43239 4372793 [waitproc] sshd 2400 pinfo::maybe_set_exit_code_from_windows:
pid 5820, exit value - old 0x0, windows 0x5, cygwin 0x8000500

--- Process 484, exception 00000005 at 00007FFA4F5D5BF8
 9907 4522411 [main] sshd 484 seterrno_from_win_error:
windows error 5
   36 4522447 [main] sshd 484 geterrno_from_win_error: windows error 5 ==
errno 13

The 64bit sshd then proceeds to fetch my credentials from the registry and
forks the command, while the 32bit winds down and does an exit(5).

Ideas?  I have done a passwd -R in both environments just in case these
would be stored in different registry keys.


Problem reports:
Unsubscribe info:

More information about the Cygwin mailing list