From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: davek@6thstreetradio.org
Cc: cygwin@cygwin.com
Subject: Re: sshd error "seteuid: No such device or address"
Date: Tue, 12 Mar 2019 21:31:00 -0000 [thread overview]
Message-ID: <20190312213051.GR3785@calimero.vinschen.de> (raw)
In-Reply-To: <CAHdnY6OKu_2Zf8qRM3u9=T-rpKXWH4GiY8mJZUGLJr39O3kHBg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1535 bytes --]
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.
>
> 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:
>
> sshd: PID 2588: fatal: seteuid 1056480: No such device or address
>
> The google suggested that the error was pty related, but it was not.
>
> 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.
>
> 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.
>
> 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
--
Corinna Vinschen
Cygwin Maintainer
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-03-12 21:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 21:09 David Dombrowsky
2019-03-12 21:31 ` Corinna Vinschen [this message]
2019-03-13 0:18 ` David Dombrowsky
2019-03-13 0:54 ` Bill Stewart
2019-03-13 2:02 ` David Dombrowsky
2019-03-13 2:11 ` Bill Stewart
2019-03-13 18:32 ` Achim Gratz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190312213051.GR3785@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=davek@6thstreetradio.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).