X-Recipient: archive-cygwin AT delorie DOT 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=ttDDex+GPrQKidJOLScbT0GRJa8LyDVPIp2XmRbjbCEImty0ZvGS3
	kzloMN9Xrsz4t3TpNqwBzSp/ZCKS8EPY1QwL8wCNj3iPP7trbgmrltF6r4bk/xmj
	Hw4IuJrmTiN5T+WaW5YB8NjRQEGWt41A8X0ufCYWS6QY1DnaJNDwKw=
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=iQ6gdW188aprpb8+Ph2nWKrBePg=; b=ZiIgjPMOYlzx71BGK9aOc/TetiAr
	5YE7q9mZ/cGFF/50yEnLmcEaZFH5zbQ5qWx5P2omcvccD/QI6W5FzG9UFmyqrgPP
	Psg+D/LL6orW/G+Jeu3npO3rthEBHERv+lTZ3hYVH9Lw8fR/1netsZLoDuUuF2Si
	J5bIOSwDokqHdHg=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Authentication-Results: sourceware.org; auth=none
X-Spam-SWARE-Status: No, score=-100.9 required=5.0 tests=BAYES_00,GOOD_FROM_CORINNA_CYGWIN,KAM_LAZY_DOMAIN_SECURITY,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=wow64, WOW64, w10, W10
X-HELO: mout.kundenserver.de
Date: Wed, 20 Feb 2019 21:25:36 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
Message-ID: <20190220202536.GX4256@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <19759126 DOT 568100 DOT 1550686604174 DOT ref AT mail DOT yahoo DOT com> <19759126 DOT 568100 DOT 1550686604174 AT mail DOT yahoo DOT com> <alpine DOT DEB DOT 2 DOT 21 DOT 1902201038580 DOT 32163 AT ckhb05> <47883ab06634fed3ecdaa375016dc3fb AT smtp-cloud8 DOT xs4all DOT net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="mHEGYOlXWdrdotU2"
Content-Disposition: inline
In-Reply-To: <47883ab06634fed3ecdaa375016dc3fb@smtp-cloud8.xs4all.net>
User-Agent: Mutt/1.10.1 (2018-07-13)

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

On Feb 20 21:01, Houder wrote:
> On Wed, 20 Feb 2019 10:53:09, scowles at ckhb dot org wrote:
> >=20
> > i can confirm the same behaviours on a 3.0.0 system.  i've done several=
 checks=20
> > and have been unable to find the source of the problem.  ssh -vvv shows=
 that the=20
> > connection proceeds all the way through the connection process, sends t=
he=20
> > appropriate key tokens, then the server abruptly closes the connection.=
 all=20
> > accounts on the system show the same results.
> >=20
> > my 2.11.1 system, with identical ssh[d]_config files has no such proble=
ms.
> >=20
> > on both systems, all relevant files and directories have correct owners=
 and=20
> > permissions.
>=20
> Yes, failure for 3.0.0 (and 3.0.1); success for 2.11.2
>=20
> Henri
>=20
> 64-@@ uname -a
> CYGWIN_NT-6.1 Seven 3.0.1(0.338/5/3) 2019-02-20 10:19 x86_64 Cygwin
>=20
> 64-@@ tail /var/log/sshd.log
> Server listening on 0.0.0.0 port 222.
> seteuid 1004: Permission denied

Sorry guys, but I can't reproduce this problem at all.  I tested ssh
login on Vista, W7 and W10 1809, in each case on 64 bit and under
WOW64.  On all systems I can login with domain as well as local
accounts.

For completeness sake I started sshd under SYSTEM as wel as under
cyg_server account and every time it just worked.

The only reason for failing logins coming to mind is the case of
the usernames.  It must be written *exactly* as returned by
`getent passwd'.  I.e.:

  $ getent passwd | grep -i foo
  MACHINE+Foo:*:197608:197121:U-MACHINE\Foo,[...]

You have to login like this:

  $ ssh MACHINE+Foo

This will not work:

  $ ssh machine+foo


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxtt78ACgkQ9TYGna5E
T6Al6g/+O+joC3KzMVq1/O3VhyUZVq0kRT9KdOPLsAtSv1FkJnm/CTUIqqpWLaio
+UhnjfK8KWDpYqjWB9ieg/G9CXuX2ZVMfQxwO6JEK0MAi7Wnyh7fGEysWgIwZN+O
CkPpYtI5ZiBJIC1ikKk+hfrn+8e95hVRCHOF4TpP7T285sWvEW+z6vmF6Wh1EH4B
8B/C5VMzN57pZO80PlHZx2DCx8LcynslxnvjOYuRm0PG9WHFtO4yX5KcrD5UB0Eb
zKLCcIgJzOETkPMzVLzvuV3U39HTjObTZE3YRlx3fZxjPBn75prmRhyknNIghkkc
xuzhLmiaOPvfs+o+W3Vjif0aNNEOnwCaepMb7kBnE/TGRhhEBcuFWb7P18gzg2o3
8jXW2b1YhzmpwpyTc6PmKu4l+DxMvW79xhxFOIvO6ExnjzOAVlNT9yHtD9nkdhkW
al+aj0mjrtzknJ2svwz7+XGzOi6z8dzvxygv+dTRoRuqXjVM/QzQceYRQ4+8NWAx
A2dFHF0xL7YVPjZydCfeqH6eUPg3kJihyOLCSk3PNGQPp0894D9fDvWV9Rg2aJEN
ZdDvTxVabmu34ewIW0pYqtqJLf35tM6DeO0WQeBAAB5tA5ATx/Hn6+YXVQN+OPWY
mn9UUZbz3+FuszNihuOtHIQEUJyfSxxzX4kN2Dz2CwwJkyRX3aA=
=3iXS
-----END PGP SIGNATURE-----

--mHEGYOlXWdrdotU2--