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:from:date:message-id:subject:to
	:content-type; q=dns; s=default; b=vpWMtJuXYr5oQXtvJeTcxZ5yDf6Zw
	RhT2wB5uJSZRV4i8cLXHOZsohtQ0r/X0lAci7Qza4dl19ryZDp1xDmNhfdyvrTLr
	Pcdj6s9vScl66MDPz0cvmh74TmK3azEwMOOBOeyJ81ZXj2SWPNiDNjpMnejQRp6k
	L/Zwsgm7tLrTI0=
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
MIME-Version: 1.0
From: Bill Stewart <bstewart AT iname DOT com>
Date: Tue, 12 Feb 2019 16:07:21 -0700
Message-ID: <CANV9t=QxA_FW-3OCZuYFJpxrekbO8Yc-WsnxGLiyc0Bqz=fPUw@mail.gmail.com>
Subject: sshd: computer name's case must match?
To: cygwin AT cygwin DOT com
Content-Type: text/plain; charset="UTF-8"

Good day,

I am testing sshd using the cygwin1.dll 3.x version (run as SYSTEM -
S4U logon - works great!).

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.

This doesn't seem to be the case if I change the username's case -
'COMPUTER+localname' also works.

Is this by design or by accident?

Thanks,

Bill

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