While I understand the rationale behind this policy, it was a bit jarring to discover the change when 5.15.0-70.77 suddenly rendered my 10GbE interfaces unavailable. I wasn't aware that the qlge module had been moved to staging years ago, and didn't understand what the problem was until I tried to manually load the driver.
It's likely that others are experiencing similar functional regressions. I'm not sure what the best way to ensure a good experience for people affected by this transition is. I ended up disabling Secure Boot rather than e.g. enrolling a new key and signing the module manually for each update. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1642368 Title: linux: Staging modules should be unsigned Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: In Progress Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Won't Fix Status in linux source package in Zesty: Fix Released Status in linux source package in Impish: Won't Fix Status in linux source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Released Bug description: Modules under the drivers/staging hierarchy get little attention when it comes to vulnerabilities. It is possible that memory mapping tricks that expose kernel internals would go unnoticed. Therefore, do not sign staging modules so that they cannot be loaded in a secure boot environment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1642368/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp