From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: Re: ssh troubles
Date: Wed, 17 Jun 2020 21:34:12 +0200 [thread overview]
Message-ID: <c3e72b9b-3c20-6502-b23d-c8258446108a@gmail.com> (raw)
In-Reply-To: <CADF5XCynm6M2+teNKBDOeR_u0vT5pmbdctXrThdseR_FZz=5HA@mail.gmail.com>
On 17.06.2020 20:46, Raman Gupta via Cygwin wrote:
> Hello all, for some reason I've started having troubles with cygwin sshd,
> despite having successfully used it for years. Not sure if some recent
> Windows updates broke it or something, but now I'm getting the infamous:
>
> sshd: PID 1855: fatal: seteuid 1049703: No such device or address
>
> I believe I've followed all the advice given on this list over the years
> regarding this error:
>
> * installed cygwin 64-bit (this fixed it for a while, but now its broken
> again)
> * uninstalled the service, and reinstalled with ssh-host-config
> * verified all permissions on home, .ssh, and authorized_keys files are
> correct (and configuring in non-strict mode doesn't work either anyway)
> * running the service as Local System (as installed by recent versions of
> ssh-host-config)
> * updated to the latest openssh version available (this also fixed it for a
> while, but then it broke again)
> * removing any /etc/password or /etc/group files
> * removing any value for CYGWIN environment variable
>
> $ cygcheck -c openssh
> Cygwin Package Information
> Package Version Status
> openssh 8.3p1-1 OK
>
> What's very odd is that, recently, I seem to be able to get it to work with
> various approaches (see above), it works for a while, and then it borks
> again.
>
> Any ideas?
>
> Regards,
> Raman
> --
Corporate computer with continuous reset of corporate policy ?
I had such experience in the past.
please provide the cygcheck.out as ATTACHMENT
see https://cygwin.com/problems.html
next prev parent reply other threads:[~2020-06-17 19:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 18:46 Raman Gupta
2020-06-17 19:34 ` Marco Atzeri [this message]
2020-06-20 17:46 ` Raman Gupta
2020-06-24 4:17 ` Raman Gupta
2020-06-17 21:40 ` Kevin Schnitzius
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=c3e72b9b-3c20-6502-b23d-c8258446108a@gmail.com \
--to=marco.atzeri@gmail.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).