From: scowles@ckhb.org
To: Bill Stewart <bstewart@iname.com>
Cc: cygwin@cygwin.com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
Date: Wed, 20 Feb 2019 20:01:00 -0000 [thread overview]
Message-ID: <alpine.DEB.2.21.1902201142530.32163@ckhb05> (raw)
In-Reply-To: <CANV9t=SH3EsTjm0B0uMreWZCpKnOn8XHskNq53x34eVWKNY_cg@mail.gmail.com>
user names are not the problem.
and my reply was incomplete; my observations are for windows 10 pro, 1809,
installations.
i have now seen the thread "Problem with sshd on W7 with 32bit cygwin 3.0" and
am looking at that for leads.
--
s. cowles
scowles@ckhb.org
+1 510 380 8661
Key fingerprint = A156 277B 875A D6E3 A00C 23D9 869E 72BE 1FD3 5B80
On Wed, 20 Feb 2019, Bill Stewart wrote:
> Date: Wed, 20 Feb 2019 11:04:29
> From: Bill Stewart <bstewart@iname.com>
> To: cygwin@cygwin.com
> Subject: Re: cygwin 3.0.1-1 breaks my sshd install
>
> In Cygwin 3.x, the case of the username must match exactly.
> I wonder if that's the problem?
> 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-20 19:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19759126.568100.1550686604174.ref@mail.yahoo.com>
2019-02-20 18:53 ` James R. Phillips via cygwin
2019-02-20 19:04 ` scowles
2019-02-20 19:47 ` Bill Stewart
2019-02-20 20:01 ` scowles [this message]
2019-02-20 20:25 ` Houder
2019-02-20 21:27 ` Corinna Vinschen
2019-02-20 21:34 ` Andy Moreton
2019-02-20 21:39 ` Corinna Vinschen
2019-02-20 22:13 ` scowles
2019-02-20 21:50 ` Houder
2019-02-20 22:38 ` Corinna Vinschen
2019-02-20 22:44 ` Corinna Vinschen
2019-02-21 11:43 ` Corinna Vinschen
2019-02-21 16:01 ` Houder
2019-02-23 19:15 ` Cary Lewis
2019-02-24 6:58 ` Cary Lewis
2019-09-15 6:45 ` Basin Ilya
2019-09-15 7:07 ` Basin Ilya
2019-02-20 21:35 ` Bill Stewart
2019-02-20 21:37 ` Houder
2019-02-20 21:50 ` Corinna Vinschen
2019-02-20 22:08 ` Houder
2019-02-20 22:32 ` Houder
2019-02-20 22:43 ` Corinna Vinschen
2019-02-21 5:16 ` Houder
2019-02-20 22:36 ` scowles
2019-02-20 23:08 ` Corinna Vinschen
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=alpine.DEB.2.21.1902201142530.32163@ckhb05 \
--to=scowles@ckhb.org \
--cc=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).