From: Peter Seiderer <ps.report@gmx.net>
To: Steve <sleepy_dog@gmx.de>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] openssh - kernel messages upon connection attempts (always ending with "connection reset" at the other end)
Date: Wed, 20 Oct 2021 18:54:35 +0200 [thread overview]
Message-ID: <20211020185435.48c2eddb@gmx.net> (raw)
In-Reply-To: <20211020185304.60af9ff8@gmx.net>
Hallo Steve,
>
> This is maybe a known feature/bug of the combination of openssh and (some) external
> toolchains, see [1] for discussion, patch/hack to avoid the problem and/or
> the hint to use another/internal toolchain..., or use dropbear instead of openssh...
>
> Regards,
> Peter
>
And the missing link:
[1] https://bugs.busybox.net/show_bug.cgi?id=13671
Regards,
Peter
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-10-20 16:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 11:36 [Buildroot] openssh - kernel messages upon connection attempts (always ending with "connection reset" at the other end) Steve
2021-10-20 12:01 ` Arnout Vandecappelle
2021-10-20 13:38 ` Steve
2021-10-20 16:53 ` Peter Seiderer
2021-10-20 16:54 ` Peter Seiderer [this message]
2021-10-20 17:31 ` Steve
-- strict thread matches above, loose matches on Subject: below --
2021-10-20 15:43 Steve
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=20211020185435.48c2eddb@gmx.net \
--to=ps.report@gmx.net \
--cc=buildroot@buildroot.org \
--cc=sleepy_dog@gmx.de \
/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