diff options
| author | Rafał Miłecki <rafal@milecki.pl> | 2023-07-25 09:51:35 +0200 |
|---|---|---|
| committer | Rafał Miłecki <rafal@milecki.pl> | 2023-07-25 10:04:34 +0200 |
| commit | c74b5e09e692839b39c8325b5f8dc5f2a3b3896c (patch) | |
| tree | 31a6e1a0fc475b8818a0a6a65d412fa767ba8b54 /package/kernel/linux | |
| parent | d91f38a99e37b3aa45889f21e9522ac443f2662b (diff) | |
| download | upstream-c74b5e09e692839b39c8325b5f8dc5f2a3b3896c.tar.gz upstream-c74b5e09e692839b39c8325b5f8dc5f2a3b3896c.tar.bz2 upstream-c74b5e09e692839b39c8325b5f8dc5f2a3b3896c.zip | |
urngd: update to the latest master
7aefb47 jitterentropy-rngd: update to the v1.2.0
What's interesting about jitterentropy-rngd v1.2.0 release is that it
bumps its copy of jitterentropy-library from v2.2.0 to the v3.0.0. That
bump includes a relevant commit 3130cd9 ("replace LSFR with SHA-3 256").
When initializing entropy jent calculates time delta. Time values are
obtained using clock_gettime() + CLOCK_REALTIME. There is no guarantee
from CLOCK_REALTIME of unique values and slow devices often return
duplicated ones.
A switch from jent_lfsr_time() to jent_hash_time() resulted in many less
cases of zero delta and avoids ECOARSETIME.
Long story short: on some system this fixes:
[ 6.722725] urngd: jent-rng init failed, err: 2
This is important change for BCM53573 which doesn't include hwrng and
seems to have arch_timer running at 36,8 Hz.
Signed-off-by: Rafał Miłecki <rafal@milecki.pl>
Diffstat (limited to 'package/kernel/linux')
0 files changed, 0 insertions, 0 deletions