This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Windows Server 2012R2 64bit and 32bit Cygwin sshd

On Sep  2 15:16, Achim Gratz wrote:
> Corinna Vinschen <corinna-cygwin <at>> writes:
> > I have no idea what could be wrong in your environment, sorry.
> Me neither.  I've set all three Cygwin environments up exactly the same way,
> using identical users and command lines (just different service names,
> obviously).
> I still have to use a local cyg_server account and a local sshd account, the
> latter of which gets mapped from MACHINE+sshd to plain sshd via /etc/passwd
> to get sshd to start.

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.

>   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.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

Attachment: pgpzRpCdIzk58.pgp
Description: PGP signature

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]