FS#60700 - [rng-tools] build with support for jitterentropy
Attached to Project:
Community Packages
Opened by George Angelopoulos (gangelop) - Monday, 05 November 2018, 11:47 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Thursday, 10 January 2019, 20:44 GMT
Opened by George Angelopoulos (gangelop) - Monday, 05 November 2018, 11:47 GMT
Last edited by Massimiliano Torromeo (mtorromeo) - Thursday, 10 January 2019, 20:44 GMT
|
Details
jitter is not available as an entropy source for rngd. Can
we have it back?
It appears that this used to work but upstream has changed from using a git submodule for jitter to expecting it as a library installed on the system. In the git log check the following (https://github.com/nhorman/rng-tools): 57521f8 Allow use of --disable-jitterentropy/--enable-jitterentropy c3de862 rngd: Link against jitterentropy as a shared library 117a742 Removing jitterentropy submodule This might require for https://github.com/smuellerDD/jitterentropy-library I haven't figured out exactly how it should be installed or if the rng-tools PKGBUILD needs to be modified once the library is available on the system. Expected results, JITTER should appear as an available and enabled entropy source: $ ssh rhel7 rngd -l Entropy sources that are available but disabled 1: TPM RNG Device 4: NIST Network Entropy Beacon Available and enabled entropy sources: 5: JITTER Entropy generator Actual results, JITTER doesn't appear as enabled or available: rngd -l Entropy sources that are available but disabled 1: TPM RNG Device (tpm) 4: NIST Network Entropy Beacon (nist) Available and enabled entropy sources: |
This task depends upon
Closed by Massimiliano Torromeo (mtorromeo)
Thursday, 10 January 2019, 20:44 GMT
Reason for closing: Implemented
Additional comments about closing: rng-tools-6.6-2
Thursday, 10 January 2019, 20:44 GMT
Reason for closing: Implemented
Additional comments about closing: rng-tools-6.6-2
> This might require the creation of a new package for https://github.com/smuellerDD/jitterentropy-library
If you rebuild rng-tools with the jitterentropy package installed it works
So how should this work considering it's a build and runtime dependency? Should jitterentropy be brought into the community repo and marked as an optional dependency for rng-tools?
Since rngd will be linked with libjitterentropy it cannot be marked as optional or it'll fail to start if jitterentropy is not installed.
It should be moved to community by a Trusted User.
Usually 10 votes on AUR are needed, but in this case jitterentropy can be considered a new makedeps and so it can probably we moved without waiting for 10 votes (https://wiki.archlinux.org/index.php/AUR_Trusted_User_Guidelines#Rules_for_Packages_Entering_the_.5Bcommunity.5D_Repo)