X-Recipient: archive-cygwin@delorie.com
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=mbHTdzBsSc/J0+e2SAh8dTDcecvMDYGH7m3FYAVb2rOzYcaePUfJj
	w9CDaYp84cmSeIwHGVyvgSmbuaMW+RW1mGxUZ+vcKIuYQKhmiwncR/vGUaSSoyXL
	W7rYsJQt3bA1ShqZgR1Iu/93u5+dQ9vY0Gx26j7S30cwXsHrzetXyA=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default;
	 bh=r1oJohhTqoHTwCV4tKlVBxwnUaE=; b=XMgY72f05HrvF5xt04X4WOMkuclB
	ji5LHOhyUkLcq+ZXm6DDjItdtBUA4emzkstRkBkIeh5McEtv8cT3BFFus4dqcaxJ
	AAAYnrALOZObDhqnfh5mfSnJ7lex1oyvJQgXaqLmd52al/OsMoadUCd8DVgt8YEm
	Tttvnpi/10kjMwE=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-100.4 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,KAM_NUMSUBJECT,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=H*F:D*cygwin.com
X-HELO: mout.kundenserver.de
Date: Mon, 18 Feb 2019 21:54:50 +0100
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Problem with sshd on W7 with 32bit cygwin 3.0
Message-ID: <20190218205450.GI4256@calimero.vinschen.de>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20190218105842.GA1050@GIOVE> <20190218141111.GZ4256@calimero.vinschen.de> <20190218160402.GA1319@GIOVE>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="ZQ93ZA/51YEIDw4/"
Content-Disposition: inline
In-Reply-To: <20190218160402.GA1319@GIOVE>
User-Agent: Mutt/1.10.1 (2018-07-13)

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

On Feb 18 17:04, Enrico Forestieri wrote:
> On Mon, Feb 18, 2019 at 03:11:11PM +0100, Corinna Vinschen wrote:
> >=20
> > Two workarounds for now:
> >=20
> > - Start sshd as 64 bit Cygwin process.
> > - Utilize https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd3
>=20
> Thank you. The second method above worked. This is a private network,
> so that is Ok.

I uploaded new developer snapshots with fixes for this problem:
https://cygwin.com/snapshots/  Please give it a try.=20


Thanks,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--ZQ93ZA/51YEIDw4/
Content-Type: application/pgp-signature; name="signature.asc"

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxrG5oACgkQ9TYGna5E
T6ArLhAAnk7cy6+++0wFh4EaGXGHnTh+kJCThdwR8yfzV9ynI7Ed9PiodvL6GeHo
OJNeEd9Tqmuma2UrZTfIUvpjN5z3W8cn9toO7umwYDSklO2zbrKCC0AkHcXluKb9
nKPiNZt52f4mGSKi1WUyy+5UYZW+wr/Vb+3VvWSW01i8B8cZuy7z7uVZalS72sJO
m823YHYoix5Ghm1RxpiFToc2AKlVyjsO1EF7NIhPKrSYQYelBjwXGqSiP6bKBarB
BrOupGOL21mP9kd97CKtIb+ZHQ+LQuVF0wPuGznrzx1OyzB2Q7XAiX7RbbuHRD7M
HbHfd/5YWVeFswIr4coSeszBzOOwkDkuH30vwV2fzGXbNlX2Due9QuOqeeJhPs2v
gEnlfN4KOZdnHRm0SQeQptMwGhEBr1VLXQ6eOrY5stXRYofMyrAtYeXRtQo0oi8b
aXQwvec6Xz28wuy4gOHxsPRwNxB+KRk9W6nDYKXOOgWPOzjjwCNaCe3RuAT13mib
RPaYW0U7naoI31XBU9qj7eBpS8E47p+rSF+L3g6YuqM7mwQIkujkmrfIOt65Oosf
ROmME0Y+kn2BJuGSnMgOjvvXxqOk4R8r0UVGjyhkzP75lkAdOdjSBCFWeQ6BcMTM
w3MHq76K53TQK6kvAOt6UZZ2RMSa90n9ijARDSuWBGovB7iFkQk=
=ou6F
-----END PGP SIGNATURE-----

--ZQ93ZA/51YEIDw4/--
