From: Christopher Mapes <apresence@hotmail.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: 3.0.7: Possible sshd bug when running as a service and public key offered
Date: Tue, 03 Dec 2019 13:16:00 -0000 [thread overview]
Message-ID: <BYAPR01MB52056EF81AF0FE6045FFF06EB7420@BYAPR01MB5205.prod.exchangelabs.com> (raw)
In-Reply-To: <BYAPR01MB5205D937AD9706CB9E793721B7420@BYAPR01MB5205.prod.exchangelabs.com>
I was able to get the debug logging working while running sshd as a service. Here is a snippet of the issue:
...
debug2: input_userauth_request: try method publickey [preauth]
debug2: userauth_pubkey: valid user user-xx attempting public key ssh-rsa rsa-data-xx [preauth]
debug3: userauth_pubkey: have ssh-rsa signature for RSA SHA256:sha-data-xx [preauth]
debug3: mm_key_allowed entering [preauth]
debug3: mm_request_send entering: type 22 [preauth]
debug3: mm_key_allowed: waiting for MONITOR_ANS_KEYALLOWED [preauth]
debug3: mm_request_receive_expect entering: type 23 [preauth]
debug3: mm_request_receive entering [preauth]
debug3: mm_request_receive entering
debug3: monitor_read: checking request 22
debug3: mm_answer_keyallowed entering
debug3: mm_answer_keyallowed: key_from_blob: 0x60008fcf0
debug1: temporarily_use_uid: 1074753138/1073742337 (e=18/18)
seteuid 1074753138: No such device or address
debug1: do_cleanup
debug1: Killing privsep child 302
--
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 parent reply other threads:[~2019-12-03 13:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BYAPR01MB5205D937AD9706CB9E793721B7420@BYAPR01MB5205.prod.exchangelabs.com>
2019-12-03 13:16 ` Christopher Mapes [this message]
2019-12-05 11:19 Christopher Mapes
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=BYAPR01MB52056EF81AF0FE6045FFF06EB7420@BYAPR01MB5205.prod.exchangelabs.com \
--to=apresence@hotmail.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).