Thanks Dimitri, > If this is time critical for you, you could install kmod from focal on > your bionic system (or use it from chroot).
It's nothing urgent. The issue fell out of a script I was working on. But I've got a feeling it's going to take a few years for the kmod changes to become readily available. I'll probably switch to a C program using OpenSSL to do it. Jeff On Mon, Sep 7, 2020 at 5:03 AM Dimitri John Ledkov <x...@ubuntu.com> wrote: > > Hey, > > linux kernel upstream has changed how signatures look like in > v5.2-rc1, and only kmod 27 learned how to parse them. But bionic ships > kmod 24, meaning with hwe / cloud kernels, the information printed by > e.g. modinfo is incomplete. > > Normally bug reports should be opened in launchpad, i have done so now > at https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1894611 > > If this is time critical for you, you could install kmod from focal on > your bionic system (or use it from chroot). > > On Sun, 6 Sep 2020 at 01:40, Jeffrey Walton <noloa...@gmail.com> wrote: > > > > Hi Everyone, > > > > Ubuntu 18.04's modinfo looks like it is subject to > > https://bugzilla.redhat.com/show_bug.cgi?id=1320921 and > > https://bugzilla.redhat.com/show_bug.cgi?id=1490975. > > > > $ modinfo crypto_simd > > filename: /lib/modules/5.3.0-66-generic/kernel/crypto/crypto_simd.ko > > license: GPL > > srcversion: 701320EC07F22E0D8427859 > > depends: cryptd > > retpoline: Y > > intree: Y > > name: crypto_simd > > vermagic: 5.3.0-66-generic SMP mod_unload > > signat: PKCS#7 > > signer: > > sig_key: > > sig_hashalgo: md4 > > > > A quick Google search did not pick up a similar Ubuntu bug report, > > like Red Hat's 1320921 and 1490975. > > > > It looks like the fix was checked in about a year and a half ago. Also > > see https://lwn.net/Articles/779249/. > > > > Would it be possible to pick up the fix? -- Ubuntu-devel-discuss mailing list Ubuntu-devel-discuss@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel-discuss
