aboutsummaryrefslogtreecommitdiffstats
path: root/include/logo.svg
diff options
context:
space:
mode:
authorRafał Miłecki <rafal@milecki.pl>2023-07-25 09:51:35 +0200
committerRafał Miłecki <rafal@milecki.pl>2023-08-28 16:36:08 +0200
commitaeb1221784c70eccf2d65086b132fb365e4e81a1 (patch)
tree5cdaca26366b6baac3c75ba5a64547b89d5b3450 /include/logo.svg
parent687004139b1e5c85ce01cd6d535fe6c09bb510bb (diff)
downloadupstream-aeb1221784c70eccf2d65086b132fb365e4e81a1.tar.gz
upstream-aeb1221784c70eccf2d65086b132fb365e4e81a1.tar.bz2
upstream-aeb1221784c70eccf2d65086b132fb365e4e81a1.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> (cherry picked from commit c74b5e09e692839b39c8325b5f8dc5f2a3b3896c)
Diffstat (limited to 'include/logo.svg')
0 files changed, 0 insertions, 0 deletions