From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd: computer name's case must match?
Date: Thu, 14 Feb 2019 13:14:00 -0000 [thread overview]
Message-ID: <20190214131345.GB30859@calimero.vinschen.de> (raw)
In-Reply-To: <CANV9t=Q49YOZ26AEKu0nx4UW2hGvaXt+0wf3nKtRq3_AguYz6A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1899 bytes --]
On Feb 13 13:55, Bill Stewart wrote:
> On Wed, Feb 13, 2019 at 1:25 PM Corinna Vinschen
> <corinna-cygwin@cygwin.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.
>
> 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.
>
> 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
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-02-14 13:13 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
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 [this message]
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=20190214131345.GB30859@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).