From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0b-00235401.pphosted.com (mx0b-00235401.pphosted.com [205.220.180.225]) by sourceware.org (Postfix) with ESMTPS id D69703857BAC for ; Tue, 24 May 2022 22:15:06 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org D69703857BAC Received: from pps.filterd (m0282623.ppops.net [127.0.0.1]) by mx0b-00235401.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 24OHW8Rf012247 for ; Tue, 24 May 2022 22:15:06 GMT Received: from email.bryanlgh.org (musketeers.bryanlgh.org [198.203.245.8]) by mx0b-00235401.pphosted.com (PPS) with ESMTPS id 3g93um0bj4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for ; Tue, 24 May 2022 22:15:06 +0000 From: Dale Lobb To: "'cygwin@cygwin.com'" Subject: Issue with seteuid and openssh Thread-Topic: Issue with seteuid and openssh Thread-Index: Adhvtv02KbP6OJaqT2yFog+Hy47J/g== Date: Tue, 24 May 2022 22:15:05 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.240.2.50] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Proofpoint-GUID: SzNgpnZPhe5bi6gdeSM28eCZB1IGkGt0 X-Proofpoint-ORIG-GUID: SzNgpnZPhe5bi6gdeSM28eCZB1IGkGt0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 clxscore=1011 mlxscore=0 suspectscore=0 mlxlogscore=677 spamscore=0 priorityscore=1501 adultscore=0 bulkscore=0 lowpriorityscore=0 phishscore=0 malwarescore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2204290000 definitions=main-2205240110 X-Spam-Status: No, score=-0.1 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, LIKELY_SPAM_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 May 2022 22:15:08 -0000 Greetings All, Has anyone seen an issue similar to this? I have a VMWare virtual machine loaded with Windows Server 2016 OS and a = Cygwin installation. Cygwin runs an installed SSHD service via cygrunsrv.e= xe. A data gateway engine on a different machine makes regular programmati= c connections via SFTP to the server throughout the day. This setup was es= tablished in 2021 and has run without issue for almost a year. Last night, the server rebooted automatically after windows updates. Aft= er the reboot, the data gateway was then no longer able to connect to the s= erver. This condition persisted until I was informed of the issue this mor= ning and connected to the Windows server using RDP to take a look at the is= sue, at which point the SSH connection suddenly started working. Further t= ests showed this to be entirely repeatable. After rebooting the server, th= e SSHD daemon does not allow connections, neither with password nor public = key authorization, until someone connects to the server via RDP, at which t= ime the SSH connections suddenly starts working again. The server's Windows application event log shows numerous errors from the= SSHD daemon stating "sshd: PID <####>: fatal: seteuid 197108: No such devi= ce or address" during the time frame when SSH connection were not working. = The errors stop immediately when the RDP connection is recorded in the sam= e event log. A google search for the error message turned up something somewhat simila= r from this mailing list back in March of 2019, bit there is no mention of = RDP in that exchange. Also, the advice given, to convert the SSHD service = from running under the cyg_server account to LocalSystem, does not apply he= re, because the Cygwin installation is recent enough that it is already run= ning under LocalSystem. When this issue started, the server was running openssh-8.7p1-1. The ser= ver was subsequently updated to the latest, openssh-9.0p1-1, but there has = been no change in the observed behavior. Best Regards, Dale Lobb ________________________________ CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is = for the sole use of the intended recipients and may contain confidential an= d privileged information. Any unauthorized review, use, disclosure or distr= ibution is prohibited. If you are not the intended recipient, please contac= t the sender by reply e-mail and destroy all copies of the original message= .