This is the mail archive of the
mailing list for the Cygwin project.
Re: Windows Server 2012R2 64bit and 32bit Cygwin sshd
- From: Achim Gratz <Stromeko at nexgo dot de>
- To: cygwin at cygwin dot com
- Date: Tue, 02 Sep 2014 19:32:19 +0200
- Subject: Re: Windows Server 2012R2 64bit and 32bit Cygwin sshd
- Authentication-results: sourceware.org; auth=none
- References: <8761hphfps dot fsf at Rainer dot invalid> <loom dot 20140902T134545-288 at post dot gmane dot org> <20140902140751 dot GD6056 at calimero dot vinschen dot de> <loom dot 20140902T171114-72 at post dot gmane dot org> <20140902153757 dot GE6056 at calimero dot vinschen dot de>
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.
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Factory and User Sound Singles for Waldorf rackAttack:
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple