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=W1q4fs3LWLFrDA3MyYFqKqkPZVErBZTDV63c1MRFC3BLzbGYYSU2b
	6hf0S5+0FadfncVIHPtPP3iBW17jvyDQjAA1tW1lotu8pavuBfIipcBoBODpuYLO
	V5XrG0N7+qKZ+9+MHAspSYjpchg9gAXIt7r1iukm7tC6iUlPGfdFpY=
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=gfLILJM+TgCZkLS4WJkNgQa9ZvQ=; b=ibpgL7r99SAF/S3QzMuX5bU6jPso
	mtr2dPTX24KUPpwNDt//inFAWHmFDXkre50s7VUxjnP8y7/SoQ/SWcDmaltLO9M2
	4a2XjjNus514l1pPnX1QueG965KpotnisYNnlpXUBQW/qtTplga0qONOktig+mq9
	rWYu9Kft5n8N4iA=
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,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 spammy=*should*, Hx-languages-length:1880
X-HELO: mout.kundenserver.de
Date: Thu, 14 Feb 2019 14:13:45 +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: <20190214131345.GB30859@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20190213122509 DOT GL3718 AT calimero DOT vinschen DOT de> <CANV9t=TW6Kwxo9pN=3Hp8Yzi5A4i2qQpiLoGyEqxR5rq7vu5pA AT mail DOT gmail DOT com> <20190213161029 DOT GY3718 AT calimero DOT vinschen DOT de> <CANV9t=RiBTNsGUwEf6BS9A6b=fMcHeiGD_RDOueKHJ5c9Zwe_g AT mail DOT gmail DOT com> <20190213162614 DOT GA3718 AT calimero DOT vinschen DOT de> <CANV9t=RmEik5VN-Zebc5h+9JUqYZL0QO5RP0UH5F--=zX8NkYg AT mail DOT gmail DOT com> <20190213175541 DOT GE3718 AT calimero DOT vinschen DOT de> <CANV9t=S6zO_qXBrUALxTCKPCPkXfgc-6FFchV_prbkMyD7GpRA AT mail DOT gmail DOT com> <20190213202537 DOT GF3718 AT calimero DOT vinschen DOT de> <CANV9t=Q49YOZ26AEKu0nx4UW2hGvaXt+0wf3nKtRq3_AguYz6A AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="kXdP64Ggrk/fb43R"
Content-Disposition: inline
In-Reply-To: <CANV9t=Q49YOZ26AEKu0nx4UW2hGvaXt+0wf3nKtRq3_AguYz6A@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)

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

On Feb 13 13:55, Bill Stewart wrote:
> On Wed, Feb 13, 2019 at 1:25 PM Corinna Vinschen
> <corinna-cygwin AT cygwin DOT com> wrote:
> > > (a) Domain or computer name portion to the left of the "+" must always
> > > be uppercase
> >
> > No, the case must match the case of the domain or computername.
> >
> > > (b) Username after "+" sign (or username alone, without "+" sign) must
> > > match case exactly
> > >
> > > Questions:
> > >
> > > 1. Are the above two statements (a) and (b) complete/correct?
> > >
> > > 2. With regards to (a), are there any cases where the domain or
> > > computer name is not uppercase?
> >
> > Yes.  In my domain I have four machines using all-lowercase machine
> > name for no apparent reason.  One is a Linux machine, one is a
> > Windows 7 64 bit, the other two are Windows 8.1 32 and 64 bit machines.
> > All others, including the Windows 8 machines, are all uppercase.
>=20
> The computer or domain name case inconsistency would seem to be a
> source of confusion, mainly because on the Windows side we are
> case-retentive but not case-sensitive, and it is not immediately
> obvious which case will apply in the case of a computer or domain
> name.
>=20
> According to: http://pubs.opengroup.org/onlinepubs/9699919799/ -
> [...]
> >From this reference, it seems that a POSIX-compliant username cannot
> contain the + character?

*should*, not *must*.  It may be a portabiliy problem but it's not
strictly disallowed.  I'm also not sure what this has to do with the
matter at hand.

> So my suggestion is for Cygwin to convert the name part before the +
> automatically to upper (or lower) case.

The problem may be compatibility with existing scripts and OpenSSH
Match rules.

> Thoughts?

I'm in the process of discussing with the OpenSSH maintainers how to
proceed.


Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

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

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

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlxlaYkACgkQ9TYGna5E
T6Ce0g//amINvv5cD3YXb9saXolGex3wgOzf7ha5wvrbG5KdQeUKkjj75PslPgAV
7tHFc5Y2laIc5o1arxB6Z9cGak6ac1rLZ7RSoObUip0+iDV8PEf68UNSgTz/lKAi
D60GvTWzZ+Eg8oDTWcsZXqSaX4FlnXOMyQ/dV2OiABTmsprJB28FIchGUhQbDtOy
Nw+PFip1Eqq4zWLutW6gefsi0cxfQ9VPOPcV+sfGJsWsBvUAOXNqPxZjxuUXDp+U
zsZvhjWq16hN/51OU+aHAc3ghDljszBCGJGlyYUYYjRIjIglaHOscuZt5NYQPtUb
0spkNTLV8qurHDxXwIXRSd4NPWR0rpdFsr1eS/Lk1HFyePbF0RfLUltSgLMKCqWm
rGCXfr9A3GLzr9OxHwIhrMPOiuUi/Mvcj7AzRVzVPIUOKbYvkdGKiK9HgletTbkC
gmqXvU1tM7WPyp8sVs4bcKDkhA2kMAWCCpYv4KD9ReRcecoka6n/Lgt/yG87Xs/f
ecHAD6faUHRECNc1gVUAGVKM2heLaNyY8JbXFAuCXdcsS+xuUpBonnd6wpL4BKOm
roeOt8fdjeg00gJbdF60uclPccek+NojAFvR8aGDiT+VWOe6JRiHR6UXw7RM9y1b
OIh8fdhj3ckIll8OCcJBQSRnvh/1UgPomBPh7bnOaPtQ2jz53iQ=
=Ypnm
-----END PGP SIGNATURE-----

--kXdP64Ggrk/fb43R--