DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:references:in-reply-to:from:date
	:message-id:subject:to:content-type; q=dns; s=default; b=fJeP5Ev
	QmUZNKomiBRWcLmoBP6aLKpI5ZE8d+dFgrLaNqpv/XWFF15xPlCtlyijy7XKd3Er
	JuHIF1Y2e2WM2jmDfMreJyPdUPvxFxawOi5oKWWlM7qu1KGJE/QwDh+8HuTG7023
	FSsTtFG8lajjG4sba742XILuyFvaFSoTglXg=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
References: <20190306010254.GA4210@zebra> <20190306121154.GN3785@calimero.vinschen.de> <20190306124816.GR3785@calimero.vinschen.de> <20190306141716.GS3785@calimero.vinschen.de> <20190306143424.GU3785@calimero.vinschen.de> <CANV9t=SHLCT_xN_T35qTgJmoEBu98gGPaKjHMt559MZ+AwyToQ@mail.gmail.com> <20190306153404.GX3785@calimero.vinschen.de>
In-Reply-To: <20190306153404.GX3785@calimero.vinschen.de>
From: Bill Stewart <bstewart@iname.com>
Date: Wed, 6 Mar 2019 09:45:12 -0700
Message-ID: <CANV9t=QiOH4cB47XzKZsReH7RLdaB0CxgY-o3jYgZ46DbV3OdA@mail.gmail.com>
Subject: Re: sshd problem on WS2008R2 64bit
To: cygwin@cygwin.com
Content-Type: text/plain; charset="UTF-8"

On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:

> On Mar  6 08:38, Bill Stewart wrote:
> > On Wed, Mar 6, 2019 at 7:34 AM Corinna Vinschen  wrote:
> > > On Mar  6 15:17, Corinna Vinschen wrote:
> > > > But the old Systems like Windows 7 don't want to play nice.
> > > >
> > > > - On Vista and Windows 7 WOW64, MsV1_0S4ULogon isn't implemented
> > > >   at all, which required to keep the create_token method
> > > >   available
> > > >
> > > > - On Vista and Windows 7 MsV1_0S4ULogon does not work without
> > > >   some user logged in locally, even if it's just the cyg_server
> > > >   service account.
> > >
> > > FTR, Windows 8 / Server 2012 is affected as well,
> > >      Windows 8.1 / Server 2012 R2 is not.
> > > >
> > > > Question is, what is a good solution?  Reverting cyglsa as
> > > > well to allow the old methods to work as before?  This is
> > > > the opposite of what I had hoped to accomplish :(
> >
> > I agree that the new S4U logon method is by far the best solution.
> >
> > It seems to me that this MSV1 S4ULogon behavior on versions older than
NT
> > 6.3 (Vista/Srv2008/Win7/Srv2008R2/Win8/Srv2012) is not expected.
> >
> > What precisely happens when Cygwin uses MSV1 S4ULogon on versions older
> > than 6.3 before a user has logged on?
>
> MsV1S4ULogon returns with STATUS_NOT_SUPPORTED.  Funny status code,
> given it works if some user already logged in by other means...

OK, so here's another potential workaround that doesn't require running the
service as a specific user...

Create a scheduled task to run using the following settings:

General -> Run using user account - > choose a local account
General -> "Run whether user is logged on or not"
Triggers -> Run at system startup
Actions -> Start a program -> Program/script: %SystemRoot%\Cystem32\cmd.exe
Actions -> Start a program -> Add arguments: /c exit

Full password logon is required (seems we can't use "do not store password"
option).

The local account does not have to be a member of Administrators, but it
does require user right "Log on as a batch job" (SeBatchLogonRight).

In my prefunctory testing this seems to fix this problem.

Does this work?

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