DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=yCm9SsG
	UtobvnzbOOvjQyOG+sYYmLhclq+gmNNgHeSvYFlRSJO1xGQh/8FpWddWIRMEBVX6
	CKDY5vfuj2KxJDRrWU+6WejCW6xovhsbnrTaie1t+HOJ34LchWAvUILwLpzrIUgZ
	XrNaXIrPVcO2AkG36kTHUacM0ld2V5FSd1us=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
References: <20190213122509.GL3718@calimero.vinschen.de> <CANV9t=TW6Kwxo9pN=3Hp8Yzi5A4i2qQpiLoGyEqxR5rq7vu5pA@mail.gmail.com> <20190213161029.GY3718@calimero.vinschen.de> <CANV9t=RiBTNsGUwEf6BS9A6b=fMcHeiGD_RDOueKHJ5c9Zwe_g@mail.gmail.com> <20190213162614.GA3718@calimero.vinschen.de> <CANV9t=RmEik5VN-Zebc5h+9JUqYZL0QO5RP0UH5F--=zX8NkYg@mail.gmail.com> <20190213175541.GE3718@calimero.vinschen.de> <CANV9t=S6zO_qXBrUALxTCKPCPkXfgc-6FFchV_prbkMyD7GpRA@mail.gmail.com> <20190213202537.GF3718@calimero.vinschen.de> <CANV9t=Q49YOZ26AEKu0nx4UW2hGvaXt+0wf3nKtRq3_AguYz6A@mail.gmail.com> <20190214131345.GB30859@calimero.vinschen.de>
In-Reply-To: <20190214131345.GB30859@calimero.vinschen.de>
From: Bill Stewart <bstewart@iname.com>
Date: Thu, 14 Feb 2019 06:43:23 -0700
Message-ID: <CANV9t=QE9n6kej+1CYYV7OMktLpv05ZhYpSdPe=LzpbnwiH9Hw@mail.gmail.com>
Subject: Re: sshd: computer name's case must match?
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

On Thu, Feb 14, 2019 at 6:14 AM Corinna Vinschen wrote:
> > 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.

I was looking for a simple way to resolve the case issue.

> > 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.

This makes sense. My suggestion may be a bit too simplistic.

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

Sounds good. Thank you for thinking about this problem.

I understand the username case needing to match. This is easily
instructed on the Windows side - just make sure the case matches and
it will work.

I think this is the difficulty: When a computer name is not uppercase,
how do we find out the correct case when we specify an authority name
(before the +)?

(A domain name is easier: We can translate name -> SID -> name and get
the correct case.)

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple