DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=KGz5TiFzB52MG5P0
	FJNeLiQjA6gaE2nS4waW6DF8OvD3lgHup1z/q1PXjYlzrMWnqbb81saBcrbGbNd6
	mNXF3UWcxfg1LsWlOkvEZa6/Hq3xiuGNiO/JtwfeFVhrGXrrnkLRNEKkA8rs5G7z
	kODl2Krw1Wd5SH4AT1tGllBICAY=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Subject: Re: seteuid problem with sshd
To: cygwin@cygwin.com
References: <68371e6b-aee9-4e70-d079-098160f7bf61@halcomp.com> <1231848485.20190314025011@yandex.ru>
From: Bruce Halco <bruce@halcomp.com>
Message-ID: <032d1268-15e7-f10d-bdd7-45effb6b6a2b@halcomp.com>
Date: Wed, 13 Mar 2019 22:20:08 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <1231848485.20190314025011@yandex.ru>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

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