[Bug 1748310] Please test proposed package

[Robie Basak]

Hello Vineetha, or anyone else affected,

Accepted libgcrypt20 into xenial-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/libgcrypt20/1.6.5-2ubuntu0.4 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-xenial to verification-done-xenial. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-xenial. In either case, details of your
testing will help us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to libgcrypt20 in Ubuntu.
https://bugs.launchpad.net/bugs/1748310

Title:
  [SRU][xenial]boot stalls looking for entropy in FIPS mode

Status in libgcrypt20 package in Ubuntu:
  Fix Released
Status in libgcrypt20 source package in Xenial:
  Fix Committed

Bug description:
  [IMPACT]
  libgcrypt20 is not a FIPS certified library. On a machine running FIPS enabled kernel, the library by default goes into FIPS mode if /proc/sys/crypto/fips_enabled=1. FIPS mode is not a configurable compile option currently in the library. Hence FIPS code paths are always executed on a FIPS enabled machine. In FIPS mode, it runs self tests and integrity checks and it looks for quality entropy from /dev/random. Additionally in desktop environments, gnome keyring daemon also queries libgcrypt for /dev/random entropy, slowing down the GUI startup.  

  On encrypted installations, cryptsetup uses libgcrypt20. During boot
  on an encrypted machine running in FIPS mode, cryptsetup invokes
  libgcrypt and it stalls looking for quality entropy from /dev/random.
  This results in significant delays during startup. The issue was
  reported by a FIPS customer.

  The issue impacts libgcrypt versions in xenial and bionic.

  lsb_release -rd
  Description:	Ubuntu 16.04.3 LTS
  Release:	16.04

  version - 1.6.5-2ubuntu0.3

  lsb_release -rd
  Description:	Ubuntu Bionic Beaver (development branch)
  Release:	18.04

  version - 1.8.1-4

  [FIX]
  This fix proposes to disable libgcrypt reading /proc/sys/crypto/fips_enabled. We only want fips certified modules
  reading this file and running in fips mode. libgcrypt is not one of our
  fips certified modules, so should not be reading this along with our fips certified modules to determine whether to run in fips mode. The libgcrypt fips code in xenial is outdated and some algorithms are no longer allowed by recent FIPS 140-2 standards.

  However, users do have the option to create a /etc/gcrypt/fips_enabled
  file, manually, and force libgcrypt to run in fips mode. We propose to
  leave this as is, so as to not regress anyone who is using this option.
  We believe a user who uses this option is doing so with awareness.

  [TEST]
  Tested on a VM installed with xenial desktop iso and one with xenial server iso. Enabled full disk encryption during install. Tested with and without FIPS. No delays were observed during boot after the fix patch was applied.

  Tested on a VM installed with Bionic development release version of
  desktop ISO with full disk encryption. Installed the xenial FIPS
  kernel and installed the fixed libgcrypt and did not observe any
  delays during the boot.

  With FIPS enabled on encrypted install, without the patch fix, the
  boot stalls before and after prompting for decryption password. In
  desktop installations, a delay is observed during the GUI startup as
  well.

  [REGRESSION POTENTIAL]
  The regression potential for this is small. A fips kernel is required to
  create /proc/sys/crypto/fips_enabled. For users forcing fips mode via
  /etc/gcrypt/fips_enabled or the control option in libgcrypt, nothing has
  changed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libgcrypt20/+bug/1748310/+subscriptions