public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Houder <houder@xs4all.nl>
To: cygwin@cygwin.com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
Date: Wed, 20 Feb 2019 21:50:00 -0000	[thread overview]
Message-ID: <cf5bae0d3d06c3bb508cc766c5c18226@smtp-cloud8.xs4all.net> (raw)
In-Reply-To: <vz1pnrmnoat.fsf@gmail.com>

On Wed, 20 Feb 2019 21:27:22, Andy Moreton  wrote:

> I've seen a similar failure, on a domain-joined Windows 10 box running
> cygsshd using a local cyg_server user account. I've fixed it by:
> 1) Open the "Computer Management" app
>    Select "Services and Applications", then "Services", and
>    choose the cygsshd service from the list.
> 2) Stop the service
> 3) Select the "Log On" tab, choose "Local System Account" and click OK.
> 4) Restart the service.
> 
> This changed the account reported by "cygrunsrv -VQ" from "./cyg_server"
> to "LocalSystem".

64-@@ uname -a
CYGWIN_NT-6.1 Seven 3.0.1(0.338/5/3) 2019-02-20 10:19 x86_64 Cygwin

First I replaced cygwin1.dll again w/ the last version, as you can see ...

Then I carried out you instruction ...

To my surprise it did the trick! Thank you!

Perhaps Corinna can give a hint of why the modification made the difference.

Henri


--
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

  parent reply	other threads:[~2019-02-20 21:50 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 [this message]
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=cf5bae0d3d06c3bb508cc766c5c18226@smtp-cloud8.xs4all.net \
    --to=houder@xs4all.nl \
    --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).