Ben, et al, On Sun, 19 Jun 2022 12:59:55 +0200, Ben Hutchings wrote: > In the mean time, we have another security update coming which might > not hit this bug again. But there are 28,679 signed binaries across > the three architectures, so the probability is only about 65%.
I looked at the following new (Jul 2, 2022) binaries: * linux-image-4.19.0-21-686-pae_4.19.249-2_i386.deb * linux-image-4.19.0-21-686_4.19.249-2_i386.deb * linux-image-4.19.0-21-amd64_4.19.249-2_amd64.deb * linux-image-4.19.0-21-arm64_4.19.249-2_arm64.deb * linux-image-4.19.0-21-cloud-amd64_4.19.249-2_amd64.deb * linux-image-4.19.0-21-rt-686-pae_4.19.249-2_i386.deb * linux-image-4.19.0-21-rt-amd64_4.19.249-2_amd64.deb * linux-image-4.19.0-21-rt-arm64_4.19.249-2_arm64.deb There were 25,011 signed kernel modules, with one bad signature: * binary package: linux-image-4.19.0-21-amd64 * version: 4.19.249-2 * file: lib/modules/4.19.0-21-amd64/kernel/net/openvswitch/vport-vxlan.ko Perhaps this bug should be retitled? Thank you! Dan Urbana, Illinois
