DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=Fec+DIzNe05qE8BXTLnD8bV6adw/zHM70CQ2VwaXjURAWvdn/UIpT
	0cnK/MP8mc8A+4Q7X8QfueNZyl9tYSijBopKG3ouNBO5fbRDHVheQA9oq+g8TXGw
	R3W0HHadbF6BrA18ZYuw0EVE8o0kZTMgeqtPfFkOfuQdTEADf41ueU=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 18 Feb 2019 15:11:11 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: Problem with sshd on W7 with 32bit cygwin 3.0
Message-ID: <20190218141111.GZ4256@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20190218105842 DOT GA1050 AT GIOVE>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="c7rykKtsZvepKFKR"
Content-Disposition: inline
In-Reply-To: <20190218105842.GA1050@GIOVE>
User-Agent: Mutt/1.10.1 (2018-07-13)

--c7rykKtsZvepKFKR
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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".
>=20
> 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

--=20
Corinna Vinschen
Cygwin Maintainer

--c7rykKtsZvepKFKR
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxqvP8ACgkQ9TYGna5E
T6B4aQ//UWuzOAAgWNQQt6iPqFPxGtJbx9SKnvSOpByGhysyKfAv13tmTuCeNwhQ
74qLLYw9Zc3JjupJYolahxNFi+rf9R0qqobIWy4sDHYbgkmQ3nunkbAdSvnoer9r
XnRCw2AQlz4S6AKGqBwO6Is+dxDjm0Mmu83kJjZUzpg8Ibnty38Lp17GijchxImg
mB8VwuB6UUm3xej7FhGfYF5bvm3sIGUqD3zw1wPAzELi7pPon/mBOZ4HRyLIhN/4
kEwpaLPBweYx/Khif390O4mY7beFVIAeq1qA6t9yQTqOlrpeqharaLh/AJPRfME2
kp7awjmPGeDCm9XgeB+Fr3glyEw1BX6psBqaL2pagKA7biPZZQiGw7x8WcNDyTgC
+YjhNxEo4K4axQYm+yIw6rCBtIbuEPUp+EJln+2KswVdCeCpPCBJlbHxojkYFqNd
zmUl7pdM1HbuALRSkl/4rSLX6IxhbanZv1q3aX4OLjFQUU5cQ1kU7+TNlK7WV/pi
5VevTx46k+H4KBbSt/NTTz2eIHdh0FoWdMvMm96ICuzfOVxspHUcxDfLqKbqJwAE
q+p05Vho1lM2py0Hn6iACyjiN0/2f4e17SUxoiAwOPm3z1Vq4m/MqO6inMeWm4yT
0SWdOwaGSiQSP8YLoLd+nQLGwKwy7Rm19TLw8852xvmFX8J4npk=
=9dr6
-----END PGP SIGNATURE-----

--c7rykKtsZvepKFKR--