From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Windows Server 2012R2 64bit and 32bit Cygwin sshd
Date: Tue, 19 Aug 2014 17:02:00 -0000 [thread overview]
Message-ID: <20140819170235.GB29878@calimero.vinschen.de> (raw)
In-Reply-To: <loom.20140819T152804-628@post.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1683 bytes --]
On Aug 19 13:37, Achim Gratz wrote:
> I've run strace on both the 32bit and the 64bit sshd and here's the
> difference between the two, right after sshd gets an exception 5 from the DC:
>
> 32bit
> --- Process 5820, exception 00000005 at 75BF1D4D
> 43239 4372793 [waitproc] sshd 2400 pinfo::maybe_set_exit_code_from_windows:
> pid 5820, exit value - old 0x0, windows 0x5, cygwin 0x8000500
>
> 64bit
> --- Process 484, exception 00000005 at 00007FFA4F5D5BF8
> 9907 4522411 [main] sshd 484 seterrno_from_win_error:
> .../cygwin-snapshot-20140819-1/winsup/cygwin/sec_auth.cc:263
> windows error 5
This is a call to the Win32 API call NetUserGetGroups creating an
exception due to an "access denied". The difference between 32 and 64
bit is probably a result of the differences in exception handling, and
given that an ExceptionCode 5 will be ignored by Cygwin's exception
handler, it's probably the next handler in the chain.
Are you running sshd under a local cyg_server account or under a domain
cyg_server account? Is it possible that this is a local cyg_server
account, and as a non-domain account actually gets an "access denied"
when trying to request AD user information?
If your cyg_server is a local account I'd suggest to try with an
AD account per https://cygwin.com/faq/faq.html#faq.using.sshd-in-domain
Other than that I have a funny idea how to workaround this problem from
inside Cygwin. If you want to give it a try, I'll send you a pointer
to a 32 bit DLL via PM.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-19 17:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 17:26 Achim Gratz
2014-08-19 13:37 ` Achim Gratz
2014-08-19 17:02 ` Corinna Vinschen [this message]
2014-08-19 17:21 ` Achim Gratz
2014-08-19 19:09 ` Corinna Vinschen
2014-08-19 19:21 ` Achim Gratz
2014-09-02 11:52 ` Achim Gratz
2014-09-02 14:07 ` Corinna Vinschen
2014-09-02 15:16 ` Achim Gratz
2014-09-02 15:38 ` Corinna Vinschen
2014-09-02 17:32 ` Achim Gratz
2014-09-03 7:17 ` Achim Gratz
2014-09-03 13:03 ` Achim Gratz
2014-09-03 13:37 ` Corinna Vinschen
2014-09-04 11:24 ` Achim Gratz
2014-09-04 12:28 ` Corinna Vinschen
2014-09-04 14:12 ` Achim Gratz
2014-09-04 14:59 ` Achim Gratz
2014-09-05 11:16 ` Corinna Vinschen
2014-09-05 11:56 ` Corinna Vinschen
2014-09-05 18:17 ` Achim Gratz
2014-09-03 13:26 ` Corinna Vinschen
2014-09-02 16:25 ` Achim Gratz
2014-09-02 19:14 ` Corinna Vinschen
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=20140819170235.GB29878@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).