From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Fixing problems installing IPFire on systems without randomness
Date: Wed, 29 Apr 2020 19:33:02 +0000 [thread overview]
Message-ID: <20200429193304.21404-1-michael.tremer@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 635 bytes --]
This is a small patchset trying to fix problems with setting up
IPFire on systems like PC Engines APU boards.
When running through setup, the admin password cannot be set because
htpasswd(8) now calls the get_random() syscall which locks for forever
when the kernel's CPRNG has not been initialised, yet.
These patches start rngd before that and pause the boot process
until enough randomness is available.
This is not a great solution, but a good hotfix right now.
We will have to revisit this soon and hopefully get rid of
the loopy script which has its own flaws.
I am happy to listen to any creative ideas :)
Best,
-Michael
next reply other threads:[~2020-04-29 19:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-29 19:33 Michael Tremer [this message]
2020-04-29 19:33 ` [PATCH 1/2] random: Launch rngd earlier in the boot process Michael Tremer
2020-04-29 19:33 ` [PATCH 2/2] random: Initialise the kernel's PRNG earlier Michael Tremer
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=20200429193304.21404-1-michael.tremer@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.org \
/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