Corinna Vinschen <corinna-cygwin <at> cygwin.com> 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.
I've switched privilege separateion off completely, but no dice. The Access Denied comes from trying to switch from primary group "MACHINE+None" to "Domain Users". That is expected to happen, what I still don't get is why the parent process winds up with the exception instead of the originating process as on 64bit. > 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. When the process comes to this point it has already verified the user via AD. > The strace shows that it doesn't even *try* to start bash, but it's > entirely unclear why. Is it possible to run sshd in gdb? Regards, Achim. -- 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
