Description of problem: Starting with RHEL9, package files have IMA signatures, for example, # dnf install attr rpm-plugin-ima -yq # dnf reinstall iproute -yq # getfattr -m - -d /usr/sbin/ip # file: usr/sbin/ip security.ima=0sAwIE0zIESQBnMGUCMArBSY0jCqiMiJSsMpCz+TUiu8gb39l4Lxm+5+XA7dNfrD/ja5DYaVWjZmWEcW5GFgIxAOFCQTeL27qbPn+FDAEBqzxXsG5uUtAa3Itu/BS/cJiFyQMwCLvE/74DYfF6pHonuQ== Please ship the IMA CA and code-signing certificates as secureboot-ca-ima.cer and secureboot-kernel-ima.cer respectively. secureboot-ca-ima.cer will be built into the kernel's .builtin_trusted_keys keyring and secureboot-kernel-ima.cer will be added to the %:.ima keyring from userspace. Version-Release number of selected component (if applicable): How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: # rpm -ql redhat-sb-certs |grep ima /etc/pki/sb-certs/secureboot-ca-ima.cer /etc/pki/sb-certs/secureboot-kernel-ima.cer Additional info:
> Expected results: > > # rpm -ql redhat-sb-certs |grep ima > /etc/pki/sb-certs/secureboot-ca-ima.cer > /etc/pki/sb-certs/secureboot-kernel-ima.cer One thing to note here is that dracut expects the IMA certs to be in /etc/keys/ima/ (also they're not really secure boot certs).
Closing this bug since there is a new approach to ship the IMA certificates. Thanks all for your attention!