affects 935945 + linux-image-amd64
thanks
affects 935945 + linux-image-5.3.0-1-amd64
affects 935945 + linux-image-amd64
Thanks!
Unfortunately, the problem still persists in linux-image-5.3.0-1-amd64
(Source-Version: 5.3.7-1) as the MOK is added to the ".platform"
keyring, which is not used for module verification (Niv Sardi's patch
shoul
I also have this problem and, unfortunately did not find this bug report
earlier and opened a duplicate in #940181. As noted there, I believe the
issue can be fixed by setting CONFIG_SECONDARY_TRUSTED_KEYRING=y in the
kernel config.
sorry, this is a duplicate of #935945
Package: src:linux
Version: 5.2.9-2
Severity: important
Dear Maintainer,
I sign the kernel for UEFI secure boot with my own key and also do so for
custom-build kernel modules such as "vboxdrv" for VirtualBox (package
virtualbox-6.0). This worked without a flaw for linux-image-4.19.0-5-amd64, bu
5 matches
Mail list logo