FS#68828 - [rng-tools] Are jitterentropy activated?

Attached to Project: Community Packages
Opened by Eivind (mokkurkalve) - Wednesday, 02 December 2020, 23:06 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Thursday, 03 December 2020, 00:04 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Massimiliano Torromeo (mtorromeo)
Architecture x86_64
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After rng-tools 6.10-2 rebuild for jitterentropy 3.0.0-1 the output of "systemctl status rngd.service" does not show jitterentropy being enabled at all. Don't know if there is a bug here, but thought I could report as previous [jitter] was in this list, but are now nowhere to be seen:

des. 02 23:46:23 audhumla systemd[1]: Started Hardware RNG Entropy Gatherer Daemon.
des. 02 23:46:23 audhumla rngd[553]: Initializing available sources
des. 02 23:46:23 audhumla rngd[553]: [hwrng ]: Initialized
des. 02 23:46:23 audhumla rngd[553]: [rdrand]: Enabling RDSEED rng support
des. 02 23:46:23 audhumla rngd[553]: [rdrand]: Initialized
des. 02 23:46:23 audhumla rngd[553]: [pkcs11]: No pkcs11 slots available
des. 02 23:46:23 audhumla rngd[553]: [pkcs11]: Initialization Failed
des. 02 23:46:23 audhumla rngd[553]: [rtlsdr]: Initialization Failed


Additional info:
* package version(s)
rng-tools 6.10-2
jitterentropy 3.0.0-1
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:
systemctl status rngd.service
This task depends upon

Closed by  Massimiliano Torromeo (mtorromeo)
Thursday, 03 December 2020, 00:04 GMT
Reason for closing:  Fixed
Additional comments about closing:  rng-tools-6.10-3
Comment by Doug Newgard (Scimmia) - Wednesday, 02 December 2020, 23:15 GMT
It's not linked to the library, so I'm guessing you're right.
Comment by Massimiliano Torromeo (mtorromeo) - Thursday, 03 December 2020, 00:04 GMT
Seems like the new jitterentropy was itself missing a link to pthread. Should be fixed now.

Loading...