From: n0nc3 <pkoshar@compunetix.com>
To: cygwin@cygwin.com
Subject: OpenSSH: SSHD daemon (as SYSTEM) is partially broken
Date: Thu, 27 Feb 2020 18:09:00 -0000 [thread overview]
Message-ID: <1582826967147-0.post@n5.nabble.com> (raw)
It appears Cygwin SSHD's functionality is partially broke in the later
versions, where SSHD runs as SYSTEM (no longer cyg_server).
On reboot, any attempt to SSH into the server *before* any previous logon
attempt (RDP/locally/etc) is quickly denied:
debug1: Offering public key: /home/<user>/.ssh/id_rsa
debug3: send_pubkey_test
debug2: we sent a publickey packet, wait for reply
Connection closed by <server_addr>
Once an RDP/local login is attempted, regardless of success/failure,
subsequent ssh attempts will progress to the password prompt which
eventually gets us in.
The Event Viewer shows the attached error message, relating to a NULL SID
and 0xC00000BB status.
ssh_as_first_login.txt
<http://cygwin.1069669.n5.nabble.com/file/t11987/ssh_as_first_login.txt>
It was a rather vanilla 'ssh-host-config' run to get it installed: strict
modes = no, no special ssh_/sshd_config settings at this point.
Running latest cygwin packages on Windows Server 2016 Standard:
CYGWIN_NT-10.0 <server_name> 3.1.4(0.340/5/3) 2020-02-19 08:49 x86_64 Cygwin
...
openssh 8.2p1-1 OK
--
Sent from: http://cygwin.1069669.n5.nabble.com/Cygwin-list-f3.html
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next reply other threads:[~2020-02-27 18:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 18:09 n0nc3 [this message]
2020-02-27 19:34 ` Bill Stewart
2020-02-27 23:10 ` TestUser1
2020-02-28 14:53 ` Bill Stewart
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=1582826967147-0.post@n5.nabble.com \
--to=pkoshar@compunetix.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).