From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: question about checking for HW RNG support on apu4 appliance
Date: Thu, 08 Sep 2022 21:16:27 +0200 [thread overview]
Message-ID: <f4e51a18f8763f297aedf1eb52dd0ef1e1b76ac2.camel@sicho.home> (raw)
[-- Attachment #1: Type: text/plain, Size: 1293 bytes --]
Hi all
If I understand it correctly, when HW RNG is supported, the Random
Number Generator Daemon (rngd) should be running ?
So in my Zabbix monitoring template for IPFire, I try to check if HW
RNG is available and if so, I monitor the state of the rngd daemon.
Previously I had no HW RNG support on the apu4 appliance until a few
core updates ago where this was introduced with a firmware update. So
now the rngd daemon is automatically started on the appliance.
To know if HW RNG is supported, I currently check the contents of
/proc/cpuinfo for the occurrence of the string "rdrand" (which seems a
correct check on x86_64 machines) but this string was and still is not
present on the apu4 appliance.
So I was wondering if anyone knows how to correctly check if HW RNG
support is available? So that this check works for all platforms.
Sidenote: This information (HW RNG support / rndg daemon state) was
previously also available on the entropy page of the IPFire GUI, but it
seems this info is now gone together with the now obsolete entropy
graph. Was this intentional ? I assume that information is still
relevant even when with the entropy value gone?
Thanks
Robin
--
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.
next reply other threads:[~2022-09-08 19:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-08 19:16 Robin Roevens [this message]
2022-09-08 19:31 ` Michael Tremer
2022-09-08 20:12 ` Robin Roevens
2022-09-08 21:37 ` Robin Roevens
2022-09-09 8:26 ` Paul Simmons
2022-09-09 10:31 ` Michael Tremer
2022-09-09 11:17 ` Robin Roevens
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=f4e51a18f8763f297aedf1eb52dd0ef1e1b76ac2.camel@sicho.home \
--to=robin.roevens@disroot.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