DMARC-Filter: OpenDMARC Filter v1.4.2 delorie.com 50HE1EGt695536
Authentication-Results: delorie.com; dmarc=pass (p=none dis=none) header.from=cygwin.com
Authentication-Results: delorie.com; spf=pass smtp.mailfrom=cygwin.com
DKIM-Filter: OpenDKIM Filter v2.11.0 delorie.com 50HE1EGt695536
Authentication-Results: delorie.com;
	dkim=pass (1024-bit key, unprotected) header.d=cygwin.com header.i=@cygwin.com header.a=rsa-sha256 header.s=default header.b=QHBqJClW
X-Recipient: archive-cygwin AT delorie DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6E7F23847838
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1737122473;
	bh=Z54tZLuxgUfGTgEhW/X/iJOhaP8wm4g7isTrvfG1pI0=;
	h=Date:To:Subject:References:In-Reply-To:List-Id:List-Unsubscribe:
	 List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc:
	 From;
	b=QHBqJClW6HFnV/f4yc1u/3GHRZDgy3RBFM8Ael3wjpLutteE5+nJF2aFKuzSL8jw7
	 hlSfT95tl65SosNSutjzqGrbpFpRcvB1xxN4kmg4xBlqs9I2cGrVEVMNglPkqd/gmF
	 wrgNVfueN6sII5yQllcQlndVRihYg5+Y/RqMp890=
X-Original-To: cygwin AT cygwin DOT com
Delivered-To: cygwin AT cygwin DOT com
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org EBF61384781B
Date: Fri, 17 Jan 2025 15:00:49 +0100
To: cygwin AT cygwin DOT com
Subject: Re: sshd not working properly
Message-ID: <Z4pikbPJz1kDINbY@calimero.vinschen.de>
Mail-Followup-To: cygwin AT cygwin DOT com
References: <LTQOVCXmc0omW9pKR5Kf2VV2rkqMLBgNy-HyfSog-h2-eEjbnJroxxEUCUTKQSQrMGXaZJ7FH2qocwS-hpfW3RveKOrq-HlRtJqh7NDg8w4=@proton.me>
 <CAL63K1XbYdKYGxacM-ifuakReCQefYB1K5MmWS2YuT2+La=RdQ AT mail DOT gmail DOT com>
 <6c39972b-43ef-4e32-a238-f2778f3cc4e5 AT emmenlauer DOT de>
 <Z4pSUtv0CdZNZSo4 AT calimero DOT vinschen DOT de>
 <6e459d03-150e-4dd3-8fed-9fbe7dbcff40 AT SystematicSW DOT ab DOT ca>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <6e459d03-150e-4dd3-8fed-9fbe7dbcff40@SystematicSW.ab.ca>
X-BeenThere: cygwin AT cygwin DOT com
X-Mailman-Version: 2.1.30
Precedence: list
List-Id: General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe: <https://cygwin.com/mailman/options/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive: <https://cygwin.com/pipermail/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe: <https://cygwin.com/mailman/listinfo/cygwin>,
 <mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From: Corinna Vinschen via Cygwin <cygwin AT cygwin DOT com>
Reply-To: cygwin AT cygwin DOT com
Cc: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com
Sender: "Cygwin" <cygwin-bounces~archive-cygwin=delorie DOT com AT cygwin DOT com>

On Jan 17 06:41, Brian Inglis via Cygwin wrote:
> On 2025-01-17 05:51, Corinna Vinschen via Cygwin wrote:
> > On Jan 17 11:59, Mario Emmenlauer via Cygwin wrote:
> > > I am under the impression that there may be a misbehavior in more recent
> > > Cygwin OpenSSH :-(
> > > 
> > > I observe the same problem as Andy Wood was having, and found another
> > > very recent identical report at https://serverfault.com/q/1168457/473559.
> > > Their cases, as well as mine, seem to share, that OpenSSH can no longer
> > > correctly authenticate as a user without having the plain text password
> > > stored in the registry.
> > > 
> > > In my case, this is exclusively limited to domain users. Local users
> > > work correctly. I can see that at least one other report, the one at
> > > Serverfault, is also for a domain user. Also, everything that is
> > > reported at Serverfault applies basically identically to my case, i.e.
> > > the connection being just dropped, and the only relevant message from
> > > OpenSSH being "fatal: seteuid 4096: Function not implemented".
> > 
> > I just tested this on my local W11 24H2 Enterprise installation with
> > Cygwin 3.5.5 and OpenSSH 9.9p1 installed as service under the SYSTEM
> > account, and it works fine for me in a Windows domain with one 2019 and
> > one 2022 Domain Server.
> > 
> > I tested with a user account in the administrators group as well as with
> > a non-admin user account, and to both accounts I can login with pubkey
> > authentication as expected.
> > 
> > The error message "seteuid 4096: Function not implemented" is weird.
> > The internal implementation only uses documented functions.
> > 
> > Which Windows version are you running the service on exactly?
> > 
> > Do you have any other entries in the server-side Windows Log, which may
> > be connected, especially inside the Security log.  Kerberos or so.
> > 
> > Other than that, it might be prudent to run sshd in a SYSTEM shell
> > under strace.
> 
> Any chance the user is also running Windows sshd and tyhat has grabbed the port?

Good point, worth checking...


Corinna

-- 
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple