From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: scowles@ckhb.org
Cc: cygwin@cygwin.com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
Date: Wed, 20 Feb 2019 23:08:00 -0000 [thread overview]
Message-ID: <20190220224433.GD4256@calimero.vinschen.de> (raw)
In-Reply-To: <alpine.DEB.2.21.1902201421390.17909@ckhb05>
[-- Attachment #1: Type: text/plain, Size: 1179 bytes --]
On Feb 20 14:31, scowles@ckhb.org wrote:
>
> On Wed, 20 Feb 2019, Houder wrote:
> > On Wed, 20 Feb 2019 22:41:08, Corinna Vinschen wrote:
> >
> > > On Feb 20 22:35, Houder wrote:
> > [snip]
> >
> > > >
> > > > Perhaps I missed something in the last couple of month. Did I have
> > > > to change
> > > > something in the setup of openssh?
> > >
> > > I really don't know, this all works fine for me. Try switching the
> > > account starting sshd from cyg_server to LocalSystem and change
> > > ownership of all files /etc/ssh* to SYSTEM.
> >
> > I carried out Andy M.'s instruction and it worked (as I wrote). The
> > files you mention above are still owned by cyg_server (and readable
> > by group Adminstrators).
> >
> > Henri
>
>
> i, too, made the switch to Local System startup for the sshd daemon. i also
> changed ownership of the /etc/ssh* files to SYSTEM. now, ssh services,
> under 3.0.1-1, are working as expected.
I'm relieved to read that.
> many thanks to henri and andy. and thank you. corinna, for your kind
> marshalling of this group and cygwin.
Thanks!
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2019-02-20 22:44 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
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 [this message]
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=20190220224433.GD4256@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=scowles@ckhb.org \
/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).