Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#77089 - [rng-tools] Unable to obtain AES key, disabling JITTER source

Attached to Project: Community Packages
Opened by Eivind (mokkurkalve) - Wednesday, 11 January 2023, 08:27 GMT
Last edited by Toolybird (Toolybird) - Thursday, 12 January 2023, 20:53 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

With rng-tools 6.15-2, jitter entropy source was initialized just fine, but after upgrading to 6.16-1 the following happens:

jan. 11 09:02:35 audhumla rngd[574]: [rdrand]: Initialized
jan. 11 09:02:35 audhumla rngd[574]: [jitter]: JITTER timeout set to 5 sec
jan. 11 09:02:35 audhumla rngd[574]: [jitter]: Initializing AES buffer
jan. 11 09:02:40 audhumla rngd[574]: [jitter]: Unable to obtain AES key, disabling JITTER source
jan. 11 09:02:40 audhumla rngd[574]: [jitter]: Initialization Failed

My processor:

vendor_id : GenuineIntel
cpu family : 6
model : 142
model name : Intel(R) Core(TM) i5-10210U CPU @ 1.60GHz

Additional info:

* package version(s)
6.16-1
* config and/or log files etc.
* link to upstream bug report, if any

Steps to reproduce:

This task depends upon

Closed by  Toolybird (Toolybird)
Thursday, 12 January 2023, 20:53 GMT
Reason for closing:  None
Additional comments about closing:  See comments
Comment by Toolybird (Toolybird) - Wednesday, 11 January 2023, 20:35 GMT
Seems to start up fine in a fresh VM. Have you modified "/etc/conf.d/rngd" ? Either way, this could easily be an upstream issue so you could try reporting it there.
Comment by Eivind (mokkurkalve) - Thursday, 12 January 2023, 20:27 GMT
I reinstalled "jitterentropy-3.4.1-1" and that fixed the issue. Now I can't figure out what might have caused this. Anyway, this ticket can be closed.

Loading...