From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19188 invoked by alias); 6 Mar 2019 16:45:46 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 18836 invoked by uid 89); 6 Mar 2019 16:45:45 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=BAYES_00,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 spammy=Actions, H*c:alternative, password X-HELO: mout.gmx.com Received: from mout.gmx.com (HELO mout.gmx.com) (74.208.4.201) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 06 Mar 2019 16:45:43 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mail.com; s=dbd5af2cbaf7; t=1551890741; bh=onY1WARvM7DA64DUeyjmvt8PhFdSnaLyFeOzvaNckRo=; h=X-UI-Sender-Class:References:In-Reply-To:From:Date:Subject:To; b=lPE4dUpunZkbDSgjNeZ/icVHmgVFx/VA/8KxenyzfjZ87i2PpHpx9FPtvn5VwIdEF w2VignoCb6/v2P63lHw9TsA1AqJUuRHDAHe2fM+m7RozEAQDC+/ZAihTnysOj9erFe UhqyQTUeZIX12ItWKsILGXeVK+zJeuYddPZ4me8s= X-UI-Sender-Class: 214d933f-fd2f-45c7-a636-f5d79ae31a79 Received: from mail-lj1-f175.google.com ([209.85.208.175]) by mail.gmx.com (mrgmxus001 [74.208.5.15]) with ESMTPSA (Nemesis) id 0LeMmZ-1hJnuy0rG9-00qDw1 for ; Wed, 06 Mar 2019 17:45:41 +0100 Received: by mail-lj1-f175.google.com with SMTP id z20so11498263ljj.10 for ; Wed, 06 Mar 2019 08:45:40 -0800 (PST) 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> <20190306153404.GX3785@calimero.vinschen.de> In-Reply-To: <20190306153404.GX3785@calimero.vinschen.de> From: Bill Stewart Date: Wed, 06 Mar 2019 16:45:00 -0000 Message-ID: Subject: Re: sshd problem on WS2008R2 64bit To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00113.txt.bz2 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