I suspect that the root cause of this issue is that Ubuntu Pro FIPS's libgcrypt relies on the Linux getrandom syscall accepting a GRND_RESEED flag, but that flag is not in the upstream Linux kernel so no kernels other than those supplies by Ubuntu Pro support it.
I think the solution is to either not use the GRND_RESEED flag, or to submit the addition of the flag to the Linux kernel project so all kernels will eventually support it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2112154 Title: fips: Fatal: unexpected error from getentropy: Invalid argument To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgcrypt20/+bug/2112154/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
