public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Cary Lewis <cary.lewis@gmail.com>
To: cygwin@cygwin.com
Subject: Re: cygwin 3.0.1-1 breaks my sshd install
Date: Sun, 24 Feb 2019 06:58:00 -0000	[thread overview]
Message-ID: <CAEF1h+XzzKnzpeqh=pE5tsexUVHPNCXnNfAvK0PEu9OCFDvjdg@mail.gmail.com> (raw)
In-Reply-To: <DBA38EC0-BF79-4F49-B75E-C47C2894E3FE@gmail.com>

Changing the sshd service to run as localsystem rather than cyg_server
allows me to again ssh into the machine.

Thanks for everyone on this mailing list - I spent hours trying to figure
this out - and because the list doesn't seem to get indexed by google, the
web searches I was doing were of no help.

Looking forward to a newer version of openssh...

On Sat, Feb 23, 2019 at 1:20 PM Cary Lewis <cary.lewis@gmail.com> wrote:

> I’m seeing a similar issue. Will try using localsystem.
>
> > On Feb 21, 2019, at 6:43 AM, Houder <houder@xs4all.nl> wrote:
> >
> >> On Thu, 21 Feb 2019 11:09:11, Corinna Vinschen  wrote:
> >>
> >> I managed it today already but I'm somewhat stumped.
> >>
> >> I ran ssh-host-config and let the script install a new local account
> >> "test_server" to use for the sshd service.  I started the service and
> >> tried to login with a local account and it just worked out of the box.
> >
> > This is my case: using local accounts only.
> >
> > Reminder: sshd did work w/ 2.11.2 ...
> > (and it works now in 3.0.1 after replacing cyg_server w/ SYSTEM (*) )
> >
> > Way back I started using cyg_server because "csih" forced me to create
> > this privileged account (W7!).
> >
> > I studied "csih" (cygwin-service-installation-helper.sh) again ...
> >
> > 64-@@# editrights -u cyg_server -l
> > SeAssignPrimaryTokenPrivilege
> > SeCreateTokenPrivilege
> > SeServiceLogonRight
> > SeDenyInteractiveLogonRight
> > SeDenyRemoteInteractiveLogonRight
> >
> > Compared to "csih", the SeTcbPrivilege privilege was missing. I am not
> > in the habit of messing with privileges ...
> >
> > Consequently, like you, I am stumped too :-)
> >
> > (*) after "moving" the sshd service from cyg_server to SYSTEM, I also
> > changed the ownership of /var/empty and /etc/ssh* (to SYSTEM) ...
> >
> > Next, I disabled the cyg_server and sshd accounts. ssh still works.
> >
> > 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
> >
>

--
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-24  3:08 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 [this message]
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='CAEF1h+XzzKnzpeqh=pE5tsexUVHPNCXnNfAvK0PEu9OCFDvjdg@mail.gmail.com' \
    --to=cary.lewis@gmail.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).