From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32242 invoked by alias); 29 Mar 2019 14:41:15 -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 32232 invoked by uid 89); 29 Mar 2019 14:41:14 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,GIT_PATCH_2,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.1 spammy=row, H*c:alternative 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; Fri, 29 Mar 2019 14:41:12 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mail.com; s=dbd5af2cbaf7; t=1553870470; bh=p1zKXm7Pr5O8Jom4UomXXrW9O9t7AtANSL4BjPp7H+s=; h=X-UI-Sender-Class:References:In-Reply-To:From:Date:Subject:To; b=CdOt8IvXA/ZxYwtV2v9nEXcxhrUZaMgI/u1Xs9t8KtPOy9DuXspWX6YOwnNrhG9VK d39+YP4j5BJwoqTgOSzEkA3TtsKwyXFsUdiM477VxVuX8OlqRy2iOYa4O0vHggJm/U tDpFiBGWEn+eMmDp+gTRlztmKz2P3F0bnWG81I40= X-UI-Sender-Class: 214d933f-fd2f-45c7-a636-f5d79ae31a79 Received: from mail-lj1-f177.google.com ([209.85.208.177]) by mail.gmx.com (mrgmxus001 [74.208.5.15]) with ESMTPSA (Nemesis) id 0LtaPy-1h09JK05v2-010wwd for ; Fri, 29 Mar 2019 15:41:10 +0100 Received: by mail-lj1-f177.google.com with SMTP id r24so2195915ljg.3 for ; Fri, 29 Mar 2019 07:41:09 -0700 (PDT) MIME-Version: 1.0 References: <31d69fd2-4906-4e32-29ca-d5bedb31088d@SystematicSw.ab.ca> <20190329095937.GD4096@calimero.vinschen.de> In-Reply-To: <20190329095937.GD4096@calimero.vinschen.de> From: Bill Stewart Date: Fri, 29 Mar 2019 14:41:00 -0000 Message-ID: Subject: Re: sshd/SYSTEM account/OS version and Cygwin "bitness" limitations To: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-IsSubscribed: yes X-SW-Source: 2019-03/txt/msg00653.txt.bz2 On Fri, Mar 29, 2019 at 4:00 AM Corinna Vinschen wrote: > > On 2019-03-28 15:36, Bill Stewart wrote: > > I am trying to understand the limitations when running sshd using the > > SYSTEM account. > > > > Is the following complete and correct? > > > > ========== > > > > OS_version* OS_bitness sshd_bitness Notes > > -------------------------------------------------- > > < 6.3 64-bit 32-bit Note 1 > > < 6.3 64-bit 64-bit Note 2 > > < 6.3 32-bit 32-bit Note 2 > > > = 6.3 64-bit 64-bit No problems > > > = 6.3 64-bit 32-bit No problems > > > = 6.3 32-bit 32-bit No problems > > > > * "< 6.3" = "older than Windows 8.1/Server 2012 R2"; ">= 6.3" = "at least > > Windows 8.1/Server 2012 R2" > > > > Note 1: sshd cannot authenticate local accounts, but it can authenticate > > domain accounts. > > > > Note 2: sshd can't authenticate local accounts after a reboot unless > > another logon happens first. > > > > Unfortunate implication of Note 1: 32-bit version of sshd running as SYSTEM > > account on OS < 6.3 on non-domain member computer cannot authenticate any > > accounts. > > Or https://cygwin.com/cygwin-ug-net/ntsec.html > > AFAIK, the only problem left are OS versions 6.0 (Vista/2008) > and 6.1 (7/2008R2), and only 32 bit Cygwin running under WOW64, > *not* 32 bit Cygwin running on a 32 bit Windows. I read the documentation again (ntsec.html), and I don't see detailed Windows version specifics. (Hence this message...) Regarding 6.0 (Vista/Server 2008) and 6.1 (7/Server 2008 R2) 64-bit OS running 32-bit sshd: That's covered in the first row of the table (OS_version < 6.3). Regarding 6.0 (Vista/Server 2008) and 6.1 (Windows 7) 32-bit OS running 32-bit sshd: Only affected by Note 2 (third row of table). It would seem that my breakdown is complete and correct, then. (If anyone sees an error, please reply.) Thanks! 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