From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: sshd problem on WS2008R2 64bit
Date: Wed, 06 Mar 2019 15:34:00 -0000 [thread overview]
Message-ID: <20190306153404.GX3785@calimero.vinschen.de> (raw)
In-Reply-To: <CANV9t=SHLCT_xN_T35qTgJmoEBu98gGPaKjHMt559MZ+AwyToQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
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...
Corinna
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-06 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-06 1:03 Stephen Carrier
2019-03-06 12:12 ` Corinna Vinschen
2019-03-06 12:48 ` Corinna Vinschen
2019-03-06 14:17 ` Corinna Vinschen
2019-03-06 14:34 ` Corinna Vinschen
2019-03-06 15:30 ` Bill Stewart
2019-03-06 15:34 ` Corinna Vinschen [this message]
2019-03-06 15:59 ` Bill Stewart
2019-03-06 16:45 ` Bill Stewart
2019-03-06 20:13 ` Corinna Vinschen
2019-03-06 20:48 ` Bill Stewart
2019-03-06 20:59 ` Corinna Vinschen
2019-03-06 21:25 ` Bill Stewart
2019-03-06 23:44 ` Stephen Paul Carrier
2019-03-06 23:54 ` Stephen Paul Carrier
2019-03-07 6:15 ` Brian Inglis
2019-03-07 8:54 ` Corinna Vinschen
2019-03-07 14:04 ` Brian Inglis
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=20190306153404.GX3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).