From: Bill Stewart <bstewart@iname.com>
To: cygwin@cygwin.com
Subject: Re: sshd problem on WS2008R2 64bit
Date: Wed, 06 Mar 2019 15:59:00 -0000 [thread overview]
Message-ID: <CANV9t=Th1O3G3bPOrs89fzZGs-1Av=fHc1MdZ6wDrHP1=Lw6HA@mail.gmail.com> (raw)
In-Reply-To: <20190306153404.GX3785@calimero.vinschen.de>
On Wed, Mar 6, 2019 at 8:34 AM Corinna Vinschen wrote:
> > 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...
Agreed. It seems to me that this behavior is not expected (bug/defect).
Can someone provide a short sample test program that illustrates this
specific problem?
It is possible that I have the ability to address this with Microsoft
through a support resource.
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
next prev parent reply other threads:[~2019-03-06 15:59 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
2019-03-06 15:59 ` Bill Stewart [this message]
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='CANV9t=Th1O3G3bPOrs89fzZGs-1Av=fHc1MdZ6wDrHP1=Lw6HA@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).