DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:cc:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=KnsL9LrlT659qix4qNj+ZMLFdBDcfTw/JLJqpCPAlt8WL2WAIC9+V
	fEZSN8OJ0aznc0RUKBP3AiUyTEmZyq3VrmbpfCa3mRJr+CWqlIYNMtJ7frphTNnR
	bH1PDdsxklkOwlW/QsN+tX5pax+7yuV7rlvolxEGAATuJrx2HgftEI=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Tue, 12 Mar 2019 22:30:51 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: davek AT 6thstreetradio DOT org
Cc: cygwin AT cygwin DOT com
Subject: Re: sshd error "seteuid: No such device or address"
Message-ID: <20190312213051.GR3785@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: davek AT 6thstreetradio DOT org, cygwin AT cygwin DOT com
References: <CAHdnY6OKu_2Zf8qRM3u9=T-rpKXWH4GiY8mJZUGLJr39O3kHBg AT mail DOT gmail DOT com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;	protocol="application/pgp-signature"; boundary="7oQ1FFvyVKNZi+9s"
Content-Disposition: inline
In-Reply-To: <CAHdnY6OKu_2Zf8qRM3u9=T-rpKXWH4GiY8mJZUGLJr39O3kHBg@mail.gmail.com>
User-Agent: Mutt/1.11.3 (2019-02-01)

--7oQ1FFvyVKNZi+9s
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Mar 12 17:09, David Dombrowsky wrote:
> I managed to solve this problem, but I'd love some confirmation that I
> solved it the right way.
>=20
> After updating cygwin and rebooting, all of a sudden I couldn't ssh
> into my windows box.  The remote gave the usual "connection closed by
> <bla> port 22" before anything happened.  Running in debug mode from
> an admin shell didn't yield anything, but looking in the windows
> application logs, I saw:
>=20
> sshd: PID 2588: fatal: seteuid 1056480: No such device or address
>=20
> The google suggested that the error was pty related, but it was not.
>=20
> By accident, I noticed that I could log in from an account that I
> hadn't set up public key auth, using my password.  So I forced ssh to
> prompt for my password and viola!  I got in just fine.
>=20
> On the server, I started another admin shell and did `passwd -R
> my.username` and input my password.  That was the key.  I can now log
> in using public key auth as I could a few hours ago.
>=20
> Was that the correct solution?  Is that expected?  This windows box is
> on a domain, so that might have something to do with it.

Just switch the account sshd is running under from "cyg_server" to
SYSTEM (or "LocalSystem") and you should be able to logon without the
passwd -R method again.

This is a side effect of changing how Cygwin switches the user
context by default.  See

https://cygwin.com/cygwin-ug-net/ntsec.html#ntsec-nopasswd1


HTH,
Corinna

--=20
Corinna Vinschen
Cygwin Maintainer

--7oQ1FFvyVKNZi+9s
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEoVYPmneWZnwT6kwF9TYGna5ET6AFAlyIJQsACgkQ9TYGna5E
T6ApRg//ZP8YHuQGfDItdFm6HwXOGlFvTa0VV+g5m5PA6gA8oNEbe6BBQ0xX9Slv
K/B4aI6BrT9k2mKHdmh2ojVkwXgFuDZbWLH6ZsLYXZFICQ7artPVjWnv6cuFUPdm
hCWJ0TqF8jry94BfDziNzD+8+DqGL6au32x3lr8GldWlVIibxlKTCQ5dfpGxMsJO
dUI1yQFTbwT0u4b/ImD0XeatUKq6a6xOZRkmBYOKOona7spUnyAdidAyRtpguD1a
lWnuHnkGxDmbS893Nsr6RgFYA5vb2OMYewF5o2P1PNypdcVx8vfBoAbBuc6qjX45
DLliTmqRSUzW689KiFhzvRiSKxCZESGI3MQfQJ+IR7ccT4f+k5xRQyQiBVaNgV3b
gmIIc8qw+qIjoqJZetZDN+w/6TWxnnAcuG0hT3hELh+/FxqOKb+lHCBAjWzMg75I
bDtvq7zfKk2Gizbb9vphhW7DESTieGHYvXxIxLEu5dof8AUPf9dtKtoqo/m2Th2a
wB2E4z9104+qpK9r89AUegEX/4rdDjN9wkus/7PTN6eUe9yOLyLpKq7bM0Ow01WV
GsWDsc/VpmLHcl1Qkp0ppyVA+r8Gr57ZiNecGmZnzc99RmrPHFnrAC7cdL1VLDUf
MhWghj6hoPaBqCUa8LFnCjLD8hwwUPV1Q21sGH5Z/u3LcSIiAJo=
=98ZG
-----END PGP SIGNATURE-----

--7oQ1FFvyVKNZi+9s--