From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: sshd/SYSTEM account/OS version and Cygwin "bitness" limitations
Date: Fri, 29 Mar 2019 14:41:00 -0000 [thread overview]
Message-ID: <CANV9t=SQwC15S2LdQs=u_HHqH3FUZ3emwrjppF8WbWb=89p=Yw@mail.gmail.com> (raw)
In-Reply-To: <20190329095937.GD4096@calimero.vinschen.de>
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
prev parent reply other threads:[~2019-03-29 14:41 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
2019-03-29 9:59 ` Corinna Vinschen
2019-03-29 14:41 ` Bill Stewart [this message]
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='CANV9t=SQwC15S2LdQs=u_HHqH3FUZ3emwrjppF8WbWb=89p=Yw@mail.gmail.com' \
--to=bstewart@iname.com \
--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).