Ubuntu
libgcrypt20 package

  1. Bug #2036724
  2. Comment #7

Comment 7 for bug 2036724

Revision history for this message
Steve Langasek (vorlon) wrote :

> Yes. This wasn't the case when the patch was added, so back then
> it helped make the archive version usable with a FIPS kernel.
> Nowadays we ship our own libgcrypt20 so it doesn't make a difference.

The original reason for this patch being added was LP: #1748310. Do we really want to risk reintroducing such a bug? A FIPS customer who has the FIPS archive enabled SHOULD be using the libgcrypt20 from the FIPS archive; but if they make a mistake and have the libgcrypt20 from the main Ubuntu archive installed, with this patch reverted, will this misbehave on boot?

FIPS is not supported on non-LTS releases so I don't actually care about this from a feature freeze POV, consider the exception granted. But we still need to be sure that dropping this change is the correct thing to do from the perspective of 24.04 LTS.