Bug#935945: (no subject)

affects 935945 + linux-image-amd64 thanks

Bug#935945: fixed in linux 5.3.7-1

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

Bug#935945: linux-image-5.2.0-2-amd64: does not load signed kernel modules when UEFI Secure Boot is enabled

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.

Bug#940181: Duplicate

sorry, this is a duplicate of #935945

Bug#940181: linux-image-5.2.0-2-amd64: Kernel does not accept self-signed modules using UEFI db key

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,

Bug#835518: libnetcdf11: no support for NetCDF-4 type NC_STRING

Package: libnetcdf11 Version: 1:4.4.1-1 Severity: important Dear Maintainer, Please include support for the netcdf 4 type NC_STRING. It seems not to be compiled in. When using it for a variable I git an NC_BADTYPE error. This was not the case with the previous package libnetcdfc7. Thank you!