Re: Problem with sshd on W7 with 32bit cygwin 3.0

[Corinna Vinschen <corinna-cygwin at cygwin dot com>]

On Feb 18 11:58, Enrico Forestieri wrote:
> After upgrading to cygwin 3.0.0 (32bit version) on W7 64bit, it is
> not possible to connect using ssh. The returned error is something
> like "Connection closed by x.x.x.x port 22".
> 
> I also tried the 2019-02-18 snapshot without success.
> However, simply downgrading to 2.11.2 fixes the issue.

I tested this myself and from what I can tell, Microsoft didn't
implement S4U for local accounts on WOW64 on older OSes.  If I
start a 32 bit sshd from an Windows 7 64 bit WOW64 environment,
then domain accounts work fine using kerberos S4U, but for local
accounts with MsV1_0 S4U the underlying Windows function returns
STATUS_INVALID_PARAMETER.

Note that this works fine in Windows 7 64 bit with 64 bit Cygwin.  It
seems only older WOW64 environments (maybe even only in W7) didn't
implement this.

Two workarounds for now:

- Start sshd as 64 bit Cygwin process.
- Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer

Attachment: signature.asc
Description: PGP signature