Re: seteuid problem with sshd

2019-03-14 Thread Bruce Halco
On 3/14/19 5:47 AM, Corinna Vinschen wrote: On Mar 13 22:20, Bruce Halco wrote: I had found nothing referencing "No such file or directory", which sounds rather different from a permissions problem. Running sshd under the Local System account made no difference. passwd -R was no help. What

Re: seteuid problem with sshd

2019-03-14 Thread Corinna Vinschen
On Mar 13 22:20, Bruce Halco wrote: > I had found nothing referencing "No such file or directory", which sounds > rather different from a permissions problem. > > Running sshd under the Local System account made no difference. > > passwd -R was no help. > > What I did discover was that cygwin/ss

Re: seteuid problem with sshd

2019-03-13 Thread Bruce Halco
I had found nothing referencing "No such file or directory", which sounds rather different from a permissions problem. Running sshd under the Local System account made no difference. passwd -R was no help. What I did discover was that cygwin/sshd apparently now requires the Windows account to

Re: seteuid problem with sshd

2019-03-13 Thread Andrey Repin
Greetings, Bruce Halco! > I'm having to update a number of cygwin installations that are about a > year old (cygwin 2.9.0-3). Usually I just run the installer and > everything goes fine.  Occasionally I've run into a problem and had to > remove the existing installation and reinstall. > Appare

Re: seteuid problem with sshd

2019-03-13 Thread Houder
On Wed, 13 Mar 2019 19:26:11, Bruce Halco wrote: > I'm having to update a number of cygwin installations that are about a > year old (cygwin 2.9.0-3). Usually I just run the installer and > everything goes fine.  Occasionally I've run into a problem and had to > remove the existing installation

seteuid problem with sshd

2019-03-13 Thread Bruce Halco
I'm having to update a number of cygwin installations that are about a year old (cygwin 2.9.0-3). Usually I just run the installer and everything goes fine.  Occasionally I've run into a problem and had to remove the existing installation and reinstall. Apparently something has changed with ss