From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Windows Server 2012R2 64bit and 32bit Cygwin sshd
Date: Tue, 19 Aug 2014 17:21:00 -0000 [thread overview]
Message-ID: <87bnrgpf8e.fsf@Rainer.invalid> (raw)
In-Reply-To: <20140819170235.GB29878@calimero.vinschen.de> (Corinna Vinschen's message of "Tue, 19 Aug 2014 19:02:35 +0200")
Corinna Vinschen writes:
> 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.
Well, as I said, Cygwin64 dutifully ignores the exception and then goes
to fetch my password from the registry and forks off the command given
to ssh.
> 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?
It's a local account, actually I've got a separate account cyg_server32
for that. I've double checked that this is set up the same way as the
original cyg_server account except for the home directory.
> 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
I can try but the AD admins are still sitting on their thumbs for the
sshd domain account, so I don't have high hopes for fast enough
turnaround. Plus, they have new rules that forbid administrative
accounts that have unlimited activation, so I don't know how much use
this is.
> 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.
Yes please. As long as I don't get sshd to work, I can't use this
installation for its intended purpose anyway.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds
--
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:[~2014-08-19 17:21 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
2014-08-19 17:21 ` Achim Gratz [this message]
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=87bnrgpf8e.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).