From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 61265 invoked by alias); 6 Mar 2019 15:30:40 -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 51945 invoked by uid 89); 6 Mar 2019 15:30:25 -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=precisely, H*c:alternative X-HELO: mout.gmx.com Received: from mout.gmx.com (HELO mout.gmx.com) (74.208.4.200) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 06 Mar 2019 15:30:22 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mail.com; s=dbd5af2cbaf7; t=1551886216; bh=KeDrVhkEVsBRNi2Zla4JFqTvp0Ntu7Nb1u59WEKVZVM=; h=X-UI-Sender-Class:References:In-Reply-To:From:Date:Subject:To; b=Ta9k0etpuyzwo7jWhhrMQAxD4fQaQ1ka8pGZGoC/nUbh/g5XW+F8/wHkb6N2UKnlO cP3jTPicizzNp4DjnVLr/n7f0gaWO4TdP2FsljwKJdeEJ1tnUYg5f3YAqAon72arSl nIt0xREdUv2WZY0b9BjpyoRHN+yhxpkibz8L7Vv0= X-UI-Sender-Class: 214d933f-fd2f-45c7-a636-f5d79ae31a79 Received: from mail-lj1-f177.google.com ([209.85.208.177]) by mail.gmx.com (mrgmxus002 [74.208.5.15]) with ESMTPSA (Nemesis) id 0M9JcW-1gosFy1DbC-00Cexb for ; Wed, 06 Mar 2019 16:30:16 +0100 Received: by mail-lj1-f177.google.com with SMTP id w6so11250041ljd.7 for ; Wed, 06 Mar 2019 07:30:15 -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> In-Reply-To: <20190306143424.GU3785@calimero.vinschen.de> From: Bill Stewart Date: Wed, 06 Mar 2019 15:30: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/msg00107.txt.bz2 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? 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