Since security extension uses the bb file, not the extension using local.conf, the generated filename is different. This sets the correct filename for security extensions. Signed-off-by: Nobuhiro

Hi Jan,

From: Quirin Gylstorff <quirin.gylstorff@...> The kas files ebg-swu.yml and qemu-swupdate.yml overlap in some cases. Clarify their use by moving all efibootguard related configuration to

Right, that file is only an option file anyway. Jan -- Siemens AG, T RDA IOT Corporate Competence Center Embedded Linux

Alternative would be to change ` -WKS_FILE = "qemu-amd64-${SWUPDATE_BOOTLOADER}.wks" +WKS_FILE = "${MACHINE}-${SWUPDATE_BOOTLOADER}.wks" ` Quirin

Yes, Quirin, that's sufficient to point it out.

Yes, just now I have changed settings and made it plaintext while replying, earlier it was HTML. I hope it will fix this issue. Thanks for pointing it. Sure, I will do that.

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. *Please note that the IRC meeting was rescheduled to UTC (GMT) 09:00 starting

I added the following sentence to the README for the keys: The formating is off: Dinesh is that sufficient? Quirin

Thanks, applied to next. We may eventually also want to do a renaming of qemu-swupdate.yml to qemu-amd64-swupdate.yml - just for the case that there will also be ARM qemu target to demonstrate/test

Dinesh, your citation settings are broken. When sending plaintext, as it is common on public lists, you need to set the mark "> " at the beginning of all cited line. Feel free to send a patch (or MR

No idea. All the servers I touched at work were still booting via legacy BIOS. Mind you that these were old servers. The latest machine we have, an AMD EPYC 7002, is UEFI only. I never looked at

Hi! Backport is trivial in this case. This is UEFI secure boot, and it is more of "implement missing blacklist functionality" than a bugfix. If someone uses secure boot on UEFI, we may need to do

From: Quirin Gylstorff <quirin.gylstorff@...> The variable BOOTLOADER is only used for swupdate. Add the prefix SWUPDATE to indicate the intended usage. Signed-off-by: Quirin Gylstorff

From: Quirin Gylstorff <quirin.gylstorff@...> This patch removes the variable U_BOOT from the swupdate-config.bbclass. It also adds the suffix `SWUPDATE` to the variable BOOTLOADER. If a

From: Quirin Gylstorff <quirin.gylstorff@...> The dependency to ${U_BOOT} is unnecessary for the SWUPDATE build and the package deployment. The package `u-boot-${MACHINE}-config` is requested

Hi! Thank you! According to https://ubuntu.com/security/CVE-2021-31829 it is those two patches that fix it. So this should get resolved in 5.10.35 for us. Best regards, Pavel -- DENX

From: Quirin Gylstorff <quirin.gylstorff@...> The variables U_BOOT and BOOTLOADER are only used for swupdate. Add the prefix SWUPDATE to indicate the intended usage. Signed-off-by: Quirin

From: Quirin Gylstorff <quirin.gylstorff@...> The dependency to ${U_BOOT} is unnecessary for the SWUPDATE build and the package deployment. The package `u-boot-${MACHINE}-config` is requested

From: Quirin Gylstorff <quirin.gylstorff@...> This patch removes the variable U_BOOT from the swupdate-config.bbclass. It also adds the suffix `SWUPDATE` to the variable BOOTLOADER. If a