Public bug reported: Running Ubuntu Pro with FIPS enabled on a kernel other than the one provided by Jammy results in an error.
Until a Focal kernel update released in April, this error occurred when Ubuntu Jammy FIPS was run on Ubuntu Focal too. See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2055825 For example, running an Ubuntu Pro 22.04 with FIPS enabled docker image on Amazon Linux 2023 fails when apt-get is used. Here's how to reproduce this issue: 1. Run AL2023 in FIPS mode in a virtual machine 2. docker run -it registry1.dso.mil.ironbank/canonical/ubuntu-pro-cis-fips-stig:22.04_stable (see https://ironbank.dso.mil/repomap/details;registry1Path=canonical%252Fubuntu-pro-cis-fips-stig) 3. In the container, run apt-get update The result is this error: Fatal: unexpected error from getentropy: Invalid argument fatal error in libgcrypt, file ../../src/misc.c, line 146, function _gcry_logv: internal error (fatal or bug) Aborted (core dumped) I believe this issue is also reproducible when using kernels provided by other vendors, such as Microsoft's Azure Linux. ** Affects: libgcrypt20 (Ubuntu) Importance: Undecided Status: New -- 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
