Re: [OE-core] [PATCH 1/4] libjitterentropy: upgrade 3.6.3 -> 3.7.0

["Mathieu Dubois-Briand" <mathieu.dubois-briand@bootlin.com>]

On Fri Oct 2, 2026 at 9:15 AM CEST, Jaipaul Cheernam wrote:
> Source: CHANGES.md
>
> 3.7.0
>  * Add secure memory implementation for Linux and {Net,Open,Free}BSD, MacOS and Windows
>  * Update supported CMake version to 3.10
>  * doc: use Doxygen-style comments
>  * NTG.1 compliance: Modify startup such that the memory access and SHA-3 loop are treated as independent noise sources which are sampled to collect at least 240 bits each before first block of random numbers is released
>  * Remove all code when JENT_CONF_DISABLE_LOOP_SHUFFLE is unset. This code is already discouraged for a long time. Now it is taken out for good.
>  * If cache size cannot be detected from base system (e.g. virtualization), use the requested memory size.
>  * Change the stuck test to always calculate the absolute values of the 2nd and 3rd discrete derivation of time.
>  * Replace SHA3-256 output generation with XDRBG-256
>  * Prune the jitterentropy.h header file of internal definitions and delcarations which are moved to src/jitterentropy-internal.h. With that, jitterentropy.h only contains the API. This modification does not alter the Jitter RNG behavior at all.
>  * Update secure storage memory implementation for libgcrypt and OpenSSL
>  * Add API jent_status
>
> License-Update: copyright years updated.
>
> Signed-off-by: Jaipaul Cheernam <jaipaul.cheernam@est.tech>
> ---

Hi Jaipaul,

Thanks for the upgrade.

It looks like this is breaking rng-tools:

ERROR: lib32-rng-tools-6.17-r0 do_compile: oe_runmake failed
...
| ../sources/rng-tools-6.17/rngd_jitter.c: In function 'rngd_notime_start':
| ../sources/rng-tools-6.17/rngd_jitter.c:56:45: error: invalid use of undefined type 'struct jent_notime_ctx'
|    56 |         ret = -pthread_attr_init(&thread_ctx->notime_pthread_attr);

https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/4614
https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/4816

Can you have a look at the issue?

Thanks,
Mathieu

-- 
Mathieu Dubois-Briand, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com