Web lists-archives.com

Re: seteuid problem with sshd




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 be Enabled.  That was not the case previously.

The target systems in my application are in restaurant offices, and only use a single Windows login.

As the people who use ssh do not need local Windows accounts, I've always used the practice of Disabling those user accounts in Windows. The credentials were available to ssh, without the security issues of all those extra active accounts.

Unless someone can suggest an alternative, I'll have to leave all those accounts Enabled. I can put some long, nasty passwords on them to keep the risk acceptable.

Thanks.

Bruce


On 3/13/19 7:50 PM, Andrey Repin wrote:
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.
Apparently something has changed with ssh.  I now go though the same
installation process I've been using for years, but sshd logins fail
after connection with
      "fatal: seteuid xxxxxx: No such file or directory"
The ssh client gets as far as offering the key. The last two lines from
the client side are
      debug1: Offering public key: bhalco.ssh RSA
SHA256:DDFVOXwQIpPODxXJPxp8Mxj1Y1mXsMqdmrvVYi5P51c agent
      Connection closed by 192.168.0.12 port 32000
I've reproduced the problem on two computers. Both are running Windows
7, although the same update will need to be applied to Windows 10 systems.
I haven't found any info using Google or the cygwin archives.
Please don't lie. The archive is full of recent reports.

I don't even have a good guess what file or directory is missing.
I'd greatly appreciate any suggestions.
Try changing the owning user of sshd service to LocalSystem for a starter.




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