one way is to make rng-tools use less resources on embedded devices
perhaps limit the number of cores its give and buffer sizes.
secondly send a patch to remove openssh dependency on rng-tools perhaps
On Thu, May 5, 2022 at 2:34 PM Wes Malone wrote:
>
> I'm not well versed enough in these details
I'm not well versed enough in these details to make a decision but I'd
like to help fix it once the decision is made. I of course moved on
with a small append on my end but I'd like to help fix this since it
affected my project.
On Tue, May 3, 2022 at 11:21 AM Khem Raj wrote:
>
> On Tue, May 3, 2
On Tue, May 3, 2022 at 8:23 AM Wes Malone wrote:
>
> > Isn't this desirable if you don't have an hwrng?
> Perhaps what's needed then is a 'hwrng' in MACHINE_FEATURES?
>
> > Can’t rng-tools figure out the right sources at run time?
> rng-tools enables jitter by default if it's built in, even if hwr
> Isn't this desirable if you don't have an hwrng?
Perhaps what's needed then is a 'hwrng' in MACHINE_FEATURES?
> Can’t rng-tools figure out the right sources at run time?
rng-tools enables jitter by default if it's built in, even if hwrng is
available. Maybe it's faster to do this on more powerfu
Yes, I wonder why this needs to be disabled altogether at build time. Can’t
rng-tools figure out the right sources at run time?
Alex
On Mon 2. May 2022 at 23.33, William A. Kennington III via
lists.openembedded.org wrote:
> Isn't this desirable if you don't have an hwrng? We want to generate
>
Isn't this desirable if you don't have an hwrng? We want to generate
entropy so we can perform cryptographic operations by default if we
bring in rng-tools.
On Mon, May 2, 2022 at 2:10 PM Wes Malone wrote:
>
> After boot rngd maxes out the processor initializing JITTER entropy for
> some minutes.
After boot rngd maxes out the processor initializing JITTER entropy for
some minutes. Here we disable libjitterentropy in favor of only using
the hardware random source via config.
Signed-off-by: Wes Malone
---
meta/recipes-support/rng-tools/rng-tools_6.15.bb | 1 -
1 file changed, 1 deletion(-)
Since updating to kirkstone from hardknott, after boot rngd maxes out my
rpi4's processor for minutes initializing JITTER. The sustained CPU
usage was triggering my resource monitoring alerts. Changing config to
disable jitter with -x jitter stops the initialization process and uses
just the pi's h
