Does this mean that haveged is no longer needed on armhf hosts that are running 
kernels later than 5.3.9 ?

I notice my armhf (Cubox) host on Debian Testing  that the haveged daemon does 
not start.

> root@cube:~# uname -a
> Linux cube 5.4.0-3-armmp #1 SMP Debian 5.4.13-1 (2020-01-19) armv7l GNU/Linux
> root@cube:~# service haveged status
> * haveged.service - Entropy Daemon based on the HAVEGE algorithm
>     Loaded: loaded (/lib/systemd/system/haveged.service; enabled; vendor 
> preset: enabled)
>      Active: failed (Result: signal) since Sun 2020-02-09 00:41:35 PST; 10min 
> ago
>        Docs: man:haveged(8)
>              http://www.issihosts.com/haveged/
>     Process: 1033 ExecStart=/usr/sbin/haveged --Foreground --verbose=1 
> $DAEMON_ARGS (code=killed, signal=SYS)
>    Main PID: 1033 (code=killed, signal=SYS)


On Sat, Nov 9, 2019, at 1:50 PM, Ben Hutchings wrote:
> On Thu, 2019-11-07 at 22:36 +0100, Cyril Brulebois wrote:
> > Hi Ben,
> > 
> > Ben Hutchings <b...@decadent.org.uk> (2019-11-07):
> > > Linux 5.4 introduces an in-kernel jitter-entropy implementation for
> > > systems without a usable hardware RNG, which should remove the need for
> > > haveged.
> > > 
> > > We could possibly cherry-pick that change on to 5.3, to avoid the need
> > > for further changes to haveged packaging.
> > 
> > Oh, great.
> > 
> > Feel free to either follow-up on this bug report once you have
> > backported it to 5.3, or alternatively once 5.4 trunk has reached
> > experimental, so that the switch away from haveged can be tested.
> 
> This is included in 5.3.9-1, which is currently building.
> 
> Ben.
> 
> -- 
> Ben Hutchings
> Everything should be made as simple as possible, but not simpler.
>                                                       - Albert Einstein
> 
> 
> 
> Attachments:
> * signature.asc

Reply via email to