public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: sshd: computer name's case must match?
Date: Thu, 14 Feb 2019 15:23:00 -0000	[thread overview]
Message-ID: <CANV9t=QE9n6kej+1CYYV7OMktLpv05ZhYpSdPe=LzpbnwiH9Hw@mail.gmail.com> (raw)
In-Reply-To: <20190214131345.GB30859@calimero.vinschen.de>

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

  reply	other threads:[~2019-02-14 13:43 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
2019-02-14 15:23                         ` Bill Stewart [this message]
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=QE9n6kej+1CYYV7OMktLpv05ZhYpSdPe=LzpbnwiH9Hw@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).