From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd: computer name's case must match?
Date: Wed, 13 Feb 2019 17:55:00 -0000 [thread overview]
Message-ID: <20190213175541.GE3718@calimero.vinschen.de> (raw)
In-Reply-To: <CANV9t=RmEik5VN-Zebc5h+9JUqYZL0QO5RP0UH5F--=zX8NkYg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
On Feb 13 10:43, Bill Stewart wrote:
> On Wed, Feb 13, 2019 at 9:26 AM Corinna Vinschen
> <corinna-cygwin@cygwin.com> wrote:
> > No, that was a bug. With case insenitive usernames, the pattern
> > matching in OpenSSH won't work and you create a potential security
> > problem.
>
> I see - interoperability issue.
>
> Therefore it becomes imperative on the Windows side to match username
> case exactly and we need to explain this.
>
> However I would say that the case of the domain or computername
> shouldn't matter?
>
> I just tested with cygwin1.dll (13 Feb 2019) and this worked:
>
> ssh COMPUTERNAME+username@computername
>
> however this didn't work:
>
> ssh computername+username@computername
>
> Am I not understanding something?
The complete string "domain+samaccountname" is the Cygwin username,
see the output of `getent passwd <user>' The entire Cygwin username
should always use the same case, otherwise case sensitive pattern
matching on the name returned in the passwd name field won't work.
Play with `getent passwd' with the latest and the previous Cygwin
DLL. That should give you an idea.
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-13 17:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 23:07 Bill Stewart
2019-02-13 1:35 ` Andrey Repin
2019-02-13 10:32 ` Corinna Vinschen
2019-02-13 12:25 ` Corinna Vinschen
2019-02-13 15:53 ` Bill Stewart
2019-02-13 16:10 ` Corinna Vinschen
2019-02-13 16:24 ` Bill Stewart
2019-02-13 16:26 ` Corinna Vinschen
2019-02-13 17:43 ` Bill Stewart
2019-02-13 17:55 ` Corinna Vinschen [this message]
2019-02-13 18:13 ` Bill Stewart
2019-02-13 20:25 ` Corinna Vinschen
2019-02-13 20:55 ` Bill Stewart
2019-02-13 22:50 ` Andrey Repin
2019-02-14 13:14 ` Corinna Vinschen
2019-02-14 15:23 ` Bill Stewart
2019-02-14 16:20 ` Bill Stewart
2019-02-21 20:17 ` Bill Stewart
2019-02-22 9:39 ` Corinna Vinschen
2019-02-22 15:43 ` Bill Stewart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190213175541.GE3718@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).