From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: sshd: computer name's case must match?
Date: Wed, 13 Feb 2019 16:24:00 -0000 [thread overview]
Message-ID: <CANV9t=RiBTNsGUwEf6BS9A6b=fMcHeiGD_RDOueKHJ5c9Zwe_g@mail.gmail.com> (raw)
In-Reply-To: <20190213161029.GY3718@calimero.vinschen.de>
On Wed, Feb 13, 2019 at 9:10 AM Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
> This can't work correctly with OpenSSH. The decision to allow only
> the correct case in OpenSSH was made back in 2010, because otherwise
> we would need a lot of special rules in OpenSSH just for Cygwin.
> Sorry, but that's how it is.
Thanks for the explanation -- this is understandable.
In that case, the former arrangement before the patch was preferable.
That is: For DOMAIN+username or COMPUTERNAME+username, the part before
the "+" must be UPPERCASE, but the username is not case-sensitive.
IMO This is the simplest and most straightforward arrangement.
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
next prev parent reply other threads:[~2019-02-13 16:24 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 [this message]
2019-02-13 16:26 ` Corinna Vinschen
2019-02-13 17:43 ` Bill Stewart
2019-02-13 17:55 ` Corinna Vinschen
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='CANV9t=RiBTNsGUwEf6BS9A6b=fMcHeiGD_RDOueKHJ5c9Zwe_g@mail.gmail.com' \
--to=bstewart@iname.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).