From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 13671] New: openSSH server closes connection before authentication is finished
Date: Tue, 23 Mar 2021 19:28:39 +0000 [thread overview]
Message-ID: <bug-13671-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=13671
Bug ID: 13671
Summary: openSSH server closes connection before authentication
is finished
Product: buildroot
Version: 2021.02
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: g.lens at livetech-systems.com
CC: buildroot at uclibc.org
Target Milestone: ---
After updating from v2019.02.09 to v2021.02, I am not able to connect to my
board via SSH. The OpenSSH server on my device closes the connection abruptly
and exits with 255 before the keys can be exchanged. I have tried to use a
password, but this gave the same result. I am using the default sshd_config as
this was working with v2019.02.09.
I attached the server and client logs as well as the defconfig for more
information.
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2021-03-23 19:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-23 19:28 bugzilla at busybox.net [this message]
2021-03-23 19:30 ` [Buildroot] [Bug 13671] openSSH server closes connection before authentication is finished bugzilla at busybox.net
2021-03-23 20:01 ` bugzilla at busybox.net
2021-03-23 20:45 ` bugzilla at busybox.net
2021-03-23 21:16 ` bugzilla at busybox.net
2021-03-23 22:10 ` bugzilla at busybox.net
2021-03-23 22:32 ` bugzilla at busybox.net
2021-03-24 11:35 ` bugzilla at busybox.net
2021-03-25 21:09 ` bugzilla at busybox.net
2021-03-27 16:51 ` bugzilla at busybox.net
2021-03-28 17:41 ` bugzilla at busybox.net
2021-03-30 10:18 ` bugzilla at busybox.net
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=bug-13671-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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