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=l6lbDxWU89ZWIrCnJvbXdr53/vMvXnnZTkCod8IFAHs9C/sFDYJuM
	2XyEvPbp81std1SVBIc/NqV4eNGw2JAQmynhw2zaNHeUnJyoYyCqLDDQqPbgjyfl
	/4u7s1bOgubAz7XFUYNaAQme1QbAKxjpZuWi61+VOavv6mpN34SsYk=
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: Wed, 13 Feb 2019 11:32:00 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: sshd: computer name's case must match?
Message-ID: <20190213103200.GK3718@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <CANV9t=QxA_FW-3OCZuYFJpxrekbO8Yc-WsnxGLiyc0Bqz=fPUw AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="E7i4zwmWs5DOuDSH"
Content-Disposition: inline
In-Reply-To: <CANV9t=QxA_FW-3OCZuYFJpxrekbO8Yc-WsnxGLiyc0Bqz=fPUw@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)

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

On Feb 12 16:07, Bill Stewart wrote:
> Good day,
>=20
> I am testing sshd using the cygwin1.dll 3.x version (run as SYSTEM -
> S4U logon - works great!).
>=20
> One thing I've noticed is that if I use ssh log onto a remote
> domain-joined machine (e.g., connect with COMPUTER+localname), the
> 'COMPUTER' prefix must be uppercase - if I specify
> 'computer+LocalName', the user is unknown.
>=20
> This doesn't seem to be the case if I change the username's case -
> 'COMPUTER+localname' also works.
>=20
> Is this by design or by accident?

sshd checks usernames case-sensitive against their name stored in the
user DB.  The problem that you can use differently cased usernames
here is that the Windows function for checking the name is case-
insensitive, so it takes the username any way it comes in and
sshd eventually checks against the wrongly cased name.

I fixed that partially in Cygwin by making sure that the account name
stored in the internal passwd/group info is stored case-correct:
https://cygwin.com/git/?p=3Dnewlib-cygwin.git;a=3Dcommitdiff;h=3D9a3cc77b2a=
fc

So if you have a domain DOMAIN and a user xyz

$ getent passwd DoMaIn+XyZ

Prior to the above patch  it returned

  DOMAIN+XyZ:...

Now it will return

  DOMAIN+xyz:...

The problem is this:  If the account is from another domain than the
local machine or the machine domain, the call to LookupAccountSid to fix
the account name won't fix the account name.

Apparently the account name is cached on the local machine in exactly
the same spelling as has been used when asking for the account the first
time.  I still have to find a way to workaround that.


Thanks,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxj8iAACgkQ9TYGna5E
T6CE6w/+LjSHlZ1ANvgjpRJ+rS235xP/j3/Yz7Um3pGPzcAl18bm7/RgG+zW8BxB
teAOtXilkipQ/KmIaKxypURQjelDw/Yd5JrUEGfr9eZuJnJwk4eKaysLw7nb0Kbx
Jc5S1kXjcRm0li7kh5rMISBTfYthPQhZ0pm1nX1Jo7ZDKg2Wf7oXbdAiljxpjEx4
0+ZR5XilGaMmdLx27I3errgyK26d5UEVQvLYt6ao5xkFZfx6kOMRd5eBKbu1Zznz
CxoUj6Z8GRsUTEmrHfhSTFuGlZyARtAdTA3yaI6X7th2anelL1clgvZNrIrkCxuZ
88B1ZAG+FmNefP1G8JS6EhqiOtJT36bTnGefcad/Bvf7EywjNkMr/Ot0nhJtQ85+
orzzKYNiDdK0IoywPekJ2qQa4lO5am8WRL3zE+RwTVRu54jL4HB0mT8+Kh9ycNC7
8q+Z1x04Bzu6HV752AGTiOcCyNy3Wo+SpE2vbeKVzB3+yZR9n5QRat5LzuNZQrAZ
tEWoOBFNvakjT38vokeZQGBTUPoOqYrx8bpBGVuA+ICStDlIwXP3F+1zKVrAdYPi
UkuZmVZ6u1EaDqI3DL9d1LCPYD9ZsX/mHa6DWisfocPtjKUJ2M5vJDcEz5LiLdMl
SH+IlKGjBmDjBfctvyRAyeo8azyLQxALADa+32OLwZ05kNw4Gys=
=K2vT
-----END PGP SIGNATURE-----

--E7i4zwmWs5DOuDSH--