From: Andrey Repin <anrdaemon@yandex.ru>
To: Bruce Halco <bruce@halcomp.com>, cygwin@cygwin.com
Subject: Re: seteuid problem with sshd
Date: Thu, 14 Mar 2019 00:05:00 -0000 [thread overview]
Message-ID: <1231848485.20190314025011@yandex.ru> (raw)
In-Reply-To: <68371e6b-aee9-4e70-d079-098160f7bf61@halcomp.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=utf-8, Size: 1625 bytes --]
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.
--
With best regards,
Andrey Repin
Thursday, March 14, 2019 2:48:44
Sorry for my terrible english...\x03B‹KCB”\x1c›Ø›\x19[H\x1c™\^[Ü\x1cΈ\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÜ\x1c›Ø›\x19[\Ëš\x1d^[[\x03B‘TNˆ\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ˜\KÃB‘^[ØÝ[Y[\x18]\x1a[ÛŽˆ\b\b\b\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÙ^[ØÜËš\x1d^[[\x03B•[œÝXœØÜšX™H\x1a[™›Îˆ\b\b\b\b\b\x1a\x1d\x1d\x1c\x0e‹ËØÞYÝÚ[‹˜ÛÛKÛ[\vÈÝ[œÝXœØÜšX™K\Ú[\^[\x19CBƒB
next prev parent reply other threads:[~2019-03-14 0:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 23:26 Bruce Halco
2019-03-14 0:00 ` Houder
2019-03-14 0:05 ` Andrey Repin [this message]
2019-03-14 2:20 ` Bruce Halco
2019-03-14 9:47 ` Corinna Vinschen
2019-03-14 10:45 ` Bruce Halco
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=1231848485.20190314025011@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=bruce@halcomp.com \
--cc=cygwin@cygwin.com \
/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).