From: Andreas Ziegler <br015@umbiko.net>
To: buildroot@busybox.net
Subject: [Buildroot] SSH server starts too late
Date: Fri, 21 Feb 2020 13:51:18 +0100 [thread overview]
Message-ID: <33327ed4301c921b1ded444b5b7c3b89@umbiko.net> (raw)
In-Reply-To: <mailman.11.1582286403.41897.buildroot@busybox.net>
Hi Omar,
On 2020-02-21 13:00, Hammami Omar <omar18hammami@gmail.com> wrote
> I am using the buildroot version "2019.11.1" and I have noticed that my
> SSH
> server starts too late.
> I was using an old version "2017.08" and the SSH server was starting
> normally.
This issue is not related to Buildroot, but caused by changes in
libopenssl (which in turn is used by OpenSSH), starting around the
middle of last year. You will find a lot of background information when
you search the www for 'boot-time entropy starvation'; the cause is,
reading random data from /dev/urandom blocks until the kernel entropy
pool has been initialized.
Workarounds:
(a) Patch libopenssl (not recommended for nodes directly connected to
the WAN).
(b) Use a more recent kernel; version 5.4.y introduced a temporary fix
for this issue.
(c) Use other sources of extra randomness, as proposed by Peter
Seiderer.
Kind regards,
Andreas
next parent reply other threads:[~2020-02-21 12:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11.1582286403.41897.buildroot@busybox.net>
2020-02-21 12:51 ` Andreas Ziegler [this message]
2020-02-24 9:29 ` [Buildroot] SSH server starts too late Hammami Omar
[not found] ` <1d91f38acaeecb790f5a44d104ae0ca1@umbiko.net>
2020-02-24 13:07 ` Andreas Ziegler
[not found] ` <CAGSpp9ng2yxCK=RZeq1Z_Bce4pwij9FQED23SpGuvjqm5awHhg@mail.gmail.com>
2020-02-24 13:22 ` Andreas Ziegler
2020-02-24 14:07 ` Hammami Omar
2020-02-24 15:16 ` Hammami Omar
2020-02-21 9:13 Hammami Omar
2020-02-21 10:19 ` Peter Seiderer
2020-02-21 14:50 ` Hammami Omar
2020-02-21 16:16 ` Hammami Omar
2020-02-21 18:08 ` Grant Edwards
2020-02-21 18:30 ` Hammami Omar
2020-03-03 12:33 ` Hammami Omar
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=33327ed4301c921b1ded444b5b7c3b89@umbiko.net \
--to=br015@umbiko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.