> From testing it seems this shows up due to swtpm_setup using the openssl
> config for key setup information. I managed to fix the issue by adding
>
> #include <abstractions/openssl>
>
> to the TEMPLATE.qemu file in the apparmor directory. I tested with the
> ppa:
>
> ppa:lvoytek/libvirt-allow-openssl-qemu-jammy
FWIW this is a common problem/fix with openssl3; the exact same fix was
applied to squid's apparmor profile a few days ago.
On Thursday, April 07 2022, Lena Voytek wrote:
> From testing it seems this shows up due to swtpm_setup using the openssl openssl> libvirt- allow-openssl- qemu-jammy
> config for key setup information. I managed to fix the issue by adding
>
> #include <abstractions/
>
> to the TEMPLATE.qemu file in the apparmor directory. I tested with the
> ppa:
>
> ppa:lvoytek/
FWIW this is a common problem/fix with openssl3; the exact same fix was
applied to squid's apparmor profile a few days ago.
--
Sergio
GPG key ID: E92F D0B3 6B14 F1F4 D8E0 EB2F 106D A1C8 C3CB BF14