From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: sshd/SYSTEM account/OS version and Cygwin "bitness" limitations
Date: Thu, 28 Mar 2019 23:18:00 -0000 [thread overview]
Message-ID: <31d69fd2-4906-4e32-29ca-d5bedb31088d@SystematicSw.ab.ca> (raw)
In-Reply-To: <CANV9t=SKR5bnKmKeQHsjK5y956h1gT6sUQ6TiQeXxto1+h63iw@mail.gmail.com>
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.
cygstart /usr/share/doc/Cygwin/html/ntsec.html
--
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada
This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
--
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
next prev parent reply other threads:[~2019-03-28 23:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 21:37 Bill Stewart
2019-03-28 23:18 ` Brian Inglis [this message]
2019-03-29 9:59 ` Corinna Vinschen
2019-03-29 14:41 ` Bill Stewart
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=31d69fd2-4906-4e32-29ca-d5bedb31088d@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).