From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: Windows Server 2012R2 64bit and 32bit Cygwin sshd
Date: Tue, 02 Sep 2014 17:32:00 -0000 [thread overview]
Message-ID: <87iol6q670.fsf@Rainer.invalid> (raw)
In-Reply-To: <20140902153757.GE6056@calimero.vinschen.de> (Corinna Vinschen's message of "Tue, 2 Sep 2014 17:37:57 +0200")
Corinna Vinschen writes:
> Don't use privilege separation, then the non-privileged sshd user won't
> matter at all. Privsep on Cygwin is only half-useful on Cygwin anyway,
> if at all. As for the local cyg_server account, I'm not sure. Usually,
> a local machine account has no or only limited access to AD information.
> As an account which needs AD to get user information it's a bit
> unfortunate if it doesn't have access.
Unless it's possible to set these rights depending on whether a 32bit or
a 64bit process is run by the user I don't see how this would come into
play. As I said, it's the exact same user and the exact same setup for
both 64bit and 32bit.
>> Did the strace I sent you give any clue (I can make
>> one again if that helps) because it seems that everything just works out as
>> it should until the fork that should start the command given to ssh.
>
> The strace shows that it doesn't even *try* to start bash, but it's
> entirely unclear why.
See my other mail, not that it elucidates the reason, but I think I've
pinpointed where it happens now.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
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-09-02 17:32 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
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 [this message]
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=87iol6q670.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).